Room for More · product and technology
Product and technology
This is the planned safe path for improving the website and tools without exposing the private business vault, real member data or production credentials.
Status: not open yet
There is no separate contribution workspace yet. The current repository mixes the website with private business material, and GitHub access cannot safely be limited to just the website inside that repository.
Do not request or accept access to the current repository. Martin may record your interest, but no product or technology task begins until a separate mirror, split repository or equivalent route has been tested for private-data leakage, review and revocation.
What you own
Once the route is open: the issue or component named in your accepted assignment. You can investigate it in the contribution workspace, make a branch change, add tests or documentation, and open or update a pull request.
Where you start
After activation, start with one bounded documentation, test or low-risk code issue with clear acceptance criteria and a named reviewer. Use synthetic test data. The first task must be useful without requiring production access.
Done and handoff
- The issue criteria are met and the relevant checks pass.
- The pull request or patch explains what changed, privacy/security effects and known risk.
- Third-party code and dependencies have clear source and license information.
- The GitHub link and concise status are in #finished-work.
A local change is not a deployment. Martin or the named maintainer reviews and merges. Deployment and production changes are separate decisions.
Stop and ask
- You see a secret, real member/attendee data or private-vault material.
- The change touches production, payments, authentication, personal-data flows, safety controls or legal copy.
- You need a new paid service/dependency or are unsure about a license.
- The issue needs broader scope, merge, deploy or production configuration.
For an accidental exposure, stop work and tell Martin immediately. Do not investigate production yourself.
Access, confidentiality and rights
Your repository, branch and test access is personal and limited to the task. Do not copy non-public material outside the approved workspace or share it after the task ends.
Before a non-trivial contribution, the paid/unpaid route, confidentiality, ownership or license of the contribution, open-source provenance, credit and portfolio use are put in a separate written agreement. Reading this guide is not acceptance of those terms.
How it can grow
Repeated reviewed delivery can lead to owning a named component or maintenance queue for a period. Repository, merge, deploy and production access remain separate grants. Broader capability in technology does not create access to the private business vault.