I have no interesting being the owner or sole maintainer of this project. This is now a proper open source project, and it should have multiple people taking care of it. I'm looking to recruit a few gatekeepers for the project. I don't think we need to be more than 3 total for now, unless the project really starts to grow.
You do not have to be good at developing Wildstar addons, but you should probably know enough git and github to take care of administrative work. By and large, you would be reviewing pull requests and issues. Once we put out a release on Curse, issues and feature requests will start pouring in, both here and on Curse comments, and I'd like to keep things as organized as possible.
You will want to make sure that commits are self contained and properly documented in their commit messages.
You will also handle releases when they happen. This involves making sure everything that we wanted to do for a release is done, tag and document the release, and put it up on Curse.
I was thinking of asking @itsthatguy about using his vikinghug organization, but that's his stuff, and it might not be okay. Alternatively we can create a new organization, probably just call it NewVikings or VikingReborn (ideas welcome), and assign gatekeepers there.
The author field in addons will be set to the organization name. Addons will be distributed with an AUTHORS file listing everyone who has ever helped us. Releases on Curse will be done under an organization-wide login, and all gatekeepers will have access.
I have no interesting being the owner or sole maintainer of this project. This is now a proper open source project, and it should have multiple people taking care of it. I'm looking to recruit a few gatekeepers for the project. I don't think we need to be more than 3 total for now, unless the project really starts to grow.
You do not have to be good at developing Wildstar addons, but you should probably know enough git and github to take care of administrative work. By and large, you would be reviewing pull requests and issues. Once we put out a release on Curse, issues and feature requests will start pouring in, both here and on Curse comments, and I'd like to keep things as organized as possible.
You will want to make sure that commits are self contained and properly documented in their commit messages.
You will also handle releases when they happen. This involves making sure everything that we wanted to do for a release is done, tag and document the release, and put it up on Curse.
I was thinking of asking @itsthatguy about using his vikinghug organization, but that's his stuff, and it might not be okay. Alternatively we can create a new organization, probably just call it NewVikings or VikingReborn (ideas welcome), and assign gatekeepers there.
The author field in addons will be set to the organization name. Addons will be distributed with an AUTHORS file listing everyone who has ever helped us. Releases on Curse will be done under an organization-wide login, and all gatekeepers will have access.