Jump to: navigation, search


< UX
Revision as of 20:50, 2 March 2016 by Piet Kruithof (talk | contribs) (Cores)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This is an overview of the core approval process for UI Designs.


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:

  • #openstack-horizon
  • #openstack-mistral
  • #openstack-operators
  • #openstack-ux
  • #murano

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.


  • David Lyle (david-lyle)
  • Eric Peterson (ducttape)
  • Ju Lim (julim)
  • Matt Borland (matt-borland)
  • Michael Hinnant (hinnant)
  • Piet Kruithof (piet)
  • Rob Cresswell (robcresswell)
  • Thai Tran (tqtran)
  • Timur Sufiev (tsufiev)
  • Travis Tripp (TravT)
  • Diana Whitten (hurgleburgler)
  • Dan Kingshott (dank_)


  1. Mocks are loaded into Invision as a project
  2. Community members are given no less than one week to comment on a design before cores are able to vote.
  3. Only cores can +/- 2 a project
    1. 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.
    2. Community members are invited to leave feedback by add a +/- 1.
    3. Must have at +2 votes from two different companies
  4. Also, cores cannot +/- 2 their own projects.

Design Updates

There will be circumstances where a project is approved by the cores, but changes are required to the design because of challenges with implementation. In those cases, the developer is asked to reach-out to the community for feedback. This will be an informal process and not require core approval.