kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #01573
Re: Re: Interested new developer
-
To:
kicad-devel@xxxxxxxxxxxxxxx
-
From:
c w <panhandler13@...>
-
Date:
Fri, 30 May 2008 07:37:32 -0700 (PDT)
-
In-reply-to:
<483DFE0B.4070009@...>
-
Reply-to:
panhandler13@...
--0-90187940-1212158252=:354 Content-Type: text/plain; charset=us-ascii
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
--0-90187940-1212158252=:354 Content-Type: text/html; charset=us-ascii
<table cellspacing='0' cellpadding='0' border='0' background='none' style='font-family:arial;font-size:10pt;color:rgb(51, 51, 51);background-color:rgb(255, 255, 255);width:100%;'><tr><td valign='top' style='font: inherit;'>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.<br><br>--- On <b>Wed, 5/28/08, Dick Hollenbeck <i><dick@...></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;">From: Dick <span>Hollenbeck</span> <dick@...><br>Subject: Re: [kicad-devel] Re: Interested new developer<br>To: kicad-devel@xxxxxxxxxxxxxxx<br>Date: Wednesday, May 28, 2008, 8:51 PM<br><br><div id="yiv936897799">
<div id="ygrp-text">
<p><br>
> Dick,<br>
><br>
> I took looked at the coding standards document you sent me a while back. <br>
> It is an excellent document. It was a lot more detailed than what I <br>
> was thinking. I was envisioning something along the lines of the Linux <br>
> kernel coding standards document. More anecdotal and less detailed. I <br>
> have had my free cut significantly due to some additional consulting <br>
> work. Maybe some of the other developers would like to take a stab at it.<br>
><br>
> Wayne<br>
><br>
> <br>
<br>
Wayne,<br>
<br>
Good luck with the consulting, hopefully it pays better that working on <br>
Kicad.<br>
<br>
The extra detail in the document is harmless, and probably serves C++ <br>
and why and how it should be used over C in an application like Kicad.<br>
<br>
It also speaks consistently about style with respect to the style <br>
embedded in uncrustify.cfg file.<br>
<br>
Thanks for at least letting us know you are un-volunteering on it. We <br>
will not wait for you now.<br>
<br>
Mostly we need someone that:<br>
<br>
1) knows C++,<br>
2) knows OpenOffice Writer,<br>
3) knows English well<br>
<br>
to step up. They are listed in order of importance, with 3) being the <br>
most important. The result could be a *.odt file that we occasionally <br>
export to *.pdf and put on the wiki. It is now about a 15 page document <br>
if I recall, and it needs some formatting mostly. It was imported from <br>
WordPerfect and not so nicely at that, and seriously modified since then.<br>
<br>
Thanks,<br>
<br>
Dick<br>
<br>
</p>
</div>
</div></blockquote></td></tr></table><br>
--0-90187940-1212158252=:354--
Follow ups
References