This topic describes how membership in Pavilion works. As this is the cannonical source of knowledge for how membership works, the ability to edit it is restricted, however feel free to post in this topic with any questions or suggestions.
Goals of membership
Our membership structure is designed to:
- help us work efficiently and effectively for clients and our open source stakeholders;
- allow members to develop and work at their own pace and in their own direction;
- make our respective roles and responsibilities clear; and
- democratically represent the equal members of our cooperative.
The first thing to know about Pavilion membership is that it is divided into two specialisations: Development (Dev) and Product Management (PM). Each area has three levels: “Open Source”, “Standard” and “Senior”; and a corresponding badge.
Members can hold badges in both specialisations. It is possible to be Senior in both PM and Development. However, this should not be the case for most members. The membership structure is designed to promote focus on one specialisation.
Becoming a member
To join Pavilion you need to take on one open source Dev or PM project with the sponsorship of a senior member in that area (i.e. Dev or PM).
Membership of Pavilion is free. To maintain your membership you need to participate in the work appropriate to your area of focus and level.
Joining as a software developer
Unless it’s really necessary, don’t send a private message to the member you want to review your work. Make a post on the task you want to work on and @mention the member to get their attention. The senior member will assess your case for working on the project and for joining.
If the senior member approves your proposal to work on the project, and agrees to sponsor your membership, you’ll become an open source member and work on the project under the senior member’s supervision.
Joining as a product manager
There will naturally be fewer PM-focused members than Dev-focused members. Each project can have only one PM responsibility (if any), but can have multiple Dev responsibilities. This means that senior product managers will accept fewer sponsorships of new members.
This is not to say that we don’t accept new product managers! If you’re interested in joining as an Open Source Product Manager, make a post in a PM project topic and @mention a member with a senior PM badge. As with Dev sponsorships, it’s best not to send members private messages about sponsorship unless it’s really necessary.
Working on Projects
Once you’re an Open Source member you can work on the development of (if you have a Dev badge), or help to manage (if you have a PM badge), any open source projects.
Each badge level gives you greater access to work. The access is described in the description for each badge. It follows this pattern for both areas (PM and Dev).
- Open Source: You can work on open source.
- Standard: You can work on standard client jobs.
- Senior: You can work on difficult client jobs, and sponsor new members.
Open source work is not compensated, but it is just as important as our Client work. One of Pavilion’s core goals is to maintain, extend and strengthen our open source work.
Client work is compensated according to the value each participant in the work provides to the client. The process of specifiying, assessing and assigning work is described in more detail in How we work with clients.
Every member, no matter what badges they have, is expected to devote time to open source work. Open source work is an important part of the philosophy and culture of Pavilion, and also underlies and supports alot of our client work.
There are no specific quotas on open source work, however a member’s involvement in our open source work is a factor in whether they maintain their badge(s) and the membership (see “Losing a badge” and “Ending a membership” below.
Gaining a badge
Everyone, no matter what you’ve done before, starts at Open Source. You can gain a Standard badge in a area if at least three quarters (3/4) of cooperative members approve in a vote. Currently these votes are held on a case by case basis via private poll on this site. Member’s votes in a member-badge poll are secret.
Factors that members consider when granting a badge to a member by poll are:
- the member’s contributions, in the badge’s specialisation, to open source and client work;
- the attitude and teamwork of the member; and
- the skill of the member in the badge’s specialisation.
The skill of a member matters, but it is considered equally alongside the other factors. Furthermore, the volume of a members’ contributions is not determinative. Pavilion encourages a healthy work-life balance and does not reward a high volume of contributions over a short period.
Consistency of a member’s contributions is more important than volume. If a member consistently makes quality contributions at a high volume they will not be penalised for this, but the sustainability of a member’s volume of contributions over time is considered.
Not all members will want to gain badges other than Open Source. Our badge system does not necessarily relate to skill level. You may be an experienced software developer, and just want to work on our open source projects in your spare time (if that’s you, please get in touch!).
Holding a badge
A member must be an active participant in the work a badge grants access to to maintain that badge.
It is possible to lose a badge. This can happen for a few different reasons, and should not be seen as inherently a bad thing. Member’s focus or life circumstances can change, meaning that holding a badge no longer makes sense.
Members can give up a badge voluntarily. A member’s badge can also be removed if three quarters (3/4) of cooperative members decide to remove it by a poll. Member’s votes in a badge removal poll are secret.
Factors that are considered by members in a badge removal vote are the same as the factors considered in granting a badge, with one caveat: a member’s skill is not a determinative factor in badge removal, unless the member’s contributions are consistently of poor quality over time and the member does not demonstrate improvement.
Conversely, if a member’s skill level is high, but they have a bad attitude, demonstrate poor teamwork, or are not contributing to open source projects, their skill in the area will not prevent their badge being removed.
Ending a membership
Any member can leave Pavilion voluntarily at any time and their membership will end. A membership can also cease if three quarters (3/4) of the membership vote to end the membership in a poll on this site. Member’s votes in a poll to end a membership are secret.
The factors that are considered in ending a membership, whether voluntarily or by poll, are:
- the length of time the member has been a member of Pavilion;
- the length of time the member has been inactive in any type of work; and
- the attitude and teamwork of the member.
Performance is not a factor in considering whether to end a membership. Furthermore, as with the granting of badges, being an ‘active participant’ is not primarily measured by volume. Members are not expected to work 24/7, 365 days of the year. Consistency of a member’s contributions is more important.