[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-cvs: CVS update: index.html
User: danmc
Date: 07/03/09 09:59:40
Added: . index.html projects.html
Log:
move elsewhere to avoid a conflict
Revision Changes Path
1.1 eda/geda/website/gsoc/index.html
Index: index.html
===================================================================
<HTML>
<HEAD>
<TITLE>gEDA Google Summer of Code 2007</TITLE>
<STYLE TYPE="text/css" MEDIA="all" TITLE="Default">
@IMPORT URL(../geda.css);
</STYLE>
<LINK rel="icon" href="../favicon.ico" type="image/x-icon">
<LINK rel="shortcut icon" href="../favicon.ico" type="image/x-icon">
</HEAD>
<BODY>
<div id="nav">
<IMG SRC="../graphics/navlogo.gif" WIDTH="105" HEIGHT="24">
<ul>
[
<li> <A HREF="../index.html">Home</A> </li> |
<li> <A HREF="../news/index.html">News</A> </li> |
<li> <A HREF="../screenshots/index.html">Screenshots</A> </li> |
<li> <A HREF="../tools/index.html"></A>Tools </li> |
<li> <A HREF="../download.html">Download</A> </li> |
<li> <A HREF="../mailinglist/index.html">Lists</A> </li> |
<li> <A HREF="http://geda.seul.org/wiki";>Docs</A> </li> |
<li> <A HREF="../developer.html">Devel</A> </li> |
<li> <A HREF="../search.html">Search</A> </li> |
<li> <A HREF="../links.html">Links</A> </li>
]
</ul>
<h3>
<A HREF="../index.html">gEDA</A> -> GSoC 2007
</h3>
</div>
<div id="faq">
<CENTER>
<H2>
gEDA Google Summer of Code 2007<br>
Application information
</H2>
</CENTER>
<H3>
<A HREF="#google">Google applications</A><BR>
<A HREF="#timeline">Timeline and Commitment Level</A><BR>
<A HREF="#project">Project Details</A><BR>
<A HREF="#integration">Integration into gEDA</A><BR>
<A HREF="#student">Student Details</A><BR>
</H3>
<HR>
<H4>
<A NAME="timeline"></A>
Project timeline and commitment level
</H4>
<p>
Details for student applications to Google can
be found in the <a href="http://code.google.com/soc/studentfaq.html";>
Google SOC Student FAQ</a>.
</p>
<hr>
<H4>
<A NAME="timeline"></A>
Project timeline and commitment level
</H4>
<p>Google Summer of Code projects should be considered a full
time job and will require that level of time commitment. In addition,
there must be some working code committed in time for the midterm
evaluation for a good review.
</p>
<hr>
<H4>
<A NAME="project"></A>
Project Details
</H4>
<p>When submitting an application or project proposal, please include the
following details about the project:
<ul>
<li>Summary of the project including the end goal</li>
<li>Detail the scope of the project. What do you intend on delivering
and what do you not indend on delivering.</li>
<li>Provide a timetable for the project including certain
milestones.</li>
<li>Is this a rewrite or porting of existing software or is it a "from
scratch" project.</li>
</ul>
</p>
<hr>
<H4>
<A NAME="integration"></A>
Project Integration
</H4>
<p>
It is important for us to understand how your project will
fit into the rest of gEDA. To help us understand this, also include
the following information:
<ul>
<li>Which componenents of gEDA will be affected and require code
changes? Examples are "only PCB" or "libgeda, gnetlist, gschem, and
PCB".</li>
<li>Are any new dependencies required over the existing ones? If so,
what are they? Are the new dependencies widely ported?</li>
<li>Will these changes force a change in any existing work flows that users may currently be employing?</li>
</ul>
</p>
<hr>
<H4>
<A NAME="student"></A>
Student Information
</H4>
<p>
Tell us a little about yourself in your application.
<ul>
<li>What programming experience do you have?</li>
<li>What experience do you have with CAD tools in general and gEDA in
particular?</li>
<li>What electronics experience do you have?</li>
<li>Are you familar with the existing codebase which may affect your
project?</li>
<li>Anything else which may be relevent to this project?</li>
</ul>
</p>
</div>
<div id="footer">
<h5>
Last update:
$Id: index.html,v 1.1 2007/03/09 14:59:40 danmc Exp $
</h5>
</div>
</BODY>
</HTML>
1.1 eda/geda/website/gsoc/projects.html
Index: projects.html
===================================================================
<HTML>
<HEAD>
<TITLE>gEDA Google Summer of Code 2007 Project Ideas</TITLE>
<STYLE TYPE="text/css" MEDIA="all" TITLE="Default">
@IMPORT URL(../geda.css);
</STYLE>
<LINK rel="icon" href="../favicon.ico" type="image/x-icon">
<LINK rel="shortcut icon" href="../favicon.ico" type="image/x-icon">
</HEAD>
<BODY>
<div id="nav">
<IMG SRC="../graphics/navlogo.gif" WIDTH="105" HEIGHT="24">
<ul>
[
<li> <A HREF="../index.html">Home</A> </li> |
<li> <A HREF="../news/index.html">News</A> </li> |
<li> <A HREF="../screenshots/index.html">Screenshots</A> </li> |
<li> <A HREF="../tools/index.html"></A>Tools </li> |
<li> <A HREF="../download.html">Download</A> </li> |
<li> <A HREF="../mailinglist/index.html">Lists</A> </li> |
<li> <A HREF="http://geda.seul.org/wiki";>Docs</A> </li> |
<li> <A HREF="../developer.html">Devel</A> </li> |
<li> <A HREF="../search.html">Search</A> </li> |
<li> <A HREF="../links.html">Links</A> </li>
]
</ul>
<h3>
<A HREF="../index.html">gEDA</A> -> projects
</h3>
</div>
<div id="faq">
<CENTER>
<H2>
Google Summer of Code 2007<br>
Project Ideas
</H2>
</CENTER>
<H3>
<A HREF="#whatis">What is pcb?</A><BR>
<A HREF="#look">What does it look like?</A><BR>
<A HREF="#author">Who are the current authors of pcb?</A><BR>
<A HREF="#version">What is the current version?</A><BR>
<A HREF="#download">Where can I download it?</A><BR>
</H3>
<HR>
<H4>
<A NAME="whatis"></A>
What is pcb?
</H4>
<p>
<em>PCB</em>: PCB support for multiple non-copper layers that are
more editable. These layers would need to be allowed as part of an
element and standalone. These are things like keepout regions,
assembly drawing, an actual board outline layer that is not just a
copper layer. See <a
href="http://pcb.cvs.sourceforge.net/pcb/pcb/doc/ideas/database.txt?view=markup";>database.txt</a>
and
<a
href="http://pcb.cvs.sourceforge.net/pcb/pcb/doc/ideas/keepouts.txt?view=markup";>keepouts.txt</a>
for some thoughts on this.
<p>
<hr>
<H4>
<A NAME="look"></A>
What does it look like?
</H4>
<p>
<em>New component/gschem</em>: A parts manager that takes a graphical
symbol and a physical footprint and marries the two to produce a heavy
part. In addition, this tool should be able to support multiple
backend flows. By this I mean that the parts manager should be able
to also indicate how the symbol should be netlisted for spice, gnucap,
or other backends. If possible it would be nice to integrate this
into gschem in a way that allowed symbols to be placed and the
footprint attribute to come up with a list of choices.
</p>
<hr>
<H4>
<A NAME="look"></A>
What does it look like?
</H4>
<p>
<em>gnetlist</em>: Totally rework the internals using gnetman and/or
Steve Meiers work. This would be with an eye towards scalability.
Ideally highly capable and efficient internal data structures and
methods for accessing the database should be used. Then a
scheme/guile api provided. It may be a benefit to use swig to allow
easy interfacing to multiple scripting languages.</td>
</p>
<hr>
<H4>
<A NAME="look"></A>
What does it look like?
</H4>
<p>
<em>libgeda</em>: expand libgeda (if needed) to provide a complete
enough guile interface to be able to do more complex database
manipulations. One use would be to have a back annotation tool that
used libgeda instead of relying on perl. The problem with perl is
that you've involved Yet Another Gschem Parser. This actually may be
combined with the previous project about rewriting the gnetlist
internals.
</p>
<hr>
<H4>
<A NAME="look"></A>
What does it look like?
</H4>
<p>
<em>gwave</em>: work on bringing gwave more up to speed in terms of
not requiring guile-gtk (which is basically dead I as far as I can
tell), possibly supporting hdf5 (as a way to help move towards a
better than ascii format that is non proprietary), adding a waveform
calculator that lets you do things like add waveforms, do fft's, etc.
<em>Needs a gwave mentor</em>.
</p>
<hr>
<H4>
<A NAME="look"></A>
What does it look like?
</H4>
<p>
<em>PCB</em>: develop a test framework for as much of pcb as possible.
I'd love to see a fairly large regression test suite. Some examples
are sets of layouts that just barely pass and just barely fail each of
the different DRC checks, generate BOM's, x-y files, generate gerbers
and maybe use gerbv to do a graphical xor against a "golden" file.
</p>
<hr>
<H4>
<A NAME="look"></A>
What does it look like?
</H4>
<p>
<em>PCB</em>: improve the DRC interface for pcb. Perhaps have a drc
layer that gets generated when you run DRC. Then you could have an
interface that lets you step through them and see on that layer,
exactly what failed. Maybe this could be combined with making the drc
checks more unit testable.
</p>
<hr>
<H4>
<A NAME="look"></A>
What does it look like?
</H4>
<p>
<em>libgeda/gschem</em>: add hooks into gschem needed to fully support
things like backannotation of simulation results and click-to-plot
results.
</p>
<hr>
<H4>
<A NAME="look"></A>
What does it look like?
</H4>
<p>
Build a footprint calculator that can take the IPC rules and produce a
pcb footprint. Preferably write this in a way where the core program
is independent of a gui so that you can script it for generating
entire large famlies of footprints or hook it up to a GUI of choice
(lesstif, gtk, maybe even cgi). Would require the purchase of
IPC-7351 (approximately U.S.A. $100)and verifying that one is allowed
to produce such a calculator.
</p>
</div>
<div id="footer">
<h5>
Last update:
$Id: projects.html,v 1.1 2007/03/09 14:59:40 danmc Exp $
</h5>
</div>
</BODY>
</HTML>
_______________________________________________
geda-cvs mailing list
geda-cvs@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-cvs