Skip to content
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

Add more maintainers #48

Open
sibelius opened this issue Jan 17, 2017 · 3 comments
Open

Add more maintainers #48

sibelius opened this issue Jan 17, 2017 · 3 comments

Comments

@sibelius
Copy link

The idea of this package is great, but there are still some bugs on it

the development is stopped since last August, would be good to add more maintainers to help review Pull requests and help fix issues

@sghiassy
Copy link
Owner

@sibelius - agreed.

Any volunteers?

@sghiassy
Copy link
Owner

Maintainers needed

When I released this package I wasn't aware it would be helpful for that many people. To my surprise, it has become used more and more. The flipside is that an open-source package requires a lot of work to keep up and running. This is work I'd love to do, but my work schedule in short-term seems overloaded as it is, so I don't think I can be that person(s) for the time being. So with that being said, I'm looking to bring on one or more maintainers to help maintain and improve this package.

Questions I have

  • How should I pick a maintainer? Do I accept anyone with enthusiasm or should there be some review/qualifications? I understand that in larger open source communities you start by fixing bugs and move up the ladder - this is a much smaller piece of software so I'm not sure how that applies here.

  • How do we ensure that the package stays stable over time for all platforms and React Native versions? What tests need to be run on PRs? In my experience unit tests are easy, but UI tests in RN are hard.

  • Should we build a roadmap for this package of where it should go? Or simply keep it maintained?

@st0ffern
Copy link

st0ffern commented Apr 30, 2017

I would be glad to help out.

Answers:

  1. Pick people you know are in the community and theyr repos and what they have to offer.
  2. Add Semantic Release and Commitizen to the repo. Make branches with versions and release them throu like they should with Semantic Release. Look here: https://github.com/semantic-release/semantic-release and here: https://github.com/commitizen/cz-cli (autmated NPM releasing, Release notes, and Changelog)
  3. Dont think Roadmap is the place to start. I find it a little overkill 😉

Add a real test like jest would be a nice thing to have.
It will ensure that everything works after a commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants