Community Guidelines and Code of Conduct for Puppet Communities
We want to keep the Puppet communities awesome, and we need your help to keep it that way. While we have specific guidelines for various tools (see links below), in general, you should:
- Be nice: Be courteous, respectful and polite to fellow community members. No offensive comments related to gender, gender identity or expression, sexual orientation, disability, physical appearance, body size, race, religion; no sexual images in public spaces, real or implied violence, intimidation, oppression, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, or unwelcome sexual attention will be tolerated.
- Encourage diversity and participation: Make everyone in our community feel welcome, regardless of their background, and do everything possible to encourage participation in our community.
- Keep it legal: Basically, don't get us in trouble. Share only content that you own, do not share private or sensitive information, and don't break the law.
- Stay on topic: Make sure that you are posting to the correct online channel and avoid off-topic discussions. Also remember that nobody likes spam.
Guideline violations --- 3 strikes method
The point of this section is not to find opportunities to punish people, but we do need a fair way to deal with people who do harm to our community. Extreme violations of a threatening, abusive, destructive, or illegal nature will be addressed immediately and are not subject to 3 strikes.
- First occurrence: We'll give you a friendly, but public, reminder that the behavior is inappropriate according to our guidelines.
- Second occurrence: We'll send you a private message with a warning that any additional violations will result in removal from the community.
- Third occurrence: Depending on the violation, we might need to delete or ban your account.
- Obvious spammers are banned on first occurrence. If we don’t do this, we’ll have spam all over the place.
- People who are committing minor formatting / style infractions will get some education, rather than hammering them in the 3 strikes process.
- Contact email@example.com to report abuse or appeal violations. This email list goes to Kara Sowles (kara at puppet.com) and Katie Abbott (katie dot abbott at puppet.com).
Getting technical help
- Don't be a jerk: Treat people with respect and consideration.
- Be helpful: Be patient with new people and be willing to jump in to answer questions.
- Be generous: The written word is always subject to interpretation, so give people the benefit of the doubt.
- Don't post chunks: Avoid posting big chunks of text --- use pastebin, gists, or other similar services to shorten it to a link.
- Be patient: Folks might not be around when you ask a question, so wait a while for someone to speak before leaving.
- Search first: Your question might not be new or you might be able to find someone who has already asked or answered your question.
- Don't private message: Ask permission before you send someone a private message (PM). Not everyone likes them. Also, by keeping it in public, others with similar issues can see the solution you were given.
You can log issue and bug reports for Lumogon by filing issues against the repository.
Here are a few guidelines that apply specifically to filing issues:
- Each report is for only one issue. If you find several issues, please separate them into several reports.
- Search before you file an issue, and try to avoid filing duplicates by taking a look at whether your issue has already been filed before.
- Don't start debates on topics not directly related to the scope of a specific issue. We have other places for general discussions.
- Remove unnecessary lines when quoting other comments.
- Please double check to make sure that the information you are including is public (not confidential), especially in attached log files or screenshots.
Git / source guidelines
- If you want to contribute code, start with a discussion on a pull request or issue to make sure that what you want to submit is a good idea and architected in a way that will be useful for others.
- Look at existing pull requests and issues to make sure that you aren’t duplicating effort.
- Review any existing CONTRIBUTOR.MD files associated with the project.
- If you are new to git or GitHub, you might find these resources useful: GitHub help files, Git cheat sheets, and Git Reference documentation.
These documents belong to the community and are licensed under the Creative Commons. You can help improve them!
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License.