Problem: A lot of energy is waisted by people not knowing how to use Github. This suggestion below highlights this.
Possible solution: Create a team.md to add to the "mast repo" for a specific team or product.
For example. iOS team has 5 repositories which could link back to the most used repository or the team's "central" repository, where the contributor would add their github handle and time commitment as a pull request to that team.
it would be good to switch the engineering volunteer form from a google survey thing that it is now, to raising a pull request against a repository to apply, I think this would mean at least people in the funnel had a basic understanding of how git works (which many don't).
What do you think about this? I don't want to create a high barrier to entry, but I guess there should be at least some level of skill required.
This was partly why we stopped doing iOS team huddles a while back, we spent the whole hour resolving merge conflicts and teaching git :face_palm:
Problem: A lot of energy is waisted by people not knowing how to use Github. This suggestion below highlights this.
Possible solution: Create a team.md to add to the "mast repo" for a specific team or product.
For example. iOS team has 5 repositories which could link back to the most used repository or the team's "central" repository, where the contributor would add their github handle and time commitment as a pull request to that team.