Emanuele Stoppa (https://github.come/ematipico)
A toolchain for web projects, aimed to provide functionalities to maintain them. Biome offers formatter, linter and import sorting usable via CLI, LSP and WASM.
As the project is gaining traction and being used by big projects, we want to provide a secure environment to its maintainers and dependents.
The Biome is a young and welcoming project, that aims to provide alternatives to the developer tools that today exists in the web ecosytem. It follows the OpenJS Foundation principles to operate transparently, openly, collaboratively, and ethically.
By joining the OpenJS Foundation, we want to secure a safe status from a legal point of view, considering the background of the project (being a fork of Rome, licensed by a private company called Rome Tools Inc). We want to make sure that contributions of our contributors are legally protected.
Biome is a Rust a project, hence we are trying to create a learning space, where contributors can learn a new language, especially for people that have "web" background.
Recently Biome won a bounty, which place it as an excellent alternative to Prettier, with outstanding performance gains, especially in CI enviroments.
Biome is currently used by sentry, Polar, Ant Design, Unleash, React Data Grid and more.
In the next months, Biome wants to span itself in different directions: being able to handle CSS/HTML/Vue/Svelte/Markdown, incrasing its formatting capabilities. Also, it wants to increate its linting capabilities, by adding a sub set of the TypeScript checker, and offer more useful lint rules that are currently used by big projects. This will create a viable alterantive to ESLint.
Biome offers LSP and WASM capabilities, which allow it to offers diagnostics out of the box. It doesn't require Node.js to function, so users can download the binary and use it without additional tools.
At Large
- GitHub
- Discord
- Blog posts
N/A
The leadrship of the project is set by the core contributors team. Among these memebers, we have a lead team that deals with conflict resolution and has access important resources such as website, social accounts, emails.
Any core contributor can step up and become a lead.
Current members:
- Jon Egeland @faultyserver
- Madeline Gurriarán @SuperchupuDev
- Nicolas Hedger @nhedger
- Victor Teles @victor-teles
- Takayuki Maeda @TaKO8Ki
- Jon Egeland @faultyserver
Contributors can become maintainers after some contributions to the project, and have passed a voting phase. Maintaines can become core contributors after significant contributions to the project, and have passed a voting phase.
The project is willing to adopt the OpenJS Foundation Code of Conduct (CoC).
https://github.com/biomejs/biome/blob/main/GOVERNANCE.md
- https://github.com/biomejs/biome
- https://github.com/biomejs/biome/blob/main/LICENSE-APACHE
- https://github.com/biomejs/biome/blob/main/LICENSE-MIT
- https://github.com/biomejs/biome/blob/main/ROME_LICENSE (old, forked license)
https://github.com/biomejs/biome-vscode https://github.com/biomejs/setup-biome
https://github.com/biomejs/resources
For each repository, please provide:
- link to repo,
- license information,
- who owns the Intellectual Property (IP),
- link to issue tracker,
- link to code of conduct (CoC),
- optionally, the full list of vendored dependencies contained in the source tree, including license information. A full audit of all vendored dependencies will be required before your project can officially join the foundation, but this can be done later with foundation support.
Does your project currently receive funds? Who do they come from and what are the funds used for?
What needs will your project have from the foundation? Feel free to provide a list.
What questions do you have? What questions might arise during your application?