gEDA-dev: Peripheral SoC Project ideas

[Marc Moreau]

I think those fall under 'not-code'.  SoC rules say that the project must be code.  THey explicitly preclude documentation.  I think symbol verification and fixing falls closer to documentaion then it does to code.

We could give it a try, but I don't think it is viable.

-Marc


On Mon, 12 Mar 2007 17:28:32 +0000
Peter Clifton <pcjc2 at cam.ac.uk> wrote:

> Hi,
>
> Does the Google SoC allow projects related to open-source software, yet
> not "code"?
>
> I was wondering if projects including fixing up / verifying symbol  /
> footprint libraries (perhaps via software tools to do so), would be
> allowed.
>
> Another teaching related idea - not necessarily code related:
>
> Teaching materials / tutorials / electronic design case studies taken
> step-by-step through the tools. Bonus points if this is "automated" so
> that all screen-shots etc.. can be grabbed and compiled into the
> documents by doing "make", thereby meaning the screen-shots can (if
> necessary) be kept up-to-date with the current version of the software.
>
> (Perhaps this requires too much hacking of the gschem / PCB code to
> automate with GUI looking like its being "driven").
>
>
> --
> Peter Clifton
>
> Electrical Engineering Division,
> Engineering Department,
> University of Cambridge,
> 9, JJ Thomson Avenue,
> Cambridge
> CB3 0FA
>
> Tel: +44 (0)7729 980173 - (No signal in the lab!)
>
>
>
> _______________________________________________
> geda-dev mailing list
> geda-dev at moria.seul.org
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.seul.org/pipermail/geda-dev/attachments/20070312/378e9d72/attachment.pgp