CGL5 relevant documentation

[joe@xxxxxxxxxxxx (Joe MacDonald)]

Hi Florian,

On Wed, Jan 25, 2012 at 3:09 PM, Florian Heigl <florian.heigl at gmail.com>wrote:

> Hi,
>
> I wanted to ask if there are any other documents applying to the
> CGL5.0 spec than
>
> CGL_5.0_Specification.pdf
> CGL_5.0_Registration_Template.xls
>
> AlpineLinux (a quite telco-like oss distro) is currently weeding out
> the kernel modules they deliver per default.
> I suggested we go through the CGL spec for a baseline since that way
> we have nice xls / pdf list to tick off.
> A few items from the signaling world that a real CGL distro would
> include will of course be overkill, still I think CGL is the best way
> to define a stable base for a kernel :)
>
> I just remember there was more different spec files during the 3.0
> time. Will the above files do as a good starting point?
> Anything else you recommend?


While you can have a look at the older documents, our objective in creating
the CGL 5.0 specification was to simplify the spec as much as possible.
 That's why there's only one "book" now, whereas in earlier versions there
were a number of documents you had to collect together to get the whole
picture, so to speak.  One of the things you may find valuable in looking
at the older versions of the spec, if your objective is to pare things
down, would be looking at the requirements in the 5.0 spec marked
"deprecated" or the like.  Most of those were deprecated because the CGL
workgroup considered them now so commonplace they're not even worth calling
out as requirements anymore.

That's my initial advice.  The other advice I have is continuing with what
you're already doing, investigating and discussing strategies and
objectives here (or elsewhere in the community).  I hope that helps and
please feel free to send questions or comments to the list.  We're always
happy to have this type of discussion.

-- 
Joe MacDonald
:wq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lf_carrier/attachments/20120125/0ba0a943/attachment.html>