Clarify the GitHub organization membership in the documentation

[SoryRawyer]

We have a page on using GitHub to communicate but it currently only provides guidelines to show membership or adjust notifications. I think we could expand on this to provide more details on the following:

• How contributors get to be invited to the organization
• Why someone would want to be added to the organization
• If we have any specialized roles or groups in the organization and how they're used

[anishasingh-dev]

Hi @jywarren 👋

I’d like to work on this issue. From what I understand, the goal is to expand the existing GitHub communication page to better explain:

• "How contributors are invited to the organization ",

• "why someone might want to be added ", and

• "whether there are specific roles or groups within the organization and how they’re used."

My plan would be to first review the current documentation and existing practices, then propose clear, non-prescriptive wording that reflects how things work today (without introducing new policies).

Please let me know if this sounds good, or if there’s a specific file or page you’d prefer I start with. Thanks!

[magdmartin]

@SoryRawyer are you making a reference to the Communicating via GitHub page?

• How contributors get to be invited to the organization
• Why someone would want to be added to the organization
• If we have any specialized roles or groups in the organization and how they're used

The questions you listed are relevant and answered in OpenRefine governance document. Could we just add a mention in the Communicating via GitHub page to reference the Governance document?

[SoryRawyer]

@magdmartin that's the page I'm thinking of, yes. I think a link to the governance document with a short snippet about what questions are answered there would be a sufficient update to close this issue.

@anishasingh-dev, is this update something you'd be interested in working on? Also, I'm not sure what association @jywarren has but it doesn't look like they're a part of the OpenRefine GitHub organization and so cannot assign issues in the project.

[anishasingh-dev]

Yes, I’d be happy to work on this update.
And sorry about the earlier mention ,that was my mistake. I understand now that the change would involve adding a short snippet on the Communicating via GitHub page with a link to the Governance document.
I can open a PR with this update shortly, unless there’s anything specific you’d like me to include.

[anishasingh-dev]

I’ve closed the earlier PR and opened PR #538 which updates
docs/technical-reference/github.md as requested and fixes the broken link.
Happy to adjust anything if needed.