First shot to the AUTHORS and CONTRIBUTORS file in the TODO list
Thomas Arendsen Hein
thomas at intevation.de
Wed Jun 29 15:41:07 UTC 2005
* Rafael Villar Burke <pachi at mmn-arquitectos.com> [20050629 17:17]:
> Thomas Arendsen Hein wrote:
> >>+Thomas Arendsen Hein
> >
> >Hey, you got my last name sorted correctly ;)
> (A new patch is attached listing Mr.Hein in the right alphabetical order).
Oh no, the first patch was indeed correct!
My last name really is "Arendsen Hein".
> >And maybe the email addresses should be added, too?
>
> He, he, I'm completely certain you deserve a higher place in the list,
> as you have been doing a lot of good work to get Mercurial as good as it
> is now,
Thanks, though I'm only trying to polish the surface.
Other people (especially Matt) did the real work of getting the core
running.
> but alphabeticall order is less hairy than merit order here... ;).
Absolutely right :)
> I wouldn't add email addresses, as it makes the list more difficult to
> maintain
This doesn't matter that much, it is more for distinguish people
with similar or even identical names: Before my marriage my last
name was "Koester", there are two other "Thomas Koester" in the city
I live, and about 70 others in the northern part of Germany.
> and it's an easy way to get a whole lot of spam.
Replacing "@" with " at " should be enough obfuscation, as the email
addresses show up in the same format on the ML archive pages.
> As for CREDITS, I think CONTRIBUTORS can be renamed to it, I just used
> that name as it's quite common in gnome projects and I feel it's easier
> to have a list of contributors who have sent patches that got merged and
> be fair, than giving credit to some other projects.
The primary purpose for the CREDITS file would be for listing
contributors, but this name is more flexible, and it is shorter :)
> This last option can be tricky without much gain.
CREDITS (or CONTRIBUTORS) is not about gaining something, but about
giving away something, i.e. credits.
> If some code gets into Mercurial it should
> be stated in the copyright notice
Of course, this is important in the file where the code was put in.
> or in the README.
This might clutter the README too much.
Thomas
--
Email: thomas at intevation.de
http://intevation.de/~thomas/
More information about the Mercurial
mailing list