Most recent revision: April 1, 2020
The web deserves interoperability between component frameworks and design systems. The UI community is in a similar place as the industrial revolution prior to standardization. Untold amounts of human effort are exhausted globally every day on rebuilding identical components for web apps.
This should not be the case. The UI community should standardize namings and structures for common components. We should also standardize a way of theming these components. We should set a path for existing solutions to converge and for browsers to natively provide these things in the future.
UI component patterns have evolved and stabilized but have not made their way to to browsers or standards. Designers and developers reinvent the same components for every product they build. When building a web app or web page designers and developers should have a common set of components at their disposal. We shouldn't have to rebuild a dropdown, modal dialog, split button, or other components before we build our products.
These are the goals Open UI believes will realize the above vision.
The below process aims for efficiency and asynchronous changes but also allows for transparency and opportunities to ensure consesus from the community.
needs mergefor review by the community group and editors
Consensus on individual issues does not equate to the specification's current stage
In order to ensure transparency and that we have consensus from the community the following needs to occur for each contribution:
Upon merge or can't agree on solution to accomplish the requirements for merging a PR.
Add the label
agenda+ and be prepared to speak to it on the upcoming
telecon where your agenda item is discussed
If there is a disagreement a resolution will try to be gained on the telecon. In order to gain consensus it is the majority opinion of those on the call.
Note: Resolutions can be over-turned upon new information becoming available Note: It is helpful for efficiency to have denoted in the PR or issue the proposed options so that you can quickly cover the options and the group can discuss it and vote on it.
Being an editor of a specification is an important responsibility. You need to ensure that the specifications you're responsible for continue to make progress. Additionally you should be one of the reviewers of PRs to the specifications you are an editor of.
An editor must:
There is no additional weight to the chairs vote when making a decision that requires consensus. The chairs' primary responsibilities are:
Upon the need or desire for adding/changing co-chairs the process will be as such.