There are currently 2 versions.
First one is short and sweet and can be put up now.
Second one is more full blown (but needs some work toward the end), which I think can be used later after the project official release.
First, thank you for considering contributing to Makepad. It's people like you that make the open source community such a great community!
We welcome any type of contribution, not just code. You can help with:
As maintainers of this project, we want to ensure that the project lives and continues to grow. Progress should not be blocked by any one person's availability.
One of the simplest ways of doing this is by encouraging a larger set of contributors. Using this approach we hope to mitigate the challenges of maintaining a project that needs regular updates.
It is normal for your first pull request to be a potential fix for a problem but moving on from there to helping the project's direction can be difficult.
We try to help contributors cross that barrier by identifying good first step issues (labelled good-first-issue
). These issues are considered appropriate for first time contributors. Generally, these should be non-critical issues that are well defined. Established contributors will not work on these, to make space for others.
New contributors may consider picking up issues labelled needs-triage
or help-wanted
. These may not necessarily require code changes but rather help with debugging and finding the cause of the issue whether it's a bug or a user's incorrect setup of the library or project.
We keep all project discussion inside GitHub issues. This ensures that valuable information can be searched easily. GitHub issues are the go to tool for questions about how to use the library, or how the project is run.
You shouldn't feel bad for not contributing to open source. We want contributors like yourself to provide ideas, keep the ship shipping and to take some of the load from others. It is non-obligatory; we’re here to get things done in an enjoyable way. 🏆
In order to keep the high performance and efficiency of the Makepad framework, we discourage the introduction of new external dependencies into the codebase. Any new dependency that wants to be introduced must be vetted by the core team ahead of time.
Makepad has a full test suite with coverage setup.
To run the tests, run npm install to install dependencies, then run npm run build:tests-tools && npm test.
Note that the test suite assumes that docker is installed in your environment.
The bigger the pull request, the longer it will take to review and merge. Where possible try to break down large pull requests into smaller chunks that are easier to review and merge. It is also always helpful to have some context for your pull request. What was the purpose? Why does it matter to you? What problem are you trying to solve? Tag in any relevant issues.
To assist reviewers, we ask that you fill out the pull request template as much as possible.
Use a draft pull request if your pull request is not complete or ready for review.
Pull Requests to the protected branches require peer-review approvals and passing status checks to be able to be merged.
When reviewing a Pull Request please check the following steps as well as the existing automated checks:
First off, thanks for taking the time to contribute! ❤️
All types of contributions are encouraged and valued. See the Table of Contents for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions. 🎉
And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
- Star the project
- Tweet about it
- Refer this project in your project's readme
- Mention the project at local meetups and tell your friends/colleagues
This project and everyone participating in it is governed by the
Makepad Code of Conduct.
By participating, you are expected to uphold this code. Please report unacceptable behaviour
to <>.
If you want to ask a question, we assume that you have read the available Documentation.
Before you ask a question, it is best to search for existing Issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
If you then still feel the need to ask a question and need clarification, we recommend the following:
We will then take care of the issue as soon as possible.
Legal Notice
When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project licence.
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <>.
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
Once it's filed:
needs-repro
. Bugs with the needs-repro
tag will not be addressed until they are reproduced.needs-fix
, as well as possibly other tags (such as critical
), and the issue will be left to be implemented by someone.This section guides you through submitting an enhancement suggestion for Makepad, including completely new features and minor improvements to existing functionality. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
Enhancement suggestions are tracked as GitHub issues.
This guide is based on the contributing-gen. Make your own!