How we got started?
We had our start at NFC 2026 after Glexes organized a "small" Roomparty in the Clarion Room 2210. Sadly only about 20min into the first DJ we got shutdown.
As the rule abiding Con goers that we are the Norwegians (Glexes and Appel) decided to not in fact continue to party in the room, but to instead rent one of the Boats next to NFC.
Since then we had the Idea to do Parties at Cons for everyone to enjoy.
Project Philosophy
OpenForge CLI is built on three core principles:
🎯 Developer Experience First
Every feature should reduce friction and cognitive load. If it's not intuitive, it needs work.
🔧 Minimal Dependencies
We keep the dependency tree small and auditable. Security and maintainability over convenience.
📖 Open by Default
Decisions are made in public. Code, discussions, and roadmap are all transparent.
Contributing
Getting Started
- Fork the repository on GitHub
- Clone your fork locally
- Create a feature branch:
git checkout -b feature/my-feature - Make your changes with tests
- Run the test suite:
npm test - Push and open a Pull Request
What We Look For
- Tests: All new features need tests
- Documentation: Update docs for user-facing changes
- Commit messages: Follow conventional commits
- Code style: ESLint + Prettier enforced
- Scope: Small, focused PRs are preferred
good first issue — they're designed for new contributors.
Code of Conduct
We are committed to providing a welcoming and inclusive environment for everyone.
Treat everyone with respect. Disagreement is not an excuse for poor behavior.
Focus on what is best for the community. Offer suggestions, not just criticism.
Welcome newcomers. Help them learn and grow.
Harassment of any kind will not be tolerated.
Read the full Code of Conduct
Governance
Decision Making
Major decisions are made through RFCs (Request for Comments). Anyone can propose an RFC, and decisions are made after community discussion.
- RFCs are discussed in GitHub Discussions
- Maintainers have final say on merge decisions
- Breaking changes require consensus
Release Process
We follow semantic versioning (SemVer) and maintain a predictable release schedule.
- Patch: Bug fixes (weekly as needed)
- Minor: New features (monthly)
- Major: Breaking changes (yearly)
Maintainers
The project is maintained by a small team of dedicated developers.
Funding & Sponsorship
OpenForge CLI is free and open source, made possible by our sponsors and contributors.
Support the Project
Your sponsorship helps us maintain the project, review PRs, and build new features.
Where Funds Go
- Maintainer time for reviews & releases
- Infrastructure costs (CI, hosting)
- Security audits
- Community events & swag
FAQ
How do I report a bug?
Open an issue on GitHub Issues with reproduction steps.
Is OpenForge production-ready?
Yes! OpenForge is used by thousands of projects in production, including several Fortune 500 companies.
How do I contribute?
Check our Community page for contribution guidelines.
We Need Your Help
There are many ways to contribute beyond code. Here's what we're looking for:
Bug Reports
Found a bug? Report it with reproduction steps.
Documentation
Help improve guides, examples, and API docs.
Translations
Help translate docs to your language.
Feature Ideas
Share your ideas in Discussions.