haskal
/
kicad
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

CONTRIBUTING.md: minor cleanup

This commit is contained in:
Evils 2022-10-12 20:12:08 +02:00
parent 8dea227da7
commit 0047f1433d
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.md
View File

@ -3,7 +3,7 @@
To begin contributing to KiCad, you should first join the [KiCad Developers mailing list](https://groups.google.com/a/kicad.org/g/devlist). This mailing list is used for announcements about development progress (milestones, deadlines, new releases, etc.), discussing the implementation of new features, and for asking general questions about the KiCad codebase. To begin contributing to KiCad, you should first join the [KiCad Developers mailing list](https://groups.google.com/a/kicad.org/g/devlist). This mailing list is used for announcements about development progress (milestones, deadlines, new releases, etc.), discussing the implementation of new features, and for asking general questions about the KiCad codebase.
New developers are encouraged to start small with their contribution, and gradually work their way up to larger changes as they gain knowledge in the codebase. The development team labels issues in the [issue tracker](https://gitlab.com/kicad/code/kicad/-/issues) with "[starter](https://gitlab.com/kicad/code/kicad/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=starter)" when the issue or feature being requested is a good way for a new person to contribute to KiCad. Alternately, you can search through the issue tracker for any issues that look interesting and leave a comment saying you are interested in working on it. If you have any questions while working on these issues, please leave a comment in the issue with the question or comment and other developers can help you. New developers are encouraged to start small with their contribution, and gradually work their way up to larger changes as they gain knowledge in the codebase. The development team labels issues in the [issue tracker](https://gitlab.com/kicad/code/kicad/-/issues) with "[starter](https://gitlab.com/kicad/code/kicad/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=starter)" when the issue or feature being requested is a good way for a new person to contribute to KiCad. Alternately, you can search through the issue tracker for any issues that look interesting and leave a comment saying you are interested in working on it. If you have any questions while working on these issues, please leave a comment in the issue with the question or comment so other developers can help you.
Developing any larger change, such as a new feature, should be discussed on the developers mailing list before substantial work is done. This allows for input from the lead development team to ensure the feature is aligned with the current development goals, and to prevent duplication of work by contributors. Developing any larger change, such as a new feature, should be discussed on the developers mailing list before substantial work is done. This allows for input from the lead development team to ensure the feature is aligned with the current development goals, and to prevent duplication of work by contributors.
@ -34,6 +34,6 @@ Make sure to read the [KiCad Code Style Guide](https://dev-docs.kicad.org/en/rul
Please configure your personal fork of the KiCad project with the following settings: Please configure your personal fork of the KiCad project with the following settings:
1. Settings->General->Visibility->Pipelines should be enabled and set to "Everyone with access". 1. Settings->General->Visibility->CI/CD should be enabled and set to "Everyone with access".
2. Settings->CI/CD->General Pipelines timeout should be set to 3 hours or longer 2. Settings->CI/CD->General pipelines Timeout should be set to 3 hours or longer.
3. The "Allow commits from members who can merge to the target branch." option check box at the bottom of your merge request must be checked. 3. The "Allow commits from members who can merge to the target branch." option check box at the bottom of your merge request must be checked.