|
# Frequently Asked Questions
|
|
# Frequently Asked Questions
|
|
|
|
|
|
### Are you aware that Kicad's code base is not of the highest quality?
|
|
### Are you aware that KiCad's code base is not of the highest quality?
|
|
|
|
|
|
Yes, before embarking on this project we conducted an in-depth study of
|
|
Yes, before embarking on this project we conducted an in-depth study of
|
|
the code base of Kicad and other open source EDA packages. We are very
|
|
the code base of Kicad and other open source EDA packages. We are very
|
|
much aware of the places in the Kicad code base where a serious clean-up
|
|
much aware of the places in the KiCad code base where a serious clean-up
|
|
would be useful. Fortunately, thanks to the work of many competent
|
|
would be useful. Fortunately, thanks to the work of many competent
|
|
programmers, these areas are becoming less and less numerous. We also
|
|
programmers, these areas are becoming less and less numerous. We also
|
|
plan to help in that domain. The main Kicad developers are also
|
|
plan to help in that domain. The main KiCad developers are also
|
|
conscious of this problem and are working hard to improve things. Having
|
|
conscious of this problem and are working hard to improve things. Having
|
|
said this, if you can criticize Kicad code it's because it is open
|
|
said this, if you can criticize KiCad code it's because it is open
|
|
source. Nobody knows if the code for proprietary EDA packages is better
|
|
source. Nobody knows if the code for proprietary EDA packages is better
|
|
or worse.
|
|
or worse.
|
|
|
|
|
... | @@ -18,11 +18,11 @@ or worse. |
... | @@ -18,11 +18,11 @@ or worse. |
|
Of course, it would be better to do more, but this is what we can afford
|
|
Of course, it would be better to do more, but this is what we can afford
|
|
now. However, this already represents quite a step forward with respect
|
|
now. However, this already represents quite a step forward with respect
|
|
to the past. To our knowledge, this is the first time a full-time
|
|
to the past. To our knowledge, this is the first time a full-time
|
|
developer is devoted to Kicad for a full year, and we will be able to do
|
|
developer is devoted to KiCad for a full year, and we will be able to do
|
|
even more if people
|
|
even more if people
|
|
[donate](http://cernandsociety.web.cern.ch/technology/kicad-development).
|
|
[donate](http://cernandsociety.web.cern.ch/technology/kicad-development).
|
|
We hope that our example will be followed by other organizations, so
|
|
We hope that our example will be followed by other organizations, so
|
|
that manpower is not an issue for Kicad anymore. Then the issue will be
|
|
that manpower is not an issue for KiCad anymore. Then the issue will be
|
|
to properly organize this manpower and to ensure only high-quality code
|
|
to properly organize this manpower and to ensure only high-quality code
|
|
makes it to the main
|
|
makes it to the main
|
|
tree.
|
|
tree.
|
... | @@ -33,25 +33,25 @@ We are lucky to have several very competent object-oriented developers |
... | @@ -33,25 +33,25 @@ We are lucky to have several very competent object-oriented developers |
|
in our section. Our team is mostly made of electronics engineers and
|
|
in our section. Our team is mostly made of electronics engineers and
|
|
computer scientists, with lots of experience in complex projects, both
|
|
computer scientists, with lots of experience in complex projects, both
|
|
hardware and software. But ultimately, the best way to evaluate the
|
|
hardware and software. But ultimately, the best way to evaluate the
|
|
quality of our work is to look at the code we contribute to Kicad.
|
|
quality of our work is to look at the code we contribute to KiCad.
|
|
|
|
|
|
### How aligned are you with the main Kicad developers?
|
|
### How aligned are you with the main KiCad developers?
|
|
|
|
|
|
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?)
|
|
### 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
|
|
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
|
|
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
|
|
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
|
|
it too seriously. Real contributions to KiCad are made through Launchpad
|
|
(see e.g. the
|
|
(see e.g. the
|
|
[kicad-gal](https://code.launchpad.net/~cern-kicad/kicad/kicad-gal)
|
|
[kicad-gal](https://code.launchpad.net/~cern-kicad/kicad/kicad-gal)
|
|
project for which there is [daily-built
|
|
project for which there is [daily-built
|
|
PPA](https://code.launchpad.net/~adamwolf/+archive/kicad-gal-testing-daily))
|
|
PPA](https://code.launchpad.net/~adamwolf/+archive/kicad-gal-testing-daily))
|
|
and are extensively discussed in the Kicad developers mailing list.
|
|
and are extensively discussed in the KiCad developers mailing list.
|
|
|
|
|