Community
Community
Section titled “Community”Protos is an experimental open-source programming-language project under active development. Questions, ideas, bug reports, documentation improvements, code, tests, benchmarks, tools, examples, and other contributions are welcome.
GitHub remains the live project coordination surface; this website does not mirror issue state or design conversations.
News and milestones
Section titled “News and milestones”Official Protos announcements are published in GitHub Discussions — Announcements. The homepage displays recent announcements dynamically from that source, without maintaining a versioned Markdown archive in the website. GitHub Discussions is the canonical news archive and the place to read or react to announcements.
Make your first contribution
Section titled “Make your first contribution”If you are new to Protos, start with the pinned newcomer Discussion: Want to make your first contribution to Protos? Start here 🌱.
It points newcomers toward the current contribution path without copying live Issue state into this website. You can also browse open good first issues.
Useful contributions are not limited to runtime code. Documentation, executable examples, tests, independent environment/installation reports, tooling, and focused bug reproduction are all valid ways to help.
Questions, ideas, and design discussion
Section titled “Questions, ideas, and design discussion”Use GitHub Discussions for questions about using or understanding Protos, exploratory proposals, design discussion, contributor help, introductions, and experiments.
If you are unsure whether something is ready to become tracked work, start in Discussions.
Bugs and actionable work
Section titled “Bugs and actionable work”Use GitHub Issues for reproducible bugs, concrete documentation problems, and sufficiently scoped actionable work.
A design idea does not need to become an Issue until there is a concrete problem or outcome worth tracking.
Contributing
Section titled “Contributing”Read the contribution guide before preparing a substantial change.
For external contributions, a branch or fork followed by a Pull Request is the normal integration boundary. Changes should be narrow enough to review, respect the normative specification, and report validation evidence appropriate to their impact.
AI-assisted and fully AI-generated contributions are welcome under the same correctness, review, provenance, specification, and validation standards as other contributions. When AI materially shaped a contribution, the project asks for a brief disclosure in the Pull Request.
Security
Section titled “Security”Do not publish vulnerability details, credentials, private data, or working exploit material in an ordinary public Issue or Discussion.
Follow the canonical Security Policy, which directs reporters to GitHub’s private vulnerability-reporting path when available.
Conduct and support
Section titled “Conduct and support”Project spaces follow the Code of Conduct. Strong technical disagreement is welcome; personal attacks and harassment are not.
Support is currently best-effort because Protos is experimental. The canonical Support guide explains where to ask questions and what information makes them easier to answer.