Skip to content

Latest commit

 

History

History
44 lines (30 loc) · 1.9 KB

File metadata and controls

44 lines (30 loc) · 1.9 KB

"Diamond Does It" Code of Conduct

Our Pledge

I Pledge allegience to the quality standards inherant in the code base provided. There is no way to hold anyone accountable for maintaining quality beyond that. I pledge allegience to the code formatting best practices set forth by Douglas Crockford at least in as far as I comprehend the purpose of those practices. I accept that using a jslint plugin in my IDE is neccessary and indispensable from quality code. I pledge allegience to the future and give my word bound by my honor that I will make the best of my present including all contributions made to this project so the future may realize its full potential.

Our Standards

The Standard response for behavior found to be repugnant according to "Our Pledge" is rejection of commits and potentially, but not promised, comments explaining the changes that would make the code acceptable. The standard process is technically to use a "New Branch, Merge-into-default, Feature Release" model for Git contributions.

Enforcement Responsibilities

There are two types of of communitty members set forth here as "You" and "Me." The responsablities are as follows: "You" do you and I will do me. This is non-negotiable and any repugnance will lead to a full reassessment of things beyond the scope of this document. Please use the contact method provided for further clarification if this becomes neccessary.

Scope

Nothing in this document is restricted neccessarily to the project and is therefore intended to be honored by all participants at all times not withstanding.

Enforcement

The enforcement will be on a case by case basis however in the event enforement needs exceed the resources available a new enforement policy may be adopted without guaruntee of an update made to this document.

Enforcement Guidelines

Each case will have unique guidelines outlined in the comments when provided.