... | @@ -40,18 +40,5 @@ quality of our work is to look at the code we contribute to KiCad. |
... | @@ -40,18 +40,5 @@ quality of our work is to look at the code we contribute to KiCad. |
|
We have a lot of respect for their work and we have been discussing
|
|
We have a lot of respect for their work and we have been discussing
|
|
these plans for a long time with them. The [roadmap](WorkPackages) we
|
|
these plans for a long time with them. The [roadmap](WorkPackages) we
|
|
presented is a direct outcome of these discussions. We want to be just
|
|
presented is a direct outcome of these discussions. We want to be just
|
|
one more contributor to
|
|
one more contributor to KiCad.
|
|
KiCad.
|
|
|
|
|
|
|
|
### What's the use of your [Git repo](https://www.ohwr.org/project/cern-kicad/tree/master?)
|
|
|
|
|
|
|
|
It's just a private playground to test ideas. We also use it as
|
|
|
|
convenient temporary storage. It should not be taken to represent in any
|
|
|
|
way code we intend to submit to the main KiCad tree. Please do not take
|
|
|
|
it too seriously. Real contributions to KiCad are made through Launchpad
|
|
|
|
(see e.g. the
|
|
|
|
[kicad-gal](https://code.launchpad.net/~cern-kicad/kicad/kicad-gal)
|
|
|
|
project for which there is [daily-built
|
|
|
|
PPA](https://code.launchpad.net/~adamwolf/+archive/kicad-gal-testing-daily))
|
|
|
|
and are extensively discussed in the KiCad developers mailing list.
|
|
|
|
|
|
|