State of SIPs

[Maxime Beauchemin]

Hey all,

Here's a useful GitHub project that keeps track of SIP state:
https://github.com/apache/incubator-superset/projects/7#card-41449231

This is not urgent, but please push your SIPs forward or close them if they
fell out of relevance!

Max

[VOTE] [SIP-50] Proposal for using ECharts as our main charting library

[Maxime Beauchemin]

The discussion https://github.com/apache/incubator-superset/issues/10418 seems
to have converged without important disagreements.

Let's VOTE!

Max

On Sun, Jul 26, 2020 at 11:03 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Please discuss this SIP (Superset Improvement Proposal) here:
> https://github.com/apache/incubator-superset/issues/10418
>
> Vote will take place if/when the discussion converges.
>
> Max
>

Graduation

[Maxime Beauchemin]

Community and @mentors!

Junlin and I were talking about pushing the graduation process forward, and
even though I've done it once before, we could really use some help around
navigating the process.

The first step is to look at the checklist and identify the gaps, and I
think there are very few at this time.

Can one of our mentors volunteer to provide guidance?

Volunteers are welcomed as always, we'll also communicate as we break down
the checklist into tasks.

Thanks,

Max

[DISCUSS] [SIP-50] Proposal for using ECharts as our main charting library

[Maxime Beauchemin]

Please discuss this SIP (Superset Improvement Proposal) here:
https://github.com/apache/incubator-superset/issues/10418

Vote will take place if/when the discussion converges.

Max

Crowdsourcing Release Notes

[Maxime Beauchemin]

Hey!

As 0.37.0 is still baking, I wanted to bring up the topic of putting
together [curated] release notes - key features, areas, with small
descriptions and maybe even screenshots.

While it's pretty easy / automatable to put the detailed changelog
together, it's hard to find the key features, nuggets and themes out of
there to come up with comprehensive release notes. Release management is
hard and tedious enough without having to do this, so let's help our
release managers.

So, committers and contributors! It'd be great to crowdsource the process a
bit. One way is to label key PRs with `changelog-highlight`. We should do
this as we go along moving forward. Here are the PRs I tagged (doing a fast
first pass)
https://github.com/apache/incubator-superset/pulls?q=is%3Apr+label%3Achangelog-highlight+is%3Aclosed

Complementarily, we can list out areas that have seen progress and have
been heavily worked on (usually a collection of many PRs).  I isted what is
top of mind for me for 0.37 in a Google doc, *please review and add to the
list!*

https://docs.google.com/document/d/1M9_ICzXDB2Zd_01Ith1MdQyhdrPYk3nA8EjIPm4fDIE/edit?usp=sharing

This should get easier as we increase release cadence and as we flex our
release muscles.

Max

Re: [VOTE] [SIP-48] Using Ant Design as our primary component library

[Maxime Beauchemin]

+1 binding

On Tue, Jul 14, 2020 at 2:05 PM Aaron Suddjian  wrote:

> +1 binding
>
> On Mon, Jul 13, 2020 at 1:58 PM Evan Rusackas  wrote:
>
> > Hi all,
> >
> > This is a call to vote for SIP-48!
> >
> > Further details here:
> > https://github.com/apache/incubator-superset/issues/10254
> >
> > The vote will be open for at least 1 Week or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thank you!
> >
> > -e-
> >
> > Evan Rusackas
> > ( he | him )
> > Frontend Lead
> > Preset | preset.io
> >
>
>
> --
> Aaron Suddjian, Software Engineer at Preset
>

Re: [CANCELLED] [VOTE] Release Apache Superset (incubating) 0.37.0 based on Superset 0.37.0rc1

[Maxime Beauchemin]

Please link to the issue if it's out already.

Also everyone(!), please keep poking holes at 0.37.0rc1 and testing it as
much as you can. We want for as many issues as possible to be discovered
prior to going through the trouble of assembling RC2

Thanks,

Max

On Mon, Jul 13, 2020 at 9:51 AM Ville Brofeldt 
wrote:

> Dear Superset Community,
>
> a critical regression was identified during testing of 0.37.0rc1 (thanks
> for reporting this @bryanck!). We are therefore cancelling the vote on this
> release candidate. A new vote will be started shortly after all fixes for
> known issues on the first release candidate are finalized.
>
> Thanks,
> The Apache Superset (Incubating) Team
>
>
> > On 11. Jul 2020, at 11.53, Ville Brofeldt 
> wrote:
> >
> > Hello Superset Community,
> >
> > This is a call for the vote to release Apache Superset
> > (incubating) version 0.37.0.
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.0rc1/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-superset/tree/0.37.0rc1
> >
> > The Change Log for the release:
> > https://github.com/apache/incubator-superset/blob/0.37.0rc1/CHANGELOG.md
> >
> > public keys are available at:
> >
> > https://www.apache.org/dist/incubator/superset/KEYS
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > The Apache Superset (Incubating) Team
>
>

[RESULT] [VOTE] [SIP-47] modernize/facelift superset.apache.org

[Maxime Beauchemin]

Vote passes!

Received 5 * +1s (Erik, Will, Evan, Krist, Max)

No negative or neutral votes.

Max

On Mon, Jun 29, 2020 at 5:37 PM Krist Wongsuphasawat 
wrote:

> +1 (binding)
>
> -Krist
>
> On Mon, Jun 29, 2020 at 4:17 PM Evan Rusackas  wrote:
>
> > +1, binding
> >
> > Evan Rusackas
> > ( he | him )
> > Frontend Lead
> > Preset | preset.io
> > On Jun 29, 2020, 3:34 PM -0700, Maxime Beauchemin <
> > maximebeauche...@gmail.com>, wrote:
> > > I'm kicking off the vote for SIP-47
> > > <https://github.com/apache/incubator-superset/issues/10088>, see the
> > > [DISCUSS] thread-equivalent in the GitHub issue comment.
> > > <https://github.com/apache/incubator-superset/issues/10088>
> > >
> > > As the author of the SIP, consider this a +1 from me!
> > >
> > > Max
> > >
> > > On Tue, Jun 23, 2020 at 10:08 AM Maxime Beauchemin <
> > > maximebeauche...@gmail.com> wrote:
> > >
> > > > FYI - there's a conversation considering Docusaurus as an alternative
> > to
> > > > Gatsby/DocZ for superset.apache.org please chime in in the SIP issue
> > on
> > > > GitHub if you have an opinion on the matter!
> > > >
> > > > I'm looking to kick off a vote as comments/input settles.
> > > >
> > > > Max
> > > >
> > > > On Wed, Jun 17, 2020 at 10:20 PM Maxime Beauchemin <
> > > > maximebeauche...@gmail.com> wrote:
> > > >
> > > > > Please read and chime in here:
> > > > > https://github.com/apache/incubator-superset/issues/10088
> > > > >
> > > >
> >
>
>
> --
>
> *Krist Wongsuphasawat, PhD*
> http://kristw.yellowpigz.com
>

[VOTE] [SIP-47] modernize/facelift superset.apache.org

[Maxime Beauchemin]

I'm kicking off the vote for SIP-47
<https://github.com/apache/incubator-superset/issues/10088>, see the
[DISCUSS] thread-equivalent in the GitHub issue comment.
<https://github.com/apache/incubator-superset/issues/10088>

As the author of the SIP, consider this a +1 from me!

Max

On Tue, Jun 23, 2020 at 10:08 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> FYI - there's a conversation considering Docusaurus as an alternative to
> Gatsby/DocZ for superset.apache.org please chime in in the SIP issue on
> GitHub if you have an opinion on the matter!
>
> I'm looking to kick off a vote as comments/input settles.
>
> Max
>
> On Wed, Jun 17, 2020 at 10:20 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
>> Please read and chime in here:
>> https://github.com/apache/incubator-superset/issues/10088
>>
>

Re: [ANNOUNCE] New committer and PPMC member: Will Barrett

[Maxime Beauchemin]

Nice! Welcome aboard Will!

On Wed, Jun 24, 2020 at 9:56 AM Evan Rusackas  wrote:

> The Project Management Committee (PMC) for Apache Superset has invited
> Will Barrett 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.
>
> In the name of the community as a whole, we're very glad to have you on
> board, Will!
>
> Evan Rusackas
> ( he | him )
> Frontend Lead
> Preset | preset.io
>

Re: [DISCUSS] [SIP-47] modernize/facelift superset.apache.org

[Maxime Beauchemin]

FYI - there's a conversation considering Docusaurus as an alternative to
Gatsby/DocZ for superset.apache.org please chime in in the SIP issue on
GitHub if you have an opinion on the matter!

I'm looking to kick off a vote as comments/input settles.

Max

On Wed, Jun 17, 2020 at 10:20 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Please read and chime in here:
> https://github.com/apache/incubator-superset/issues/10088
>

Re: Getting ready for 0.37.0

[Maxime Beauchemin]

Nice! Thanks for taking the lead on 0.37!

Max

On Sun, Jun 21, 2020 at 7:09 AM Ville Brofeldt 
wrote:

> Dear Superset community,
>
> we are currently getting ready to make the first release candidate of the
> long overdue 0.37 release of Apache Superset (Incubating). The committers
> have added the `0.37` tag to any outstanding issues/PRs that they feel need
> to be merged/fixed before baking the first release candidate. If there are
> any issues/PRs that the community feels need to be addressed/reviewed,
> please don’t hesitate to post a comment on GitHub, on the #apache-releases
> channel on Slack or send an email to the dev mailing list!
>
> Ville

Re: FYI - Forked NVD3

[Maxime Beauchemin]

I moved it to `apache-superset` org earlier today. It started as a bit of
an experiment (I never created an npm package before) and didn't know how
well this would work (had to use "Grunt"!?) and wanted to keep the
experiment in our backyard before it worked.

Here: https://github.com/apache-superset/nvd3

Max

On Thu, Jun 18, 2020 at 10:28 AM Erik Ritter 
wrote:

> I'm curious why we decided to fork to preset-io/nvd3 vs.
> apache-superset/nvd3, but otherwise I think it makes sense. Maybe you can
> add the nvd3-fork package inside the superset-ui organization (
> https://www.npmjs.com/settings/superset-ui/members) so that all the
> publishing permissions work automatically?
>
> Erik
>
> On Thu, Jun 18, 2020 at 10:23 AM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Just an FYI that I forked NVD3 last night.
> > https://github.com/apache-superset/superset-ui/pull/615
> >
> > I reached out to the maintainers more than a week ago to offer help but
> > they're not responsive.
> > https://github.com/novus/nvd3/issues/
> >
> > Happy to grant access to the npm package to committers/PMC, do we have a
> > publish list of all of the committers/PMC npm usernames somewhere?
> >
> > The primary/trunk branch had fixes we've been needing for years that
> never
> > got released, and it's likely that we need to patch/tweak the lib in the
> > future.
> >
> > The goal is really just to be able to patch things, clearly we're not
> > investing further in NVD3, the plan being to move towards some other
> > library, echarts <https://github.com/novus/nvd3/issues/> being a top
> > contender.
> >
> > Max
> >
>

Re: [EXTERNAL] Re: Addressing Charts directly / how to handle embedding in dev, stage, prod cycle?

[Maxime Beauchemin]

For reference, I did some work around introducing uuids in the past, but
never got it through https://github.com/apache/incubator-superset/pull/7829.

On Thu, Jun 18, 2020 at 9:16 AM Dennis Meyer  wrote:

> Ok, I understand, this definitely makes good sense!
> This would definitely be a great help for different envs.
>
> Dennis
>
> > On 18. Jun 2020, at 18:13, Andy Clapson  wrote:
> >
> > A big +1 on this one 👍.
> >
> > UUIDs would solve some definite deployment challenges on this one -
> mainly importing a pre-built set of Dashboards into many different
> environments.
> >
> > Andy
> >
> > On 2020-06-18 12:11, Maxime Beauchemin wrote:
> >> I meant uuid in its pure form (just a universal unique identifier), not
> a
> >> fingerprint/hash of the object.
> >>
> >> Currently the importer has to keep track of the "export_object_id" to
> try
> >> to upsert properly if the same object is re-imported. It can have
> collision
> >> issue when multiple systems are involved and has other disadvantages.
> >>
> >> Max
> >>
> >> On Thu, Jun 18, 2020 at 6:35 AM Dennis Meyer 
> wrote:
> >>
> >>> @Eric:
> >>> Thanks for the feedback Eric. It’s good to know. We’ll keep it in the
> >>> options list for now as this would also have some advantages :-)
> >>>
> >>> @Max:
> >>> Removing the slice id and passing all parameters works, that’s really
> >>> useful information. We might stick with this until slugs are available.
> >>> Thanks very much!
> >>> The charts can be static, but we need filtering on certain IDs.
> Something
> >>> like a product ID filter for example. But this seem to work ok with the
> >>> approach by adding a simple filter :-)
> >>>
> >>> Rison would be awesome for debugging and developing for sure!Even
> though
> >>> UUIDs would solve our problem they can get a pain pretty quick if not
> >>> architected very thoroughly. You have to use hashes in a consistent way
> >>> (which data/column do you use? What happens with added columns on DDL
> >>> updates etc) and dealing with those is non trivial when there’s no good
> >>> transportable way in generating those across application and DBs. Slug
> >>> seems to abstract the problem [at least the one we have] a lot better
> and
> >>> simpler at the same time.
> >>>
> >>> Dennis
> >>>
> >>>> On 18. Jun 2020, at 02:38, Erik Ritter 
> wrote:
> >>>>
> >>>> Hi Dennis,
> >>>>
> >>>> You mention that cloning the complete Superset database seems overkill
> >>>> here, but for our use case, we've found that copying almost the entire
> >>>> Superset db into our dev and staging environments solves these types
> of
> >>>> issues for us. To ensure the process doesn't take too long, we exclude
> >>> the
> >>>> `logs` and the `queries` tables from our DB dump, but everything else
> we
> >>>> copy straight from prod to dev and staging for testing purposes.
> >>>>
> >>>> I know this doesn't address a case where you build a chart in dev and
> >>> want
> >>>> to move it to prod, but that's not a pattern we've really seen or
> needed
> >>> in
> >>>> our deployment.
> >>>>
> >>>> Hope this helps!
> >>>> Erik
> >>>>
> >>>> On Wed, Jun 17, 2020 at 7:46 AM Maxime Beauchemin <
> >>>> maximebeauche...@gmail.com> wrote:
> >>>>
> >>>>> Few thoughts:
> >>>>> - did you try removing the id? this should work without the id since
> >>> it's
> >>>>> totally possible to have an explore session without a saved chart
> >>>>> - we spoke in the past about introducing *uuids* for
> >>> exportable/importable
> >>>>> objects that would be consistent across superset instances
> >>>>> - slugs for chart would help here, and should be easy to implement -
> we
> >>>>> need that regardless
> >>>>> - side note: it'd be great to userison here for more readable URL
> >>> encoding
> >>>>> - more generally - should an embeddable snippet point to a chart or a
> >>> state
> >>>>> of an explore session? I think bo

FYI - Forked NVD3

[Maxime Beauchemin]

Just an FYI that I forked NVD3 last night.
https://github.com/apache-superset/superset-ui/pull/615

I reached out to the maintainers more than a week ago to offer help but
they're not responsive.
https://github.com/novus/nvd3/issues/

Happy to grant access to the npm package to committers/PMC, do we have a
publish list of all of the committers/PMC npm usernames somewhere?

The primary/trunk branch had fixes we've been needing for years that never
got released, and it's likely that we need to patch/tweak the lib in the
future.

The goal is really just to be able to patch things, clearly we're not
investing further in NVD3, the plan being to move towards some other
library, echarts  being a top
contender.

Max

Re: Addressing Charts directly / how to handle embedding in dev, stage, prod cycle?

[Maxime Beauchemin]

I meant uuid in its pure form (just a universal unique identifier), not a
fingerprint/hash of the object.

Currently the importer has to keep track of the "export_object_id" to try
to upsert properly if the same object is re-imported. It can have collision
issue when multiple systems are involved and has other disadvantages.

Max

On Thu, Jun 18, 2020 at 6:35 AM Dennis Meyer  wrote:

> @Eric:
> Thanks for the feedback Eric. It’s good to know. We’ll keep it in the
> options list for now as this would also have some advantages :-)
>
> @Max:
> Removing the slice id and passing all parameters works, that’s really
> useful information. We might stick with this until slugs are available.
> Thanks very much!
> The charts can be static, but we need filtering on certain IDs. Something
> like a product ID filter for example. But this seem to work ok with the
> approach by adding a simple filter :-)
>
> Rison would be awesome for debugging and developing for sure!Even though
> UUIDs would solve our problem they can get a pain pretty quick if not
> architected very thoroughly. You have to use hashes in a consistent way
> (which data/column do you use? What happens with added columns on DDL
> updates etc) and dealing with those is non trivial when there’s no good
> transportable way in generating those across application and DBs. Slug
> seems to abstract the problem [at least the one we have] a lot better and
> simpler at the same time.
>
> Dennis
>
> > On 18. Jun 2020, at 02:38, Erik Ritter  wrote:
> >
> > Hi Dennis,
> >
> > You mention that cloning the complete Superset database seems overkill
> > here, but for our use case, we've found that copying almost the entire
> > Superset db into our dev and staging environments solves these types of
> > issues for us. To ensure the process doesn't take too long, we exclude
> the
> > `logs` and the `queries` tables from our DB dump, but everything else we
> > copy straight from prod to dev and staging for testing purposes.
> >
> > I know this doesn't address a case where you build a chart in dev and
> want
> > to move it to prod, but that's not a pattern we've really seen or needed
> in
> > our deployment.
> >
> > Hope this helps!
> > Erik
> >
> > On Wed, Jun 17, 2020 at 7:46 AM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> >> Few thoughts:
> >> - did you try removing the id? this should work without the id since
> it's
> >> totally possible to have an explore session without a saved chart
> >> - we spoke in the past about introducing *uuids* for
> exportable/importable
> >> objects that would be consistent across superset instances
> >> - slugs for chart would help here, and should be easy to implement - we
> >> need that regardless
> >> - side note: it'd be great to userison here for more readable URL
> encoding
> >> - more generally - should an embeddable snippet point to a chart or a
> state
> >> of an explore session? I think both use-cases make sense
> >>
> >> On Tue, Jun 16, 2020 at 12:39 PM Dennis Meyer 
> wrote:
> >>
> >>> Sorry for broken formatting. The URL contains an “slice_id”, see edited
> >>> mail below for better readability.
> >>>
> >>>
> >>>>
> >>>> Hi,
> >>>>
> >>>> In the charts there’s an explicit embedding functionality generating
> >>> Iframe code:
> >>>>
> >>>>  >>>> width="600"
> >>>> height="400"
> >>>> seamless
> >>>> frameBorder="0"
> >>>> scrolling="no"
> >>>
> >>> src="…slice_id=306…”
> >>>
> >>>
> >>>> 
> >>>>
> >>>> It seems like there’s an ID hardcoded (see above) - which is very
> >>> unfortunate when exporting and importing again and the embedding is in
> >>> another application. In this case ids are different after import.
> >>>>
> >>>> I found a ticket about adding Slug to a chart, but it didn’t get too
> >>> much attention.
> >>>> https://github.com/apache/incubator-superset/issues/6537 <
> >>> https://github.com/apache/incubator-superset/issues/6537>
> >>>>
> >>>> Is there currently a way to address this better if I wanted to use
> >>> embedding code in dev, staging and prod environments?
> >>>> Cloning the complete Superset database seems overkill for this. Also
> it
> >>> won’t really work if you let production add charts by users and create
> >> some
> >>> major charts in dev you want to move to prod after some thorough
> testing.
> >>>>
> >>>> I’m glad for any suggestion.
> >>>>
> >>>> Thanks,
> >>>> Dennis
> >>>>
> >>>>
> >>>
> >>>
> >>
>
>

[DISCUSS] [SIP-47] modernize/facelift superset.apache.org

[Maxime Beauchemin]

Please read and chime in here:
https://github.com/apache/incubator-superset/issues/10088

Re: Addressing Charts directly / how to handle embedding in dev, stage, prod cycle?

[Maxime Beauchemin]

Few thoughts:
- did you try removing the id? this should work without the id since it's
totally possible to have an explore session without a saved chart
- we spoke in the past about introducing *uuids* for exportable/importable
objects that would be consistent across superset instances
- slugs for chart would help here, and should be easy to implement - we
need that regardless
- side note: it'd be great to use rison here for more readable URL encoding
- more generally - should an embeddable snippet point to a chart or a state
of an explore session? I think both use-cases make sense

On Tue, Jun 16, 2020 at 12:39 PM Dennis Meyer  wrote:

> Sorry for broken formatting. The URL contains an “slice_id”, see edited
> mail below for better readability.
>
>
> >
> > Hi,
> >
> > In the charts there’s an explicit embedding functionality generating
> Iframe code:
> >
> >  >  width="600"
> >  height="400"
> >  seamless
> >  frameBorder="0"
> >  scrolling="no"
>
> src="…slice_id=306…”
>
>
> > 
> >
> > It seems like there’s an ID hardcoded (see above) - which is very
> unfortunate when exporting and importing again and the embedding is in
> another application. In this case ids are different after import.
> >
> > I found a ticket about adding Slug to a chart, but it didn’t get too
> much attention.
> > https://github.com/apache/incubator-superset/issues/6537 <
> https://github.com/apache/incubator-superset/issues/6537>
> >
> > Is there currently a way to address this better if I wanted to use
> embedding code in dev, staging and prod environments?
> > Cloning the complete Superset database seems overkill for this. Also it
> won’t really work if you let production add charts by users and create some
> major charts in dev you want to move to prod after some thorough testing.
> >
> > I’m glad for any suggestion.
> >
> > Thanks,
> > Dennis
> >
> >
>
>

Re: Mentoring Superset

[Maxime Beauchemin]

+1!

I think we could really use the extra help. We currently have 2 mentors but
definitely could use a 3rd one.

Max

On Sat, Jun 6, 2020 at 1:00 AM Felix Cheung 
wrote:

> Hello,
>
> I spoke to Alan and wanted to offer my help to Apache Superset in the
> Incubator, and hope that I can help in its journey to graduation.
>
> I’m Committer and PMC member of Apache Spark, Zeppelin and I am currently
> mentoring Pinot and few other projects.
>
> Regards,
> Felix
>

Re: [ANNOUNCE] New committer and PPMC member: Jesse Yang

[Maxime Beauchemin]

So glad to have you on board Jesse!

On Fri, Jun 5, 2020 at 12:46 PM Krist Wongsuphasawat 
wrote:

> The Project Management Committee for Apache Superset (incubating)
> has invited Jesse Yang (@ktmud) to become a committer/PPMC member and we
> are pleased
> to announce that he has accepted.
>
> *Jesse Yang (@ktmud)* has been contributing steadily to the project since
> January 2020. During that time, he has authored 24 merged pull requests
>  (and
> 30
> more 
> on
> @superset-ui). Here are some of the highlights:
> * Migration of all Travis CI jobs to github actions.
> * Initiate the migration to merge @superset-ui and @superset-ui-plugins
> repositories.
> * Resolve the pain point about webpack and npm link that has been
> disrupting the development process for a long time.
> * Improve performance of table chart rendering.
> * Improve how BigNumber handle missing data.
> * Rewrite the metric selector to support easily rearrangement of metrics.
> * Provides thorough code reviews and covers a number of bug fixes.
>
> 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.
>
> Best regards,
>
> Krist W.
>

Re: Mentoring Apache Superset

[Maxime Beauchemin]

+1!

We are actively seeking more mentorship for our project/community

Max

On Fri, Jun 5, 2020 at 12:14 PM Furkan KAMACI 
wrote:

> Hi,
>
> I've seen at the general@incubator.a.o. mail list that Apache Superset
> needs an experienced mentor. I already mentor incubator projects right now
> and have time to dedicate for Superset.
>
> On the other hand, I am a committer and PMC of Druid. So, I am much
> interested in the project. I would like to help the Apache Superset as a
> mentor.
>
> Kind Regards,
> Furkan KAMACI
>

Re: Time for me to step down as a mentor

[Maxime Beauchemin]

We're grateful for your contribution Alan!

You'll always be welcomed and appreciated in this community regardless of
the mentor status :)

Max

On Thu, Jun 4, 2020 at 5:02 PM Alan Gates  wrote:

> Superset team, it's time for me to step down from the Incubator PMC, which
> means I need to step down from mentoring Superset.  I know you have faced
> quite a lot of changes in your mentors through your incubation, and I'm
> sorry I need to need leave before your time is up.  I will put out an
> appeal on the incubator general list for more mentors, plus you have Jim's
> capable help to rely on.
>
> Thank you for having me as a mentor.  I know your start in the incubator
> was challenging, but you've gone on to build a strong community and I'm
> confident you'll make a great TLP in the near future.
>
> Alan.
>

Re: Superset chart with percentiles with data from druid

[Maxime Beauchemin]

Hi Batchu, we recommend using the SQLAlchemy connector to druid from
Superset as we're slowly deprecating the native Druid connector.

Knowing that, you can use the SQL function "APPROX_QUANTILE(my_metric,
0.95)" just like you can as any other function
[image: Screen Shot 2020-06-02 at 11.00.26 PM.png]

On Tue, Jun 2, 2020 at 2:26 AM Batchu Venkatasai
 wrote:

> Hello everyone,
>
> We have a use case where we have to show the 90th, 95th and 99th
> percentile value of a dimension. I came across this
> https://druid.apache.org/docs/latest/development/extensions-core/datasketches-quantiles.html.
> Here we can add this extension to druid to get the 95th percentile
> aggregator. Is there any way to use this aggregator in Superset so that we
> can plot 90th, 95th, 99th percentile value of a dimension in a single chart
> or across multiple charts ? I found that we can define custom post
> agrregators in Superset for druid but not sure if we can define custom
> aggregators too.
>
> Thanks,
> Bharat
>

[DISCUSS][SIP-19] Simplify Superset's set of permissions

[Maxime Beauchemin]

This was written a while back, but never discussed or voted on. We're
looking to revive this effort and looking for input from the community.
https://github.com/apache/incubator-superset/issues/7510

The goal with the discuss thread is to help shape the proposal prior to a
future vote once the design settles.

Max

[ANNOUNCE] New IPMC member Bogdan Kyryliuk

[Maxime Beauchemin]

Hey!

The Project Management Committee (PMC) for Apache Superset has invited *Bogdan
Kyryliuk* 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.

In the name of the community as a whole, we're very glad to have you on
board, Bogdan!

Max

Virtual Apache Superset Meetup this Wednesday

[Maxime Beauchemin]

Hey!

Quick reminder that we're hosting our first Virtual Meetup this Wednesday:
https://www.meetup.com/SF-Bay-Area-Apache-Superset-Incubating-Meetup/events/270385151/

The agenda:
* Introduce what's new and highlights from the recent 0.36 release
* Committers Q&A, ask us anything! Please use this link to send and upvote
questions 

@committers! many of us have committed (no pun intended) to attend already,
but please try to make it and be available to answer questions!

Looking forward to seeing you there,

Max

Setting up a commit message linter

[Maxime Beauchemin]

Hey,

Check out https://github.com/apache/incubator-superset/pull/9655, I'm copy
pasting the PR description here:

---

Sets up gitlint , which enforces
Conventional
Commits  and sets up the
proper post commit hook to enforce it.

Also modifying the PR template to remove redundant annoying checkbox
section.

Once we adopt, I'm hoping we can modify our bot to auto-label based on the
commit type.


This requires a bit more discipline upfront, but should lead to a cleaner
`git log` in master, meaning better release notes and such.
---

Max

Re: Newcomers and Google Season of Docs

[Maxime Beauchemin]

Quick note to say we're looking at this thread and seeing how we can
support this at Preset. We'd love to help enable this, especially as we're
looking to hire someone to work on documentation / tutorials / howtos / FAQ.

Also somewhat related to helping onboard contributors: I was inspired by
Holden Karau's series of videos around contributing to Airflow a while back.
https://www.youtube.com/watch?v=6smd-x3CbCQ

I love the candid approach, leveraging her experience contributing to other
open source projects and showing a path forward for others. To me it showed
how hard it is even for senior engineers with open source experience and
ambition to start contributing to a project like Airflow.

We've been talking about improving / rewriting much of our CONTRIBUTING.md
to and make it easier to setup a docker-backed dev environment. Also
related - I used to label some issues with "starter-task" label as good
onramping tasks (small features or bug fixes), but haven't been doing this
in a while. We should start doing this again!

Max

On Mon, Apr 20, 2020 at 8:19 AM Erik Ritter  wrote:

> Hi Gaurav,
>
> Thanks for the thorough email with the great ideas for improving Superset!
> To address your two main points:
>
> The Google Season of Docs seems like a very worthwhile initiative to
> participate in, but I wonder if we can support it sufficiently within the
> Superset organization. I see that we require 2 organization administrators
> and at least 2 open source mentors for the documentation writers to
> participate in the program. While I suspect many people would be interested
> in helping out as mentors, it's unclear what the workload required is for
> the organization administrator role within the program.
>
> Additionally, since the deadline for registration is May 4th, it might not
> be possible to put together an application within this time frame. While
> I'm not counting out the ability for us to participate, I'd expect that
> we'd need at least 2 Commiters/PPMC members willing to own this project. I
> would be happy to be one of them in a supporting role, but I think we need
> someone else willing to step up and drive the application process as I'm
> quite busy already this quarter. If anyone else wanted to volunteer then we
> could continue this conversation in a Slack channel to try and nail down
> details if we think it's worthwhile to apply.
>
> As for improving the curve for newcomers/students, I'm all in favor for the
> standard of tagging beginner issues as "good first issue". I believe we
> have a bot that we can use so that anyone can add tags to issues if they
> feel they're good first issues (is this correct Max?), and I'd also like to
> autogenerate some issues for TypeScript conversion that would be good first
> issues as well. In general, providing a good entry point for new
> contributors is important to maintaining and growing the Superset
> community, and I think most of us would be in favor of making it easier for
> new contributors to participate.
>
> Thanks again for your email and your ideas!
> Erik Ritter
>
> On Sat, Apr 18, 2020 at 10:07 AM Gaurav Agrawal <
> agrawalgaurav1...@gmail.com>
> wrote:
>
> > Hi Everyone,
> >
> > I am Gaurav Agrawal, a student who often likes to work on superset and
> > engage with the community.
> >
> > I am aware that superset has recently been appreciated for improving the
> > docs, but I feel for further improvements and project's outreach with
> > students around the world it could be really nice for it to participate
> in
> > Google Season of Docs.
> >
> > It's deadline for Organizations is very near, around 4th May is the last
> > date.
> >
> >
> > As It comes under Apache so I am not completely sure about project's
> > policies and procedures for the same.
> >
> >
> > The second thing is about improving the curve for newcomers and students,
> > one such great trick for doing such thing is Newcomer issues, this is a
> > very popular and established way which many open source projects adopt.
> > They leave many issues explicitly which are not so urgent and are
> newcomer
> > friendly for students and newcomers by labelling them as "newcomers" or
> > "good first issue" .
> >
> > In some cases developers even leave comments that can make solving the
> > issue really easy.
> >
> >
> > If this is a feasible option for Superset I would really like to see this
> > happening so that we can have more and more people getting comfortable
> and
> > started with it. I feel that for any open source project newcomers are a
> > great and for students/newcomers themselves Open source is  a great way
> to
> > learning a lot of things like coding, community engagement, distributed
> > development workflow etc.
> >
> >
> > Thanks for your time and consideration, hope that these ideas will be
> > considered.
> >
> >
> > Best Regards,
> > Gaurav
> >
>

Re: Superset support for Druid with Kerberos authentication

[Maxime Beauchemin]

I think Kerberos needs to be supported by the driver first (pydruid) . This
seems relevant: https://github.com/druid-io/pydruid/pull/126

Note that pydruid contains both the native driver wrapper and the
SQLAlchemy dialect / dbapi driver.

Max


On Fri, Apr 17, 2020 at 12:44 AM Luca Toscano 
wrote:

> Hi Maxime,
>
> I have never experimented with Druid + Kerberos with Superset (but
> will surely do in the future), do you know if there are any snipped of
> configuration for Druid with SQLAlchemy to enable kerberos? Something
> like
> https://github.com/apache/incubator-superset/issues/8794#issuecomment-605603773
> but for Druid. It would be great to have a doc page somewhere with
> these kind of snippets to link people to it (or a markdown doc in the
> repo).
>
> Thanks in advance,
>
> Luca
>
> On Fri, Apr 17, 2020 at 6:43 AM Maxime Beauchemin  wrote:
> >
> > Hi Paula,
> >
> > I left a comment on your PR. It needs to be rebased and some comments
> need
> > to be addressed.
> >
> > Best,
> >
> > Max
> >
> > On Wed, Apr 15, 2020 at 6:19 PM Paula Morais 
> wrote:
> >
> > > Hello
> > >
> > > I have a druid cluster with kerberos authentication enabled.
> > >
> > > As of now, Superset doesn’t support kerberos authentication when
> sending
> > > the API calls to a druid cluster.
> > >
> > > There’s an open PR with a solution, but hasn’t been merged
> yet(comments not
> > > being addressed) -
> https://github.com/apache/incubator-superset/pull/7091
> > >
> > >
> > > Plus, Superset also uses pydruid in some of the queries to Druid. The
> > > version of pydruid used also doesn’t support kerberos authentication.
> > >
> > >
> > > I did a custom implementation so I could overcome the issue,
> > >
> > > Basically i'm doing a kinit every time a request is sent to Druid. Not
> an
> > > ideal solution, if we have many users setting up charts and dashboards,
> > > since the principal used is always the same (e.g. superset)
> > >
> > > The best solution would be to have implemented a general authentication
> > > function, once the application is started and  TGT renewal process
> once it
> > > expires.
> > >
> > >
> > > Is there an ongoing process for having this implemented?
> > >
> > >
> > > Kind regards
> > >
> > > Paula Morais Clavica
> > >
>

[DISCUSS] chart and dashboard ownership #9576

[Maxime Beauchemin]

More details, and let's have the DISCUSS thread here:
https://github.com/apache/incubator-superset/issues/9576

Re: [ANNOUNCE] Apache Superset (Incubating) version 0.36.0 Released

[Maxime Beauchemin]

Great work Ville, thanks for pushing this release through!

Also great work to all contributors, this takes an army. Amazing work.

Oh btw here's the [soon to be merged] changelog everyone:
https://github.com/apache/incubator-superset/pull/9570/files

Max

On Fri, Apr 17, 2020 at 7:53 AM Ville Brofeldt 
wrote:

> Hello Community,
>
> The Apache Superset (incubating) team is pleased to announce that Superset
> 0.36.0 has just been released.
>
> Apache Superset (incubating) is a modern, enterprise-ready business
> intelligence web application
>
> The official source release:
> https://downloads.apache.org/incubator/superset/0.36.0/
>
> The PyPI package: https://pypi.org/project/apache-superset/0.36.0/
>
> If you have any usage questions, or have problems when upgrading or
> find any problems about enhancements included in this release, please
> don't hesitate to let us know by sending feedback to this mailing
> list.
>
> =
> *Disclaimer*
>
> Apache Superset is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Incubator. 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.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: Superset support for Druid with Kerberos authentication

[Maxime Beauchemin]

Hi Paula,

I left a comment on your PR. It needs to be rebased and some comments need
to be addressed.

Best,

Max

On Wed, Apr 15, 2020 at 6:19 PM Paula Morais  wrote:

> Hello
>
> I have a druid cluster with kerberos authentication enabled.
>
> As of now, Superset doesn’t support kerberos authentication when sending
> the API calls to a druid cluster.
>
> There’s an open PR with a solution, but hasn’t been merged yet(comments not
> being addressed) - https://github.com/apache/incubator-superset/pull/7091
>
>
> Plus, Superset also uses pydruid in some of the queries to Druid. The
> version of pydruid used also doesn’t support kerberos authentication.
>
>
> I did a custom implementation so I could overcome the issue,
>
> Basically i'm doing a kinit every time a request is sent to Druid. Not an
> ideal solution, if we have many users setting up charts and dashboards,
> since the principal used is always the same (e.g. superset)
>
> The best solution would be to have implemented a general authentication
> function, once the application is started and  TGT renewal process once it
> expires.
>
>
> Is there an ongoing process for having this implemented?
>
>
> Kind regards
>
> Paula Morais Clavica
>

Re: RC3 table search box issue / Jinja - accessing Flask g

[Maxime Beauchemin]

Accessing `flask.g` in SQL Lab (in async mode) is tricky because the
execution is run on a celery worker where there's no Flask context. I think
we've done work before to make "current_username" available across the
board (async/not async).
http://superset.apache.org/sqllab.html#superset.jinja_context.current_username

We're also looking to move towards more of an async execution model across
the board as detailed here:
https://github.com/apache/incubator-superset/issues/9190. It'd be nice to
have access to some current user-related object in Jinja templates in the
async world too, and have some way to add user attributes (things like
team, department, ...) to that user objects so that they can be referenced
in that context. Clearly there are considerations around caching, security
and privacy in that area.

I'm curious as to what you're trying to accomplish, is it some sort of
row-level-security thing? We merge a RLS feature recently, wondering if
that may work for you.
https://github.com/apache/incubator-superset/pull/8699

Max

On Tue, Apr 7, 2020 at 2:22 PM Dennis Meyer  wrote:

> Hi,
>
> We encountered an issue with RC3 on Table search boxes. I know there’s
> been some bug reported on not emitting filters on selects, but now the
> search doesn’t function any more at all. I will get some time tomorrow to
> investigate further and track down a bug if I cannot overcome the issue.
> But someone might want to cross check if search boxes (in Table Chart
> advances settings) still works ok. Thanks!
>
> As I’m already writing and StackOverflow is dead silent: I was wondering
> how one could access the flask.g context using e.g. superset SQLLab. I'd
> like to set a value on login and later use it in Jinja. Is this possible?
>
>
> @expose('/login/', methods=['GET', 'POST'])
> def login(self):
> g.my_value = 'bar'
> …
> In SQLLab:
> {{flask.g.my_value}}
>
> https://stackoverflow.com/questions/61088292/how-can-i-attach-a-value-at-login-time-for-jinja-and-reuse-it-later-on-in-apache
> <
> https://stackoverflow.com/questions/61088292/how-can-i-attach-a-value-at-login-time-for-jinja-and-reuse-it-later-on-in-apache
> >
>
> Thanks,
> Dennis

Re: [VOTE] Release Apache Superset (incubating) 0.36.0 based on Superset 0.36.0rc3

[Maxime Beauchemin]

+1 (binding)

On Mon, Apr 6, 2020, 6:49 PM Evan Rusackas  wrote:

> +1, binding
>
> (Personal testing centered largely on Explore/viz, and recent UI component
> updates, FWIW)
>
> Evan Rusackas
> Preset, Inc.
> On Apr 2, 2020, 3:51 AM -0700, Ville Brofeldt ,
> wrote:
> > Hello Superset Community,
> >
> > This is a call for the vote to release Apache Superset
> > (incubating) version 0.36.0.
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/superset/0.36.0rc3/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-superset/tree/0.36.0rc3
> >
> > The Change Log for the release:
> > https://github.com/apache/incubator-superset/blob/0.36.0rc3/CHANGELOG.md
> >
> > public keys are available at:
> >
> > https://www.apache.org/dist/incubator/superset/KEYS
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > The Apache Superset (Incubating) Team
>

[DISCUSS] The need to version objects (dashboard, charts, ...) in Superset

[Maxime Beauchemin]

Hi all,

At our bi-weekly committers meeting, Grace brought up a user story around
versioning and collision around dashboards. We decided to *not* deep dive
in the context of the meeting and to start a thread here instead.

Some things to discuss:
* the more immediate need to prevent collisions, perhaps looking at the
last updated ts on an object and notifying the user / allowing them to
"save as" or force-overwrite, but making it clear who the last updater was,
...
* the need to keep track of version history log, and allow users to diff,
explore, and restore previous versions
* which objects are affected: dashboards for sure, charts too, "saved
queries", ...?

What are some next steps here: SIP(s)? Design work? Clarify ownership?

Max

Re: [VOTE] [SIP-38] Visualization plugin refactoring

[Maxime Beauchemin]

+1 binding

On Thu, Mar 26, 2020 at 12:03 PM Ville Brofeldt 
wrote:

> +1 binding
>
> Ville
>
> On Thu, Mar 26, 2020, 20:24 Evan Rusackas  wrote:
>
> > Superset Community,
> >
> > This is a call to vote for SIP-38: Visualization plugin refactoring
> >
> > Further details here:
> > https://github.com/apache/incubator-superset/issues/9187
> >
> > The vote will be open for at least 1 Week or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thank you!
> >
> > Evan Rusackas
> > Preset, Inc.
> >
>

Re: Presto, Superset and Kerberos

[Maxime Beauchemin]

Nice, thanks Bogdan!

On Tue, Mar 17, 2020 at 4:54 AM Luca Toscano  wrote:

> To keep archives happy: after some work Bogdan released PyHive 0.6.2 -
> https://pypi.org/project/PyHive/0.6.2 \o/
>
> This is a great example of cross-community work, thanks all for the
> help and time spent!
>
> Luca
>
> Il giorno mar 18 feb 2020 alle ore 19:08 Luca Toscano
>  ha scritto:
> >
> > Hi Bogdan,
> >
> > thanks a lot for the help, it is a great news! Totally ok with what
> > you said about relying on the community, I think it is something that
> > we all agree on. The problem was that nobody reviewed or merged
> > patches :)
> >
> > I would concentrate, if possible, in releasing 0.6.2 with the Kerberos
> > support, it shouldn't be a ton of work and a lot of people would
> > benefit from it. What is the best way to get to the release in PyPi?
> > Should we pick a github issue and start from there? (like
> > https://github.com/dropbox/PyHive/issues/288)
> >
> > Luca
> >
> > Il giorno mar 18 feb 2020 alle ore 18:44 Bogdan Kyryliuk
> >  ha scritto:
> > >
> > > Hey Luca and Maxime,
> > > we will be reviving the repo, however we would need to rely on the
> community for the contribution & testing.
> > > Happy to review & merge diffs & support the work for the new library
> release.
> > >
> > > Another quick thing, it is possible to do pip install from the github
> repository, that may be a quicker way to unblock yourself:
> > >
> https://stackoverflow.com/questions/15268953/how-to-install-python-package-from-github
> > >
> > >
> > >
> > >
> > > On Fri, Feb 7, 2020 at 1:18 AM Luca Toscano 
> wrote:
> > >>
> > >> Hi Maxime,
> > >>
> > >> thanks a lot for the follow up. I'd really like to be in the loop if
> > >> anything comes up! I can also help with PyHive if needed, even if it
> > >> seems that it would just need a new release for the moment (plus some
> > >> testing, that I can do for sure).
> > >>
> > >> About Druid, it is not a priority for me right now, but I'll try to
> > >> see what can be done during the next months and possibly send a PR :)
> > >>
> > >> Luca
> > >>
> > >> Il giorno ven 7 feb 2020 alle ore 08:03 Maxime Beauchemin
> > >>  ha scritto:
> > >> >
> > >> > Coincidentally I reached out to fellow Superset committer Bogdan
> Kyryliuk
> > >> > (cced) who's joined Dropbox to ask about the state of PyHive at
> Dropbox,
> > >> > and whether they would welcome help maintaining the project. We can
> keep
> > >> > you in the loop.
> > >> >
> > >> > About Druid, I'm a maintainer on PyDruid but realistically can't
> spend much
> > >> > time on it. I can certainly review / merge short PRs.
> > >> >
> > >> > Max
> > >> >
> > >> > On Thu, Feb 6, 2020 at 2:50 AM Luca Toscano 
> wrote:
> > >> >
> > >> > > Forgot to ask also what are the plans for Superset + Kerberos +
> Druid
> > >> > > (as far as I can see there are some pull requests opened) :)
> > >> > >
> > >> > > Luca
> > >> > >
> > >> > > Il giorno gio 6 feb 2020 alle ore 11:13 Luca Toscano
> > >> > >  ha scritto:
> > >> > > >
> > >> > > > Hi everybody,
> > >> > > >
> > >> > > > I am bringing up
> > >> > > > https://github.com/apache/incubator-superset/issues/8794 to
> the dev
> > >> > > > mailing list to reach a broader audience and see if there is
> any new
> > >> > > > idea about how to proceed. The TL;DR is that Presto
> > >> > > > (https://prestodb.io/) and Superset seems not working when
> Presto is
> > >> > > > authenticated via Kerberos. The main issue seems to be that the
> PyHive
> > >> > > > (used by Superset) project seems not active anymore (see
> > >> > > > https://github.com/dropbox/PyHive/issues/296) and
> unfortunately the
> > >> > > > last Pypi version available does not contain the code that
> Superset
> > >> > > > would need to work with Presto and Kerberos
> > >> > > > (
> > >> > >
> https://github.com/dropbox/PyHive/commit/6925cd74721cc474a02a6759490b2b4c8bef3831
> > >> > > ).
> > >> > > >
> > >> > > > Maybe there is somebody in this list that can reach out to
> DropBox and
> > >> > > > ask if they have plans for PyHive?
> > >> > > >
> > >> > > > Presto seems to be a really nice backend to use together with
> Druid
> > >> > > > for Superset, I'd love to see this problem unblocked.
> > >> > > >
> > >> > > > Thanks in advance!
> > >> > > >
> > >> > > > Luca
> > >> > >
> > >
> > >
> > >
> > > --
> > > Best regards,
> > > Bogdan Kyryliuk.
>

Re: [CANCELLED] [VOTE] Release Apache Superset (incubating) 0.36.0 based on Superset 0.36.0rc1

[Maxime Beauchemin]

Thanks Luca, we typically only push releases to pypi once they are voted in
following the Apache process. The ASF refers to them as "convenience
releases", and [mayy be] a liability to push one that is not approved
or contains incompatible license or IP.

But it should be possible to "pip install {release}.tar.gz" and bypass pypi.

Oh also there's a hack to pip install any Github tag too, just go to the
tag page https://github.com/apache/incubator-superset/releases/tag/0.36.0rc1,
copy the link address of the tarball (
https://github.com/apache/incubator-superset/archive/0.36.0rc1.tar.gz ) and
just install straight from that link: `pip install
https://github.com/apache/incubator-superset/archive/0.36.0rc1.tar.gz`

On Tue, Mar 10, 2020 at 10:42 AM Luca Toscano 
wrote:

> Hi everybody,
>
> not sure if pertinent or not to this thread, but I'd be happy to test
> Superset in my testing environment and provide feedback (we already
> have a ton of dashboards and plugin used) but we currently deploy a
> venv created via pip, so the new version would need to be pushed to
> PyPI first. I am not sure if this is a problem for whoever is the
> release manager or not, but it would be great to have RC candidates in
> PyPI :)
>
> I also have to say that from 0.28 to 0.35 there has to be a huge
> improvement in the release process, thanks a lot for all the work
> done!
>
> Luca
>
> Il giorno mar 10 mar 2020 alle ore 18:30 Maxime Beauchemin
>  ha scritto:
> >
> > Side note, I tried to `npm link` the table visualization plugin to debug
> > this and ran into some issues. We really need to make it much easier to
> do
> > development in plugins.
> >
> > Max
> >
> > On Mon, Mar 9, 2020 at 11:01 PM Ville Brofeldt <
> ville.v.brofe...@gmail.com>
> > wrote:
> >
> > > Hi all,
> > >
> > > due to the presence of a few bugs in this RC, I am terminating this
> vote to
> > > be able to stabilize the 0.36.0 release. We will revert with a new RC
> once
> > > the critical blockers have been addressed.
> > >
> > > Ville
> > >
> > > On Sun, Mar 8, 2020 at 4:35 PM Bolke de Bruin 
> wrote:
> > >
> > > > imho this
> > > >
> > > > https://github.com/apache/incubator-superset/issues/8273
> > > >
> > > > Should be considered blocking. It's a regression that keeps us on
> 0.34
> > > >
> > > > So consider this my -1, non-binding
> > > >
> > > > Bolke
> > > >
> > > > Sent from my iPhone
> > > >
> > > > > On 7 Mar 2020, at 21:23, Ville Brofeldt <
> ville.v.brofe...@gmail.com>
> > > > wrote:
> > > > >
> > > > > Hello Superset Community,
> > > > >
> > > > >
> > > > > This is a call for the vote to release Apache Superset
> > > > >
> > > > > (incubating) version 0.36.0.
> > > > >
> > > > >
> > > > > The release candidate:
> > > > >
> > > > >
> https://dist.apache.org/repos/dist/dev/incubator/superset/0.36.0rc1/
> > > > >
> > > > >
> > > > > Git tag for the release:
> > > > >
> > > > > https://github.com/apache/incubator-superset/tree/0.36.0rc1
> > > > >
> > > > >
> > > > > The Change Log for the release:
> > > > >
> > > > >
> > >
> https://github.com/apache/incubator-superset/blob/0.36.0rc1/CHANGELOG.md
> > > > >
> > > > >
> > > > > public keys are available at:
> > > > >
> > > > >
> > > > > https://www.apache.org/dist/incubator/superset/KEYS
> > > > >
> > > > >
> > > > > The vote will be open for at least 72 hours or until the necessary
> > > number
> > > > >
> > > > > of votes are reached.
> > > > >
> > > > >
> > > > > Please vote accordingly:
> > > > >
> > > > >
> > > > > [ ] +1 approve
> > > > >
> > > > > [ ] +0 no opinion
> > > > >
> > > > > [ ] -1 disapprove with the reason
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > The Apache Superset (Incubating) Team
> > > >
> > >
>

Re: [VOTE] [SIP-39] Global Async Query Support

[Maxime Beauchemin]

+1 (binding)

On Tue, Mar 10, 2020 at 4:09 PM William Barrett  wrote:

> +1 (non-binding)
>
> Will Barrett
> Staff Software Engineer
> Preset, Inc. | https://preset.io
> On Mar 10, 2020, 4:06 PM -0700, Erik Ritter ,
> wrote:
> > +1 (non-binding)
> >
> > Erik
> >
> > On Tue, Mar 10, 2020 at 3:49 PM Craig Rueda 
> wrote:
> >
> > > +1 binding
> > >
> > > -Craig
> > > 
> > > From: Evan Rusackas 
> > > Sent: Tuesday, March 10, 2020 3:44 PM
> > > To: d...@superset.apache.org 
> > > Subject: [VOTE] [SIP-39] Global Async Query Support
> > >
> > > Superset Community,
> > >
> > > This is a call to vote for SIP-39: Global Async Query Support
> > >
> > > Further details here:
> > > https://github.com/apache/incubator-superset/issues/9190
> > >
> > > The vote will be open for at least 1 Week or until the necessary
> number of
> > > votes are reached.
> > >
> > > Please vote accordingly:
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Thank you!
> > >
> > > Evan Rusackas
> > > Preset, Inc.
> > >
>

Re: [VOTE] [SIP-37] Proposal to implement CSS-in-JS using Emotion

[Maxime Beauchemin]

+1 (binding)

On Tue, Mar 10, 2020 at 4:06 PM Erik Ritter  wrote:

> +1 (non-binding)
>
> Erik
>
> On Tue, Feb 25, 2020 at 2:24 PM William Barrett  wrote:
>
> > +1 (non-binding)
> >
> > Will Barrett
> > Staff Software Engineer
> > Preset, Inc. | https://preset.io
> > On Feb 25, 2020, 2:12 PM -0800, Rob DiCiuccio , wrote:
> > > +1 (non-binding)
> > >
> > > On Tue, Feb 25, 2020 at 10:00 AM Evan Rusackas  wrote:
> > >
> > > > Hello Superset Community,
> > > >
> > > > This is a call to vote for SIP-37 Proposal to implement CSS-in-JS
> using
> > > > Emotion.
> > > >
> > > > Further details here:
> > > > https://github.com/apache/incubator-superset/issues/9123
> > > >
> > > > The vote will be open for at least 1 Week or until the necessary
> number
> > > > of votes are reached.
> > > >
> > > > Please vote accordingly:
> > > >
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > Thanks,
> > > >
> > > > Evan Rusackas
> > > > Preset, Inc.
> > > >
> > >
> > >
> > > --
> > >
> > > *Rob DiCiuccio*
> > > Director of Engineering
> > > Preset | https://preset.io
> >
>

Re: [CANCELLED] [VOTE] Release Apache Superset (incubating) 0.36.0 based on Superset 0.36.0rc1

[Maxime Beauchemin]

Side note, I tried to `npm link` the table visualization plugin to debug
this and ran into some issues. We really need to make it much easier to do
development in plugins.

Max

On Mon, Mar 9, 2020 at 11:01 PM Ville Brofeldt 
wrote:

> Hi all,
>
> due to the presence of a few bugs in this RC, I am terminating this vote to
> be able to stabilize the 0.36.0 release. We will revert with a new RC once
> the critical blockers have been addressed.
>
> Ville
>
> On Sun, Mar 8, 2020 at 4:35 PM Bolke de Bruin  wrote:
>
> > imho this
> >
> > https://github.com/apache/incubator-superset/issues/8273
> >
> > Should be considered blocking. It's a regression that keeps us on 0.34
> >
> > So consider this my -1, non-binding
> >
> > Bolke
> >
> > Sent from my iPhone
> >
> > > On 7 Mar 2020, at 21:23, Ville Brofeldt 
> > wrote:
> > >
> > > Hello Superset Community,
> > >
> > >
> > > This is a call for the vote to release Apache Superset
> > >
> > > (incubating) version 0.36.0.
> > >
> > >
> > > The release candidate:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/superset/0.36.0rc1/
> > >
> > >
> > > Git tag for the release:
> > >
> > > https://github.com/apache/incubator-superset/tree/0.36.0rc1
> > >
> > >
> > > The Change Log for the release:
> > >
> > >
> https://github.com/apache/incubator-superset/blob/0.36.0rc1/CHANGELOG.md
> > >
> > >
> > > public keys are available at:
> > >
> > >
> > > https://www.apache.org/dist/incubator/superset/KEYS
> > >
> > >
> > > The vote will be open for at least 72 hours or until the necessary
> number
> > >
> > > of votes are reached.
> > >
> > >
> > > Please vote accordingly:
> > >
> > >
> > > [ ] +1 approve
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 disapprove with the reason
> > >
> > >
> > > Thanks,
> > >
> > > The Apache Superset (Incubating) Team
> >
>

Re: [VOTE] [SIP-26] Proposal for Implementing Connection Pooling for Analytics Database Connections

[Maxime Beauchemin]

+1 binding

On Tue, Mar 3, 2020 at 10:40 AM Craig Rueda  wrote:

> +1 binding
> 
> From: daniel gaspar 
> Sent: Tuesday, March 3, 2020 10:22 AM
> To: d...@superset.apache.org 
> Subject: [VOTE] [SIP-26] Proposal for Implementing Connection Pooling for
> Analytics Database Connections
>
> Superset Community,
>
> This is a call to vote for SIP-26 Proposal for Implementing Connection
> Pooling for Analytics Database Connections
>
> Further details here:
> https://github.com/apache/incubator-superset/issues/8574
>
> The vote will be open for at least 1 Week or until the necessary number of
> votes are reached.
>
> Please vote accordingly:
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks!
> Daniel Gaspar
>

Re: [VOTE] [SIP-40] Proposal for Custom Error Messages

[Maxime Beauchemin]

+1 (binding)

On Tue, Mar 3, 2020 at 12:42 PM Chris Williams
 wrote:

> +1
>
> (also, binding/non-binding doesn't make sense for SIPs, right? since they
> are a Superset-specific concept/not Apache?)
>
> Chris
>
> Data Visualization
> San Francisco
>
>
> On Mon, Mar 2, 2020 at 9:55 PM Ville Brofeldt 
> wrote:
>
> > +1 (binding)
> >
> > Ville
> >
> > On Tue, Mar 3, 2020 at 12:39 AM Erik Ritter 
> > wrote:
> >
> > > Superset Community,
> > >
> > > This is a call to vote for SIP-40: Proposal for Custom Error Messages.
> > >
> > > Further details here:
> > > https://github.com/apache/incubator-superset/issues/9194
> > >
> > > The vote will be open for at least 1 Week or until the necessary number
> > of
> > > votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Thanks!
> > > Erik
> > >
> >
>

Re: Podling Superset Report Reminder - March 2020

[Maxime Beauchemin]

I think we're all set, thanks Evan for writing and Jakob for reviewing /
approving!
https://cwiki.apache.org/confluence/display/INCUBATOR/March2020#superset

Max

On Sun, Mar 1, 2020 at 12:10 PM  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 18 March 2020, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, March 04).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
> *   How does the podling rate their own maturity.
>
> This should be appended to the Incubator Wiki page at:
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/March2020
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Note: The format of the report has changed to use markdown.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>

Re: Podling Superset Report Reminder - March 2020

[Maxime Beauchemin]

more directly: *@mentors* please review our podling report!
https://cwiki.apache.org/confluence/display/INCUBATOR/March2020#superset

On Mon, Feb 24, 2020 at 3:08 PM Evan Rusackas  wrote:

> Hi Justin,
>
> Max and I did a first take of the podling report. If you and the other
> mentors could take a look and let us know if you spot any errors or
> omissions, we’ll be happy to make any necessary adjustments.
>
> Thank you,
>
> Evan Rusackas
> Preset, Inc.
> On Feb 20, 2020, 4:43 PM -0800, jmcl...@apache.org, wrote:
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 18 March 2020, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, March 04).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Candidate names should not be made public before people are actually
> > elected, so please do not include the names of potential committers or
> > PPMC members in your report.
> >
> > Thanks,
> >
> > The Apache Incubator PMC
> >
> > Submitting your Report
> >
> > --
> >
> > Your report should contain the following:
> >
> > * Your project name
> > * A brief description of your project, which assumes no knowledge of
> > the project or necessarily of its field
> > * A list of the three most important issues to address in the move
> > towards graduation.
> > * Any issues that the Incubator PMC or ASF Board might wish/need to be
> > aware of
> > * How has the community developed since the last report
> > * How has the project developed since the last report.
> > * How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://cwiki.apache.org/confluence/display/INCUBATOR/March2020
> >
> > Note: This is manually populated. You may need to wait a little before
> > this page is created from a template.
> >
> > Note: The format of the report has changed to use markdown.
> >
> > Mentors
> > ---
> >
> > Mentors should review reports for their project(s) and sign them off on
> > the Incubator wiki page. Signing off reports shows that you are
> > following the project - projects that are not signed may raise alarms
> > for the Incubator PMC.
> >
> > Incubator PMC
>

Re: [DISCUSS] SIP-35 Proposal for Improving Superset’s Python Code Organization

[Maxime Beauchemin]

+1 (binding)

though the email thread subject should say "[VOTE] SIP-35 Proposal for
Improving Superset’s Python Code Organization" instead of "[DISCUSS]..."

On Mon, Feb 24, 2020 at 4:54 PM Craig Rueda  wrote:

> +1 binding
> 
> From: Rob DiCiuccio 
> Sent: Monday, February 24, 2020 4:45 PM
> To: dev@superset.incubator.apache.org 
> Subject: Re: [DISCUSS] SIP-35 Proposal for Improving Superset’s Python
> Code Organization
>
> Note that this is a *new vote* for SIP-35, now that discussions are largely
> finished, and should replace the previous vote.
>
> +1 (non-binding)
>
> On Mon, Feb 24, 2020 at 4:39 PM Craig Rueda  wrote:
>
> > Please discuss & subscribe here:
> >
> > https://github.com/apache/incubator-superset/issues/9077
> >
>
>
> --
>
> *Rob DiCiuccio*
> Director of Engineering
> Preset | https://preset.io
>

[ANNOUNCE] new committer & PPMC member: Evan Rusackas

[Maxime Beauchemin]

The Project Management Committee (PMC) for Apache Superset
has invited Evan Rusackas 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.

In the name of the community as a whole, we're very glad to have you on
board, Evan!

Max

Github board to track SIPs

[Maxime Beauchemin]

Hi all,

With the multiplication of SIPs, it has gotten trickier to keep track of
their state over time. To help with this I created this Github board:
https://github.com/apache/incubator-superset/projects/7

While adding the SIPs on the board, it appeared to me that many SIPs never
got a proper [DISCUSS], [VOTE] or [RESULTS] thread.

@committers / @authors, please take the time to update / close your SIPs as
needed.

Thanks,

Max

[RESULT][VOTE] SIP-34 Proposal to establish a new design direction, system, and process for Superset

[Maxime Beauchemin]

Thanks to all participants, the vote for SIP-34 is now closed.

The vote PASSED with 11 +1 and 0 -1 votes:

Binding votes:
- Grace
- Daniel
- Craig
- Max
- Ville

Further details here:
https://github.com/apache/incubator-superset/issues/8976

Thanks,
Max


On Tue, Feb 4, 2020 at 10:11 PM Arthur Wiedmer  wrote:

> +1 (non-binding)
>
> On Sun, Feb 2, 2020 at 9:56 PM Maxime Beauchemin <
> maximebeauche...@gmail.com>
> wrote:
>
> > Superset Community,
> >
> > This is a call to vote for SIP-34: Proposal to establish a new design
> > direction, system, and process for Superset
> >
> > Further details here:
> > https://github.com/apache/incubator-superset/issues/8976
> >
> > The vote will be open for at least 1 Week or until the necessary number
> of
> > votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Best,
> >
> > Max
> >
>

Re: Superset and kerberized Druid cluster

[Maxime Beauchemin]

Marco, to unsubscribe, send an email to

dev-unsubscr...@superset.incubator.apache.org

On Thu, Feb 20, 2020 at 2:26 PM Marco Lobo  wrote:

> please take me of this email list.
>
> Marco LoboChief Customer Officer atDispersee:ma...@disperse.io
> m: +1 (929) 505 6542
>
>
>
>
>
> On Thu, Feb 20, 2020 10:24 PM, lakshman pervatoju
> lakshman.pervat...@gmail.com
> wrote:
>
>
>
>
>
>
> On 2020/02/20 17:11:07, Maxime Beauchemin 
> wrote:
>
> > Python 2.7 isn't supported anymore, neither by Superset or Python
> itself...
>
> > We run test against 3.6 and recommend that for now.
>
> >
>
> > Max
>
> >
>
> > On Thu, Feb 20, 2020 at 8:52 AM Brannon, Terrence
>
> >  wrote:
>
> >
>
> > > Hi Lakshman:
>
> > > * I did a quick google search for your error message and this Superset
>
> > > issue came up -
> https://github.com/apache/incubator-superset/issues/8425
>
> > > ... which version of superset are you running? In fact, as a word to
>
> > > Superset: is there a standard bug reporting format that a user can
> generate
>
> > > via a single command to give all details relevant to a problem?
>
> > >
>
> > > ALSO: apparently this error occurs with some people who are running
> 0.35.1
>
> > > -
>
> > >
>
> https://stackoverflow.com/questions/59289314/superset-0-35-1-druid-error-name-pydruid-is-not-defined
>
> > >
>
> > > * Superset has "deprecated support for Python 2" -
>
> > > https://superset.incubator.apache.org/installation.html ... why are
> you
>
> > > running on Python 2 instead of 3.6?
>
> > >
>
> > > -Original Message-
>
> > > From: lakshman pervatoju 
>
> > > Sent: Thursday, February 20, 2020 8:28 AM
>
> > > To: d...@superset.apache.org
>
> > > Subject: [EXTERNAL] Superset and kerberized Druid cluster
>
> > >
>
> > > Hi Everybody,
>
> > > We have a kerberized druid cluster and have few datasources created.
>
> > > Installed superset and trying to Load Druid data source and get the
> below
>
> > >
>
> > > "name 'PyDruid' is not defined"
>
> > >
>
> > > but I am able to import PyDruid.
>
> > > The current version of python we have is 2.7.5
>
> > >
>
> > > Note: we have set up Basic authentication for druid and while adding
> druid
>
> > > cluster we did provide these credentials.
>
> > >
>
> > > Also, looking into how AD authentication and superset work together.
>
> > >
>
> > > Appreciate the help.
>
> > > Thanks in Advance,
>
> > >
>
> > >
>
> > > U.S. BANCORP made the following annotations
>
> > > -
>
> > > Electronic Privacy Notice. This e-mail, and any attachments, contains
>
> > > information that is, or may be, covered by electronic communications
>
> > > privacy laws, and is also confidential and proprietary in nature. If
> you
>
> > > are not the intended recipient, please be advised that you are legally
>
> > > prohibited from retaining, using, copying, distributing, or otherwise
>
> > > disclosing this information in any manner. Instead, please reply to the
>
> > > sender that you have received this communication in error, and then
>
> > > immediately delete it. Thank you in advance for your cooperation.
>
> > >
>
> > > -
>
> > >
>
> > Hi Brannon,
>
> Thank you for your response.
>
> We were running superset on gunicorn and see multiple instances of
> superset on
> the server.
>
> Killed those and started as single web server (as mentioned in the superset
> installation guide) and now see druid data sources are being listed.
>
>
>
>
> But unable to retrieve data from those data sources.
>
> Also, superset is not coming up on the server's DNS URL, its only coming up
> using the IP address.

Re: Superset and kerberized Druid cluster

[Maxime Beauchemin]

Python 2.7 isn't supported anymore, neither by Superset or Python itself...
We run test against 3.6 and recommend that for now.

Max

On Thu, Feb 20, 2020 at 8:52 AM Brannon, Terrence
 wrote:

> Hi Lakshman:
> * I did a quick google search for your error message and this Superset
> issue came up - https://github.com/apache/incubator-superset/issues/8425
>  ... which version of superset are you running? In fact, as a word to
> Superset: is there a standard bug reporting format that a user can generate
> via a single command to give all details relevant to a problem?
>
> ALSO: apparently this error occurs with some people who are running 0.35.1
> -
> https://stackoverflow.com/questions/59289314/superset-0-35-1-druid-error-name-pydruid-is-not-defined
>
> * Superset has "deprecated support for Python 2" -
> https://superset.incubator.apache.org/installation.html  ... why are you
> running on Python 2 instead of 3.6?
>
> -Original Message-
> From: lakshman pervatoju 
> Sent: Thursday, February 20, 2020 8:28 AM
> To: d...@superset.apache.org
> Subject: [EXTERNAL] Superset and kerberized Druid cluster
>
> Hi Everybody,
> We have a kerberized druid cluster and have few datasources created.
> Installed superset and trying to Load Druid data source and get the below
>
> "name 'PyDruid' is not defined"
>
> but I am able to import PyDruid.
> The current version of python we have is 2.7.5
>
> Note: we have set up Basic authentication for druid and while adding druid
> cluster we did provide these credentials.
>
> Also, looking into how AD authentication and superset work together.
>
> Appreciate the help.
> Thanks in Advance,
>
>
> U.S. BANCORP made the following annotations
> -
> Electronic Privacy Notice. This e-mail, and any attachments, contains
> information that is, or may be, covered by electronic communications
> privacy laws, and is also confidential and proprietary in nature. If you
> are not the intended recipient, please be advised that you are legally
> prohibited from retaining, using, copying, distributing, or otherwise
> disclosing this information in any manner. Instead, please reply to the
> sender that you have received this communication in error, and then
> immediately delete it. Thank you in advance for your cooperation.
>
> -
>

Re: Re: [VOTE] [SIP-26] Proposal for Implementing Connection Pooling for Analytics Database Connections

[Maxime Beauchemin]

Yes, sorry I thought we had sent the [DISCUSS] notice pointing to the
Github issue a while back.

The SIP process is well documented in SIP-0
<https://github.com/apache/incubator-superset/issues/5602> and we're
supposed to send a [DISCUSS] notice to dev@ prior to the vote.

Let's revive the conversation in the Github issue and re-kick off a fresh
vote in ~a week.

Max

On Tue, Feb 18, 2020 at 2:16 PM Erik Ritter 
wrote:

> I think discussion occurring in the Github issue is ideal. However, as I
> (and many others) don't often view notifications from issues being created,
> we depend on the [DISCUSS] email to alert us to a new SIP being created.
>
> Erik
>
> On Tue, Feb 18, 2020 at 1:57 PM Brannon, Terrence
>  wrote:
>
> > It seems that discussion also occurs in the github issue itself:
> > https://github.com/apache/incubator-superset/issues/8574
> >
> > Do you desire a single place of discussion? Or is it OK for discussion to
> > occur in the github ticket as well the dev-list?
> >
> > -Original Message-
> > From: Erik Ritter 
> > Sent: Tuesday, February 18, 2020 11:23 AM
> > To: dev@superset.incubator.apache.org
> > Cc: d...@superset.apache.org
> > Subject: [EXTERNAL] Re: [VOTE] [SIP-26] Proposal for Implementing
> > Connection Pooling for Analytics Database Connections
> >
> > -1 (non binding)
> >
> > It appears that this SIP did not have a [DISCUSS] email sent to the dev
> > list (see mailing list history here:
> >
> >
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.apache.org_list.html-3Fdev-40superset.apache.org-3Alte-3D1y-3ASIP-2D26&d=DwIFaQ&c=1hIq-C3ayh4zm6RZ7m4R2A&r=YFv754w0-1hOQn5jCB3GpLIc7nupwqAk7x9jHnHpUVw&m=E8BZqaFzEwFAZ1PA2nZUTav7ln9yEwst8LDPhLoYO8M&s=Yxfh76rdED68gjVEHvvclUe0AEa7-Mlsq5d_DkAwpYM&e=
> > ), so I'm concerned that everyone who wanted to provide feedback didn't
> get
> > a chance. Could we make this the [DISCUSS] thread then revote a week from
> > now?
> >
> > Thanks,
> > Erik
> >
> > On Tue, Feb 18, 2020 at 7:22 AM Craig Rueda 
> wrote:
> >
> > > +1 binding
> > >
> > > - Craig
> > >
> > > > On Feb 17, 2020, at 9:46 PM, Grace Guo
> > > > 
> > > wrote:
> > > >
> > > > +1 binding
> > > >
> > > > - Grace
> > > >
> > > >> On Feb 14, 2020, at 2:41 PM, Maxime Beauchemin <
> > > maximebeauche...@gmail.com> wrote:
> > > >>
> > > >> Superset Community,
> > > >>
> > > >> This is a call to vote for SIP-26 Proposal for Implementing
> > > >> Connection Pooling for Analytics Database Connections
> > > >>
> > > >> Further details here:
> > > >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apa
> > > >> che_incubator-2Dsuperset_issues_8574&d=DwIFaQ&c=1hIq-C3ayh4zm6RZ7m4
> > > >> R2A&r=YFv754w0-1hOQn5jCB3GpLIc7nupwqAk7x9jHnHpUVw&m=E8BZqaFzEwFAZ1P
> > > >> A2nZUTav7ln9yEwst8LDPhLoYO8M&s=USx_1rKoin5B7pP1oQ3gJxRAj3D7fowah4AT
> > > >> veNYt1s&e=
> > > >>
> > > >> The vote will be open for at least 1 Week or until the necessary
> > > >> number
> > > of
> > > >> votes are reached.
> > > >>
> > > >> Please vote accordingly:
> > > >>
> > > >> [ ] +1 approve
> > > >> [ ] +0 no opinion
> > > >> [ ] -1 disapprove with the reason
> > > >>
> > > >> Thanks!
> > > >>
> > > >> Max
> > > >
> > >
> >
> >
> > U.S. BANCORP made the following annotations
> > -
> > Electronic Privacy Notice. This e-mail, and any attachments, contains
> > information that is, or may be, covered by electronic communications
> > privacy laws, and is also confidential and proprietary in nature. If you
> > are not the intended recipient, please be advised that you are legally
> > prohibited from retaining, using, copying, distributing, or otherwise
> > disclosing this information in any manner. Instead, please reply to the
> > sender that you have received this communication in error, and then
> > immediately delete it. Thank you in advance for your cooperation.
> >
> > -
> >
>

[VOTE] [SIP-26] Proposal for Implementing Connection Pooling for Analytics Database Connections

[Maxime Beauchemin]

Superset Community,

This is a call to vote for SIP-26 Proposal for Implementing Connection
Pooling for Analytics Database Connections

Further details here:
https://github.com/apache/incubator-superset/issues/8574

The vote will be open for at least 1 Week or until the necessary number of
votes are reached.

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks!

Max

Re: [VOTE] [SIP-36] Proposal for standardizing use of TypeScript

[Maxime Beauchemin]

+1 (binding)

Max

On Tue, Feb 11, 2020 at 12:44 PM Chris Williams
 wrote:

> +1 (binding)
>
> Chris
>
> Data Visualization
> San Francisco
>
>
> On Tue, Feb 11, 2020 at 11:20 AM Ville Brofeldt <
> ville.v.brofe...@gmail.com>
> wrote:
>
> > +1 (binding)
> >
> > Ville
> >
> > On Tue, Feb 11, 2020 at 3:14 AM Erik Ritter 
> > wrote:
> >
> > > Superset Community,
> > >
> > > This is a call to vote for SIP-36: Proposal for standardizing use of
> > > TypeScript.
> > >
> > > Further details here:
> > > https://github.com/apache/incubator-superset/issues/9101
> > >
> > > The vote will be open for at least 1 Week or until the necessary number
> > of
> > > votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > > Thanks!
> > > Erik
> > >
> >
>

Re: Presto, Superset and Kerberos

[Maxime Beauchemin]

Coincidentally I reached out to fellow Superset committer Bogdan Kyryliuk
(cced) who's joined Dropbox to ask about the state of PyHive at Dropbox,
and whether they would welcome help maintaining the project. We can keep
you in the loop.

About Druid, I'm a maintainer on PyDruid but realistically can't spend much
time on it. I can certainly review / merge short PRs.

Max

On Thu, Feb 6, 2020 at 2:50 AM Luca Toscano  wrote:

> Forgot to ask also what are the plans for Superset + Kerberos + Druid
> (as far as I can see there are some pull requests opened) :)
>
> Luca
>
> Il giorno gio 6 feb 2020 alle ore 11:13 Luca Toscano
>  ha scritto:
> >
> > Hi everybody,
> >
> > I am bringing up
> > https://github.com/apache/incubator-superset/issues/8794 to the dev
> > mailing list to reach a broader audience and see if there is any new
> > idea about how to proceed. The TL;DR is that Presto
> > (https://prestodb.io/) and Superset seems not working when Presto is
> > authenticated via Kerberos. The main issue seems to be that the PyHive
> > (used by Superset) project seems not active anymore (see
> > https://github.com/dropbox/PyHive/issues/296) and unfortunately the
> > last Pypi version available does not contain the code that Superset
> > would need to work with Presto and Kerberos
> > (
> https://github.com/dropbox/PyHive/commit/6925cd74721cc474a02a6759490b2b4c8bef3831
> ).
> >
> > Maybe there is somebody in this list that can reach out to DropBox and
> > ask if they have plans for PyHive?
> >
> > Presto seems to be a really nice backend to use together with Druid
> > for Superset, I'd love to see this problem unblocked.
> >
> > Thanks in advance!
> >
> > Luca
>

Upcoming Superset Bay Area Meetup

[Maxime Beauchemin]

Hi all,

As mentioned in the recent newsletter, Preset is hosting a Superset meetup
in San Mateo on February 11th.

@ [local] committers and contributors, we're looking for speakers that want
to give short talks (5 to 20 minutes). Please reach out to me if you're
interested in sharing.

Find all the details about the meetup here:
https://www.meetup.com/SF-Bay-Area-Apache-Superset-Incubating-Meetup/events/268260513/

Looking forward to getting this group together!

Max

[VOTE] SIP-34 Proposal to establish a new design direction, system, and process for Superset

[Maxime Beauchemin]

Superset Community,

This is a call to vote for SIP-34: Proposal to establish a new design
direction, system, and process for Superset

Further details here:
https://github.com/apache/incubator-superset/issues/8976

The vote will be open for at least 1 Week or until the necessary number of
votes are reached.

Please vote accordingly:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Best,

Max

Re: [ANNOUNCE] New PPMC member Ville Brofeldt

[Maxime Beauchemin]

Welcome aboard!

On Thu, Jan 30, 2020 at 8:05 AM Emmanuel Palomeque Alcázar <
epalome...@gmail.com> wrote:

> Congrats Ville
>
> El jue., 30 ene. 2020 a las 9:07, Craig Rueda ()
> escribió:
>
> > Congrats!
> >
> > - Craig
> >
> > > On Jan 30, 2020, at 6:38 AM, Charles Givre  wrote:
> > >
> > > Congrats Ville!
> > > -- C
> > >
> > >> On Jan 30, 2020, at 9:34 AM, daniel gaspar  >
> > wrote:
> > >>
> > >> Hello Community,
> > >>
> > >> I'm pleased to announce that the Superset PMC has voted for Ville
> > Brofeldt
> > >> to
> > >> be a PPMC member.
> > >>
> > >> Congrats Ville!
> > >>
> > >> Cheers,
> > >> Daniel Gaspar
> > >
> >
>
>
> --
> ***
> Emmanuel Palomeque Alcázar
> DevOps / Python+Django+Rest+Mobile
>
> gmail. epalome...@gmail.com
> msn. epalome...@hotmail.com
>

FYI Superset Meetup @ Preset in San Mateo on 2020-02-11

[Maxime Beauchemin]

Hi all,

We're hosting a Superset meetup in 2 weeks at Preset in San Mateo (SF Bay
Area)
https://www.meetup.com/SF-Bay-Area-Apache-Superset-Incubating-Meetup/events/268260513/

Let us know if you'd like to speak, and please RSVP if you're planning to
attend. We're also planning on having some video feed for those who cannot
make it.

Hoping to see you there!

Max

Re: [DISCUSS] SIP-34 Proposal to establish a new design direction, system, and process for Superset

[Maxime Beauchemin]

Quick reminder that this SIP is massively important and pivotal. This is
setting a new north star for this community. Here's a glimpse of the Github
reactions so far :)
[image: Screen Shot 2020-01-22 at 2.47.05 PM.png]

We're welcoming more feedback before kicking off the vote!



On Wed, Jan 15, 2020 at 5:49 PM Evan Rusackas  wrote:

> Please discuss & subscribe here:
> https://github.com/apache/incubator-superset/issues/8976
>
> Thank you,
>
> Evan Rusackas
> Preset, Inc.
>

Re: [VOTE] SIP-32 Proposal for moving frontend assets to the base of the repo

[Maxime Beauchemin]

+1, let's get rid of the symlink and get the javascript source files out of
the python package, clean up the MANIFEST.in

On Fri, Jan 17, 2020 at 9:55 AM Ville Brofeldt 
wrote:

> Also +1 non-binding from me. Was the final naming convention already
> decided? If not I vote for the proposal by DiggidyDave.
>
> Ville
>
> On Fri, Jan 17, 2020, 19:46 Aaron Suddjian  wrote:
>
> > Big non-binding +1 from me!
> >
> > On Fri, Jan 17, 2020 at 9:33 AM daniel gaspar  >
> > wrote:
> >
> > > Hello Superset Community,
> > >
> > > This is a call to vote for SIP-32 Proposal for moving frontend assets
> to
> > > the base of the repo
> > >
> > > Further details here:
> > > https://github.com/apache/incubator-superset/issues/8805
> > >
> > > The vote will be open for at least 1 Week or until the necessary number
> > > of votes are reached.
> > >
> > > Please vote accordingly:
> > >
> > > [ ] +1 approve
> > > [ ] +0 no opinion
> > > [ ] -1 disapprove with the reason
> > >
> > >
> > > Thanks,
> > > The Apache Superset (Incubating) Team
> > >
> >
> >
> > --
> > Aaron Suddjian, Software Engineer at Preset
> >
>

Re: [ANNOUNCE] Apache Superset (Incubating) version 0.35.2 Released

[Maxime Beauchemin]

Nice!

Oh and for the record: Ville, Daniel and I have made great progress at
making the release process more streamlined and less error prone over the
past few releases. The process is now well documented, and some
release-related tooling is really coming together.

Cheers!

Max

On Wed, Jan 15, 2020 at 7:14 AM Daniel Gaspar  wrote:

> Great work Ville!
>
> On 2020/01/15 14:45:21, Ville Brofeldt 
> wrote:
> > Hello Community,
> >
> >
> > The Apache Superset (incubating) team is pleased to announce that
> Superset
> >
> > 0.35.2 has just been released.
> >
> >
> > Apache Superset (incubating) is a modern, enterprise-ready business
> > intelligence web application
> >
> >
> > The official source release:
> >
> >
> > https://www.apache.org/dist/incubator/superset/0.35.2
> >
> >
> > The Pypi package:
> >
> >
> > https://pypi.org/project/apache-superset/
> >
> >
> > If you have any usage questions, or have problems when upgrading or
> >
> > find any problems about enhancements included in this release, please
> >
> > don't hesitate to let us know by sending feedback to
> d...@superset.apache.org
> > .
> >
> >
> > =
> >
> > *Disclaimer*
> >
> >
> > Apache Superset is an effort undergoing incubation at The Apache Software
> >
> > Foundation (ASF), sponsored by the Incubator. 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.
> >
> >
> > -
> >
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>

Re: [VOTE] SIP-33 Proposal for Removing SQLite Support for Metadata Databases

[Maxime Beauchemin]

+1 binding

On Fri, Jan 10, 2020 at 7:31 AM Craig Rueda  wrote:

> +1 binding
>
> - Craig
>
> > On Jan 10, 2020, at 4:31 AM, daniel gaspar 
> wrote:
> >
> > Hello Superset Community,
> >
> > This is a call to vote for SIP-33 for removing SQLite support for
> > metadata databases.
> >
> > Further details here: github.com/apache/incubator-superset/issues/8874
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> >
> > Thanks,
> > The Apache Superset (Incubating) Team
>

Re: [VOTE] Release Apache Superset (incubating) 0.35.2 based on Superset 0.35.2rc2

[Maxime Beauchemin]

+1 (binding)

tested:
* opened all test dashboards
* basic dashboard interactions / filtering
* SQL Lab schema browsing
* SQL Lab autocomplete
* SQL Lab basic query running, sync and async

On Tue, Jan 7, 2020 at 2:31 PM Craig Rueda  wrote:

> +1 (binding)
> 
> From: Ville Brofeldt 
> Sent: Monday, January 6, 2020 11:11 AM
> To: d...@superset.apache.org 
> Subject: [VOTE] Release Apache Superset (incubating) 0.35.2 based on
> Superset 0.35.2rc2
>
> Hello Superset Community,
>
>
> This is a call for the vote to release Apache Superset
>
> (incubating) version 0.35.2. This vote replaces the vote for 0.35.2rc1,
> which contained a regression that has been fixed in 0.35.2rc2. Apologies
> for any inconvenience this may have caused.
>
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/superset/0.35.2rc2/
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-superset/tree/0.35.2rc2
>
>
> The Change Log for the release:
>
> https://github.com/apache/incubator-superset/blob/0.35.2rc2/CHANGELOG.md
>
>
> public keys are available at:
>
>
> https://www.apache.org/dist/incubator/superset/KEYS
>
>
> The vote will be open for at least 72 hours or until the necessary number
>
> of votes are reached.
>
>
> Please vote accordingly:
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove with the reason
>
>
> Thanks,
>
> The Apache Superset (Incubating) Team
>

Re: [DISCUSS] Simplify the SIP voting process

[Maxime Beauchemin]

Right, adding a comment with a snapshot of the result at the time the vote
ends is a simple solution.

Max

On Fri, Dec 20, 2019 at 2:47 PM David Smith  wrote:

> If there is a way to "freeze" the reactions at the time the vote is
> closed--maybe the bot adds a comment documenting the closing vote total and
> sends an email--then there is no issue.  It would only be a problem if a
> vote could "pass" 5-4 or something, and then later a viewer would see 4 up
> and 5 down votes with no additional record.
>
> On Fri, Dec 20, 2019 at 2:19 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > I'm positive that edited comments are saved in history, and that
> reactions
> > have timestamps attached to them
> > <
> >
> https://developer.github.com/v3/reactions/#list-reactions-for-a-commit-comment
> > >.
> > Same goes for labels (effectively marking when voting starts/ends).
> >
> > [eventually] it would also be possible for our bot to:
> > * catch and delete reactions when voting isn't open
> > * send emails as needed
> > * do accounting based on who's a PMC / committer / contributor
> > (binding/non-binding). Hopefully Whimsy has some REST API we can hit to
> get
> > list of Github handles of committers / PMCs
> >
> > Max
> >
> > On Fri, Dec 20, 2019 at 2:07 PM David Smith 
> > wrote:
> >
> > > I think it would be vastly superior in terms of user-experience. I
> think
> > > the pushback would possibly be that email produces an immutable record
> of
> > > the vote and any conversation around it, whereas github votes can be
> > > changed after the fact, comments may be edited, etc.
> > >
> > > It depends on what one is optimizing for, I suppose.
> > >
> >
>

[ANNOUNCE] New committer and PMC member: Craig Rueda

[Maxime Beauchemin]

The Project Management Committee (PMC) for Apache Superset
has invited Craig Rueda to become a committer & PMC member 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.

Re: [DISCUSS] Simplify the SIP voting process

[Maxime Beauchemin]

I'm positive that edited comments are saved in history, and that reactions
have timestamps attached to them
.
Same goes for labels (effectively marking when voting starts/ends).

[eventually] it would also be possible for our bot to:
* catch and delete reactions when voting isn't open
* send emails as needed
* do accounting based on who's a PMC / committer / contributor
(binding/non-binding). Hopefully Whimsy has some REST API we can hit to get
list of Github handles of committers / PMCs

Max

On Fri, Dec 20, 2019 at 2:07 PM David Smith  wrote:

> I think it would be vastly superior in terms of user-experience. I think
> the pushback would possibly be that email produces an immutable record of
> the vote and any conversation around it, whereas github votes can be
> changed after the fact, comments may be edited, etc.
>
> It depends on what one is optimizing for, I suppose.
>

[DISCUSS] Simplify the SIP voting process

[Maxime Beauchemin]

Hey all,

The ASF's email-driven voting process is pretty cumbersome, and I'd like to
propose to amend SIP-0
 to have the vote
take place on Github instead, using reactions (thumbs up / thumbs down) in
the body of the issue itself, and using labels to mark state as in
"sip-discuss" "sip-voting-ongoing" and "sip-voting-closed" as needed.

The mailing list would still be used to draw attention to the SIP. One
super short email would be sent:
- to start a [DISCUSS] equivalent on the issue
- to kick off the [VOTE] equivalent on the issue
- to send the [RESULT]

Eventually and as the process becomes more clear, we could have our Github
bot take care of much of this (sending emails, counting votes, prevent
voting during "discuss", ...)

What do you think?

Max

Re: Stability of git master branch vs. PyPI release

[Maxime Beauchemin]

Docs are versioned here:
https://readthedocs.org/projects/apache-superset/

But you're right, superset.apache.org *should* point to latest official ASF
release (and it does not, my mistake)

All SHAs on master pass the test suite, but ASF releases also guarantee:
* a vote has to pass with PPMC members, sometimes multiple release
candidates are voted-on prior to publishing a release
* more rigor around license validation
* pinned documentation in the link above
* a signed tarball on SVN
* a process for patch/micro releases on top of that release
* [eventually] and official docker / tag
* ... maybe more ... (?)

There's a Slack channel #apache-releases dedicated to people coordinating
on releases if you want to follow what is going on or get involved.

Find more about the release process here:
https://github.com/apache/incubator-superset/tree/master/RELEASING

Max

On Mon, Dec 16, 2019 at 11:20 AM Brannon, Terrence
 wrote:

> I'm not sure if this is the right place to ask this, but:
>
> 0.35.1 version of Superset was released to PyPI on Nov 26, 2019.
>
> Since then there have been about 100 new commits to master.
>
> It is also a fact that the online docs are sync'ed to the master branch
> NOT the PyPI release:
>
> https://github.com/apache/incubator-superset/issues/8795#issuecomment-565769648
>
> This of course makes one wonder: which version of Superset is most stable?
> Do both pass a test suite? If so then the git version would be more
> attractive because it has more features and fixes.
>
> - T
>
>
>
> U.S. BANCORP made the following annotations
> -
> Electronic Privacy Notice. This e-mail, and any attachments, contains
> information that is, or may be, covered by electronic communications
> privacy laws, and is also confidential and proprietary in nature. If you
> are not the intended recipient, please be advised that you are legally
> prohibited from retaining, using, copying, distributing, or otherwise
> disclosing this information in any manner. Instead, please reply to the
> sender that you have received this communication in error, and then
> immediately delete it. Thank you in advance for your cooperation.
>
> -
>

Re: [VOTE] New committer and PMC member: Craig Rueda

[Maxime Beauchemin]

Oops. That was meant for priv...@superset.apache.org , sorry about the
confusion.

On Thu, Dec 5, 2019 at 4:46 PM Maxime Beauchemin 
wrote:

> Hi folks!
>
> I'd like to nominate Craig Rueda as a committer and PMC member in the
> Incubator for Superset. Craig has been contributing steadily to the
> project since November 2018. During that time, he has shipped 15 pull
> requests (
> https://github.com/apache/incubator-superset/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Acraig-rueda+is%3Aclosed+),
> covering bug fixes, chores, new features.
>
> Most notably, he's created SIP-24
> <https://github.com/apache/incubator-superset/issues/8318> around getting
> our flask implementation to respect the factory pattern, and delivered a
> solution <https://github.com/apache/incubator-superset/pull/8418> for it.
> Craig has also started to work around containers and developer experience.
> He's planning on continuing work in that direction by taking ownership of
> docker images, docker-compose, and CI/CD-related topics (amongst many other
> things).
>
> Voting ends next Wednesday, i.e. midnight UTC.
>
> Max
>

[VOTE] New committer and PMC member: Craig Rueda

[Maxime Beauchemin]

Hi folks!

I'd like to nominate Craig Rueda as a committer and PMC member in the
Incubator for Superset. Craig has been contributing steadily to the project
since November 2018. During that time, he has shipped 15 pull requests (
https://github.com/apache/incubator-superset/pulls?utf8=%E2%9C%93&q=is%3Apr+author%3Acraig-rueda+is%3Aclosed+),
covering bug fixes, chores, new features.

Most notably, he's created SIP-24
 around getting
our flask implementation to respect the factory pattern, and delivered a
solution  for it.
Craig has also started to work around containers and developer experience.
He's planning on continuing work in that direction by taking ownership of
docker images, docker-compose, and CI/CD-related topics (amongst many other
things).

Voting ends next Wednesday, i.e. midnight UTC.

Max

Incubation Status report

[Maxime Beauchemin]

Hello @Mentors & Justin,

As Superset gets closer to graduation, we're looking at the "Incubation
Status" page, a manually maintained XML document on SVN

[shivers], and recently found duplicated / more dynamic information on
Whimsy around the roster.

rendered page: https://incubator.apache.org/projects/superset.html
more dynamic page on whimsy: https://whimsy.apache.org/roster/ppmc/superset

Is there any way we can 1 - use something else than that xml thing, like a
Confluence page maybe? 2 - if we absolutely have to edit that SVN XML file,
can we just link out to Whimsy for roster info?

Also I noticed that Whimsy has other metadata around licensing (in *red* at
the bottom), how do we alter that? Does it matter?

Thanks,

Max

Re: [ANNOUNCE] Apache Superset (Incubating) version 0.35.1 Released

[Maxime Beauchemin]

Nice! Great work Daniel, and thank you for improving the docs and tooling
along the way.

On Tue, Nov 26, 2019 at 1:49 PM  wrote:

> Hello Community,
>
> The Apache Superset (incubating) team is pleased to announce that Superset
> 0.35.1 has just been released.
>
> Apache Superset (incubating) is a modern, enterprise-ready business
> intelligence web application
>
> The official source release:
>
> https://www.apache.org/dist/incubator/superset/0.35.1
>
> The Pypi package:
>
> https://pypi.org/project/apache-superset/
>
> If you have any usage questions, or have problems when upgrading or
> find any problems about enhancements included in this release, please
> don't hesitate to let us know by sending feedback to this mailing
> list.
>
> =
> *Disclaimer*
>
> Apache Superset is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Incubator. 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.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

Re: Submitted the suitable name search for Superset

[Maxime Beauchemin]

Awesome, thanks Dellaena for submitting this. For the record, this is one
of the last important steps (I think) towards graduation (!!!)

+cc Mark Thomas who's been kindly approve similar requests in the past.

Cheers,

Max

On Mon, Nov 25, 2019 at 4:07 PM Dellaena Maliszewski 
wrote:

> Hello!
> We submitted the suitable name search for Superset.
>
> Here is a link to the Issue and search data:
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-173
>
> If you have a moment to provide feedback or comments on the issue, any
> help or support would be appreciated.
>
> Have a great day!
> Dellaena
>

Re: [VOTE] Release Superset 0.35.1 based on Superset 0.35.1rc1

[Maxime Beauchemin]

+1

- Tested on Preset infra deployment. Opened all examples dashboards.
- Also ran the docker build from the tarball (`export
SUPERSET_VERSION_RC=0.35.1rc1; ./test_run_tarball.sh`), fired up the
container and made sure things looked ok.

Max

On Fri, Nov 15, 2019 at 8:19 AM Ville Brofeldt 
wrote:

> Hi all,
>
> for additional context, this release aims to address a bug in 0.35.0, which
> caused the server to fail to start if the optional dependency pydruid was
> not installed. In addition to fixing that problem, a few other fixes have
> also been included that were merged to master after the 0.35 branch was
> cut. Due to the severity of the bug, the 0.35.0 release will not be
> published on PyPI, but will be postponed until 0.35.1 is released.
>
> Ville
>
> On Fri, Nov 15, 2019 at 5:46 PM daniel gaspar 
> wrote:
>
> > Hi everyone,
> >
> > The source release 0.35.1 RC1 for Apache Superset is baked and available
> > at:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/superset/0.35.1rc1/
> >
> > public keys are available at:
> >
> > https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> >
> > This release mainly aims to fix bugs, and update dependencies.
> >
> > Cherry picks applied on 0.35.1 RC1 since 0.35.0:
> >
> > b91205d9 [pydruid] Bumping the pydruid version (#8430)
> > a8f1589d fixing typo. (#8487)
> > 650c8482 [cli] Fix, import datasources exported by UI (#8477)
> > 4c2a6537 build: bump dompurify version because of nasty xss bypass.
> (#8498)
> > 59bc2206 bump legacy-preset-chart-nvd3 to 0.11.5 (#8558)
> > efb44ba5 [druid] Fix, pydruid forced dependency (#8566)
> > 49ea232c [fix] Improve csv upload functionality (#8457)
> >
> > Happy testing,
> > Daniel Gaspar
> >
>

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

[Maxime Beauchemin]

Also Windows is not really supported and not recommended (we don't run any
test against it).

Max

On Wed, Nov 13, 2019 at 9:57 AM daniel gaspar 
wrote:

> Hi,
>
> This thread is not the right place to report issues or questions. Please
> feel free to open an issue on Github so that we can properly help you.
>
> Thank you,
> Daniel Gaspar
>
>
> On Wed, 13 Nov 2019 at 15:02, Thammaneni, Srinivasa Rao <
> sthamman...@teksystems.com> wrote:
>
>> Hi Team,
>>
>>
>>
>> I am trying to clone new apache o.35 release into my windows10 OS
>> machine, but it is asking to have "pyarrow<0.15.0,>=0.14.1" as a dependency
>> module. I tried to install required version of pyarrow from pip installer,
>> saying there is no version available as pyarrow 0.14.1. I tried by
>> installing pyarrow 0.14.0 and 0.15.0 versions as well but no luck. I am
>> using latest pip version 19.3.1 and python 3.7. Any suggestions here ?
>>
>>
>>
>> Ref:
>>
>>
>>
>>
>>
>>
>>
>> Thanks & Regards,
>>
>> Srinivas T.
>>
>>
>>
>> -Original Message-
>> From: Daniel Gaspar [mailto:dpgas...@apache.org]
>> Sent: Wednesday, November 13, 2019 1:16 AM
>> To: d...@superset.apache.org
>> Subject: Re: [ANNOUNCE] Release Apache Superset (incubating) version
>> 0.35.0
>>
>>
>>
>> It's part of the release, we have merged the CHANGELOG to master, but it
>> was already on the release branch
>>
>>
>>
>> On 2019/11/12 18:30:23, Bolke de Bruin  wrote:
>>
>> > Awesome. But I guess the (updated) changelog is not part of the
>>
>> > release then?
>>
>> >
>>
>> >
>>
>> > On 12 November 2019 at 19:28:32, Daniel Gaspar (dpgas...@apache.org)
>> wrote:
>>
>> >
>>
>> > True, was merged 5 min ago :)
>>
>> >
>>
>> >
>>
>> > On 2019/11/12 18:01:58, Bolke de Bruin  wrote:
>>
>> > > Hi Daniel,
>>
>> > >
>>
>> > > The changelog does not seem to be updated?
>>
>> > >
>>
>> > > Cheers
>>
>> > > Bolke
>>
>> > >
>>
>> > >
>>
>> > > On 12 November 2019 at 17:28:40, daniel gaspar
>>
>> > > (danielvazgas...@gmail.com)
>>
>> >
>>
>> > > wrote:
>>
>> > >
>>
>> > > Dear all,
>>
>> > >
>>
>> > > The Apache Superset (incubating) community is happy to announce
>>
>> > > Apache Superset
>>
>> > > (incubating) version 0.35.0!
>>
>> > >
>>
>> > > Apache Superset (incubating) is a business intelligence web
>>
>> > > application
>>
>> > >
>>
>> > > *0.35.0 is our third official Apache release!*
>>
>> > >
>>
>> > > A full list of the changes in this release can be found in the
>>
>> > > release
>>
>> > > notes:
>>
>> > >
>>
>> > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache
>>
>> > _incubator-2Dsuperset_blob_master_CHANGELOG.md-23change-2Dlog&d=DwIBaQ
>>
>> > &c=_EdSgJoS8igo01XnekBu_azVXoUPxJkwz9O2AzwhBbE&r=UStC5YS3VNq1KspFf9vgA
>>
>> > Pb1Fjv1EbWV19AyDPI2X9I&m=y9WXGwYMRt7YpUMuFkzV-kO5NNutPBZ95Tm3gR2hxmE&s
>>
>> > =i-ZN1Ln3hHcjhTrKVfrXBKVutSvm9Lg2VWzMHblyHnY&e=
>>
>> > >
>>
>> > > A link to the source download can be found here:
>>
>> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__www.apache.org_
>>
>> > > dist_incubator_superset_0.35.0_&d=DwIBaQ&c=_EdSgJoS8igo01XnekBu_azVX
>>
>> > > oUPxJkwz9O2AzwhBbE&r=UStC5YS3VNq1KspFf9vgAPb1Fjv1EbWV19AyDPI2X9I&m=y
>>
>> > > 9WXGwYMRt7YpUMuFkzV-kO5NNutPBZ95Tm3gR2hxmE&s=HsTG8B29yNkfNKggYQ3uL8r
>>
>> > > 5ZO1KvaLgjzL4U-Qr-DQ&e=
>>
>> > >
>>
>> > > Find links to Apache Superset related resources on our Github:
>>
>> > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apac
>>
>> > > he_incubator-2Dsuperset&d=DwIBaQ&c=_EdSgJoS8igo01XnekBu_azVXoUPxJkwz
>>
>> > > 9O2AzwhBbE&r=UStC5YS3VNq1KspFf9vgAPb1Fjv1EbWV19AyDPI2X9I&m=y9WXGwYMR
>>
>> > > t7YpUMuFkzV-kO5NNutPBZ95Tm3gR2hxmE&s=1DSJuzFNTeh8KZiKN6SgfzgGjVqG2ai
>>
>> > > w86t90js_lZc&e=
>>
>> > >
>>
>> > > 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.
>>
>> > >
>>
>> >
>>
>>
>> This electronic mail (including any attachments) may contain information
>> that is privileged, confidential, and/or otherwise protected from
>> disclosure to anyone other than its intended recipient(s). Any
>> dissemination or use of this electronic mail or its contents (including any
>> attachments) by persons other than the intended recipient(s) is strictly
>> prohibited. If you have received this message in error, please notify us
>> immediately by reply e-mail so that we may corre

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

[Maxime Beauchemin]

Nice! Thank you Daniel for making this happen

On Tue, Nov 12, 2019, 8:28 AM daniel gaspar 
wrote:

> Dear all,
>
> The Apache Superset (incubating) community is happy to announce Apache
> Superset
> (incubating) version 0.35.0!
>
> Apache Superset (incubating) is a business intelligence web application
>
> *0.35.0 is our third 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/0.35.0/
>
> 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.
>

Re: [VOTE] Release Superset 0.35.0 based on Superset 0.35.0rc2

[Maxime Beauchemin]

+1 (binding)

* opened all examples dashboard, tested filters, layout adjustments, saving
* tested basic explore functionalities
* tested basic SQL Lab functionalities using a database in async mode




On Mon, Oct 28, 2019 at 2:30 PM Grace Guo 
wrote:

> +1
>
> - Grace
>
> > On Oct 28, 2019, at 7:15 AM, daniel gaspar 
> wrote:
> >
> > Hi everyone,
> >
> > The source release 0.35.0 RC2 for Apache Superset is baked and available
> at:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/superset/0.35.0rc2/
> >
> > public keys are available at:
> >
> > https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> >
> > This release mainly aims to fix bugs, introduce new features and update
> > dependencies.
> > This is a direct cut from master at SHA 8f246ce with one cherry applied:
> >
> > Cherry pick applied on RC2:
> >
> > [fix] Updating parse_human_timedelta typing (#8436)
> >
> > Change log since 0.34.1:
> >
> > 8f246cec chore: disable another flaky cypress test (#8423)
> > cca689b7 Add improved typed casting to BigQuery (#8331)
> > 4cfd6b3c [tests] Fix, removing deprecated function for future Python
> > release compatibility. (#8353)
> > 1e533db3 fixed typo in installation instructions (#8413)
> > 9fc37ea9 [ci] Deprecate flake8 (#8409)
> > a1999018 [sqla] Enforcing ISO 8601 date/timestamp formats (#7702)
> > d3406e0a [Config] Cache static resources (#8370)
> > c62b2f43 [docs] CTAS on PostgreSQL needs commit to apply (#8367)
> > c422b492 Update Slack invitation link (#8399)
> > 876d3294 [fix] make names non-nullable (#8371)
> > fcb39f90 [form-data] Deleting obsolete Superset.get_form_data method
> (#8390)
> > 2117d1ef Add 0.34.1 PRs to CHANGELOG (#8376)
> > 03b35b3c [migration] Migrating since/until to time_range (#8372)
> > 558680d6 [Cypress] Skip another flaky sqllab test (#8374)
> > 9a186ffb Add incubating to NOTICE (#8369)
> > 7133429a [Docs] Put superset users in abc order (#8368)
> > 66e3708a Update README.md (#8365)
> > 7e7ea3d9 Revert "[fix] make datasource names non-nullable (#8332)"
> (#8363)
> > 8b85a8f3 [dashboard] show less filter indicators (#8345)
> > c09e3e7e Fix pypi link and replace gitter badge with slack (#8330)
> > edec8745 Revert "[init] Setting up cache before registering blueprints
> > (#7992)" (#8005)
> > 78366716 Add support for Exasol (#8343)
> > b0934065 fix saving new sql lab queries (#8351)
> > 04c3d1f5 Remove unused methods from Presto (#8350)
> > ec86d9de Fix lint in `superset/db_engine_spec` (#8338)
> > 65a05ca4 [fix] make datasource names non-nullable (#8332)
> > b6b6a753 Add Fanatics to companies that use Superset (#8344)
> > 46227b75 [docs] Add Deepomatic in organization list (#8347)
> > 9596935c feat: Set moment library language during app setup (#8296)
> > 4a8799b9 fix: npm audit fix bumps handlebars 4.1.2->4.3.1 (#8299)
> > 05b67673 [metric] Adding security for restricted metrics (#8175)
> > 8c708037 [Presto] Handle uncaught exception in get_create_view (#8304)
> > f21cc630 [SQL Lab] Improve autocomplete (#8305)
> > fbbc5f05 Allow overwriting a SQLLab query that has previously been saved
> > (#8298)
> > d55fe541 refactor: remove unused code (#8300)
> > 25e2517d Update RunQueryActionButton.jsx (#8320)
> > cff10ebf Adding explicit Flask session cookie options to default config
> > (#8317)
> > d59e0c46 [superset] Fix, missing return on error and improved query
> (#8239)
> > 7ea76922 allow non-relative LOGO_TARGET_PATH (#8307)
> > 3764d43f Add safaricom to companies using superset (#8311)
> > 52a84d25 Add explicit support for python 3.7 (#8309)
> > 6d418308 Refine release instructions (#8272)
> > 11935ce1 Add commit to attempt to resolve query table lock (#8262)
> > 09bbdd27 chore: skip flaky SQL Lab test (#8282)
> > d4651077 [migration] Stripping leading and trailing whitespace (#8261)
> > 5d1bf424 [sql_json] Ensuring the request body is JSON encoded (#8256)
> > f3065a76 [database] Improve form and API validation for invalid URI
> (#8240)
> > bc83b5fb More intuitive display of negative time deltas (#8274) (#8276)
> > 7090725d Fix no data in Presto (#8268)
> > 731c19b6 refactor: use deck.gl plugins from npm package (#8258)
> > dfb3bf69 [typing] add typing for superset/connectors and superset/common
> > (#8138)
> > 8bc5cd7d [SQLLab] Refactor sql json endpoint (#8163)
> > 6df74c6b Remove __row_id (#8257)
> > 799e08d7 Update another pypi case from superset to apache-superset
> (#8250)
> > 115bc83b docs: reflect the pypi move from superset to apache-superset
> > (#8244)
> > 0c94f0fd [sqllab] create query slightly earlier (#8224)
> > 8e1fc2b0 Fix array casting (#8253)
> > 12fb8e70 Show Presto views as views, not tables (#8243)
> > 4088a84e Small fix for Presto dtype map (#8251)
> > 8d04e1f5 Update README.md (#8246)
> > 0cd4ef54 Add RegisteredLookupExtraction support to extraction function
> > (#8185)
> > 88777943 Better distinction between tables and views, and show CREATE
> VIEW
> > (#8213)
> > 4132d8fb Simplify and improve `expand_data` in Presto (#8233)
> > 88

Re: [VOTE] Release Superset 0.35.0 based on Superset 0.35.0rc1

[Maxime Beauchemin]

-1 (binding)

Any other requests before we get started on rc2 ?

On Thu, Oct 24, 2019 at 10:04 PM Ville Brofeldt 
wrote:

> Hi all,
>
> thanks Daniel for starting the 0.35 release process. As the fix seems quite
> vital, I vote -1 (non-binding) and propose starting a new RC with the
> aforementioned fix.
>
> Ville
>
> On Fri, Oct 25, 2019 at 3:01 AM Grace Guo 
> wrote:
>
> > Hi Daniel,
> >
> > Thanks for the release work. We just make a new Superset release to
> airbnb
> > (airbnb release <
> > https://github.com/airbnb/incubator-superset/commits/release--0.43>),
> > which is pretty close to 0.35rc1. We found this PR <
> > https://github.com/apache/incubator-superset/pull/8436> is a necessary
> > fix in our release. You probably want to add this to 0.35rc1.
> >
> > Thanks!
> >
> > - Grace
> >
> > > On Oct 23, 2019, at 7:41 AM, daniel gaspar 
> > wrote:
> > >
> > > Hi everyone,
> > >
> > > The source release 0.35.0 RC1 for Apache Superset is baked and
> available
> > at:
> > >
> > > https://dist.apache.org/repos/dist/dev/incubator/superset/0.35.0rc1/
> > >
> > > public keys are available at:
> > >
> > > https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> > >
> > > This release mainly aims to fix bugs, introduce new features and update
> > > dependencies.
> > > This is a direct cut from master at SHA 8f246ce no cherries were added.
> > >
> > > Change log since 0.34.1:
> > >
> > > 8f246cec chore: disable another flaky cypress test (#8423)
> > > cca689b7 Add improved typed casting to BigQuery (#8331)
> > > 4cfd6b3c [tests] Fix, removing deprecated function for future Python
> > > release compatibility. (#8353)
> > > 1e533db3 fixed typo in installation instructions (#8413)
> > > 9fc37ea9 [ci] Deprecate flake8 (#8409)
> > > a1999018 [sqla] Enforcing ISO 8601 date/timestamp formats (#7702)
> > > d3406e0a [Config] Cache static resources (#8370)
> > > c62b2f43 [docs] CTAS on PostgreSQL needs commit to apply (#8367)
> > > c422b492 Update Slack invitation link (#8399)
> > > 876d3294 [fix] make names non-nullable (#8371)
> > > fcb39f90 [form-data] Deleting obsolete Superset.get_form_data method
> > (#8390)
> > > 2117d1ef Add 0.34.1 PRs to CHANGELOG (#8376)
> > > 03b35b3c [migration] Migrating since/until to time_range (#8372)
> > > 558680d6 [Cypress] Skip another flaky sqllab test (#8374)
> > > 9a186ffb Add incubating to NOTICE (#8369)
> > > 7133429a [Docs] Put superset users in abc order (#8368)
> > > 66e3708a Update README.md (#8365)
> > > 7e7ea3d9 Revert "[fix] make datasource names non-nullable (#8332)"
> > (#8363)
> > > 8b85a8f3 [dashboard] show less filter indicators (#8345)
> > > c09e3e7e Fix pypi link and replace gitter badge with slack (#8330)
> > > edec8745 Revert "[init] Setting up cache before registering blueprints
> > > (#7992)" (#8005)
> > > 78366716 Add support for Exasol (#8343)
> > > b0934065 fix saving new sql lab queries (#8351)
> > > 04c3d1f5 Remove unused methods from Presto (#8350)
> > > ec86d9de Fix lint in `superset/db_engine_spec` (#8338)
> > > 65a05ca4 [fix] make datasource names non-nullable (#8332)
> > > b6b6a753 Add Fanatics to companies that use Superset (#8344)
> > > 46227b75 [docs] Add Deepomatic in organization list (#8347)
> > > 9596935c feat: Set moment library language during app setup (#8296)
> > > 4a8799b9 fix: npm audit fix bumps handlebars 4.1.2->4.3.1 (#8299)
> > > 05b67673 [metric] Adding security for restricted metrics (#8175)
> > > 8c708037 [Presto] Handle uncaught exception in get_create_view (#8304)
> > > f21cc630 [SQL Lab] Improve autocomplete (#8305)
> > > fbbc5f05 Allow overwriting a SQLLab query that has previously been
> saved
> > > (#8298)
> > > d55fe541 refactor: remove unused code (#8300)
> > > 25e2517d Update RunQueryActionButton.jsx (#8320)
> > > cff10ebf Adding explicit Flask session cookie options to default config
> > > (#8317)
> > > d59e0c46 [superset] Fix, missing return on error and improved query
> > (#8239)
> > > 7ea76922 allow non-relative LOGO_TARGET_PATH (#8307)
> > > 3764d43f Add safaricom to companies using superset (#8311)
> > > 52a84d25 Add explicit support for python 3.7 (#8309)
> > > 6d418308 Refine release instructions (#8272)
> > > 11935ce1 Add commit to attempt to resolve query table lock (#8262)
> > > 09bbdd27 chore: skip flaky SQL Lab test (#8282)
> > > d4651077 [migration] Stripping leading and trailing whitespace (#8261)
> > > 5d1bf424 [sql_json] Ensuring the request body is JSON encoded (#8256)
> > > f3065a76 [database] Improve form and API validation for invalid URI
> > (#8240)
> > > bc83b5fb More intuitive display of negative time deltas (#8274) (#8276)
> > > 7090725d Fix no data in Presto (#8268)
> > > 731c19b6 refactor: use deck.gl plugins from npm package (#8258)
> > > dfb3bf69 [typing] add typing for superset/connectors and
> superset/common
> > > (#8138)
> > > 8bc5cd7d [SQLLab] Refactor sql json endpoint (#8163)
> > > 6df74c6b Remove __row_id (#8257)
> > > 799e08d7 Update another pypi case from superset to apache-

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

[Maxime Beauchemin]

Just saw this late. Awesome! Thanks much Ville for putting the release
together!

Daniel and I are lining up to cut the 0.35 branch and craft 0.35.0rc1 off
of its head early next week.

We'd love to get more people from the community involved in the release
validation process, so please consider helping out. I'm happy to break down
concrete ways you can help around releases in another email if you all
think that's helpful.

Max

On Sat, Oct 12, 2019 at 8:14 AM Ville Brofeldt 
wrote:

> Dear all,
>
> The Apache Superset (incubating) community is happy to announce Apache
> Superset (incubating) version 0.34.1, our second official Apache release!
>
> Apache Superset (incubating) is a business intelligence web application.
>
> 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/0.34.1/
>
> 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.
>

Re: Integrating new component in Superset

[Maxime Beauchemin]

What kind of component? "Component" screams React, not Flask...

On Sun, Oct 6, 2019 at 2:07 AM Araveti, Nithya 
wrote:

> Hi ,
>
>
>
> We are trying to integrate new flask component into Superset. Can we get
> help in understanding which files need to be changed.
>
>
>
>
>
>
>
> -Thank you,
>
> *Nithya A* *|* *Senior Software Engineer*
>
>
>
>
>
>
> This electronic mail (including any attachments) may contain information
> that is privileged, confidential, and/or otherwise protected from
> disclosure to anyone other than its intended recipient(s). Any
> dissemination or use of this electronic mail or its contents (including any
> attachments) by persons other than the intended recipient(s) is strictly
> prohibited. If you have received this message in error, please notify us
> immediately by reply e-mail so that we may correct our internal records.
> Please then delete the original message (including any attachments) in its
> entirety. Thank you
>

Re: [VOTE] Release Superset 0.34.1 based on Superset 0.34.1rc2

[Maxime Beauchemin]

+1 (binding)
--
Deployed on a sandbox on Preset infra, LGTM, validated that:

* opened all example dashboards, did some basic interactions, looking good
* polygon example works, toggling the legend seem broken, but not a
dealbreaker, seems to be an issue in master, this PR
https://github.com/apache-superset/superset-ui-plugins-deckgl/pull/1 addresses
it
* ran some queries in SQL Lab, followed the "explore" flow

On Mon, Sep 30, 2019 at 9:34 PM Ville Brofeldt 
wrote:

> Dear all,
>
>
> The source release 0.34.1 RC2 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 release mainly aims to fix bugs that have surfaced since the first
> official release 0.34.0. For context the `0.34` release branch was cut at
> SHA 9233a63, that was merged on master on Aug 8th 2019. 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.
>
>
> New cherries in 0.34.1rc2:
>
>
> 270fd32a Fix: Missing time series datapoints in druid show up as absurd
> values in line chart (#8271)
>
> 779976e1 Fixed korean translation error. (#8265)
>
> cc023a41 Fix sync failed when datasource is schema-less (#8223)
>
> 078af117 [SQL Lab] Fix bug when filtering on results that include nulls
> (#8231)
>
> 40cea544 Bump flask-appbuilder to 2.1.13 (#8174)
>
> 49bba75e Bump FAB to 2.1.13 (#8176)
>
> e81f3746 [examples] Fix, sf population polygons div by zero error (#8209)
>
> a8576aad [Explore view] Fix extra data fetch when user clicks Run Query
> (#8070)
>
>
> New cherries in 0.34.1rc1:
>
>
> aaed4a77 updating version to 0.34.1
>
> 30ded7dd [sql lab] persist tables list in localStorage (#8054)
>
> 301211b5 Revert "Fixed Histogram visualization bug.  (#8077)" (#8145)
>
> eb3cb955 fix: issues #8041 - bubble support for complex metrics (#8044)
>
> 7ca58f02 adding spaces missing from string concatenations (#8126)
>
> 9e6c0ab7 Update core.py (#8191)
>
> 7326f371 [feat] Add d3 legend formatting for Arc, Polygon and Scatter
> deck.gl maps (#7951)
>
> 92481b7b [bugfix] Correctly quote table and schema in select_star (#8181)
>
> c5249cef Make orderby native sqla construct (#8180)
>
> 3136af12 [bugfix] fix timegrain addon regression (#8165)
>
> a8b05484 Add check for calls to cache_key_wrapper (#8128)
>
> 20a05954 Fix to Werkzeug ProxyFix; expose ProxyFix configuration items
> (#8117)
>
> 4e49b8f3 Fixed Histogram visualization bug.  (#8077)
>
> 6f6e068c Set disableErrorBoundary in SuperChart to fix chart error handling
> (#8052)
>
> 08f19f1d  fix: onSave datasource raises React error (#8049)
>
> 66340f1a fix: handle case where result exists but corresponding query
> cannot be found (#8037)
>
> f85ba81c [bugfix] Fix deck_polygon metric bug and update examples chart
> (#8025)
>
> 85f959f6 [fix] Allow dashboard viewer auto refresh dashboard (#8014)
>
> de21a7f1 Fix: There was an issue fetching the favorite status of this
> dashboard #6824 (#8013)
>

Re: [VOTE] Release Superset 0.34.1 based on Superset 0.34.1rc1

[Maxime Beauchemin]

As we're flexing our release-process muscles, I think it'd be good to do
another RC here. It will help identify the friction points, improve docs /
tooling, ...

I'm switching my vote to "-1" (if I can), let's do an RC2! If any of the
new cherries are not easy to merge, I'd pass on them as I think the goal
here is to practice the release process, not getting to a perfect release.

Daniel and I can commit to work on the next release next week. We have to
decide whether we should aim at 0.35.0 (fresh cut out of master) or 0.34.2
(building upon 0.34.1). Right now I'm thinking we'd work on 0.35.0 unless
instructed otherwise.

Max

On Thu, Sep 26, 2019 at 6:30 AM Daniel Gaspar  wrote:

> Hi,
>
> I agree with Ville regarding the FAB bump to 2.1.13 that might introduce a
> regression risk and could make sense to leave it on the wild a little time
> longer. The security fixes are medium severity and if I'm not mistaken the
> OAuth issue addresses an edge case.
>
> Regarding the polygons fix, may make sense since 0.34.1rc1 already has
> another fix for the polygons chart, I would say it's a minor fix on an
> examples chart but makes sense for the sake of context.
>
> On 2019/09/26 13:00:58, Charles Givre  wrote:
> > Hello all,
> > As a mere member FWIW, I'd vote for new release, given the
> vulnerabilities that are being fixed, the FAB bump and OAUTH login fix.
> > -- C
> >
> > > On Sep 26, 2019, at 8:47 AM, Ville Brofeldt <
> ville.v.brofe...@gmail.com> wrote:
> > >
> > > Oh, 0.34.0 is already on PyPI:
> https://pypi.org/project/apache-superset/
> > >
> > > On Thu, Sep 26, 2019 at 3:21 PM Charles Givre 
> wrote:
> > >
> > >> I'd also like to put in a vote for updating Pypi now that we got the
> > >> ownership situation straightened out.  ;-)
> > >> --C
> > >>
> > >>> On Sep 26, 2019, at 7:48 AM, Ville Brofeldt <
> ville.v.brofe...@gmail.com>
> > >> wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> Both look ok to me, I think it comes down to whether or not we want
> to
> > >>> delay 0.34.1 by kicking off a new vote on 0.34.1rc2 or defer these
> to the
> > >>> 0.34.2 release, or potentially even 0.35. I'm fine either way, as
> baking
> > >> a
> > >>> new release candidate should be fairly quick. However, it would be
> > >> helpful
> > >>> to get some assistance validating the FAB bump, as there's a risk
> that
> > >> that
> > >>> might introduce an unrelated regression.
> > >>>
> > >>> Ville
> > >>>
> > >>> On Thu, Sep 26, 2019 at 1:08 PM Daniel Gaspar 
> > >> wrote:
> > >>>
> >  Just a note:
> > 
> >  FAB: 2.1.13 also includes a bootstrap version bump:
> > 
> >  Bootstrap 3.4.1 solves the following security issues:
> > 
> >  CVE-2018-14040 - Medium Severity Vulnerability Publish Date:
> 2018-07-13
> >  CVE-2018-14041 - Medium Severity Vulnerability Publish Date:
> 2018-07-13
> >  CVE-2018-14042 - Medium Severity Vulnerability Publish Date:
> 2018-07-13
> >  CVE-2018-20677 - Medium Severity Vulnerability Publish Date:
> 2019-01-09
> >  CVE-2019-8331 - Medium Severity Vulnerability Publish Date:
> 2019-02-20
> > 
> > 
> >  On 2019/09/26 09:46:54, Paul Vickers  .INVALID>
> >  wrote:
> > > If you are spinning up an update could you also consider including
> > > https://github.com/apache/incubator-superset/pull/8174 to fix
> OAuth
> >  logins?
> > >
> > > On Thu, 26 Sep 2019 at 10:10, Daniel Gaspar 
> > >> wrote:
> > >
> > >>
> > >> Looks good but I have two minor concerns:
> > >>
> > >> - Regarding #8025, the polygons chart still causes a division by
> zero,
> >  can
> > >> we include PR #8209?
> > >> - On dashboards the little box that shows what we are filtering
> for on
> > >> each chart disappeared, is it supposed to be like that?
> > >>
> > >>
> > >> On 2019/09/23 20:33:06, Ville Brofeldt <
> ville.v.brofe...@gmail.com>
> > >> wrote:
> > >>> Dear all,
> > >>>
> > >>>
> > >>> The source release 0.34.1 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 release mainly aims to fix bugs that have surfaced since the
> >  first
> > >>> official release 0.34.0. For context the `0.34` release branch
> was
> >  cut at
> > >>> SHA 9233a63, that was merged on master on Aug 8th 2019. 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.
> > >>>
> > >>>
> > >>> Cherries since 0.34.0:
> > >>>
> > >>> aaed4a77 updating version to 0.34.1
> > >>>
> > 

Re: [VOTE] Release Superset 0.34.1 based on Superset 0.34.1rc1

[Maxime Beauchemin]

+1 , pushed onto our infra and ran some manual tests aligned with the
recent cherries. LGTM

On Mon, Sep 23, 2019 at 6:07 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Thanks for doing this Ville!
>
> I'm hoping that Daniel and I will deploy, test and vote tomorrow.
>
> I'm also hoping that in the near future we could make Preset.io
> interactive instances available to members of the community for people to
> validate/test/reproduce bugs on release candidates. We're also thinking
> about running integration tests (and providing interactive environments)
> connected to popular analytics database engines (Redshift, BigQuery, Druid,
> Snowflake, ...).
>
> Max
>
> On Mon, Sep 23, 2019 at 1:33 PM Ville Brofeldt 
> wrote:
>
>> Dear all,
>>
>>
>> The source release 0.34.1 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 release mainly aims to fix bugs that have surfaced since the first
>> official release 0.34.0. For context the `0.34` release branch was cut at
>> SHA 9233a63, that was merged on master on Aug 8th 2019. 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.
>>
>>
>> Cherries since 0.34.0:
>>
>> aaed4a77 updating version to 0.34.1
>>
>> 30ded7dd [sql lab] persist tables list in localStorage (#8054)
>>
>> 301211b5 Revert "Fixed Histogram visualization bug.  (#8077)" (#8145)
>>
>> eb3cb955 fix: issues #8041 - bubble support for complex metrics (#8044)
>>
>> 7ca58f02 adding spaces missing from string concatenations (#8126)
>>
>> 9e6c0ab7 Update core.py (#8191)
>>
>> 7326f371 [feat] Add d3 legend formatting for Arc, Polygon and Scatter
>> deck.gl maps (#7951)
>>
>> 92481b7b [bugfix] Correctly quote table and schema in select_star (#8181)
>>
>> c5249cef Make orderby native sqla construct (#8180)
>>
>> 3136af12 [bugfix] fix timegrain addon regression (#8165)
>>
>> a8b05484 Add check for calls to cache_key_wrapper (#8128)
>>
>> 20a05954 Fix to Werkzeug ProxyFix; expose ProxyFix configuration items
>> (#8117)
>>
>> 4e49b8f3 Fixed Histogram visualization bug.  (#8077)
>>
>> 6f6e068c Set disableErrorBoundary in SuperChart to fix chart error
>> handling
>> (#8052)
>>
>> 08f19f1d  fix: onSave datasource raises React error (#8049)
>>
>> 66340f1a fix: handle case where result exists but corresponding query
>> cannot be found (#8037)
>>
>> f85ba81c [bugfix] Fix deck_polygon metric bug and update examples chart
>> (#8025)
>>
>> 85f959f6 [fix] Allow dashboard viewer auto refresh dashboard (#8014)
>>
>> de21a7f1 Fix: There was an issue fetching the favorite status of this
>> dashboard #6824 (#8013)
>>
>

Re: [VOTE] Release Superset 0.34.1 based on Superset 0.34.1rc1

[Maxime Beauchemin]

Thanks for doing this Ville!

I'm hoping that Daniel and I will deploy, test and vote tomorrow.

I'm also hoping that in the near future we could make Preset.io interactive
instances available to members of the community for people to
validate/test/reproduce bugs on release candidates. We're also thinking
about running integration tests (and providing interactive environments)
connected to popular analytics database engines (Redshift, BigQuery, Druid,
Snowflake, ...).

Max

On Mon, Sep 23, 2019 at 1:33 PM Ville Brofeldt 
wrote:

> Dear all,
>
>
> The source release 0.34.1 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 release mainly aims to fix bugs that have surfaced since the first
> official release 0.34.0. For context the `0.34` release branch was cut at
> SHA 9233a63, that was merged on master on Aug 8th 2019. 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.
>
>
> Cherries since 0.34.0:
>
> aaed4a77 updating version to 0.34.1
>
> 30ded7dd [sql lab] persist tables list in localStorage (#8054)
>
> 301211b5 Revert "Fixed Histogram visualization bug.  (#8077)" (#8145)
>
> eb3cb955 fix: issues #8041 - bubble support for complex metrics (#8044)
>
> 7ca58f02 adding spaces missing from string concatenations (#8126)
>
> 9e6c0ab7 Update core.py (#8191)
>
> 7326f371 [feat] Add d3 legend formatting for Arc, Polygon and Scatter
> deck.gl maps (#7951)
>
> 92481b7b [bugfix] Correctly quote table and schema in select_star (#8181)
>
> c5249cef Make orderby native sqla construct (#8180)
>
> 3136af12 [bugfix] fix timegrain addon regression (#8165)
>
> a8b05484 Add check for calls to cache_key_wrapper (#8128)
>
> 20a05954 Fix to Werkzeug ProxyFix; expose ProxyFix configuration items
> (#8117)
>
> 4e49b8f3 Fixed Histogram visualization bug.  (#8077)
>
> 6f6e068c Set disableErrorBoundary in SuperChart to fix chart error handling
> (#8052)
>
> 08f19f1d  fix: onSave datasource raises React error (#8049)
>
> 66340f1a fix: handle case where result exists but corresponding query
> cannot be found (#8037)
>
> f85ba81c [bugfix] Fix deck_polygon metric bug and update examples chart
> (#8025)
>
> 85f959f6 [fix] Allow dashboard viewer auto refresh dashboard (#8014)
>
> de21a7f1 Fix: There was an issue fetching the favorite status of this
> dashboard #6824 (#8013)
>

[ANNOUNCE] Please welcome new Superset committer & PPMC Daniel Gaspar

[Maxime Beauchemin]

All,

I'm pleased to announce that the Superset PMC has voted in Daniel Gaspar to
be
a committer and PPMC member. Daniel has been actively involved in the
project for some time
now, contributing patches, reviewing other's PRs, and participating in
Github issues as well as related discussions. Please join in me
congratulating Daniel for becoming a Superset committer & PPMC.

Welcome Daniel!

Cheers,

Max, on behalf of the Superset PMC

Re: Podling Report Reminder - September 2019

[Maxime Beauchemin]

Some post mortem notes:
* confluence "reset password" flow is broken, the flow might even break
other things (deactivate account when failed too many times? break an
account?)
* I hit a weird bug on id.apache.org , after logging in it would generate
an infinite page and ultimately crash my browser, resetting password there
fixed that issue
* resetting id in id.apache.org seem to take a while to propagate to
Confluence

Max

On Mon, Sep 9, 2019 at 3:01 PM Maxime Beauchemin 
wrote:

> Ooops, I think we crossed the streams here, I managed to get it in too.
>
> On Mon, Sep 9, 2019 at 2:59 PM Jeff Feng 
> wrote:
>
>> added!
>>
>> On Mon, Sep 9, 2019 at 1:47 PM Maxime Beauchemin <
>> maximebeauche...@gmail.com> wrote:
>>
>>> I can't login to Confluence, I even just went to reset my password as `
>>> id.apache.org`, tried all possible combinations on Confluence, but just
>>> can't seem to log on.
>>>
>>> Can someone with access please copy paste the doc I wrote?
>>>
>>> Max
>>>
>>> On Sun, Sep 8, 2019 at 1:37 PM Julian Feinauer <
>>> j.feina...@pragmaticminds.de> wrote:
>>>
>>>> Hey,
>>>>
>>>>
>>>>
>>>> short comment... Justin just checked… superset PPMC group has acces..
>>>> so just use ASF login.
>>>>
>>>>
>>>>
>>>> J
>>>>
>>>>
>>>>
>>>> *Von: *Julian Feinauer 
>>>> *Antworten an: *"dev@superset.incubator.apache.org" <
>>>> dev@superset.incubator.apache.org>
>>>> *Datum: *Sonntag, 8. September 2019 um 13:33
>>>> *An: *"dev@superset.incubator.apache.org" <
>>>> dev@superset.incubator.apache.org>
>>>> *Betreff: *Re: Podling Report Reminder - September 2019
>>>>
>>>>
>>>>
>>>> Hey,
>>>>
>>>>
>>>>
>>>> confuent is attached to ASF A/D now so just use your regular apache.org
>>>> credentials.
>>>>
>>>>
>>>>
>>>> J
>>>>
>>>>
>>>>
>>>> *Von: *Jeff Feng 
>>>> *Antworten an: *"dev@superset.incubator.apache.org" <
>>>> dev@superset.incubator.apache.org>
>>>> *Datum: *Sonntag, 8. September 2019 um 09:27
>>>> *An: *Apache Superset Dev 
>>>> *Betreff: *Re: Podling Report Reminder - September 2019
>>>>
>>>>
>>>>
>>>> I just tried and I somehow lost my access to update the wiki as well.
>>>>
>>>>
>>>>
>>>> On Sun, Sep 8, 2019 at 9:19 AM Maxime Beauchemin <
>>>> maximebeauche...@gmail.com> wrote:
>>>>
>>>> I'm been trying to edit
>>>> https://cwiki.apache.org/confluence/display/INCUBATOR/September2019 to
>>>> include our report, but been unsuccessful having troubles logging in and
>>>> changing my password
>>>>
>>>>
>>>>
>>>> Can someone else with working access copy/paste the report (google doc)
>>>> <https://docs.google.com/document/d/16rHtw1NEAxlhs_KgUc79BdPrLSeL4DILQ2suB2DgNSo/edit?usp=sharing>
>>>> into the wiki?
>>>>
>>>>
>>>>
>>>> Max
>>>>
>>>>
>>>>
>>>> On Fri, Sep 6, 2019 at 11:03 AM Alan Gates 
>>>> wrote:
>>>>
>>>> LGTM.
>>>>
>>>> Alan.
>>>>
>>>> On Fri, Sep 6, 2019 at 10:29 AM Maxime Beauchemin <
>>>> maximebeauche...@gmail.com> wrote:
>>>>
>>>> > Here's the link (still editing over the next 10-20 minutes), mentors
>>>> please
>>>> > feel free to comment on and review:
>>>> >
>>>> >
>>>> https://docs.google.com/document/d/16rHtw1NEAxlhs_KgUc79BdPrLSeL4DILQ2suB2DgNSo/edit?usp=sharing
>>>> >
>>>> > @mentors who can in charge of validating and adding to confluence?
>>>> >
>>>> > Max
>>>> >
>>>> > On Fri, Sep 6, 2019 at 10:19 AM Maxime Beauchemin <
>>>> > maximebeauche...@gmail.com> wrote:
>>>> >
>>>> > > Let me rush this right now, I had gotten the email but scanned it
>>>> and saw
>>>> > > "18 September 2019" and thought there was plenty of time.
>>>> > >
>>>> > > Max
>>>> > >
>>>> > > On Fri, Sep 6, 2019 at 12:28 AM Justin Mclean 
>>>> > wrote:
>>>> > >
>>>> > >> Hi,
>>>> > >>
>>>> > >> Anyone? It would be a shame for superset to start missing reports
>>>> (which
>>>> > >> are now overdue) given the recent progress.
>>>> > >>
>>>> > >> Thanks,
>>>> > >> Justin
>>>> > >>
>>>> > >
>>>> >
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> *Jeff Feng*
>>>>
>>>> Product Lead
>>>>
>>>> m: (949)-610-5108
>>>>
>>>> twitter: @jtfeng
>>>>
>>>>
>>>>
>>>
>>
>> --
>>
>> *Jeff Feng*
>> Product Lead
>> m: (949)-610-5108
>> twitter: @jtfeng
>>
>>

Re: Podling Report Reminder - September 2019

[Maxime Beauchemin]

Ooops, I think we crossed the streams here, I managed to get it in too.

On Mon, Sep 9, 2019 at 2:59 PM Jeff Feng 
wrote:

> added!
>
> On Mon, Sep 9, 2019 at 1:47 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
>> I can't login to Confluence, I even just went to reset my password as `
>> id.apache.org`, tried all possible combinations on Confluence, but just
>> can't seem to log on.
>>
>> Can someone with access please copy paste the doc I wrote?
>>
>> Max
>>
>> On Sun, Sep 8, 2019 at 1:37 PM Julian Feinauer <
>> j.feina...@pragmaticminds.de> wrote:
>>
>>> Hey,
>>>
>>>
>>>
>>> short comment... Justin just checked… superset PPMC group has acces.. so
>>> just use ASF login.
>>>
>>>
>>>
>>> J
>>>
>>>
>>>
>>> *Von: *Julian Feinauer 
>>> *Antworten an: *"dev@superset.incubator.apache.org" <
>>> dev@superset.incubator.apache.org>
>>> *Datum: *Sonntag, 8. September 2019 um 13:33
>>> *An: *"dev@superset.incubator.apache.org" <
>>> dev@superset.incubator.apache.org>
>>> *Betreff: *Re: Podling Report Reminder - September 2019
>>>
>>>
>>>
>>> Hey,
>>>
>>>
>>>
>>> confuent is attached to ASF A/D now so just use your regular apache.org
>>> credentials.
>>>
>>>
>>>
>>> J
>>>
>>>
>>>
>>> *Von: *Jeff Feng 
>>> *Antworten an: *"dev@superset.incubator.apache.org" <
>>> dev@superset.incubator.apache.org>
>>> *Datum: *Sonntag, 8. September 2019 um 09:27
>>> *An: *Apache Superset Dev 
>>> *Betreff: *Re: Podling Report Reminder - September 2019
>>>
>>>
>>>
>>> I just tried and I somehow lost my access to update the wiki as well.
>>>
>>>
>>>
>>> On Sun, Sep 8, 2019 at 9:19 AM Maxime Beauchemin <
>>> maximebeauche...@gmail.com> wrote:
>>>
>>> I'm been trying to edit
>>> https://cwiki.apache.org/confluence/display/INCUBATOR/September2019 to
>>> include our report, but been unsuccessful having troubles logging in and
>>> changing my password
>>>
>>>
>>>
>>> Can someone else with working access copy/paste the report (google doc)
>>> <https://docs.google.com/document/d/16rHtw1NEAxlhs_KgUc79BdPrLSeL4DILQ2suB2DgNSo/edit?usp=sharing>
>>> into the wiki?
>>>
>>>
>>>
>>> Max
>>>
>>>
>>>
>>> On Fri, Sep 6, 2019 at 11:03 AM Alan Gates  wrote:
>>>
>>> LGTM.
>>>
>>> Alan.
>>>
>>> On Fri, Sep 6, 2019 at 10:29 AM Maxime Beauchemin <
>>> maximebeauche...@gmail.com> wrote:
>>>
>>> > Here's the link (still editing over the next 10-20 minutes), mentors
>>> please
>>> > feel free to comment on and review:
>>> >
>>> >
>>> https://docs.google.com/document/d/16rHtw1NEAxlhs_KgUc79BdPrLSeL4DILQ2suB2DgNSo/edit?usp=sharing
>>> >
>>> > @mentors who can in charge of validating and adding to confluence?
>>> >
>>> > Max
>>> >
>>> > On Fri, Sep 6, 2019 at 10:19 AM Maxime Beauchemin <
>>> > maximebeauche...@gmail.com> wrote:
>>> >
>>> > > Let me rush this right now, I had gotten the email but scanned it
>>> and saw
>>> > > "18 September 2019" and thought there was plenty of time.
>>> > >
>>> > > Max
>>> > >
>>> > > On Fri, Sep 6, 2019 at 12:28 AM Justin Mclean 
>>> > wrote:
>>> > >
>>> > >> Hi,
>>> > >>
>>> > >> Anyone? It would be a shame for superset to start missing reports
>>> (which
>>> > >> are now overdue) given the recent progress.
>>> > >>
>>> > >> Thanks,
>>> > >> Justin
>>> > >>
>>> > >
>>> >
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Jeff Feng*
>>>
>>> Product Lead
>>>
>>> m: (949)-610-5108
>>>
>>> twitter: @jtfeng
>>>
>>>
>>>
>>
>
> --
>
> *Jeff Feng*
> Product Lead
> m: (949)-610-5108
> twitter: @jtfeng
>
>

Re: Podling Report Reminder - September 2019

[Maxime Beauchemin]

I can't login to Confluence, I even just went to reset my password as `
id.apache.org`, tried all possible combinations on Confluence, but just
can't seem to log on.

Can someone with access please copy paste the doc I wrote?

Max

On Sun, Sep 8, 2019 at 1:37 PM Julian Feinauer 
wrote:

> Hey,
>
>
>
> short comment... Justin just checked… superset PPMC group has acces.. so
> just use ASF login.
>
>
>
> J
>
>
>
> *Von: *Julian Feinauer 
> *Antworten an: *"dev@superset.incubator.apache.org" <
> dev@superset.incubator.apache.org>
> *Datum: *Sonntag, 8. September 2019 um 13:33
> *An: *"dev@superset.incubator.apache.org" <
> dev@superset.incubator.apache.org>
> *Betreff: *Re: Podling Report Reminder - September 2019
>
>
>
> Hey,
>
>
>
> confuent is attached to ASF A/D now so just use your regular apache.org
> credentials.
>
>
>
> J
>
>
>
> *Von: *Jeff Feng 
> *Antworten an: *"dev@superset.incubator.apache.org" <
> dev@superset.incubator.apache.org>
> *Datum: *Sonntag, 8. September 2019 um 09:27
> *An: *Apache Superset Dev 
> *Betreff: *Re: Podling Report Reminder - September 2019
>
>
>
> I just tried and I somehow lost my access to update the wiki as well.
>
>
>
> On Sun, Sep 8, 2019 at 9:19 AM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> I'm been trying to edit
> https://cwiki.apache.org/confluence/display/INCUBATOR/September2019 to
> include our report, but been unsuccessful having troubles logging in and
> changing my password
>
>
>
> Can someone else with working access copy/paste the report (google doc)
> <https://docs.google.com/document/d/16rHtw1NEAxlhs_KgUc79BdPrLSeL4DILQ2suB2DgNSo/edit?usp=sharing>
> into the wiki?
>
>
>
> Max
>
>
>
> On Fri, Sep 6, 2019 at 11:03 AM Alan Gates  wrote:
>
> LGTM.
>
> Alan.
>
> On Fri, Sep 6, 2019 at 10:29 AM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Here's the link (still editing over the next 10-20 minutes), mentors
> please
> > feel free to comment on and review:
> >
> >
> https://docs.google.com/document/d/16rHtw1NEAxlhs_KgUc79BdPrLSeL4DILQ2suB2DgNSo/edit?usp=sharing
> >
> > @mentors who can in charge of validating and adding to confluence?
> >
> > Max
> >
> > On Fri, Sep 6, 2019 at 10:19 AM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> > > Let me rush this right now, I had gotten the email but scanned it and
> saw
> > > "18 September 2019" and thought there was plenty of time.
> > >
> > > Max
> > >
> > > On Fri, Sep 6, 2019 at 12:28 AM Justin Mclean 
> > wrote:
> > >
> > >> Hi,
> > >>
> > >> Anyone? It would be a shame for superset to start missing reports
> (which
> > >> are now overdue) given the recent progress.
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> > >
> >
>
>
>
>
> --
>
> *Jeff Feng*
>
> Product Lead
>
> m: (949)-610-5108
>
> twitter: @jtfeng
>
>
>

Re: Podling Report Reminder - September 2019

[Maxime Beauchemin]

I'm been trying to edit
https://cwiki.apache.org/confluence/display/INCUBATOR/September2019 to
include our report, but been unsuccessful having troubles logging in and
changing my password
[image: Screen Shot 2019-09-08 at 9.15.42 AM.png]

Can someone else with working access copy/paste the report (google doc)
<https://docs.google.com/document/d/16rHtw1NEAxlhs_KgUc79BdPrLSeL4DILQ2suB2DgNSo/edit?usp=sharing>
into the wiki?

Max

On Fri, Sep 6, 2019 at 11:03 AM Alan Gates  wrote:

> LGTM.
>
> Alan.
>
> On Fri, Sep 6, 2019 at 10:29 AM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Here's the link (still editing over the next 10-20 minutes), mentors
> please
> > feel free to comment on and review:
> >
> >
> https://docs.google.com/document/d/16rHtw1NEAxlhs_KgUc79BdPrLSeL4DILQ2suB2DgNSo/edit?usp=sharing
> >
> > @mentors who can in charge of validating and adding to confluence?
> >
> > Max
> >
> > On Fri, Sep 6, 2019 at 10:19 AM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> > > Let me rush this right now, I had gotten the email but scanned it and
> saw
> > > "18 September 2019" and thought there was plenty of time.
> > >
> > > Max
> > >
> > > On Fri, Sep 6, 2019 at 12:28 AM Justin Mclean 
> > wrote:
> > >
> > >> Hi,
> > >>
> > >> Anyone? It would be a shame for superset to start missing reports
> (which
> > >> are now overdue) given the recent progress.
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> > >
> >
>

Re: Proposed Meetup One-off Schedule Change

[Maxime Beauchemin]

+1

On Sat, Sep 7, 2019 at 7:11 PM Daniel Gaspar  wrote:

>
>
> On 2019/09/06 21:06:11, Erik Ritter  wrote:
> > Hi All,
> >
> > As discussed in today's Superset Meetup, the current time we have
> scheduled
> > for meetups (every other Friday at 12PM PT) isn't very friendly to our
> > contributors in other parts of the world. As there are a few folks from
> > Europe that we already know of actively contributing to Superset, I'd
> like
> > to propose moving the next Superset Meetup to Thursday, September 19th at
> > 9AM PT. This should correspond to Thursday afternoon for our European
> > contributors and be much easier to attend than Friday nights.
> >
> > I'm proposing this as a one-off change to gauge interest, but we may want
> > to incorporate a rotating time for meetups into the official schedule in
> > the future as the community continues to grow. If consensus is positive
> > regarding the proposed time change, then I'll follow up confirming the
> > change.
> >
> > Thanks!
> > Erik
> >
>
> +1 Thanks
>

Re: Pypi Repo

[Maxime Beauchemin]

Confirmed, thanks much Charles!

Happy to add all other committers that want to get involved with releases.
Just send me your pypi username and I'll add you as an admin.

Thanks,

Max

On Fri, Sep 6, 2019 at 11:13 AM Charles Givre  wrote:

> HI Max,
> I just got an email from the Pypa folks and you should now have control
> over the apache-superset repo on Pypi.
> Thanks,
> -- C
>
>
> > On Sep 6, 2019, at 1:35 PM, Maxime Beauchemin 
> wrote:
> >
> > 0.34.0 <https://github.com/apache/incubator-superset/releases/tag/0.34.0
> >
> > Repository: apache/incubator-superset <
> https://github.com/apache/incubator-superset> · Tag: 0.34.0 <
> https://github.com/apache/incubator-superset/tree/0.34.0> · Commit:
> 20e68c8 <
> https://github.com/apache/incubator-superset/commit/20e68c87402414fabb3e0fd715be487fa7ebf5cc>
> · Released by: mistercrunch <https://github.com/mistercrunch>
> > Related release message to the ASF community
> >
> > Dear all,
> >
> > The source release 0.34.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
> >
> > We're using the 0.34 branch as the base for this first ASF release as
> opposed to 0.33 in previous attempts. I think all license-related issues
> have been ironed out in our dependency, here's the FOSSA report. 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 [yet-to-be-merged]
> RELEASING/README.md in the repo, latest edits here #8016 . As part of
> `RELEASING/`, we ship docker files to help test releases in a reproducible
> way.
> >
> > For context the `0.34` release branch was cut at SHA 9233a63, that was
> merged on master on Aug 8th 2019. 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.
> >
> > 
> > —
> > This release has 2 assets:
> >
> > Source code (zip)
> > Source code (tar.gz)
> > Visit the release page <
> https://github.com/apache/incubator-superset/releases/tag/0.34.0> to
> download them.
> >
> > —
> > You are receiving this because you are watching this repository.
> > View it on GitHub <
> https://github.com/apache/incubator-superset/releases/tag/0.34.0?email_source=notifications&email_token=ABKB7PQWZFGNWNZBP7PQPKTQIKIG3A5CNFSM4IULLUXKYY3PNVWWK3TUL52HS4DFU5JGK3DFMFZWLKTDN5WW2ZLOORPWSZGOAEXGAIY>
> or unsubscribe <
> https://github.com/apache/incubator-superset/unsubscribe_via_email/ABKB7PULUJWIOHU6EMBRGCTQIKIG3ANCNFSM4AS2FRJA>
> from all notifications for this repository.
> >
>
>

Re: Podling Report Reminder - September 2019

[Maxime Beauchemin]

Here's the link (still editing over the next 10-20 minutes), mentors please
feel free to comment on and review:
https://docs.google.com/document/d/16rHtw1NEAxlhs_KgUc79BdPrLSeL4DILQ2suB2DgNSo/edit?usp=sharing

@mentors who can in charge of validating and adding to confluence?

Max

On Fri, Sep 6, 2019 at 10:19 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Let me rush this right now, I had gotten the email but scanned it and saw
> "18 September 2019" and thought there was plenty of time.
>
> Max
>
> On Fri, Sep 6, 2019 at 12:28 AM Justin Mclean  wrote:
>
>> Hi,
>>
>> Anyone? It would be a shame for superset to start missing reports (which
>> are now overdue) given the recent progress.
>>
>> Thanks,
>> Justin
>>
>

Re: Podling Report Reminder - September 2019

[Maxime Beauchemin]

Let me rush this right now, I had gotten the email but scanned it and saw
"18 September 2019" and thought there was plenty of time.

Max

On Fri, Sep 6, 2019 at 12:28 AM Justin Mclean  wrote:

> Hi,
>
> Anyone? It would be a shame for superset to start missing reports (which
> are now overdue) given the recent progress.
>
> Thanks,
> Justin
>

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

[Maxime Beauchemin]

Yippee! Welcome aboard!

On Thu, Aug 29, 2019 at 2:27 PM Jeff Feng 
wrote:

> Congrats Erik!  So excited to have you as one of the Comitters!
>
> On Thu, Aug 29, 2019 at 11:55 AM Chris Williams
>  wrote:
>
> > CONGRATSSS! Very well deserved 🏆 👏
> >
> > Chris
> >
> > Data Visualization
> > San Francisco
> >
> >
> > On Thu, Aug 29, 2019 at 11:11 AM Michelle Thomas
> >  wrote:
> >
> > > Congrats Erik!!
> > >
> > > On Thu, Aug 29, 2019 at 10:11 AM Eli Brumbaugh
> > >  wrote:
> > >
> > > > Congratulations Erik! 🙌
> > > >
> > > > On Thu, Aug 29, 2019 at 10:03 AM Ville Brofeldt <
> > > > ville.v.brofe...@gmail.com>
> > > > 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
> > > >
> > >
> >
>
>
> --
>
> *Jeff Feng*
> Product Lead
> m: (949)-610-5108
> twitter: @jtfeng
>

Re: Convenience releases

[Maxime Beauchemin]

I couldn't find that person's contact info, so I'm not sure how to go about
it.

Max

On Wed, Aug 28, 2019 at 9:21 AM Stephanie Rivera 
wrote:

> Good point!
>
> Cheers,
>
> Stephanie
>
>
> *Stephanie Rivera* |* Vice President, Data Intelligence*
>
> 8181 Arista Place | Broomfield, CO 80021
>
> <
> http://www.google.com/url?q=http%3A%2F%2Fwww.spotxchange.com%2F&sa=D&sntz=1&usg=AFrqEzdlZjMtAvYRCQByfN6D_6PjZhSbSw
> >*Everyone
> you will ever meet knows something you don't.*
>
> <
> https://www.google.com/url?q=https%3A%2F%2Fdl.dropbox.com%2Fs%2F5se5ucpqodjsq1h%2Flinkedin.png&sa=D&sntz=1&usg=AFrqEzdTHQrlDWywpW7VZVpwGJJdOBY-Wg
> >
>
>
>
>
> On Wed, Aug 28, 2019 at 10:16 AM Bolke de Bruin  wrote:
>
> > You could argue that for a convenience release you could use "superset
> > based on the source release of Apache superset" which might get
> rid/reduce
> > the licensing challenge. It's not an official release channel so why
> treat
> > it as such?
> >
> > Did you try contacting the author on pypi's superset? It's a bit a
> > trademark issue I guess. You could ask Apache legal to help eventually as
> > trademark protection is important. Besides malware could be spread this
> way
> > as well.
> >
> > B.
> >
> > Sent from my iPhone
> >
> > > On 28 Aug 2019, at 18:04, Maxime Beauchemin <
> maximebeauche...@gmail.com>
> > wrote:
> > >
> > > Hi all,
> > >
> > > Now that 0.34.0 is out, I'd like to ship convenience releases in the
> for
> > of
> > > a PyPI.org release and a Docker image, ideally served on dockerhub.
> > >
> > > Now we have a few blockers/concerns:
> > >
> > > * as mentioned before, it looks like someone claimed "apache-superset"
> on
> > > pypi.org, probably by mistake.
> > https://pypi.org/user/cidiomar.dias.restoque/,
> > > there's no process to re-claim it just yet, but folks seem to be
> working
> > on
> > > it here https://github.com/pypa/warehouse/issues/1506. Anyone has the
> > > ability to pull strings at pypi.org ? :)
> > > * can we just use `superset` in pypi (which we own) or does it have to
> be
> > > `apache-superset`?
> > > * for a release to be convenient, we should ship our minified JS
> bundles,
> > > but I'm afraid that forces us to craft a 600+ entries LICENSE file
> > > dynamically. Workaround might be to add a `superset build` command that
> > > would well build this stuff. Requires having npm/node and such, working
> > on
> > > some user-space dir as we should treat `site-packages` as be immutable.
> > I'm
> > > not sure if that's reasonable/doable
> > > * about docker, I'm assuming similar licensing issues for images that
> > > contain minified bundles (is that the case?), but it's probably ok to
> > share
> > > just a Dockerfile itself
> > > * Maybe we should just automate the process that compiles the LICENSE
> > file
> > > with the 600 npm libs? I did a bit of work in that area before
> > > https://github.com/apache/incubator-superset/pull/5801
> > >
> > > Thoughts?
> > >
> > > Max
> >
>

Convenience releases

[Maxime Beauchemin]

Hi all,

Now that 0.34.0 is out, I'd like to ship convenience releases in the for of
a PyPI.org release and a Docker image, ideally served on dockerhub.

Now we have a few blockers/concerns:

* as mentioned before, it looks like someone claimed "apache-superset" on
pypi.org, probably by mistake. https://pypi.org/user/cidiomar.dias.restoque/,
there's no process to re-claim it just yet, but folks seem to be working on
it here https://github.com/pypa/warehouse/issues/1506. Anyone has the
ability to pull strings at pypi.org ? :)
* can we just use `superset` in pypi (which we own) or does it have to be
`apache-superset`?
* for a release to be convenient, we should ship our minified JS bundles,
but I'm afraid that forces us to craft a 600+ entries LICENSE file
dynamically. Workaround might be to add a `superset build` command that
would well build this stuff. Requires having npm/node and such, working on
some user-space dir as we should treat `site-packages` as be immutable. I'm
not sure if that's reasonable/doable
* about docker, I'm assuming similar licensing issues for images that
contain minified bundles (is that the case?), but it's probably ok to share
just a Dockerfile itself
* Maybe we should just automate the process that compiles the LICENSE file
with the 600 npm libs? I did a bit of work in that area before
https://github.com/apache/incubator-superset/pull/5801

Thoughts?

Max

[ANNOUNCE] Release Apache Superset (incubating) version 0.34.0

[Maxime Beauchemin]

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.

Re: Superset Meetup @ Preset

[Maxime Beauchemin]

Haven't heard of anyone I know going to ApacheCon this year :(

This will be under the "SF Bay Area Apache Superset Incubating meetup" but
broadcasted live and recorded
https://www.meetup.com/SF-Bay-Area-Apache-Superset-Incubating-Meetup/

Max

On Wed, Aug 21, 2019 at 2:51 PM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi Max,
>
> this is a nice idea.
> But, next month is also the Apache Con NA.
> Will be someone there from the Superset Team?
> It would also be a good opportunity to get in contact.
>
> I will be at the ApacheCon but I think I have no time to come over to you
> guys, sadly : /
>
> Julian
>
> Am 21.08.19, 23:43 schrieb "Maxime Beauchemin" <
> maximebeauche...@gmail.com>:
>
> Hey all!
>
> We'd love to host a Superset meetup at Preset (in San Mateo California)
> sometime next month. We have a fairly large office and can rent a
> bigger
> room upstairs if we need to adjust for a larger crowd. We'll also
> setup an
> A/V feed, live + recorded for people who cannot make it in time and
> space.
>
> We'd like to have 3-4 short-ish (10-20 minutes) talks, and have a Q/A
> panel
> with the committers present. If you'd like to speak please reach out
> to me
> directly and we can coordinate.
>
> Some (non-prescriptive!) ideas for talks:
> * how Superset is used in your organization / company, tweaks /
> extensions
> / integrations
> * visualization plugins and implementations
> * recent improvements / contributions to Superset
> * more general data visualization-related topics
> * ...
>
> I'll share the meetup invite as soon as we have a date and an agenda.
>
> Thanks,
>
> Max
>
>
>

Superset Meetup @ Preset

[Maxime Beauchemin]

Hey all!

We'd love to host a Superset meetup at Preset (in San Mateo California)
sometime next month. We have a fairly large office and can rent a bigger
room upstairs if we need to adjust for a larger crowd. We'll also setup an
A/V feed, live + recorded for people who cannot make it in time and space.

We'd like to have 3-4 short-ish (10-20 minutes) talks, and have a Q/A panel
with the committers present. If you'd like to speak please reach out to me
directly and we can coordinate.

Some (non-prescriptive!) ideas for talks:
* how Superset is used in your organization / company, tweaks / extensions
/ integrations
* visualization plugins and implementations
* recent improvements / contributions to Superset
* more general data visualization-related topics
* ...

I'll share the meetup invite as soon as we have a date and an agenda.

Thanks,

Max