Re: gEDA-dev: Newbie developer guidelines.

[al davis <ad136-at-NOSPAMfreeelectron_dot_net>]

On Tuesday 24 April 2007 14:35, Stuart Brorson wrote:
> 1.  E-mail Al Davis and ask him if he has any projects
> suitable for you.  Maybe tell him a little bit about your
> skill level, interests, etc.
>
> 2.  Alternately, just choose a project you think you'd like
> (for example implementing JFET models), make it work, and
> then send Al the patches.
>
> The advantage to #1 is that you and Al are on teh same page
> from teh beginning, and you are sure to be working on a
> project he is interested in.  The disadvantage is that he
> might suggest something you are not interested in.  Or he
> might not respond.

The reason I didn't respond to anything in the past few weeks 
was I was on vacation and email sending access was difficult.  
Otherwise, usually a non-response means something got lost and 
you should try again.

>
> The advantage to #2 is that you can get your feet wet
> privately, to see if you enjoy what you are doing, whether
> the code makes sense, etc.  The disadvantage is that Al may
> be uninterested in your work, and you won't find out until
> the end, when you send patches.

That is one of the reasons for plugins.  Everything that can 
move into plugins is moving to plugins.  That way, you can make 
a plug-in for anything you want.  I expect to have many sets of 
user-contributed plug-ins, so even really obscure ones and 
really experimental ones can be distributed,

Without plugins, there is a serious quality issue.  Anything 
that goes into the core needs to be of very high quality, and 
come with complete test cases, otherwise it causes big problems 
in the future. Plugins solve the problem, because people will 
only use the plugins that benefit them.


_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev