Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document community organisation process and contacts #71

Open
fdegir opened this issue Oct 12, 2020 · 2 comments
Open

Document community organisation process and contacts #71

fdegir opened this issue Oct 12, 2020 · 2 comments
Labels
documentation Improvements or additions to documentation

Comments

@fdegir
Copy link
Member

fdegir commented Oct 12, 2020

Description

Eiffel Community is an active community and there are times certain requests require to be handled. Some of the example requests are

  • adding/inviting people to Eiffel GitHub Organisation
  • creating new repositories
  • creating new maintainers group
  • adjusting permissions of individuals on certain repositories

These requests are currently taken care of by few volunteers from the community. It is important the community contributes to managing Eiffel Organisation so the workload on individuals who are currently working with community support can be reduced.

In order for this to happen, it is important to

  • list and document types of activities that are currently being handled by volunteers from the community
  • determine the approval requirements (eg. approval of 1 TC members is sufficient for a change to pass for infra changes)
  • appoint individuals as Eiffel organisation contacts

Motivation

Identify and document community support process and contacts who look after support issues.

Exemplification

Communities generally have list of interested/appointed people looking after support issues which Eiffel Community could adapt as well.

Benefits

Increased visibility on how community support works and reduced workload on the current volunteers.

Possible Drawbacks

N/A

@fdegir
Copy link
Member Author

fdegir commented Oct 12, 2020

@henning-roos This is the AP we got during the TC meeting 2 weeks ago. Could you please check and update the issue if I missed anything or didn't clarify enough?

@henning-roos
Copy link
Member

You have captured the essence of it, @fdegir , I think. I don't have anything to add.

@magnusbaeck magnusbaeck added the documentation Improvements or additions to documentation label Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants