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

Principle 0: Don't be a Jerk ;) #313

Closed
awright opened this issue Apr 13, 2022 · 4 comments
Closed

Principle 0: Don't be a Jerk ;) #313

awright opened this issue Apr 13, 2022 · 4 comments

Comments

@awright
Copy link

awright commented Apr 13, 2022

Questions/issue inspired during the 04-13-22 TODO Working Group Call:

  • Every projects has a CoC and Contributing Guidelines. How is this different than the social framework of engagement projects articulate here?
  • How does this sit in relationship to such CoC and Contribution covenant? Making something repetitive or superseding existing guidelines is not the intent, so what is the intent?
  • Would we ever want this to be something that companies "sign on to" as a commitment to how they intend to engagement with open source communties?
@awright
Copy link
Author

awright commented Apr 13, 2022

@jlprat @DuaneOBrien I think these are very important questions. How does this complement and distinguish itself from existing work.

@DuaneOBrien do you recall if these principles were based on another template?

@jwflory
Copy link

jwflory commented Apr 15, 2022

Hi, I was asked to comment from working on the Principles of Authentic Participation.

Every projects has a CoC and Contributing Guidelines. How is this different than the social framework of engagement projects articulate here?

A CoC and contributing guidelines usually deal with person-to-person interaction. Contributor to contributor, contributor to maintainer, maintainer to contributor, etc. The Principles approached it from the lens of a larger organization looking to clarify, codify, and cement its open source vision and mission, and how the organization seeks to shape their image in the open source ecosystem.

How does this sit in relationship to such CoC and Contribution covenant? Making something repetitive or superseding existing guidelines is not the intent, so what is the intent?

It is a type of governance document, similar to a project charter. The Principles were more an expression of values and vision, stemming from influence of the Free Software movement's similar origin in the 1980s and why we wanted to work on the Principles.

Since a CoC or other community covenant is rooted in person-to-person interactions, it deals with more practical governance of the project. Something like the Principles focuses (in my mind) more on the high-level vision and how to cement the foundation of a community.

Would we ever want this to be something that companies "sign on to" as a commitment to how they intend to engagement with open source communties?

The Principles articulated an idealistic vision of how we believed organizations, enterprises, and companies should engage in the open source ecosystem, coming from our group's perspective in the Sustain Summit 2020. Something like the Principles could be adopted as a new commitment, but there should be a sense of how to measure or document adherence to the Principles in order to preserve the authenticity and genuineity of the Principles.

@alice-sowerby
Copy link
Contributor

@awright I am looking to close issues associated with this guide so we can publish it and tidy up the repo. Do you consider this issue concluded and OK to close?

@alice-sowerby
Copy link
Contributor

Closing due to age of issue and overall agreement in calls that the guide contains what it needs to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants