I agree.

I’d be perfectly happy with PyPA as a lifter of last resort as long as there’s a lightweight process for the active maintainer(s) of any given project to readily claim their stake.

Sent from my comm

On Mar 23, 2021, at 15:08, Dustin Ingram <di@python.org> wrote:

> My preference would be for these projects to enroll individually, and for those maintainers that wish to direct the project’s compensation to the PSF or another entity should do so, and those that wish to distribute the compensation to contributors or co-maintainers should do so. For example, in the CherryPy projects, I share compensation with a co-maintainer and on Setuptools, I’ve offered equal shares to those aiding substantially with the maintenance.

The issue is that with the exception of setuptools (more than $800/mo) we haven't done this already and currently have a total of nearly $1,000/mo that we're just leaving on the table, which we could be using to pay for infrastructure / have bug bounties / hire contractors / pay maintainers at the PyPA's discretion.

I'm personally fine with you continuing to accept all the Tidelift funding on behalf of the setuptools project, as long as the other maintainers are in agreement and we have a plan to disperse that funding in the event of another more active maintainer joining or you deciding to wind down down your maintainership. I think that's one of the advantages of the PyPA accepting funding for the projects under its umbrella instead, though.

On Sat, Mar 20, 2021 at 11:40 AM Ian Stapleton Cordasco <graffatcolmingov@gmail.com> wrote:
So long as I don't take any funding, my company's legal team is fine with me continuing to work on Twine.

Sent from my phone with my typo-happy thumbs. Please excuse my brevity

On Thu, Mar 18, 2021, 06:59 Ian Stapleton Cordasco <graffatcolmingov@gmail.com> wrote:
To be clear, I don't see myself as critical to Twine. If I were, that would be a huge issue.

Brian does an excellent job and Jason is available to help a lot of the time. Regardless, I have meeting with senior legal counsel for my employer Friday. So I'll know more then.

All of this is to say, go ahead. I'll know more about whether I'm still a maintainer this weekend.

Sent from my phone with my typo-happy thumbs. Please excuse my brevity

On Wed, Mar 17, 2021, 14:56 Dustin Ingram <di@python.org> wrote:
I don't think this is much different than the PSF accepting funding
from organizations like CZI on behalf of projects like pip, but I
would definitely recommend checking with your employer. We can just
exclude twine from this for now, I'd hate to potentially lose you as a

On Wed, Mar 17, 2021 at 2:52 PM Ian Stapleton Cordasco
<graffatcolmingov@gmail.com> wrote:
> That's what I thought but our legal team is somewhat ... aggressively against any appearance of outside business activity
> Sent from my phone with my typo-happy thumbs. Please excuse my brevity
> On Wed, Mar 17, 2021, 14:49 Dustin Ingram <di@python.org> wrote:
>> Correct, all funds would go to the PSF, earmarked for the PyPA to
>> distribute as it sees necessary. You would not be required to receive
>> funding as a lifter.
>> On Wed, Mar 17, 2021 at 2:41 PM Bernat Gabor <gaborjbernat@gmail.com> wrote:
>> >
>> > I'm in the same position, but I had the impression that in this case
>> > you'll not receive any compensation. Instead the Tidelift value gets
>> > donated to PSF. So the way I see you're not getting any compensation
>> > if you sign up for it. I might be missing here something though,
>> >
>> > Bernat
>> >
>> > > I need to check with my employer but it's likely this will cause me to have to resign from twine as a maintainer. My contract disallows me from receiving any compensation for F/OSS work and this will likely look an awful like that to the folks in legal. Sent from my phone with my typo-happy thumbs. Please excuse my brevity
PyPA-Committers mailing list -- pypa-committers@python.org
To unsubscribe send an email to pypa-committers-leave@python.org
Member address: jaraco@jaraco.com