sghiassy
commented
7 years ago @sibelius - agreed.
Any volunteers?
Open sibelius opened 7 years ago
sghiassy
commented
7 years ago @sibelius - agreed.
Any volunteers?
sghiassy
commented
7 years ago 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.
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
commented
7 years ago I would be glad to help out.
Answers:
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)Add a real test like jest would be a nice thing to have.
It will ensure that everything works after a commit.
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