X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=mail.ud03.udmedia.de; h= mime-version:in-reply-to:references:content-type:message-id :content-transfer-encoding:from:subject:date:to; s=beta; bh=NoF9 IyHpvOAQynhCZ8UJLuf95TOIxuHdffjzWtrIdog=; b=Dwk4gZAf7jiKdJsuHs8F 1xYrr0PeFKACIYTZuw3iymCCWwWk53A3+4CSfOdwFG8dOSe723RJX0IOiceqBIOK mx4grfmFxooeR2z3w3VrFeXypLNL7zkM3ADhPqyvh/runap7TW3ltdmtBx2lpnud Fai/5k7hZpDCFOn+ovVua1Y= Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: <201210250104.q9P14cfD020621@envy.delorie.com> References: <0EEF0A12-8BF9-435B-9CE0-ABBF2C655879 AT jump-ing DOT de> <201210250104 DOT q9P14cfD020621 AT envy DOT delorie DOT com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Markus Hitter Subject: Re: [geda-user] gEDA/PCBs diversity Was: Pin hole size Date: Thu, 25 Oct 2012 03:53:23 +0200 To: geda-user AT delorie DOT com X-Mailer: Apple Mail (2.753.1) Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk 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/