Re: [ANNOUNCE] Please welcome new Superset committer Erik Ritter

[Eli Brumbaugh]

Congratulations Erik! 

On Thu, Aug 29, 2019 at 10:03 AM Ville Brofeldt 
wrote:

> Congratulations Erik, well deserved and definitely an asset to the project!
> Ville
>
> On Thu, Aug 29, 2019, 19:49 Grace Guo 
> wrote:
>
> > Hi folks!
> >I'm very pleased to announce that the Superset PMC has voted Erik
> > Ritter to be a committer. Since late May this year, he has closed a few
> > pull requests (
> >
> https://github.com/apache/incubator-superset/pulls?q=is%3Apr+author%3Aetr2460+is%3Aclosed
> > <
> >
> https://github.com/apache/incubator-superset/pulls?q=is:pr+author:etr2460+is:closed
> >),
> > covering bug fixes, chores, new features. Erik has done incredible work
> in
> > improving Superset’s documentation, issues and community involvement.
> >
> > Please join me in welcoming Erik Ritter!
> >
> > Thanks,
> >
> > Grace
> > on behalf of the Superset PMC
> >
> >
>
-- 
Eli Sebastian Brumbaugh
Pronouns: He, Him, His
Design Manager  |  Data Platform, Production Platform, Information Security
Indigenous@ Airfinity Group Founder

Re: [ANNOUNCE] Release Apache Superset (incubating) version 0.34.0

[Eli Brumbaugh]

Congratulations all!

On Tue, Aug 27, 2019 at 3:09 PM Tao Feng  wrote:

> Congrats Max and the team for all the hard work on 1st Superset Apache
> release !
>
> On Tue, Aug 27, 2019 at 1:29 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Dear all,
> >
> > The Apache Superset (incubating) community is happy to announce Apache
> > Superset
> > (incubating) version 0.34.0!
> >
> > Apache Superset (incubating) is a business intelligence web application
> >
> > *0.34.0 is our first official Apache release!*
> >
> > A full list of the changes in this release can be found in the release
> > notes:
> >
> >
> https://github.com/apache/incubator-superset/blob/master/CHANGELOG.md#change-log
> >
> > A link to the source download can be found here:
> > https://www.apache.org/dist/incubator/superset/
> >
> > Find links to Apache Superset related resources on our Github:
> > https://github.com/apache/incubator-superset
> >
> > Best regards,
> >
> > The Apache Superset (incubating) Team
> > ___
> > DISCLAIMER:
> > Apache Superset (incubating) is an effort undergoing incubation at The
> > Apache
> > Software Foundation (ASF), sponsored by the name of Apache Incubator PMC.
> > Incubation is required of all newly accepted projects until a further
> > review indicates that the infrastructure, communications, and decision
> > making process have stabilized in a manner consistent with other
> successful
> > ASF projects. While incubation status is not necessarily a reflection of
> > the completeness or stability of the code, it does indicate that the
> > project has yet to be fully endorsed by the ASF.
> >
>
-- 
Eli Sebastian Brumbaugh
Pronouns: He, Him, His
Design Manager  |  Data Platform, Production Platform, Information Security
Indigenous@ Airfinity Group Founder

Re: [Superset] Design interest group

[Eli Brumbaugh]

Hi Max,

Thank you for sharing this exciting update. I am interested in
participating on behalf of Airbnb Design.

I look forward to working with you all.

Best,
Eli

On Mon, Aug 5, 2019 at 4:54 PM Maxime Beauchemin 
wrote:

> Hi all,
>
> As mentioned at the bi-weekly community meeting, the team at Preset is
> planning to sponsor an engagement with design agency Cartel
>  to assist the community in defining what the
> future of Superset may evolve looking like. The folks at Cartel (cced) are
> specialized in designing data-heavy, highly-interactive applications like
> Superset.
>
> The effort will take place over September - October - November, and for
> that engagement we'd like to assemble a small interest group (6-8 people)
> that can help shape the direction of this effort, from across the
> community. We'd like for the major contributors to be represented, and for
> representation to be roughly be based on merit accumulated so far. The
> folks at Cartel told us they've had much better success working with
> smaller group so we're trying to respect that.
>
> People who want to get involved should:
> * be able to commit 2H+ a week over those 3 months
> * have a history of involvement in the project, merit and/or merit
> representation
> * a deep understanding of the product
> * design sense + good UI / UX intuition
> * understanding Superset use cases and users
>
> We'd also like to be able to communicate progress throughout the process
> and offer a way for the people from the wider community to provide
> feedback. One or two people in the interest group will be in charge of
> communicating in and out as we move forward.
>
> The interest group will define what areas to focus on and the deliverables
> as we engage with the agency. My personal intuition going into this is that
> we'll prefer to go wide and shallow as opposed to dig super deep into a
> small set of specific area. Though we'll likely focus on core-ux workflows
> like content creation, and tying up the different pieces of Superset
> together. We may explore new areas like spreasheet-type interactions,
> notebooky-type interfaces and things of that nature as well. In any case,
> expect to see lots of wireframes!
>
> We do not intend for the designs produced during this engagement to be an
> absolute for the future of Superset, but instead as an inspiration and
> guiding material to build upon as we work on individual PRs.
>
> Anyhow! Please reach out if you're interested or have feedback on the
> process. We're intending to report progress on the mailing list as we go.
>
> Thanks,
>
> Max
>


-- 
Eli Sebastian Brumbaugh
Pronouns: He, Him
Design Manager  |  Data Platform, Data UX & Data Design System
Indigenous@ Airfinity Group Lead

Re: [VOTE] SIP-15/15A Proposal for Transparent and Consistent Time Intervals

[Eli Brumbaugh]

+1

On Thu, Jun 20, 2019 at 2:57 PM Krist Wongsuphasawat 
wrote:

> +1
>
> On Thu, Jun 20, 2019 at 1:49 PM Vyl Chiang 
> wrote:
>
> > +1!
> > Vyl Chiang
> > Product
> > 650.279.1185
> >
> > 
> >
> >
> > On Thu, Jun 20, 2019 at 11:25 AM Jeff Feng  >
> > wrote:
> >
> > > +1 Binding
> > >
> > > On Thu, Jun 20, 2019 at 10:43 AM Michelle Thomas
> > >  wrote:
> > >
> > > > +1
> > > >
> > > > On Wed, Jun 19, 2019 at 2:42 PM John Bodley  > > > .invalid>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I would like to call a vote on SIP-15/15A:
> > > > >
> > > > >- https://github.com/apache/incubator-superset/issues/6360
> > > > >- https://github.com/apache/incubator-superset/issues/7656
> > > > >
> > > > > These are proposals for transparent and consistent time intervals
> > > across
> > > > > the Druid REST API and SQLAlchemy connectors. Note though the logic
> > is
> > > > > quite simple the changes required are somewhat involved and
> include a
> > > > > method for transitioning between the current and proposed
> solutions.
> > > > >
> > > > > If anyone has any hesitation, questions, or concerns about the
> logic
> > > > please
> > > > > comment on the relevant SIPs.
> > > > >
> > > > > Thanks
> > > > > -John
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > *Jeff Feng*
> > > Product Lead
> > > m: (949)-610-5108
> > > twitter: @jtfeng
> > >
> >
>
>
> --
>
> *Krist Wongsuphasawat, PhD*
> http://kristw.yellowpigz.com
>


-- 
Eli Sebastian Brumbaugh
Pronouns: He, Him
Design Manager  |  Data Platform, Data UX & Data Design System
Indigenous@ Airfinity Group Lead

Re: [VOTE] Hosting questions / answers on StackOverFlow

[Eli Brumbaugh]

+1

On Tue, Apr 23, 2019 at 7:55 PM John Bodley 
wrote:

> +1
>
> > On Apr 23, 2019, at 7:02 PM, Jeff Feng 
> wrote:
> >
> > +1
> >
> > On Tue, Apr 23, 2019 at 6:19 PM Chris Williams
> >  wrote:
> >
> >> +1
> >>
> >> Chris
> >>
> >> Data Visualization
> >> San Francisco
> >>
> >>
> >> On Tue, Apr 23, 2019 at 6:03 PM Abhishek Sharma <
> >> abhioncbr.apa...@gmail.com>
> >> wrote:
> >>
> >>> +1
> >>>
> >>> On Tue, Apr 23, 2019 at 8:49 PM Kan Ouivirach  >
> >>> wrote:
> >>>
>  +1
> 
>  On Wed, Apr 24, 2019 at 7:47 AM Michelle Thomas
>   wrote:
> 
> > +1
> >
> > On Tue, Apr 23, 2019 at 5:42 PM Krist Wongsuphasawat <
> > krist.wo...@gmail.com>
> > wrote:
> >
> >> Hi Superset Community,
> >>
> >> Per the previous thread "[DISCUSS] Best place for questions /
> >>> answers",
> >> there is a proposal to
> >>
> >>   - Host Superset Q (questions such as "How do I do something in
> >>   Superset?") on StackOverFlow instead of github issues.
> >>   - New questions on other channels (github/slack/etc.) will not
> >> be
> >>   answered and the authors will be notified to ask on
> >> StackOverFlow
> >> instead.
> >>   - Only keep bug reports, feature requests and project
> >> maintenance
> > issues
> >>   on github. Old FAQs can be copied over to StackOverFlow. (Will
> >>> need
> >>   volunteers for this.)
> >>
> >> I would like to call for a VOTE to migrate to StackOverFlow.
> >> Please +1 if you support this decision, 0 for no comment or -1 if
> >> you
> >> disagree.
> >>
> >> This poll will end on Friday April 26th, 11:59pm Pacific time.
> >>
> >> Best regards,
> >>
> >> Krist
> >>
> >> --
> >>
> >> *Krist Wongsuphasawat*
> >> http://kristw.yellowpigz.com
> >>
> >
> 
> >>>
> >>
>
-- 
Eli Sebastian Brumbaugh
Design Lead  |  Data Platform, Data UX & Data Design System
Indigenous@ Diversity Group Lead

Re: [VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC1

[Eli Brumbaugh]

+1

On Fri, Apr 19, 2019 at 8:53 AM Vyl Chiang  wrote:

> +1 so excited!!
> Vyl Chiang
> Product
> 650.279.1185
>
> 
>
>
> On Fri, Apr 19, 2019 at 7:14 AM Krist Wongsuphasawat <
> krist.wo...@gmail.com>
> wrote:
>
> > +1 thank you Max
> >
> > Best regards,
> >
> > Krist
> >
> > --
> >
> > Krist Wongsuphasawat
> > http://kristw.yellowpigz.com
> > On Apr 19, 2019, 06:15 -0700, Jeff Feng ,
> > wrote:
> > > Exciting news! +1 binding
> > >
> > > On Thu, Apr 18, 2019 at 10:36 PM Maxime Beauchemin <
> > > maximebeauche...@gmail.com> wrote:
> > >
> > > > Dear all,
> > > >
> > > > The source release 0.32.0 RC1 for Apache Superset is baked and
> > available
> > > > at:
> > > > https://dist.apache.org/repos/dist/dev/incubator/superset/, public
> > > > keys are available
> > > > at
> https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> > > >
> > > > This is the second ASF release candidate of Superset (!)* We're still
> > > > ironing out our release process, so please bear with us and help if
> you
> > > > can*
> > > > .
> > > >
> > > > As I went along, I documented the process in RELEASING.md in the
> repo,
> > > > latest edits here
> > https://github.com/apache/incubator-superset/pull/7329
> > > >
> > > > For context (and similarly to 0.31) the `0.32` release branch was cut
> > at
> > > > SHA 1fece0d2f, that was merged on master on Jan 22nd. From that
> common
> > > > ancestor, the following list of commit was added as cherry-picks. The
> > SHAs
> > > > in the list bellow reference the cherries on the release branch, PR
> > number
> > > > are available to get more details.
> > > >
> > > > b89cdbdc RELEASING.md from master
> > > > 0e23f2e6 Add sign.sh
> > > > 21804346 [load_examples] download data at runtime (#7314)
> > > > b32d5900 Remove LICENSE entry around dataset (#7318)
> > > > b3aa5633 (release--0.31) 0.31rc23
> > > > 24a595f4 bugfix: improve 'Time Table' (#6959)
> > > > c70abbed 0.31rc22
> > > > dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244)
> > > > 2ab07a08 Fix race condition when fetching results in SQL Lab (#7198)
> > > > (#7242)
> > > > a9d54894 0.31.0rc21
> > > > b959fcd2 fix PRODUCT-67916 Click OK button cannot close error message
> > modal
> > > > (#7179)
> > > > 2da9613f Update __init__.py (#7166)
> > > > 538da2e3 0.31.0.rc20
> > > > 7ce35d2a [migration] Fixing issue with fb13d49b72f9 downgrade (#7145)
> > > > 947f02ff [migration] Fixing issue with c82ee8a39623 downgrade (#7144)
> > > > daf2b8e5 Bump python lib croniter to an existing version (#7132)
> > > > eb4c1355 Use metric name instead of metric in filter box (#7106)
> > > > 2ff721ae handle null column_name in sqla and druid models
> > > > e83a07d3 [forms] Fix handling of NULLs
> > > > 76d26f37 0.31.0.rc19
> > > > fe78b4ec Fix filter_box migration PR #6523 (#7066)
> > > > c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined
> query
> > > > (#7029)
> > > > b64a452a [sql lab] improve table name detection in free form SQL
> > (#6793)
> > > > 2357c4aa Adding custom control overrides (#6956)
> > > > 9dd7e84a [sql-parse] Fixing LIMIT exceptions (#6963)
> > > > 5d8dd142 [csv-upload] Fixing message encoding (#6971)
> > > > f454dedd [main] Disable resetting main DB attributes (#6845)
> > > > e967b268 [sqla] Fixing order-by for non-inner-joins (#6862)
> > > > a5d9a4e0 Adding template_params to datasource editor for sqla tables
> > > > (#6869)
> > > > 6b895413 [datasource] Ensuring consistent behavior of datasource
> > > > editing/saving. (#7037)
> > > > 8ef2789f Adding warning message for sqllab save query (#7028)
> > > > 0ebdb564 fix inaccurate data calculation with adata rolling and
> > > > contribution (#7035)
> > > > b3af6a26 [fix] explore chart from dashboard missed slice title
> (#7046)
> > > > c54b067c [db-engine-spec] Aligning Hive/Presto partition logic
> (#7007)
> > > > bd65942e Changing time table viz to pass formatTime a date (#7020)
> > > > 50accda9 [fix] Cursor jumping when editing chart and dashboard titles
> > > > (#7038)
> > > > 5ace5769 0.31.0rc17
> > > > 927a5846 [WIP] fix user specified JSON metadata not updating
> dashboard
> > on
> > > > refresh (#7027)
> > > > fafb824d 0.31.0rc16
> > > > 7b72985e [fix] /superset/slice/id url is too long (#6989)
> > > > b497d9e7 fix dashboard links in welcome page (#6756)
> > > > c42afa11 0.31.0rc15
> > > > 35c55278 Enhancement of query context and object. (#6962)
> > > > 1c41020c Split tags migration (#7002)
> > > > ec7a0b22 0.31.0rc14
> > > > 4655cb4c Remove Cypress from package.json (#6912)
> > > > fb8e3208 0.31.0rc13
> > > > b4cbe13d VIZ-190 fix (#6958)
> > > > 5b7b22fd 0.31.0rc12
> > > > 51804229 Fix deck.gl form data (#6953)
> > > > 9939a52d 0.31.0rc11
> > > > c3db74d9 (apache/cherry_c3db74d9021f9e60ef21beeb0847ff9f4b0277fd) Fix
> > > > rendering regression from the introduction of bignumber (#6937)
> > > > 9940d30a 0.31.0rc10
> > > > 3df2b8d5 Add a safety check before getting clientHeight (#6923)
> > > > ccb51385 v0.31.0rc9
> > 

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

[Eli Brumbaugh]

Hi All,

I wanted to let the group know that we've updated the Apache Superset
design sync to 5-6 PM (PST) from the previous 2-3 PM (PST) timing that
would have been more difficult for those of us who are distributed.

Jolly & Rasmiranjan, I hope this new time is more reasonable. Thank you for
sharing your itinerary with us. I will add it to the agenda.

Best,
- Eli

On Mon, Jan 7, 2019 at 11:05 PM Jolly Paramjit 
wrote:

> Eli,
>   Thanks for your reply, I think we should attend the video conference
> whatever odd hours it may be.  We will join the call.
> As I want first discussion with full information & some basic demo to
> showcase.
>
> We will be presenting:
> 1. Our high level planning for superset overall feature enhancements.
> (in-case everyone is interested)
> 2. Design system - We are working in Guavus
> 3. How we are thinking to use same in superset but we need some guidance
> from stake holders.
>
> Looking forward for the upcoming meeting.
>
> --
> Thanks & Regards
> Jolly
> Handphone: +91-9971815749
>
> [We Learn, Unlearn & Re-learn.]
>
>
> On 08/01/19, 5:17 AM, "Eli Brumbaugh" 
> wrote:
>
> Hi Jolly, Rasmiranjan (and the community!)
>
> Thank you again for letting the community know about your time zone
> difference (13.5 hours ahead of those of us in the Bay Area) and how
> the
> time originally set for the design sync is difficult for you to attend.
>
> *Geographically distributed collaboration proposal:*
> Please let us know what you think about this solution.
>
>- In place of a video conference we collaborate via this email
> alias,
>shared (publicly accessible docs) and Sketch files.
>- The ASF how-it-works
><http://www.apache.org/foundation/how-it-works.html> suggest the
>following:
>   - *"Communication is done via mailing lists. These identify
> "virtual
>   meeting rooms" where conversations happen asynchronously, which
> is a
>   general requirement for groups that are so geographically
> distributed to
>   cover all time zones (like it's normally the case for the
> various Apache
>   communities).*
>- With our global distribution working asynchronously via the dev@
> email
>and google docs seems like the best way to move forward while
> maximizing
>the transparency of our discussions.
>
> *Sharing your proposal: *
> Jolly and Rasmiranjan, would you be willing to share your Superset
> Design
> System and custom UI framework proposal via the dev@ email alias
> along with
> any related publically accessible docs for discussion and if you
> desire a
> vote?
>
> *Upcoming design sync:*
>
>1. The Thursday, January 31st video chat will still occur for all
> who
>can attend.
>   - *All discussion*, notes, open questions, to do's, etc will be
> documented
>   in this publicly
>   <
> https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing
> >
>   accessible google doc.
>   - *All decisions* will still be put to a vote in the dev@ email
> alias.
>2. This doc
><
> https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing
> >
>will be sent out to the dev@ email alias as a reminder for
> additional
>comments/discussion.
>   - Please be sure to comment and leave feedback!
>3. This doc
><
> https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing
> >
>will serve as a record of meeting notes that can be accessed easily
> by all.
>
> *If anyone has any thoughts or concerns please let the thread know!*
>
> Best,
> Eli
>
>
>
>     On Fri, Jan 4, 2019 at 11:35 AM Jolly Paramjit <
> jolly.param...@guavus.com>
> wrote:
>
> > Hi Eli,
> >
> > We can use hangouts not an issue, officially we use zoom.
> >
> > --
> > Thanks & Regards
> > Jolly
> > Handphone: +91-9971815749
> >
> > [We Learn, Unlearn & Re-learn.]
> >
> >
> > On 05/01/19, 12:34 AM, "Eli Brumbaugh"  .INVALID>
> > wrote:
> >
> > Hi Jolly,
> >
> > Thank you for letting me know about your location and custom
> design
> > system
> > / UI framework. I will work on finding a time that works for
> everyone.
> 

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

[Eli Brumbaugh]

Hi Jolly, Rasmiranjan (and the community!)

Thank you again for letting the community know about your time zone
difference (13.5 hours ahead of those of us in the Bay Area) and how the
time originally set for the design sync is difficult for you to attend.

*Geographically distributed collaboration proposal:*
Please let us know what you think about this solution.

   - In place of a video conference we collaborate via this email alias,
   shared (publicly accessible docs) and Sketch files.
   - The ASF how-it-works
   <http://www.apache.org/foundation/how-it-works.html> suggest the
   following:
  - *"Communication is done via mailing lists. These identify "virtual
  meeting rooms" where conversations happen asynchronously, which is a
  general requirement for groups that are so geographically distributed to
  cover all time zones (like it's normally the case for the various Apache
  communities).*
   - With our global distribution working asynchronously via the dev@ email
   and google docs seems like the best way to move forward while maximizing
   the transparency of our discussions.

*Sharing your proposal: *
Jolly and Rasmiranjan, would you be willing to share your Superset Design
System and custom UI framework proposal via the dev@ email alias along with
any related publically accessible docs for discussion and if you desire a
vote?

*Upcoming design sync:*

   1. The Thursday, January 31st video chat will still occur for all who
   can attend.
  - *All discussion*, notes, open questions, to do's, etc will be
documented
  in this publicly
  
<https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing>
  accessible google doc.
  - *All decisions* will still be put to a vote in the dev@ email alias.
   2. This doc
   
<https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing>
   will be sent out to the dev@ email alias as a reminder for additional
   comments/discussion.
  - Please be sure to comment and leave feedback!
   3. This doc
   
<https://docs.google.com/document/d/1OokXB2BNdYx8-M4IGYyaoVU3J74Pe0ZNJeqSHjyLAmA/edit?usp=sharing>
   will serve as a record of meeting notes that can be accessed easily by all.

*If anyone has any thoughts or concerns please let the thread know!*

Best,
Eli



On Fri, Jan 4, 2019 at 11:35 AM Jolly Paramjit 
wrote:

> Hi Eli,
>
> We can use hangouts not an issue, officially we use zoom.
>
> --
> Thanks & Regards
> Jolly
> Handphone: +91-9971815749
>
> [We Learn, Unlearn & Re-learn.]
>
>
> On 05/01/19, 12:34 AM, "Eli Brumbaugh" 
> wrote:
>
> Hi Jolly,
>
> Thank you for letting me know about your location and custom design
> system
> / UI framework. I will work on finding a time that works for everyone.
>
> Quick question: Can you use Google Hangouts?
>
> Best,
> Eli
>
> On Wed, Jan 2, 2019 at 5:15 PM Jolly Paramjit <
> jolly.param...@guavus.com>
> wrote:
>
> > 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  > .INVALID<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
> > <
> https://apache-superset.slack.com/archives/CCKHMGRRB/p1545423476013000>
> > 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 

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

[Eli Brumbaugh]

Hi Jolly,

Thank you for letting me know about your location and custom design system
/ UI framework. I will work on finding a time that works for everyone.

Quick question: Can you use Google Hangouts?

Best,
Eli

On Wed, Jan 2, 2019 at 5:15 PM Jolly Paramjit 
wrote:

> 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  .INVALID<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
> <https://apache-superset.slack.com/archives/CCKHMGRRB/p1545423476013000>
> 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
>


-- 

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

Apache Superset Design Sync (vote on next meet up)

[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)

[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
> > ><https://www.sketchapp.com/> (unlike Photoshop, there is no
> comparable
> > >free

Re: design system in superset

[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: design system in superset

[Eli Brumbaugh]

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

Re: Some feedback from the Apache board on the last incubator report

[Eli Brumbaugh]

Thank you, Alan!

I appreciate the positive feedback on the report and the list image config
info.

Best,
Eli

On Wed, Dec 26, 2018 at 1:26 PM Alan Gates  wrote:

> Each month the incubator reports to the board, and a few bits of feedback
> from the board on the incubator report this month concerned superset.  I
> thought I'd share with you:
>
> Thanks to Daffodil, Skywalking, and Superset forthoughtfully written
> reports
>
> Please let superset know that their lists can be configured to allow image
> attachments if they wish.
>
> Alan.
>
-- 

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)

[Eli Brumbaugh]

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
><https://www.sketchapp.com/> (unlike Photoshop, there is no comparable
>free tool). Sketch files *community accessible* (for free) through Sketch
>Cloud <https://www.sketchapp.com/docs/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

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

[Eli Brumbaugh]

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

Re: New Committer: Krist Wongsuphasawat

[Eli Brumbaugh]

Congratulations Krist! Well deserved!

On Tue, Nov 20, 2018 at 9:07 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Well deserved, welcome on board Krist!
>
> On Tue, Nov 20, 2018 at 9:01 AM Michelle Thomas
>  wrote:
>
> > Congrats Krist!!
> >
> > On Tue, Nov 20, 2018 at 6:17 AM Stephanie Rivera
>  > >
> > wrote:
> >
> > > <
> > >
> >
> https://chrome.google.com/webstore/detail/bitmoji/bfgdeiadkckfbkeigkoncpdieiiefpig
> > > >
> > > Cheers,
> > >
> > > Stephanie
> > >
> > >
> > > *Stephanie Rivera* |* Sr. Director of Data Intelligence*
> > >
> > > 8181 Arista Place | Suite 300 | Broomfield, CO 80021 | Westminster, CO
> > > 80020
> > > <
> > >
> >
> http://www.google.com/url?q=http%3A%2F%2Fwww.spotxchange.com%2F=D=1=AFrqEzdlZjMtAvYRCQByfN6D_6PjZhSbSw
> > > >
> > >
> > > <
> > >
> >
> https://www.google.com/url?q=https%3A%2F%2Fdl.dropbox.com%2Fs%2F5se5ucpqodjsq1h%2Flinkedin.png=D=1=AFrqEzdTHQrlDWywpW7VZVpwGJJdOBY-Wg
> > > >
> > >
> > >
> > >
> > >
> > > On Tue, Nov 20, 2018 at 12:47 AM Jeff Feng 
> wrote:
> > >
> > > > The Project Management Committee (PMC) for Apache Superset has
> invited
> > > > Krist Wongsuphasawat to become a committer and we are pleased to
> > announce
> > > > that he has accepted.
> > > >
> > > > Being a committer enables easier contribution to the project since
> > there
> > > is
> > > > no need to go via the patch submission process. This should enable
> > better
> > > > productivity. Being a PMC member enables assistance with the
> management
> > > and
> > > > to guide the direction of the project.
> > > >
> > > > Congratulations Krist!
> > > > Jeff
> > > >
> > >
> >
>


-- 

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

Re: Regarding [SIP-3] Scheduled email reports for Slices / Dashboards

[Eli Brumbaugh]

+1

On Tue, Nov 13, 2018 at 1:21 PM Chris Williams
 wrote:

> +1
>
> Chris
>
> Data Visualization
> San Francisco
>
>
> On Tue, Nov 13, 2018 at 12:37 PM Stephanie Rivera  >
> wrote:
>
> > +1
> > Cheers,
> >
> > Stephanie
> >
> >
> > *Stephanie Rivera* |* Sr. Director of Data Intelligence*
> >
> > 8181 Arista Place | Suite 300 | Broomfield, CO 80021 | Westminster, CO
> > 80020
> > <
> >
> http://www.google.com/url?q=http%3A%2F%2Fwww.spotxchange.com%2F=D=1=AFrqEzdlZjMtAvYRCQByfN6D_6PjZhSbSw
> > >
> >
> > <
> >
> https://www.google.com/url?q=https%3A%2F%2Fdl.dropbox.com%2Fs%2F5se5ucpqodjsq1h%2Flinkedin.png=D=1=AFrqEzdTHQrlDWywpW7VZVpwGJJdOBY-Wg
> > >
> >
> >
> >
> >
> > On Tue, Nov 13, 2018 at 12:41 PM Abhishek Sarangan
> >  wrote:
> >
> > > Hello guys,
> > >
> > > Apologies for asking again, but is there any decision made about the
> > > scheduled emails PR (SIP-3)?
> > >
> > > Thanks,
> > > Abhishek Sarangan
> > > Yahoo Gemini Engineering, Oath Inc
> > >
> > > On Thu, Nov 8, 2018 at 3:05 PM Abhishek Sarangan 
> > > wrote:
> > >
> > > > Greetings Superset Supers,
> > > >
> > > > Apologies if this is a question that's been asked repeatedly, but
> would
> > > > the PR for SIP-3: Scheduled email reports be merged anytime soon?
> > > >
> > > > We at Oath have been using Superset for the past two years, and our
> > users
> > > > have been recently asking for the email functionality, which exists
> as
> > an
> > > > SIP at https://github.com/apache/incubator-superset/pull/5294.
> > > >
> > > > Please do let us know the timeline, if any, or if it won't be merged.
> > > >
> > > > Thanks,
> > > > Abhishek Sarangan
> > > > Yahoo Gemini Engineering, Oath Inc.
> > > >
> > >
> >
>


-- 

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

Re: [VOTE] SIP-12 Proposal for Branch Management and Release Process

[Eli Brumbaugh]

+1

On Tue, Nov 13, 2018 at 7:14 AM Stephanie Rivera 
wrote:

> +1
>
> Cheers,
>
> Stephanie
>
>
> *Stephanie Rivera* |* Sr. Director of Data Intelligence*
>
> 8181 Arista Place | Suite 300 | Broomfield, CO 80021
> 
> | Westminster, CO 80020
> <
> http://www.google.com/url?q=http%3A%2F%2Fwww.spotxchange.com%2F=D=1=AFrqEzdlZjMtAvYRCQByfN6D_6PjZhSbSw
> >
>
> <
> https://www.google.com/url?q=https%3A%2F%2Fdl.dropbox.com%2Fs%2F5se5ucpqodjsq1h%2Flinkedin.png=D=1=AFrqEzdTHQrlDWywpW7VZVpwGJJdOBY-Wg
> >
>
>
>
>
> On Tue, Nov 13, 2018 at 12:31 AM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > +1
> >
> > On Mon, Nov 12, 2018 at 10:59 PM Chris Williams
> >  wrote:
> >
> > > +1
> > >
> > > Chris
> > >
> > > Data Visualization
> > > San Francisco
> > >
> > >
> > > On Mon, Nov 12, 2018 at 9:21 PM John Bodley  > > .invalid>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > I would like to call a vote on [SIP-12] Proposal for Branch
> Management
> > > and
> > > > Release Process <
> > > https://github.com/apache/incubator-superset/issues/6131
> > > > >.
> > > >
> > > > Thanks
> > > > -John
> > > >
> > >
> >
>
-- 

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

Re: [Vote] SIP-13: Proposal for Code Review Process

[Eli Brumbaugh]

+1

On Thu, Nov 8, 2018 at 1:15 PM Chris Williams
 wrote:

> +1
>
> Chris
>
> Data Visualization
> San Francisco
>
>
> On Thu, Nov 8, 2018 at 11:04 AM Krist Wongsuphasawat <
> krist.wo...@gmail.com>
> wrote:
>
> > Hi dev@superset,
> >
> > I would like to call a vote on *SIP-13: Proposal for Code Review
> Process*.
> >
> > The proposal details and discussion can be found here.
> > https://github.com/apache/incubator-superset/issues/6132
> > One small modification from the original proposal is I have dropped the
> > stale branch check.
> >
> > Best regards,
> >
> > Krist
> >
>


-- 

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

Re: [SIP-0] Vote

[Eli Brumbaugh]

+1
On Wed, Oct 24, 2018 at 2:37 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> FYI
> https://community.apache.org/committers/voting.html
>
> On Wed, Oct 24, 2018 at 1:59 PM Beto Dealmeida 
> wrote:
>
> > Hi, all.
> >
> > I would like to call a vote on SIP-0, "Superset Improvement Proposals":
> >
> > https://github.com/apache/incubator-superset/issues/5602
> >
> > Beto
> >
> >
>
-- 
Eli Sebastian Brumbaugh
Design Lead  |  Data Platform  |  Data UX
Indigenous@ Diversity Group Founder

Re: [VOTE] Deprecate support for Python <3.6

[Eli Brumbaugh]

+1
On Thu, Sep 20, 2018 at 10:16 PM John Bodley  wrote:

> +1
>
> > On Sep 20, 2018, at 9:51 PM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
> >
> > Since Superset is a product, and not a library, people have the luxury to
> > pick which version of Python they desire when setting up Superset.
> >
> > Supporting 2.7 has been a burden and we have to look into the future.
> >
> > Arguments for this:
> > * take advantage of py2.7...py3.6 features
> >   * type annotations
> >   * async / await
> >   * fstrings syntactic sugar
> >   * a decade of improvements listed here:
> > https://docs.python.org/3/whatsnew/index.html
> > * less Superset bugs related to version incompatibilities
> > * free up slots in the build matrix
> > * faster
> > * maintained beyond 2020
> >
> > Cons:
> > * People living in the past will have to update their deploy scripts now
> > instead of a year from now
> >
> > -
> > if you "-1" please state your reasons!
>
-- 
Eli Sebastian Brumbaugh
Design Lead  |  Data Platform  |  Data UX
Indigenous@ Diversity Group Founder

Re: brand-primary color

[Eli Brumbaugh]

Hey Max,

That is a great point. I'll noodle on a few options and share them with the
team tomorrow.

Best,
- Eli

On Tue, Jun 12, 2018 at 11:45 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Hi,
>
> I totally understand and agree that we should be moving away from babu.
>
> I think my main point is that if we go purple or some other warm color for
> the logo/brand, we probably need a colder complementary color for links and
> action buttons to go along with it. I'm pretty clueless about
> color/branding so I'm very open to all ideas and designs.
>
> Max
>
> On Tue, Jun 12, 2018 at 9:53 AM Eli Brumbaugh
>  wrote:
>
> > Hi All,
> >
> > Thanks, Chris and Jeff for sharing this with me.
> >
> > Thanks for sharing these thoughts, Max!
> >
> > Since this is an open source project I personally feel Superset should
> have
> > a neutral brand color which is why we moved away from Airbnb's "babu" or
> > green color.
> >
> > I personally don’t think a somber theme is needed for Superset to be
> > effective at communicating data. I think we can collectively align on
> > something that helps the tool feel modern without being somber or
> > distracting the viewer from the data. A modern turquoise could be okay.
> It
> > is a fairly standard color for analytics tools. However, everything out
> > there these days is green and blue.
> >
> > I believe Superset is deserving of standing out from the crowd. Let's
> > explore options that reflect this unique offering.
> >
> > Alternatively, we can reduce the amount of brand color we use in the UI
> if
> > user distraction is what you're most concerned about.
> >
> > Best,
> > - Eli
> >
> >
> > On Mon, Jun 11, 2018 at 3:20 PM Jeff Feng  wrote:
> >
> > > + Eli & Airbnb development team on Superset
> > >
> > > On Mon, Jun 11, 2018 at 10:36 AM Maxime Beauchemin <
> > > maximebeauche...@gmail.com> wrote:
> > >
> > >> Hey,
> > >>
> > >> I've noticed the new sweet [purple] loading spinner in master and
> wanted
> > >> to
> > >> bring up a conversation about our primary color (currently
> > turquoiseish).
> > >>
> > >> I'm reading from previous conversations and recent mock-ups that
> Airbnb
> > >> wants to change the color-primary [from the current color that is used
> > for
> > >> customer facing products at Airbnb] to a shade of purple.
> > >>
> > >> Personally I prefer cold colors for links/buttons, especially for
> > Superset
> > >> where we're trying to have a super sober theme to make the data
> > >> visualizations and content standout as much as possible. I'm open to
> > have
> > >> a
> > >> warmer logo, but it can be nice to a single brand-primary color used
> for
> > >> the logo as well as actionable links/buttons.
> > >>
> > >> My incline would be to go to a different shade of turquoise, but open
> to
> > >> discuss as always.
> > >>
> > >> Max
> > >>
> > > --
> > >
> > > *Jeff Feng*
> > > Product Lead
> > > m: (949)-610-5108 <(949)%20610-5108> <(949)%20610-5108>
> > > twitter: @jtfeng
> > >
> > > --
> > Eli Sebastian Brumbaugh
> > Design Lead  |  UX Platform  |  Data UX
> > Indigenous Peoples Diversity Group Founder
> >
>
-- 
Eli Sebastian Brumbaugh
Design Lead  |  UX Platform  |  Data UX
Indigenous Peoples Diversity Group Founder