Transferring J-Pilot from a personal to an organizational GitHub repository

[unforgettableid]

Hi Judd!

I wonder if it might be worthwhile for you to transfer J-Pilot from a personal repository to an organizational repository. If you do so, then when you're no longer around, I can possibly add new committers who can keep the project going. (Right now, I can't add to the list of approved J-Pilot committers, since this is your personal repository.)

Depending on the outcome of desrod/pilot-link#5, perhaps the same organizational repository can hold pilot-link, too. But then again, perhaps @desrod wants pilot-link to be stored separately from J-Pilot; this is because he might be more cautious about granting permissions to others.

Judd, thank you for reading this! I'd be curious to hear your thoughts.

[unforgettableid]

Possibly related: #47.

[juddmon]

I'm thinking about this. Where are the docs on creating/having a backup maintainer?

[unforgettableid]

You already have a backup maintainer who can commit changes. The problem is that, if you're not present and a backup maintainer takes over, there's no way for the backup maintainer to add additional maintainers. The group may eventually end up having to fork the project, which is an unnecessary hassle.

You might want to transfer J-Pilot from a personal repository to an organizational repository.[1] If you do so, then you can designate backup maintainers who in turn can add additional maintainers.

^ [1]. https://docs.github.com/en/repositories/creating-and-managing-repositories/transferring-a-repository

[unforgettableid]

It's been a few years, and there's been no movement on this. Have you had any thoughts in the meantime?

Thanks and have a good one!