-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider GitHub repo migration plan from 4pr0n/ripme to ripmeapp/ripme #559
Comments
This sounds like a great idea |
In other words, he gave you the lead of RipMe under the conditions of "You can keep the software alive as you see fit, but you don't own it in any sense" despite having made a completely Open Source "do as you wish" software he abandoned. |
@rautamiekka That's a bit strong, and not really fair. @4pr0n is not actively preventing me from doing anything. Even if he gave me admin on this repo (under his user account) I wouldn't feel right granting admin to other users without his direct consent. Using an organization to group admins seems like a better approach anyway. Here I'm just talking about a plan to migrate from the user's repo and move the whole effort to the organization instead. |
After migrating all of the open issues, we need to update the entry on up-for-grabs to point to ripmeapp/ripme (See #556) |
@cyian-1756 @rautamiekka (and anyone else who might be interested in write privileges on our new home): can you message me directly on Gitter? https://gitter.im/metaprime |
Right now I'm a maintainer added as a collaborator by @4pr0n but I don't have admin to expand the maintainer team.
I've already created a mirror of this repo in the organization ripmeapp: https://github.com/ripmeapp/ripme/
We're already (theoretically) using a repo in that org to take PRs to the Wiki: https://github.com/ripmeapp/ripme-wiki
We should consider how to migrate from here to there.
After moving there, I'll be able to add more maintainers, potentially admins to the organization, and grow the crew maintaining this project, which will help with issue responsiveness, merging PRs, and so on, and free (yours truly) up to do some real dev work instead of strictly issue triage, maintenance, and PR merging.
The text was updated successfully, but these errors were encountered: