On Sun, 2007-03-25 at 20:28 -0500, Adrian Holovaty wrote: > On 3/25/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > Given our "no names in code" policy, I'd been thinking about not > > applying this. All translators' names are (or should be) in AUTHORS in > > any case. > > > > Apologies for not making my intentions clear in the ticket: I was > > waiting until after 0.96 to have the conversation, since we didn't seem > > to have enough spare cycles to address even all the things we had to do > > before hand. > > > > Are you happy with having all the credits at the top like this? > > Ahh -- great point. I completely neglected to consider that policy. My > mistake! > > Are there any arguments *for* breaking the policy and including the > names? If not, let's roll it back.
I don't think there are strong arguments for including the names. Ironically, the patch was submitted because of a suggestion I made on the i18n list and only 24 hours later did I think of how it integrates with our policy (I realised that translators were no more or less special than other contributors). One thing we do have to watch out for as translation activity picks up is that we currently have no language coordinators/maintainers. This could potentially lead to translation "battles" with some phrases changing back and forth, if there's any confusion or dispute. Having the names of previous contributors makes tracking down the history and resolving these problems a little easier. However, Jacob and I have discussed (after prompting from the translators) giving commit privileges under django/conf/locale/ to certain language maintainers -- one for each language -- to keep things on an even keel there. That makes a lot of sense to me, because, frankly, I have no way to judge if a patch for, say, the XYZ locale is an improvement or not; I would much rather have a native speaker take responsibility there. Jacob wants to make it easier for those people to set up passwords via the web interface to ease his load a little, so that will happen in due course, but I realise he seems pretty busy at the moment, so I'm not pushing that yet. For now, we don't really have a problem here, so it's not blindingly urgent. Assuming you're happy with allowing locale maintainers to commit directly (it's pretty normal on a lot of other projects), I don't think there's a technical reason for having the names in the code, so we should be consistent. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
