<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#ffffff"> Hi all, I'm certainly not an authority in this field, but willing to change our tools (SVN, mercurial, Drupal or whatever), a few weeks before the event is not really a bright idea in my point of view. We already spent weeks doing the actual LGM2011 website, and even if it's not prefect, it do the job. In the best scenario , trying to restart everything again now will only conduct to a beta quality website two weeks before the event. Furthermore, using a revision control system is not ideal because it increase complexity, and forbid quick testing in the production environment (it's easy to make a typo mistake in a javascript file for example). Drupal is a good CMS, but we will need time to set it up fully, so it will be wiser to use it for next year. Said simply, as already said by a number fo people here, let's focus on next tasks instead of re-doing the same ones again and again. Cheers, Camille Le 20/03/2011 22:32, a.l.e a écrit : <blockquote cite="mid:20110320223259.1b599984@eisflach" type="cite"> <pre wrap="">ciao yuval, </pre> <blockquote type="cite"> <pre wrap="">On March 18, 2011 07:57:25 pm a.l.e wrote: </pre> <blockquote type="cite"> <pre wrap="">the content is managed in a wiki form and is stored in a database. </pre> </blockquote> <pre wrap=""> the source control architecture would not back up the database itself, only the code to generate it and access it. however you don't need SSH to access a wiki/database from the html front end? </pre> <blockquote type="cite"> <pre wrap="">the access to the server is only need to modify the forms and the templates. </pre> </blockquote> <pre wrap=""> for forms and templates it would work. i have set up recently a mercurial over https configuration. it boils down to adding users in the .htaccess file, no SSH access required (which I understand is what you are wary about?). </pre> <blockquote type="cite"> <pre wrap="">personally, i haven't yet used mercurial yet (nor git; i still normally use svn, which is not ok to publish a website). </pre> </blockquote> <pre wrap=""> Why do you state that SVN is not OK to publish a website? Hugin moved to Mercurial only a year ago. Prior to that it was in SVN. The website too. And it worked well. </pre> </blockquote> <pre wrap=""> it's not really practical to put a svn check out on a webserver: it's polluted with .svn directories... </pre> <blockquote type="cite"> <blockquote type="cite"> <pre wrap="">let's see how we will manage the site next year... i think that we will give up with anwiki. mercurial could then be a way to manage it! </pre> </blockquote> <pre wrap=""> I don't know the site's architecture. I do know that before giving up a tool I would want to have a comprehensive look at what works and what not, and make sure that the change of tool is not just for the sake of changing tool. </pre> </blockquote> <pre wrap=""> we are changing now for drupal. the new site will be up as soon as possible. i hope we won't have to change again next year! not sure if it's worth to put a drupal instance in a revision system... we will see. ciao a.l.e _______________________________________________ CREATE mailing list <a class="moz-txt-link-abbreviated" href="mailto:CREATE@lists.freedesktop.org">CREATE@lists.freedesktop.org</a> <a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/create">http://lists.freedesktop.org/mailman/listinfo/create</a> </pre> </blockquote> </body> </html>