PEG Rules of Engagement

(Redirected from The prpl Way)
Jump to: navigation, search

Everyone participates as an individual[edit]

Individuals who participate in a prpl Foundation PEG or are elected as a community representative to the TSC does so on their own behalf and not on behalf of their employer or another entity. This is intended to encourage frank and open discussion as well as collaboration between individuals from different employers and backgrounds.

Open to all positive participation[edit]

prpl Foundation PEGs are open to all people who have an interest in the software created by a PEG, regardless of their official membership in prpl or their employer's membership in prpl. This specifically includes individuals from all marginalized groups. Individuals may only be excluded in extreme situations if they violate the community code of conduct.

Access to higher levels of authority will be granted to members of the community based upon the peer acclaim with an appreciation of the unique experiences and skills of those members.


PEG discussions, minutes, deliberations, project plans, plans for new features, and other artifacts are open, public, and easily accessible. (from [1]). Meetings announcements should be provided with sufficient notice for all members. A summary of the discussions of every meeting will be posted online. As is as far as is technically possible, all meetings will be recorded and made freely available online. This level of transparency is intended to allow members of the community to understand the current status of the project regardless of geographic location or ability to participate in meetings.


Code modification proposals in prpl foundation PEGs are decided using consensus. The purpose of this system is for all members of the community to have an equal say in the direction of the project. This participation will lead to software that best fits the needs of all members of the community.


Consistent with prpl Foundation’s mission, PEGs will create software which is interoperable across architectures and platforms. Minor optimizations and bug fixes for platforms are acceptable but all features will be interoperable.