Taking a back seat

[willmcgugan]

This is intended for maintainers, but anyone can chip in if they like.

You might have noticed I've not been that active on PyFilesystem for a while, issues and PRs have been piling up. Work / life commitments and Rich have left me with little context switching capacity.

I was hoping that PyFilesystem would reach a level of maturity that it wouldn't need much work going forwards, but filesystems are such a delightful source of edge cases I guess the work will be ongoing. So I think I should let go of the reigns and let other maintainers take over, i.e. full commit rights. I should probably have done this sooner, but its hard to let go!

Alternatively, it would be awesome if we could get sponsorship. Paid work would certainly make it easier to justify time spent.

Thoughts?

[willmcgugan]

@lurch @althonos @zopyx

[althonos]

Hi @willmcgugan,

Pyfilesystem2 has been the first open-source project I really contributed to and I feel this was because you used some of your time to mentor me; now that I have a bunch of libraries that have a real user base, I can see how time-consuming it is to guide people instead of fixing everything yourself. So for this, thank you!

I can use a bit of my energy now to help with the maintenance, starting with the PRs and the recent issues.

[willmcgugan]

Thanks @althonos ! I think the mentoring has been bidirectional. :)

I've given all the org members write privileges. Feel free to commit away.

I'm not going to disappear entirely. Mention me if I can contribute.

[althonos]

I created the @PyFilesystem/maintainers team to discuss some more beyond issues. I added you @lurch because I saw you still commenting around here, but feel free to drop out if don't want to be there. I'd be happy to get some feedback, like about triage, goal for an EOL release before the end of the year with as much bugfixes as possible before Python 2 is formally dropped, and so on.

[zopyx]

Sorry for answering late. I clearly have a personal interest in using PyFilesystem2 for the future and can perhaps commit some resources here and there. Unfortunately I am pretty much swamped with a lot of high-profile projects at the moments.

[althonos]

Hi @willmcgugan , I wanted to setup GitHub Actions to automatically publish tagged releases to PyPI, but I don't have access to the PyFilesystem2 settings page, meaning I can't add the PyPI token to the Actions secrets. Could you either:

• Give me access to the project settings
• Add a secret named PYPI_API_TOKEN to the PyPI environment in GitHub, with a PyPI API token allowing uploads for the fs package?

Cheers !

[willmcgugan]

@althonos I have added you as a maintainer, which I think should give you access. Let me know if that worked!

[althonos]

@willmcgugan : I can see the Settings page, but only a limited part of it, so I still can't add Actions secrets :cry:

[willmcgugan]

Heck, I'll give you admin!

[althonos]

Thanks ! I'll refrain from breaking everything ahah :wink:

[althonos]

Everything worked, and we have a new release v2.4.13 published straight from the CI. Thanks again :smiley: