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

[Docs] Document how to become collaborator on the Arrow project #35130

Closed
raulcd opened this issue Apr 14, 2023 · 3 comments · Fixed by #36445
Closed

[Docs] Document how to become collaborator on the Arrow project #35130

raulcd opened this issue Apr 14, 2023 · 3 comments · Fixed by #36445

Comments

@raulcd
Copy link
Member

raulcd commented Apr 14, 2023

Describe the enhancement requested

With the migration to GitHub we have started using the collaborator role which allows us to give triage role to some users.
I was myself a collaborator before being a committer. This was done in order to be able to label issues, assign them, etcetera.

The role is documented here from the INFRA wiki: https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub

We should document how are we giving triage role so there's a clear way of giving the role to new users.

Component(s)

Documentation

@raulcd
Copy link
Member Author

raulcd commented Jul 3, 2023

We have been adding collaborators and the process for being added as a collaborator is not clear. The role is useful in order to be able to triage for labeling and assigning issues.
At the moment the process is that someone proposes new collaborators on a PR and this usually get approved and merged by a committer. I would propose adding something like the following, not sure if we should do that here: https://github.com/apache/arrow-site/blob/main/committers.md as this is only for the apache/arrow repo:

### Becoming a collaborator

The collaborator role allows users to be given triage role to be able to help with triaging issues. The role allows users to label and assign issues.
A user can ask to become a collaborator or can be proposed by another community member when they have been collaborating in the project for a period of time. Collaborations can be but are not limited to: creating Pull requests, answering questions, creating issues, reviewing PRs, etcetera.
In order to propose someone as a collaborator you must create a PR adding the user to the collaborators list on `.asf.yaml`. Committers can review the past collaborations for the user and approve.

Collaborators that have been inactive for a period of time can be removed from the list of collaborators.

@raulcd
Copy link
Member Author

raulcd commented Jul 3, 2023

@kou do you think this (or something like this) should be proposed to be added to the arrow-site repo or is there somewhere else you think this would fit better?

@kou
Copy link
Member

kou commented Jul 3, 2023

I think that https://github.com/apache/arrow-site/blob/main/committers.md isn't suitable for collabrators because it focuses on "committer".
How about adding this to https://arrow.apache.org/docs/dev/developers/reviewing.html#labelling ? Labelling is one of important permissions for collaborators.

@kou kou closed this as completed in #36445 Jul 5, 2023
kou added a commit that referenced this issue Jul 5, 2023
…role (#36445)

### Rationale for this change

Since we migrated to GitHub we have been using the collaborator role to allow some contributors to start helping with a triage role.
There has been some discussions on making more clear on the process to become a collaborator.

### What changes are included in this PR?

Add some documentation on how to propose / become a collaborator.

### Are these changes tested?

Will trigger the preview-docs.

### Are there any user-facing changes?

No
* Closes: #35130

Lead-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
@kou kou added this to the 13.0.0 milestone Jul 5, 2023
westonpace pushed a commit to westonpace/arrow that referenced this issue Jul 7, 2023
…riage role (apache#36445)

### Rationale for this change

Since we migrated to GitHub we have been using the collaborator role to allow some contributors to start helping with a triage role.
There has been some discussions on making more clear on the process to become a collaborator.

### What changes are included in this PR?

Add some documentation on how to propose / become a collaborator.

### Are these changes tested?

Will trigger the preview-docs.

### Are there any user-facing changes?

No
* Closes: apache#35130

Lead-authored-by: Raúl Cumplido <raulcumplido@gmail.com>
Co-authored-by: Sutou Kouhei <kou@cozmixng.org>
Co-authored-by: Joris Van den Bossche <jorisvandenbossche@gmail.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants