In the Fireside Chats, we noted the need for more concrete examples for each Principle. This makes it easier for a reader (an individual or organization) to understand what each Principle looks like in practice.

Summary

There's been two dependabot alerts and they should be looked at although both are of of moderate-severity.

Background

@jwflory @RichardLitt kindly review.

Details

Outcome

Summary

Provide guidance and suggestions on how someone not involved can get involved with core or periphery work

Background

Currently I ask people interested in the Principles to introduce themselves on a Discourse thread. Because things are vague and unclear on the Principles, this is not a great call to action. With the current core group of folks we have now, we should do some brainstorming and thinking on how to involve others in core circle discussions and periphery participation to spread the Principles far and wide.

Details

Some helpful resources to frame this: the XR Self-Organizing System and @alnermcgunn's thoughts on self-obsolescence in Sustain Podcast ep. 19.

Putting out some kickstarter thoughts:

• Maintenance: Volunteer committee to review changes and proposals to Principles
  • Helpful but this also requires a governance conversation, not sure if we're there yet 😬
• Advocacy: Champion the Principles by bringing them to your org and encouraging internal adoption
• Design: Useful design resources for promoting the Principles would be cool
  • Also a helpful way to include designers as contributors, although might need to make some accommodations for inclusivity
• Promotion: Creating copy+paste definitions to include in a README/CONTRIBUTING guidelines file (?)

Outcome

Decentralized model that includes more people in the design and outreach work for the Principles of Authentic Participation

Summary

Define who Gives authentic participation and who Receives authentic participation to be clear on intended audience / users of these Principles

Background

It is impossible to meet the needs of every type of group. Currently, we are have four loosely-defined target groups:

• Corporations
• Individual contributors
• Humanitarian orgs / NGOs
• Open source project communities

This is a good start, but drilling down deeper into what each group's relationship is to these Principles will enable this Working Group to better name who these Principles are for, and who/what we are trying to contextualize for the intended "user" of these Principles.

Details

I think we are writing these Principles for large organizations (corporate, NGO, or government) that have a vested, selfish interest in open source. Being selfish is okay, but we want to define the ways to get at what you want without stepping on the open source projects and communities. We want to contextualize the norms and expectations of open source projects for individual contributors from large organizations.

Not sure where this will belong in our Principles just yet, but it might help to write a "FAQ" or similar about what these are and who they are for.

Outcome

Clear-eyed vision of who these Principles are for, who/what is being contextualized, so we can always keep that in focus as we push these Principles forward

Originally posted by @jwflory in #6 (comment)

Summary

Create an annotated version of the Principles, à la Annotated OSD, to explain them in more context

Background

An annotated copy of the Principles is a no-nonsense, simple extension to the Principles. Just like the Annotated OSD offers more context to the Open Source Initiative's Open Source Definition, the Annotated Principles would serve a similar function for us.

Details

It does not need to be long. We should focus on simplicity and starting small to get something published, and then iterate further with feedback and a community, if we can build one up. :slightly_smile:

So, closing criteria might be 3-4 sentences for each Principle to offer more context and explanation of meaning.

Outcome

Better insurance that the meaning of the Principles of Authentic Participation will not be corrupted by decentralization

Summary

Create packaged material of Q&A's, FAQs, or other written content to explain and contextualize the Principles

Background

We have gone through the Principles in the last few calls, and now we are at a point where this current group of people are happy with the first initial draft we have. Now, we need to expand the rings of feedback to help this work live on in a decentralized, asynchronous way.

Cue stage-left, the Advocate Kit. This is essentially pre-packaged language to help members of this Working Group and also others who are not to understand these Principles, talk about them with other people, and make sure we mean the same thing when we talk about any given Principle.

Why do this work?

First, it is an experiment. The P.A.P. Working Group was never intended to last forever. It is a special topic of a larger "Accountability & Transparency" group. So, now the primary work is over, how does this work live on from here? What will come of the last three months of conversations? This is an experiment to give participants and future readers a resource they can take and use to advocate for non-public conversations. (Something really hard to measure!)

Second, we are switching from centralized conversations where key stakeholders are all participating in a wider conversation, to a decentralized model. In the decentralized model, we cannot guarantee that anyone who uses, extends, or modifies these Principles will come back and tell the Working Group they did something with the work. So, the point is, the message we send at the start is important. The members of the Working Group may have a keen understanding of what each Principle is all about, but we cannot assume that of every reader. So, let us try to design the language of the conversation with this Advocate Kit, to compromise on the fact that our "downstream" users may not ever come back upstream with how the messaging of these Principles worked or not for them.

Details

• Draft outline of contents for Advocate Kit (below)
• Make new pull request to this repo with Advocate Kit (#9)
• Post request for review as new thread in Sustain forum (here)
• Post update in Working Group thread here
• Write at least one blog post about Advocate Kit

Outcome

Create common language and understanding on what the Principles mean before we focus on outreach and distribution, to ensure the original message is not lost