Re: [Corelinux-public] Doc standard

[Frank V. C. <fr...@co...>]

In a previous message from Rik :

> #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.

That is one I would have recommended. Keep in mind that it slants to
development patterns. It is good to keep in mind that patterns exist
everywhere (Business, e-commerce, Chaos, etc.). I agree we need to first
focus on those patterns that will be of use to developers but I wouldn't
mind future discussions on analysis of real-world patterns that we may go
after.

> > 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 ? ;)

Great. You might want to find out if there is some form of graphic or
multi-media Open Source license that we need to use (and state) before we
put these things up.

> > 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

Even better! We will need this in a big way once we start rolling. I have
received a few flames about not having it in the current tarballs, but the
build system I included worked anyway. Another area will be binary packages
(RPM, and whatever else) for various platforms.

As far as access see my follow on post "If you want to join the team".