-
Notifications
You must be signed in to change notification settings - Fork 46
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
Move to phpmnd namespace #23
Comments
To chime in, I just migrated Mockery and Humbug over to organisations. The upside is that it's very simple. Just name the organisation after phpmnd, add a single "team" with commit access that you can add members to (you would retain full administrative control - it's your baby afterall), update Packagist URI, and a few other odds and ends. A few minutes and the project is parcelled into a tidy package for any future needs. In time you can find a dependable person or two to add to the organisation to help with issues/PRs, and cover you should you need to be absent for a while. This is coming from someone who went absent for nearly TWO YEARS and left a project in limbo 😬 by not being prepared for that eventuality. The downside...well, basically it's more difficult if you wait too long, or leave the project without at least one nominated lieutenant to mind the shop in your absence. |
Hehe...I just realised that I am not a "dependable person" in this scenario 😀. I take some pretty long vacations! |
Implements povils#23
If you plan to support & maintain this project over many years, it could be beneficial to move this tool away from your personal namespace/GitHub user to a phpmnd specific namespace/GitHub organisation.
This could also lower the barriers for others to co-maintain it (if that's an option anyway).
The text was updated successfully, but these errors were encountered: