Difference between revisions of "UX/Design"
< UX
(→Process) |
(→Process) |
||
| Line 27: | Line 27: | ||
## Community members are invited to leave feedback by add a +/- 1. | ## Community members are invited to leave feedback by add a +/- 1. | ||
# Also, cores cannot +/- 2 their own projects. | # Also, cores cannot +/- 2 their own projects. | ||
| − | |||
| − | |||
Revision as of 18:12, 26 August 2015
This is an overview of the core approval process for UI Designs.
Contents
Overview
UI designs will be posted for review in the Invision review tool for no less than one week to solicit comments from the overall OpenStack community. It also best practice to post a link to the project in the various IRC communities including the following:
Core Reviewers
Core reviewers are selected based on the quality and frequency of their contributions to the Invision OpenStack community. In addition, we will also try to have some diversity in terms of roles, ie operators, developers, designers, researchers, etc.
Cores
- David Lyle (david-lyle)
- Travis Tripp (TravT)
- Rob Cresswell (robcresswell)
- Timur (tsufliev)
- Piet Kruithof (piet)
- Eric Peterson (ducttuape)
- Matt Borland (matt-borland)
- Kevin Fox (kfox1111)
- Thai Tran (tqtran)
- Ju Lim (julim)
Process
- Mocks are loaded into Invision as a project
- Community members are given no less than one week to comment on a design before cores are able to vote.
- Only cores can +/- 2 a project
- Invision projects will require at least two +2 votes to be accepted. Any projects that receive a -2 from a core will not be accepted.
- Community members are invited to leave feedback by add a +/- 1.
- Also, cores cannot +/- 2 their own projects.
