
Thanks for initiating this Nick! I agree that it would be great to get ChangeSet to help with this. *Nicole Harris* Kabu Creative *Mobile:* + 44 (0) 7480 910 191 *E-mail:* n.harris@kabucreative.com http://kabucreative.com On 23 May 2018 at 14:00, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 23 May 2018 at 00:13, Dustin Ingram <di@python.org> wrote:
With regards to:
- How do we clearly communicate upcoming changes and enhancements to tools in the Python packaging ecosystem? (the external communications question)
I think this could probably be expanded to include any type of external communication with the community (although I agree that communicating deltas is probably the highest-value type of external communication).
Specifically, I think it would be worthwhile to have some set of standards or guidelines for how PyPA "members" engage the community, whether it be on issue trackers, on Twitter, IRC, mailinglists, etc.
In my opinion, one of the successes of the PyPI/MOSS work was that we spent significant effort attempting to include the community in the project, respond to issues/bug reports/feature requests with respect, and making the project a welcoming place for new contributors.
I don't think that this should (or could) be enforceable but I do think setting a consistent tone for communication across all PyPA projects would go a long way.
I'd see anything along those lines as part of the initial answer to "What are our expectations for maintainers and lead maintainers on PyPA projects in terms of reachability and responsibility for the overall UX of Python packaging tools?", as I'd suggest using a fairly broad definition of "overall UX" for that question.
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
_______________________________________________ PyPA-Committers mailing list pypa-committers@python.org https://mail.python.org/mm3/mailman3/lists/pypa-committers.python.org/