Re: improving our translations process

[email protected] (Philip Olson) Tue, 14 Apr 2009 12:45:45 -0700
Newsgroups php.doc,php.doc.ar,php.doc.bg,php.doc.cs,php.doc.da,php.doc.de,php.doc.es,php.doc.el,php.doc.fa,php.doc.fi,php.doc.fr,php.doc.he,php.doc.hk,php.doc.hu,php.doc.it,php.doc.ja,php.doc.kr,php.doc.nl,php.doc.pl,php.doc.pt,php.doc.pt-br,php.doc.ro,php.doc.ru,php.doc.sk,php.doc.sl,php.doc.sv,php.doc.tr,php.doc.tw,php.doc.zh,php.doc.no,php.doc.se
Message-ID <[email protected]>
On 14 Apr 2009, at 08:50, Benjamin wrote:

> transifex looks like an excellent alternative.
>
> Philip on the strategy of user registration, group organization, are  
> there
> any new proposal?, that the current method works very slowly, maybe  
> a lot of
> bureaucracy

I'm not exactly sure what you mean here (please explain) but am unsure  
how exactly our php.net accounts would interface with a system like  
transifex, like if we'd also have users with only access to transifex.  
This topic is part of the research process.

I don't see a problem with the theory behind the current registration  
system which is:
  - If people have work to contribute, they are given account
  - If people want an account, they first have work to contribute
  - Doing work does not require an account, but leads to one
  - People introduce themselves into the community before being given  
an account

How exactly this is managed could likely be improved but there are  
plenty of people out there who simply want, for example, a @php.net  
address without doing anything except ask for it. And gaining commit  
access without showing capacity to commit decent work or be involved  
with the community doesn't feel right. Not that anyone is suggesting  
that, but it's something the current system deals with.

All ideas and thoughts are welcome and up for discussion although this  
is getting a bit off topic for this thread.

Regards,
Philip