Privileges and Responsibilities of Membership

Membership of the Programming Historian project comes with both privileges and responsibilities. This page outlines some of those, so that members understand the expectations upon them, and so that the team can function efficiently.

Privileges

Membership of the Programming Historian project comes with the following explicit privileges:

• The right to participate in all decisions made by the Editorial Board, through Github or meetings
• The right to publicly declare yourself a member of the project team, and to use that association in any job applications, grant applications, social media, public facing profiles, etc, as long as it is done in a manner that does not put the reputation of the project at risk or that has not specifically been requested by the board to cease.
• The right to a sabbatical as per our Sabbatical guidelines

Responsibilities

Membership of the Programming Historian project comes with the following explicit responsibilities:

• A duty to do your best for the project at all times.
• A duty to speak up and express concerns.
• A minimum average contribution of one half-day per month to the project.
• Active engagement in any roles held by the member, performed to a suitably high standard
• Average response times to direct @ requests on Github of seven business days.
• All responses when editing a lesson of one week or less (even if just to say I will respond in X days).
• Regular attendance at meetings, or apologies sent in advance.
• A duty to inform the team of any planned absences that will exceed seven business days (eg, planned vacations)

Members who are unable to meet the above requirements are asked to consider stepping down. Members who are found not to meet the above responsibilities may be asked to step down. This allows the team to work efficiently and maintain its strength