Hi all, First, current setup makes it hard to change anything regarding the way our Wordpress instance looks. I'm not talking about content here, this is ok as we have editor accounts set up. If you want to do even a minor correction to the CSS or the template, you have to clone Og's repository from github, commit your changes locally and then pass your changes to Og so that he pushes them to his repo and applies them to the Wordpress instance running on www.foresightlinux.org. That means that there's no way to test your changes before you submit them and that also means a lot of possible bottlenecks.
So the proposed change is to use next.foresightlinux.org as a test instance. People that need to change things on the website would have access to a git repo (I think we could use Og's) where they could push their changes directly. next.foresightlinux.org would always run master HEAD and once a satisfying version has been reached, you'd just tag it and a post-push hook (called post-receive on github) would then trigger a copy to www.foresightlinux.org. This proposal comes mostly from my thoughts about it and the discussions I had with ermo. I'd welcome any comment on that or even better ideas if you happen to have some. :-) I expect at least Paul Scott-Wilson (maintainer of next.fl.org) and Og Maciel (current maintainer of our Wordpress instance) to show up and give their opinion on this topic and proposal. Second, a "website clean up + add content" sprint will happen on Friday the 21st, at 14:00 UTC (http://www.timeanddate.com/worldclock/fixedtime.html?year=2009&month=8&day=21&hour=14&min=0&sec=0). If you want to give a hand, feel free to join us on #foresight-qa on Freenode. -- Alexandre Franke _______________________________________________ Foresight-devel mailing list Foresight-devel@lists.rpath.org http://lists.rpath.org/mailman/listinfo/foresight-devel
