kicad-developers team mailing list archive

[hauptmech <hauptmech@xxxxxxxxx>]

Hi Seth,

I appreciate you sharing your thoughts on this, but it's long in the 
past. I shared the thread links with Wayne so he could see what 'not 
interested' looks like from this community members side. First post with 
no feedback on changing the TRACK object I figured people were busy. 
Second post with no feedback and I figured it was a no-go zone. The 
magnitude of the job touched a lot of points in the source but none of 
it hard. I would have been happy to implement a patch that satisfied the 
core devs. I was little disappointed at the time that I didn't get much 
interest, but otherwise no hard feelings.

I don't agree with you that I, or any other non-core developer, should 
be touching the roadmap. It's a priorities and goals document, a form 
letter so that Wayne and the core team do not have to repeat this info 
for every person that is new or only checks in occasionally. And the 
people achieving the goals should be removing them from the roadmap. It 
would take me days of combing through commits and posts to do what they 
could do in minutes. Not really a good use of time in my opinion.

I do want to mention that if you'd written this a year ago in response 
my original posts, it probably would have led me to persist a bit 
longer. I appreciate that.

Right now I have no time for development, no immediate need for arcs, 
and a big patch for clearances and fan-out that may well have bit-rotted 
into irrelevance by the time work on 6 starts.

Thanks for the reply.

-Hauptmech



On 2/09/18 03:57, Seth Hillbrand wrote:
> Hello hauptmech-
>
> I suspect that the tepid response you have received may be partially a 
> result of the magnitude of doing this job well.  It touches many 
> aspects of the PNS router, zone filling, connectivity, drc among 
> others.  Without a clear, written plan first, it will be hard to say 
> which aspects you are missing.  I suspect that this is why Tomasz gave 
> you a list of definite prerequisites to a good implementation that 
> would be accepted.  Now that these are mostly implemented in the code, 
> you could use them to implement the next steps that Wayne listed below 
> (Gerber plotting/DRC).
>
> In other words, the responses you have received have given you 
> suggestions for groundwork that will let us ensure the overall 
> implementation fits in the project and can be supported in the future.
>
> That said, if your primary interest in Altium import, you might have a 
> look at the Eagle plugin that handles curved traces by approximating 
> them with segments of straight traces.  This gets you everything 
> except PNS support as PNS requires 45º increments at the moment.
>
> On the roadmap, you are correct, it is out of date.  Please feel free 
> to submit a patch to update them (clear the things that are 
> accomplished, move missing v5 items onto v6) and then propose 
> additions.  The files are located in Documentation/development.
>
> Best-
> Seth
>
>
> Am Fr., 31. Aug. 2018 um 21:45 Uhr schrieb hauptmech 
> <hauptmech@xxxxxxxxx <mailto:hauptmech@xxxxxxxxx>>:
>
>      On 1/09/18 00:44, Wayne Stambaugh wrote:
>
> >     I don't ever remember myself or JP not being interested in round traces.
> >       It's just been a matter of priorities and manpower.
>     With arc tracks I had an itch to scratch and tried twice to get
>     core dev buy-in
>     (https://lists.launchpad.net/kicad-developers/msg27878.html,
>     https://lists.launchpad.net/kicad-developers/msg29877.html) so
>     that I could put together a patch that used an approach that would
>     get accepted. When suggesting options for modifying class TRACK I
>     got silence from the core devs and took the hint. C'est la vie.
> >     I do remember
> >     being pretty firm on ensuring that the gerber plotting and DRC are
> >     correct before the drawing tools and file format changes go live.  The
> >     reason for this should be obvious.  Fixing the DRC is in the v6 road map
> >     so that would be the best place to start for someone who has a lot of
> >     free time.
>
>     Why limit development to people that have a lot of free time?
>
>     The v6 roadmap has not been updated in a long time. What remains
>     to be fixed? Looking at the commit history to DRCish files, it
>     looks like there is plenty of activity going on. Can we ask those
>     people to touch the roadmap and update it?
>
>     There have been some ambitious ideas posted on this list about
>     what DRC needs to be, as well as bugs and blueprints. They are not
>     in the v6 roadmap. Should any of them be added?
>
>
> >     The amount of work to implement this is not going to be
> >     trivial and I will expect the design and quality of the DRC code changes
> >     to be high.
> >
> >     Cheers,
> >
> >     Wayne
>
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     <https://launchpad.net/%7Ekicad-developers>
>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>     Unsubscribe : https://launchpad.net/~kicad-developers
>     <https://launchpad.net/%7Ekicad-developers>
>     More help   : https://help.launchpad.net/ListHelp