Thank you, Mihir, for bringing more Design presence to the Superset open source community! Both of your latest design proposals-Explore redesign and Capitalization are very valuable and they landed pretty nicely.
A few questions that come to mind How do we define whether an issue is "settled" or not? Should we utilize the voting mechanism same as SIP? If we have a different mechanism, how do we weigh opinions from committers vs. general users? How should we address future comments and concerns from people who weren't a part of the previous discussion after a guideline is settled in wiki? Do we reopen the discussion? thanks, -junlin On Tue, Jan 26, 2021 at 4:49 PM Mihir Chahuan <mi...@preset.io> wrote: > Hi everyone, > > We want to implement a new way of bringing small design proposals to the > community on an ongoing basis, for discussion, and then addition to the > wiki. The flow will be as follows, if all agree: > > 1) Design proposals will be written up as Github Issues with the > `design:proposal` tag. > 2) Design proposals will remain open for 3 days, or longer if contention > arises in the thread. In that event, a [DISCUSS] thread can be sent here on > the dev list, to draw attention/comments to the GitHub issue. > 3) When the issue settles on Github (after 3 days, by default), the result > will be added to the Wiki > <https://github.com/apache/superset/blob/master/CONTRIBUTING.md> in the > upcoming Design Guidelines section > <https://github.com/apache/superset/pull/12749>. > > These UI copy capitalization guidelines > < > https://github.com/apache/superset/blob/master/CONTRIBUTING.md#capitalization-guidelines > > > are > an example of a design guideline that can be added to the Wiki. > > Not every design proposal will result in a design guideline on the wiki, > but we wanted to establish a proposal for how things can arrive on the wiki > with due process. > > Let me know what you think! > > Thanks, > Mihir >
