Page Comparison

...

In general ONAP pre-requisite for committer entails responsibilities documented under

Highlighted few below below are a few responsibilities and processes which are more important from the DCAE standpoint.

Committer Responsibilities

ONAP contributors seeking promotion to committer status should demonstrate the following abilities and behaviors

Gerrit involvement - putting up reviews of their own, reviewing other reviews of contributors/committers
Proactive - do not wait to be part of a epic/story/task or wait to be part of a review, or wait to bring forward build/design issues, or wait to bring new capabilities to the project and any other members of ONAP pushing or pulling from your component
JIRA involvement - including one or more of raising, reviewing, commenting, testing, linking, attaching to, answering questions on, closing JIRAs
Design review of all the release Epics and wiki documentation for the current and pending release.
Confluence involvement - writing/editing/reviewing/answering-on wiki pages around their projects, building in general
Participation in onap-discuss work including helping with issues, raising issues
Participation in the weekly project meeting
Participation in pre-release blitzes
Integration ability - the developer should be able to bring up the entire ONAP deployment either in OOM or HEAT to be able to E2E test their particular component and any flows involving it
Support for atleast 2 release as committer role preferred
Champion an requirement/usecase end-end for a release. This requires working close with Integration team and usecase owners for documentation/delivery.
Share project progress and plan on ONAP conferences
Review Security fixes and vulnerability report and proactively address them with community

Discuss with internal management to ensure you can spend ~30% of your time for supporting DCAE committer responsibilities if approved. As the committer changes goes through several stage of approval, expectation is candidate would serve in this role for alteast 1 year or more.
Complete Make a copy of the template (Template - Committer Promotion Request for [your-project-tag] and move all/selected DCAE]: <Candidate Name>] under this page and fill the necessary fields
Notify and discuss with PTL on what items you can help
Once PTL acknowledges, poll will initiated among existing committer.committers
If majority of DCAE committers approve, then PTL request infrastructure-coordinator@onap.org and TSC for approval
Once approved by TSC
- PTL updates Resources and Repositories
- PTL/new committer approved must update all INFO.yaml for impacted repo (include Jess/LF on the gerrit change)

...

will send notice onap-tsc on committer change.
PTL will submit the INFO.yaml updates to impacted repository; once the gerrit changes are merged by other committers, it will trigger LF process for repository updates - Committer Management Automation via INFO.yaml
PTL/committer updates Resources and Repositories (Deprecated)#DataCollectionAnalyticsandEvents

...