Editorial and rights policy — Penemue Audio discovery map
Purpose: Preserve credit, enable discovery and practical collaboration, and reduce mistaken assumptions about who owns, created, maintains or has already implemented audio technology. The map is inclusive of commercial, freeware and open-source projects. No developer or manufacturer needs to release source code to merit a listing or respect.
Publish only what the evidence supports
- Identify the original hardware maker, software author, current maintainer, collaborators and rights holder as distinct roles when supported by sources. Do not infer that a software author owns the original brand or firmware.
- Prefer primary sources: vendor documentation, official repositories, release notes, published licenses, public developer statements, maintainer issue trackers. Secondary accounts can supplement but should be labeled.
- Separate source availability, binary availability, firmware requirements, compatibility reports, hands-on verification, and development status. Never imply a generated build has been verified on MPC without a device test.
- Correct outdated or mistaken records promptly. If two people dispute credit, keep the wording neutral and add only evidence-supported information pending resolution. Keep visible change history in the repository.
- Don't describe missing entries as proof a project never existed, or "open opportunity" as a right to clone proprietary software.
IP and rights boundaries
- Respect copyright, trademarks, database rights, license conditions, trade secrets and legally restricted materials. No proprietary ROMs, firmware, samples, factory libraries, product artwork or illegally sourced code are published here.
- Open-source licenses differ. Source availability is not permission to relicense, remove notices, copy trademarks or distribute proprietary assets bundled with an emulator.
- Names are used descriptively to identify products and their makers. No official endorsement, affiliation, or licensing is implied unless documented.
- The site favors legitimate original development, documented reverse engineering, explicit licenses, and lawful collaboration. It does not provide unauthorized bypasses or infringement instructions.
- If a rights holder asks for a review, acknowledge the concern, check the record and relevant evidence, and correct attribution or remove disputed materials when warranted. Use private contact for sensitive details.
Publication authority
The public may submit proposals and pull requests. Only the Penemue owner or an explicitly delegated trusted maintainer can approve deployment. Require GitHub protected branch / ruleset settings and approved PR merges before publishing. A form suggestion is not a validated fact, publication order or endorsement.
Privacy and credit
Use publicly chosen names/handles and professional links; do not publish private addresses, phone numbers, private emails, account credentials, unapproved headshots, or allegations. Allow correction requests and reasonable removal of gratuitous personal details. Contributors do not give up authorship by suggesting an entry.
Commercial respect
Paid software can be great. A commercial modeler may have invested years measuring hardware and maintaining a robust product. Present it as an available legitimate option, not a failure to share source. Open source can enable research and portability; paid software can provide polish, verified compatibility, professional support and a sustainable developer income. Both belong on this map.