LCOO Working Group - Year 2 Approach

1. Hold monthly Topic focused meetings:
   • Member companies come prepared to present information (initatives, challenges, priorities, successes, opportunities, etc) on the topic. All (willing) members would take turns presenting on the topic.
   • Each meeting is dedicated to a single topic of interest (For ex, month 1 is Edge, month 2 security, etc.)
   • Allow time within each presentation for questions.
   • Allow time at the end for general discussion.
   • Any follow-up/collaboration should emerge organically among the participants out of a recognized opportunity for mutual benefit. There would not be an expectation of follow-up/collaboration.
   • Possible outcomes include formation of SIG's, new projects, simple relationship building, etc., or nothing.
   • Follow-up meetings would be planned and conducted on the side, ad hoc and by the interested parties for as long as needed until the course is run. The monthly topical meeting schedule and cadence would not change.
2. On the alternate weeks the lcoo coordinators (our current regular attendees) from each member will meet to:
   • Review and prioritize topic proposals.
   • Engage key contacts from member companies and secure commitments to present/participate.
   • Publish topics far enough in advance to allow members to draw in the key people to present & discuss for that subject.
   • Plan the topical session schedule & meeting logistics:
     1. Prepare & publish specific agendas.
     2. Coordinate general meeting logistics like conference bridges, etc.
     3. Prepare and distribute promotional information about upcoming topical sessions.
     4. Capture, share and maintain key artifacts, contacts and learnings by topic in the wiki. For example, maintain organized copies of each presentation, an index of key contacts, meeting minutes, etc.).
     5. Host/Facilitate the meetings (perhaps a rotating responsibility?) .
     6. During the meeting watch for synergies. Where they emerge, assist the interested parties in organizing and conducting any desire follow-up, tool needs like the LCOO wiki, Jira, Slack, etc. Serve as "community guides" helping orient any newbies to community culture and functional norms.
   • Get updates on any collaborations which may be underway (in their own side meetings).
   • Maintain LCOO tools like our Confluence Wiki and Jira. Arrange for and assist any collaborations underway in their use.
   • Coordinate LCOO engagement at Community Events.
   • Share info/awareness about upcoming community events, what's happening in other working groups, or anything else that may be happening in the community and of interest.
   • Generally drive the bus and keep it running down the road.
3. Hold Quarterly Stakeholder review meetings where the most promising items from each monthly meeting are brought to the Stakeholders for further action/commitment.

Some related subjects needing discussion/decisions:

• Length of meetings, logistics (ex.Skype vs. WebEx vs. Zoom?) 
  • an hour or 1.5hr would be ideal Shintaro Mizuno (Unlicensed)
  • Skype does not work for me because of the China Great Firewall, Zoom should be OK and there is zoom client for my linux laptop, it's my best choice,   Yaguo Zhou (Unlicensed)
• A standard Agenda structure/timing 
  • we can create agenda discussion page on confluence and propose topics there and discuss at the coordination meeting. Shintaro Mizuno (Unlicensed)
• Marketing of the Topical sessions? 
• Should this be a means to do new member recruiting? Who to target? If so, how? 
  • If any company has vendors or other operators who are already working on a proposed agenda item, they can invite their partners to the meeting to create a wider team for the topic. Shintaro Mizuno (Unlicensed)
• Do we need to revise our Charter? Wiki page? If so how?
  
  • Jamey McCabe volunteering to start this as a Wikipage here so input can be added by all. Finalize by 10/12 LCOO session.
• How do we overall reinvent ourselves into LCOO 2.0?  Use Sydney to promote?
  • We can use Sydney WG session if we can have one.
• How do we relate to SIGs?
  • Once the topic is agreed, we can create a SIG to attract wider members (including devs/ops) from the community. Shintaro Mizuno (Unlicensed)