-
Notifications
You must be signed in to change notification settings - Fork 39
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 #32
Comments
Hi @grantcarthew, sorry for the delay in getting back, things are crazy at work and I went M.I.A for a very long time. I just saw all the work you did and I'm really glad somebody is taking care of keeping this up to date. My original plan was indeed to get things started and involve other people in the project, I'd like to get back onboard at some point, but I don't see that happening at the moment. Therefore, I'm really in favour of adding maintainers, that was my idea when transitioning to an organisation! People in #29 are more than welcome, so is everybody who wants to contribute, IMHO... |
OK @hal0gen I have invited @peerbolte and will invite anyone else who shows interest more than just opening an issue. This doesn't mean @peerbolte and others will have the time to help, however inviting people gives them a sense of ownership. |
Hey guys, thanks for the invite. I don't have too much time myself, but I'm willing to spend some evening hours on the repo. Do you have a slack channel or something where we can chat? |
Oh, my mistake. The current trendy comms everything tool is Keybase. |
Hey @hal0gen,
I just saw the latest reply in #29 and was thinking about how this project would be a great with many more maintainers. Specifically I am talking about the template, not your plans for components.
If someone shows interest I would suggest adding them in as a maintainer.
For example the guys giving feedback to #29 could be added as maintainers if they are happy to.
Keep in mind that this project is just a template and does not have the same change control restrictions that a dependency package would need.
The text was updated successfully, but these errors were encountered: