Mail Archives: geda-user/2014/04/14/13:31:34
Ed Simmons wrote:
> On 11/04/14 21:21, al davis wrote:
>
>> On Friday 11 April 2014, Stefan Salewski wrote:
>>
>>> The primary question is, if someone other than
>>> Alfons itself can understand his code at all (in reasonable
>>> time).
>>>
>> The code quality is excellent. What it needs is user
>> documentation and a simple way to build it. Just adding a
>> Makefile would go a long way.
>>
>> Don't worry. The Kicad people will take care of it.
>>
> I just tried this out and I'm very impressed - I had a brief look at the
> code and it seems readable and understandable.
>
> Is there anyone making any attempts at integrating this into PCB yet or
> is it purely discussion so far?
>
> Value added to PCB by integrating the ideas in freerouting would be
> enormous. We use PCB for all our layout tasks in house and the one thing
> I wish it had was manual push and shove routing. 5 minutes with
> freerouting had me dreaming of using it with one of my current layouts.
>
> Export -> use freerouting -> import work flow would be a good start, but
> I'd love to see PCB with these features...
>
> What would be the best way to start this task? I have little knowledge
> of the innards of PCB beyond exporters, but I'm very willing to work on
> this...
>
> Bert, I expect you have some plan in mind...???
>
> Ed
>
>
>
Hi Ed and all,
I have not made a plan ... yet.
Best course of action I can imagine is to set up a development branch
called "freerouting" or "devel" on http://git.geda-project.org/pcb/ and
start adding code and (hopefully) applying (Launchpad) patches later on.
This is doable for me because of having push rights on the pcb repository.
BTW: anyone interested in development could apply with DJ for developer
rights.
P.S.: There is a gEDA code of conduct (of course), and some coding style
guidelines and some other limitations (sorry no free beer tokens or
pizza vouchers), but basically this rocks (try not to break stuff).
Another approach is that anyone (and I mean *really* anyone) can fork
and/or clone my development repository at https://github.com/bert/pcb
for free (as in beer), which tries to be an "exact" mirror of the
upstream git://git.geda-project.org/pcb.git (and a lot of topic branches
with Launchpad patches waiting to be merged), and anyone can start to
co-develop, followed by a pull-request when someone feels something with
substance is added (so I can push that upstream).
This approach has the benefit of drive-by commits.
I like to hear other approaches/plans ! They are most welcome.
Kind regards,
Bert Timmerman
- Raw text -