Andrey9kin
commented
8 years ago - Access rights: How about praqma-all as admins?
- master branch protection? Prevent force push and direct pushes without pre-integration?
- Pipeline: I would recommend using Travis CI unless we need to build a very complex pipeline. Moreover, Travis CI is maintenance free and more accessible for contributors coming from outside of Praqma, i.e. in case of Jenkins people from outside need to know slaves setup, credentials details and so on which is very unpractical. Don't forget that our Jenkins instance is in a very bad shape
- I would argue about Praqmatic workflow. Labeling is good, but I would avoid pushing changes without discussion. This approach works just fine within a team that has possibility to discuss things up front, have planning and pair programming. When we dealing with outside contributors then we don't really have that option. So one way is to use pull requests verified by Travis CI or Jenkins and then maintainer will bring them in when the time is right.
- Readme should contain contribution instructions including planning process, how to build and test, how to submit new change
- Releases to jitpack (at least for Java code, technically it is possible to setup Gradle to build anything as zip files and publish it to JitPack)
sofusalbertsen