10:00 PST will be very tough for me. I could probably do 8:00am PST. -glenn Sent by GoodLink (www.good.com) -----Original Message----- From: Dan Cauchy [mailto:dcauchy@xxxxxxxxxx] Sent: Monday, November 12, 2007 04:33 PM Pacific Standard Time To: lf_carrier@xxxxxxxxxxxxxxxxxxxx Subject: CGL Conference Call - Thurs Nov 15th 10am PST = Hi all, = I propose that we have a conference call this week to follow up on our last call (see minutes below). = Agenda: = - review progress on the 4.0 analysis (division to satisfied req.) = - review / comment on the SCOPE Gaps Document (now published) = - Discuss the plans for the Tokyo meetings = Proposed data/time: = Thursday Nov 15th - 10am PST = (Please indicate your availability for this slot. If we cannot get a core team we will consider moving it.) The SCOPE Gaps document can be found here: = http://www.scope-alliance.org/pr/SCOPE_CGOS_GAPS_PROFILE_v2.pdf = Bridge info to follow. = Thanks, Dan. = Dan Cauchy = Director of Marketing Carrier & Mobile Products = MontaVista Software http://mvista.com/ Email: dcauchy@xxxxxxxxxx = Office: +1-408-572-7918 Cell: +1-408-623-4789 -----Original Message----- From: lf_carrier-bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx [mailto:lf_carrier-bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of John Cherry Sent: Thursday, October 18, 2007 3:09 PM To: lf_carrier@xxxxxxxxxxxxxxxxxxxxxxxxxx Subject: Minutes: CGL conf call - 10/18 Attendees =3D=3D=3D=3D=3D=3D=3D=3D=3D John Cherry - LF Bruce Beare - Cisco Joe McDonald - WindRiver Tim Anderson - MontaVista Troy Hebers - HP Peter Badovinatz - IBM Dan Cauchy - MontaVista Markus Rex - LF Jim Zemlin - LF Agenda =3D=3D=3D=3D=3D=3D - 4.0 analysis (division to satisfied requirements and gaps); assignments/volunteers for each of the specs - SCOPE GCOS gaps document. Has anybody seen this yet? - Joint CGL/SCOPE meetings in Tokyo - Transition in leadership - AOB 4.0 Analysis =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Assignees/volunteers for spec analysis: Availability Troy Clustering John Hardware Joe Serviceability Tim Performance Troy Security Joe Standards Peter The objective of this review is to classify if the requirement has kernel component or not. If it has a kernel component, is it in the current kernel.org source. For application/userland components, we can do something like "maintained", "in distros" and any other note you have. Spreadsheet will be coming out soon with a good column division that we can all use for the analysis. Thanks Tim! SCOPE CGOS gaps document =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - Was supposed to be release to the CGL workgroup by now - Dan Cauchy to check on the status of the document and report back = to the team. Joint CGL/SCOPE meetings in Tokyo =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D - Leadership meeting on Wednesday to define the CGL/SCOPE relationship. - Technical meeting on Friday to discuss the SCOPE gaps document and to define CGL requirements from the gaps. - Those planning to attend (that were on the call): Dan, Tim, Peter, Glenn, Troy, Dave, Jim, Markus - Jim is Beijing on Wednesday, so Markus will probably represent LF at the leadership meeting. Transition in Leadership =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - John is not with the Linux Foundation any more. Markus Rex will be assuming responsibility for the CGL workgroup for the Linux Foundation. - John's contact info: cherrypits@xxxxxxxxx It has been a pleasure working with the Carrier Grade Linux Workgroup. I have a lot of history with this group and many good friends. I wish you all the best in your continued participation with the Linux Foundation. I believe the CGL/SCOPE relationship is key to the ongoing success of CGL workgroup and the work that can be accomplished between now and the Tokyo meetings will set the stage well. I'm in the process of exploring my options moving forward from here. Keep in touch. Cheers, John _______________________________________________ Lf_carrier mailing list Lf_carrier@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/lf_carrier _______________________________________________ Lf_carrier mailing list Lf_carrier@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/lf_carrier -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.org/pipermail/lf_carrier/attachments/200= 71112/56d7821d/attachment.htm