On Jan 3, 5:03 pm, David Siegel <[email protected]> wrote: > Here's an article demonstrating many of these recommendations: > > http://datadesk.latimes.com/posts/2012/01/sphinx-on-github/ > > David
Hi David, Thanks for the link, that seems like a powerful workflow. I'm not sure if I have the power or ability to do those things, but maybe someone does! ta, Oisín > On Monday, January 2, 2012 at 11:43 AM, David Siegel wrote: > > Oisín, thank you for taking this on. > > > I receive a few emails per month about this issue, and although I don't see > > it as my concern since I haven't been involved in the project for a few > > years, I do have some recommendations: > > > * Move the project from Launchpad/Bazaar to GitHub/Git. > > * Move the entire website, including the wiki, under version control. > > * Create a Git-based workflow for contributing to and updating the website, > > which reuses the same authentication and group permissions as the code > > host, so that anyone can proposes merges for the website, and any > > contributor can push updates to the live site. > > > As far as the Git-based workflow is concerned, I would recommend porting > > the existing site to a static site generator such as Jekyll or Middleman. > > If the new website were build with one of these static generators, and > > hosted on GitHub, we could use GitHub's static website serving (GitHub > > Pages) to automatically serve the site from the Git repo. This would > > naturally inherit GitHub's team authentication, solve the spam problem, and > > give us a much more robust way to make and publish changes. > > > David > > > On Saturday, December 31, 2011 at 4:03 PM, Oisín Mac Fhearaí wrote: > > > > Hi all, > > > > I went to the Do website on davebsd.com (http://davebsd.com) today to > > > look for some basic > > > instructions on using Do. Eventually I found the instructions, but not > > > before being totally bombarded by spam. So I cleaned up a few of the > > > pages, reverting months of crud from spammers fighting each other. > > > Checking again about 8 hours later, there were already a bunch more > > > new pages created by spambots. > > > If nobody has time to install some kind of Captcha tool or something, > > > then maybe new page creation should be disabled, or even all edits to > > > the wiki other than by one or two admins? > > > > Also it would be nice to update the version info - at the moment it > > > says the last release was in 2009, and the immediate impression the > > > site gives is that the project is dead, which it apparently is not! :) > > > > p.s. Happy new year! > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "GNOME Do" group. > > > To post to this group, send email to [email protected] > > > (mailto:[email protected]). > > > To unsubscribe from this group, send email to > > > [email protected] > > > (mailto:[email protected]). > > > For more options, visit this group > > > athttp://groups.google.com/group/gnome-do?hl=en. -- You received this message because you are subscribed to the Google Groups "GNOME Do" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en.
