On 9/9/25 12:44 PM, G. Branden Robinson wrote:
Questions are what qualifies a person to become the group member and
what level of the responsibilities is expected from the group members.
I can't answer this for Chet/bash, but for groff, commit privileges
attach to this status
I believe this is what "write access to the group's repositories" means.
For example, if I become a member, am I expected to be available for
responding or fixing reported issues?
For groff, the answer is "yes", within one's domain of expertise.
I think this is a common perspective across a range of projects, but it's
a project-specific decision.
I welcome bug fixes, but I've never made it someone else's obligation, so
by that standard, having no other members makes sense.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU [email protected] http://tiswww.cwru.edu/~chet/
