So I'll ask a stupid question: Why not base it off of the millions of CoC's already out there? https://abc.xyz/investor/other/google-code-of-conduct.html is a good start. Yes, it's a commercial company, but it could easily be modified.
The CoC as it stands is ridiculous. Here is my contribution to helping. Don't call out inclusion, it should naturally happen with an open CoC. I like the KISS method of working. We want the FreeBSD Project to be a venue where people can work together to make the best operating system, built by a strong community. These values extend beyond just development to all aspects of the Project. This code applies equally to everyone representing the FreeBSD Project in any way, from new members, to committers, to the core team itself. These rules are intended to ensure everyone feels welcome both working within, and interacting with, the Project. This document is a guide to make it easier to enrich all of us and the technical communities in which we participate. This code of conduct applies to all spaces used by the FreeBSD Project, including our mailing lists, IRC channels, and social media, both online and off. Anyone who is found to violate this code of conduct may be sanctioned or expelled from FreeBSD Project controlled spaces at the discretion of the FreeBSD Code of Conduct Committee. Some FreeBSD Project spaces may have additional rules in place, which will be made clearly available to participants. Participants are responsible for knowing and abiding by these rules. *Rules:* *Do no Evil* - Follow the law, acting honorably, and treating co-workers with courtesy and respect. Recognize that everything we do in connection with FreeBSD will be, and should be, measured against the highest possible standards of ethical conduct. *No Retaliation* - FreeBSD prohibits retaliation against any person who reports or participates in an investigation of a possible violation of our Code, policies, or the law. If you believe you are being retaliated against, please contact Ethics & Compliance. *Serve Our Users* - Our users value FreeBSD not only because we deliver a great Operating System, but because we hold ourselves to a higher standard in how we treat users and operate more generally. Keeping the following principles in mind will help us to maintain that high standard: · *Integrity* - Our reputation as a community that our users can trust is our most valuable asset, and it is up to all of us to make sure that we continually earn that trust. All of our communications and other interactions with our users should increase their trust in us. · *Usefulness* - Our Operating System should be useful for all our users. We have many different types of users, from individuals to large businesses, but one guiding principle: “Is what we are offering useful?” · *Freedom of Expression* - FreeBSD is committed to advancing privacy and freedom of expression for our users around the world. Where user privacy and freedom of expression face government challenges, we seek to implement internationally recognized standards that respect those rights as we develop products, do business in diverse markets, and respond to government requests to access user information or remove user content. Contact Legal or Ethics & Compliance if you have questions on implementing these standards in connection with what you do with FreeBSD. · *Responsiveness* - Part of being useful and honest is being responsive: We recognize relevant user feedback when we see it, and we do something about it. We take pride in responding to communications from our users, whether questions, problems, or compliments. If something is broken, fix it. · *Take Action* - Any time you feel our users aren’t being well-served, don’t be bashful - let someone in the community know about it. Continually improving our product takes all of us, and we’re proud that FreeBSD champions our users and take the initiative to step forward when the interests of our users are at stake. *Equal Opportunity Community* Bring a contributor to the FreeBSD community is based solely upon individual merit and qualifications directly related to competence. We strictly prohibit unlawful discrimination or harassment on the basis of race, color, religion, veteran status, national origin, ancestry, pregnancy status, sex, gender identity or expression, age, marital status, mental or physical disability, medical condition, sexual orientation, or any other characteristics protected by law. We also make all reasonable accommodations to meet our obligations under laws protecting the rights of the disabled. *Harassment, Discrimination, and Bullying* FreeBSD prohibits discrimination, harassment and bullying in any form – verbal, physical, or visual If you believe you’ve been bullied or harassed by anyone at FreeBSD, or in the community, we strongly encourage you to immediately report the incident contact to the FreeBSD Ethics & Compliance group. *Conclusion* FreeBSD aspires to be a different kind of community. It’s impossible to spell out every possible ethical scenario we might face. Instead, we rely on one another’s good judgment to uphold a high standard of integrity for ourselves and our company. We expect all FreeBSD’ers to be guided by both the letter and the spirit of this Code. Sometimes, identifying the right thing to do isn’t an easy call. If you aren’t sure, don’t be afraid to ask questions of the FreeBSD Ethics & Compliance group. And remember… don’t be evil, and if you see something that you think isn’t right – speak up! Not really that hard, eh? ---- Julian On Wed, Mar 7, 2018 at 6:44 AM, Julian H. Stacey <j...@berklix.com> wrote: > Mark Linimon wrote: > > On Mon, Mar 05, 2018 at 11:46:59PM +0100, Julian H. Stacey wrote: > > > I agree with the other person's thoughts that FreeBSD fixes uncommited > > > for years destroys incentive to file more fixes. > > > > I do not know anyone who disagrees with this. > > > > The issue is how to get people involved with this utterly thankless task. > > > > And, even if the backlog were to suddenly disappear, we still get more > > PRs per day than we can effectively handle. > > > > One person is not going to be enough to fix this -- and I know, because > > in the past, I've tried being that one person. > > > > > If so, it would be nice if FreeBSD Foundation got a refund for CoC > > > & spent it on a a student janitor to clear up years old send-pr's. > > > > There is a false equivalence here, that time spent on the CoC somehow > > took time away from working on PRs. I don't detect much overlap between > > the people that work on the one, vs. the other. > > > > mcl > > Yes, little overlap in skill sets, just money. A non tech paid for > the easy job of writing a CoC couldn't do send-pr clearance, though > many a FreeBSD user could write a CoC unpaid, without the bad bits. > > Send-pr clearance is much larger, harder, unattractive compared to text or > code creation. Commercial companies get unattractive jobs done using > Money. > FreeBSD Foundation won't have enough money for much send-pr (esp. if > things > like CoC are paid, increasing costs and reducing contributions). > > The Foundation could treat each send-pr cleared like a lottery ticket: > each month some randomised bug clearers would get an unexpected bonus. > Bonus winners advertised monthly on FreeBSD media, encouraging more bug > clearance & more donations to fund it. > > Cheers, > Julian > -- > Julian Stacey, Computer Consultant, Systems Engineer, BSD Linux Unix, > Munich > Brexit Referendum stole 3,700,000 votes, inc. 700,000 from British in EU. > UK Govt. lied it's "democratic" in Article 50 letter to EU paragraph 3. > Petition for votes: http://berklix.eu/queen/ > _______________________________________________ > email@example.com mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-advocacy > To unsubscribe, send any mail to "freebsd-advocacy-unsubscr...@freebsd.org > " > _______________________________________________ firstname.lastname@example.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-advocacy To unsubscribe, send any mail to "freebsd-advocacy-unsubscr...@freebsd.org"