how can users be removed from contributor list?

Valient Gough vgough at pobox.com
Tue Feb 1 06:45:12 CST 2005




Dafydd Harries wrote:
>Ar 31/01/2005 am 23:25, ysgrifennodd Valient Gough:
>  
>>Dafydd Harries wrote:
>>    
>>>Since we can differentiate between translators who have contributed at
>>>some time in the past and translators whose work is currently included,
>>>I suggest we split the contributors list into two parts: current
>>>contributors and past contributors.
>>>      
>>But then speaking as someone who will package up the translations, I'm 
>>just going to combine those lists and sort them either alphabetically or 
>>maybe sometimes in spiffy random order
>>    
>
>Sure. With this way of doing things, maintainers have the choice of
>which they would like to use, and the information is still useful for
>people just looking on the website.
>
>  

Instead of aggregating the information into 2 lists, maybe you could 
summarize the information?  For instance, I take it you know how many 
translation entries are still active for a particular contributor 
(although I think some of this information has been lost), and how long 
ago it was they made their last contribution.   That would make it 
possible for a maintainer to decide how to group the list of translators 
(if they want to group them at all). 

A small project as mine is bound to get fewer translation contributions, 
so if you have just a single definition of what a past contributor is 
vs. a current contributor, then small projects may get listed as having 
mostly past contributors and few current ones.

Also, this is a rosetta specific measure, isn't it?  When I upload a new 
.po file, it may contain changes from other sources, which will not be 
represented in rosetta..  Rosetta says that I'm the primary contributor 
for most of my .po files, even though I didn't do anything but fix up 
some formatting problems.

That is one reason why I'd rather err on the side of equally crediting 
all contributors, because the system is not yet accurate enough to 
assign credit without mistakes.  And since I don't know of any way to 
manually correct mistaken credit assignment, that means the base credit 
data is known to contain errors..

Valient





More information about the rosetta-users mailing list