Time for me to step down as a mentor

[Alan Gates]

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: Incubation Status report

[Alan Gates]

Whimsy appears to be pulling the SGA from
https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings/superset.yml
Justin, is that a generated file or do we edit it directly (as Superset
does have an SGA on file)?

I can't figure out where Whimsy is pulling the release info from, but
Superset has made several releases.

Alan.

On Wed, Dec 4, 2019 at 5:55 PM Maxime Beauchemin 
wrote:

> Hello @Mentors & Justin,
>
> As Superset gets closer to graduation, we're looking at the "Incubation
> Status" page, a manually maintained XML document on SVN
> <
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/superset.xml
> >
> [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: [Review/Sign Off Request] Superset Podling Report 12/2019

[Alan Gates]

Done.

Alan.

On Mon, Dec 2, 2019 at 2:08 PM Dellaena Maliszewski 
wrote:

> Good Afternoon!
> We have appended the Superset Podling Report for December 2019
> 
> to the wiki and request a review/sign off.
>
> *URL:*
> https://cwiki.apache.org/confluence/display/INCUBATOR/December2019#superset-1
>
> Thanks so much!
> Dellaena
>

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

[Alan Gates]

+1.  Checked the signature, hash, DISCLAIMER, NOTICE, and LICENSE files.
Checked that source files had license header and made sure there were no
binary files (beyond fonts and images).

Alan.

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: [VOTE] Release Superset 0.35.0 based on Superset 0.35.0rc2

[Alan Gates]

+1.  Reviewed the LICENSE, NOTICE, and DISCLAIMER files.  Looked for any
binary files or files not containing Apache License.  Checked the signature
and the shasum.

Alan.

On Mon, 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)
> 8847e105 Allow users to estimate query cost before executing it (#8172)
> b9be01fc Handle int64 columns with missing data in SQL Lab (#8226)
> bf7ce621 refactor: prepare control panel configs for separation into
> plugins (#8222)
> 1522d3fb fix: initialize control state for inline control config 

Re: Reminder to send a result message

[Alan Gates]

No worries, that's what incubation is for.  Congrats on pushing through
another release.

Alan.

On Mon, Oct 7, 2019 at 10:52 AM Ville Brofeldt 
wrote:

> Thanks Alan,
>
> sorry about the slip up (new to this voting business); will send through a
> result message pronto.
>
> Ville
>
> On Mon, Oct 7, 2019 at 8:47 PM Alan Gates  wrote:
>
> > Once you've closed a vote you should sent a message on the same thread
> with
> > a modified subject that adds [RESULT] and that summarizes the voting
> > results.  For example, on the current thread on the dev list (not yet
> > general since that vote is still open) the message would look like
> >
> > Subj:  [RESULT][VOTE] Release Superset 0.34.1 based on Superset 0.34.1rc2
> >
> > With 3 binding +1s (from Max, Daniel, and Ville) and no -1s the vote
> > passes.  Thanks to everyone who voted.
> > ...
> >
> > This gives people viewing the vote thread a quick way to see the results
> of
> > the vote without having to parse all of the vote emails in the thread.
> >
> > Alan.
> >
>

Reminder to send a result message

[Alan Gates]

Once you've closed a vote you should sent a message on the same thread with
a modified subject that adds [RESULT] and that summarizes the voting
results.  For example, on the current thread on the dev list (not yet
general since that vote is still open) the message would look like

Subj:  [RESULT][VOTE] Release Superset 0.34.1 based on Superset 0.34.1rc2

With 3 binding +1s (from Max, Daniel, and Ville) and no -1s the vote
passes.  Thanks to everyone who voted.
...

This gives people viewing the vote thread a quick way to see the results of
the vote without having to parse all of the vote emails in the thread.

Alan.

Re: Podling Report Reminder - September 2019

[Alan Gates]

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: [RESULT][VOTE] Release Superset 0.34.0 based on Superset 0.34.0rc1

[Alan Gates]

Yes, mentors are required to be part of the IPMC.  When Max starts the
thread on general I'll forward my +1.  So we'll just need one more, since
we also have Jakob's.

Alan.


On Sat, Aug 17, 2019 at 2:50 AM Bolke de Bruin  wrote:

> Alan
>
> Are you ipmc member as well? If so does your vote carry forward to the
> ipmc together with Jakob’s? Maybe its good to include that?
>
> B.
>
> Verstuurd vanaf mijn iPad
>
> > Op 16 aug. 2019 om 22:10 heeft Alan Gates  het
> volgende geschreven:
> >
> > Yes.
> >
> > Alan.
> >
> > On Fri, Aug 16, 2019 at 12:45 PM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> >> @mentors, so should I kick off a vote with general@ now?
> >>
> >> Max
> >>
> >>> On Fri, Aug 16, 2019 at 12:00 PM Jakob Homan 
> wrote:
> >>>
> >>> +1 (binding)
> >>> * Some LICENSEs appear to be missing; can be fixed next release
> >>> * Artifact contains rc1 suffix; usually this isn't the case.  Not sure
> >>> if the IPMC will be concerned
> >>> * Sig looks good
> >>> * DISCLAIMER/LICENSE (other than above)/NOTICE look good
> >>> * Spot check on headers look good
> >>>
> >>> -Jakob
> >>>
> >>> On Thu, Aug 15, 2019 at 4:11 PM Beto Dealmeida 
> >>> wrote:
> >>>>
> >>>> I can take a look at the release today and vote.
> >>>>
> >>>>> On 8/15/19 3:51 PM, Alan Gates wrote:
> >>>>> We should have a 3rd PPMC vote.  If we can get Thejas or Jakob to
> >> vote
> >>> as
> >>>>> mentors that will give us another PPMC vote and one more IPMC vote.
> >>>>>
> >>>>> Alan.
> >>>>>
> >>>>> On Thu, Aug 15, 2019 at 2:26 PM Maxime Beauchemin <
> >>>>> maximebeauche...@gmail.com> wrote:
> >>>>>
> >>>>>> Vote passes!
> >>>>>>
> >>>>>> +2 binding votes (Alan & Max)
> >>>>>> +3 non-binding vote (Ville, Charles, Bolke)
> >>>>>>
> >>>>>> No neutral or negative votes.
> >>>>>>
> >>>>>> Now (assuming 2 binding votes are enough) I have to figure out what
> >> my
> >>>>>> steps are. I think it consist of starting a vote thread similar to
> >>> this one
> >>>>>> on gene...@incubator.apache.org where I [think I] need 3 or more
> >> IPMC
> >>>>>> binding votes.
> >>>>>>
> >>>>>> Max
> >>>>>>
> >>>>>> On Mon, Aug 12, 2019 at 2:48 PM Maxime Beauchemin <
> >>>>>> maximebeauche...@gmail.com> wrote:
> >>>>>>
> >>>>>>> +cc Justin  I'd appreciate if you could do a pass on this as you
> >>>>>> uncovered
> >>>>>>> the most issues last time
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>>
> >>>>>>> Max
> >>>>>>>
> >>>>>>> On Mon, Aug 12, 2019 at 1:38 PM Maxime Beauchemin <
> >>>>>>> maximebeauche...@gmail.com> wrote:
> >>>>>>>
> >>>>>>>> We should probably develop and evolve guidelines on what
> >>> constitutes a
> >>>>>>>> release blocker. For this first Apache release I think we're more
> >>>>>> focussed
> >>>>>>>> on license-related topics and ASF-type requirements along with
> >>> "P0"-type
> >>>>>>>> blockers that would make significant portions of Superset
> >> unusable.
> >>>>>>>>
> >>>>>>>> Bellow are some of the issues raised in a previous release attempt
> >>> (from
> >>>>>>>> an email that Justin McLean sent). I believe everything in there
> >> has
> >>>>>> been
> >>>>>>>> tackled, but we should probably double check.
> >>>>>>>>
> >>>>>>>> ```
> >>>>>>>> I checked:
> >>>>>>>> - incubating is missing from name
> >>>>>>>> - signatures and hashes good
> >>>>>>>> - DISCLAIMER exists
> &g

Re: [RESULT][VOTE] Release Superset 0.34.0 based on Superset 0.34.0rc1

[Alan Gates]

Yes.

Alan.

On Fri, Aug 16, 2019 at 12:45 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> @mentors, so should I kick off a vote with general@ now?
>
> Max
>
> On Fri, Aug 16, 2019 at 12:00 PM Jakob Homan  wrote:
>
> > +1 (binding)
> > * Some LICENSEs appear to be missing; can be fixed next release
> > * Artifact contains rc1 suffix; usually this isn't the case.  Not sure
> > if the IPMC will be concerned
> > * Sig looks good
> > * DISCLAIMER/LICENSE (other than above)/NOTICE look good
> > * Spot check on headers look good
> >
> > -Jakob
> >
> > On Thu, Aug 15, 2019 at 4:11 PM Beto Dealmeida 
> > wrote:
> > >
> > > I can take a look at the release today and vote.
> > >
> > > On 8/15/19 3:51 PM, Alan Gates wrote:
> > > > We should have a 3rd PPMC vote.  If we can get Thejas or Jakob to
> vote
> > as
> > > > mentors that will give us another PPMC vote and one more IPMC vote.
> > > >
> > > > Alan.
> > > >
> > > > On Thu, Aug 15, 2019 at 2:26 PM Maxime Beauchemin <
> > > > maximebeauche...@gmail.com> wrote:
> > > >
> > > >> Vote passes!
> > > >>
> > > >> +2 binding votes (Alan & Max)
> > > >> +3 non-binding vote (Ville, Charles, Bolke)
> > > >>
> > > >> No neutral or negative votes.
> > > >>
> > > >> Now (assuming 2 binding votes are enough) I have to figure out what
> my
> > > >> steps are. I think it consist of starting a vote thread similar to
> > this one
> > > >> on gene...@incubator.apache.org where I [think I] need 3 or more
> IPMC
> > > >> binding votes.
> > > >>
> > > >> Max
> > > >>
> > > >> On Mon, Aug 12, 2019 at 2:48 PM Maxime Beauchemin <
> > > >> maximebeauche...@gmail.com> wrote:
> > > >>
> > > >>> +cc Justin  I'd appreciate if you could do a pass on this as you
> > > >> uncovered
> > > >>> the most issues last time
> > > >>>
> > > >>> Thanks,
> > > >>>
> > > >>> Max
> > > >>>
> > > >>> On Mon, Aug 12, 2019 at 1:38 PM Maxime Beauchemin <
> > > >>> maximebeauche...@gmail.com> wrote:
> > > >>>
> > > >>>> We should probably develop and evolve guidelines on what
> > constitutes a
> > > >>>> release blocker. For this first Apache release I think we're more
> > > >> focussed
> > > >>>> on license-related topics and ASF-type requirements along with
> > "P0"-type
> > > >>>> blockers that would make significant portions of Superset
> unusable.
> > > >>>>
> > > >>>> Bellow are some of the issues raised in a previous release attempt
> > (from
> > > >>>> an email that Justin McLean sent). I believe everything in there
> has
> > > >> been
> > > >>>> tackled, but we should probably double check.
> > > >>>>
> > > >>>> ```
> > > >>>> I checked:
> > > >>>> - incubating is missing from name
> > > >>>> - signatures and hashes good
> > > >>>> - DISCLAIMER exists
> > > >>>> - LICENSE is missing a few licenses (see below)
> > > >>>> - NOTICE should not include LICENSE information e.g The line about
> > CC
> > > >>>> 4.0. This may need to be removed. Also this content may be
> Category
> > X
> > > >> and
> > > >>>> this can’t included in a source release. [11]
> > > >>>> - Some 3rd party code have headers with "[LICENSE TBD]”
> > [4][5][6][7][9]
> > > >>>> which seems odd
> > > >>>> - The ASF headers on a number of files are not correct e.g the
> file
> > [13]
> > > >>>> and other under that directory (search for COPYRIGHT 2016 and and
> > > >> COPYRIGHT
> > > >>>> 2017 and COPYRIGHT 2018) Or are these files not actually licensed
> > to the
> > > >>>> ASF?
> > > >>>> - Source release may contained compiled code e.g [20] my
> > understanding
> > > >> is
> > > >>>> that a .mo file is compiled from the .po fi

Re: [RESULT][VOTE] Release Superset 0.34.0 based on Superset 0.34.0rc1

[Alan Gates]

We should have a 3rd PPMC vote.  If we can get Thejas or Jakob to vote as
mentors that will give us another PPMC vote and one more IPMC vote.

Alan.

On Thu, Aug 15, 2019 at 2:26 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Vote passes!
>
> +2 binding votes (Alan & Max)
> +3 non-binding vote (Ville, Charles, Bolke)
>
> No neutral or negative votes.
>
> Now (assuming 2 binding votes are enough) I have to figure out what my
> steps are. I think it consist of starting a vote thread similar to this one
> on gene...@incubator.apache.org where I [think I] need 3 or more IPMC
> binding votes.
>
> Max
>
> On Mon, Aug 12, 2019 at 2:48 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > +cc Justin  I'd appreciate if you could do a pass on this as you
> uncovered
> > the most issues last time
> >
> > Thanks,
> >
> > Max
> >
> > On Mon, Aug 12, 2019 at 1:38 PM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> >> We should probably develop and evolve guidelines on what constitutes a
> >> release blocker. For this first Apache release I think we're more
> focussed
> >> on license-related topics and ASF-type requirements along with "P0"-type
> >> blockers that would make significant portions of Superset unusable.
> >>
> >> Bellow are some of the issues raised in a previous release attempt (from
> >> an email that Justin McLean sent). I believe everything in there has
> been
> >> tackled, but we should probably double check.
> >>
> >> ```
> >> I checked:
> >> - incubating is missing from name
> >> - signatures and hashes good
> >> - DISCLAIMER exists
> >> - LICENSE is missing a few licenses (see below)
> >> - NOTICE should not include LICENSE information e.g The line about CC
> >> 4.0. This may need to be removed. Also this content may be Category X
> and
> >> this can’t included in a source release. [11]
> >> - Some 3rd party code have headers with "[LICENSE TBD]” [4][5][6][7][9]
> >> which seems odd
> >> - The ASF headers on a number of files are not correct e.g the file [13]
> >> and other under that directory (search for COPYRIGHT 2016 and and
> COPYRIGHT
> >> 2017 and COPYRIGHT 2018) Or are these files not actually licensed to the
> >> ASF?
> >> - Source release may contained compiled code e.g [20] my understanding
> is
> >> that a .mo file is compiled from the .po file. I not sure if it could be
> >> classified as code however, but even if that is so it may be best to
> remove
> >> them from the source release.
> >>
> >> There is a few bits of missing licensing  information:
> >> - How is the map date here licensed? [3] Is it from
> >> http://www.diva-gis.org/Data? I can see there is a credit in the code
> >> that has a link to https://bl.ocks.org/john-guerra. How is that code
> >> licensed?
> >> - This file [7] is missing from LICENSE I assume it’s public domain? [8]
> >> - This file [9] is licensed how? It seems to come from here [10] which
> >> says to contact the author for a license.
> >> - How is this image [14] licensed? (One reference I found said it could
> >> only be used for personal use [21])
> >> - LICENSE is missing license information for these fonts
> >> [15][16][17][18][19] The license for Glyphicons Halflings is complex
> and in
> >> this context (outside of bootstrap) a commercial license may be needed
> [22]
> >> and so it can’t be included.
> >>
> >> Some other improvements that could be made:
> >> - The LICENSE fieldworker is a little odd with headings like BSD
> 2-Clause
> >> licenses with noting under them, people (or tools) may incorrectly
> assume
> >> that it does contain BSD 2-Clause licensed code.
> >> - Make vote link link in future emails to lists.apache,org
> >> - Sign release with an apache.org email address
> >> - This [12] has copyright 2018 when it shovel be 2019
> >>
> >> Thanks,
> >> Justin
> >>
> >> 1. https://incubator.apache.org/policy/incubation.html#releases
> >> 2.
> >>
> https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
> >> 3. apache-superset
> >> -0.32.0rc2/superset/assets/src/visualizations/CountryMap/*
> >> 4.
> apache-superset-0.32.0rc2/superset/assets/vendor/cal-heatmap/cal-heatmap.js
> >> / .css
> >> 5
> apache-superset-0.32.0rc2/superset/assets/vendor/parallel_coordinates/d3.parcoords.js
> >> / .css
> >> 6. apache-superset
> >> -0.32.0rc2/superset/assets/vendor/parallel_coordinates/divgrid.js
> >> 7 apache-superset-0.32.0rc2/superset/assets/vendor/pygments.css
> >> 8. https://github.com/richleland/pygments-css/blob/master/UNLICENSE.txt
> >> 9. ./apache-superset
> >> -0.32.0rc2/superset/assets/vendor/parallel_coordinates/divgrid.js
> >> 10. http://bl.ocks.org/syntagmatic/3687826
> >> 11. http://www.tavfrna.incubator.apache.org/legal/resolved.html#cc-sa
> >> 12. ./apache-superset-0.32.0rc2/docs/conf.py
> >> 13. ./apache-superset-0.32.0rc2/superset/translations/messages.pot
> >> 14. ./apache-superset-0.32.0rc2/superset/assets/images/babytux.jpg
> >> 15. apache-superset
> >> 

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

[Alan Gates]

Ville is right, only PMC votes count for release, as the PMC is the group
delegated from the board to manage a project.

In the case of podling the PPMC's[1] vote is advisory and the Incubator PMC
(IPMC) is the legally binding vote, but mentors and the IPMC look to the
PPMC's vote as they assume the PPMC knows more about the project and as
it's good practice for the PPMC, since they will someday be the PMC for the
project.

So we need 3 PPMC votes, of which mentor votes count.  We have 2 currently
(me and Max).  Then we'll need 3 from the IPMC (again mentor votes count
here).

Alan.

1. PPMC stands for Podling PMC, or Practice PMC if you prefer.

On Mon, Aug 12, 2019 at 10:23 AM Ville Brofeldt 
wrote:

> It's my understanding that only PMC members can cast binding votes. Hence
> my non-binding vote (committer, not PMC member). Ville
>
>
> On Mon, Aug 12, 2019, 20:08 Bolke de Bruin  wrote:
>
> > We need binding votes from the committers... 3 being the minimum. Its
> > common to make it clear that you are either voting binding or non
> binding.
> > Binding votes can only be cast by committers.
> >
> > This is my +1, NON-binding.
> >
> > Bolke
> >
> > Verstuurd vanaf mijn iPad
> >
> > > Op 10 aug. 2019 om 06:16 heeft Ville Brofeldt <
> > ville.v.brofe...@gmail.com> het volgende geschreven:
> > >
> > > Hi all,
> > >
> > > I believe this is a good point in time to cut the 0.34 release, as
> there
> > > have been numerous important bugfixes and features introduced since
> 0.33,
> > > with especially important license housekeeping in the form of removal
> of
> > > requests (thanks Gianluca!) and FOSSA CI (thanks Max!). So would like
> to
> > > extend my non-binding +1 to this. Fingers crossed!
> > >
> > > Ville
> > >
> > > On Fri, Aug 9, 2019 at 9:36 PM Maxime Beauchemin <
> > maximebeauche...@gmail.com>
> > > wrote:
> > >
> > >> 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
> > >> <
> > >>
> >
> https://app.fossa.com/projects/custom+11342%2f...@github.com:apache%2Fincubator-superset.git/refs/branch/0.34/a04fad858644466219b7ea399aead110cb8ea655
> > >>>
> > >> . *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.
> > >>
> > >> 
> > >>
> >
> >
>

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

[Alan Gates]

+1.  Looked at the LICENSE, NOTICE, and DISCLAIMER files.  Checked the
licenses of files in the distro.

Alan.

On Fri, Aug 9, 2019 at 11:36 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> 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
> <
> https://app.fossa.com/projects/custom+11342%2f...@github.com:apache%2Fincubator-superset.git/refs/branch/0.34/a04fad858644466219b7ea399aead110cb8ea655
> >
> . *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.
>
> 
>

Re: [RESULT][VOTE] Release Superset 0.33.0 based on Superset 0.33.0rc1

[Alan Gates]

Again, I don't think this has to be fixed for your first incubator
release.  It will need to be fixed before you do a second release.  And if
you were a TLP you couldn't release with this.  But for now, as a learning
exercise and to get a release out ASAP, I'm ok without fixing it first.
Especially since there are similar issues to deal with on the JavaScript
side.

Alan.

On Tue, May 28, 2019 at 11:54 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> @community,  it'd be great if someone could volunteer to do this (making
> the python library "requests" an optional dependency). It appears it's used
> in its simplest form in a few places (requests.get) which should be easy to
> replace with urrlib2. The Druid connector uses a more advanced feature
> (basic auth), but that could be made just an optional dependency, as we're
> deprecating the Druid connector, to be replaced by the SQLAlchemy Druid
> connector/dialect. There it's just a matter of moving `pydruid` and
> `requests` to the "extra_requires" section of our setup.py, and doing late
> imports.
>
> If not it may take me a moment to get to do this on top of everything else
> needed for the ASF official release.
>
> Max
>
> On Sat, May 25, 2019 at 12:33 AM Bolke de Bruin  wrote:
>
> > https://issues.apache.org/jira/browse/LEGAL-192
> >
> > Details why. It comes down to that you can use LGPL, but only if it’s an
> > optional dependency. This is policy of the ASF in order not to limit
> > downstream usage of its own products. Ie. A Non optional dependency would
> > require downstream usage of Superset to abide by the LGPL (“reverse
> > engineering”) without a way out.
> >
> > As our use of the requests modules is fairly limited I suggest to
> > replicate the functionality that is required. Another option is to fork
> > requests and kick out the chardet dependency which is only used in one
> > place and probably not relevant to Superset.
> >
> > Cheers
> > Bolke
> >
> > Verstuurd vanaf mijn iPad
> >
> > > Op 23 mei 2019 om 01:37 heeft Maxime Beauchemin <
> > maximebeauche...@gmail.com> het volgende geschreven:
> > >
> > > Related, about requests/chardet
> > > https://github.com/kennethreitz/requests/issues/3389
> > >
> > > For the source code release, do [unbundled] deps need to be cleared?
> From
> > > my understanding we only needed to clear the code we ship.
> > >
> > > If that's the case we've got work to do on the JS side.
> > >
> > > Max
> > >
> > >> On Wed, May 22, 2019 at 4:11 PM Bolke de Bruin 
> > wrote:
> > >>
> > >> Oef chardet is pulled in by requests. The usage of chardet (ie
> > triggered)
> > >> is unlikely as it is only used when the encoding is not set in
> headers.
> > >>
> > >> You could ask the maintainer of chardet to release under another
> > license.
> > >> This can be tough as their might be several people to contact that
> need
> > to
> > >> agree with relicensing. Or do a PR to make the usage of chardet
> > optional in
> > >> requests. Or use urllib and maybe create a wrapper that mimics
> requests.
> > >>
> > >> B.
> > >>
> > >>
> > >> Verstuurd vanaf mijn iPad
> > >>
> > >>> Op 23 mei 2019 om 00:03 heeft Alan Gates  het
> > >> volgende geschreven:
> > >>>
> > >>> +1 with caveats, see below.  I looked at the LICENSE, NOTICE, and
> > >>> DISCLAIMER files, checked for any binary files (executables, there's
> > >> plenty
> > >>> of image files in the distribution), and looked over the licenses of
> > the
> > >>> dependencies.
> > >>>
> > >>> More information on the dependencies:
> > >>> I found https://pypi.org/project/pip-licenses/ which explains how to
> > >> check
> > >>> licenses, very useful.
> > >>>
> > >>> The licenses of modules that will be pulled in when a system is
> > compiled
> > >> or
> > >>> run matter, as the system won't run without them.  So it isn't ok to
> > >> have a
> > >>> GPL licensed library that's necessarily pulled in at compile/runtime,
> > as
> > >> to
> > >>> run the product you'll still be pulling in the GPL which will
> basically
> > >>> turn the whole thing GPL.  (Optional or contrib components are
> > different,
> >

Re: [RESULT][VOTE] Release Superset 0.33.0 based on Superset 0.33.0rc1

[Alan Gates]

+1 with caveats, see below.  I looked at the LICENSE, NOTICE, and
DISCLAIMER files, checked for any binary files (executables, there's plenty
of image files in the distribution), and looked over the licenses of the
dependencies.

More information on the dependencies:
I found https://pypi.org/project/pip-licenses/ which explains how to check
licenses, very useful.

The licenses of modules that will be pulled in when a system is compiled or
run matter, as the system won't run without them.  So it isn't ok to have a
GPL licensed library that's necessarily pulled in at compile/runtime, as to
run the product you'll still be pulling in the GPL which will basically
turn the whole thing GPL.  (Optional or contrib components are different,
as users can choose not to run with them if they aren't ok with the license
of the optional component.)

Running the above on the modules in setup.py, I see that the vast majority
are BSD, MIT, Apache, or PSFL, all of which are fine.  The ones that aren't
in that category are:
 certifi MPL-2.0: This is ok, as it's binary
 chardet LGPL Not Ok
 click   UNKNOWN
 jsonschema  UNKNOWN
 python-dateutil Dual License
 python-dotenv   UNKNOWN
 python-geohash  UNKNOWN
 python3-openid  UNKNOWN

The MPL one is fine since it's included in binary form.  The unknown and
dual license need some digging to determine what they are.  chardet, the
LGPL one, is not ok.

Since this is an incubating release I am still voting +1, with the caveat
that the unknown licenses need to be figured out before the next release,
and the LGPL dependency will have to be removed.  Right now I think getting
a release out is more important than fixing these issues.

Alan.

On Wed, May 22, 2019 at 2:01 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Oh actually the commands above just shows the dep tree.
>
> For deps in python there's
> https://github.com/dhatim/python-license-check
>
> On the JS side I did some work here to attempt building the LICENSE file
> dynamically as the dep tree evolves
> https://github.com/apache/incubator-superset/pull/5801
>
> I thought validating the licenses of deps wasn't necessary for source
> releases though. We may want to start the conversation on convenience
> releases. To me having solid docker images (or just dockerfiles if images
> are troublesome) (that are lean and optimized to build fast) would be
> ideal, especially if they are used in CI.
>
> Max
>
> On Wed, May 22, 2019 at 1:52 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Python:
> > pip install pipdeptree && pipdeptree
> >
> > NPM:
> > cd superset/assets && npm ls
> >
> > On Wed, May 22, 2019 at 11:09 AM Alan Gates 
> wrote:
> >
> >> Yes, I checked, it works now.  I just haven't yet because I'm still
> >> looking
> >> at all the dependencies it pulls in.  Maven makes this super easy to do,
> >> but I need to learn enough about python setuptools to figure out how to
> >> check the licenses on those modules.
> >>
> >> Alan.
> >>
> >> On Wed, May 22, 2019 at 10:56 AM Bolke de Bruin 
> >> wrote:
> >>
> >> > Is the signature now verifiable? Otherwise it won’t pass the IPMC ...
> >> >
> >> > Verstuurd vanaf mijn iPad
> >> >
> >> > > Op 22 mei 2019 om 19:26 heeft Maxime Beauchemin <
> >> > maximebeauche...@gmail.com> het volgende geschreven:
> >> > >
> >> > > Oops, changing thread title this time around
> >> > >
> >> > > Vote passes!
> >> > >
> >> > > +3 binding votes (Max, Jeff & Abhishek)
> >> > > +1 non-binding vote (Ville)
> >> > >
> >> > > No neutral or negative votes.
> >> > >
> >> > > On Tue, May 21, 2019 at 12:31 AM Jeff Feng
> >>  >> > >
> >> > > wrote:
> >> > >
> >> > >> +1 binding
> >> > >>
> >> > >> On Mon, May 20, 2019 at 3:54 PM Maxime Beauchemin <
> >> > >> maximebeauche...@gmail.com> wrote:
> >> > >>
> >> > >>> @Alan, looks like I messed up the signature somehow. I got tangled
> >> into
> >> > >>> adding a new entry (moving from my gmail to my apache.org
> address),
> >> > >>> deleting the old one and my svn kungfu is beyond rusty...
> >> > >>>
> >> > >>> Oh I think I just forgot to run "svn commit" (maybe i ran "svn
> >> u

Re: [RESULT][VOTE] Release Superset 0.33.0 based on Superset 0.33.0rc1

[Alan Gates]

Yes, I checked, it works now.  I just haven't yet because I'm still looking
at all the dependencies it pulls in.  Maven makes this super easy to do,
but I need to learn enough about python setuptools to figure out how to
check the licenses on those modules.

Alan.

On Wed, May 22, 2019 at 10:56 AM Bolke de Bruin  wrote:

> Is the signature now verifiable? Otherwise it won’t pass the IPMC ...
>
> Verstuurd vanaf mijn iPad
>
> > Op 22 mei 2019 om 19:26 heeft Maxime Beauchemin <
> maximebeauche...@gmail.com> het volgende geschreven:
> >
> > Oops, changing thread title this time around
> >
> > Vote passes!
> >
> > +3 binding votes (Max, Jeff & Abhishek)
> > +1 non-binding vote (Ville)
> >
> > No neutral or negative votes.
> >
> > On Tue, May 21, 2019 at 12:31 AM Jeff Feng  >
> > wrote:
> >
> >> +1 binding
> >>
> >> On Mon, May 20, 2019 at 3:54 PM Maxime Beauchemin <
> >> maximebeauche...@gmail.com> wrote:
> >>
> >>> @Alan, looks like I messed up the signature somehow. I got tangled into
> >>> adding a new entry (moving from my gmail to my apache.org address),
> >>> deleting the old one and my svn kungfu is beyond rusty...
> >>>
> >>> Oh I think I just forgot to run "svn commit" (maybe i ran "svn update"
> >>> instead?), so you should just have to import that new KEYS file and it
> >>> should work.
> >>>
> >>> Sorry about the confusion. All of this is pretty error-prone,
> especially
> >>> the [few] first time[s] around.
> >>>
> >>> Max
> >>>
> >>> On Mon, May 20, 2019 at 11:29 AM Abhishek Sharma <
> >>> abhioncbr.apa...@gmail.com>
> >>> wrote:
> >>>
> >>>> +1 binding.
> >>>>
> >>>> Newly built docker image
> >>>> <
> >>>>
> >>>
> >>
> https://cloud.docker.com/u/abhioncbr/repository/docker/abhioncbr/docker-superset
> >>>>>
> >>>> working fine.
> >>>>
> >>>> Thanks
> >>>> Abhishek
> >>>>
> >>>> On Mon, May 20, 2019 at 2:03 PM Alan Gates 
> >> wrote:
> >>>>
> >>>>> Max, when I check the signature (gpg --verify ) it tells me:
> >>>>> gpg: Signature made Sat May 18 15:36:55 2019 PDT
> >>>>> gpg:using RSA key
> >>>> 8CA186C4568E92301E5F2491A3B3BE2CCC1BB7E4
> >>>>> gpg: Can't check signature: No public key
> >>>>>
> >>>>> I imported the KEYS file referenced in your message, but it doesn't
> >>>> appear
> >>>>> to contain that key.  I think you need to either generate a new
> >>> signature
> >>>>> with the key in the file and upload that .asc file to the dist site
> >> (no
> >>>>> need to rerole the release itself) or place the key you used into the
> >>>> KEYS
> >>>>> file.
> >>>>>
> >>>>> Alan.
> >>>>>
> >>>>> On Sat, May 18, 2019 at 4:01 PM Maxime Beauchemin <
> >>>>> maximebeauche...@gmail.com> wrote:
> >>>>>
> >>>>>> Dear all,
> >>>>>>
> >>>>>> The source release 0.33.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 now attempting to use 0.33 as the base for the first release
> >> as
> >>>>>> opposed to 0.32 in previous attempts. Many license-related issues
> >> had
> >>>>> been
> >>>>>> solved by the process shipping visualizations as plugins, and that
> >>>>>> migration wasn't completed on 0.32. This is the third ASF release
> >>>>> candidate
> >>>>>> of Superset *We're still ironing out our release process, so please
> >>>> bear
> >>>>>> with us and help if you can*.
> >>>>>>
> >>>>>> As I went along, I documented the process in [yet-to-be-merged]
> >>>>>> RELEASING/README.md in the repo, latest edits here
> >>>>>> https://github.com/apache/incubator-superset/pull/7539 . As part
> >> of
> >>>>>> `RELEASING/`, we ship docker files to help package and test
> >> releases.
> >>>>>>
> >>>>>> For context the `0.33` release branch was cut at SHA 51068f007,
> >> that
> >>>> was
> >>>>>> merged on master on Apr 17th. 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.
> >>>>>>
> >>>>>> 7591a709 (tag: 0.33.0rc1, apache/release--0.33) 0.33.0rc1
> >>>>>> b7ffdb8b Improve instructions
> >>>>>> 4bbd68c6 Change babytux to open image in birth dashboard
> >>>>>> eaa679e8 remove unused LICENSE entries
> >>>>>> 42d50f9d Add Roboto font to LICENSE, remove glyphicons files
> >>>>>> 5ae2836b Address COPYRIGHT + LICENSE issues
> >>>>>> ea807f20 [WiP] Improvements related to ASF release process
> >>>>>> c57ef5dc 0.31.0rc1.dev1
> >>>>>> 51068f00 Adding permission for can_only_access_owned_queries
> >> (#7234)
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
> >> --
> >>
> >> *Jeff Feng*
> >> Product Lead
> >> m: (949)-610-5108
> >> twitter: @jtfeng
> >>
>

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

[Alan Gates]

Max, when I check the signature (gpg --verify ) it tells me:
gpg: Signature made Sat May 18 15:36:55 2019 PDT
gpg:using RSA key 8CA186C4568E92301E5F2491A3B3BE2CCC1BB7E4
gpg: Can't check signature: No public key

I imported the KEYS file referenced in your message, but it doesn't appear
to contain that key.  I think you need to either generate a new signature
with the key in the file and upload that .asc file to the dist site (no
need to rerole the release itself) or place the key you used into the KEYS
file.

Alan.

On Sat, May 18, 2019 at 4:01 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Dear all,
>
> The source release 0.33.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 now attempting to use 0.33 as the base for the first release as
> opposed to 0.32 in previous attempts. Many license-related issues had been
> solved by the process shipping visualizations as plugins, and that
> migration wasn't completed on 0.32. This is the third ASF release candidate
> of Superset *We're still ironing out our release process, so please bear
> with us and help if you can*.
>
> As I went along, I documented the process in [yet-to-be-merged]
> RELEASING/README.md in the repo, latest edits here
> https://github.com/apache/incubator-superset/pull/7539 . As part of
> `RELEASING/`, we ship docker files to help package and test releases.
>
> For context the `0.33` release branch was cut at SHA 51068f007, that was
> merged on master on Apr 17th. 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.
>
> 7591a709 (tag: 0.33.0rc1, apache/release--0.33) 0.33.0rc1
> b7ffdb8b Improve instructions
> 4bbd68c6 Change babytux to open image in birth dashboard
> eaa679e8 remove unused LICENSE entries
> 42d50f9d Add Roboto font to LICENSE, remove glyphicons files
> 5ae2836b Address COPYRIGHT + LICENSE issues
> ea807f20 [WiP] Improvements related to ASF release process
> c57ef5dc 0.31.0rc1.dev1
> 51068f00 Adding permission for can_only_access_owned_queries (#7234)
>

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

[Alan Gates]

+1.  Checked LICENSE, NOTICE, and DISCLAIMER files, signature and hash.
Checked to make sure there were no binary files in the distribution.

Alan.

On Fri, Apr 19, 2019 at 3:25 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Dear all,
>
> The source release 0.32.0 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 is the second ASF release candidate of Superset (!)* We're still
> ironing out our release process, so please bear with us and help if you
> can*
> .
>
> As I went along, I documented the process in RELEASING.md in the repo,
> latest edits here https://github.com/apache/incubator-superset/pull/7329
>
> For context (and similarly to 0.31) the `0.32` release branch was cut at
> SHA 1fece0d2f, that was merged on master on Jan 22nd. From that common
> ancestor, the following list of commit was added as cherry-picks. The SHAs
> in the list bellow reference the cherries on the release branch, PR number
> are available to get more details.
>
> New commits since 0.32.0rc1 *in bold:*
>
> *8fb4ba0d (HEAD -> release--0.32, tag: 0.32.0rc2) 0.32.0rc2*
> *3e6f6848 Add disclaimer and remove counter (#6738)*
> c7b32ac8 (tag: 0.32.0rc1, apache/release--0.32) 0.32.0rc1
> b89cdbdc RELEASING.md from master
> 0e23f2e6 Add sign.sh
> 21804346 [load_examples] download data at runtime (#7314)
> b32d5900 Remove LICENSE entry around dataset (#7318)
> b3aa5633 (release--0.31) 0.31rc23
> 24a595f4 bugfix: improve 'Time Table' (#6959)
> c70abbed 0.31rc22
> dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244)
> 2ab07a08 Fix race condition when fetching results in SQL Lab (#7198)
> (#7242)
> a9d54894 0.31.0rc21
> b959fcd2 fix PRODUCT-67916 Click OK button cannot close error message modal
> (#7179)
> 2da9613f Update __init__.py (#7166)
> 538da2e3 0.31.0.rc20
> 7ce35d2a [migration] Fixing issue with fb13d49b72f9 downgrade (#7145)
> 947f02ff [migration] Fixing issue with c82ee8a39623 downgrade (#7144)
> daf2b8e5 Bump python lib croniter to an existing version (#7132)
> eb4c1355 Use metric name instead of metric in filter box (#7106)
> 2ff721ae handle null column_name in sqla and druid models
> e83a07d3 [forms] Fix handling of NULLs
> 76d26f37 0.31.0.rc19
> fe78b4ec Fix filter_box migration PR #6523 (#7066)
> c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined query
> (#7029)
> b64a452a [sql lab] improve table name detection in free form SQL (#6793)
> 2357c4aa Adding custom control overrides (#6956)
> 9dd7e84a [sql-parse] Fixing LIMIT exceptions (#6963)
> 5d8dd142 [csv-upload] Fixing message encoding (#6971)
> f454dedd [main] Disable resetting main DB attributes (#6845)
> e967b268 [sqla] Fixing order-by for non-inner-joins (#6862)
> a5d9a4e0 Adding template_params to datasource editor for sqla tables
> (#6869)
> 6b895413 [datasource] Ensuring consistent behavior of datasource
> editing/saving. (#7037)
> 8ef2789f Adding warning message for sqllab save query (#7028)
> 0ebdb564 fix inaccurate data calculation with adata rolling and
> contribution (#7035)
> b3af6a26 [fix] explore chart from dashboard missed slice title (#7046)
> c54b067c [db-engine-spec] Aligning Hive/Presto partition logic (#7007)
> bd65942e Changing time table viz to pass formatTime a date (#7020)
> 50accda9 [fix] Cursor jumping when editing chart and dashboard titles
> (#7038)
> 5ace5769 0.31.0rc17
> 927a5846 [WIP] fix user specified JSON metadata not updating dashboard on
> refresh (#7027)
> fafb824d 0.31.0rc16
> 7b72985e [fix] /superset/slice/id url is too long (#6989)
> b497d9e7 fix dashboard links in welcome page (#6756)
> c42afa11 0.31.0rc15
> 35c55278 Enhancement of query context and object. (#6962)
> 1c41020c Split tags migration (#7002)
> ec7a0b22 0.31.0rc14
> 4655cb4c Remove Cypress from package.json (#6912)
> fb8e3208 0.31.0rc13
> b4cbe13d VIZ-190 fix (#6958)
> 5b7b22fd 0.31.0rc12
> 51804229 Fix deck.gl form data (#6953)
> 9939a52d 0.31.0rc11
> c3db74d9 (apache/cherry_c3db74d9021f9e60ef21beeb0847ff9f4b0277fd) Fix
> rendering regression from the introduction of bignumber (#6937)
> 9940d30a 0.31.0rc10
> 3df2b8d5 Add a safety check before getting clientHeight (#6923)
> ccb51385 v0.31.0rc9
> db0235fb Fix database typeahead in SQL Lab (#6917)
> 953d6dc9 Address tooltip's disappearance and stickiness (#6898)
> c0eaa5f6 Fix extra_filters in multi line viz (#6868)
> ebcadc1f (apache/cherry_ebcadc1f50994d98bd3dc42e2199b8d0328c061c) Fix
> tooltip (#6895)
> 5fa5acb5 Add show metadata button back to the explore view (#6911)
> ce76560a v0.31.0rc8
> 8c549b46 Relayout SQL Editor (#6872)
> bfe18963 [cosmetic] TableSelector use  instead of  for refresh
> (#6783)
> 19b588b5 0.31.0rc7
> d7e038ea Fixing issue where tooltip gets hidden on dashboard for all charts
> (#6852)
> 38e0ddac 0.31.0rc6
> b7d2bd09 Fix line chart overflowing the right side (#6829)
> b7e02ab7 [sql 

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

[Alan Gates]

-1, the DISCLAIMER file was removed.  It was present in the previous rc.

Alan.

On Thu, Apr 18, 2019 at 10:36 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Dear all,
>
> The source release 0.32.0 RC1 for Apache Superset is baked and available
> at:
> https://dist.apache.org/repos/dist/dev/incubator/superset/, public
> keys are available
> at https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
>
> This is the second ASF release candidate of Superset (!)* We're still
> ironing out our release process, so please bear with us and help if you
> can*
> .
>
> As I went along, I documented the process in RELEASING.md in the repo,
> latest edits here https://github.com/apache/incubator-superset/pull/7329
>
> For context (and similarly to 0.31) the `0.32` release branch was cut at
> SHA 1fece0d2f, that was merged on master on Jan 22nd. From that common
> ancestor, the following list of commit was added as cherry-picks. The SHAs
> in the list bellow reference the cherries on the release branch, PR number
> are available to get more details.
>
> b89cdbdc RELEASING.md from master
> 0e23f2e6 Add sign.sh
> 21804346 [load_examples] download data at runtime (#7314)
> b32d5900 Remove LICENSE entry around dataset (#7318)
> b3aa5633 (release--0.31) 0.31rc23
> 24a595f4 bugfix: improve 'Time Table' (#6959)
> c70abbed 0.31rc22
> dd8c2db9 [filter_box] allow empty filters list (#7220) (#7244)
> 2ab07a08 Fix race condition when fetching results in SQL Lab (#7198)
> (#7242)
> a9d54894 0.31.0rc21
> b959fcd2 fix PRODUCT-67916 Click OK button cannot close error message modal
> (#7179)
> 2da9613f Update __init__.py (#7166)
> 538da2e3 0.31.0.rc20
> 7ce35d2a [migration] Fixing issue with fb13d49b72f9 downgrade (#7145)
> 947f02ff [migration] Fixing issue with c82ee8a39623 downgrade (#7144)
> daf2b8e5 Bump python lib croniter to an existing version (#7132)
> eb4c1355 Use metric name instead of metric in filter box (#7106)
> 2ff721ae handle null column_name in sqla and druid models
> e83a07d3 [forms] Fix handling of NULLs
> 76d26f37 0.31.0.rc19
> fe78b4ec Fix filter_box migration PR #6523 (#7066)
> c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined query
> (#7029)
> b64a452a [sql lab] improve table name detection in free form SQL (#6793)
> 2357c4aa Adding custom control overrides (#6956)
> 9dd7e84a [sql-parse] Fixing LIMIT exceptions (#6963)
> 5d8dd142 [csv-upload] Fixing message encoding (#6971)
> f454dedd [main] Disable resetting main DB attributes (#6845)
> e967b268 [sqla] Fixing order-by for non-inner-joins (#6862)
> a5d9a4e0 Adding template_params to datasource editor for sqla tables
> (#6869)
> 6b895413 [datasource] Ensuring consistent behavior of datasource
> editing/saving. (#7037)
> 8ef2789f Adding warning message for sqllab save query (#7028)
> 0ebdb564 fix inaccurate data calculation with adata rolling and
> contribution (#7035)
> b3af6a26 [fix] explore chart from dashboard missed slice title (#7046)
> c54b067c [db-engine-spec] Aligning Hive/Presto partition logic (#7007)
> bd65942e Changing time table viz to pass formatTime a date (#7020)
> 50accda9 [fix] Cursor jumping when editing chart and dashboard titles
> (#7038)
> 5ace5769 0.31.0rc17
> 927a5846 [WIP] fix user specified JSON metadata not updating dashboard on
> refresh (#7027)
> fafb824d 0.31.0rc16
> 7b72985e [fix] /superset/slice/id url is too long (#6989)
> b497d9e7 fix dashboard links in welcome page (#6756)
> c42afa11 0.31.0rc15
> 35c55278 Enhancement of query context and object. (#6962)
> 1c41020c Split tags migration (#7002)
> ec7a0b22 0.31.0rc14
> 4655cb4c Remove Cypress from package.json (#6912)
> fb8e3208 0.31.0rc13
> b4cbe13d VIZ-190 fix (#6958)
> 5b7b22fd 0.31.0rc12
> 51804229 Fix deck.gl form data (#6953)
> 9939a52d 0.31.0rc11
> c3db74d9 (apache/cherry_c3db74d9021f9e60ef21beeb0847ff9f4b0277fd) Fix
> rendering regression from the introduction of bignumber (#6937)
> 9940d30a 0.31.0rc10
> 3df2b8d5 Add a safety check before getting clientHeight (#6923)
> ccb51385 v0.31.0rc9
> db0235fb Fix database typeahead in SQL Lab (#6917)
> 953d6dc9 Address tooltip's disappearance and stickiness (#6898)
> c0eaa5f6 Fix extra_filters in multi line viz (#6868)
> ebcadc1f (apache/cherry_ebcadc1f50994d98bd3dc42e2199b8d0328c061c) Fix
> tooltip (#6895)
> 5fa5acb5 Add show metadata button back to the explore view (#6911)
> ce76560a v0.31.0rc8
> 8c549b46 Relayout SQL Editor (#6872)
> bfe18963 [cosmetic] TableSelector use  instead of  for refresh
> (#6783)
> 19b588b5 0.31.0rc7
> d7e038ea Fixing issue where tooltip gets hidden on dashboard for all charts
> (#6852)
> 38e0ddac 0.31.0rc6
> b7d2bd09 Fix line chart overflowing the right side (#6829)
> b7e02ab7 [sql lab] fix stuck offline (#6782)
> 8a7c245c 0.31.0rc5
> f24efa72 Backend only tagging system (#6823)
> 1ddacc42 [wtforms] Using wtforms-json which supports None (#5445)
> 4f37b9ae 0.31.0rc4
> 845c7aa9 creating new circular-json safe stringify and replacing one call
> (#6772)
> 8ea805ea 

Re: [VOTE] Release Superset 0.31.0 based on Superset 0.31.0 RC18

[Alan Gates]

The PR looks fine, except that if Superset doesn't include that data as
part of the distribution you should remove the CC BY 4 license note from
LICENSE.

To be clear, I wasn't saying you had to remove those files.  IIUC it's fine
to distribute that data under that license.  I just wanted to be clear on
what was covered by that license.  Since you can't put headers in the data
files I'd just put a note in the LICENSE file like ".csv and .csv.gz files
in this directory are included under CC BY 4" or something.

Alan.

On Tue, Apr 16, 2019 at 11:20 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> @Alan Gates  I'm hoping that I addressed the
> data-related issue here
> https://github.com/apache/incubator-superset/pull/7314
>
> On Tue, Apr 16, 2019 at 5:17 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
>> Given the os-level dependencies and all sorts of other environmental
>> things, like whether we should use "virutalenv" or not, or the fact that we
>> recommend to have a second clone of the repo (because "git clean" will
>> remove everything that is not git ignored, like your virtualenv or local
>> configs), I'm tempted to use docker as a reproducible way to generate and
>> test the source release. This would make the process more insulated and
>> reproducible. Seems reasonable?
>>
>> Max
>>
>> On Tue, Apr 16, 2019 at 5:01 PM Maxime Beauchemin <
>> maximebeauche...@gmail.com> wrote:
>>
>>> For context David, setup.py says "croniter>=0.3.28" but
>>> "requirements.txt" has it pinned, though the INSTALL.txt does not
>>> [currently at least] say to install the pinned deps.
>>>
>>> It's debatable whether we should add "pip install -r requirements.txt"
>>> in INSTALL.txt, but I think given that Superset is an application, I think
>>> we should do it.
>>>
>>> Max
>>>
>>> On Tue, Apr 16, 2019 at 2:16 PM David Smith 
>>> wrote:
>>>
>>>> True, things can come up. But the croniter issue occurred 21 days ago
>>>> <https://github.com/taichino/croniter/issues/124> and should not have
>>>> been
>>>> an issue .  We probably don't need to take this thread into a deep
>>>> discussion about this, but I do think this is a huge gap in how branch
>>>> mechanics are moving code around and how it feeds the release
>>>> process/chronology.  I'll move the discussion to a more appropriate
>>>> channel.
>>>>
>>>> Dave
>>>>
>>>>
>>>> On Tue, Apr 16, 2019 at 2:01 PM Bolke de Bruin 
>>>> wrote:
>>>>
>>>> > I think this one was “mid-flight”. A dependency was deleted from the
>>>> repos
>>>> > after the release candidate was created. That’s a race condition that
>>>> is
>>>> > kind of unsolvable ;-).
>>>> >
>>>> > Verstuurd vanaf mijn iPad
>>>> >
>>>> > > Op 16 apr. 2019 om 20:19 heeft David Smith 
>>>> het
>>>> > volgende geschreven:
>>>> > >
>>>> > > What tests are being performed before releasing? To be blunt: we
>>>> > shouldn't
>>>> > > be able to get to a "release" vote without validating that the code
>>>> runs,
>>>> > > we need to make the process account for robust testing.
>>>> > >
>>>> > >> On Tue, Apr 16, 2019 at 11:11 AM Bolke de Bruin >>> >
>>>> > wrote:
>>>> > >>
>>>> > >> Have to change to -1, non-binding due to the below mentioned
>>>> issue. It
>>>> > >> seems to be a kind of blocker for a first release ;-)
>>>> > >>
>>>> > >> I suggest restarting the ([CANCEL] first [VOtE] next )vote with a
>>>> fix
>>>> > and
>>>> > >> a bit more boiler plate in the message (binding/non binding, 72h
>>>> etc).
>>>> > >>
>>>> > >> B.
>>>> > >>
>>>> > >> Verstuurd vanaf mijn iPad
>>>> > >>
>>>> > >>> Op 16 apr. 2019 om 02:27 heeft abhishek sharma <
>>>> > >> abhioncbr.apa...@gmail.com> het volgende geschreven:
>>>> > >>>
>>>> > >>> -1 (since, depenedency croniter==0.3.26 is failing.)
>>>> > >>&

Re: [VOTE] Release Superset 0.31.0 based on Superset 0.31.0 RC18

[Alan Gates]

Per https://www.apache.org/legal/resolved.html#cc-by the CC BY 4.0 license
can only be used on things included in binary form.  It appears that it is
data from the diva-gis.org that is being included under this license, which
I would think meets the requirement.  But I don't know how to verify that
only data files from that source are being included.  Is there a list
somewhere of the files included from that source?

Other than that, things look good.  License, notice, and disclaimer files
all look good.  All the .py and .sh files have the appropriate Apache
License header, I didn't find any binaries.

Alan.

On Mon, Apr 15, 2019 at 10:47 AM John Bodley 
wrote:

> +1
>
> On Sun, Apr 14, 2019 at 9:18 AM Krist Wongsuphasawat <
> krist.wo...@gmail.com>
> wrote:
>
> > +1 exciting!
> >
> > Best regards,
> >
> > Krist
> >
> > --
> >
> > Krist Wongsuphasawat
> > http://kristw.yellowpigz.com
> > On Apr 14, 2019, 06:24 -0700, Jeff Feng ,
> > wrote:
> > > +1 Binding
> > >
> > > On Sun, Apr 14, 2019 at 6:20 AM Bolke de Bruin 
> > wrote:
> > >
> > > > +1, non-binding
> > > >
> > > > I checked:
> > > >
> > > > * SHA512
> > > > * Signature of the release, can use some improvement but the key
> > checks out
> > > > here (https://people.apache.org/keys/committer/):
> > > >
> > > > gpg: Signature made Tue Mar 19 07:35:24 2019 CET
> > > > gpg: using RSA key BB990B01715969F648C7A65472DC479A3011B01B
> > > > gpg: Good signature from "Maxime Beauchemin <
> > maximebeauche...@gmail.com>"
> > > > [unknown]
> > > > gpg: WARNING: This key is not certified with a trusted signature!
> > > > gpg: There is no indication that the signature belongs to the
> > > > owner.
> > > > Primary key fingerprint: BB99 0B01 7159 69F6 48C7 A654 72DC 479A 3011
> > B01B
> > > >
> > > > * NOTICE present
> > > > * LICENSE present
> > > > * DISCLAIMER present
> > > > * INSTALL.txt present (did not check build)
> > > > * ran apache-rat
> > > >
> > > > Good luck at the incubator!
> > > >
> > > > (O and the vote is open for a minimum of 48h I believe :-) ).
> > > >
> > > > B.
> > > >
> > > >
> > > >
> > > > On 14 April 2019 at 00:24:11, Jeff Feng (jeff.f...@airbnb.com.invalid
> )
> > > > wrote:
> > > >
> > > > ++ this is very exciting. Thank you Max!
> > > >
> > > > On Sat, Apr 13, 2019 at 3:19 PM Bolke de Bruin 
> > wrote:
> > > >
> > > > > Great stuff Max! Good to see this happening!
> > > > >
> > > > > - Maybe good to note that only the vote of committers counts as a
> > binding
> > > > > vote and that it's good practice to make that clear when voting?
> > > > >
> > > > > I'll verify the release tomorrow.
> > > > >
> > > > > B.
> > > > >
> > > > > Sent from my iPhone
> > > > >
> > > > > > On 13 Apr 2019, at 23:56, Maxime Beauchemin <
> > > > maximebeauche...@gmail.com>
> > > >
> > > > > wrote:
> > > > > >
> > > > > > Dear all,
> > > > > >
> > > > > > The source release 0.31.0 RC18 for Apache Superset is baked and
> > > > available
> > > > > > at:
> > > > > > https://dist.apache.org/repos/dist/dev/incubator/superset/,
> public
> > > > > > keys are available
> > > > > > at
> > https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> > > > > >
> > > > > > This is the first ASF release candidate of Superset (!)* We're
> > still
> > > > > > ironing out our release process, so please bear with us and help
> > if you
> > > > > can*.
> > > > > > Note that we understand that starting at "RC18" is confusing, but
> > > > > > constitute an outlier as we handoff from the old process to the
> new
> > > > one.
> > > > > > From this point onwards, we intend on using a linear sequence
> that
> > maps
> > > > > > one-to-one with Apache-submitted release candidates. The term
> > release
> > > > > > candidate and label RC should be exclusive to the proper
> > > > Apache-compliant
> > > > > > release process moving forward.
> > > > > >
> > > > > > Also note that I decided to use the label `0.31.0rc18` (pypi
> > compliant)
> > > > > > instead of a semver compliant `0.31.0-rc.18` which Pypi and
> > Python's
> > > > > > PEP-440 won't allow. This being a Python project, we use Python's
> > > > > standards.
> > > > > >
> > > > > > As I went along, I documented the process in RELEASING.md in the
> > repo,
> > > > > > latest edits here
> > > > > > https://github.com/apache/incubator-superset/pull/7296/files
> > > > > >
> > > > > > For context, the `0.31` release branch was cut at SHA 1fece0d2f,
> > that
> > > > was
> > > > > > merged on master on Jan 22nd. From that common ancestor, the
> > following
> > > > > list
> > > > > > of commit was added as cherry-picks. The SHAs in the list bellow
> > > > > reference
> > > > > > the cherries on the release branch, PR number are available to
> get
> > more
> > > > > > details.
> > > > > >
> > > > > > c43d0fd3 [sqlparse] Fixing table name extraction for ill-defined
> > query
> > > > > > (#7029)
> > > > > > b64a452a [sql lab] improve table name detection in free form SQL
> > > > (#6793)
> > > > > > 2357c4aa Adding custom control 

Re: [DISCUSS] Best place for questions / answers

[Alan Gates]

The feedback on general has been mostly positive, and there doesn't seem to
be any solid policy for or against.  You can see the thread at
https://lists.apache.org/thread.html/fc4971196fa9230ceb89deb25ee9a6b136dce06553288d903b5b538a@%3Cgeneral.incubator.apache.org%3E

There's useful feedback in the thread from Julian on using SO to help with
community building and Ted on how to connect it to your user list so people
on one can find things on the other.

Alan.

On Wed, Apr 3, 2019 at 5:55 PM Alan Gates  wrote:

> I can't see any reason why that would be an issue, but I'll ask on general@
> to make sure.
>
> Alan.
>
> On Wed, Apr 3, 2019 at 5:48 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
>> Mentors! As we seem to drift towards a StackOverflow consensus, can we get
>> an ASF stamp on directing question traffic in that direction?
>>
>> Max
>>
>> On Wed, Apr 3, 2019 at 4:00 PM David Smith 
>> wrote:
>>
>> > +1 for Stackoverflow.  I think Discourse, Discord, Slack, etc all have
>> the
>> > same discoverability problem.
>> >
>> > On Wed, Apr 3, 2019 at 3:50 PM Stephanie Rivera
>> 
>> > wrote:
>> >
>> > > +1 stack overflow
>> > >
>> > > Cheers,
>> > >
>> > > Stephanie Rivera
>> > > sent from my mobile
>> > >
>> > > On Wed, Apr 3, 2019, 4:18 PM Jeff Feng 
>> > > wrote:
>> > >
>> > > > ++ agreed on Q on Stackoverflow or Discourse and not on email as
>> > well.
>> > > >
>> > > > On Wed, Apr 3, 2019 at 3:17 PM Vyl Chiang > >
>> > > > wrote:
>> > > >
>> > > > > +1 on stackoverflow or discourse and not on mailing list
>> > > > > Vyl Chiang
>> > > > > Product
>> > > > > 650.279.1185
>> > > > >
>> > > > > <https://www.lyft.com/>
>> > > > >
>> > > > >
>> > > > > On Wed, Apr 3, 2019 at 1:41 PM Krist Wongsuphasawat <
>> > > > krist.wo...@gmail.com
>> > > > > >
>> > > > > wrote:
>> > > > >
>> > > > > > I would prefer not to host the FAQ in mailing list as its
>> > > > discoverability
>> > > > > > is low and it is not obvious what is the right answer in long
>> email
>> > > > > > thread + what John said.
>> > > > > > Discussion like this thread is ok in email format, but asking
>> how
>> > to
>> > > > > > install something or solve particular problem perhaps is not.
>> > > > > >
>> > > > > > How about setting some deadline so we have a clear plan to move
>> > > > forward.
>> > > > > > If hosting product Q outside of mailing list OK with ASF, in a
>> > week
>> > > > > from
>> > > > > > now we will vote between using
>> > > > > > A. StackOverflow
>> > > > > > B. Discourse
>> > > > > >
>> > > > > > Then after the vote is done, we will ask for volunteers to help
>> > > > migrating
>> > > > > > the questions to target platform and close the issues on github.
>> > > > > >
>> > > > > > For now, people can discuss and advocate for their choice.
>> > > > > >
>> > > > > > -Krist
>> > > > > >
>> > > > > > On Wed, Apr 3, 2019 at 10:11 AM ronald munjoma <
>> simb...@gmail.com>
>> > > > > wrote:
>> > > > > >
>> > > > > > > Hi All,
>> > > > > > >
>> > > > > > > First post here. I have been lurking around for sometime (with
>> > the
>> > > > > > > intention to evaluate Superset someday)
>> > > > > > >
>> > > > > > > Discourse seems to be the Q cool kid these days. Most
>> projects
>> > > > have a
>> > > > > > > self hosted discourse forum.
>> > > > > > >
>> > > > > > > Regards
>> > > > > > > Ronald
>> > > > > > >
>> > > > > > > On Wed, 03 Apr, 2019 at 18:42, John Bodley <
>> > john.bod...@gmail.com>
>> > > > > > wrote:
>> &g

Trademark issues

[Alan Gates]

In your quarterly report you mentioned there were trademark issues you
needed help with.  I'm sorry, but I missed earlier requests for help on
this.  What do you need?

Alan.

Podling report

[Alan Gates]

The quarterly podling report is due ASAP. Anyone have a chance to put one
together?

Alan.

Fwd: Google Summer of Code 2019 is coming

[Alan Gates]

-- Forwarded message -
From: Ulrich Stärk 
Date: Tue, Jan 29, 2019 at 4:24 AM
Subject: Google Summer of Code 2019 is coming
To:


Hello PMCs (incubator Mentors, please forward this email to your podlings),

Google Summer of Code [1] is a program sponsored by Google allowing
students to spend their summer
working on open source software. Students will receive stipends for
developing open source software
full-time for three months. Projects will provide mentoring and
project ideas, and in return have
the chance to get new code developed and - most importantly - to
identify and bring in new committers.

The ASF will apply as a participating organization meaning individual
projects don't have to apply separately.

If you want to participate with your project we ask you to do the
following things by no later than
2019-01-31 19:00 UTC (applications from organizations close a week later)

1. understand what it means to be a mentor [2].

2. record your project ideas.

Just create issues in JIRA, label them with gsoc2019, and they will
show up at [3]. Please be as
specific as possible when describing your idea. Include the
programming language, the tools and
skills required, but try not to scare potential students away. They
are supposed to learn what's
required before the program starts.

Use labels, e.g. for the programming language (java, c, c++, erlang,
python, brainfuck, ...) or
technology area (cloud, xml, web, foo, bar, ...).

Please use the COMDEV JIRA project for recording your ideas if your
project doesn't use JIRA (e.g.
httpd, ooo). Contact d...@community.apache.org if you need assistance.

[4] contains some additional information (will be updated for 2019 shortly).

3. subscribe to ment...@community.apache.org; restricted to potential
mentors, meant to be used as a
private list - general discussions on the public
d...@community.apache.org list as much as possible
please). Use a recognized address when subscribing (@apache.org or one
of your alias addresses on
record).

Note that the ASF isn't accepted as a participating organization yet,
nevertheless you *have to*
start recording your ideas now or we might not get accepted.

Over the years we were able to complete hundreds of projects
successfully. Some of our prior
students are active contributors now! Let's make this year a success again!

P.S.: this email is free to be shared publicly if you want to.

[1] https://summerofcode.withgoogle.com/
[2] http://community.apache.org/guide-to-being-a-mentor.html
[3] https://s.apache.org/gsoc2019ideas
[4] http://community.apache.org/gsoc.html

commit rights for Vyl and Sylvia

[Alan Gates]

I think all this got taken care of over the holidays, so Vyl and Sylvia
should have their full commit rights now.  Let me know if you see any
issues.

Alan.

Re: Helping Vyl and Sylvia with committer rights

[Alan Gates]

I've submitted the requests for both Vyl and Sylvia.  I assume there'll be
a few days delay due to the holidays, but you should have your accounts
soon.

Alan.

On Thu, Dec 27, 2018 at 4:44 AM Sylvia Tomiyama
 wrote:

> Sorry for the delay! I'd like stomiyama please. Thank you!
>
> On Sat, Dec 22, 2018 at 7:24 AM Vyl Chiang 
> wrote:
>
> > I'd like vyl please. Thanks!
> > Vyl Chiang
> > Product
> > 650.279.1185
> >
> > <https://www.lyft.com/>
> >
> >
> > On Fri, Dec 21, 2018 at 8:35 AM Alan Gates  wrote:
> >
> > > One question I forgot to ask.  Vyl and Sylvia, any request for what
> your
> > > Apache id will be?  You can check that your preferred id is not already
> > > taken by using http://people.apache.org/phonebook.html
> > >
> > > Alan.
> > >
> > > On Thu, Dec 20, 2018 at 3:49 PM Sylvia Tomiyama
> > >  wrote:
> > >
> > > > Thanks a ton Alan!
> > > >
> > > > On Thu, Dec 20, 2018 at 3:28 PM Jeff Feng
>  > >
> > > > wrote:
> > > >
> > > > > Thanks so much Alan!  Not that I am aware of, but I encourage folks
> > to
> > > > > speak up if that is you.
> > > > > -Jeff
> > > > >
> > > > > On Thu, Dec 20, 2018 at 3:16 PM Alan Gates 
> > > wrote:
> > > > >
> > > > > > Ok, I've added my vote for Vyl so we'll have the required 3
> +1s.  I
> > > can
> > > > > > take it from here and get both Vyl and Sylvia added.
> > > > > >
> > > > > > Is there anyone else that's been voted in but not given karma?
> > > > > >
> > > > > > Alan.
> > > > > >
> > > > > > On Thu, Dec 20, 2018 at 3:06 PM Jeff Feng
> > >  > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hey Alan,
> > > > > > >
> > > > > > > I did some searching and I was able to forward you the VOTE
> > threads
> > > > for
> > > > > > > Michelle, Sylvia, Vyl and Krist.  We might need to re-initiate
> > the
> > > > vote
> > > > > > for
> > > > > > > Vyl since that thread had 2 +1s and 0 -1s.
> > > > > > >
> > > > > > > I also cross-checked the list of original committers and
> > committers
> > > > > voted
> > > > > > > in that you found together with the Superset Roster (
> > > > > > > https://whimsy.apache.org/roster/ppmc/superset) and there are
> a
> > > few
> > > > > > > additional committers listed on the project there that weren't
> > > > included
> > > > > > in
> > > > > > > your email.  This includes:
> > > > > > >
> > > > > > >- Timi Fasubaa
> > > > > > >- Kevin Williams
> > > > > > >- Hugh Miles
> > > > > > >- Fabian Menges
> > > > > > >
> > > > > > > Let us know about recommended next steps for Sylvia and Vyl,
> > > thanks!
> > > > > > >
> > > > > > > Jeff
> > > > > > >
> > > > > > > On Thu, Dec 20, 2018 at 1:44 PM Alan Gates <
> alanfga...@gmail.com
> > >
> > > > > wrote:
> > > > > > >
> > > > > > > > At our meeting last week Vyl and Sylvia both mentioned that
> > they
> > > > had
> > > > > > > > submitted their ICLAs but hadn't received their committer
> karma
> > > > yet.
> > > > > > So
> > > > > > > > (with a little extra poking from Vyl :) ) I went looking
> today
> > > but
> > > > I
> > > > > > > can't
> > > > > > > > find the email trail for the votes, which I need in order to
> > give
> > > > > them
> > > > > > > > karma.  I'm not sure if I'm failing in my search skills
> > (entirely
> > > > > > > possible)
> > > > > > > > or if there wasn't a vote.
> > > > > > > >
> > > > > > > > From the original proposal for Superset I see the following
> > > initial
> > > > > > > > committers:
> > > &

Some feedback from the Apache board on the last incubator report

[Alan Gates]

Each month the incubator reports to the board, and a few bits of feedback
from the board on the incubator report this month concerned superset.  I
thought I'd share with you:

Thanks to Daffodil, Skywalking, and Superset forthoughtfully written reports

Please let superset know that their lists can be configured to allow image
attachments if they wish.

Alan.

Re: Helping Vyl and Sylvia with committer rights

[Alan Gates]

One question I forgot to ask.  Vyl and Sylvia, any request for what your
Apache id will be?  You can check that your preferred id is not already
taken by using http://people.apache.org/phonebook.html

Alan.

On Thu, Dec 20, 2018 at 3:49 PM Sylvia Tomiyama
 wrote:

> Thanks a ton Alan!
>
> On Thu, Dec 20, 2018 at 3:28 PM Jeff Feng 
> wrote:
>
> > Thanks so much Alan!  Not that I am aware of, but I encourage folks to
> > speak up if that is you.
> > -Jeff
> >
> > On Thu, Dec 20, 2018 at 3:16 PM Alan Gates  wrote:
> >
> > > Ok, I've added my vote for Vyl so we'll have the required 3 +1s.  I can
> > > take it from here and get both Vyl and Sylvia added.
> > >
> > > Is there anyone else that's been voted in but not given karma?
> > >
> > > Alan.
> > >
> > > On Thu, Dec 20, 2018 at 3:06 PM Jeff Feng  >
> > > wrote:
> > >
> > > > Hey Alan,
> > > >
> > > > I did some searching and I was able to forward you the VOTE threads
> for
> > > > Michelle, Sylvia, Vyl and Krist.  We might need to re-initiate the
> vote
> > > for
> > > > Vyl since that thread had 2 +1s and 0 -1s.
> > > >
> > > > I also cross-checked the list of original committers and committers
> > voted
> > > > in that you found together with the Superset Roster (
> > > > https://whimsy.apache.org/roster/ppmc/superset) and there are a few
> > > > additional committers listed on the project there that weren't
> included
> > > in
> > > > your email.  This includes:
> > > >
> > > >- Timi Fasubaa
> > > >- Kevin Williams
> > > >- Hugh Miles
> > > >- Fabian Menges
> > > >
> > > > Let us know about recommended next steps for Sylvia and Vyl, thanks!
> > > >
> > > > Jeff
> > > >
> > > > On Thu, Dec 20, 2018 at 1:44 PM Alan Gates 
> > wrote:
> > > >
> > > > > At our meeting last week Vyl and Sylvia both mentioned that they
> had
> > > > > submitted their ICLAs but hadn't received their committer karma
> yet.
> > > So
> > > > > (with a little extra poking from Vyl :) ) I went looking today but
> I
> > > > can't
> > > > > find the email trail for the votes, which I need in order to give
> > them
> > > > > karma.  I'm not sure if I'm failing in my search skills (entirely
> > > > possible)
> > > > > or if there wasn't a vote.
> > > > >
> > > > > From the original proposal for Superset I see the following initial
> > > > > committers:
> > > > > Maxime Beauchemin
> > > > > Alanna Scott
> > > > > Bogdan Kyryliuk
> > > > > Vera Liu
> > > > > Jeff Feng
> > > > > Ashutosh Chauhan
> > > > > Nishant Bangarwa
> > > > > Slim Bouguerra
> > > > > Priyank Shah
> > > > > Harsha Chintalapani
> > > > > Daniel Dai
> > > > > Luke Han
> > > > >
> > > > > On https://lists.apache.org/list.html?priv...@superset.apache.org
> I
> > > can
> > > > > find votes for:
> > > > > Beto Dealmaida
> > > > > Ricardo Massa
> > > > > Grace Guo
> > > > > Chris Williams
> > > > > John Bodley
> > > > >
> > > > > I also find votes that opened for Krist Wongsuphasawat and Michelle
> > > > Thomas
> > > > > though I don't find any resolutions for either of those.
> > > > >
> > > > > So, if there was a vote and I missed it, please send me the link
> and
> > > I'll
> > > > > get these two their karma.  If there wasn't, since everyone seemed
> to
> > > > > already think they were committers I suggest you start a vote soon
> > and
> > > > then
> > > > > we can go from there.
> > > > >
> > > > > Alan.
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > *Jeff Feng*
> > > > Product Lead
> > > > m: (949)-610-5108
> > > > twitter: @jtfeng
> > > >
> > >
> >
> >
> > --
> >
> > *Jeff Feng*
> > Product Lead
> > m: (949)-610-5108
> > twitter: @jtfeng
> >
>

Re: Helping Vyl and Sylvia with committer rights

[Alan Gates]

Ok, I've added my vote for Vyl so we'll have the required 3 +1s.  I can
take it from here and get both Vyl and Sylvia added.

Is there anyone else that's been voted in but not given karma?

Alan.

On Thu, Dec 20, 2018 at 3:06 PM Jeff Feng 
wrote:

> Hey Alan,
>
> I did some searching and I was able to forward you the VOTE threads for
> Michelle, Sylvia, Vyl and Krist.  We might need to re-initiate the vote for
> Vyl since that thread had 2 +1s and 0 -1s.
>
> I also cross-checked the list of original committers and committers voted
> in that you found together with the Superset Roster (
> https://whimsy.apache.org/roster/ppmc/superset) and there are a few
> additional committers listed on the project there that weren't included in
> your email.  This includes:
>
>- Timi Fasubaa
>- Kevin Williams
>- Hugh Miles
>- Fabian Menges
>
> Let us know about recommended next steps for Sylvia and Vyl, thanks!
>
> Jeff
>
> On Thu, Dec 20, 2018 at 1:44 PM Alan Gates  wrote:
>
> > At our meeting last week Vyl and Sylvia both mentioned that they had
> > submitted their ICLAs but hadn't received their committer karma yet.  So
> > (with a little extra poking from Vyl :) ) I went looking today but I
> can't
> > find the email trail for the votes, which I need in order to give them
> > karma.  I'm not sure if I'm failing in my search skills (entirely
> possible)
> > or if there wasn't a vote.
> >
> > From the original proposal for Superset I see the following initial
> > committers:
> > Maxime Beauchemin
> > Alanna Scott
> > Bogdan Kyryliuk
> > Vera Liu
> > Jeff Feng
> > Ashutosh Chauhan
> > Nishant Bangarwa
> > Slim Bouguerra
> > Priyank Shah
> > Harsha Chintalapani
> > Daniel Dai
> > Luke Han
> >
> > On https://lists.apache.org/list.html?priv...@superset.apache.org I can
> > find votes for:
> > Beto Dealmaida
> > Ricardo Massa
> > Grace Guo
> > Chris Williams
> > John Bodley
> >
> > I also find votes that opened for Krist Wongsuphasawat and Michelle
> Thomas
> > though I don't find any resolutions for either of those.
> >
> > So, if there was a vote and I missed it, please send me the link and I'll
> > get these two their karma.  If there wasn't, since everyone seemed to
> > already think they were committers I suggest you start a vote soon and
> then
> > we can go from there.
> >
> > Alan.
> >
>
>
> --
>
> *Jeff Feng*
> Product Lead
> m: (949)-610-5108
> twitter: @jtfeng
>

Helping Vyl and Sylvia with committer rights

[Alan Gates]

At our meeting last week Vyl and Sylvia both mentioned that they had
submitted their ICLAs but hadn't received their committer karma yet.  So
(with a little extra poking from Vyl :) ) I went looking today but I can't
find the email trail for the votes, which I need in order to give them
karma.  I'm not sure if I'm failing in my search skills (entirely possible)
or if there wasn't a vote.

>From the original proposal for Superset I see the following initial
committers:
Maxime Beauchemin
Alanna Scott
Bogdan Kyryliuk
Vera Liu
Jeff Feng
Ashutosh Chauhan
Nishant Bangarwa
Slim Bouguerra
Priyank Shah
Harsha Chintalapani
Daniel Dai
Luke Han

On https://lists.apache.org/list.html?priv...@superset.apache.org I can
find votes for:
Beto Dealmaida
Ricardo Massa
Grace Guo
Chris Williams
John Bodley

I also find votes that opened for Krist Wongsuphasawat and Michelle Thomas
though I don't find any resolutions for either of those.

So, if there was a vote and I missed it, please send me the link and I'll
get these two their karma.  If there wasn't, since everyone seemed to
already think they were committers I suggest you start a vote soon and then
we can go from there.

Alan.

Re: Introduction and offer to help with mentoring

[Alan Gates]

>From a look at whimsy it looks like I've already been added.

And thank you Dave, hopefully I can be helpful.

Alan.

On Sun, Dec 2, 2018 at 10:38 PM Dave Fisher  wrote:

> Alan can add himself via whimsy.
>
> He has mentored many projects. He is certain to be helpful.
>
> Regards,
> Dave
>
> On 2018/12/01 21:46:11, Jeff Feng  wrote:
> > +gene...@incubator.apache.org 
> >
> > Could anyone help direct us as to how we can add Alan Gates as a mentor
> on
> > our Superset Roster page?
> >
> > https://whimsy.apache.org/roster/ppmc/superset
> >
> > Thanks,
> > Jeff
> >
> > On Fri, Oct 5, 2018 at 6:27 AM Maxime Beauchemin <
> maximebeauche...@gmail.com>
> > wrote:
> >
> > > Very glad to have you on board Alan!
> > >
> > > Let's revive the thread titled "Our first Apache release". I'd love
> more
> > > mentor input on the topic.
> > >
> > > Max
> > >
> > > On Thu, Oct 4, 2018 at 10:47 PM Stephanie Rivera
>  > > >
> > > wrote:
> > >
> > > > Welcome Alan!!! Thanks for joining us
> > > >
> > > > Cheers,
> > > >
> > > > Stephanie
> > > >
> > > >
> > > > *Stephanie Rivera* |* Sr. Director of Data Intelligence*
> > > >
> > > > 8181 Arista Place | Suite 300 | Broomfield, CO 80021 | Westminster,
> CO
> > > > 80020
> > > > <
> > > >
> > >
> http://www.google.com/url?q=http%3A%2F%2Fwww.spotxchange.com%2F=D=1=AFrqEzdlZjMtAvYRCQByfN6D_6PjZhSbSw
> > > > >
> > > >
> > > > <
> > > >
> > >
> https://www.google.com/url?q=https%3A%2F%2Fdl.dropbox.com%2Fs%2F5se5ucpqodjsq1h%2Flinkedin.png=D=1=AFrqEzdTHQrlDWywpW7VZVpwGJJdOBY-Wg
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Thu, Oct 4, 2018 at 7:58 PM Luke Han  wrote:
> > > >
> > > > > That's great and happy to see new mentor join this community.
> > > > >
> > > > > Best Regards!
> > > > > -
> > > > >
> > > > > Luke Han
> > > > >
> > > > >
> > > > > On Wed, Oct 3, 2018 at 5:52 AM Alan Gates 
> > > wrote:
> > > > >
> > > > > > All, with Jim stepping down as mentor it looks like your
> community
> > > > needs
> > > > > > some additional mentors.  I'm happy to help if you would like.
> > > > > >
> > > > > > Some background on me.  I've been involved with various Apache
> big
> > > data
> > > > > > projects since 2007.  I got started with Pig (when it was in the
> > > > > > incubator), am currently active in the Hive community, and have
> > > helped
> > > > > > mentor many projects, including Flink, Ranger, and Bigtop.
> > > > > >
> > > > > > Alan.
> > > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> >
> > *Jeff Feng*
> > Product Lead
> > m: (949)-610-5108
> > twitter: @jtfeng
> >
>

Re: Question on the CODE_OF_CONDUCT.md file

[Alan Gates]

I don't know what the policy is on this.  Apache has an official code of
conduct at https://www.apache.org/foundation/policies/conduct.html. There
appears to be some shared lineage between the two as some of the text is
identical, though there are a number of differences.

My concern is that "community organizers" is undefined in the Apache
context, and thus if a violation does occur who should handle is undefined.


If the Superset community wants to point at the Apache code as their code,
that would clearly be fine.  If they want to continue with their own code I
think we should seek guidance from the incubator PMC on how best to do
that.  I'm happy to help start that discussion in the incubator PMC if
that's what the community wants.

Alan.

On Wed, Nov 14, 2018 at 12:21 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> It was created using Github's template. Here's the original PR:
> https://github.com/apache/incubator-superset/pull/3991
>
> Is there an ASF-approved template we can use?
>
> Max
>
> On Wed, Nov 14, 2018 at 11:57 AM Alan Gates  wrote:
>
> > Reading through this it read as if it came from pre-Apache days (since it
> > mentions community organizers as the enforcers of the code).  Is that
> > accurate?
> >
> > Alan.
> >
>

Question on the CODE_OF_CONDUCT.md file

[Alan Gates]

Reading through this it read as if it came from pre-Apache days (since it
mentions community organizers as the enforcers of the code).  Is that
accurate?

Alan.

Re: Helping Superset grow into an Apache community

[Alan Gates]

Picking this thread back up.

On the code in the vendors folder, do we know where that came from?  If it
was not contributed to Superset we need to 1) check that it's ok to have it
at all (ie, we have the author's blessing); 2) figure out what license the
author released it under; 3) put the license and copyright information in
the LICENSE and NOTICE files.

Same questions apply for code in the visualizations folder.  With just a
quick look through there I didn't see any licenses, notices, copyright
statements, etc.

A few other things I noticed:

You need a NOTICE file at the top of the source directory, see
https://incubator.apache.org/guides/releasemanagement.html and
http://www.apache.org/legal/release-policy.html

You need a DISCLAIMER file, see
https://incubator.apache.org/guides/branding.html

None of the source files appear to have Apache headers on them.  I didn't
find a header in any of the css, html, py, js, sh, or yaml files.  I'm not
saying these are the only file types that should have them, they're just
the ones I checked.  Any non-binary file that can take comments should have
the header.  (By header I mean the "Licensed to the Apache Software
Foundation..." bit, which you can find in any Apache project's code.

Other than the image files, I didn't see any binary or executable files,
which is good.

There might be other issues, but this will be a good start.

Alan.

On Fri, Oct 26, 2018 at 12:49 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Super. This clarifies things for me. If it's a source only release, then we
> have MUCH LESS concerns. Some things to check are:
> * This vendors folder
> <
> https://github.com/apache/incubator-superset/tree/master/superset/assets/vendor
> >,
> files in here are copied & modified
> * parallel-coordinates:
> https://github.com/syntagmatic/parallel-coordinates/blob/master/LICENSE
> (what license is this?)
> * cal-heatmap:
> https://github.com/wa0x6e/cal-heatmap/blob/master/LICENCE-MIT (MIT)
> * pygment.css: https://github.com/nex3/pygments/blob/master/LICENSE
> (BSD2 <https://github.com/nex3/pygments/blob/master/LICENSE(BSD2>)
> * the visualization folder
> <
> https://github.com/apache/incubator-superset/tree/master/superset/assets/src/visualizations
> >
> has some copied/modified code as well, mostly coming from bl.ocks.org . I
> believe there should be headers in all cases as to where it came from. We
> probably need to dig in here. Good news is that there's ongoing work to
> ship all visualizations as plugins, so that we can keep this out of the
> source releases.
>
> Max
>
> On Fri, Oct 26, 2018 at 11:22 AM Alan Gates  wrote:
>
> > Responses inlined.
> >
> > On Fri, Oct 26, 2018 at 8:57 AM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> > > One of the main challenge/blocker to date has been around crafting our
> > > LICENSE.txt file, and keeping it up to date as our JS dependency tree
> is
> > > massive, deep and very dynamic. It seemed like we have to do this
> > > programmatically. I started writing a script to do so a little while
> back
> > > and was looking for more mentor guidance as to how to handle the
> special
> > > cases. There are many libs under "MIT*" or "BSD*" where the "*" needs
> to
> > be
> > > investigated and personally I'm not qualified to know whether "MIT with
> > > LLVM clause" is ok or not... So while I can commit time to this, I can
> > only
> > > raise questions in the process. Also there have been questions around
> > > convenience releases and whether it's ok to have grey-zone license if
> > > they're fetched at build time. We need mentor and legal guidance here.
> > > https://github.com/apache/incubator-superset/pull/5801
> >
> >
> > Sorry if this is repetitive as I'm new here, but step 1 should be doing a
> > source release.  Apache doesn't do binary releases, it does convenience
> > binaries.  If the convenience binary isn't 100% Apache approved yet,
> we'll
> > solve that in a step 2.
> >
> > For the source release I'm guessing that all the JS stuff doesn't get
> > pulled in, is that right?  If so, then we can proceed to the first phase
> > and get an Apache release out.  And we can post those convenience
> binaries
> > in their current messy state.  Then we'll start working on getting the
> > licensing and packaging right for those.
> >
> >
> > >
> > > I also have filled in the "The Apache Project Maturity Checklist" last
> > > month in the GH issue bellow, and it seems like we're doing fairly
> well:
> > > htt

Re: Helping Superset grow into an Apache community

[Alan Gates]

Responses inlined.

On Fri, Oct 26, 2018 at 8:57 AM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> One of the main challenge/blocker to date has been around crafting our
> LICENSE.txt file, and keeping it up to date as our JS dependency tree is
> massive, deep and very dynamic. It seemed like we have to do this
> programmatically. I started writing a script to do so a little while back
> and was looking for more mentor guidance as to how to handle the special
> cases. There are many libs under "MIT*" or "BSD*" where the "*" needs to be
> investigated and personally I'm not qualified to know whether "MIT with
> LLVM clause" is ok or not... So while I can commit time to this, I can only
> raise questions in the process. Also there have been questions around
> convenience releases and whether it's ok to have grey-zone license if
> they're fetched at build time. We need mentor and legal guidance here.
> https://github.com/apache/incubator-superset/pull/5801


Sorry if this is repetitive as I'm new here, but step 1 should be doing a
source release.  Apache doesn't do binary releases, it does convenience
binaries.  If the convenience binary isn't 100% Apache approved yet, we'll
solve that in a step 2.

For the source release I'm guessing that all the JS stuff doesn't get
pulled in, is that right?  If so, then we can proceed to the first phase
and get an Apache release out.  And we can post those convenience binaries
in their current messy state.  Then we'll start working on getting the
licensing and packaging right for those.


>
> I also have filled in the "The Apache Project Maturity Checklist" last
> month in the GH issue bellow, and it seems like we're doing fairly well:
> https://github.com/apache/incubator-superset/issues/5951
>
> I believe that the issues around having discussions off-lists can be
> addressed easily, but we need to clarify what's acceptable or not. Is Slack
> ok? Are in-person operational community meetings ok if everyone is welcomed
> to attend, minutes are posted and no important decisions are taken?
>

The key in Apache is "if it didn't happen on the lists, it didn't happen".
Anything that copies to the lists (JIRA, GitHub, etc.) counts.  Obviously
people are going to have f2f, slack, etc. discussions.  The key is to
always report the content of those discussions and allow those on the list
to be part of the discussion and decision making process.  The issue with
any realtime tool like slack is that no matter what time of day you pick,
it's 3am somewhere, which makes it hard to build a geographically
distributed community.

Let me give an example of how we handle this in the Hive community.  Since
many Hive developers work for either Cloudera or Hortonworks, obviously a
lot off list discussion happens.  But _no_ changes are made without a
JIRA.  And a JIRA patch must be up for 24 hours before anyone can commit
it.  This way everyone has a chance to take a look at it before it's
committed, even if the initial idea for the change is based on some hallway
conversation somewhere.  Superset will probably prefer git to JIRA, but the
same principles apply if you let any PR stay open for 24 hours before
merging it.


>
> Personally I'm committed to align with "the Apache Way" and do a
> significant portion of the work that we have to do in order to graduate,
> but I would love support and help from committers and mentors to make it
> happen.
>

Glad to hear you're committed.  We mentors are here to help.  If we have a
first pass of what a source release looks like I can take a look and give
some feedback.

Alan.

Helping Superset grow into an Apache community

[Alan Gates]

All, there are concerns in the Incubator that Superset is not learning the
Apache Way as it should.
It is still doing non-Apache releases.  Some have pointed out evidence that
decisions may be being taken off list and corporate allegiance may be
determining peoples choices.  If Superset is going to move through the
Incubator and eventually graduate it needs to begin addressing these issues
immediately, as the Incubator PMC is loosing patience.  Alternatively,
maybe Apache isn't the best home for Superset, and if so, that's ok.

The purpose of this email is to start a discussion around what the
community needs to do to address these issues.

Alan.

Introduction and offer to help with mentoring

[Alan Gates]

All, with Jim stepping down as mentor it looks like your community needs
some additional mentors.  I'm happy to help if you would like.

Some background on me.  I've been involved with various Apache big data
projects since 2007.  I got started with Pig (when it was in the
incubator), am currently active in the Hive community, and have helped
mentor many projects, including Flink, Ranger, and Bigtop.

Alan.