kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxxxx>]

On 5/10/2010 3:58 PM, Dick Hollenbeck wrote:
> Wayne Stambaugh wrote:
>> On 5/10/2010 10:31 AM, Dick Hollenbeck wrote:
>>  
>>> Wayne Stambaugh wrote:
>>>    
>>>> On 5/9/2010 11:32 PM, Dick Hollenbeck wrote:
>>>>  
>>>>      
>>>>> jp.charras@xxxxxxxxxx wrote:
>>>>>           
>>>>>> Dick Hollenbeck a écrit :
>>>>>>               
>>>>>>> Alain Portal wrote:
>>>>>>>                     
>>>> <<< snipped >>>
>>>>
>>>>  
>>>>      
>>>>> My opinion:

<<< snipped >>>

>>>>>

> I think we need to start from the perspective that quality talent like
> yours is valuable and should not be taken for granted, not disrespected,
> and not ignored.  So the tail should not wag the dog.
> 
> Having said that, give a lot of thought to low risk ways to introduce a
> new format.  I might suggest using a text editor and a blueprint and
> mail messages.  I would get the format accepted first before you code to
> support it.  Build the format with a text editor, and some concrete
> manually converted examples.

I don't want to change the scope of this thread but this is already in
process.  I am about a third of the way complete on the preliminary
documentation.  I am using OpenOffice writer for the documentation since
all of our existing file format documentation is in odt format.  I'm
using a monospace font for the examples.  It's taking a bit more effort
than I anticipated (doesn't it always?) so it will be while before I
submit a blueprint.

> 
> 
> Then after getting it accepted and coded, simply ask that the new code
> be tested, because by then we will know it is going into the project, no
> question, (you got acceptance earlier on the format).  Therefore it is
> to everyone's benefit to work out the bugs earlier than later.  I would
> like to assume that your tool for migrating old files to new format
> should preserve the original files, so that if a tester finds a bug,
> they are not left in limbo.  They can have an older 2nd Kicad version
> installed to get useful work done if you go off on vacation for a week
> before a bug is fixed..
> 
> You voiced a concern, but I think if you get all the lower level pieces
> in place first, the upper level ones will be well supported with minimal
> risk regarding wasted effort.
> 
> Have you gotten any feedback on the new format?

I am using input from the very long discussion about the new libraries
and library file format that occurred last year on the dev list as a
guideline for the new format.  I think I can cover most of the issues
discussed cleanly as well as some ideas that I have which should prove
useful.

> 
>>   This defeats your feedback analogy because the larger
>> pool of developers is not testing all of the new code in individual
>> branches that would have been tested in SVN head.  I'm not trying to
>> belabor the point here.  I want to be sure I'm not heading down one path
>> and everyone else is going down another.  I'm only trying to avoid
>> having to do things over because I misinterpreted something.
>>   
> 
> Once you get approval on the new format, I say you are the dog, the rest
> of us are the tail, WRT to that enhancement.  Until then, put on your
> salesman's hat and I will be your sales assistant and understudy.   Will
> everyone endorse a new format?  Probably not.  But if it solves a number
> of problems immediately, and offers a simpler way to solve future
> problems than what we have, then I think the majority of those capable
> of formulating an informed opinion will support it.

I will create a Launchpad blueprint when I finish the file format
documentation and we can hash out any concerns then.  Can you add an
attachment to a blueprint?  If not, I will upload the odt file to the
Kicad wiki an add a link to the blueprint.  A quick note to everyone,
please refrain from commenting on the new component library file format
until I submit the blueprint.  We beat this horse death already and
we'll have plenty of opportunity to beat it again after I submit the
preliminary documentation.

> 
> 
> 
> Everything I've had to say today has been in the interest of
> streamlining and simplifying the lives of Jean-Pierre and you.  If any
> one thinks differently, then please go back and read carefully, and
> identify where I am being unclear.
> 
> 
> Remember, the software is free.  If anyone wants to object to the way
> you contribute your valuable time, you can always offer to give them
> their money back, even offer to payback 110 percent.

If they don't like it, they can cut my Kicad development pay in half ;).

Wayne

> 
> 
> Dick
> 
>> Wayne
>>
>>   
> 
>