Tim Perdue <[EMAIL PROTECTED]> tapota :
>>>Savannah -> GForge migration will begin soon >> What does it have to do with a merge? Do you call that a success >> story, a succesful platform that get broken for more than a month with >> decisions being made for no known reasons, against the will of the >> people that made the platform running almost only by themselves over >> the year? > > Maybe you just aren't aware of the reasons? In my previous mail, I said that if an authoritative message was available on the archives of a public list, I would be happy to get a pointer to it Unless such reasons are publicly mentioned, or at least to the persons that made Savannah running for the last three years, I will not consider myself as aware of such reasons. > I have received phone calls from FSF that said they had a lot of > reasons that made sense to me. Mainly, that their old codebase was > not being actively developed any more The ChangeLog of the Savane sourcecode proves the contrary. Since I had a dinner with Richard Stallman in November while I was hired to work on this code base and we talked about Savannah, it is hard to explain how such an erroneous statement could have been made. > and that their volunteers would not tolerate the new security > restrictions. That's just about savannah.gnu.org, it is not related to Savannah. What is called here "new security restriction" is just establishment of a distrust attitude. That's a completely different issue. And to talk about security, with this attitude, Savannah would be still compromised. The rootkit has been found by someone joining the team very very recently before the compromise. Since he had the idea to made such checks while usual maintainers (including me didn't) and since the FSF USA staff was probably not considering doing such check (since doing a kernel upgrade was not possible for them since several months), there is no reason to think that the compromised would have been found otherwise. So when it comes to "new security restrictions", you just talk about savannah.gnu.org day to day maintainance. But frankly, you do not plan to reply to users request at savannah.gnu.org, do you? These reasons just don't make sense. I suspect people that gave you that reasons to know that. That's the only explanation I can come up with to explain the fact that they are not willing to publicly give their reasons. Regards, -- Mathieu Roy +---------------------------------------------------------------------+ | General Homepage: http://yeupou.coleumes.org/ | | Computing Homepage: http://alberich.coleumes.org/ | | Not a native english speaker: | | http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english | +---------------------------------------------------------------------+ _______________________________________________ Savane-dev mailing list [EMAIL PROTECTED] https://mail.gna.org/listinfo/savane-dev
