infrastructure steps for adding isis as a bridgedb maintainer
I would like to be bridgedb's new maintainer. This was discussed with karsten, weasel, and others in the tpo services working group in the first breakout session of Tuesday morning at the Summer 2013 Tor developer meeting. Weasel also asked Roger about an hour later and, down with hierarchy and all that, but Roger gave the OK. As I stated in the session, I am willing to take responsibility both for the VM running the service as well as the codebase.
I would like it if my commits were reviewed and declared acceptable by some other person who is familiar with the code before merging, even if I am the one to merge it. To facilitate this process, I propose using the git workflow that I have used for my other projects.
For what it's worth, I also sign all [0] my git commits with the signing subkey of 0xA3ADB67A2CDB8B35.
I would like a personal repo on git.tpo, please pretty please. :)
repo users/isis/bridgedb.git
RW+ = isis
R = all
Are there any other things that must be done to become the maintainer? Is that process documented anywhere, and, if not, should I document it so that the next person taking over maintenance of something has it?
[0]: "all" means "most", afaik there isn't an automated way to resign rebased commits with manually amending every commit.