-
-
Notifications
You must be signed in to change notification settings - Fork 147
-
-
Notifications
You must be signed in to change notification settings - Fork 147
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
Maintainers #33
Comments
Would love to help. Couple thoughts: Recommended workflow for future contributions? I'm assuming should still submit PR's to give you/someone a chance to take a look. I'd be interested in working on some of the issues that have been on the back-burner - do you mind adding more detail on #8, #9 and #10 at some point? |
Thanks @stephen! I'll add you now. Workflow Pretty simple really... never work on master directly, always on a branch, to merge into master open up a pull request and get someone to review or leave it for a little and then review yourself (only if you can't get anyone else). Then merge! Backlog Burning That would be great, I'll try and add a little more description to them soon. |
Cheers @bencevans! |
Although I love to work on the project and will carry on when I have time, I think adding additional maintainers would be great. Also as I'm going to be away from a computer for quite a while I don't want my unavailability to affect pull-request review/merges and other development.
I was wondering if @stephen, @mrose17 and/or others would be up for it?
Cheers,
Ben
The text was updated successfully, but these errors were encountered: