Update GOVERNANCE.md to list expectations of TSC members

Open Beginner friendly
#29 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Open GOVERNANCE.md and review the existing TSC member guidance and links. Add the agreed expectations, including participation, ambassadorship, project stewardship, Code of Conduct and Technical Charter familiarity, and GitHub and LFX Open Profile accounts. Done means the document clearly includes all five expectations and preserves the referenced links.

Written by the indexing model from the issue text.

Description

In today's TSC meeting, we discussed a proposal to add text like the following to the GOVERNANCE.md document:

TSC members are expected to help guide the Chapel project’s direction by…
…participating in TSC activities such as meetings, discussions, and votes
…seeking out and share opportunities to improve the project and grow the community over time
…being guided by what they consider to be best for the Chapel language, its users, the Chapel project, the historical investment in it, and its success going forward
…upholding Chapel’s code of conduct and being familiar with its technical charter
…maintaining an LFX openprofile.dev account for the sake of project voting and coordination

Based on feedback from @DanilaFe , here is a proposed minor update to the second item, discussed (maybe using slightly different words) during the meeting:

…serving as an ambassador to the Chapel project, looking for ways to improve the project and grow the community over time

@ShreyasKhandekar suggested adding GitHub to the final bullet:

…maintaining GitHub and LFX openprofile.dev accounts for the sake of project voting and coordination

There seemed to be general consensus for all of the above, so this issue captures the TODO of making this addition to GOVERNANCE.md

Dominant language
No language data
Stars
1
Forks
1
Avg merge
12d 2h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from chapel-lang/TSC

All issues in chapel-lang/TSC

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.