Some contributors may object to their email addresses being put in plaintext files.
I don't have a workaround, and the ASF uses email addresses as identifiers and as part of code provenance. So long as there is a place where we can recover email addresses from the names we list, I think we can demonstrate provenance without publishing the email addresses directly. In general, we do not accept anonymous contributions, so there needs to be a way to handle the objections, whenever one arrives. It is probably better to figure this out now rather than wait until a contributor complains. - Dennis -----Original Message----- From: Peter Kelly [mailto:[email protected]] Sent: Saturday, August 1, 2015 09:12 To: [email protected] Subject: Re: [PROPOSAL] make release 0.1 > On 1 Aug 2015, at 11:10 pm, Peter Kelly <[email protected]> wrote: > >> On 1 Aug 2015, at 10:18 pm, jan i <[email protected]> wrote: >> >>> Another thing I would like to suggest is we have a CONTRIBUTORS file (or >>> similar name) which lists all those who have contributed to the project. >>> I’m aware this isn’t strictly required, but I think it's a good way to give >>> credit/recognition to everyone involved for their work. >>> >> +1, I assume you mean the file contains the names of people who have >> actively done commits on what is being released ? > > Yes - everyone who’s name is present as an author or committer in the git log > (or mentioned there as having been the author of a patch). I think a simple > alphabetical listing of names & email addresses would be appropriate. BTW I volunteer to create this as well. — Dr Peter M. Kelly [email protected] PGP key: http://www.kellypmk.net/pgp-key <http://www.kellypmk.net/pgp-key> (fingerprint 5435 6718 59F0 DD1F BFA0 5E46 2523 BAA1 44AE 2966)
