On Tuesday, 22 September 2015 01:38:03 UTC-7, William wrote:
>
>
>
> On Monday, September 21, 2015, Dima Pasechnik <dim...@gmail.com 
> <javascript:>> wrote:
>
>>
>>
>> On Monday, 21 September 2015 21:42:31 UTC-7, William wrote:
>>>
>>> On Mon, Sep 21, 2015 at 7:58 PM, Kwankyu Lee <ekwa...@gmail.com> wrote: 
>>> > I have written a couple of AUTHORS-blocks, but I think I did it not to 
>>> have 
>>> > a credit but to be responsible for the code. 
>>> > 
>>> > AUTHORS blocks are rather for developers, not for end users. 
>>> These blocks 
>>> > are rather hindrance for end users as  they usually appear at the head 
>>> of a 
>>>
>>> When I "invented" this idea of AUTHORS blocks, they were definitelynot 
>>> only for developers but also for end users.    They were partly meant 
>>> as an antidote to what happened with Magma when "they" deleted all the 
>>> names of many of the contributors to Magma from the beginnings of the 
>>> relevant sections of the reference manual, which pissed a lot of 
>>> contributors off. 
>>>
>>> When you read a mathematics paper you don't say "this statement of the 
>>> authors of this paper at the top is not for readers and is a 
>>> hindrance". 
>>>
>>> If anything, I think we should systematically do vastly *more* to 
>>> clearly acknowledge and appreciate the code contributors to Sage. 
>>> They are by far the most important people to the existence of Sage. g
>>>
>>
>> I know at least one prolific Sage contributor who does not add himself to 
>> AUTHORS block,
>> and actually is removing these blocks.
>>
>
> Who?
> Is he removing his own name or other people's name?
>
see done by the request of the reviewer

http://git.sagemath.org/sage.git/commit/?id=edb886e9f9d0f505f272fe769e69e8a51ab265df
on http://trac.sagemath.org/ticket/19098 

One way or another, there are Copyright notices with names in many files, 
and Author entries, sometimes they
have to do something with each other, sometimes not, sometimes there are 
huge additions done
by people without adding their names to either of these fields...
It's a mess.



>> IMHO we need an official policy on this. 
>>
>>
>>
>>>  -- William 
>>>
>>> > documentation but these information, like TODO and TESTS, is not 
>>> usually 
>>> > what the user expects to see in the doc.  These developer-oriented 
>>> blocks 
>>> > are better to be hidden or placed in less prominent place for the end 
>>> users. 
>>> > 
>>> > -- 
>>> > You received this message because you are subscribed to the Google 
>>> Groups 
>>> > "sage-devel" group. 
>>> > To unsubscribe from this group and stop receiving emails from it, send 
>>> an 
>>> > email to sage-devel+...@googlegroups.com. 
>>> > To post to this group, send email to sage-...@googlegroups.com. 
>>> > Visit this group at http://groups.google.com/group/sage-devel. 
>>> > For more options, visit https://groups.google.com/d/optout. 
>>>
>>>
>>>
>>> -- 
>>> William (http://wstein.org) 
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sage-devel" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sage-devel+unsubscr...@googlegroups.com.
>> To post to this group, send email to sage-devel@googlegroups.com.
>> Visit this group at http://groups.google.com/group/sage-devel.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Sent from my massive iPhone 6 plus.
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to