kicad-developers team mailing list archive

[Cirilo Bernardo <cirilo_bernardo@xxxxxxxxx>]

----- Original Message -----

> From: Javier Serrano <javier.serrano.pareja@xxxxxxxxx>
> To: Oscad Team <oscad.team@xxxxxxxxx>
> Cc: kannan@xxxxxxxxxx; "kicad-developers@xxxxxxxxxxxxxxxxxxx Developers" <kicad-developers@xxxxxxxxxxxxxxxxxxx>
> Sent: Wednesday, June 11, 2014 12:55 AM
> Subject: Re: [Kicad-developers] Requesting your co-operation for new version of Oscad, a free and open source EDA tool
> 
> [giving in to top posting :)]
> 
> Hello Oscad Team,
> 
> I think it would make sense for us -- and whoever else wants to join
> -- to work together on the preparation of a blueprint encompassing all
> actions required to make simulation work nicely in KiCad. This would
> probably include changes/extensions in file formats and in-depth
> discussion about UI aspects among others. If you do all coding without
> a preliminary green light from the project leader you expose
> yourselves to a bigger probability of having your code rejected, and
> you also deprive yourselves from the possibility of getting good
> feedback during the brainstorming process. For example, off the top of
> my head: QUCS seems to have support for simulating SPICE netlists in
> their roadmap (or maybe done already, I don't know). QUCS can also
> simulate S-Parameter models. What would be the added value of
> supporting ngspice? It's just an example question. I have not given it
> much thought myself. Regarding attribution, the standard way is to
> include a copyright statement in the header of each one of your files.
> If you look at the KiCad sources, you will see many. I guess this
> should be enough for funding agencies to appreciate the extent of your
> work.
> 
> Cheers,
> 
> Javier
> 
> 


[snip]

Generally a statement in the source code is not enough due to the fact
that only developers will ever see this. What funding agencies usually
want is something in a printed document. In addition to the statement
in the source code, there should be an acknowledgement in the eeschema
and/or pcbnew documentation (whichever ones use the code). The exact
requirements of course are to be negotiated between the Oscad team and
their funding agencies. The print requirement is not surprising; the
funding agencies themselves have to report on how they disbursed their
funds and why they believe it was a good use of their resources. Their
bosses won't be at all impressed with "we were mentioned somewhere in
source code" - they want something more publicly visible.

- Cirilo