Akraino Sub-Committees

Slides:



Advertisements
Similar presentations
NATIONAL AERONAUTICS AND SPACE ADMINISTRATION 1 NASA Earth Science Data Systems (ESDS) Software Reuse Working Group CEOS WIGSS-22 Annapolis, MD September.
Advertisements

<<replace with Customer Logo>>
Doc.: IEEE /024 Submission January 2001 Jim Carlo, Texas InstrumentsSlide 1 Patents and IEEE 802 Stds IEEE 802 Chair’s Viewpoint Jim Carlo General.
1 LBNL Enterprise Computing (EC) January 2003 LBNL Enterprise Computing.
NH Department of Education NH Department of Education Developing the School Improvement Plan April 15, 2011 Referencing requirements for Schools in Need.
The R&M Task Group mandate is to: Develop specific recommendations on how social housing project reporting and monitoring could be improved and made more.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Web Development Process Description
Software Engineering Modern Approaches
1 Collaborative Provision and External Examining Nicola Clarke Centre for Academic Standards and Quality Enhancement (CASQE)
Library Services CDRS Requirements Report February 9, 2001.
Peggy McCoey, M.S. (215)
Networking the World TM IEEE: Networking the World.
Health eDecisions Use Case 2: CDS Guidance Service Strawman of Core Concepts Use Case 2 1.
ARIP Technical Committee Convener Call 07 April
CTI Technical Committee Convener Call 11 May
ARIP Technical Committee Convener Call 07 April
PROMCODE Technical Committee Convener Call 14 February
IEEE MEDIA INDEPENDENT HANDOVER DCN: mugm Title: Group Management TG Opening Note Date Submitted: September 18, 2012 Presented at.
Terms of reference Classification: Internal.
State of Georgia Release Management Training
OData Technical Committee Convener Call June 5, 2012.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
ESSRT In-Process Review September 10, Agenda 1.Work Completed Till Date 2.Scope of future activities and deliverables 2.
CABLING SYSTEM WARRANTY REGISTRATION. PURPOSE OF CABLING REGISTRATION.
How to Access and Redeem Cisco Certification Exam Discount Vouchers Step-by-Step Guide August 2013.
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
Lab Results Interfaces S&I Framework Initiative Bi-Weekly Initiative Meeting July 18, 2011.
Developers Users Committers How do I configure this now? Just one more fix and I am done! CVS Download/Use Software Submit problems/ request features Store.
PACR Technical Committee Convener Call 09 January /9/131.
Sample Fit-Gap Kick-off
Rapid Launch Workshop ©CC BY-SA.
North Carolina Council on Developmental Disabilities
What We Need to Launch Community Buy-in Web Page in Place
Tina Tsou, Bryan Sullivan,
Open-O Project Proposal Template
How to Access and Redeem Cisco Certification Exam Discount Vouchers Step-by-Step Guide August 2013.
ISA 201 Intermediate Information Systems Acquisition
Project Management Lifecycle Phases
TechStambha PMP Certification Training
Implementation Strategy July 2002
Description of Revision
ONAP Security Sub-committee Update
Standards and Certification Training
Engineering Processes
Group Projects Pre-Project Kickoff
Simplified Development Toolkit
Health Ingenuity Exchange - HingX
Change Control Process
Health Ingenuity Exchange - HingX
INFORMATION TECHNOLOGY NEW USER ORIENTATION
1 Stadium Company Network. The Stadium Company Project Is a sports facility management company that manages a stadium. Stadium Company needs to upgrade.
Employee engagement Close out presentation
Governance, Intellectual Property and Membership
Global Grants Breakout
MODULE B - PROCESS SUBMODULES B1. Organizational Structure
IEEE MEDIA INDEPENDENT HANDOVER DCN: mugm
Recruitment & Selection Process For Talent Acquisition
North Carolina Council on Developmental Disabilities
Portfolio, Programme and Project
DSC Governance Sub Group Recommendations
Engineering Processes
Executive Project Kickoff
ESHAC #8 Safety Readiness Review Thomas Hansson, ESH
{Project Name} Organizational Chart, Roles and Responsibilities
Akraino R2 inputs, goals, & Planning
Project Name Here Kick-off Date
NMDWS Internship Portal
Fundamental Science Practices (FSP) of the U.S. Geological Survey
Presentation transcript:

Akraino Sub-Committees These TSC Sub-Committees have been established to provide expert guidance in technical subject areas Sub-Committee Chair Accomplishments Next Steps Process, Project review and recommend, documentation Jim Einarsson Jim Einarsson elected as chair on 11/14 Established credentials to book meetings. Blueprint templates have been finalized and saved to the web site. Scheduling a meeting Thursday or Friday to review blueprint and project proposals prior to F2F meeting. Community Tapio Tallgren Tapio Tallgren elected as chair on 11/26 Upstream Wenjing Chu Wenjing Chu elected as chair on 11/14 Review blueprint and project proposals prior to F2F meeting to identify upstream communities that could be in-scope for release 1. CI & Blueprint Verification Lab Cesar Berho Cesar Berho elected as chair on 11/13 Re-named sub-committee to ‘Blueprint Validation Lab, documentation sub-committee’ Review and update Akraino Lab IT Requirements for 2019 Budget Documentation TBD Tina sent a follow up request for participation on 11/27 Security Kickoff scheduled for 12/3 API Kickoff to be scheduled after the TSC F2F meeting

Akraino Blueprint Proposals In addition to the blueprint and project proposals that have been posted to the Akraino wiki, the TSC will need to consider the following when reviewing each proposal: When requesting the creation or modification of an Akraino Blueprint, requestors should demonstrate the following aspects to the TSC: The TSC will need to conduct an incubation review to officially launch the project and to support its needs until project Termination Review. The following artifacts are expected: Criteria Each initial blueprint is encouraged to take on at least two Committers from different companies Complete all templates outlined in this document A lab with exact configuration required by the blueprint to connect with Akraino CI and demonstrate CD. User should demonstrate either an existing lab or the funding and commitment to build the needed configuration. Blueprint is aligned with the Akriano Edge Stack Charter Blueprint code that will be developed and used with Akraino repository should use only Open Source software components either from upstream or Akriano projects. For new blueprints submission, the submitter should review existing blueprints and ensure it is not a duplicate blueprint and explain how the submission differs . The functional fit of an existing blueprint for a use case does not prevent an additional blueprint being submitted. Criteria Name of the project is appropriate (no trademark issues etc.); Proposed repository name is all lower-case without any special characters Project contact name, company and email are defined and documented Description of the project goal and its purpose are defined Scope and project plan are well defined Resources committed and available Contributors identified Initial list of committers identified (elected/proposed by initial contributors) Meets Akraino TSC Policies Proposal has been socialized with potentially interested or affected projects and/or parties Cross Project Dependencies (XPDs). In the case where a project will require changes in other projects, those projects are listed in the proposal, and a sponsoring developer in the project has been identified Tools have been identified and discussed with relevant partners (Linux Foundation, IT). Once the project passes the review, the tools chain must be created within one week. Tools encompass Configuration Management, CI/CD, Code Review, Testing, Team Wiki, End Users documentation (not exhaustive)