On 28 June 2017 at 01:58, Barry Warsaw
On Jun 25, 2017, at 11:33 AM, Nick Coghlan wrote:
I'd favour "Participate" over any variant of "Contribute", as without context, "Contribute" makes me think of financial support in the crowdfunding/tip jar sense.
"Participate" may mean two different things.
* Here's the development home, with a repo and issue tracker, contributions welcome!
* Here's the mailing list or other forum where we discuss the future of Guido's Magical Mystery Time Machine.
It would be nice to be able to capture both meanings.
This isn't feasible to capture generically, since projects have so many different approaches to communication. 1. A lot of modern projects *only* have their repo & issue tracker, with no other dedicated discussion or help forum (with sites like Stack Overflow handling requests for help) 2. Bigger projects will have *multiple* venues for communication, usually including at least one near-real-time channel (e.g. IRC, Slack, Gitter), and one more asynchronous one (e.g. a mailing list or web forum) So the only generic reader-centric (rather than publisher-centric) distinctions we can reliably make are: * "I want to use this project, tell me how" (aka "Documentation") * "I want to participate in the design and development of this project, tell me how" (aka "Participate") * "I want to help fund the design and development of this project, tell me how" (aka "Funding") That doesn't preclude having other more specific links (e.g. the PEP 459 draft also proposes "Home", "Repository" and "Tracker": https://www.python.org/dev/peps/pep-0459/#project-urls), it's just about reserving the "Documentation" tag primarily for user documentation rather than contributor documentation. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia