Add a link to the Apache Code of Conduct#35
Merged
asfgit merged 1 commit intoapache:asf-sitefrom Aug 4, 2016
Merged
Conversation
|
My two cents - good idea to include the link. |
Member
|
Good idea. No need to be discussed on the mailing list IMHO. LGTM |
Member
|
Agreed. Good idea. LGTM |
Author
|
Thanks all. Self-merged. |
robertwb
pushed a commit
to robertwb/incubator-beam
that referenced
this pull request
Jun 5, 2018
melap
pushed a commit
to apache/beam
that referenced
this pull request
Jun 20, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
R: @francesperry
I saw that Apache Fluo (incubating) had this link, and I liked it. https://www.apache.org/foundation/policies/conduct#specific-guidelines
I did not see that this was required by the Podling rules, but IMO there's no harm in being explicit that we want to create a good environment. This is Apache policy anyway, I don't think Beam would be exempt if we wanted to be.
[@jbonofre -- does this need discussion on the Beam list?]