Skip to content

Conversation

@estroz
Copy link
Member

@estroz estroz commented Apr 29, 2020

Add community membership guidelines and membership issue template.

@jberkhahn
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 7, 2020
Copy link
Member

@jmrodri jmrodri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm


New contributors should be welcomed to the community by existing members,
helped with PR workflow, and directed to relevant documentation and
communication channels.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we have a "getting started for contributors" doc? If so, we should link it here (if not, lemme add a TODO).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, will add a TODO.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@estroz
Copy link
Member Author

estroz commented Jul 23, 2020

I've been busy with the SDK v1.0 release, will get around to these comments soon.

@jberkhahn
Copy link
Contributor

I think we need a section for community co-chairs. There might(?) have been a plan to add that in a separate PR but I can't find any reference to that, it might have gotten lost in the shuffle.

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Sep 9, 2020
@estroz
Copy link
Member Author

estroz commented Sep 9, 2020

@jberkhahn you mean community co-chair election? There should be a (s)election process for appointment, so that should be tackled in a separate document. I don't have any plans to work on one personally.

@jberkhahn
Copy link
Contributor

Yeah, I mean a section that says what a community co-chair is, what they do. I thought we had discussed that in the past but can't find that anywhere.

The following apply to the part of codebase for which one would be a reviewer in
an [OWNERS] file (for repos using the bot).

- Code reviewer status may be a precondition to accepting large code contributions
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"may be" is a little unclear. I assume that this precondition would be made by existing reviewers/approvers as part of a PR review?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would read better as: "Large code contributions by non-reviewers is acceptable at the discretion of existing PR reviewers"


New contributors should be welcomed to the community by existing members,
helped with PR workflow, and directed to relevant documentation and
communication channels.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link

@camilamacedo86 camilamacedo86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

after address @asmacdo comments.

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 17, 2020
@estroz estroz force-pushed the chore/community-membership branch from e4965b5 to 87fb010 Compare September 22, 2020 18:25
@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Sep 22, 2020
@openshift-ci-robot
Copy link

New changes are detected. LGTM label has been removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.