[ANNOUNCE] Apache Superset (Incubating) version 0.37.0 Released

2020-08-13 Thread Ville Brofeldt 
Hello Community,

The Apache Superset (incubating) team is pleased to announce that Superset
0.37.0 has just been released.

Apache Superset (incubating) is a modern, enterprise-ready business 
intelligence web application

The official source release:

https://www.apache.org/dist/incubator/superset/0.37.0

The Pypi package:

https://pypi.org/project/apache-superset/

If you have any usage questions, or have problems when upgrading or
find any problems about enhancements included in this release, please
don't hesitate to let us know by sending feedback to this mailing
list.

=
*Disclaimer*

Apache Superset is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Incubator. Incubation is required of all
newly accepted projects until a further review indicates that the
infrastructure, communications, and decision making process have stabilized
in a manner consistent with other successful ASF projects. While incubation
status is not necessarily a reflection of the completeness or stability of
the code, it does indicate that the project has yet to be fully endorsed by
the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
--

smime.p7s
Description: S/MIME cryptographic signature

Re: Graduation

2020-08-13 Thread Maxime Beauchemin 
I made a call and updated the file here
https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/superset.xml
through
"svn commit" to simply point to the GitHub wiki, but I don't see the
changes here https://incubator.apache.org/projects/superset.html .

This stuff is really really really painful.

Max

On Tue, Aug 11, 2020 at 10:36 AM Maxime Beauchemin  wrote:

> Resurfacing the question I asked earlier in this thread: can we use GitHub
> wiki to publish our incubation status as opposed to the xml/svn option?
> Maybe we can just link out to the wiki page from that original status file?
>
> On Tue, Aug 11, 2020 at 4:42 AM Jim Jagielski  wrote:
>
> > All looks good!
> >
> > > On Aug 7, 2020, at 1:08 PM, Junlin Chen  wrote:
> > >
> > > Community and @mentors,
> > >
> > > We've been working on graduation, and going through our status file and
> > > checklist
> > > <
> >
> https://docs.google.com/document/d/1Epi_3O9jSY2cbc3Uwcp4NTPjG38dazDTEw1tDvt7xT4/edit#
> > >.
> > > Please chime in and help complete it if you have the information.
> > > Superset website and WIKI are being updated, following the Podling
> > Website
> > > Requirements.
> > >
> > > Mentors, there are mentor related items that need to be confirmed,
> please
> > > help check below.
> > >
> > >   - You have subscribed to the pmc and general lists.
> > >   - You have access to the incubator repository
> > >   - You have been tracking project progress.
> > >
> > > We also noticed that some of the links on the graduation page
> > >  are broken and
> > would
> > > like to bring it to your attention.
> > >
> > > Thanks for your support!
> > >
> > > Best,
> > > Junlin
> > >
> > > On Thu, Jul 30, 2020 at 4:21 PM Maxime Beauchemin 
> wrote:
> > >
> > >> Community and @mentors!
> > >>
> > >> Junlin and I were talking about pushing the graduation process
> forward,
> > >> and even though I've done it once before, we could really use some
> help
> > >> around navigating the process.
> > >>
> > >> The first step is to look at the checklist and identify the gaps, and
> I
> > >> think there are very few at this time.
> > >>
> > >> Can one of our mentors volunteer to provide guidance?
> > >>
> > >> Volunteers are welcomed as always, we'll also communicate as we break
> > down
> > >> the checklist into tasks.
> > >>
> > >> Thanks,
> > >>
> > >> Max
> > >>
> >
> >
>

Re: Giving our PMs and contributors triage rights on GitHub

2020-08-13 Thread Evan Rusackas 
An emphatic +1 from me! The issues could gain a huge boost from the added human 
curation, whether it's adding sensible labels, running Project kanban boards, 
linking issues to PRs (and other relevant issues), and more. It could not only 
bring some order to the chaos, but help those in the community reporting issues 
feel like they’re being heard.

Evan Rusackas
( he | him )
Frontend Lead
Preset | preset.io
On Aug 13, 2020, 9:28 AM -0700, Maxime Beauchemin , 
wrote:
> Hi all,
>
> It just came to my attention that GitHub added a new "triage" access level
> at the repo level.
> https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
>
> In the past, we've identified that it was impossible for non-committers
> (especially our PMs and contributors-that-are-not-yet-committers) to help
> us triage issues, apply labels, assign reviews, close and reopen issues as
> needed. It's really clear to me that we really need all the help we can get
> in this area, and that not being able to involve more people into this
> process hurts us, and is a clear operational downside of using the ASF
> infra.
>
> I'd like to build a case for this to become allowed by ASF infra. But
> first, I'd love to see some +1s, and a list of GitHub handles for people in
> our community who could make use of this feature.
>
> More technically, I think the way to make that easy and painless would be
> to add a new entry to the `.asf.yaml` file that would enable maintainers to
> assign the "triage" role to whoever they see fit. For reference, here's
> more context on that piece of automation I'd like to latch this onto here:
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
>
> FYI, xposting this to general@incubator for their attention.
>
> Max

Re: Giving our PMs and contributors triage rights on GitHub

2020-08-13 Thread William Barrett 
+1 - the PMs at Preset would be very helpful to the community if they had this 
level of access.

Will Barrett
Staff Software Engineer
Preset, Inc. | https://preset.io
On Aug 13, 2020, 9:28 AM -0700, Maxime Beauchemin , 
wrote:
> Hi all,
>
> It just came to my attention that GitHub added a new "triage" access level
> at the repo level.
> https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/
>
> In the past, we've identified that it was impossible for non-committers
> (especially our PMs and contributors-that-are-not-yet-committers) to help
> us triage issues, apply labels, assign reviews, close and reopen issues as
> needed. It's really clear to me that we really need all the help we can get
> in this area, and that not being able to involve more people into this
> process hurts us, and is a clear operational downside of using the ASF
> infra.
>
> I'd like to build a case for this to become allowed by ASF infra. But
> first, I'd love to see some +1s, and a list of GitHub handles for people in
> our community who could make use of this feature.
>
> More technically, I think the way to make that easy and painless would be
> to add a new entry to the `.asf.yaml` file that would enable maintainers to
> assign the "triage" role to whoever they see fit. For reference, here's
> more context on that piece of automation I'd like to latch this onto here:
> https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features
>
> FYI, xposting this to general@incubator for their attention.
>
> Max

Giving our PMs and contributors triage rights on GitHub

2020-08-13 Thread Maxime Beauchemin 
Hi all,

It just came to my attention that GitHub added a new "triage" access level
at the repo level.
https://github.blog/changelog/2019-05-23-triage-and-maintain-roles-beta/

In the past, we've identified that it was impossible for non-committers
(especially our PMs and contributors-that-are-not-yet-committers) to help
us triage issues, apply labels, assign reviews, close and reopen issues as
needed. It's really clear to me that we really need all the help we can get
in this area, and that not being able to involve more people into this
process hurts us, and is a clear operational downside of using the ASF
infra.

I'd like to build a case for this to become allowed by ASF infra. But
first, I'd love to see some +1s, and a list of GitHub handles for people in
our community who could make use of this feature.

More technically, I think the way to make that easy and painless would be
to add a new entry to the `.asf.yaml` file that would enable maintainers to
assign the "triage" role to whoever they see fit. For reference, here's
more context on that piece of automation I'd like to latch this onto here:
https://cwiki.apache.org/confluence/display/INFRA/git+-+.asf.yaml+features

FYI, xposting this to general@incubator for their attention.

Max