Re: Apache Superset Design Sync (vote on next meet up)

2019-01-02 Thread Jolly Paramjit
Thanks Eli for setting up this meeting.

We are based in india hence plz make sure timings are not very odd. Currently 
it seems 4 am which is very early.
We are ok anytime between 9 am - 11 pm IST. Hopefully you can move to any of 
such time window.
Also regarding design system we have explored separately custom design system & 
 trying using in our custom UI framework. Also we wanted similar to used by 
superset if everyone agree to it.

Looking forward for this meeting.

~Jolly
[Sent from iPhone 7. Pls excuse typos]



On 03-Jan-2019, at 1:44 AM, Eli Brumbaugh 
mailto:eli.brumba...@airbnb.com.INVALID>> 
wrote:

Hello world,

As mentioned several weeks ago in my design operating system proposal I
would like to propose a meeting date for the next Apache Superset design
sync.

After some lightweight discussion
 in
the (publically accessible) Apache Superset Slack #design channel this is
what we would like to purpose:

*Date*: Thursday, January 31st
*Time*: 3 PM - 4 PM (PST)
*How*: Google Hangouts (publically accessible/free conference software)

Potential itinerary:

  - Introductions.
  - Review each individual's design related efforts/plans (avoid
  overlap/ensure review).
  - *Matt* and *Anita* - Update on the status of the publically accessible
  Superset UI Sketch file. (Confirmed) They are kindly doing the legwork to
  rebuild what's in code.
  - *Rasmiranjan* and *Jolly* - Sharing their work on a Superset Design
  System. I've asked them to present this effort to the group. (TBD)
  - Review operating system effectiveness. What's working. What's not
  working.

If anyone has any concerns about date, time, method or topics please let
the thread know!

Best,
Eli


Apache Superset Design Sync (vote on next meet up)

2019-01-02 Thread Eli Brumbaugh
Hello world,

As mentioned several weeks ago in my design operating system proposal I
would like to propose a meeting date for the next Apache Superset design
sync.

After some lightweight discussion
 in
the (publically accessible) Apache Superset Slack #design channel this is
what we would like to purpose:

*Date*: Thursday, January 31st
*Time*: 3 PM - 4 PM (PST)
*How*: Google Hangouts (publically accessible/free conference software)

Potential itinerary:

   - Introductions.
   - Review each individual's design related efforts/plans (avoid
   overlap/ensure review).
   - *Matt* and *Anita* - Update on the status of the publically accessible
   Superset UI Sketch file. (Confirmed) They are kindly doing the legwork to
   rebuild what's in code.
   - *Rasmiranjan* and *Jolly* - Sharing their work on a Superset Design
   System. I've asked them to present this effort to the group. (TBD)
   - Review operating system effectiveness. What's working. What's not
   working.

If anyone has any concerns about date, time, method or topics please let
the thread know!

Best,
Eli


Re: Apache Superset - Design Operating System (please review, discuss and vote)

2019-01-02 Thread Eli Brumbaugh
Hi Jolly,

Thank you for your email.

That's exciting to hear you're working on a design system for Superset.

As Superset UI is decentralized the community will have to vote on what
gets added. With that said I'm excited to see what design improvements you
want to purpose adding.

Would you and Rasmiranjan be open to presenting in the next community
design sync? I'll be sending out an email today to purpose the next meeting
date.

As I mentioned to Rasmiranjan, there is a WIP effort to capture the
Superset UI (as it exists in code today) in Sketch allowing us to make it
publicly available. This seems like an opportunity for us to collaborate in
place of introducing "the" solution.

It sounds like we're all aligned on this serving the community!

I look forward to working with you both.

Best,
Eli

---

Hi Everyone,

 Intent of “Rasmiranjan” queries was that we were thinking of
introducing the “Design system” for superset. We have our own fork from
superset & we are doing lot of customisation in it, some will be generic
which we will contribute to open source & some will be specific to our
use-cases.

Having good history about design system & contact with right set of folks
is important so we can do something good which everyone can use.

Introducing design system will really help superset to be easy to customise
& theme in terms of UX.

We would like to be part of next design related discussions, it will be
helpful to everyone.

On Wed, Jan 2, 2019 at 9:37 AM jol...@gmail.com  wrote:

> Hi Everyone,
>
>  Intent of “Rasmiranjan” queries was that we were thinking of
> introducing the “Design system” for superset. We have our own fork from
> superset & we are doing lot of customisation in it, some will be generic
> which we will contribute to open source & some will be specific to our
> use-cases.
> Having good history about design system & contact with right set of folks
> is important so we can do something good which everyone can use.
> Introducing design system will really help superset to be easy to
> customise & theme in terms of UX.
>
> We would like to be part of next design related discussions, it will be
> helpful to everyone.
> --
> Thanks & Regards
> Jolly
> Handphone: +91-9971815749
>
> [We Learn, Unlearn & Re-learn.]
>
> On 2018/12/21 19:51:19, Eli Brumbaugh 
> wrote:
> > Hi All,
> >
> > I want to take a moment to disambiguate the individual contributors from
> > the companies I mentioned in my previous email. In all future
> communication
> > I will name *individuals* and *not corporations*.
> >
> > The individuals who met to discuss Apache Superset design are:
> >
> >- Matt Spiel
> >- Anita Lillie
> >- Marie Sbrocca
> >- Chris Williams
> >- Conglei Shi
> >- Krist Wongsuphasawat
> >- Eli Brumbaugh
> >
> > *Have a wonderful holiday season everyone!*
> >
> > Best,
> > Eli
> >
> >
> >
> > On Thu, Dec 20, 2018 at 6:56 PM Eli Brumbaugh 
> > wrote:
> >
> > > Hello world,
> > >
> > > Airbnb and Lyft (design) recently had a conference call to discuss
> *Superset
> > > design*.
> > >
> > > In hindsight we should have announced this meeting to the Apache
> community
> > > in advance. For that, I apologize. In the future we will ensure that
> it is
> > > both *announced in advance* and *accessible* via *freely** available*
> > > conference software such as Google Hangouts.
> > >
> > > Below I will outline the topics we covered and the proposal we would
> like
> > > to run past the community for *discussion and a vote*.
> > >
> > > *Topics:*
> > >
> > >- Superset design system alignment and strategy.
> > >- Superset design operating model.
> > >- Next steps and action items.
> > >
> > > *Superset Design Operating System (proposal to vote on)*
> > >
> > > The goal of this operating system proposal is to standardize on
> *community
> > > accessible* (design related) discussion, proposals, process and
> reviews.
> > >
> > >1. Ad hoc (*only minor*) design discussion will happen in the Apache
> > >Superset #design *community accessible* slack channel.
> > >2. Design changes to Apache Superset should be proposed through the
> *community
> > >accessible* dev@superset.incubator.apache.org email alias for a
> vote.
> > >3. Apache Superset will be designed in Sketch
> > > (unlike Photoshop, there is no
> comparable
> > >free tool). Sketch files *community accessible* (for free) through
> Sketch
> > >Cloud . Please note
> many
> > >companies use different design tools. For example we at Airbnb use
> Figma.
> > >However, Sketch and Figma are backwards compatible.
> > >4. When design changes are submitted to the Apache Superset repo
> they
> > >should be tagged with the *community accessible* 'design' tag.
> > >
> > > *Two requests:*
> > >
> > >- If anyone is designing Superset in any a tool other than Sketch or
> > >Figma please let the 

Re: design system in superset

2019-01-02 Thread Eli Brumbaugh
Hi Jolly,

Thank you for your email.

Exciting to hear you're working on a design system for Superset!

As Superset UI is decentralized please keep in mind the community will vote
on what gets added. With that said I'm excited to see what design
improvements you want to purpose adding.

Would you and Rasmiranjan be open to presenting in the next community
design sync? I'll be sending out an email today to purpose the next meeting
date.

As I mentioned previously in this email, there is a WIP effort to capture
the Superset UI (as it exists in code today) in Sketch allowing us to make
it publicly available. This seems like an opportunity for us to collaborate
in place of introducing "the" solution.

It sounds like we're all aligned on this serving the community!

I look forward to working with you both.

Best,
Eli

On Tue, Jan 1, 2019 at 9:24 PM Jolly Paramjit 
wrote:

> Hi Everyone,
>
>  Intent of “Rasmiranjan” queries was that we were thinking of
> introducing the “Design system” for superset. We have our own fork from
> superset & we are doing lot of customisation in it, some will be generic
> which we will contribute to open source & some will be specific to our
> use-cases.
> Having good history about design system & contact with right set of folks
> is important so we can do something good which everyone can use.
> Introducing design system will really help superset to be easy to
> customise & theme in terms of UX.
>
> We would like to be part of next design related discussions, it will be
> helpful to everyone.
> --
> Thanks & Regards
> Jolly
> Handphone: +91-9971815749
>
> [We Learn, Unlearn & Re-learn.]
>
>
>
> On 2018/12/26 22:12:40, Eli Brumbaugh 
> wrote:
> > Hi Rasmiranjan,
> >
> > Thank you for reaching out to the dev@ alias about Superset design
> > processes! Great questions all around.
> >
> > Recently I sent out an email to dev@ that included information about a
> > possible Superset design system. Please check your inbox for an email
> from
> > my email alias sent to the dev@ alias. I would love to hear any thoughts
> > you have on it. Please be sure to reply to the entire group!
> >
> > Re: Does Superset follow/suggest any design system to code?
> >
> > The current Superset theme is based on a fork of
> > https://bootswatch.com/cosmo/
> >
> > Re: How did Superset come up with the decided design system?
> >
> > The cosmo theme I shared above has been modified several times over the
> > years by multiple individuals. Mostly in an effort to modernize the look
> > and feel. Everyone is welcome to share feedback/changes!
> >
> > The altered code can be found here:
> >
> https://github.com/apache/incubator-superset/tree/master/superset/assets/stylesheets/less/cosmo
> >
> > Re: How can I enable a design system in Superset?
> >
> > The UI theme should come bundled with your instance of Superset. I’m not
> an
> > engineer but I believe you can see it at /superset/theme (If anyone has
> > more information please add it/correct me if I’m wrong).
> >
> > A note:
> >
> > Currently Superset does not support dynamic themeing but I believe this
> > would be a valuable add in the future. I believe it would require a
> > refactor.
> >
> > Happy to answer any other questions you may have. If you’re interested in
> > the design of Superset be sure to join us on Slack in the public #design
> > channel!
> >
> > Best,
> > Eli
> >
> > On Wed, Dec 26, 2018 at 11:09 AM Rasmiranjan Nayak <
> > rasmiranjan.na...@guavus.com> wrote:
> >
> > > Hi,
> > >
> > > Does superset follow/suggest any Design system to code? If yes, how
> > > superset came up with decided Design system?
> > > If no, how can enable design system in superset?
> > >
> > > Happy to hear more on this front from all of you.
> > >
> > > Thanks & Regards,
> > > Rasmiranjan Nayak
> > >
> > > --
> >
> > Eli Sebastian Brumbaugh
> > Design Lead  |  Data Platform, Data UX & Data Design System
> > Indigenous@ Diversity Group Lead
> >
>
>
>
>

-- 

Eli Sebastian Brumbaugh
Design Lead  |  Data Platform, Data UX & Data Design System
Indigenous@ Diversity Group Lead


Re: Apache Superset - Design Operating System (please review, discuss and vote)

2019-01-02 Thread jollyp
Hi Everyone,

 Intent of “Rasmiranjan” queries was that we were thinking of introducing 
the “Design system” for superset. We have our own fork from superset & we are 
doing lot of customisation in it, some will be generic which we will contribute 
to open source & some will be specific to our use-cases.
Having good history about design system & contact with right set of folks is 
important so we can do something good which everyone can use.
Introducing design system will really help superset to be easy to customise & 
theme in terms of UX.

We would like to be part of next design related discussions, it will be helpful 
to everyone.
--
Thanks & Regards
Jolly
Handphone: +91-9971815749

[We Learn, Unlearn & Re-learn.]

On 2018/12/21 19:51:19, Eli Brumbaugh  wrote: 
> Hi All,
> 
> I want to take a moment to disambiguate the individual contributors from
> the companies I mentioned in my previous email. In all future communication
> I will name *individuals* and *not corporations*.
> 
> The individuals who met to discuss Apache Superset design are:
> 
>- Matt Spiel
>- Anita Lillie
>- Marie Sbrocca
>- Chris Williams
>- Conglei Shi
>- Krist Wongsuphasawat
>- Eli Brumbaugh
> 
> *Have a wonderful holiday season everyone!*
> 
> Best,
> Eli
> 
> 
> 
> On Thu, Dec 20, 2018 at 6:56 PM Eli Brumbaugh 
> wrote:
> 
> > Hello world,
> >
> > Airbnb and Lyft (design) recently had a conference call to discuss *Superset
> > design*.
> >
> > In hindsight we should have announced this meeting to the Apache community
> > in advance. For that, I apologize. In the future we will ensure that it is
> > both *announced in advance* and *accessible* via *freely** available*
> > conference software such as Google Hangouts.
> >
> > Below I will outline the topics we covered and the proposal we would like
> > to run past the community for *discussion and a vote*.
> >
> > *Topics:*
> >
> >- Superset design system alignment and strategy.
> >- Superset design operating model.
> >- Next steps and action items.
> >
> > *Superset Design Operating System (proposal to vote on)*
> >
> > The goal of this operating system proposal is to standardize on *community
> > accessible* (design related) discussion, proposals, process and reviews.
> >
> >1. Ad hoc (*only minor*) design discussion will happen in the Apache
> >Superset #design *community accessible* slack channel.
> >2. Design changes to Apache Superset should be proposed through the 
> > *community
> >accessible* dev@superset.incubator.apache.org email alias for a vote.
> >3. Apache Superset will be designed in Sketch
> > (unlike Photoshop, there is no comparable
> >free tool). Sketch files *community accessible* (for free) through Sketch
> >Cloud . Please note many
> >companies use different design tools. For example we at Airbnb use Figma.
> >However, Sketch and Figma are backwards compatible.
> >4. When design changes are submitted to the Apache Superset repo they
> >should be tagged with the *community accessible* 'design' tag.
> >
> > *Two requests:*
> >
> >- If anyone is designing Superset in any a tool other than Sketch or
> >Figma please let the community know so we can work to ensure 
> > compatibility
> >and access.
> >- If there are any other designers engaging with Superset (past,
> >present or future) please add them to the thread know so we can ensure 
> > they
> >have a voice.
> >
> > *Attention:*
> >
> >- Superset design will reconvene at the end of January. Date, time and
> >links will be shared with the Apache community in advance.
> >
> > Looking forward to your feedback.
> >
> > Best,
> > Eli
> >
> > --
> >
> > Eli Sebastian Brumbaugh
> >
> 
> 
> -- 
> 
> Eli Sebastian Brumbaugh
> Design Lead  |  Data Platform, Data UX & Data Design System
> Indigenous@ Diversity Group Lead
>