_______________________________________________I agree with Paul here. I'm happy to +1 whatever, but unless there's an actual conflict and the project maintainers are asking the wider PyPA to step in and mediate, this seems like it should be up to the individual projects' governance.
On 8/30/22 16:44, Paul Moore wrote:
+1.
But do we really need a vote for this? I'd have considered funding decisions like this to be the project's responsibility and as per the PyPA governance PEP, "As long as the project is adhering to the Code of Conduct and following specifications supported by the PyPA, the PyPA should only be concerned with large, ecosystem-wide changes".
I'd honestly rather we didn't start expecting projects to need a vote for things like this.Paul
On Tue, 30 Aug 2022 at 21:41, Ofek Lev <ofekmeister@gmail.com> wrote:
+1
_______________________________________________On Tue, Aug 30, 2022 at 4:35 PM Trishank Kuppusamy via PyPA-Committers <pypa-committers@python.org> wrote:
+1
_______________________________________________On Tue, 30 Aug 2022 at 16:33, Dustin Ingram <di@python.org> wrote:
Seconded / +1
_______________________________________________On Tue, Aug 30, 2022, 4:24 PM Oz Tiram <oz.tiram@gmail.com> wrote:
Dear Pypa Committers,
I am writing to you to ask for your vote on the following resolution:
Please approve remitting pipenv Tidelift revenue net of Python Software Foundation's administrative fee to the pipenv page maintainer, Frost Ming from March 2021 to December 2021 and 50/50 to Oz Tiram and Matt Davis from January 2022 on until such time as the maintainer(s) changes. The PyPA will share the voting results of this resolution with Python Software Foundation.
In case you have not noticed, after a long hiatus where pipenv wasn't maintained at all or solely maintained,
the project is now live and active. We (GitHub handles @oz123, @matteius) have been fixing bugs, removing old code, answering questions and released multiple versions of pipenv
in the last year.
Although there are other tools that help Python users to manage their virtualenvs, pipenv remains used by many members of the community. We know this since there are many new contributors
and bug reports in the period since we adopted this project from @frostming.
On behalf of Matt Davis and me,
Best regards
Oz Tiram
_______________________________________________
PyPA-Committers mailing list -- pypa-committers@python.org
To unsubscribe send an email to pypa-committers-leave@python.org
https://mail.python.org/mailman3/lists/pypa-committers.python.org/
Member address: di@python.org
PyPA-Committers mailing list -- pypa-committers@python.org
To unsubscribe send an email to pypa-committers-leave@python.org
https://mail.python.org/mailman3/lists/pypa-committers.python.org/
Member address: trishank.kuppusamy@datadoghq.com
PyPA-Committers mailing list -- pypa-committers@python.org
To unsubscribe send an email to pypa-committers-leave@python.org
https://mail.python.org/mailman3/lists/pypa-committers.python.org/
Member address: ofekmeister@gmail.com
PyPA-Committers mailing list -- pypa-committers@python.org
To unsubscribe send an email to pypa-committers-leave@python.org
https://mail.python.org/mailman3/lists/pypa-committers.python.org/
Member address: p.f.moore@gmail.com
_______________________________________________ PyPA-Committers mailing list -- pypa-committers@python.org To unsubscribe send an email to pypa-committers-leave@python.org https://mail.python.org/mailman3/lists/pypa-committers.python.org/ Member address: python@ml.ganssle.io
PyPA-Committers mailing list -- pypa-committers@python.org
To unsubscribe send an email to pypa-committers-leave@python.org
https://mail.python.org/mailman3/lists/pypa-committers.python.org/
Member address: oz.tiram@gmail.com