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

Code of conduct #1123

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Code of conduct #1123

wants to merge 1 commit into from

Conversation

AlexsJones
Copy link
Contributor

As we grow this community I believe a basic code of conduct will be required to maintain quality and standards.

I also have a CFP being written highlighting Helmfile and I'd like to feel we have made some steps to be inclusive as well.

This PR includes a new open googlegroup

@osterman
Copy link
Contributor

Also relevant: https://news.ycombinator.com/item?id=22388639 (GitHub appears to be introducing a discussions medium)

image

I bring this up only to say it might be the wrong timing to move discussions to Google Groups, if GitHub is coming out with something to fill this need.

@osterman
Copy link
Contributor

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported by contacting the project team at [email protected].

Never mind my earlier comment as it appears I misunderstood the purpose. =)

@AlexsJones
Copy link
Contributor Author

Also just to mention, I am happy to hand over the google group ownership to nominated project leaders if you give your email addresses.

@mumoshu
Copy link
Collaborator

mumoshu commented Mar 12, 2020

@AlexsJones Hey! Thanks for starting this.

This looks good. But on the other hand, I'm not sure - What's the exact problem we're trying to solve with this?

@AlexsJones
Copy link
Contributor Author

Hey @mumoshu from my perspective the contributor covenant achieves two things:

A) Standardises the expectation around when people create PR's + issues
B) Creates more legitimacy around the project and its community: Demonstrating there has been thought put into how people can participate in an inclusive way.

( Also google groups helps us to interact with people like yourself around the architectural design in ways that might not be suitable within a ticket )

@naseemkullah
Copy link
Contributor

Perhaps helmfile under the helm org would benefit from inheriting the CNCF CoC #758

@mumoshu
Copy link
Collaborator

mumoshu commented Mar 31, 2020

@naseemkullah Yeah, probably.

@mumoshu
Copy link
Collaborator

mumoshu commented Mar 31, 2020

@AlexsJones Thanks! Makes sense.

Now - Would anyone help me answering questions and moderation in the google group?

I'm already buried in the sea of emails, slack direct messages and mentions, github issues asking how to use helmfile. I'll easily fail if I add another place to answer questions.

@AlexsJones
Copy link
Contributor Author

Looking at #758 I think there is a synergy here on the road to legitimacy as a project.

Incidentally @mumoshu I am happy to help to moderate the end-user community.

@olblak
Copy link
Contributor

olblak commented Jul 22, 2020

I'm already buried in the sea of emails, slack direct messages and mentions, github issues asking how to use helmfile. I'll easily fail if I add another place to answer questions.

IMHO it would make sense to have a mailing list.

Having a mailing list like a google groups will be much sustainable for you as questions will be asked publicly so other people will be able to see them and maybe answer them, also it's easier to search for old information in a mailing than in a slack channel.
Most of the time your answer should be "Please ask on the ML as you reach a bigger audience."

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.

5 participants