Mail Archives: geda-user/2015/09/17/01:41:52
Kai-Martin Knaak wrote:
> Evan Foss (evanfoss AT gmail DOT com) [via geda-
> user AT delorie DOT com] wrote:
>
>
>> I understand that you have contributed meaningfully to this project but
>> we need a team to be blessed by the powers that be.
>>
> In my very humble opinion, we need a working team in the first place. The
> keyword here is "working" as opposed to let patches bit rot, not decide
> weather or not a feature branch should get merged or abandoned, or not the
> least, procrastinate releases and have no road map with goals for future
> development whatsoever. Everything else should come second.
> (Sorry for the harsh words. But realistically, the above characterizes the
> progress of the geda project since about 2008 for the most part. Yes,
> there were significant improvements in some areas and I am glad about it.
> Else, I would have switched away since long. But seen from a distance the
> progress looks glacially -- in particular when compared to projects like
> freecad or kicad)
>
>
>
>> The blessing legitimizes the team.
>>
> Kings and popes need to be blessed...
>
>
>
>> With out a legitimate team the project will devolve back into people
>> fighting on an email list
>>
> Sorry, but I have not seen developers seriously fighting on geda-user ever
> since I started reading it in 2005/2006. The list geda-devel while it was
> readable for mortal users was even more peaceful.
>
>
>
>> and even if code is written no release could ever be issued. gEDA will
>> be known as that project with a million forks,
>>
> Being motivated and capable to contribute but locked out by the powers
> that be constitutes a strong motivation to fork. This is more than pure
> speculation. Remember, why Igor started his pcb-rnd?
>
> ---<)kaimartin(>---
>
Hi Kai-Martin,
I invite you to join the pcb bug team on their quest to squash bugs
during the monthly code sprint on Sunday September 27th.
I prepared a list of bugs we need to look into at:
https://blueprints.launchpad.net/pcb/+spec/triage
The gcode bugs you mentioned in another post are amongst them and have a
prominent place in the list, to be triaged and worked upon.
<quote>
It is these bug reports:
#1389527 GCode generator errors
#1390439 GCode generator - wrong outline
#1390442 GCode generator - missing mill/drillmill
#1390450 GCode generator - drillmill is wrong
#1390452 GCode generator - drill file is mirrored
---<)kaimartin(>---
</quote>
I await your input on these bugs and hope to meet you on #geda.
Kind regards,
Bert Timmerman.
- Raw text -