[Other]: <Succession plan>

[Lxstr]

What would you like to share?

I think it would be great to have a succession plan for this repo. It is awesome and I would be sad to see it unmaintained one day for what ever reasons. We have also had this happen to https://github.com/fengsp/flask-session/issues/156

What are the options?

I believe github only has processes for deceased owner rather than missing owner and it's quite excessive and macabre: https://docs.github.com/en/site-policy/other-site-policies/github-deceased-user-policy

For having multiple owners it seems to need to be within an organisation: https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/maintaining-ownership-continuity-for-your-organization

Are there orgs this could be a part of or make one? eg. flask-pallets-eco mentioned in flask-session

Additional information

No response

[Lxstr]

So now we seem to now have successor feature: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-access-to-your-personal-repositories/maintaining-ownership-continuity-of-your-personal-accounts-repositories

As far as I can tell, successors only can:

• Archive your public repositories.
• Transfer your public repositories to their own user owned account.
• Transfer your public repositories to an organization where they can create repositories.

Unless there is a passing away in which case they can apply for direct ownership.

Perhaps, just nominating a trusted successor and indicating who they are somewhere in the repo would be enough. Would also be cool to one day have repo badges something like: 'successor nominated' and 'actively maintained'

[AsifArmanRahman]

I'll look into it. Thanks for all the suggestions.

[AsifArmanRahman]

FirebaseExtended This community seems fine to me to transfer the repo in future. Any comments? @Lxstr

[garyo]

Hi; I found this repo while looking for a way to access Firebase in python (client-side). This lib looks like it is most recently updated compared to others I've seen:

• https://bitbucket.org/joetilsed/firebase/src/master/
• https://github.com/mikexstudios/python-firebase (very old)
• https://github.com/thisbejim/Pyrebase (has most stars and activity but nothing on main branch since 2020 and many unmerged PRs/issues)

and this lib has auth and storage as well as db, which are what I need most.

These all seem somewhat related but I'm not sure which one to use or if there are any continued plans to maintain them. It looks like this lib is a fork of Pyrebase perhaps? (I see a note from @AsifArmanRahman about this at https://github.com/thisbejim/Pyrebase/pull/417)

Anyway I think if this is the best Python interface to Firebase, it would be great to transfer it to an org where it can be maintained.

[AsifArmanRahman]

Hello @garyo

this lib has auth and storage as well as db, which are what I need most.

It supports firestore as well.

This lib looks like it is most recently updated

It supports up to Python 3.11 till now (haven't tested Python 3.12 yet), while others are limited python 3.9 afaik.

I'm not sure which one to use or if there are any continued plans to maintain them. It looks like this lib is a fork of Pyrebase perhaps?

I'm planning to maintain this library for a while, after that once I'm unable to, I'll transfer this to the org I've mentioned previously in this issue. It actually uses the source code of multiple repositories, not only Pyrebase, but they contained a big percentage of common part as well.

Repos were mentioned here https://github.com/AsifArmanRahman/firebase-rest-api/commit/bcfad1e1b5563e759f865174f10f73dcf2fde8d5

Lastly thank you for your suggestion. Please feel free to nominate any other Orgs you find good and related to firebase in this issue.

[garyo]

Thank you for doing this! You are filling a big hole in the firebase ecosystem. I see the commit you mention now, where you pulled in code from each of those other projects. I will try it out today!

[Lxstr]

Hi Asif

So I think the firebase-extended seems like a logical place to go once you're not maintaining anymore. Haven't discovered much about it but there is a lot of repos on there. Will be interesting to read through it some more.

For alternatives that seem a bit more hands on there is also CodeShelter https://www.codeshelter.co/faq/ and https://jazzband.co/about/faq. I'll read more on both.

I think in the meantime the main thing (from my outsider perspective) would be just knowing that you nominated a trusted successor in your settings/account and who that is so we can go to them to if needed. What are your thoughts on that? Is there someone appropriate? It could be someone you know personally or someone in the firebase-extended/codeshelter/jazzband community perhaps.

Cheers