Core Committer Weekly Interlock - November 15, 2016

Owned by Tim Larson
Last updated: Nov 15, 2016

Previous Meeting Notes (Core Committer Weekly Interlock - November 9, 2016) and Agenda:

  1. DevCon next week
  2. Tool Transition - Updates
  3. RackHD Branch Strategy Proposal - Updates
  4. RackHD Quality Review Board Proposal
  5. Pending Pull Requests: https://github.com/RackHD/RackHD/pulls
  6. Roundtable


Attendees:

Felix [X]

Andrew [X]

Peter [-]

Brian [X]

Ben [-]

Paul [-]

Amy [-]

Leo [X]

Tim [X]

Joe H [-]

New Agenda Items:

  1. DevCon Week
  2. Open AIs from Last Week's CC Meeting
  3. Pending Pull Requests: https://github.com/RackHD/RackHD/pulls
  4. Roundtable

Notes:

OSE DevCon 2016

 

 


Start Time:

8:00 AM


Wed - 16th

Thu - 17th

8:00 AM

Arrival

Arrival

8:30 AM

Opening, Introductions, Expectations and
Ground Rules
(All)

Agenda Review for Day 2
Success Criteria for Summit Finalized

9:00 AM

The State of the RackHD Community, Reflection, Learnings and Aspirations for OSE
(Tim Larson)

RackHD Prime Workstream Readouts, Discussion and Finalization

9:30 AM

Strengths, Weakness, Threats, Opportunities (SWOT) Exercise for RackHD
(ALL)

1) RackHD Branching/Commit Workstream

10:00 AM

 ^

2) OnRack-RackHD Migration (Docs, FIT/CIT Integration)

10:30 AM

Product Group Strategies and Plans In Depth
(Tom Capirchio - Tim Larson - Joe Golio)

3) RackHD Project Tooling

11:00 AM

^ 

4) RackHD Roadmap Messaging and Communication

11:30 AM

Current RackHD Roadmap Overview
(Tom Capirchio)

5) Review Boards (Commit, Quality, Architecture)

12:00 PM

Break for Lunch (Cafeteria)

Break for Lunch (Cafeteria)

12:30 PM

Review of Morning Content

Review of Morning Content

1:00 PM

Introduction to MicroServices and Future Architecture Vision (Amy Mullins/Brian P)

RackHD Core Committer Forum Strategy and Updates
for CY'17
(All)

1:30 PM

 ^

RackHD Futures, Investments and Roadmap Proposal
for CY'17
(All)

2:00 PM

Generic Solutions, Markets, and Use Case Evaluations and Definitions
(All)

 ^

2:30 PM

^ 

RackHD Marketing Strategy for 2017
(Tom Capirchio)

3:00 PM

Continuous Deployment as an Acumen
(Guest Speaker)

^ 

3:30 PM

^ 

RackHD Roadmap and Technology Risk Analysis and Mitigation Planning
(All)

4:00 PM

Continuous Deployment Development in Practice, Learnings and Experiences to Date
(Justin Kenney)

Recap and Close - Day 2 and the Summit
(Special Guest Attendance)

4:30 PM

^ 

 

5:00 PM

Recap and Close - Day 1


5:30 PM

 


6:00 PM

Dinner


6:30 PM

110 Grill Hopkinton


7:00 PM

1 Lumber St., Hopkinton, MA 01748


7:30 PM

508.625.2141


8:00 PM

 


8:30 PM

 


9:00 PM

 


9:30 PM

 


10:00 PM

 





  • Latest considerations on Neighborhood Manager looking heavily at also leveraging Micro-services as a strategy to resolve some current challenges with scale and also better support the amalgamation of the message bus capabilities. Expecting to cover this in detail and in depth during DevCon this week. Seeing multiple work-streams converging into a modular capability with splitting out services (HA Solutions, PE Passive Discovery, Neighborhood Manager feature evolution, RackHD Core Efficiency improvements) 
  • RackHD's origins and the Renesar roots were Monolithic and this is an evolution to improve that going forward. 
  • AI(last week): Tim Larson is the RackHD Portal ready to go live? https://panpan0000.github.io/
    • Let's review at DevCon and finalize on any edits/updates needed
    • One other item for DevCon is the layout of RackHD Atlassian Cloud and the structure of the portal and document layout
  • AI(last week): Tim Larson has here been any discussion on a migration from GitHub Issues → JIRA Tracker?
    • ThomasS's proposal is to move from GitHub Issues → JIRA Tracker - Yes - this is the current proposed plan.
    • Concerns will come up with respect to GitHub issue's inline support
    • How we will put this into operations?
    • Just shut off the tab in GitHub?
    • How do we ensure that the flow from GitHub to JIRA is streamlined?
    • GitHub Issues do get indexed in Github Issues - can we replicate that?
  • AI(last week): Tim Larson will google groups still be used?
    • ThomasS's proposal is to move from Google Groups/Docs to Confluence → Our ask/intent is to ensure that the same tooling is available internal and external WRT Dell EMC tooling. 
    • Moving Pivotal Tracker to JIRA is also in the proposal