X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <55A421F0.8000208@xs4all.nl> Date: Mon, 13 Jul 2015 22:39:12 +0200 From: "Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com]" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] The new to do References: <55A2A0A2 DOT 4080403 AT ecosensory DOT com> <7AE39440-DA68-4491-A965-C1B97D1D86C1 AT sbcglobal DOT net> <20150712213152 DOT 7968b74c AT jive DOT levalinux DOT org> <304D9D86-3CF6-4D61-A5CA-6CE414EA0661 AT sbcglobal DOT net> <20150712224637 DOT 2d4cc2de AT wind DOT levalinux DOT org> <55A2E9B7 DOT 9040502 AT neurotica DOT com> <20150713131707 DOT GA782 AT recycle DOT lbl DOT gov> <55A4042E DOT 5060402 AT neurotica DOT com> <55A41115 DOT 2060607 AT xs4all DOT nl> <55A419C5 DOT 6080206 AT neurotica DOT com> In-Reply-To: <55A419C5.6080206@neurotica.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com Dave McGuire (mcguire AT neurotica DOT com) [via geda-user AT delorie DOT com] wrote: > On 07/13/2015 03:27 PM, Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via > geda-user AT delorie DOT com] wrote: > >>> I think what we need to motivate actual development, rather than >>> conversation, is cold hard CASH. I'll kick in a few bucks for the next >>> round of development, whatever it may be, for gschem and PCB. >>> >>> Anyone else? >>> >>> >> Just my proverbial 0.02 EUR. >> >> IMHO, this is not fair towards the "pure" unpaid volunteers. >> >> This approach put me off last time some bucks were collected through >> LinuxFund (1). >> >> I could be tempted myself to hold off any commits until some cash was in >> sight and a paid for target identified. >> >> To me this approach looks counter-productive on first, second and hind >> sight: if the financial threshold is not met, no commits will follow. >> >> GSoC (2) is another way of getting some progress, although as soon as >> money or big job opportunities are in sight (last time) things can turn >> out sour (abandonware: I have no hard feelings though, it's just a pitah >> nobody was able to pick this one up and follow through, it's probably >> waaaaay over our heads --> magic stuff for a genius/wizard to master). >> >> We are in this together and have to do the grunt work ourselves, long >> live the "doitocracy", these are your tools, let's keep them sharp and >> useful by (y)ourselves ;-) >> > In general I agree, but few things motivate people more than cash. I > wonder if there's some way to do it that actually works. > > -Dave > > Hi Dave, If we were all entrepeneurs depending on pcb for our livelihood ... we would scratch that itch very soon ... just about now ! So there is a way: start coding and send in patches ... and keep hammering on the remaining devs to push them ! Create consensus ! I don't know much about the pcb internals, I'm just amply able to code a plug-in or two ... well, maybe three ;-) All I can do (or did) is push an upgrade for a Dutch or Portugese translation file to the main pcb repo every now and then, correct a typo here and there ;-) I did create a lot of topic branches with patches from Launchpad, on my github sandbox repo (1), as to keep them useful by fast-forwarding (git rebase) and removing bitrot every now and then. It's just that I need someone to give me advice/direction between what is an improvement (good patch --> push this one) or what is not in line with future goals (bad patch --> do not push that one). If there is a "broad consensus" I can merge the good ones into "master" and push, all by popular demand from users and devs. Kind regards, Bert Timmerman. 1) https://github.com/bert/pcb/branches/all