Funding proposal: assistance with communications strategy development
Hi folks, As I mentioned on the email thread where we created this list, I'm planning to submit a funding proposal to the PSF's Packaging WG to help ensure that we continue to build on the improvements in communications, both between ourselves, and with end users, that took place as part of the work on the pypi.org migration. I think much of that improvement can be traced back to ChangeSet Consulting's work on the project management side of the MOSS grant, so I'm planning to submit a proposal for WG to fund up to 100 hours of their time, spread out over a period of around 3 months, where the primary deliverable would be to craft initial answers to the following questions based on consultation with maintainers of PyPA projects and other Python community members: - 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? (the internal collaboration question) - How do we clearly communicate upcoming changes and enhancements to tools in the Python packaging ecosystem? (the external communications question) - How do we handle both of those questions in a way that allows them to be primarily maintained on a volunteer basis, with only occasional assistance from PSF staff? While I have no doubt we could come up with at least somewhat workable answers to those questions on a purely volunteer basis, I think we'll get a much better result if someone that's already familiar with and know to the various PyPA projects can dedicate a decent amount of time to the task, rather than relying solely on the time that folks are able to spare for mailing list discussions of the topic. The purpose of *this* thread is then twofold: 1. Letting folks know that I'm planning to submit this funding proposal 2. Seeking feedback on the questions where we'd like assistance in crafting clearer answers than we have today. I think the three I've suggested would be pretty high impact, but that doesn't mean there aren't other possibilities that would be even more beneficial :) Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
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. D. On Tue, May 22, 2018 at 6:17 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:
Hi folks,
As I mentioned on the email thread where we created this list, I'm planning to submit a funding proposal to the PSF's Packaging WG to help ensure that we continue to build on the improvements in communications, both between ourselves, and with end users, that took place as part of the work on the pypi.org migration.
I think much of that improvement can be traced back to ChangeSet Consulting's work on the project management side of the MOSS grant, so I'm planning to submit a proposal for WG to fund up to 100 hours of their time, spread out over a period of around 3 months, where the primary deliverable would be to craft initial answers to the following questions based on consultation with maintainers of PyPA projects and other Python community members:
- 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? (the internal collaboration question) - How do we clearly communicate upcoming changes and enhancements to tools in the Python packaging ecosystem? (the external communications question) - How do we handle both of those questions in a way that allows them to be primarily maintained on a volunteer basis, with only occasional assistance from PSF staff?
While I have no doubt we could come up with at least somewhat workable answers to those questions on a purely volunteer basis, I think we'll get a much better result if someone that's already familiar with and know to the various PyPA projects can dedicate a decent amount of time to the task, rather than relying solely on the time that folks are able to spare for mailing list discussions of the topic.
The purpose of *this* thread is then twofold:
1. Letting folks know that I'm planning to submit this funding proposal 2. Seeking feedback on the questions where we'd like assistance in crafting clearer answers than we have today. I think the three I've suggested would be pretty high impact, but that doesn't mean there aren't other possibilities that would be even more beneficial :)
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/
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
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/
This seems like a good set of questions to start with. It also seemed like in general we were unsure of where to allocate monetary resources if and when we get them. Tracking that might also be helpful / some form of sustainability. Dan Ryan // pipenv maintainer gh: @techalchemy
On May 22, 2018, at 8:17 AM, Nick Coghlan <ncoghlan@gmail.com> wrote:
Hi folks,
As I mentioned on the email thread where we created this list, I'm planning to submit a funding proposal to the PSF's Packaging WG to help ensure that we continue to build on the improvements in communications, both between ourselves, and with end users, that took place as part of the work on the pypi.org migration.
I think much of that improvement can be traced back to ChangeSet Consulting's work on the project management side of the MOSS grant, so I'm planning to submit a proposal for WG to fund up to 100 hours of their time, spread out over a period of around 3 months, where the primary deliverable would be to craft initial answers to the following questions based on consultation with maintainers of PyPA projects and other Python community members:
- 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? (the internal collaboration question) - How do we clearly communicate upcoming changes and enhancements to tools in the Python packaging ecosystem? (the external communications question) - How do we handle both of those questions in a way that allows them to be primarily maintained on a volunteer basis, with only occasional assistance from PSF staff?
While I have no doubt we could come up with at least somewhat workable answers to those questions on a purely volunteer basis, I think we'll get a much better result if someone that's already familiar with and know to the various PyPA projects can dedicate a decent amount of time to the task, rather than relying solely on the time that folks are able to spare for mailing list discussions of the topic.
The purpose of *this* thread is then twofold:
1. Letting folks know that I'm planning to submit this funding proposal 2. Seeking feedback on the questions where we'd like assistance in crafting clearer answers than we have today. I think the three I've suggested would be pretty high impact, but that doesn't mean there aren't other possibilities that would be even more beneficial :)
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/
participants (4)
-
Dan Ryan -
Dustin Ingram -
Nick Coghlan -
Nicole Harris