-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Moving to "workshopper" org #254
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For the good of this project and its ecosystem I have to loosen the reigns even more and I think the best way to do that is to move to a new org. I've created "workshopper" as a place for this and its core modules to live (workshopper-*).
I've already invited most of the people who are collaborators of this project into the org as Owners, feel free to accept the invite if you're on board or ignore it if you want to move on.
After a move we should probably talk about organisational structure, ideally it should be minimal but someone needs to cut releases and having me holding those keys is suboptimal. It'd be nice if there was at least one other person with that ability and for that other person to take the primary responsibility for being gatekeeper for releases. Code changes can continue on as they do now, in a collaborative and open way (basically the way that has inspired the io.js governance and collaborator model--seek to minimise disagreement).
I'll leave this for a couple of days for comment here before pushing the button on this.
The text was updated successfully, but these errors were encountered: