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 Project Team, 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 team to cease.
• The right to a sabbatical as per our Sabbatical guidelines
• The support of ProgHist Ltd for publishing and maintaining the systems that support our journals.
• The right to be treated fairly and with respect in all matters related to the project.

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.

Members who have not been meeting their responsibilities to the Project for at least one month may be approached by the Team Development Manager or their Team Leader and asked if they need support, to take a sabbatical, or to consider taking on a new role within the project that better suits their available time and expertise. This discussion will take place through email using the email address that the member has registered to the GoogleGroup with. If the member does not respond in a timely manner (3 weeks), the Team Development Manager or Team Leader will send another email reminder with a 2 week deadline asking for a response. If no response is forthcoming, a ticket will be opened on Github asking the member to get in touch. If the team member does not respond to these attempts, they will be removed from their roles and retired from the project.