2016-12-14 RackHD Architecture Forum Meeting notes

Owned by Former user (Deleted)
Last updated: Dec 20, 2016
3 min read

Date

Attendees

Goals

  • Kickoff meeting for the RackHD Architecture Forum
  • Set expectations

Proposed Agenda

  • Logistics
    • Video or WebEx?
    • Collaboration
      • Meetings – weekly cadence for now, possibly switch to bi-weekly later
      • Slack channel – private, invite only, for now
        • Former user (Deleted): slack conversations are not condusive to SH folks, not easy to slackify information
      • RackHD Confluence – public viewable, controlled editing
      • Use of email – discuss pros/cons
        • Former user (Deleted): agree that email can be a detriment, lose history, using slack, confluence you have history of conversations, use for attachments to send to folks, threading is very important on certain topics, threading should be coming to slack "soon". 
        • Former user (Deleted): number of channels for collaboration, limit channels (email being one of the channels), limit to deliberate uses for specific reasons, Rod F asked Jonas and he said early next year (2017)
        • Former user (Deleted): slack conversations are not condusive to SH folks, not easy to slackify information h
        • Former user (Deleted): good for very focused discussions, going back and finding info (lack of threading), direct messaging via slack, Arch forum channel,
        • Former user (Deleted): do we need include google groups
        • Former user (Deleted): AI create email DL for this forum, Former user (Deleted): can give me the SMI DL smi@dell.com
      • Participation is key to success
  • Meeting agendas, meeting notes
  • Townhall readouts
    • Tim Larson: thinks this is a great idea, ensure we "pop the  bubble", no fetch the rock or guess what I'm thinking
    • Former user (Deleted): make sure dev managers are talking with their teams
    • Former user (Deleted): make sure all team members are kept in the loop, townhall readout gives everyone message at the same time
  • Mission/Vision/Goals – open discussion on how to stay focused
    • Former user (Deleted): thinks it is very important to have a mission/statement, what is rackhd and what do we see going forward
    • Tim Larson: interesting how mission statements evolve, Medtronic never changed over years, RackHD has evolved numerous times, we have to make sure the right attributes get communicated in the statement, could be different depending on the lens we put on it. Is it an open community mission/vision, or a Dell EMC mission/vision
    • Former user (Deleted): strongly agree with use of mission/vision, Microsoft "computer on every desk", hard to articulate mission/vision for RackHD as a whole, particularly useful for our Dell friends that don't have the ability to look back at RackHD for 2-3 years – what are we trying to accomplish and how are we making sure we are putting this group of people to good use
    • Tim Larson: may need different statements for different contexts, should be part of launching new RackHD next year
    • Former user (Deleted): think it is important, open source community understanding what the RackHD project is all about – what's the point – now that it is part of Dell EMC, agrees a statement in the open community can help launch this better. Tim Larson: recalls the beginning days when John Roese asked us to undertake this open source thing without knowing much about what it meant to open source a project. Mission/Vision provides clarity.
  • Scope of ecosystem - now and future
    • Reference PPT deck under "Historical" section 
    • Inclusion of  Advanced PE Services
  • Review DevCon whiteboard notes – refresher on where we left off
  • Deliverables – expectations on deliverables
  • First deliverable – updated architecture diagram including entire ecosystem
  • Action item review, next meeting agenda

Action items