Ezio Melotti added the comment: A few comments:
1) In the "Restrictions on scope" section, you could turn "Contributor Licensing Agreement" into a link. 2) You call this a "program" in a couple of place, and I'm not sure that's the right term (to me "program" sounds like an organized effort brought forward by the PSF rather than just a self-compiled list of names). 3) I would have kept the 2 disclosure-related cases separate from the availability for paid work, but I guess practicality beats purity and the paragraph you added to clarifies the difference does a good-enough job. 4) In the "commercial contacts" bullet point, you could clarify what kind of contacts are allowed (e.g. link, email address, phone numbers, company address, etc.). 5) Several devs already have a bio page on the wiki. Instead of repeating it here, it might be easier to just add a link to that. This makes the list shorter and easier to read, and allows people to write as much as they want on their wiki page. 6) If the bio is moved to the wiki, a more concise table-based approach might work better. The table can include columns for names, affiliations, availability for paid work (just a check mark), link to bio, and possibly other links. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25194> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
