Hi Gerard,
I've had a few PRs open on SC lessons for around 2 weeks. Two of them
have not received any response at all. One of them had a brief
conversation, ending with me asking for clarification as to what edits
would be required to have the PR merged.
This is sad. I know from some notifications on my inbox that you are
contributing a lot with the lessons.
Now I know the maintainers are volunteers (I am also a lesson
maintainer), and have other priorities, but it's frustrating to go to
the bother of submitting a PR only to get nothing of use back.
So I'm asking two things:
* Should Software Carpentry have a response time, where a maintainer
should assign the PR within 2 days, or at least comment to indicate
their expected response time? This is the approach I have been taking,
but I must concede that I get far fewer PRs on the lesson I maintain.
* What can PR submitters do in my situation?
I wish that GitHub (or GitLab or ...) had a "Trust system", this is how
Discourse [1] named one of their feature that they describe as
As members become trusted regulars over time, they earn abilities to
help maintain their community.
Have something automatically like this would be a great feature for any
project like Software Carpentry who is writing lessons collaborative.
For example, after 5 pull requests merged the system could allow that
user to merge pull requests that change 1% (or one line) of the files it
touch (the case of typos) and after 10 pull requests merged the system
could offer the user the possibility to request a maintainer seat.
I don't remember our rules to give write access to a repository to a
contributor but I think that Gerard demonstrated enough skills to have
write access to the repository that he is contributing.
Raniere
[1]: https://www.discourse.org/
_______________________________________________
Discuss mailing list
[email protected]
http://lists.software-carpentry.org/listinfo/discuss
