Bitrise steps community

[viktorbenei]

@eliot_pear

I do like the idea of having a Github organization for community-maintained steps.

I agree, I’m just not sure about a couple of details - but we’re discussing it internally as well as sharing our notes here

@eliot_pear

forking abandoned or poorly maintained steps into the community organization

That’s an excellent point, I’d be motivated to create a github organization just for this single reason actually!

@eliot_pear

We should be careful to have a way to establish trust in a group of maintainers here: those in good standing in the community with a track record of maintaining their own steps with high code quality and being responsive to PRs.

That’s exactly one of our main concern and discussion topic internally, how we could protect these steps to be deleted or “destroyed” completely by someone who has access to the GH organization, e.g. by force git push-ing into every step. We trust our community, but life experience is that even the most humble/brilliant people can sometimes get angry/exhaused and/or do irrational things. We have to be sure to minimize the chance of letting someone destroy other people’s work.

@eliot_pear

I think you can even set up different github ACLs so that some members could do advisory PR reviews but only some people would have permission to merge to master.

I’ll have to check this, or if anyone has any experience with a GitHub permission setup like this, please let us know!

@eliot_pear

Code review is a great way to foster quality and build consensus on best practices.

Awesome point again, I’d definitely be happy to do code review for others’ steps or ask for a review from someone else!

@eliot_pear

I’d consider volunteering as a member of a community maintenance group.

You’ll be the first one if/when we create a GH organization