Migrating Caster project into an Organization

[synkarius]

This issue is to be used to create a census about Caster joining the Dictation Toolbox organization, another organization, or our own organization. More information regarding Github Organizations.

I would like to hand control of the Caster repository to the community maintainers. I am happy to provide input and code as time allows, but I no longer wish to guide the direction of the project, as I am no longer an active user. I think that the users know their needs best.

Advantages of joining another organization:

1. increased visibility of the project
2. leads to better support and maintenance
3. and also more people reached

Advantages of joining Dictation Toolbox in particular:

• efforts are already underway to increase synergy/ interoperabilitybetween Aenea and Caster
• similar user bases

[LexiconCode]

I can't thank you enough for creating Caster and your support over the years. Caster gave me the inspiration for programming not just the tools. I hope we can continue to be good stewards of your work for all those yet to come to the project.

I would be in favor of joining the Dictation Toolbox. In the event that that does not work out or it is not a good fit we can create our own. Either way I think it's a good way to move forward with Caster and the community.

[kendonB]

@calmofthestorm, @nirvdrum, FYI

[LexiconCode]

I've been in contact with calmofthestorm.

[nirvdrum]

I'm a bit ashamed to say that I had never heard of caster before, but I thank you for thinking of us. I'd be happy to adopt the project under the Dictation Toolbox organization. The use case of programming via dictation is quite niche as it is, so unifying the two communities makes a great deal of sense to me.

[calmofthestorm]

Sorry, I've been traveling. I did email LexiconCode back with quite a tome, however:-)

I'd also support this. Currently in dictation-toolbox, our agreement has been to not use admin privileges on each other's repositories (each retaining full ownership of the project), except in the event of someone disappearing, so we can provide continuity. So I'd want to continue with that (and possibly write it down somewhere on the organization by way of explanation) as well.

It would also be great to bring in the Dragonfly fork as well, for precisely the same reasons.

[LexiconCode]

I sent you a carrier pigeon with my reply. :) The future looks bright!

[calmofthestorm]

FYI, looking to get agreement from the current admins on dictation-toolbox/dictation-toolbox#1. Next step would probably be to ensure whoever on the Caster side is going to be its owners also agree, and then add them as admins to dictation-toolbox, add Caster to the meta README, and migrate it. I also think it would be wise to add an OWNERS file to each repo.

I'm not entirely clear on who has decision making power for Caster, so I'd probably want to see consensus on that point.

Trying to strike a balance of keeping this lightweight while still ensuring all stakeholders have a chance to raise any concerns.

[Versatilus]

I would like to see this move forward.

I'm one of four people with full access to the Caster repository. The others are:

• @synkarius, obviously.
• @LexiconCode, who is the one who continues to drive this project forward.
• @chilimangoes, who currently doesn't have any free time for the project.

We all defer to @synkarius, though he's been quite busy lately. The bulk of the new code comes from @mrob95, @comodoro, @gerrish, and myself (when I'm not being lazy). I try to find a consensus before I merge changes (especially my own), though I've been occasionally guilty of operating with the philosophy that it is easier to ask for forgiveness than it is to ask for permission.

[synkarius]

Welcome to the discussion, @calmofthestorm and @nirvdrum. I am the author of Caster, and so, although @Versatilus and @LexiconCode have been running the project in my absence for two years, as @Versatilus said, they defer to me for major decisions like this. I am fully in favor of @calmofthestorm's plan to move forward, and I think that @Versatilus and @LexiconCode would be excellent choices for owners of the Caster repo within the Dictation Toolbox organization.

[calmofthestorm]

@nirvdrum, can you approve dictation-toolbox/dictation-toolbox#1 when you have a chance (or let me know if you have any concerns)? I think that's the main blocker on my end at this point.

[LexiconCode]

Sounds like a plan. The Caster community is ready to merge when it's convenient.

[calmofthestorm]

Let me give @nirvdrum a few more days to weigh in. Say we'll go ahead on Jan 2?

[LexiconCode]

Sure, that would be a good way to move forward. If you feel the need for more time it shouldn't be an issue.

[calmofthestorm]

That and I'm traveling and internet access is infrequent and unreliable/slow. I'll take a look when I get back.

[calmofthestorm]

Assuming no one objects by Jan 2 let's go ahead. I'll add @Versatilus and @LexiconCode to dictation-toolbox, and we can reach out to Github to move Caster in. I assume the repository owner should initiate that request, but I'm happy to be a point of contact on the organization side.

Any other action items I should have on my radar? Other admins to add, etc?

Sorry for the delay; holiday travel + wanting to avoid bypassing anyone.

[LexiconCode]

Smart move regarding the holidays, I can't think of anything actionable at this time. If anyone in the Caster community has any suggestions feel free to let me or Versatilus know. I will initiate the request when the time comes.

[LexiconCode]

When the time comes @synkarius as the owner of the Caster repository will have to follow the instructions in repository transfers to request a transfer. Once a transfer is requested @calmofthestorm will have 24 hours to accept or the merger will automatically be declined.

[calmofthestorm]

I'll be on top of it, don't worry! Currently we're just blocked on @nirvdrum who asked for a few days to look at it. Thank you very much for your patience.

[calmofthestorm]

Ok, I have invited @LexiconCode and @LexiconCode to be admins of dictation-toolbox, and am ready to accept the transfer once initiated within 24h. I'll be home all week so should be able to reply within the window.

@synkarius I'm happy to add you as well if you like, but I understand if that would be contrary to your intend to hand off the project. Let me know if you'd like an invite.

[synkarius]

@calmofthestorm I tried to initiate the transfer but I got an error:

You don’t have the permission to create repositories on dictation-toolbox.

So I think you will have to make me an admin to do the transfer.

I plan on returning to do more Caster development this year and would not mind staying an admin on the project after the transfer. I do not want to guide Caster's direction any more (as I am no longer an active user), but I will still advise and write code for it.

[synkarius]

Wait a minute... I see Dragonfly is in there already but Danesprite isn't an admin. How did he do it?

[nirvdrum]

Dragonfly ended up being an odd one. I think it was hosted on SourceForge and I approached the original author about moving over to GitHub into our organization. He was on board with that, but some communication issue got in the way and I think he ended up just setting the repo up on GitHub without being in the org. Then he didn't want to break that link, so I forked it into the org. After the fork, he still did active dev in the original location. So, it was all pretty messy. I wouldn't look to our support for Dragonfly as a template of how to do this.

[synkarius]

Hah, got it.

[drmfinlay]

@synkarius @nirvdrum I am an admin actually, @calmofthestorm invited me. It looks like new members are private by default, I have made my membership public now. I transferred my fork of dragonfly to dictation-toolbox yesterday (see dictation-toolbox/dragonfly#48).

Transferring to organisations requires the current owner to have permission to create repositories in the organisation. Transfer requests seem to be only for personal to personal account transfers.

[LexiconCode]

Thanks that clarifies the issue. Synkarius will have to be added to the organization to transfer the Caster repository. I'll defer to @calmofthestorm for managing any additions to the organization.

[calmofthestorm]

Invitation sent!

[synkarius]

... and project transferred. 😀

[LexiconCode]

Thank you everyone for making this a easy process. Since the transfer is complete this issue will be closed. Further discussions on organization structure will be a separate issue most likely take place first on dictation-toolbox at a later date.