The NLP4Gov framework defines 20 role categories for open source project governance: 'all_project' (rules for all contributors), 'contributors' (rules for code contributors), 'maintainers' (rules for project maintainers), 'all_community' (rules for all stakeholders), 'core_team' (rules for the closed group of core contributors), 'technical_committee' (rules for technical committee operations), 'subcommittee' (rules for committee subcommittees), 'the_project' (rules for project operations), 'ecosystem' (rules for interfacing with dependencies), 'oversight' (rules for oversight roles), 'meeting_makers' (rules for meeting conduct), 'steering' (rules for steering committee conduct), 'misc' (rules for other roles), 'outside' (rules for interfacing with external entities), 'candidate' (rules for individuals seeking positions), 'project_lead' (rules for the project lead), 'reviewers' (rules for code reviewers), 'chairs' (rules for committee chairs), 'respected_members' (rules for community members without formal positions), and 'github' (rules for platform usage).

Authors

• Person: Not available Organization: arXiv
  Patterns in the Transition From Founder-Leadership to Community ...

Sources

• Patterns in the Transition From Founder-Leadership to Community ... arxiv.org arXiv via serper

Referenced by nodes (1)

• open source project governance concept