-
Notifications
You must be signed in to change notification settings - Fork 97
Community Roles
#Roles in the BUILD Open Source Community
This document identifies the Committers and Reviewers nominated for each BUILD module, and describes all the roles in the BUILD open source community. It contains the following sections:
-
Who are the Reviewers and Committers of BUILD Modules?
-
Who Contributes to BUILD Modules?">Who Contributes to BUILD Modules?
##Who are the Reviewers and Committers of BUILD Modules?"
The table below identifies key personnel in the core development teams for each BUILD module.
Note: You can highlight issues you create in the Issue Tracker for the attention of a specific person by adding # and the relevant GitHub user name / identifier to the title of the issue. GitHub usernames are displayed in parentheses in the table below. If you do not identify a specific user, your issue is assigned to the most appropriate member of the team.
##Who Contributes to BUILD Modules?"
The BUILD Open Source community comprises the following roles:
- Users
- Contributors
- Committers
- Reviewers
- Project and Sub-Project Steering Committee Members
###Users
Without our users, BUILD has no business purpose, and therefore their satisfaction is our goal. However, users' experience of creating apps for their businesses using BUILD is also an invaluable source of user information for the BUILD open source community. In addition, users police the work of open source community contributors by logging bug requests when they notice something isn't working as it should. Most current contributors are users who saw something in BUILD that they wanted to be involved with, and started contributing.
###Contributors
Describe contributor's roles and rights. Describe how they can become Committers (or who they can become)
Describe development desirable skill levels (with suggestions for where they might be useful). The Apache approach is to point beginners to areas where the can begin working straight away, without have to learn much in advance, but also to make sure that the don't change anything that impacts an expert contributor negatively.
You can find out more about our current reviewers and contributors on the [Contributors] (https://github.wdf.sap.corp/Norman/Drive/blob/master/Contributors.md) page.
###Reviewers
In general, the reviewer(s) on a team is responsible for ensuring all code and documentation submissions to BUILD modules meet the agreed requirements in terms of scope, code-quality, and functionality. Reviewers are generally experts in the environment to which the contribution applies, and are also Committers.The number of reviewers per project varies with the size of the project and the number of contribution.
On a daily basis, reviewers are responsible for:
-
Monitoring the Pull Request tab and reviewing all pull requests to ensure the code submitted conforms to the BUILD coding guidelines and test requirements. In addition, in the case of bug fixes reviewers must ensure that the code is required solution in the up-to-date code base. In the case of new features or enhancements, the reviewer must ensure that it works according to agreed specifications. The review must also provide a timely reponse to the submitter.
-
Monitoring the Issue Tracker and triage incoming issues to ensure correct categorization and prioritization.
Note: In order to optimize the chances for your submissions to pass the review stage, we recommend you review BUILD Style Guide.
Note: You can find identify current reviewers on each sub-project here.
###Committers
Committers are responsible for committing changes submitted by pull request and passed by a reviewer.
Established contributors in a project can be enabled as reviewers for that project if they receive the support of the project steering committee. It can be useful to be a committer. For example, providing support for BUILD to a customer, being a committer could be a big selling point of their skills for the customer.
Note: You can find identify current committers on each sub-project here.
###BUILD Module Steering Committee Members
Each module of BUILD should run on day to day basis by the contributors, and operates under the guidance of the of the steering committee for that module. Module steering committees are responsible for providing oversight of sub-project developments, securing and organizing resources, removing obstacles, and resolving conflicts.
Each module steering committee, in turn, operates under the guidance of the BUILD Steering Committee, which is responsible for providing overall guidance and leadership for BUILD. This leadership involves vetting individual proposals from projects for architecture and resourcing, to ensure to ensure consistency of the architecture and balancing of effort, and reviewing progress and proposals on an on-going basis.
Each BUILD module Steering Committee comprises the following:
-
A Requirements lead - The Requirements lead is responsible for gathering requirement for discussion with the other members of the SC for inclusion in an agreed release scope, that agreed contributions are delivered. They are also responsible for building a vibrant community. This role may suit, for example, the Product Owner.
-
A Project Management lead - The project management lead is responsible for the following:
-
Ensure visibility and communication across the team and overall sub-project, and communicating project status to stakeholders and the team through various means, such as weekly status reports, quality reports, iteration reviews, project meetings and so forth.
-
Ensuring team is aware of the sub-project schedule and milestones and is executing towards it. This requires the following:
-
Capacity/ Availability planning for the sub-project.
-
Supporting the teams in their iteration planning.
-
Developing an appropriately detailed project plan to monitor and track progress. For long term sub-projects this includes a Release Plan.
-
-
Managing Risk/Impediments/Dependencies.
- Identify, monitor, communicate, resolve, escalate.
-
Ensuring continuous improvement of the sub-project.
-
-
A Technical lead - an expert in the technical aspects of the project. This role may suit, for example, an architect or a senior developer.
Note: You can find identify current sub-project steering committee members here.
###BUILD Steering Committee
The BUILD Steering Committee comprises the following members:
-
Requirements/Scope Lead - the requirements lead is responsible for liaising with the sub-project requirements leads to ensure that all agreed requirements are gathered. The requirements lead is responsible for monitoring the progress of sub-projects requirements on a release-by-release basis.
-
Project Execution/Management Lead - The project execution/management lead is responsible for the following:
-
Ensuring visibility and communication across the team and overall BUILD project, and communicating project status to stakeholders and the team through various means, such as weekly status reports, quality reports, iteration reviews, project meetings and so forth.
-
Ensuring team is aware of the BUILD schedule and milestones and is executing towards it. This requires the following:
-
Capacity/ Availability planning for the overall BUILD project.
-
Supporting the teams in their iteration planning and ensure coordination between teams.
-
Developing an appropriately detailed Release plan for the overall BUILD project to monitor and track progress.
-
-
Managing Risk/Impediments/Dependencies.
- Identify, monitor, communicate, resolve, escalate.
-
Ensuring continuous improvement of the overall BUILD project.
-
-
Architectural/Technical lead - an expert in the technical aspects of the project. This role may suit, for example, an architect or a senior developer.
-
Engagement Lead/Community representative - responsible for marketing this project, reaching out to external/internal consumers, enroll more contributors to the project etc.
-
BUILD Steering Committee Lead - the BUILD Steering Committee Lead is responsible for leading this project in terms of the project structure.