Ways to Contribute - ApertureViewer/Aperture-Viewer GitHub Wiki
Aperture Viewer is a specialized, high-velocity R&D project. Our primary mission is the rapid development and architectural evolution of the viewer's core visual systems.
To maintain our development cadence, all contributions are managed through a structured and limited process. We deeply appreciate the community's interest, and this page outlines the current avenues for participation that align with our operational model.
Primary Method of Contribution: Data & Diagnostics
The most valuable way the community can contribute at this time is by providing high-quality data that aids our focused development sprints.
From time to time, the project may initiate a formal, limited-time Alpha or Beta Testing Cycle. These test cycles will be announced publicly, and participation will be managed through a designated feedback hub (typically a single, specific GitHub Issue).
During these formal testing cycles, detailed bug reports and feedback are mission-critical. Outside of these official cycles, we are not accepting general bug reports.
Code Contributions
The core development roadmap for Aperture Viewer is internally managed and we are not accepting unsolicited code contributions or pull requests at this time. This is to ensure maximum focus on our architectural goals.
Documentation Improvements
Our official documentation resides in the Aperture Viewer Wiki.
If, after thoroughly reviewing the Wiki, you discover a significant error or find that information on an Aperture-exclusive feature is critically missing or unclear, please refer to the "Documentation Inquiries" section of our master support policy.
[!WARNING]
Notice on Bug Reports and Feature Requests
In alignment with our "Ground Control" communications policy, Aperture Viewer does not accept unsolicited bug reports or feature requests via GitHub Issues, email, or any other channel. The development roadmap is closed.
The only exception is for reporting critical security and safety issues.
For a full and complete outline of our communications policy, all available resources, and the correct channel for critical safety reports, please review our canonical policy document:
<-- Contact & Support Policy -->