-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Sylvian,
On Thursday 08 Apr 2004 12:12, Sylvain Beucler wrote: > Hello, > > Thank you for asking. > > After I saw references to moving to GForge and Hugo's question, I > tried to get more information. > > The decision to move to GForge was made by Bradley Kuhn and the system > adminitrators, according to Richard Stallman. They considered Savane > could not be made secure enough. It would be interesting to discuss > that point, as Savane was just security audited. Thank you for letting me know about this, Sylvian! Now, if Bradley, Richard et al. are willing to discuss the above two points in the open I think we can take this somewhere: What security concerns do you have with Savane? Did you speak to the developers of Savane? I find "Savane could not be made secure enough" a silly reason to look elsewhere. (Perhaps silly is not the correct word.) You have not done that with other GNU software (insert package name here) so why so when it comes to Savane? I don't remember ever hearing that the FSF/GNU moved from GNU/Linux, CVS, etc., due to security problems.. If you are going to set that precedent with Savane, when will you be moving from GNU/Linux to Hurd/*BSD/... ?? > I also mentioned that the GForge team do not value copyleft (notably > as defined in Affero's license) as much as Savane's do. RMS replied it > was similar to using Apache. After thinking about it, I find this > argument discutable since there is no copyleft technical equivalent to > Apache, unlike in this case. This is actually one of the main concerns I have with GForge. I think this should be addressed.. > Another comment I got, from the sysadmins, is that Tim Perdue is > willing to make the changes necessary to make GForge usable at > Savannah. Given our current wishlist: > http://mail.gnu.org/archive/html/sv-migration/2004-03/msg00000.html; > and that people at Savane know Savannah better than GForge's staff, > using GForge will add delays. Considerably, I would think. And, remember how long it has taken just to get minimal services back up for developers to continue. I'm still waiting for my project to be imported from my RCS files.. Admittedly, I will not ask for this to be done until such basic things, such as being able to edit the `CVSROOT/modules' file, is available. > No discussion took place indeed, so we should have one right now :) > Post your thoughs. > As far as I am concerned I think upgrading to Savane would be better, > for the reasons above. I absolutely agree with you. Which is why I sent the previous mail! :) I have laid out my points, hopefully we will get a response so we can start talking. > Last, I currently lack time to deal with Savannah, and nobody can help > me answering support request at the moment (there was an help offer, > but that person disappeared). I would be pleased to get have some help > from you. It is always difficult to add somebody in a team (hence > maybe Bradley's reply to your previous offer - I myself had to insist > before Rudy and Hugo included me in the team), but I am concentrating > some information on Savannah and should be able to answer most of your > questions. I am willing to help as much as possible, and at the moment (the next couple of months) I can spare the time. I will of course have my day job to do, but I can dedicate a few hours per day to the cause. I have subscribed to savannah-hackers, but it appears my request was not approved by the list moderator! Sylvian, do you know if there is an IRC channel anywhere where we can discuss some of this live? I seem to remember a #savannah channel somewhere.. Elfyn PS- are any of you @gnu.org getting these mails? I'm not seeing them appear in the archives of the lists, and so far, have only had one response from Sylvian. - -- Elfyn McBratney, EMCB mailto:[EMAIL PROTECTED] http://www.emcb.co.uk/ PGP Key ID: 0x456548B4 PGP Key Fingerprint: 29D5 91BB 8748 7CC9 650F 31FE 6888 0C2A 4565 48B4 "Proud to be GNU/Linux Free" >> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ << << ~ Linux london 2.6.5-emcb-241 #2 i686 GNU/Linux ~ >> >> ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ << -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAdar7aIgMKkVlSLQRArADAKC2bxFWj4/rFNnev4tNBhZdZUGECwCgpVQF vtYZrFK3tvQvLjruFLV78xo= =4w7k -----END PGP SIGNATURE-----
