kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

> I also would have preferred to vet design changes through
> the development team, but unfortunately we could have
> discussed things for years without getting anywhere.
>
>   

This above paragraph is a highly questionable statement.  Historically
in this project, the pre-work discussion has been not an impediment to
real work getting done.  What has been an impediment is lack of man
hours to actually do work.  So by coming in with a commitment to
actually perform work, you move the normal bottleneck out of the
picture.  And although you might then think that the bottleneck moves to
the discussion, we have never had that problem in this project that I
can recall.  Never, and there are some good reasons for that, all of
which are deliberate.  If you doubt this, sometime google for me saying
on this list that "those that do the work get to decide".   It is an
economic reality of all pure volunteer organizations, we just happen to
recognize it here.

But "getting to decide" and always doing so alone, can be a lonely road
sometimes.


> You don't have to accept these changes and certainly not until
> they can be reviewed and test driven.  I am certainly not trying
> to tell you how to maintain the project: I know it is a daunting
> task.
>
> I would, however, suggest using the submission to form a separate
> launchpad branch from "testing", incorporating these changes
> for review and test-driving before even contemplating a merge.
> You and the other developers will want to determine whether the
> benefits outweigh the effort.  There are several things that I
> cannot do: translations for gui additions being one of them,
> testing on windows and mac being another.  I can offer to keep
> rolling updates and fixes from "testing" into the newer branch.
> I am a good tech writer too and can update documentation in
> English.  Then at some point you must of course decide whether
> to switch to the newer branch or abandon it.
>
> How does that sound?
>   

With bazaar I believe you can push your work into your own published
branch under the Kicad umbrella.  It is something you can do at your
convenience, and to the potential benefit of those that are curious and
might eventually help you get it merged into testing.

Thanks much for your involvement.

Dick