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

Remove old ML list links

This commit is contained in:
Mark Roszko 2022-07-22 19:37:06 +00:00
parent 097f30a272
commit 39105df0ea
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CONTRIBUTING.md
View File

@ -1,7 +1,7 @@
## Joining the development team ## Joining the development team
To begin contributing to KiCad, you should first join the [KiCad Developers mailing list](https://launchpad.net/~kicad-developers). 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 and other developers can help you.
@ -15,7 +15,7 @@ KiCad welcomes contributions via merge requests on GitLab. Here are some tips t
1. Always create a new branch for merge requests instead of using your fork's master branch. 1. Always create a new branch for merge requests instead of using your fork's master branch.
2. Make sure your code submission follows the [KiCad Code Style Guide](https://dev-docs.kicad.org/en/rules-guidelines/code-style/), see below for some details. 2. Make sure your code submission follows the [KiCad Code Style Guide](https://dev-docs.kicad.org/en/rules-guidelines/code-style/), see below for some details.
3. Make sure all User Interface changes follow the [User Interface Guidelines](https://dev-docs.kicad.org/en/rules-guidelines/ui/). 3. Make sure all User Interface changes follow the [User Interface Guidelines](https://dev-docs.kicad.org/en/rules-guidelines/ui/).
4. If you are planning a large change or new feature, be sure to ask on the [developer mailing list](https://launchpad.net/~kicad-developers) before you begin your work to see if anyone else is working on it and to ensure that it fits into the overall development plans. 4. If you are planning a large change or new feature, be sure to ask on the [developer mailing list](https://groups.google.com/a/kicad.org/g/devlist) before you begin your work to see if anyone else is working on it and to ensure that it fits into the overall development plans.
5. Give merge requests a short and descriptive title that summarizes the major changes it contains. A longer description of the changes should be contained inside the description of the merge request. 5. Give merge requests a short and descriptive title that summarizes the major changes it contains. A longer description of the changes should be contained inside the description of the merge request.
### Code style and formatting ### Code style and formatting

4
README.md
View File

@ -49,8 +49,8 @@ GitLab CI pipeline status can be viewed for Linux and Windows builds of the late
* [plugins](plugins) - Sourcecode for the 3D viewer plugins * [plugins](plugins) - Sourcecode for the 3D viewer plugins
* [qa](qa) - Unit testing framework for KiCad * [qa](qa) - Unit testing framework for KiCad
* [resources](resources) - Packaging resources such as bitmaps and operating system specific files * [resources](resources) - Packaging resources such as bitmaps and operating system specific files
** [bitmaps_png](bitmaps_png) - Menu and program icons - [bitmaps_png](bitmaps_png) - Menu and program icons
** [project_template](project_template) - Project template - [project_template](project_template) - Project template
* [scripting](scripting) - Python integration for KiCad * [scripting](scripting) - Python integration for KiCad
* [thirdparty](thirdparty) - Sourcecode of external libraries used in KiCad but not written by the KiCad team * [thirdparty](thirdparty) - Sourcecode of external libraries used in KiCad but not written by the KiCad team
* [tools](tools) - Helpers for developing, testing and building * [tools](tools) - Helpers for developing, testing and building