[issue6992] Adding a Contributor field in PEP 314

Marc-Andre Lemburg added the comment: Tarek Ziadé wrote: > > Tarek Ziadé added the comment: > >> The meta-data is only used by PyPI and perhaps a handful >> of other tools. > [...] >> The addition of the maintainer meta-data field would >> not hurt anyone and create more consistency. > > si

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: > The meta-data is only used by PyPI and perhaps a handful > of other tools. [...] > The addition of the maintainer meta-data field would > not hurt anyone and create more consistency. since PyPI has its own Role system (owner, maintainer) managed by the user who

[issue6992] Adding a Contributor field in PEP 314

Marc-Andre Lemburg added the comment: Tarek Ziadé wrote: > So at the end, the changes on distutils setup() side would be: > > - authors (goes in Author field - with "," separations ) > - contact_email (goes in Author-email field) > - deprecation of the "author", "author_email", > "maintain

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: > Right, but then we have: > > author > author_email > authors > maintainer > maintainer_email > > for consitency, we'd also need: > > author_emails > maintainers > maintainer_emails In my mind the "perfect" situation would be just two arguments: - authors (goes

[issue6992] Adding a Contributor field in PEP 314

Marc-Andre Lemburg added the comment: anatoly techtonik wrote: >> What does changing the type of the "author" field make clearer exactly? >> It is a field for human beings to read, and a human being is perfectly >> able to parse "AP , Tarek " without >> the help of a computer. > > Type of `auth

[issue6992] Adding a Contributor field in PEP 314

anatoly techtonik added the comment: > The good pratice, if there are several authors, is to setup a > mailing-list (and put its address as official contact address). True. Some packages already do this. > Otherwise collaboration gets inevitably messy, since authors can get > contacted in priv

[issue6992] Adding a Contributor field in PEP 314

Marc-Andre Lemburg added the comment: Tarek Ziadé wrote: > > Tarek Ziadé added the comment: > >> In order to clear up the inconsistency with maintainer >> not being a possible meta-data field, I think "Maintainer" >> should be added to the meta-data. Dito for "Maintainer-EMail". > > Do you

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: > In order to clear up the inconsistency with maintainer > not being a possible meta-data field, I think "Maintainer" > should be added to the meta-data. Dito for "Maintainer-EMail". Do you remember what's the story behind those two fields ? I am not sure about

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: > A metadata system, by definition, has to remain reasonably stable > (or be version-numbered, such that old metadata can be recognized properly). That's already the case. We have 1.0 and 1.1. 1.1 is used if you add fields like "obsoletes". > You can certainl

[issue6992] Adding a Contributor field in PEP 314

Marc-Andre Lemburg added the comment: Tarek Ziadé wrote: > > Tarek Ziadé added the comment: > >> We already have authors and maintainers (which causes confusion), >> adding yet another field for contributors is overkill, > > Not on the Metadata side though. That's only on setup() side. The

[issue6992] Adding a Contributor field in PEP 314

Antoine Pitrou added the comment: > I am bothered that more and more are people constantly jumping on my > back everytime I try to make Distutils evolves a bit or everytime I > discuss some feature proposals with the community. This is not "jumping on your back", this is being skeptical about a

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: > We already have authors and maintainers (which causes confusion), > adding yet another field for contributors is overkill, Not on the Metadata side though. That's only on setup() side. The resulting metadata only contains "Author" and "Author-email", and it's c

[issue6992] Adding a Contributor field in PEP 314

Marc-Andre Lemburg added the comment: Most of the meta data is parsed by humans, so I don't see any complication with adding multiple authors to the author field using standard email format: "Anatoli , Tarek ". We already have authors and maintainers (which causes confusion), so adding yet anot

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: > What does changing the type of the "author" field make clearer exactly? It "Author" not "Authors", that's the difference. Like we have "Classifiers" and not "Classifier". Plus, I am not breaking any compatibility here. A multi-value field in the metadata in D

[issue6992] Adding a Contributor field in PEP 314

Antoine Pitrou added the comment: > Replacing the author/author_email/maintainer/maintainer_email mess with > a single authors argument, that fills a multi-valued "Author" metadata > field make it clearer. What does changing the type of the "author" field make clearer exactly? It is a field for

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: The metadata are completely messy. Users are already confused. For instance, since the metadata fields are not fully corresponding to the argument names you can pass into setup.py, you can have an "author" and a "maintainer" argument and Distutils will put only th

[issue6992] Adding a Contributor field in PEP 314

Antoine Pitrou added the comment: > What about having a "Contact-email" then that would replace the > "Author-email" field, and an "Author" multi-valued field as described > previously. Why do we have to add new fields and deprecate others? Just for the sake of confusing users and breaking exis

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: What you are saying is that a project should have one and only one contact email. What Anatoly says is that a project should be able to have several authors. What about having a "Contact-email" then that would replace the "Author-email" field, and an "Author" mult

[issue6992] Adding a Contributor field in PEP 314

Antoine Pitrou added the comment: The good pratice, if there are several authors, is to setup a mailing-list (and put its address as official contact address). Otherwise collaboration gets inevitably messy, since authors can get contacted in private randomly. I don't think we should multiply th

[issue6992] Adding a Contributor field in PEP 314

anatoly techtonik added the comment: Having single `authors` field is enough, indeed. -- ___ Python tracker ___ ___ Python-bugs-list m

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: Notice that there's another issue: maintainer is not written in the Metadata if author is provided. Plus, PyPI has its own role system: owner+maintainer, that has nothing to do with the package Metadata (it's just who registered the package and who was granted so

[issue6992] Adding a Contributor field in PEP 314

anatoly techtonik added the comment: Too complicated. I think any who significantly contributed to some package is an author. Maintainer is the one who does the goodness of making this package available to other systems through PyPi. {{{ authors = [ 'Anatoli ', 'Tarek ' ] }}} part is op

[issue6992] Adding a Contributor field in PEP 314

Tarek Ziadé added the comment: Right, it's not handy for the emails. PyPI will display the author field, followed by the author_email field. So everyone will be displayed but not properly. But no tool is handling the Author and Author-email fields as multi-value fields. Maybe we could extend