Help us shape the beta
PyGuard is being built in the open. Bug reports, feature requests, and pull requests are all welcome. This page is everything an external contributor needs to get started.
Something broke?
Open a structured bug report. The template collects environment, reproduction steps, expected and actual behaviour, and logs so we can triage without a back-and-forth.
File a bug reportSomething missing?
Tell us the problem first, then the idea. The template asks for the pain point, proposed behaviour, and any alternatives you already considered.
Request a featureWe are honest about turnaround
Time to a first human response on every new external issue.
Time to an accept / defer / decline call with reasoning.
Reports of data loss, crashes on the primary flow, or security issues.
We are a small beta team. We acknowledge every external issue within two business days and return a triage decision (accept, defer, decline) within five.
How we work together
Two short documents describe the contribution flow and the norms we ask contributors to follow.
Section 4.3 evidence
One external user files an issue, we respond, we resolve or defer it. The links below make the full lifecycle visible. Until we paste the real URLs in, this block renders as an obvious placeholder on purpose.
Contribution lifecycle evidence
The table below is the live record of the external issue we processed during the beta. Each card links out to the relevant GitHub URL: the filed issue, the triage comment from our team, and the closing PR or deferral decision.
- 1External issue filed
Link to the GitHub issue filed by an external user.
TODO: add link - 2Team response
Link to the team's triage comment on the issue.
TODO: add link - 3Resolution / deferral
Link to the closing comment, merged PR, or deferral decision.
TODO: add link