Re: [Corelinux-public] Doc standard

[Rik H. <ri...@kd...>]

#if Frank V. Castellucci
> Unless I see otherwise I will assume you have all the "leads" to
> Patterns/OOA/OOD material you need.

I've decided to buy the 'Design Patterns' book as I get paid for my
last contract next week :) From what I've heard it seems like the
logical thing for me to read next.

> As far as the web graphics, a CoreLinux++ logo would be cool. And anyway you
> think the pages should go, the Source Forge system supports PHP (which I
> know nothing about) if that helps.

Ok, I too know nothing about PHP, but designing a logo will give me
something to do over the weekend. First things first, eh ? ;)

> So far Thomas Maguire has asked to be assigned to the project in Source
> Forge. I don't know if some of you are still testing the water or want
> access as a project team member. Clearly there is nothing to modify yet, and
> I am not overwhelmed with maintaining the changes at the speed they are
> coming in at, but there will come a point in time...

Just to let you know, I've had a fair bit of experience with GNU autoconf,
automake and libtool (further: acamel). I don't know if a decision about the
build structure has been made, but if people feel an 'acamel' based system
would be a plus then I'd be happy to 'acamel-ify' the sources and do
my best to maintain etc.

Cheers,
Rik

p.s. sorry about my abbreviation 'acamel' but how else do you say
'automake/autoconf/libtool-ify' twice in one sentence without getting
tongue-tied ?