So, I have a big problems on my hands! I can't replace all cvs/root files when a user logs in, because there can be more than one user on-line at once and it isn't pratical!
So I could change only the cvs/root file only when the user submits the new translation. If changing the root file every time is the solution, I can try to build the first beta release using this, and then see if it works fine. Your idea to let a non-cvs user to translate files is one I would like to hear from others. Maybe this would be good for projects admins to check the translator's quality. The user would create an account (only in the mysql DB), translate some files and then the admin would give him an account or ban him from the system :D Nuno Lopes P.S.: Thanks Gabor and Sean for your help & ideas! ----- Original Message ----- From: "Gabor Hojtsy" <[EMAIL PROTECTED]> To: "Nuno Lopes" <[EMAIL PROTECTED]> Cc: "Sean Coates" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, October 08, 2003 7:45 PM Subject: Re: [PHP-DOC] Re: cvs questions > CVS authentication is the tool for this... It is not at all hard to get > a CVS account, it the developers are convinced you will do something. > With such an online app, you can translate content, and let somebody > with a CVS account to commit the translation sometime. After you have > showed that you do contribute (and that someone with CVS account > proofreaded your translation and says you are a good guy), you have > fairly good chance to get that CVS account. Getting a CVS account is > something of a rewrad too, so I don't think that pushing away people > from it is a good idea at the psichological side of things either... > > IMHO the system should be ready to store translations done by some > non-CVS user, and let some CVS user commit those changes. > > Goba
