Section 5 ‐ Team Structure & Roles - ApertureViewer/Aperture-Opertations-Manual GitHub Wiki

This section details the formal roles within the Aperture Viewer project and outlines their primary responsibilities. The structure is designed to be clear and supportive of the project's goals, recognizing the volunteer nature of contributions.

5.1 Overview of Team Structure

Aperture Viewer's team comprises:

The Project Lead.
The Core Leadership Team (which includes the Project Lead).
An Advisory Board (non-operational, strategic counsel).
Contributors in various capacities (Development, QA, Documentation, Community Support, Translation, etc.), who may or may not be formal "team members" depending on their level and consistency of involvement and agreement to project policies.

Formal team membership, especially in roles with specific responsibilities or access to internal project discussions, requires adherence to the project's Code of Conduct, relevant agreements (e.g., NDA, CLA), and the onboarding process outlined in Part 3 of this AOM.

5.2 Core Leadership Team Roles & Responsibilities

5.2.1 Project Lead / Director of Development (William Weaver)

Role Title: Project Lead / Director of Development
Reports To: N/A (Founder, ultimate authority for the project)
Status: Core Leadership Team Member (Volunteer)
Overall Purpose: As the founder and Project Lead / Director of Development for Aperture Viewer, William Weaver (paperwork.resident) provides the overarching strategic vision, technical leadership, and ultimate decision-making authority for all aspects of the project. This role is responsible for guiding the project's mission to deliver unparalleled visual fidelity and creator tools, ensuring the integrity of its open-source codebase, managing key external relationships, fostering a positive team culture, and bearing final accountability for the project's operations and outcomes.
Key Responsibilities & Contributions:
- Strategic Vision, Mission, and Project Roadmap:
  - Define, articulate, and continuously champion the core vision ("Nothing Is Not Possible"), mission, ethos, and strategic objectives of the Aperture Viewer project.
  - Develop, maintain, and direct the execution of the project roadmap, including feature prioritization, development cycles, and release planning.
  - Ensure all project activities, policies, and development efforts are fully aligned with Aperture Viewer's foundational principles and its commitment to visual excellence and creator empowerment.
- Technical Leadership, Architecture, and Core Development:
  - Serve as the principal architect and lead developer for the Aperture Viewer codebase, directly responsible for the design, implementation, and integration of core systems, rendering pipeline enhancements, exclusive features (e.g., Aperture Phototools Suite (Alt+P), Post-Processing Pipeline, Procedural Stars), and shader development.
  - Establish and enforce coding standards, best practices, and architectural guidelines for all software development within the project.
  - Personally conduct the majority of advanced C++ and GLSL development for new, complex features.
  - Exclusively manage all commits to the main development branches (e.g., dev) of the official Aperture Viewer GitHub repository, ensuring code quality, stability, and rigorous version control. This includes reviewing and merging approved Pull Requests from other contributors.
- Overall Project Management and Governance:
  - Establish, maintain, and enforce the project's governance structure, including this Aperture Operating Manual (AOM) and all associated policies.
  - Oversee all operational aspects of the project, ensuring efficient workflow and resource utilization (primarily volunteer time and expertise).
  - Make final, binding decisions on all project-related matters, including feature inclusion, technical direction, policy adoption, team structure, external partnerships, and branding.
- Team Leadership, Mentorship, and Culture:
  - Lead, guide, mentor, and support the Core Leadership Team (Senior Project Partner, Head of Quality Assurance, Community & Social Media Manager) and, by extension, all project team members.
  - Foster a positive, collaborative, inclusive, and respectful team environment, ensuring adherence to the project's Community Values and Code of Conduct.
  - Oversee the recruitment, onboarding, and integration of new team members, ensuring alignment with project needs and values.
  - Resolve internal team conflicts or issues if they cannot be resolved at other levels.
- External Relations and Official Representation:
  - Act as the primary and sole official spokesperson and representative for the Aperture Viewer project in all formal and high-level communications with external entities, including Linden Lab, other Third-Party Viewer projects, press, and potential strategic partners.
  - Manage all sensitive inter-project negotiations and relationships.
- Quality Assurance and Release Management Oversight:
  - Work in close partnership with the Head of Quality Assurance to define and uphold the project's quality standards.
  - Participate in final QA reviews and make the ultimate decision on release readiness for all versions of Aperture Viewer.
  - Oversee the entire release management process, from feature freeze to public announcement.
- Legal, Licensing, and Policy Compliance:
  - Ensure the project's unwavering compliance with its open-source license (GNU Lesser General Public License v2.1) and all other applicable legal and ethical obligations.
  - Personally manage and serve as the signatory for all legal agreements entered into by the project (e.g., Contributor Agreement with Linden Lab).
  - Develop and maintain critical project policies (e.g., Privacy Policy, Code of Conduct, Contributor License Agreement).
- Community Stewardship and Vision Articulation:
  - Act as the primary champion for the project's vision within the broader Second Life and OpenSim communities.
  - Engage with the user community through official channels, providing insight into project direction and gathering feedback to inform future development.
Skills and Qualities:
- Expert-level proficiency in C++ and GLSL shader programming.
- Deep understanding of real-time 3D rendering pipelines, computer graphics principles, and game engine/viewer architecture.
- Strong strategic thinking, project management, and leadership abilities.
- Excellent problem-solving and analytical skills.
- Clear and effective communication skills, both technical and non-technical.
- Unwavering commitment to the Aperture Viewer mission, vision, ethos, and community values.
- Ability to make complex decisions and take responsibility for their outcomes.
- Resilience, dedication, and passion for pushing the boundaries of visual creation.

The Project Lead / Director of Development role is central to every aspect of Aperture Viewer, driving its innovation, ensuring its quality, and guiding its journey as a leading-edge tool for visual creators.

5.2.2 Senior Project Partner (XXXXX XXXXX)

Role Title: Senior Project Partner
Reports To: Project Lead (William Weaver)
Status: Core Leadership Team Member (Volunteer)
Overall Purpose: As Senior Project Partner for the Aperture Viewer, XXXXX XXXXX stands as a pivotal figure alongside the Project Lead, actively shaping the project's strategic trajectory, upholding its core vision, and ensuring its profound connection with the content creator community. This role recognizes her foundational contributions since the project's inception and formalizes her ongoing, integral partnership in guiding Aperture Viewer's evolution and success.
Key Responsibilities & Contributions:
- Strategic Co-Direction: Collaborates directly and actively with the Project Lead in defining, refining, and executing the overall strategic roadmap for Aperture Viewer, including feature priorities and long-term project goals.
- Decision-Making Partnership: Serves as a primary partner in the core decision-making processes for the project, bringing her trusted judgment, historical perspective, and deep understanding of the project’s ethos to bear on all significant choices.
- Vision Stewardship & Evolution: Jointly champions and safeguards the "Nothing Is Not Possible" vision, working with the Project Lead to ensure all development and community engagement efforts remain true to Aperture Viewer’s foundational principles while fostering innovation.
- Creator-Centric Guidance: Integrates her extensive experience as a content creator directly into the strategic partnership, ensuring that the needs, desires, and workflows of virtual photographers, videographers, and artists are central to project development and direction.
- Project Integrity & Values: Actively works with the Project Lead to maintain the integrity of the Aperture Viewer project, ensuring ethical considerations and community well-being are paramount.
- Community & User Experience Insight: Provides crucial insights into community sentiment, user experience expectations, and the potential impact of project decisions, leveraging her long-standing presence and understanding of virtual world cultures.
- Historical Continuity & Future Focus: Acts as a vital link to the project's origins and core motivations, bringing invaluable historical context to the partnership while actively contributing to planning Aperture Viewer's future innovations.
- Representation and Liaison (As Delegated): May, upon specific agreement with the Project Lead, represent Aperture Viewer in communications with specific community groups or individual creators, acting as a trusted liaison to build relationships and gather insights, particularly within the content creator sphere.
Skills and Qualities:
- Deep understanding and embodiment of Aperture Viewer's mission, vision, ethos, and community values.
- Extensive experience as a content creator in virtual worlds.
- Trusted judgment, strategic thinking, and advisory capabilities.
- Strong interpersonal and communication skills.
- Historical knowledge of the project and its community.
- Commitment to collaboration and partnership.

In her capacity as Senior Project Partner, XXXXX XXXXX is an essential member of Aperture Viewer's core leadership. Her perspective, wisdom, and active participation are critical to the project's continued commitment to visual excellence, creator empowerment, and groundbreaking innovation.

5.2.3 Head of Quality Assurance (XXXXX XXXXX)

Role Title: Head of Quality Assurance (QA)
Reports To: Project Lead (William Weaver)
Status: Core Leadership Team Member (Volunteer)
Overall Purpose: The Head of Quality Assurance is responsible for establishing, leading, and championing all quality assurance strategies, processes, and activities for the Aperture Viewer project. This role is critical to ensuring the stability, reliability, usability, and overall quality of each viewer release, aligning with the project's commitment to visual excellence and a refined user experience. The Head of QA works collaboratively with the Project Lead and other team members to integrate quality considerations throughout the development lifecycle.
Key Responsibilities & Contributions:
- QA Strategy and Process Development:
  - Develop, document, and implement a comprehensive QA strategy tailored to the needs of the Aperture Viewer project, considering its open-source nature and volunteer resources.
  - Define and continuously refine QA processes, methodologies, and best practices for testing new features, enhancements, bug fixes, and full release candidates.
  - Establish clear standards and criteria for software quality and release readiness.
- Test Planning and Execution:
  - Create detailed test plans and test cases for new features, major updates, and regression testing, ensuring comprehensive coverage of functionality, performance, usability, and visual fidelity.
  - Personally conduct thorough testing of Aperture Viewer builds, particularly focusing on new and modified areas.
  - Coordinate and oversee testing efforts if additional volunteer QA testers join the team, including assigning tasks, providing guidance, and collating results.
- Bug Tracking and Management:
  - Manage the bug reporting and tracking process, primarily utilizing GitHub Issues.
  - Triage incoming bug reports, verify their reproducibility, gather necessary information, and assign appropriate priorities and labels.
  - Work with the Project Lead to ensure critical bugs are addressed in a timely manner.
  - Track the status of bugs through to resolution and verification.
- Collaboration and Communication:
  - Collaborate closely with the Project Lead (developer) to understand new features, technical implementations, and potential areas of risk from a QA perspective.
  - Provide clear, concise, and constructive feedback to development regarding defects, usability issues, and potential improvements.
  - Communicate QA status, risks, and release readiness assessments to the Core Leadership Team.
  - Actively participate in Core Leadership Team discussions, providing a quality-focused perspective on project decisions.
- User Experience (UX) Advocacy:
  - Advocate for a positive user experience, identifying usability issues, inconsistencies, or areas of potential user frustration during testing.
  - Provide feedback on UI/UX design and workflow from a quality and end-user perspective.
- Documentation and Knowledge Sharing:
  - Contribute to QA-related documentation, such as testing guidelines, common issue workarounds, or information needed for effective bug reporting.
  - Help build a knowledge base of known issues and testing best practices within the team.
- Continuous Improvement:
  - Proactively identify opportunities to improve QA processes, tools, and overall software quality.
  - Stay informed about testing best practices and relevant changes in the Second Life/OpenSim viewer landscape.
Skills and Qualities:
- Proven experience in software quality assurance, with a strong understanding of testing methodologies, test planning, and bug tracking.
- Meticulous attention to detail and a passion for software quality.
- Excellent analytical and problem-solving skills.
- Strong communication and collaboration skills.
- Familiarity with Second Life/OpenSim viewers and the virtual world environment is highly desirable.
- Ability to work independently and manage priorities effectively in a volunteer setting.
- Commitment to Aperture Viewer's mission, vision, and community values.
Access & Tools:
- Access to development builds of Aperture Viewer.
- Appropriate permissions on GitHub for issue management.
- Access to internal team communication channels (Discord).

5.2.4 Community & Social Media Manager (XXXXX XXXXX)

Role Title: Community & Social Media Manager
Reports To: Project Lead (William Weaver)
Status: Core Leadership Team Member (Volunteer)
Overall Purpose: To foster a positive, engaged, and informed community around Aperture Viewer across designated social media platforms. To promote the viewer's features and benefits, share educational content, and act as a friendly, helpful liaison between the users and the development team, all while upholding the project's core values.
Key Responsibilities & Contributions (Summary): (The full scope of responsibilities, platform strategies, content plans, and limitations are detailed in the comprehensive "Aperture Viewer Social Media Roadmap" - see Appendix [H]. This summary highlights core duties.)
- Community Management & Moderation (Primarily Discord):
  - Actively monitor official community channels (especially Discord) for questions, feedback, and discussions.
  - Respond to user queries in a timely, helpful, and kind manner, upholding project values.
  - Enforce community guidelines (as per the Code of Conduct - Appendix [E]), ensuring a respectful and inclusive environment.
  - Facilitate positive community interaction and discussions.
  - Relay user feedback, common questions, and bug reports from community channels to appropriate internal team members or GitHub Issues.
- Social Media Content Curation & Posting:
  - Implement the agreed-upon Social Media Roadmap across designated platforms (Discord, YouTube, Reddit, SL Forums, Flickr [if pursued], Primfeed).
  - Post official announcements (drafted by or approved by the Project Lead) regarding releases, updates, events, etc.
  - Share links to new YouTube videos, Wiki updates, and major GitHub Release Notes.
  - Curate and share user-created content that highlights Aperture Viewer (with permission and proper credit).
  - Suggest content ideas (e.g., for YouTube Shorts, "Tip of the Day" posts) to the Project Lead.
- Community Engagement & Outreach:
  - Actively look for opportunities to engage positively on relevant social media posts and discussions where Aperture Viewer is mentioned.
  - Assist with and coordinate aspects of the influencer and press outreach strategy as defined in the Social Media Roadmap.
- Brand Voice & Values Representation:
  - Ensure all official communications and interactions reflect Aperture Viewer's ethos ("Nothing Is Not Possible") and community values (kindness, inclusion, understanding, helpfulness).
- Reporting and Feedback:
  - Provide periodic updates to the Project Lead and Core Leadership Team on community sentiment, common issues, engagement levels, and the effectiveness of social media strategies.
  - Report findings and suggestions pertaining to the recruitment of social influencers or other outreach opportunities.
Adherence to Specific Agreements:
- The Community & Social Media Manager will operate under the detailed "Role Description & Agreement for Social Media Manager" section within the Social Media Roadmap (Appendix [H]), which outlines specific responsibilities, limitations, access/tools, and includes a "Community & Social Media Manager Conduct Agreement."

(The full "Aperture Viewer Social Media Roadmap" document, including the detailed Role Description, limitations, platform strategies, etc., created by Maladriel, constitutes Appendix [H] of this AOM and is the definitive guide for this role.)

5.2.5 Considerations for Future Core Roles & Team Expansion Needs

As the Aperture Viewer project matures and its community grows, the need for additional specialized leadership or core team roles may arise. The Project Lead, in consultation with the existing Core Leadership Team, will assess these needs organically. The following are considerations for potential future roles and the types of support their teams might require:

Potential Role: Lead Documentation Writer / Wiki Custodian
- Consideration: If the volume and complexity of documentation (primarily the Wiki) expand significantly, a dedicated lead may be needed to oversee its structure, quality, consistency, and the contributions of volunteer writers.
- Focus: Ensuring all Aperture Viewer features, policies, and procedures are clearly, accurately, and comprehensively documented and readily accessible to users and contributors.
- Potential Team Needs Under This Lead:
  - Technical Writers: Individuals skilled in translating technical concepts into user-friendly guides and tutorials.
  - Proofreaders/Editors: Volunteers to ensure clarity, grammar, and consistency across all documentation.
  - Wiki Formatting Specialists: Individuals adept at GitHub Wiki markdown and page organization.
- Support from Project Lead: Direct access to information on new/changed features, review of critical documentation sections, and authority to implement agreed-upon documentation standards.
Potential Role: Head of Community Support
- Consideration: If community support demands on Discord and other channels grow beyond the capacity of the Community & Social Media Manager and general team assistance, a dedicated Head of Community Support might be beneficial.
- Focus: Organizing structured user support, training volunteer support agents, developing and maintaining FAQs and canned responses, ensuring timely and helpful assistance, and escalating complex technical issues to QA or Development.
- Potential Team Needs Under This Lead:
  - Volunteer Support Agents: Individuals with good troubleshooting skills, patience, and knowledge of Aperture Viewer, available to answer user questions on Discord/forums.
  - Moderators (Support-Focused): Community moderators who also have strong support skills.
- Support from Project Lead/Core Team: Provision of technical information for troubleshooting, guidance on official responses to complex support scenarios, and endorsement of support team structures.
Potential Role: Creator Network & Outreach Lead
- Consideration: To proactively build and nurture relationships with the core target audience (photographers, videographers, bloggers, influencers) and expand Aperture's visibility within these communities. Surrealia Hexem, as Senior Project Partner, may naturally fulfill many aspects of this, but a dedicated role could emerge.
- Focus: Identifying key creators, establishing collaborative relationships, facilitating creator showcases using Aperture, gathering specialized feedback from high-level users, and managing programs that promote Aperture within creator circles.
- Potential Team Needs Under This Lead:
  - Community Liaisons/Ambassadors: Individuals well-connected within specific creator communities.
  - Event Organizers: For potential in-world workshops, showcases, or contests featuring Aperture Viewer.
- Support from Project Lead/Core Team: Providing assets and information about Aperture for outreach, strategic guidance on partnerships, and support for creator-focused events.

The Project Lead will work with the Core Leadership Team to determine when such roles are needed and to identify suitable individuals. Any individual stepping into a new leadership role will be onboarded according to the processes in this AOM and will be expected to build and manage their potential teams in alignment with project values and policies.

5.3 Developer Roles & Responsibilities (Templates for Future Growth)

While current core development is primarily undertaken by the Project Lead, as the project potentially attracts more code contributors, defined roles can help clarify expectations and areas of focus. These are template descriptions; actual responsibilities may be tailored. All developer roles report to the Project Lead.

5.3.1 Template: Core C++/Pipeline Developer

Purpose: To contribute to the development and maintenance of the core C++ codebase of Aperture Viewer, focusing on rendering pipeline enhancements, core systems, performance optimization, and new feature implementation.
Responsibilities:
- Design, implement, and test new features or systems in C++.
- Debug and fix issues in the existing C++ codebase.
- Optimize code for performance and memory efficiency.
- Work on integrating and modifying rendering pipeline components.
- Collaborate with the Project Lead on architectural decisions.
- Adhere strictly to Aperture's coding conventions, commenting style, and commit message guidelines.
- Thoroughly test all contributions.
Skills: Strong C++ proficiency, understanding of 3D graphics principles, experience with large codebases, familiarity with game engine architecture or viewer development.

5.3.2 Template: UI/UX Developer

Purpose: To design, develop, and refine the user interface (UI) and user experience (UX) of Aperture Viewer, with a focus on creating an intuitive, efficient, and aesthetically pleasing experience for creators.
Responsibilities:
- Implement new UI elements and floaters using the viewer's UI framework (XUI, XML).
- Refine existing UI layouts for clarity and usability.
- Work on theme development and skinning.
- Gather user feedback on UI/UX and propose improvements.
- Ensure UI consistency and adherence to Aperture's design philosophy.
- Collaborate with other developers on integrating UI for new features.
Skills: Experience with UI development (ideally XUI/XML for SL viewers), understanding of UX principles, graphic design sensibilities (a plus), attention to detail.

5.3.3 Template: Shader (GLSL) Developer

Purpose: To develop, optimize, and maintain GLSL shaders for Aperture Viewer, focusing on visual effects, post-processing, material rendering, and lighting.
Responsibilities:
- Write new GLSL shaders for visual enhancements or features.
- Modify and debug existing shaders.
- Optimize shaders for performance across a range of hardware.
- Implement advanced rendering techniques through shader programming.
- Work closely with C++ developers to integrate shader logic.
Skills: Strong GLSL programming skills, deep understanding of GPU rendering pipelines, 3D math, experience with lighting and post-processing effects.

5.4 Community Team Roles (General Templates for Sub-Teams)

As the project grows, Core Leadership members (e.g., Head of QA, Community & Social Media Manager, potential future Head of Documentation or Head of Support) may build small teams of volunteers to assist in their areas of responsibility. These volunteers, while not part of the Core Leadership Team, are valued members of the broader Aperture Viewer team if they go through the formal application/onboarding process.

The following are general template descriptions for common community team roles:

5.4.1 Template: QA Tester

Reports To: Head of Quality Assurance (XXXXX XXXXX)
Purpose: To assist in testing Aperture Viewer builds (alpha, beta, release candidates) by executing test plans/cases, exploring features, and reporting bugs to ensure software quality and stability.
Responsibilities:
- Download and install test builds of Aperture Viewer as requested.
- Follow test plans and specific testing instructions provided by the Head of QA.
- Conduct exploratory testing to identify unscripted issues.
- Meticulously document and report any bugs, visual artifacts, crashes, or usability issues via GitHub Issues, following project reporting guidelines.
- Provide clear, reproducible steps for any bugs found.
- Communicate testing progress and findings to the Head of QA.
- Verify fixes for previously reported bugs.
Skills: Attention to detail, methodical approach to testing, good communication skills, familiarity with Second Life/OpenSim. Ability to follow instructions and report issues clearly.

5.4.2 Template: Community Moderator (e.g., for Discord)

Reports To: Community & Social Media Manager (XXXXX XXXXX) or Head of Community Support (if role exists)
Purpose: To help maintain a positive, respectful, and welcoming environment in official Aperture Viewer community spaces (primarily Discord) by enforcing the Code of Conduct and facilitating constructive discussion.
Responsibilities:
- Actively monitor designated community channels.
- Address and resolve minor conflicts or violations of the Code of Conduct according to established moderation guidelines.
- Issue warnings or apply temporary moderation actions (e.g., mutes) as authorized.
- Escalate serious violations or persistent problem users to the Community & Social Media Manager or Project Lead.
- Welcome new members and help guide users to appropriate channels or resources.
- Foster positive engagement and answer general questions where possible.
Skills: Strong understanding of Aperture's Community Values and Code of Conduct, good judgment, patience, de-escalation skills, clear communication. Experience with Discord moderation tools is a plus.

5.4.3 Template: Documentation Contributor / Wiki Editor

Reports To: Project Lead or future Lead Documentation Writer
Purpose: To assist in creating, updating, and improving the content of the Aperture Viewer Wiki and other project documentation.
Responsibilities:
- Write new Wiki pages or sections for features, guides, or technical explanations based on information provided or personal research.
- Update existing Wiki pages to reflect new viewer versions, changed features, or to improve clarity.
- Proofread and edit documentation for accuracy, grammar, and style.
- Help organize Wiki content and improve navigation.
- Format pages using GitHub Wiki markdown.
- Suggest areas where documentation is lacking or could be improved.
Skills: Strong writing and editing skills, clarity in explaining technical concepts, attention to detail, familiarity with Aperture Viewer features. Experience with Markdown and GitHub Wikis is a plus.

5.4.4 Template: Translator

Reports To: Project Lead (or a future Translation Coordinator if established)
Purpose: To translate Aperture Viewer's user interface, documentation (Wiki), and potentially other project communications into other languages, making the viewer more accessible to a global audience.
Responsibilities:
- Translate English UI strings (from provided files, e.g., XLIFF or XML) into a target language accurately and contextually.
- Translate Wiki pages or other documentation into a target language.
- Review translations done by others for accuracy and quality, if requested.
- Provide feedback on localization issues or cultural appropriateness of terms.
- Test the viewer with the translated language to ensure strings fit UI elements and display correctly.
Skills: Native or near-native fluency in both English and the target language(s). Strong understanding of grammar and nuance in both languages. Attention to detail. Familiarity with software localization practices is a plus. Experience with Second Life/OpenSim terminology in the target language.

Individuals in these community team roles will be onboarded as per Section 6.3 and must adhere to all project policies, including the Code of Conduct and relevant agreements (NDA, CLA).

5.5 Advisory Board Member Role

The role, responsibilities, and operational guidelines for members of the Aperture Viewer Advisory Board are formally detailed in the Advisory Board Charter, provided in Appendix [A] of this Aperture Operating Manual. In summary, members serve in a purely strategic advisory capacity, offering high-level counsel, wisdom, and perspective to the Project Lead, without operational duties or decision-making authority.

5.6 Official Team Roster & Bios

Maintaining a clear and accessible roster of official team members is important for transparency and community recognition. This section outlines the structure for public-facing bios and the handling of internal team contact information.

5.6.1 Public Team Roster & Bio Guidelines (To be hosted on the Aperture Viewer Wiki)

A dedicated page on the Aperture Viewer Wiki will list all official team members (Core Leadership, Advisory Board, and other formally recognized long-term contributors who consent to be listed).

Purpose: To publicly acknowledge the individuals contributing to the project and provide a brief overview of their roles and, if they wish, their connection to the virtual world community.
Information to Include (per team member, all optional except Name/Role):
- Name (Preferred Public Identifier): This should be the name the team member wishes to be known by publicly in relation to Aperture Viewer (e.g., "William Weaver," "XXXXX XXXXX," their primary avatar name, or a chosen project alias).
- Role(s) within Aperture Viewer: Clearly stated (e.g., "Project Lead," "Senior Project Partner," "Head of Quality Assurance," "Community & Social Media Manager," "Advisory Board Member," "Lead [Language] Translator," "Core Developer").
- In-World Name (Optional but Recommended): Their primary avatar name in Second Life or OpenSim (e.g., "paperwork.resident"). This helps the community connect the project role to an in-world presence.
- Short Bio / Statement (Optional, 2-4 sentences): A brief, self-written statement about their passion for virtual worlds, their interest in Aperture Viewer, their area of expertise, or a general positive message. This should be professional and aligned with project values.
- Link to Personal Creator Portfolio/Platform (Optional & Vetted): If a team member is a recognized content creator and wishes to link to a SFW (Safe For Work), relevant personal platform (e.g., Flickr, YouTube channel showcasing virtual world art, ArtStation), this may be included subject to review by the Project Lead to ensure alignment with project branding and values. No links to commercial stores or primarily sales-focused platforms.
- Profile Picture/Avatar Snapshot (Optional & Vetted): A small, SFW, professional-looking avatar snapshot or project-related image may be included.
Guidelines for Content:
- All content must be professional, respectful, and SFW.
- Bios should be positive and focus on contributions to Aperture Viewer or the broader virtual world community.
- No real-life personally identifiable information (beyond a chosen public name) should be included unless the team member explicitly consents and understands the public nature. The project strongly advises against sharing RL identifying details in public bios.
- The Project Lead reserves the right to review and request edits to any bio content to ensure it aligns with the project's image and values.
Exclusion for Specific Roles/Situations:
- As per the Project Lead's discretion, individuals in certain roles or situations may initially have a more limited public presence (e.g., listed as "QA Tester" without an extensive bio or direct community representation role) until a track record of positive, aligned contribution within the Aperture team is established. This is to protect the project's branding and community environment. All such decisions will be made by the Project Lead in consultation with the Core Leadership Team.

5.6.2 Internal Team Roster & Contact Information

An internal roster will be maintained by the Project Lead and made accessible only to current Core Leadership Team members and, where strictly necessary and on a need-to-know basis, other formal team members who have signed an NDA.

Purpose: To facilitate necessary internal communication and coordination.
Information (Placeholders - to be collected securely and with consent):
- Full Preferred Name (for internal use)
- Role(s) within Aperture Viewer
- Primary In-World Name(s)
- Discord Username (for internal channels)
- GitHub Username (if applicable)
- Email Address (for official project communication, if different from public contact)
- Time Zone (for coordination purposes)
- Emergency Contact Information (Strictly optional, for trusted Core Leadership access only in extreme circumstances, and only with explicit consent).
- Real-life contact information provided to Linden Lab (held by Project Lead only, as per confidentiality agreements).
Security and Confidentiality: This internal roster is considered highly confidential. Access will be strictly limited. Information will be stored securely. Team members must not share this internal contact information outside the authorized group without explicit permission from both the individual concerned and the Project Lead.