delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2012/10/24/22:16:22

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <5088A0E3.40106@icarus.com>
Date: Wed, 24 Oct 2012 19:16:03 -0700
From: Stephen Williams <steve AT icarus DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120825 Thunderbird/15.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] gEDA/PCBs diversity Was: Pin hole size
References: <0EEF0A12-8BF9-435B-9CE0-ABBF2C655879 AT jump-ing DOT de> <201210250104 DOT q9P14cfD020621 AT envy DOT delorie DOT com> <B276A77F-2426-45E6-B41D-B603DB9137EA AT jump-ing DOT de>
In-Reply-To: <B276A77F-2426-45E6-B41D-B603DB9137EA@jump-ing.de>
X-Enigmail-Version: 1.4.4
Reply-To: geda-user AT delorie DOT com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


In the Icarus Verilog world we handle the situation by using git
and teaching the newbies to make patches that I (or Cary) can
apply with a simple "git am". We get to cast an eye to make sure
our vision is being followed, but we're flexible enough that odds
are good your patch will be applied. Currently we don't have the
patch flow to justify adding yet more committers, but IV is
really dense code:-/

On 10/24/2012 06:53 PM, Markus Hitter wrote:
> 
> Am 25.10.2012 um 03:04 schrieb DJ Delorie:
> 
>> The gEDA development community needs more talented, enthusiastic,
>> and like-minded people to jump in and do the work ;-)
> 
> Maybe ... well ... if you advertise "be talented and do the work"
> it's kind of unlikely somebody jumps up and says "here I am!".
> Newbies never consider them selfs to be talented or gEDA expert or
> whatever. Yet, a lot of work is done already, it just doesn't hit
> the repo. gEDA is well written, average talent is sufficient and
> development is easy, at least to my experience.
> 
> Committing new developments can be considered to _save_ work
> instead of adding some. No more duplicated work, get your work
> updated for free, no longer ask people to compile your fork instead
> of the official one ... and so on.
> 
> 
> How about calling out for a collection? May everybody with public
> or private forks out there put his/her stuff back into the main
> repo. Acceptance guaranteed. Bug fixes go right into the master
> branch, other stuff into dedicated branches. And everybody
> interested may get access to commit and work on his stuff right in
> the main repository.
> 
> Maybe commit access for everybody sounds bold. But I see other 
> communities where this works. These messing-everything-up
> developers simply don't exist and even if some of them appear,
> that's what we have source code management for: everything is
> revertable.
> 
> Opinions?
> 
> 
> Markus
> 
> - - - - - - - - - - - - - - - - - - - Dipl. Ing. (FH) Markus
> Hitter http://www.jump-ing.de/
> 
> 
> 
> 
> 
> 


- -- 
Steve Williams                "The woods are lovely, dark and deep.
steve at icarus.com           But I have promises to keep,
http://www.icarus.com         and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlCIoOMACgkQrPt1Sc2b3im1ggCgzkuDUSwH9fQIR2zR2M7PceYx
fKwAn3Ac1vEDhaCSjBLMzg4lh2yMCHK9
=+fV1
-----END PGP SIGNATURE-----

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019