kicad-developers team mailing list archive

[Dick Hollenbeck <dick@...>]

Hi c w,

Thank you very much for volunteering! c w what is your real name?

I went to find the document and pulled it up into OpenOffice and see 
that it is 25 pages long, and there are quite a few pages in there that 
are simply not pertinent to Kicad.

So I have modified my opinion slightly in the direction of Wayne's 
comments. This document was written about 10 minutes after C++ hit the 
market, so that makes it about 20 years old, and in those days we were 
over designing everything, including this document.

Maybe give me a week to whittle it down and then I will email it to you 
to touch up.

OK with you?

Dick



> Since no one else has stepped up, I'll take a stab at it. I just 
> installed Open Office on one of my systems and as long as I can ask 
> questions when needed I'll do my best.
>
> --- On *Wed, 5/28/08, Dick Hollenbeck /<dick@...>/* wrote:
>
> From: Dick Hollenbeck <dick@...>
> Subject: Re: [kicad-devel] Re: Interested new developer
> To: kicad-devel@xxxxxxxxxxxxxxx
> Date: Wednesday, May 28, 2008, 8:51 PM
>
>
> > Dick,
> >
> > I took looked at the coding standards document you sent me a
> while back.
> > It is an excellent document. It was a lot more detailed than what I
> > was thinking. I was envisioning something along the lines of the
> Linux
> > kernel coding standards document. More anecdotal and less
> detailed. I
> > have had my free cut significantly due to some additional
> consulting
> > work. Maybe some of the other developers would like to take a
> stab at it.
> >
> > Wayne
> >
> >
>
> Wayne,
>
> Good luck with the consulting, hopefully it pays better that
> working on
> Kicad.
>
> The extra detail in the document is harmless, and probably serves C++
> and why and how it should be used over C in an application like Kicad.
>
> It also speaks consistently about style with respect to the style
> embedded in uncrustify.cfg file.
>
> Thanks for at least letting us know you are un-volunteering on it. We
> will not wait for you now.
>
> Mostly we need someone that:
>
> 1) knows C++,
> 2) knows OpenOffice Writer,
> 3) knows English well
>
> to step up. They are listed in order of importance, with 3) being the
> most important. The result could be a *.odt file that we occasionally
> export to *.pdf and put on the wiki. It is now about a 15 page
> document
> if I recall, and it needs some formatting mostly. It was imported
> from
> WordPerfect and not so nicely at that, and seriously modified
> since then.
>
> Thanks,
>
> Dick