The horizon core reviewer team is responsible for many aspects of the horizon project. These include, but are not limited to:
In essence, core reviewers share the following common ideals:
Members of the core reviewer team are expected to:
[horizon]
discussions on the mailing listPlease note in-person attendance at PTGs, mid-cycles, and other code sprints is not a requirement to be a core reviewer. Participation can also include contributing to the design documents discussed at the design sessions.
Active and consistent review of review activity, bug triage and other activity will be performed periodically and fed back to the core reviewer team so everyone knows how things are progressing.
While everyone is encouraged to review changes, members of the core reviewer team have the ability to +2/-2 and +A changes to these repositories. This is an extra level of responsibility not to be taken lightly. Correctly merging code requires not only understanding the code itself, but also how the code affects things like documentation, testing, upgrade impacts and interactions with other projects. It also means you pay attention to release milestones and understand if a patch you are merging is marked for the release, especially critical during the feature freeze.
GUI supports for most OpenStack projects are achieved via horizon plugins. The horizon core reviewer team has responsibility to help horizon plugin teams from the perspective of horizon related changes as the framework, for example, Django version bump, testing improvements, plugin interface changes in horizon and so on. A member of the team is expected to send and review patches related to such changes.
Note that involvements in more works in horizon plugins are up to individuals but it would be nice to be involved if you have time :)
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.