Section 6 ‐ General Principles of Team Membership - ApertureViewer/Aperture-Opertations-Manual GitHub Wiki

All individuals formally recognized as members of the Aperture Viewer team, regardless of their role or level of contribution, are expected to:

• Understand and wholeheartedly embrace the project's Ethos ("Nothing Is Not Possible"), Mission, Vision, and Core Philosophy as detailed in Part 1 of this AOM.
• Consistently embody and actively promote the project's Community Values (kindness, understanding, shared growth, positivity) in all interactions related to Aperture Viewer, both internally with other team members and externally with the broader community.
• Adhere strictly to the Aperture Viewer Code of Conduct (see Appendix [E]) and all other policies outlined in this AOM.
• Contribute positively to the team environment and project goals.

6.1 Philosophy on Team Growth

The Aperture Viewer project values organic growth, driven by genuine passion, shared values, and demonstrable skill. Our philosophy on expanding the team is centered on finding individuals who not only possess relevant expertise but also deeply resonate with our core principles.

• Value Alignment First: The foremost consideration for any potential new team member is their alignment with Aperture Viewer's Ethos, Community Values, Vision, and Mission. We seek individuals who are enthusiastic about our goals and committed to fostering a positive, inclusive, and respectful environment. "Good vibes" and a constructive attitude are essential.
• Skill and Contribution: We look for individuals who can bring valuable skills, knowledge, or a strong willingness to learn and contribute meaningfully to their chosen area (e.g., QA, social media, documentation, development, translation).
• Collaborative Spirit: Team members should be collaborative, open to feedback, willing to teach what they know, and eager to learn from others.
• Commitment and Reliability (within a Volunteer Context): While we understand that team members are volunteers with other commitments, a reasonable level of reliability and follow-through on accepted tasks is important for project progress.
• Organic Growth: The team will expand as needed and as suitable individuals express interest or are identified. We prioritize finding the right people over rapid expansion.
• Transparency and Honesty: We expect all team members to operate with transparency and honesty in their dealings within the project.

Our aim is to build a dedicated, passionate, and harmonious team that works together effectively to make Aperture Viewer the best it can be.

6.2 Application and Accession Process for New Team Members

The process for becoming a formal member of the Aperture Viewer team is designed to ensure that all new members are a good fit for the project's culture, values, and operational needs, and that the existing team is welcoming of their inclusion.

6.2.1 Expression of Interest / Nomination

• Individuals interested in joining the team in a specific capacity (e.g., QA tester for XXXXX XXXXX's team, social media assistant for XXXXX XXXXX's team) should typically first express their interest to the relevant Core Leadership Team member managing that area, or to the Project Lead.
• Existing team members may also nominate individuals they believe would be a valuable addition to the team.

6.2.2 Initial Discussion and Preliminary Approval by Project Lead

• Before any formal application is extended, the Core Leadership Team member who wishes to bring a new person onto their sub-team (or the Project Lead, if for a direct role) must discuss the potential candidate with the Project Lead (William Weaver).
• This discussion will cover the candidate's potential role, their suitability, and any known background relevant to their potential fit within the team.
• The Project Lead must give preliminary approval before the individual is invited to formally apply. This step ensures alignment with overall project strategy and resource considerations.

6.2.3 Formal Application

• Once preliminary approval is granted, the candidate will be invited to complete a formal (but simple) "Aperture Viewer Team Application Form" (see Appendix [C] for template).
• This form will gather basic information about the candidate, their skills, their understanding of Aperture Viewer's values, and their reasons for wanting to join the team.

6.2.4 Application Review by Line Manager / Lead

• The completed application form will be submitted to the Core Leadership Team member who will be the candidate's direct "line manager" or lead for their area of contribution (e.g., Head of QA for a QA applicant, Community & Social Media Manager for a social media applicant).
• This lead will review the application for suitability, completeness, and alignment with their team's needs.

6.2.5 Project Lead Review and Endorsement

• If the line manager/lead finds the application favorable, they will forward it with their recommendation to the Project Lead (William Weaver) for a final review.
• The Project Lead will assess the application in the context of the overall project and team dynamics.

6.2.6 Core Leadership Team and Advisory Board Accession Process (Unanimous Consent / No Objection)

This step is crucial for ensuring team cohesion and is modeled on an accession principle:

• Core Leadership Team Unanimous Consent: The candidate's application (or a summary thereof, along with the Project Lead's endorsement) will be presented to all current members of the Core Leadership Team (XXXXX XXXXX, XXXXX XXXXX, XXXXX XXXXX, and William).
  • Each Core Leadership Team member must give their explicit, affirmative consent for the candidate to join the team.
  • If any Core Leadership Team member has significant reservations or does not consent, the candidacy may be paused for further discussion or declined. The goal is full buy-in from the existing leadership.
• Advisory Board "No Objection" (for roles with significant project influence or access): For candidates being considered for roles that may involve access to highly sensitive strategic discussions or have significant influence on project direction (typically Core Leadership roles themselves, or key contributor roles as determined by the Project Lead), a "no objection" consultation will be held with formally appointed Advisory Board members.
  • Advisory Board members will be informed of the candidacy and given an opportunity to express any serious concerns or objections.
  • While not a formal vote, a strong objection from an Advisory Board member would be given serious weight by the Project Lead and Core Leadership Team in the final decision.

This accession process ensures that the team builds itself collectively and that new members are welcomed by the entire existing leadership structure, fostering a stronger, more unified team. The Project Lead (William Weaver) facilitates this process and makes the final determination based on the outcome of these consent/consultation stages.

6.2.7 Offer of Team Membership

• If the accession process is successful (unanimous Core Leadership consent and no overriding objections from the Advisory Board where consulted), the candidate will be formally offered team membership by the Project Lead or the relevant line manager/lead.

6.3 Onboarding Process & Requirements

Once an offer of team membership is accepted, the new team member must complete the following onboarding process before gaining full access to internal team resources or commencing their role:

• Review of Aperture Operating Manual (AOM): The new team member will be provided with a copy of this AOM (or a link to its official version) and will be required to read it thoroughly, paying particular attention to:
  • Part 1: Foundation & Identity (Mission, Vision, Ethos, Values)
  • Part 3: Team Membership & Conduct (Code of Conduct, other relevant policies)
  • Sections relevant to their specific role and area of contribution.
• Signing of Required Agreements:
  • Code of Conduct Acknowledgment: Formal acknowledgment (e.g., via a signed digital statement or an explicit agreement in a designated channel) that they have read, understood, and agree to abide by the Aperture Viewer Code of Conduct (Appendix [E]).
  • Non-Disclosure Agreement (NDA): All formal team members, regardless of role, must sign the Aperture Viewer Non-Disclosure Agreement (Appendix [F]) to protect confidential project information and internal discussions.
  • Contributor License Agreement (CLA) / Content Contribution Agreement: All team members, regardless of whether their primary role involves direct code or content creation, must sign the Aperture Viewer Contributor License Agreement (Appendix [K]). This is a precautionary measure to ensure that any incidental contributions (e.g., suggestions that are implemented, documentation snippets, test case descriptions) are properly licensed to the project.
• Discord Server Setup:
  • Ensure they are a member of the official Aperture Viewer Discord server.
  • Be assigned appropriate roles on Discord by an administrator (e.g., "QA Team," "Social Media Team," access to relevant private team channels).
• GitHub Access (if applicable):
  • If the role involves direct interaction with GitHub repositories (e.g., developers, QA reporting bugs, documentation contributors), they will be invited to the ApertureViewer GitHub organization with appropriate permissions for their role (e.g., "Triage" for bug reporters, "Write" access to specific documentation repositories if contributing directly there). Code commit access to primary development branches remains exclusively with the Project Lead.
• Introduction to Team & Tools:
  • Formal or informal introduction to other relevant team members.
  • Guidance on using any specific tools or platforms relevant to their role (e.g., GitHub Issue templates, specific Discord channel protocols).
• Clarification of Role and Initial Tasks:
  • A discussion with their line manager/lead (or the Project Lead) to clarify their specific responsibilities, initial tasks, and any immediate project priorities relevant to their role.

A template for an Onboarding Checklist to track these steps is provided in Appendix [D]. Completion of this onboarding process is mandatory for all new team members.