VOTE: pipenv Tidelift revenue assignment
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
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
+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
+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
+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
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 topypa-committers-leave@python.org https://mail.python.org/mailman3/lists/pypa-committers.python.org/ Member address:python@ml.ganssle.io
+1 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".
That was my initial impression too, but then Dustin, on behalf of the PSF, said it's better to confirm with PyPA members via a vote to avoid any controversy. The PSF currently laid claim to all PyPA projects income on Tidelift, mostly so they do not go to waste. They are happy to relinquish this to the actual maintainers, but as the PSF represent here the org they judged is best to get approval from the organization representatives, rather than the individual project maintainer. On Tue, Aug 30, 2022 at 1:50 PM Paul Ganssle <python@ml.ganssle.io> wrote:
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.orghttps://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: gaborjbernat@gmail.com
There isn't any conflict between me or Matt. Just to clarify, we were asked by the PSD to raise this vote in order to follow the transparency requirements of PEP609. Thank you for your votes so far. Oz On Tue, Aug 30, 2022 at 10:50 PM Paul Ganssle <python@ml.ganssle.io> wrote:
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.orghttps://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
OK. I'm really not interested in being asked to vote on every funding decision, but it's only a quick email, so it's not the end of the world. Paul On Tue, 30 Aug 2022 at 21:58, Bernat Gabor <gaborjbernat@gmail.com> wrote:
+1
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".
That was my initial impression too, but then Dustin, on behalf of the PSF, said it's better to confirm with PyPA members via a vote to avoid any controversy. The PSF currently laid claim to all PyPA projects income on Tidelift, mostly so they do not go to waste. They are happy to relinquish this to the actual maintainers, but as the PSF represent here the org they judged is best to get approval from the organization representatives, rather than the individual project maintainer.
On Tue, Aug 30, 2022 at 1:50 PM Paul Ganssle <python@ml.ganssle.io> wrote:
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.orghttps://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: gaborjbernat@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
Thanks for putting this together Oz and for everyone that has voted! I'll second what Oz has said and add that we were surprised to learn about possible tidelift funding and are simply following the process put forth to us. We are excited about improving the quality of pipenv and our momentum and collaboration week over week on bug fixes and improvements has been positive and impactful. We are also very thankful to the prior maintainer Frost Ming for all of his past accomplishments, and for getting us more involved in the project to the point of taking over maintenance. Thanks to everyone who makes pip as well, because without pip there would be no pipenv. Cheers, Matt Davis On Tue, Aug 30, 2022 at 4:58 PM Oz Tiram <oz.tiram@gmail.com> wrote:
There isn't any conflict between me or Matt. Just to clarify, we were asked by the PSD to raise this vote in order to follow the transparency requirements of PEP609.
Thank you for your votes so far.
Oz
On Tue, Aug 30, 2022 at 10:50 PM Paul Ganssle <python@ml.ganssle.io> wrote:
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.orghttps://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
_______________________________________________ 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: matteius@gmail.com
Sorry, I should have provided more context: These votes are for funding requests from the PyPA general fund (which the PSF holds for us). While these particular funds were 'earmarked' for specific projects from pre-emptively squatting Tidelift, they're still coming from a shared pool (which is the same place GitHub sponsorship of PyPA goes, etc) and so to ensure we have absolute transparency about where general funds are going and who's getting paid, I asked Bernat and Matt/Oz to raise this for a vote here. Now that we have a general fund, I'd expect us to vote on any funding proposal from the general fund, but any individual project spending funding from elsewhere would obviously not require a vote. We probably should update PEP 609 to specifically mention this, I'll start a separate thread about it. On Tue, Aug 30, 2022 at 5:56 PM Matt Davis <matteius@gmail.com> wrote:
Thanks for putting this together Oz and for everyone that has voted! I'll second what Oz has said and add that we were surprised to learn about possible tidelift funding and are simply following the process put forth to us. We are excited about improving the quality of pipenv and our momentum and collaboration week over week on bug fixes and improvements has been positive and impactful. We are also very thankful to the prior maintainer Frost Ming for all of his past accomplishments, and for getting us more involved in the project to the point of taking over maintenance. Thanks to everyone who makes pip as well, because without pip there would be no pipenv.
Cheers, Matt Davis
On Tue, Aug 30, 2022 at 4:58 PM Oz Tiram <oz.tiram@gmail.com> wrote:
There isn't any conflict between me or Matt. Just to clarify, we were asked by the PSD to raise this vote in order to follow the transparency requirements of PEP609.
Thank you for your votes so far.
Oz
On Tue, Aug 30, 2022 at 10:50 PM Paul Ganssle <python@ml.ganssle.io> wrote:
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.orghttps://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
_______________________________________________ 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: matteius@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: di@python.org
+1
On 30. Aug 2022, at 22:24, 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: jannis.leidel@pyfound.org
+1 ________________________________ From: Jannis Leidel <jannis.leidel@pyfound.org> Sent: Friday, September 2, 2022 11:05 To: Oz Tiram <oz.tiram@gmail.com> Cc: pypa-committers@python.org <pypa-committers@python.org> Subject: [pypa-committers]Re: VOTE: pipenv Tidelift revenue assignment +1
On 30. Aug 2022, at 22:24, 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: jannis.leidel@pyfound.org
This vote has passed. On Fri, Sep 2, 2022 at 11:09 AM Jason R. Coombs <jaraco@jaraco.com> wrote:
+1 ------------------------------ *From:* Jannis Leidel <jannis.leidel@pyfound.org> *Sent:* Friday, September 2, 2022 11:05 *To:* Oz Tiram <oz.tiram@gmail.com> *Cc:* pypa-committers@python.org <pypa-committers@python.org> *Subject:* [pypa-committers]Re: VOTE: pipenv Tidelift revenue assignment
+1
On 30. Aug 2022, at 22:24, 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: jannis.leidel@pyfound.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: di@python.org
participants (10)
-
Bernat Gabor -
Dustin Ingram -
Jannis Leidel -
Jason R. Coombs -
Matt Davis -
Ofek Lev -
Oz Tiram -
Paul Ganssle -
Paul Moore -
Trishank Kuppusamy