RE: Discussion on SCOPE -> CGL process

[glenn.seiler@xxxxxxxxxxxxx (Seiler, Glenn)]

Does anyone have comments on the process below?
A quick reminder what we agreed on was to send this plus the flow chart
to SCOPE CGOS on Jan 22 and then have a call on Jan 24.
 
I'll be setting up the call later this week.
 
regards,
-glenn

________________________________

From: Seiler, Glenn 
Sent: Wednesday, January 16, 2008 1:00 PM
To: lf_carrier@xxxxxxxxxxxxxxxxxxxx
Cc: 'Dan Kohn'
Subject: Discussion on SCOPE -> CGL process


I wanted to document the discussion we had yesterday regarding how SCOPE
can get feedback from LF and the community prior to publishing their
gaps.
 
0)  SCOPE Alliance; Scope Alliance submits small numbers of gaps (1-3
typically) to their CGOS committee. It is anticipated these 'groups' of
gaps will be submitted by a single company.
1) SCOPE Alliance;  SCOPE will go through their approval process to
ensure that the gaps represent the overall Telecom community are not
just a single companies 'wish list'.
2) SCOPE Alliance; Once they are official SCOPE gaps, they will be
submitted to the Carrier Grade Linux Workgroup (CGL WG) in Linux
Foundation.
 
3) CGL WG; the CGL team will do any filtering, initial clarifications,
etc and then post to Wiki page on the LF site. 
4) CGL WG; the CGL team will submit an email request to LF exec team
(Jim, Markus, Dan, etc) as well others TBD (Jonathan Corbett??)
requesting review and input on these gaps.
 
5) Linux Foundation/Community (LF);  LF will help get input from LF
Technical board, Jonathan or others on the gaps. This input may include
such things if open source projects already exist that are addressing
the gaps, or if there are alternative projects or alternative solutions.
Responses may require more clarification from the original SCOPE
submitters
 
6) LF; LF will submit any responses, or requests for clarification back
to the CGL WG;
7) CGL WG; CGL will broker and filter responses or requests for
information back to SCOPE CGOS or the original company submitter as
necessary and appropriate
 
8) CGL and SCOPE; will meet regularly to discuss the status of gaps, any
next steps, etc. Once general consensus is achieved that the community
has been involved and gap is valid it will be added to the GAPs document
of the CGL spec. Or, the alternatives or existing open source projects
may satisfy the gap. In that case the GAP will be added to the existing
solutions document of the CGL spec.
 
9) CGL; CGL team will give updates back to LF and the community to keep
good flow of status and information - close the loop.
 
 
Glenn Seiler, Director Linux Strategic Initiatives, Wind River
direct +1.510.749.2122  mobile +1.831.334.4108
fax +1.510.749.2695
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/lf_carrier/attachments/20080122/bb039d4c/attachment.htm