X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<57C73F16.4050807@xs4all.nl>
Date:	Wed, 31 Aug 2016 22:33:26 +0200
From:	"Bert Timmerman (bert DOT timmerman AT xs4all DOT nl) [via geda-user AT delorie DOT com]" <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] Mac OSX Support for pcb
References:	<CAJZxidB+XPopvZoV5hn9Mga0tP=x2jkqd2d4rn-8y=+8g_tZFQ AT mail DOT gmail DOT com> <20160205092413 DOT 21482 DOT qmail AT stuge DOT se> <CAJZxidD90UgR1j_Tsubv=nEiUs9W6Lyk5VSYp_sO6jfpc2FgKg AT mail DOT gmail DOT com> <57C703E1 DOT 3050203 AT iee DOT org>
In-Reply-To:	<57C703E1.3050203@iee.org>
Reply-To:	geda-user AT delorie DOT com

M. J. Everitt (m DOT j DOT everitt AT iee DOT org) [via geda-user AT delorie DOT com] wrote:
> On 31/08/16 17:06, Chad Parker (parker DOT charles AT gmail DOT com) [via 
> geda-user AT delorie DOT com] wrote:
>> So, if I want to share a fix for one of these bugs, the process is... 
>> what? Do I need to be granted permission to push a new branch to the 
>> geda git repository? I seem to recall something about branches 
>> needing to be "/home/user/branch". Is there anything special I would 
>> need to do to put it in that kind of path? Or is that just the branch 
>> name?
>>
>> Thanks,
>> --Chad
>>
>> On Fri, Feb 5, 2016 at 4:24 AM, Peter Stuge (peter AT stuge DOT se 
>> <mailto:peter AT stuge DOT se>) [via geda-user AT delorie DOT com 
>> <mailto:geda-user AT delorie DOT com>] <geda-user AT delorie DOT com 
>> <mailto:geda-user AT delorie DOT com>> wrote:
>>
>>     Chad Parker (parker DOT charles AT gmail DOT com
>>     <mailto:parker DOT charles AT gmail DOT com>) [via geda-user AT delorie DOT com
>>     <mailto:geda-user AT delorie DOT com>] wrote:
>>     > I don't know how many mac users of pcb there are out there, but
>>     if it's
>>     > something folks think they want to keep up, then I'll file some
>>     bug reports.
>>
>>     Please do.
>>
>>
>>     //Peter
>>
>>
> Chad .. I think DJ can give you an account on the git server. You also 
> might want to tap up Igor, and he can merge the changes into pcb-rnd 
> mainline .. there's quite a bit of active development going on there, too.
>
> Not entirely sure what the roadmap is for mainline pcb these days .. I 
> rather felt it was stuck in a 'maintenance' phase :/
Hi all,

The roadmap I have in mind is basically to get the gcode exporter bugs 
fixed and then push a release candidate to flush out any serious 
shortcomings before doing a release that can be picked by distros.

Maybe add a couple of exporters while I'm at it, there seem to be good 
candidates.

This is a roadmap which is open for debate (please do voice your opinion 
on what you think is important for you as a user of pcb).

Anyone can open a "roadmap" blue print on Launchpad and start a write-up 
about a requested feature.

Anyone can join in on how to solve a bug.

These things can get quickly done if we get rid of the bus number of "1" 
or "2".

We need more people to get active and actually test and review patches 
and get them commits to an acceptable level.

And by an acceptable level, I mean no trailing white space, no quick 
hacks, no gtk3 stuff (for now), identation, etc. etc.

Sunday September 25th will see another "monthly pcb code sprint", I hope 
to see you all participating.

Kind regards,

Bert Timmerman.

Oh, and BTW, I first have to figure out and dry-run the release process 
as it is a first for me.

- Raw text -