Re: [Savannah-hackers-public] Side comments
(The ssl cert thing is likely rather off-putting, but of course that's a different issue.) I don't appreciate the form of this comment. Following your initial inquery at savannah-hackers-public it was shown that Reed's issues were inexistant and I have yet to hear any supported argument on the matter, that is, fitting our education effort a bit more than off-putting in the middle of an unrelated conversation. You don't have to use SSL in that case, and if you still get warnings when you do, check http://savannah.gnu.org/tls/ -- Sylvain
Re: [Savannah-hackers-public] Modifying Savannah website
Hi, http://savannah.gnu.org/register/requirements.php This one is here: http://web.cvs.savannah.gnu.org/viewvc/administration/content/gnu-content/register/?root=administration To modify it: cvs -d:pserver:anonym...@cvs.sv.gnu.org:/web/administration co administration/content/gnu-content/register The checklist on the registration page is a good start but I think it will need additional information. So I want to modify this page in a way that I hope will make it more clear that: It's here, but it's raw PHP code: http://git.savannah.gnu.org/cgit/savane-cleanup.git/tree/frontend/php/register2/index.php Better send a patch. You might want to place strong (bold), big, and emphasis html tags on text that link to the requirements. Different issue, but since it came up ... for me, the brown color for links used on savannah is quite hard to distinguish from normal text. (My vision is not the best.) If we let people have their own normal link color, they would stand out a lot more. This one is here: http://git.savannah.gnu.org/cgit/savane-cleanup.git/tree/frontend/php/css/Savannah.css Please send me a patch :) a) The project will be denied approval until all mandatory requirements are met. Submissions that obviously ignore these points are disapproved without further comment. That doesn't sound good. Always justify. However closing a submission immediately in such case instead of keeping it open for 2 weeks sounds acceptable. -- Sylvain
[Savannah-hackers-public] Re: Savannah download stats progress
On Tue, May 12, 2009 at 12:30:50AM +0200, Alex Fernandez wrote: Hi Sylvain, On Fri, May 8, 2009 at 10:20 PM, Alex Fernandez ely...@gmail.com wrote: Please reply or join #savannah for the next steps :) There you go! Do I have to do anything else here? You're root now. As usual: document what you do, fix what you break :) -- Sylvain
Re: [Savannah-hackers-public] Modifying Savannah website
On Wed, 2009-05-13 at 10:44 +0200, Sylvain Beucler wrote: This one is here: http://web.cvs.savannah.gnu.org/viewvc/administration/content/gnu-content/register/?root=administration Great, I will merge the other requirements with this page. a) The project will be denied approval until all mandatory requirements are met. Submissions that obviously ignore these points are disapproved without further comment. That doesn't sound good. Always justify. Well, I have never known how to politely justify the disapproval of projects like this one: https://savannah.gnu.org/task/?9347 I am out of words, so to speak :)
Re: [Savannah-hackers-public] Modifying Savannah website
a) The project will be denied approval until all mandatory requirements are met. Submissions that obviously ignore these points are disapproved without further comment. That doesn't sound good. Always justify. Well, I have never known how to politely justify the disapproval of projects like this one: https://savannah.gnu.org/task/?9347 I am out of words, so to speak :) We don't offer test accounts ? ;) -- Sylvain
[Savannah-hackers-public] Re: Savannah download stats progress
You're root now. Wow, thanks. As usual: document what you do, fix what you break :) As Stan Lee characters like to say, with great power comes great responsibility :D Will try to be responsible and take our little project forwared with as little disruption as possible. Alex.
Re: [Savannah-hackers-public] Side comments
(In short: forget the whole thing, all is well.) I don't appreciate the form of this comment. Sorry. Following your initial inquery at savannah-hackers-public it was shown that Reed's issues were inexistant and I have yet to hear any supported argument on the matter, that is, fitting our education effort a bit more than off-putting in the middle of an unrelated conversation. I was not trying to again bring up the question of which CA to use. I was only referring to the fact that what new users were seeing is the I don't know your root authority dialog box, or (I guess) something even worse in firefox3. I think that was indeed off-putting. It occurred to me because we were talking about ssl, user experiences, and such already. However, I just now tried to open https://savannah.gnu.org in the firefox3 from CentOS, and, it seems that the cacert root is in ff3 after all! I was not aware of that. So -- yay! Everything seems good. You don't have to use SSL in that case, I don't understand that. As far as I can tell, it's not possible to get an account or register a project without using https. (Which seems perfectly fine.)
[Savannah-hackers-public] Savannah rewrite -- It has been discussed
* the value of a good architecture and modularized design: XML-RPC Fear about slowness: database query + XML-RPC transport To solve such problem both applications could be located in the same LAN or maybe even in the same machine, not in different Internet servers. * Disadvantages of using LDAP to manage users authentication. * UTF-8. * Relational data bases and the value of strong relations (foreign keys). * Unit Testing. * MySQL (MyISAM, InnoDB, MariaDB, Sun-Oracle, ...) vs PostgreSQL, SQL standards. * Django. ... * Proposed plan to realize the data migration after the new Savannah be ready: 1. Do a good analysis of the data we have now. The webapp is to manage the data; the data is the main part. 2. Do a good new database+filesystem design to hold such data. 3. Do a migration test. 4. Develop the new application which will work with such data and the new which will come. 5. Migrate data, and test that the migration was right. * For the Savannah redesign, replace MD5 hashes using the Django support for using 'sha1 + salt' or ...
[Savannah-hackers-public] Savannah and GNU Herds integration
This has been proposed: * Each webapp will maintain its frontend. * Integrate at XML-RPC level. Do not share code; anyhow the new Savannah will be Django based and gnuherds is PHP. * Keep gnuherds data in gnuherds database, and use XML-RPC only to fetch Savannah and gnuherds common data. * Components or functionality which we could integrate: * Users registration and authentication. * Skills management. * Donation pledge to Project or Task. * Look-for-volunteers list. * Job posting, if Savannah team want ... ... I will begin to develop and test in my development environments the first point user registration and authentication via XML-RPC to access current Savannah database (+ the security level to do so) and modifying the gnuherds code to rely on it.
Re: [Savannah-hackers-public] Side comments
Karl Berry wrote: However, I just now tried to open https://savannah.gnu.org in the firefox3 from CentOS, and, it seems that the cacert root is in ff3 after all! I was not aware of that. So -- yay! Everything seems good. I just tried this in a freshly installed Firefox 3 from mozilla.org upstream and it didn't include the cacert root certificate. (The cacert root may have been installed by your distro or you may have taken it yourself like I have done.) Since it isn't in the upstream and a lot of people install from the upstream I think that a lot of users will still be seeing the untrusted cert dialog in FF3. Darn. I was excited that it was going to be in there. Bob
