Re: [VOTE] Release Apache Superset (incubating) version 0.38.0

[Maxime Beauchemin]

Hi,

I thought we were ok around SIL. This was validated in previous releases as
[from my understanding] we meet the conditions listed in
https://www.apache.org/legal/resolved.html#weak-copyleft-licenses

> You should find another way to make use of these fonts.
Would loading the fonts from `npm` at build time help instead of packaging
the binaries in the source release?

Max



On Mon, Nov 16, 2020 at 10:55 AM Dave Fisher  wrote:

> -1 (binding)
>
> You are including Class B in your source release with these fonts.
>
> https://www.apache.org/legal/resolved.html#weak-copyleft-licenses
>
> 
> Third party SIL Open Font License v1.1 (OFL-1.1)
> 
>
> (SIL OPEN FONT LICENSE Version 1.1) The Inter font family (
> https://github.com/rsms/inter)
> (SIL OPEN FONT LICENSE Version 1.1) The Fira Code font family (
> https://github.com/tonsky/FiraCode)
>
> You should find another way to make use of these fonts.
>
> Regards,
> Dave
>
> > On Nov 16, 2020, at 8:44 AM, Daniel Gaspar  wrote:
> >
> > Kind reminder to the IPMC to vote on this release
> >
> > Thank you!
> >
> >
> > On 2020/11/09 19:11:35, daniel gaspar 
> wrote:
> >> Hello IPMC,
> >>
> >> The Apache Superset (incubating) community has voted on and approved a
> >> proposal to
> >> release Apache Superset (incubating) version 0.38.0.
> >> The voting thread can be found here:
> >>
> https://lists.apache.org/thread.html/rcec99715a8d9ede91b36f58a29b1bb5602eecab5a3e4dd012b44d975%40%3Cdev.superset.apache.org%3E
> >>
> >>
> >> Here are the binding +1 votes from mentors, carrying over from the
> podling
> >> vote:
> >> - Felix Cheung
> >>
> >> We now kindly request the Incubator PMC members review and vote on this
> >> incubator release.
> >>
> >> Apache Superset (incubating) is a modern, enterprise-ready business
> >> intelligence web application
> >>
> >> The release candidate:
> >> https://dist.apache.org/repos/dist/dev/incubator/superset/0.38.0rc3/
> >>
> >> Git tag for the release:
> >> https://github.com/apache/incubator-superset/tree/0.38.0rc3
> >>
> >> The Change Log for the release:
> >>
> https://github.com/apache/incubator-superset/blob/0.38.0rc3/CHANGELOG.md
> >>
> >> public keys are available at:
> >>
> >> https://www.apache.org/dist/incubator/superset/KEYS
> >>
> >> The vote will be open for at least 72 hours or until the necessary
> number
> >> of votes are reached.
> >>
> >> Please vote accordingly:
> >>
> >> [ ] +1 approve
> >> [ ] +0 no opinion
> >> [ ] -1 disapprove with the reason
> >>
> >> Thanks,
> >> The Apache Superset (Incubating) Team
> >>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Graduate Apache Superset (incubating) as a Top Level Project

[Maxime Beauchemin]

Awesome! Congrats to everyone involved!

I think there's an ASF board meeting tomorrow, can we get the board
resolution passed then!? Is there anything missing for the resolution to be
passed?

Max

On Tue, Oct 20, 2020 at 10:21 AM Felix Cheung 
wrote:

> +1
>
> ;)
>
> On Tue, Oct 20, 2020 at 2:31 AM Justin Mclean 
> wrote:
>
> > HI,
> >
> > +1 (binding)
> >
> > Thanks for addressing everything I brought up here and on your private
> > list. There's still a little more to do, but it’s being dealt with, so
> I’m
> > all good with you graduating. Do keep an eye on how you are handling
> those
> > synchronous meetings and try to make sure everyone can contribute and
> > information is brought back to the list.
> >
> > Congratulations!
> >
> > Thanks,
> > Justin
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

FWD: [VOTE] graduate Apache Superset from the Apache Incubator

[Maxime Beauchemin]

FYI - we just started a VOTE to graduate Apache Superset from the Apache
Incubator (!!!)

-- Forwarded message -
From: Maxime Beauchemin 
Date: Tue, Sep 15, 2020 at 5:46 PM
Subject: [VOTE] graduate Apache Superset from the Apache Incubator
To: 


Hi all!

Over the past few months/years, the Apache Superset community has met all
the requirements to graduate from the Apache Incubator. Given that, I
believe we are ready for graduation and I'm excited to kick off the process
with a community vote at this time.

For the record, we have been incubating since 2017-05-02, have had 8
official Apache-approved releases, and have voted in 20 PMC members and 11
committers. See our Incubation Status File for more details:
https://incubator.apache.org/projects/superset.html

For reference, you can find out everything you need to know about the
graduation requirements and process here:
https://incubator.apache.org/guides/graduation.html

Consider this an implicit +1 from me.

Cheers!

Max

Re: [VOTE] Release Apache Superset (incubating) version 0.37.1

[Maxime Beauchemin]

+1 (non-binding at the IPCM level)

and a *gentle ping* as I believe we need an extra vote from an IPMC for us
to publish the release (!)

On Wed, Sep 9, 2020 at 1:02 PM Felix Cheung  wrote:

> +1
>
> - incubating in name
> - signature and hash fine
> - DISCLAIMER is fine
> - LICENSE and NOTICE are fine
> - No unexpected binary files
> - All source files have ASF headers
>
>
> On Wed, Sep 9, 2020 at 8:37 AM Ville Brofeldt 
> wrote:
>
> > Hello IPMC,
> >
> > The Apache Superset (incubating) community has voted on and approved a
> > proposal to
> > release Apache Superset (incubating) version 0.37.1.
> > The voting thread can be found here:
> >
> https://lists.apache.org/thread.html/r4462440505c3eea8fbfdbad76575d29a6ce23e7fb575d45a66a1e946%40%3Cdev.superset.apache.org%3E
> > <
> https://lists.apache.org/thread.html/r4462440505c3eea8fbfdbad76575d29a6ce23e7fb575d45a66a1e946@%3Cdev.superset.apache.org%3E
> >
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Apache Superset (incubating) is a modern, enterprise-ready business
> > intelligence web application
> >
> > The release candidate:
> > https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.1rc1/
> >
> > Git tag for the release:
> > https://github.com/apache/incubator-superset/tree/0.37.1rc1
> >
> > The Change Log for the release:
> > https://github.com/apache/incubator-superset/blob/0.37.1rc1/CHANGELOG.md
> >
> > public keys are available at:
> > https://www.apache.org/dist/incubator/superset/KEYS
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes are reached.
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Thanks,
> > The Apache Superset (Incubating) Team
> >
>

Re: Giving our PMs and contributors triage rights on GitHub

[Maxime Beauchemin]

I can think of 3 main reasons backing the approach that I'm suggesting:

- as someone who's kicked off votes for dozens of committers across 3
communities, I know how slow and cumbersome the process of voting
committers in is. Effectively, it always takes more than 2 weeks (when
things go well) and involves many async touchpoints with many people.
- the chicken and egg issue discussed in this thread: for this type of role
triage is the probably the absolute best onramp
- personally I don't like the idea of diluting committerhood, it should be
earned through merit, not given so that people have a path to onramp

About diversity, we have to be creative and challenge the status quo
to make significant progress on this. Clearly offering a new onramp for
roles that historically haven't been well recognized in ASF projects is a
great way to improve diversity of roles, and consequently of thoughts and
backgrounds.

Max

On Thu, Aug 20, 2020 at 3:08 AM Justin Mclean 
wrote:

> Hi,
>
> > Last thought: I don't have data on this, but I think the ASF could be
> doing
> > better at diversity (see the ApacheCon picture <
> https://www.apachecon.com/>
> > as anecdotal evidence). Being inclusive of a wider range of roles and
> > offering diverse paths to "committerhood" could really help with this.
> For
> > Superset and many other projects, finding ways to involve and empower PMs
> > and designers to partake in the open source process is vital.
>
> We could always be doing a better job at diversity, but I’m not sure
> that’s the issue here.
>
> The bar to committership should be low and all forms of contribution
> considered by the (P)PMC. Many people end up being voted into communities
> without making code contributions, and this has happened to me on more than
> one occasion.
>
> Someone who is being paid to work on a project should have no issues is
> achieving this in a very short time. So I’m not sure what the issue is
> here. Is it in engaging people who have been assigned these roles to be
> publicly involved with the project and follow Apache values or is it
> something else?
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Challenges using Gitbox

[Maxime Beauchemin]

How can I propose this as a change? What's the proper forum / mailing list?

On Tue, Apr 17, 2018, 9:49 AM Ted Dunning  wrote:

> On Mon, Apr 16, 2018 at 8:28 PM, Ralph Goers 
> wrote:
>
> > ...
> > >> such people can earn merit by becoming involved with the community and
> > > helping out where they can.
> > >
> > > In theory, that sounds good, but as a practical matter, how many people
> > > that have ever been on the ASF board of directors neither know/knew,
> nor
> > > use(d) any programming languages in getting there? IOW, they got there
> > > exclusively on their ability to write documentation, do community
> > > relations, or utilize other non-coding skills?
> >
> > It has happened many times. When I was a committer on Apache Cocoon we
> > voted Arje Cahn as a committer for his contributions to the project which
> > had nothing to do with coding. He was voted in as an ASF member for
> pretty
> > much the same reason.
> >
>
>
> It has happened. I was voted as a committer for simply answering questions
> (and it stuck). I know of at least one or two others.
>
> But we should be honest here. It isn't all that common. It should be much
> more common.
>

Re: Giving our PMs and contributors triage rights on GitHub

[Maxime Beauchemin]

nd act solely in the interests of the project. This is
> precisely what we require committers to do.
>
> Yes. It's possible and I think it's the same for different people.
> Actually this statement makes me quite a bit uncomfortable. It somehow
> implies developer's "superiority" in terms of being able to comply with the
> rules of Apache regarding professional affiliation. It hurts my way of
> thinking about people being individuals and I personally think that there
> is a "discriminating" thought hidden in this statement.
>
> Being developer myself I could also feel that way, but I think personal
> integrity is not really related to the role you have in any company or your
> job description or affiliation with the company. I know both "business"
> people and "developers" with both excellent integrity and very poor one. So
> I totally don't see why "business people" would be inferior in this role.
> Both business people and developers have different kinds of commercial
> relation, sometimes ownership sometimes pay structure that might make it
> easier or more difficult to separate the affiliation from the organisation
> they are in - but I think it's eventually all the matter of personal
> integrity, peer pressure and a number of other factors that determine the
> actions of that individual - regardless of the job role they have. I - for
> one - have a significant ownership in the company i work in (being
> co-founder) but my role is purely engineering one - but my ownership could
> also influence decisions I make.
>
> > So, by this logic, a PM would earn committership in a few short months.
> But I guess you’re running into a chicken-and-egg problem: if the only
> contributions a PM can make are triaging bugs, then how can they earn
> enough merit to be made a contributor? One solution is for them to
> contribute in other ways, for example writing documentation and testing.
>
> That's the very thing - chicken and egg - I think it is very hot and
> important topic discussed recently that we should have more "non-code"
> committers in Apache projects and how valuable they are. I think we should
> make it easy for them to contribute. In our case - more often than not -
> PMs input to the documentation can be very, very limited. Most of the
> documentation we have should really be written down by the developers. For
> testing - we do everything possible to automate it in our project, and
> again - there is a limited help PMs can provide here. But this is entirely
> different story for organizing work (in whatever way). It's entirely
> different for Open Source projects than for commercial ones - but it never
> hurts to have someone who watches how the whole organisation works,
> organizes regular retrospectives, and "catalyses" the improvements in the
> way people cooperate - and being able to organize and manage projects
> issues (together with the developers) is a super important part
>   of this.
>
> > There is also a concern whether they can "act solely in the interests of
> the project”. Most of the PMs I know can do this, but a few cannot. Maybe
> it’s part of the ethics of “fiduciary responsibility” taught at business
> school; many PMs see themselves as potential officers of their company
> someday, and act accordingly.
> >
>
> Again just to reiterate. It's the same with engineers/developers. Most of
> them can do this, but a few cannot. I see no reason whatsoever why
> "business" people would be inferior here. It's all matter of personal
> integrity in my opinion, not the role people have in organisation.
>
> > Also beware establishing this model in a project where a majority of
> committers are employed by one company. The business people at such a
> company, even if they are entirely invisible on the dev list, have huge
> influence over the project by what development efforts they choose to fund,
> and how much time they give committers to review patches from outside the
> organization.
>
> True - but those kind of projects are already in a bad shape. I think if
> that's the case, the company (not business people!) has already enough
> influence on the project. And again - I do not feel comfortable with
> "business people" from the company being inferior than "developers". So for
> me this whole point is rather superficial.
>
> > Julian
> >
> >
> >
> > > On Aug 13, 2020, at 9:27 AM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
> > >
> > > xposting from d...@superset.apache.org - what's the right place to
> post this
> > > for ASF-infra's attention?
> > >
> > > -

Giving our PMs and contributors triage rights on GitHub

[Maxime Beauchemin]

xposting from d...@superset.apache.org - what's the right place to post this
for ASF-infra's attention?

---

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.

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

Max

Re: [VOTE] Release Apache Superset (incubating) version 0.37.0

[Maxime Beauchemin]

We need one more vote please, we're anxious to publish this release!

On Sat, Aug 8, 2020 at 11:17 AM Felix Cheung  wrote:

> Furkan, can you help?
>
> On Fri, Aug 7, 2020 at 11:54 AM Ville Brofeldt  >
> wrote:
>
> > Justin and Felix,
> >
> >
> >
> > warm thanks for taking the time to vote! The minimum 72h voting time is
> > now complete, and it would be great to get that last missing vote from
> the
> > IPMC to be able to release this highly anticipated release of Apache
> > Superset (Incubating).
> >
> >
> >
> > Thanks,
> >
> > The Apache Superset (Incubating) Team
> >
> >
> >
> >
> >
> >
> >
> > > On 4. Aug 2020, at 20.19, Ville Brofeldt 
> > wrote:
> >
> > >
> >
> > > Hello IPMC,
> >
> > >
> >
> > > The Apache Superset (incubating) community has voted on and approved a
> > proposal to
> >
> > > release Apache Superset (incubating) version 0.37.0.
> >
> > > The voting thread can be found here:
> >
> https://lists.apache.org/thread.html/r76d4a5f850546aed4f5ba94c5c8f7b3cb901d8842ed32832512e715b%40%3Cdev.superset.apache.org%3E
> >
> > >
> >
> > >
> >
> > > Here are the binding +1 votes from mentors, carrying over from the
> > podling vote:
> >
> > > - Felix
> >
> > >
> >
> > > We now kindly request the Incubator PMC members review and vote on this
> >
> > > incubator release.
> >
> > >
> >
> > > Apache Superset (incubating) is a modern, enterprise-ready business
> > intelligence web application
> >
> > >
> >
> > > The release candidate:
> >
> > > https://dist.apache.org/repos/dist/dev/incubator/superset/0.37.0rc4/
> >
> > >
> >
> > > Git tag for the release:
> >
> > > https://github.com/apache/incubator-superset/tree/0.37.0rc4
> >
> > >
> >
> > > The Change Log for the release:
> >
> > >
> https://github.com/apache/incubator-superset/blob/0.37.0rc4/CHANGELOG.md
> >
> > >
> >
> > > public keys are available at:
> >
> > >
> >
> > > https://www.apache.org/dist/incubator/superset/KEYS
> >
> > >
> >
> > > The vote will be open for at least 72 hours or until the necessary
> number
> >
> > > of votes are reached.
> >
> > >
> >
> > > Please vote accordingly:
> >
> > >
> >
> > > [ ] +1 approve
> >
> > > [ ] +0 no opinion
> >
> > > [ ] -1 disapprove with the reason
> >
> > >
> >
> > > Thanks,
> >
> > > The Apache Superset (Incubating) Team
> >
> >
> >
> >
>

Broken links on https://incubator.apache.org/guides/graduation.html

[Maxime Beauchemin]

Hi IPMC,

We noticed that many links seem broken on the graduation documentation and
thought we'd bring this to your attention. Specifically, most of the links
under the "Graduation Check List" section

https://incubator.apache.org/guides/graduation.html

Thanks,

Max

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

[Maxime Beauchemin]

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

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

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

Max

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

> Dear all,
>
> The Apache Superset (incubating) community is happy to announce Apache
> Superset (incubating) version 0.34.1, our second official Apache release!
>
> Apache Superset (incubating) is a business intelligence web application.
>
> A full list of the changes in this release can be found in the release
> notes:
>
> https://github.com/apache/incubator-superset/blob/master/CHANGELOG.md#change-log
>
> A link to the source download can be found here:
> https://www.apache.org/dist/incubator/superset/0.34.1/
>
> Find links to Apache Superset related resources on our Github:
> https://github.com/apache/incubator-superset
>
> Best regards,
>
> The Apache Superset (incubating) Team
> ___
> DISCLAIMER:
> Apache Superset (incubating) is an effort undergoing incubation at The
> Apache Software Foundation (ASF), sponsored by the name of Apache Incubator
> PMC. Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects. While incubation status is not necessarily a reflection of
> the completeness or stability of the code, it does indicate that the
> project has yet to be fully endorsed by the ASF.
>

[ANNOUNCE] Release Apache Superset (incubating) version 0.34.0

[Maxime Beauchemin]

Dear all,

The Apache Superset (incubating) community is happy to announce Apache
Superset
(incubating) version 0.34.0!

Apache Superset (incubating) is a business intelligence web application

*0.34.0 is our first official Apache release!*

A full list of the changes in this release can be found in the release
notes:
https://github.com/apache/incubator-superset/blob/master/CHANGELOG.md#change-log

A link to the source download can be found here:
https://www.apache.org/dist/incubator/superset/

Find links to Apache Superset related resources on our Github:
https://github.com/apache/incubator-superset

Best regards,

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

[RESULT][VOTE] Release Apache Superset (incubating) 0.34.0 [RC2]

[Maxime Beauchemin]

Votes passes with:

3 * "+1" binding votes from IPMC members (Furkan, Kevin, Alan)
2 * "+1" non-binding votes from PPMC members (Max & Jeff)

no negative of neutral votes

Keep in mind that RC2 is a very minor update on RC1 which was voted very
positively as well.


Vote thread Permalink:
https://lists.apache.org/thread.html/b0fe23ae8bbb933d86de6750df79d5474cd8336866077dc0f3792138@

Thank you to the above IPMC members for taking the time to review and
provide guidance on our release!

We will proceed with publishing the approved artifacts and sending out
the appropriate announcements in the coming days.

Max


On Mon, Aug 26, 2019 at 2:32 PM Alan Gates  wrote:

> +1.
>
> Alan.
>
> On Fri, Aug 23, 2019 at 12:56 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Hi IPMC,
> >
> > The Apache Superset PPMC and IPMC recently voted and passed a vote on RC1
> > recently, only to realize that there's was a minor blocking. The blocker
> > was that the version was labelled `0.34.0rc1` inside the tarball, as
> > opposed to `0.34.0`, meaning that when installing from source, the
> Python &
> > npm packages would appear to be a `0.34.0rc1`. As you know, altering the
> > tarball invalidates the MD5 / signature, so this is why we need this very
> > minor tweak.
> >
> > 0.34.0rc2 addresses this, and uses `0.34.0` as the version number inside
> > the tarball. I also addressed some of the [non-blocking] licensing
> comments
> > surfaced during the RC1 process, and included the latest CHANGELOG in the
> > tarball.
> >
> > Here are the 3 commits on top of RC1:
> > 20e68c87 (HEAD -> 0.34, tag: 0.34.0rc2, origin/0.34, apache/0.34) Set
> > version to 0.34.0 (no rcN)
> > 6acd25d1 fix: minor release/license related issues (#8087)
> > a13fb1d2 CHANGELOG for 0.30...0.34 (#8089)
> >
> > *This would be the first Apache release of Superset.*
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Apache Superset (incubating) is a business intelligence web application
> >
> > The community voting thread (for RC1) can be found here:
> >
> >
> https://lists.apache.org/thread.html/c9ad3ce592a695ceeabfa92969c00c0d7be8e3420b6a221c7e806f40@%3Cdev.superset.apache.org%3E
> >
> > The release candidate has been tagged in GitHub as tag 0.34.0rc2
> > <https://github.com/apache/incubator-superset/releases/tag/0.34.0rc2>,
> > available here:
> > https://github.com/apache/incubator-superset/releases/tag/0.34.0rc2
> >
> > The artifacts to be voted on are located here:
> > https://dist.apache.org/repos/dist/dev/incubator/superset/
> >
> > Release artifacts are signed with the key located here:
> > https://dist.apache.org/repos/dist/release/incubator/superset/KEYS
> >
> > This vote will be open for at least 72 hours. The vote will pass if a
> > majority of at least three +1 IPMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Superset (incubating)
> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> > Thank you IPMC! We appreciate your efforts in helping the Apache Superset
> > community to validate this release.
> >
> > On behalf of the Apache Superset Community,
> >
> > Max
> >
> > 
> >
> > Apache Superset (incubating) is an effort undergoing incubation at The
> > Apache
> > Software Foundation (ASF), sponsored by the Apache 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.
> >
>

[VOTE] Release Apache Superset (incubating) 0.34.0 [RC2]

[Maxime Beauchemin]

Hi IPMC,

The Apache Superset PPMC and IPMC recently voted and passed a vote on RC1
recently, only to realize that there's was a minor blocking. The blocker
was that the version was labelled `0.34.0rc1` inside the tarball, as
opposed to `0.34.0`, meaning that when installing from source, the Python &
npm packages would appear to be a `0.34.0rc1`. As you know, altering the
tarball invalidates the MD5 / signature, so this is why we need this very
minor tweak.

0.34.0rc2 addresses this, and uses `0.34.0` as the version number inside
the tarball. I also addressed some of the [non-blocking] licensing comments
surfaced during the RC1 process, and included the latest CHANGELOG in the
tarball.

Here are the 3 commits on top of RC1:
20e68c87 (HEAD -> 0.34, tag: 0.34.0rc2, origin/0.34, apache/0.34) Set
version to 0.34.0 (no rcN)
6acd25d1 fix: minor release/license related issues (#8087)
a13fb1d2 CHANGELOG for 0.30...0.34 (#8089)

*This would be the first Apache release of Superset.*

We now kindly request the Incubator PMC members review and vote on this
incubator release.

Apache Superset (incubating) is a business intelligence web application

The community voting thread (for RC1) can be found here:
https://lists.apache.org/thread.html/c9ad3ce592a695ceeabfa92969c00c0d7be8e3420b6a221c7e806f40@%3Cdev.superset.apache.org%3E

The release candidate has been tagged in GitHub as tag 0.34.0rc2
,
available here:
https://github.com/apache/incubator-superset/releases/tag/0.34.0rc2

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/superset/

Release artifacts are signed with the key located here:
https://dist.apache.org/repos/dist/release/incubator/superset/KEYS

This vote will be open for at least 72 hours. The vote will pass if a
majority of at least three +1 IPMC votes are cast.

[ ] +1 Release this package as Apache Superset (incubating)
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...

Thank you IPMC! We appreciate your efforts in helping the Apache Superset
community to validate this release.

On behalf of the Apache Superset Community,

Max



Apache Superset (incubating) is an effort undergoing incubation at The
Apache
Software Foundation (ASF), sponsored by the Apache 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.

Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

[Maxime Beauchemin]

Ok, I have an RC2 ready to go with very minor changes, will kick off [only]
a general@ vote and tell dev@ & PPMC they can vote on general@

Max

On Thu, Aug 22, 2019 at 11:44 AM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi,
>
> I agree with Alan that its really minor but as the signatures will change
> I would prefer another Vote to have this checked.
> If you (as Justin suggests) state your changes clearly in the thread I
> think everybody will easily carry over the vote from the previous thread so
> its just about waiting 72hrs but ensure that everything is alright.
>
> Julian
>
> Am 22.08.19, 19:21 schrieb "Alan Gates" :
>
> I would call a revote over that, it's not like you're changing
> anything of
> import.  I'd just regen the package with the change, create the new
> hash,
> and let everyone know.  I don't see any reason to drag back through the
> voting process on two lists over this.
>
> Alan.
>
> On Wed, Aug 21, 2019 at 10:43 PM Justin Mclean <
> jus...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> > > Oh here's something. Somewhere inside the source release I have a
> version
> > > string that says "0.34.0rc1" and that now I'm realizing should
> really say
> > > "0.34.0" as it becomes an official release. Now changing that
> string will
> > > make for a different SHA.
> >
> > That's a bit awkward. It would be best to call a vote again if it
> needs to
> > be changed, given the changes shod be minor it shod be easy to
> review.
> >
> > Other IPMC members might have another view. Anyone?
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
>

Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

[Maxime Beauchemin]

Oh here's something. Somewhere inside the source release I have a version
string that says "0.34.0rc1" and that now I'm realizing should really say
"0.34.0" as it becomes an official release. Now changing that string will
make for a different SHA.

How should I go about this?

On Wed, Aug 21, 2019 at 9:54 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Thanks Justin, I just addressed 1,2 and 3 here
> https://github.com/apache/incubator-superset/pull/8087, but since these
> issues seems non-blocking (given your +1) the fixes won't make 0.34.0 which
> looks like it is good to go.
>
> I couldn't get a clear read on the monokai theme's license either, I'll
> see with Erik who introduced these line whether we can just remove the
> lines.
>
> Oh, mentors, quick question about the [RESULT] post, do I account for both
> threads (dev@+general@) in it, or just the general@ one?
>
> Max
>
> On Tue, Aug 20, 2019 at 8:05 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> +1 (binding)
>>
>> I checked:
>> - incubating in name
>> - signatures and hashes fine
>> - DISCLAIMER exists, although you may want to use the DISCLAIMER_WIP [8]
>> - LICENSE is probably missing a few things (se below)
>> - NOTICE is fine
>> - No unexpected binary files
>> - I didn’t check compiling from source
>>
>> LiCENSE is missing:
>> - This BSD licensed file [1] The file also has an incorrectly has an ASF
>> header on it.
>> - This file in not mentioned [2] and I think is licensed like so [3] If
>> so that may be problematic [4]. However I seem to recall this was discussed
>> before so there may of been some conclusion about it? I also note that
>> .*geojson are explicitly listed in your rat excludes so I assume there a
>> reason for that. (Comments in the rat exclusion file could help here).
>> - This file [5] looks to contain the Monokai theme from [6] I’m unsure
>> how this is licensed. The pro version seems to require a commercial
>> license. It might of come from here [7]? which is MIT licensed.
>>
>> Thanks,
>> Justin
>>
>> 1. ./superset/extract_table_names.py
>> 2 ./assets/src/visualizations/CountryMap/countries/india.geojson
>> 3. ./licenses/LICENSE-diva-gis.txt
>> 4. https://apache.org/legal/resolved.html#cc-by
>> 5. superset/assets/src/components/FilterableTable/FilterableTable.jsx
>> 6. https://www.monokai.nl
>> 7 https://packagecontrol.io/packages/Monokai%20JSON%2B
>> 8 https://incubator.apache.org/policy/incubation.html#disclaimers
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

[RESULT][VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

[Maxime Beauchemin]

Dear community,

I'm happy to announce that the vote passes with 9 * +1 votes (7 binding, 2
non-binding)

*+1 votes*
* Justin Mclean (binding)
* Jim Jagielski (binding)
* Julian Feinauer (binding)
* Alan Gates (binding)
* Abhishek Sharma (binding)
* Jakob Homan (binding)
* Furkan Kamaci (binding)
* Jeff Feng (non-binding)
* Bolke de Bruin (non-binding)

*0 votes*
* None

*-1 votes*
* None

Vote thread can be found here
<https://mail-archives.apache.org/mod_mbox/incubator-general/201908.mbox/%3CCAHEEp7WeH8kWTP3WWeFOGVjx6oARRSW_o2Yd%3DHaF1J3tXH7kEg%40mail.gmail.com%3E>,
and the list members can be found here
<http://home.apache.org/phonebook.html?ctte=incubator>.

Look forward to an [ANNOUNCE] thread for the 0.34.0 release in the next few
days.

Cheers!

Max


On Wed, Aug 21, 2019 at 9:54 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Thanks Justin, I just addressed 1,2 and 3 here
> https://github.com/apache/incubator-superset/pull/8087, but since these
> issues seems non-blocking (given your +1) the fixes won't make 0.34.0 which
> looks like it is good to go.
>
> I couldn't get a clear read on the monokai theme's license either, I'll
> see with Erik who introduced these line whether we can just remove the
> lines.
>
> Oh, mentors, quick question about the [RESULT] post, do I account for both
> threads (dev@+general@) in it, or just the general@ one?
>
> Max
>
> On Tue, Aug 20, 2019 at 8:05 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> +1 (binding)
>>
>> I checked:
>> - incubating in name
>> - signatures and hashes fine
>> - DISCLAIMER exists, although you may want to use the DISCLAIMER_WIP [8]
>> - LICENSE is probably missing a few things (se below)
>> - NOTICE is fine
>> - No unexpected binary files
>> - I didn’t check compiling from source
>>
>> LiCENSE is missing:
>> - This BSD licensed file [1] The file also has an incorrectly has an ASF
>> header on it.
>> - This file in not mentioned [2] and I think is licensed like so [3] If
>> so that may be problematic [4]. However I seem to recall this was discussed
>> before so there may of been some conclusion about it? I also note that
>> .*geojson are explicitly listed in your rat excludes so I assume there a
>> reason for that. (Comments in the rat exclusion file could help here).
>> - This file [5] looks to contain the Monokai theme from [6] I’m unsure
>> how this is licensed. The pro version seems to require a commercial
>> license. It might of come from here [7]? which is MIT licensed.
>>
>> Thanks,
>> Justin
>>
>> 1. ./superset/extract_table_names.py
>> 2 ./assets/src/visualizations/CountryMap/countries/india.geojson
>> 3. ./licenses/LICENSE-diva-gis.txt
>> 4. https://apache.org/legal/resolved.html#cc-by
>> 5. superset/assets/src/components/FilterableTable/FilterableTable.jsx
>> 6. https://www.monokai.nl
>> 7 https://packagecontrol.io/packages/Monokai%20JSON%2B
>> 8 https://incubator.apache.org/policy/incubation.html#disclaimers
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

[Maxime Beauchemin]

Thanks Justin, I just addressed 1,2 and 3 here
https://github.com/apache/incubator-superset/pull/8087, but since these
issues seems non-blocking (given your +1) the fixes won't make 0.34.0 which
looks like it is good to go.

I couldn't get a clear read on the monokai theme's license either, I'll see
with Erik who introduced these line whether we can just remove the lines.

Oh, mentors, quick question about the [RESULT] post, do I account for both
threads (dev@+general@) in it, or just the general@ one?

Max

On Tue, Aug 20, 2019 at 8:05 PM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signatures and hashes fine
> - DISCLAIMER exists, although you may want to use the DISCLAIMER_WIP [8]
> - LICENSE is probably missing a few things (se below)
> - NOTICE is fine
> - No unexpected binary files
> - I didn’t check compiling from source
>
> LiCENSE is missing:
> - This BSD licensed file [1] The file also has an incorrectly has an ASF
> header on it.
> - This file in not mentioned [2] and I think is licensed like so [3] If so
> that may be problematic [4]. However I seem to recall this was discussed
> before so there may of been some conclusion about it? I also note that
> .*geojson are explicitly listed in your rat excludes so I assume there a
> reason for that. (Comments in the rat exclusion file could help here).
> - This file [5] looks to contain the Monokai theme from [6] I’m unsure how
> this is licensed. The pro version seems to require a commercial license. It
> might of come from here [7]? which is MIT licensed.
>
> Thanks,
> Justin
>
> 1. ./superset/extract_table_names.py
> 2 ./assets/src/visualizations/CountryMap/countries/india.geojson
> 3. ./licenses/LICENSE-diva-gis.txt
> 4. https://apache.org/legal/resolved.html#cc-by
> 5. superset/assets/src/components/FilterableTable/FilterableTable.jsx
> 6. https://www.monokai.nl
> 7 https://packagecontrol.io/packages/Monokai%20JSON%2B
> 8 https://incubator.apache.org/policy/incubation.html#disclaimers
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Release Apache Superset (incubating) 0.34.0 [RC1]

[Maxime Beauchemin]

Hi IPMC,

The Apache Superset community has voted on and approved a proposal to
release
Apache Superset (incubating) 0.34.0 (rc1). *This would be the first Apache
release of Superset.*

We now kindly request the Incubator PMC members review and vote on this
incubator release.

Apache Superset (incubating) is a business intelligence web application

The community voting thread can be found here:
https://lists.apache.org/thread.html/c9ad3ce592a695ceeabfa92969c00c0d7be8e3420b6a221c7e806f40@%3Cdev.superset.apache.org%3E

The release candidate has been tagged in GitHub as tag 0.34.0rc1
,
available here:
https://github.com/apache/incubator-superset/releases/tag/0.34.0rc1

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/superset/

Release artifacts are signed with the key located here:
https://dist.apache.org/repos/dist/release/incubator/superset/KEYS

This vote will be open for at least 72 hours. The vote will pass if a
majority of at least three +1 IPMC votes are cast.

[ ] +1 Release this package as Apache Superset (incubating) 0.15.1
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...

Thank you IPMC! We appreciate your efforts in helping the Apache Superset
community to validate this release.

On behalf of the Apache Superset Community,

Max



Apache Superset (incubating) is an effort undergoing incubation at The
Apache
Software Foundation (ASF), sponsored by the Apache 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.

Re: FOSSA.com: a new service to monitor licenses on Github repos

[Maxime Beauchemin]

Occurrences of GPL boiled down to:
* libs that supports GPL and something else, as in "MIT and GPL"
* "GPL" strings in repo as in "... this license is 100% compatible with GPL
...", in other instances, it could catch a copy/pasted function with a GPL
annotation in the code/docstring
* dev dependencies, things like sphinx (to build our docs), or pylint, a
linter, that doesn't ship or installs with the package

Also FOSSA did a good job of showing missing/dubious licenses, flagging
files or function that have license text in them, and showing where that
dependency (sometimes many nodes deep) fits in the tree. It also is good at
whitelisting and adding notes / context.

I looked into fossology a little, and it's unclear whether they offer a
Github-centric service with webhooks and all. It may require adding a check
in CI, which seems less desirable for our use case.

More generally, 3rd party Github services are becoming more and more
compelling and it's been empowering to use them, from things like probot,
codecov, travis, simon, requires.io, just to name a few, and clearly has a
place in high-velocity open source development. I'd love if we didn't have
to open ASF-INFRA tickets to set and tune those up. Fundamentally this
would probably require for the ASF to allow project to use their own Github
orgs & repos, where they can be admins. Linux Foundation allows for that
for example, so this may do doable. This is probably controversial, and I'm
guessing that's been discussed here before...

Max


On Tue, Jul 9, 2019 at 10:35 AM Ted Dunning  wrote:

> License scans like this are great, particularly for software that will
> eventually be scanned by some commercial user anyway. Hopefully most
> projects are simpler than Superset, though.
>
> Looking at the scan results, however, immediately raises the question about
> all the GPL licenses turned up in the scan. Is the Superset project aware
> of those dependencies?
>
>
>
> On Mon, Jul 8, 2019 at 11:30 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
> > Hi all,
> >
> > [this is not a promotional email in any way, I'm not affiliated with the
> > service/company discussed here]
> >
> > I just discovered fossa.com, self described as "Realtime license and
> > vulnerability management
> > for open source dependencies".
> >
> > For context, Apache Superset has a dependency tree rich of 700+ deps
> (crazy
> > right?), at that scale license management is huge burden at best, or
> worse:
> > a legal risk for the ASF.
> >
> > Oh btw I tried searching the ASF mailing lists for existing threads on
> this
> > topic but failed miserably, apologies if this has been discussed already.
> >
> > I couldn't set up the FOSSA service on the projects repo I'm PMC on as I
> > don't have the required Github rights, but I set it up against my fork
> and
> > it's all you could ever hope for in terms of license-related automation.
> > See it in action here:
> >
> >
> https://app.fossa.com/projects/git%2Bgithub.com%2Fmistercrunch%2Fsuperset/refs/branch/master/396a655de13ced6e25f4e793b0eb281bf4f4cd79/issues/licensing?status=resolved
> >
> > It seems like we may want to set this up against most if not all ASF
> > projects. As the ASF is in the line of fire for legal troubles around
> > licensing, it seems like automation/prevention would be strategic,
> > especially in a world where micro packages and frequent releases are
> > trending. Without using a service like this one, bumping a release, or
> even
> > just allowing an open version range can result in integrating
> > non-permissive licenses in a bundle, in ways that could take months to
> > catch, if ever.
> >
> > For the record I opened a ticket with ASF infra to set it up on
> > `apache/incubator-superset`:
> > https://issues.apache.org/jira/browse/INFRA-18719 I'm hoping this goes
> > smoothly, and that Apache Infra is ok granting the required perms to
> FOSSA.
> >
> > I wanted to bring the attention to this as this seems like something very
> > useful for most projects.
> >
> > Thoughts?
> >
> > Max
> >
>

FOSSA.com: a new service to monitor licenses on Github repos

[Maxime Beauchemin]

Hi all,

[this is not a promotional email in any way, I'm not affiliated with the
service/company discussed here]

I just discovered fossa.com, self described as "Realtime license and
vulnerability management
for open source dependencies".

For context, Apache Superset has a dependency tree rich of 700+ deps (crazy
right?), at that scale license management is huge burden at best, or worse:
a legal risk for the ASF.

Oh btw I tried searching the ASF mailing lists for existing threads on this
topic but failed miserably, apologies if this has been discussed already.

I couldn't set up the FOSSA service on the projects repo I'm PMC on as I
don't have the required Github rights, but I set it up against my fork and
it's all you could ever hope for in terms of license-related automation.
See it in action here:
https://app.fossa.com/projects/git%2Bgithub.com%2Fmistercrunch%2Fsuperset/refs/branch/master/396a655de13ced6e25f4e793b0eb281bf4f4cd79/issues/licensing?status=resolved

It seems like we may want to set this up against most if not all ASF
projects. As the ASF is in the line of fire for legal troubles around
licensing, it seems like automation/prevention would be strategic,
especially in a world where micro packages and frequent releases are
trending. Without using a service like this one, bumping a release, or even
just allowing an open version range can result in integrating
non-permissive licenses in a bundle, in ways that could take months to
catch, if ever.

For the record I opened a ticket with ASF infra to set it up on
`apache/incubator-superset`:
https://issues.apache.org/jira/browse/INFRA-18719 I'm hoping this goes
smoothly, and that Apache Infra is ok granting the required perms to FOSSA.

I wanted to bring the attention to this as this seems like something very
useful for most projects.

Thoughts?

Max

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

[Maxime Beauchemin]

I replaced the babytux image by one I got here
https://pixabay.com/vectors/toddlers-babies-children-303904/, now how do I
expose the license for the image?

Max

On Fri, May 17, 2019 at 4:36 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> Making progress here
> https://github.com/apache/incubator-superset/pull/7539
>
> Many of the issues have been addressed in `master` but can't easily be
> cherry-picked into 0.32, so I'm thinking about skipping to 0.33 instead
> that has been cut 1 month ago. So the next attempt will be `0.33.0rc1`
>
> Max
>
> On Tue, Apr 30, 2019 at 5:34 PM Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
>
>> FYI I'm working integrating the feedback and working towards the next RC.
>>
>> I started working on build instructions and things were getting quite
>> complex while building from source, and adding steps like the os-level
>> deps, creating the `.po` files, building the JS, and these instructions
>> tend to not be perfectly reproducible across environments, so I decided to
>> write a Dockerfile that builds from source instead of docs or a bash
>> script. Eventually that can evolve to run assertions on the build (running
>> tests, checking keys, ...) in a reproducible fashion. The built package can
>> be extracted from the docker image, or the Dockerfile can be used as a
>> reference if someone needed to make an equivalent bash script.
>>
>> Similarly, I'm thinking about using a Dockerfile for the process of
>> packaging the source release, since the process forces a "git clean" that
>> can be harmful to existing environments.
>>
>> Max
>>
>> On Sat, Apr 27, 2019 at 1:40 AM  wrote:
>>
>>> Hi,
>>>
>>> > - they are not? I dont follow? How would you suggest making them
>>> binary then?
>>>
>>> Ask on legal discuss, I don’t think they will be allowed in a source
>>> release, but it may be possible given maps are not likely to change much.
>>> Worse case you may have to find some maps under a different license or ask
>>> for them to be relicensed under a more friendly license.
>>>
>>> > On the other hand the initial picture you painted seemed quite grim
>>> but these issues can be overcome relatively easy.
>>>
>>> All of the issues are easy to fix one way or another, this stuff is hard
>>> to get right first time around, but gets easier.
>>>
>>> Thanks,
>>> Justin
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>

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

[Maxime Beauchemin]

Making progress here https://github.com/apache/incubator-superset/pull/7539

Many of the issues have been addressed in `master` but can't easily be
cherry-picked into 0.32, so I'm thinking about skipping to 0.33 instead
that has been cut 1 month ago. So the next attempt will be `0.33.0rc1`

Max

On Tue, Apr 30, 2019 at 5:34 PM Maxime Beauchemin <
maximebeauche...@gmail.com> wrote:

> FYI I'm working integrating the feedback and working towards the next RC.
>
> I started working on build instructions and things were getting quite
> complex while building from source, and adding steps like the os-level
> deps, creating the `.po` files, building the JS, and these instructions
> tend to not be perfectly reproducible across environments, so I decided to
> write a Dockerfile that builds from source instead of docs or a bash
> script. Eventually that can evolve to run assertions on the build (running
> tests, checking keys, ...) in a reproducible fashion. The built package can
> be extracted from the docker image, or the Dockerfile can be used as a
> reference if someone needed to make an equivalent bash script.
>
> Similarly, I'm thinking about using a Dockerfile for the process of
> packaging the source release, since the process forces a "git clean" that
> can be harmful to existing environments.
>
> Max
>
> On Sat, Apr 27, 2019 at 1:40 AM  wrote:
>
>> Hi,
>>
>> > - they are not? I dont follow? How would you suggest making them binary
>> then?
>>
>> Ask on legal discuss, I don’t think they will be allowed in a source
>> release, but it may be possible given maps are not likely to change much.
>> Worse case you may have to find some maps under a different license or ask
>> for them to be relicensed under a more friendly license.
>>
>> > On the other hand the initial picture you painted seemed quite grim but
>> these issues can be overcome relatively easy.
>>
>> All of the issues are easy to fix one way or another, this stuff is hard
>> to get right first time around, but gets easier.
>>
>> Thanks,
>> Justin
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

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

[Maxime Beauchemin]

FYI I'm working integrating the feedback and working towards the next RC.

I started working on build instructions and things were getting quite
complex while building from source, and adding steps like the os-level
deps, creating the `.po` files, building the JS, and these instructions
tend to not be perfectly reproducible across environments, so I decided to
write a Dockerfile that builds from source instead of docs or a bash
script. Eventually that can evolve to run assertions on the build (running
tests, checking keys, ...) in a reproducible fashion. The built package can
be extracted from the docker image, or the Dockerfile can be used as a
reference if someone needed to make an equivalent bash script.

Similarly, I'm thinking about using a Dockerfile for the process of
packaging the source release, since the process forces a "git clean" that
can be harmful to existing environments.

Max

On Sat, Apr 27, 2019 at 1:40 AM  wrote:

> Hi,
>
> > - they are not? I dont follow? How would you suggest making them binary
> then?
>
> Ask on legal discuss, I don’t think they will be allowed in a source
> release, but it may be possible given maps are not likely to change much.
> Worse case you may have to find some maps under a different license or ask
> for them to be relicensed under a more friendly license.
>
> > On the other hand the initial picture you painted seemed quite grim but
> these issues can be overcome relatively easy.
>
> All of the issues are easy to fix one way or another, this stuff is hard
> to get right first time around, but gets easier.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Release Superset 0.32.0 based on Superset 0.32.0 RC2

[Maxime Beauchemin]

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*
.

Here's link to original successful VOTE thread on dev@:
http://mail-archives.apache.org/mod_mbox/superset-dev/201904.mbox/%3ccah7q75ip1lzq61+6yvfoqvb2nser8vhsa5rca87uzrrbpj9...@mail.gmail.com%3E

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

Re: Challenges using Gitbox

[Maxime Beauchemin]

Thanks everyone for all the input!

I had not looked at https://lists.apache.org/ in a while and it looks
pretty usable along with the "site:" Google trick. Thanks to those who made
"Apache Mail Archives" happen!

About PMs, or other "non-coding contributors", it's pretty common to have
them at sponsoring organizations. For example both Airbnb and Lyft both
have a dedicated PM for Apache Superset. While they don't write code, they
contribute to the project and many other ways (prioritization / planning /
road-mapping, shaping product design, communication, training,
documentation, bug reports, issue triaging,  organizing events, ...). It
sounds like the solution is to make them committers to provide them with
the level of control they need on Github.

Another point I didn't bring up in my original email is the obsolescence of
Apache's svn binaries repository in the light of commonly used package
manager (Pypi.org for Python, npm for Javacsript, ..., Maven for Java(?) ,
...). While I understand the importance of the ASF being independent and
the need for signed binaries, it seems like effectively everyone will just
use the release available on popular package manager. Maybe in a perfect
world we'd have tooling that pushes to both repos atomically. In the
meantime, I guess it's for podlings to build their own process & tooling to
ship their releases.

On Mon, Apr 16, 2018 at 6:39 AM, Ralph Goers <ralph.go...@dslextreme.com>
wrote:

>
>
> > On Apr 11, 2018, at 11:11 AM, Maxime Beauchemin <
> maximebeauche...@gmail.com> wrote:
> >
> > Hi general@incubator!
> >
> > This is an email discussing the challenges we are facing while using
> Github
> > / Gitbox for our ASF project and wanted to start a thread to discuss
> > solutions and ways we can mitigate.
> >
> > We're very grateful for Gitbox, but here are the challenges we're facing
> > with it:
> >
> > 1. Our PMs are not committers, so they can't do simple things as labeling
> > issues, closing issues and assigning issues to people. We need either for
> > them to have write access to Github, or for them to get some sort of
> > special committer status so they can get write access. Is voting PMs as
> > committers the solution here?
>
>
> I’m just wondering what a project manager is in the context of an Apache
> project? Why would anyone be assigning issues to people? This is a
> volunteer organization.  If this is being done as part of an employer then
> it should not be handled at the ASF.
>
> Ralph
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Challenges using Gitbox

[Maxime Beauchemin]

Hi general@incubator!

This is an email discussing the challenges we are facing while using Github
/ Gitbox for our ASF project and wanted to start a thread to discuss
solutions and ways we can mitigate.

We're very grateful for Gitbox, but here are the challenges we're facing
with it:

1. Our PMs are not committers, so they can't do simple things as labeling
issues, closing issues and assigning issues to people. We need either for
them to have write access to Github, or for them to get some sort of
special committer status so they can get write access. Is voting PMs as
committers the solution here?

2. From what I gather using Github issues as a replacement for Jira is ok
as long as we set Github notifications to be sent to the mailing list. The
problem is that this makes our mailing list unusable for other purposes
than getting spammed out of our minds with Github notifications. I think
the solution would be to standardize on 2 mailing lists:
`github-notifications@{project}.apache.org` and the good old `dev@`. Though
for early adopters `dev@` is probably busted as people have filters set up
against it already. So is the solution to create another list and get
everyone to sign up for it?

3. The mailing list is a bit dated. I'm saying "a bit" here as an attempt
to be polite. Maintainers have to sort through spam (AI had solved this a
decade ago!), it's hard to know how many people and who are signed up, no
weekly or daily digest-type features, SEO is bad and the list aren't very
searchable. Something like Google Groups would be a huge step forward here.

4. Github ecosystem services (build systems, code quality services, code
coverage services, version manager, ...) are hard and sometimes impossible
to setup (without admin Github privileges), forcing us to open INFRA Jira
tickets for this. I understand the limitations here, and a lot of it is on
the Github side, but would like to think of ways to mitigate this, perhaps
by using specified "main-forks" where committers have more control? Just a
list of "Apache Approved Github-services" would help.

The ASF is all about helping growing communities, and making committers as
productive as can be should be a top priority. Joining the ASF shouldn't
make governance harder.

I hear other software foundations are less opinionated in terms of tooling,
is that something the ASF should consider? What are the constraints?

Cheers!

Max

[RESULT][VOTE] Release Airflow 1.8.2 based on Airflow 1.8.2 RC4

[Maxime Beauchemin]

Hi All,

The vote for releasing *Apache Airflow 1.8.2-incubating* is now closed.

With a total of *+3 binding* votes, the vote passes:
* Justin McLean
* John D. Ament
* Pierre Smits

Thank you to all the reviewers for taking the time to validate this release
and
provide very good feedback. We will make sure to incorporate all the
suggested changes in the next release.

Regards!

Maxime Beauchemin

On Wed, Aug 23, 2017 at 12:31 AM, Pierre Smits <pierre.sm...@gmail.com>
wrote:

> +1
>
> Best regards
>
> Pierre
>
> On Tue, 22 Aug 2017 at 13:23 John D. Ament <johndam...@apache.org> wrote:
>
> > Hi,
> >
> > +1 to release...however, please make sure you are cleaning up your old
> > releases.  Do not keep old releases on dist.a.o.
> >
> > John
> >
> > On Wed, Aug 16, 2017 at 6:18 PM Maxime Beauchemin <
> > maximebeauche...@gmail.com> wrote:
> >
> > > Hello Incubator PMC’ers,
> > >
> > > The Apache Airflow community has voted and approved the proposal to
> > release
> > > Apache Airflow 1.8.2 (incubating) based on 1.8.2 Release Candidate 4.
> We
> > > now kindly request the Incubator PMC members to review and vote on this
> > > incubator release.
> > >
> > > Airflow is a platform to programmatically author, schedule and monitor
> > > workflows. Use airflow to author workflows as directed acyclic graphs
> > > (DAGs) of tasks. The airflow scheduler executes your tasks on an array
> of
> > > workers while following the specified dependencies. Rich command line
> > > utilities make performing complex surgeries on DAGs a snap. The rich
> user
> > > interface makes it easy to visualize pipelines running in production,
> > > monitor progress, and troubleshoot issues when needed. When workflows
> are
> > > defined as code, they become more maintainable, versionable, testable,
> > and
> > > collaborative.
> > >
> > > Artefacts are available at https://dist.apache.org/repos/
> > > dist/dev/incubator/airflow, public keys are available at
> > > https://dist.apache.org/repos/dist/release/incubator/airflow.
> > >
> > > apache-airflow-1.8.2+incubating-source.tar.gz
> > > <
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.
> 8.2rc4/apache-airflow-1.8.2+incubating-source.tar.gz
> > > >
> > > is
> > > a source release that comes with INSTALL instructions. Along with it,
> for
> > > convenience, find the binary Python "sdist" as apache-airflow-1.8.2+
> > > incubating-bin.tar.gz
> > > <
> > >
> > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.
> 8.2rc4/apache-airflow-1.8.2+incubating-bin.tar.gz
> > > >
> > >
> > > Vote thread:
> > >
> > >
> > http://mail-archives.apache.org/mod_mbox/incubator-
> airflow-dev/201708.mbox/browser
> > >
> > > Git tag:
> > > https://github.com/apache/incubator-airflow/releases/tag/1.8.2rc4
> > >
> > > The vote will be open for at least 72 hours or until necessary number
> of
> > > votes are reached.
> > >
> > > Members please be sure to indicate "(Binding)" with your vote which
> will
> > > help in tallying the vote(s).
> > >
> > > * Here is my +1 (non-binding) *
> > >
> > > Cheers,
> > >
> > > Maxime Beauchemin
> > >
> >
> --
> Pierre Smits
>
> ORRTIZ.COM <http://www.orrtiz.com>
> OFBiz based solutions & services
>
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
>

Re: [VOTE] Release Airflow 1.8.2 based on Airflow 1.8.2 RC4

[Maxime Beauchemin]

Here's the related JIRA:
https://issues.apache.org/jira/browse/AIRFLOW-1525

On Wed, Aug 16, 2017 at 9:17 PM, Justin Mclean 
wrote:

> Hi,
>
> +1 (binding) if a JIRA is raised and licensing issue fixed in next release.
>
> I checked:
> - incubator in name
> - signatures and hashes good
> - disclaimer exists
> - year in NOTICE is incorrect
> - LICENSE is missing several things (see below)
> - No unexpected binary files
> - all source files have ASF headers
> - can compile from source
> - could compile from source (with a little effort)
>
> LICENSE is missing this BSD licensed file [1], this MIT licensed  file [2]
> (and the MIT header) and license (and header) for normalize.css in [3].
>
> Thanks,
> Justin
>
> 1. airflow/www/static/para/parallel.js
> 2.airflow/www/static/bootstrap-toggle.min.css
> 3.airflow/www/static/bootstrap-theme.css
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

[VOTE] Release Airflow 1.8.2 based on Airflow 1.8.2 RC4

[Maxime Beauchemin]

Hello Incubator PMC’ers,

The Apache Airflow community has voted and approved the proposal to release
Apache Airflow 1.8.2 (incubating) based on 1.8.2 Release Candidate 4. We
now kindly request the Incubator PMC members to review and vote on this
incubator release.

Airflow is a platform to programmatically author, schedule and monitor
workflows. Use airflow to author workflows as directed acyclic graphs
(DAGs) of tasks. The airflow scheduler executes your tasks on an array of
workers while following the specified dependencies. Rich command line
utilities make performing complex surgeries on DAGs a snap. The rich user
interface makes it easy to visualize pipelines running in production,
monitor progress, and troubleshoot issues when needed. When workflows are
defined as code, they become more maintainable, versionable, testable, and
collaborative.

Artefacts are available at https://dist.apache.org/repos/
dist/dev/incubator/airflow, public keys are available at
https://dist.apache.org/repos/dist/release/incubator/airflow.

apache-airflow-1.8.2+incubating-source.tar.gz
<https://dist.apache.org/repos/dist/dev/incubator/airflow/1.8.2rc4/apache-airflow-1.8.2+incubating-source.tar.gz>
is
a source release that comes with INSTALL instructions. Along with it, for
convenience, find the binary Python "sdist" as apache-airflow-1.8.2+
incubating-bin.tar.gz
<https://dist.apache.org/repos/dist/dev/incubator/airflow/1.8.2rc4/apache-airflow-1.8.2+incubating-bin.tar.gz>

Vote thread:
http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201708.mbox/browser

Git tag:
https://github.com/apache/incubator-airflow/releases/tag/1.8.2rc4

The vote will be open for at least 72 hours or until necessary number of
votes are reached.

Members please be sure to indicate "(Binding)" with your vote which will
help in tallying the vote(s).

* Here is my +1 (non-binding) *

Cheers,

Maxime Beauchemin

[VOTE] Release Apache Airflow 1.8.2 (incubating)

[Maxime Beauchemin]

Hello Incubator PMC’ers,

The Apache Airflow community has voted and approved the proposal to release
Apache Airflow 1.8.2 (incubating) based on 1.8.2 Release Candidate 2. We
now kindly request the Incubator PMC members to review and vote on this
incubator release. If the vote is successful we will rename release
candidate 2 to final.

Airflow is a platform to programmatically author, schedule and monitor
workflows. Use airflow to author workflows as directed acyclic graphs
(DAGs) of tasks. The airflow scheduler executes your tasks on an array of
workers while following the specified dependencies. Rich command line
utilities make performing complex surgeries on DAGs a snap. The rich user
interface makes it easy to visualize pipelines running in production,
monitor progress, and troubleshoot issues when needed. When workflows are
defined as code, they become more maintainable, versionable, testable, and
collaborative.

The Apache Airflow-1.8.2-incubating release candidate is now available with
the following artifacts for a project vote:

* [VOTE] Thread:*
*http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201706.mbox/%3CCAHEEp7XRRk__hGUMjOCw%2BTW0Gc--78qEewcsAsQBLrv1x6j71w%40mail.gmail.com%3E
*

TODO

*The release candidate(s) to be voted on is available at:*
https://dist.apache.org/repos/dist/dev/incubator/airflow/ or
*https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz
*

*Git branch*
https://github.com/apache/incubator-airflow/tree/v1-8-test or
https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
git;a=tree;h=refs/heads/v1-8-stable;hb=refs/heads/v1-8-test

*Git tag*
*https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;a=shortlog;h=refs/tags/1.8.2rc2
*

*PGP signature*
https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.asc

*MD5/SHA Hashes*
https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.md5
https://dist.apache.org/repos/dist/dev/incubator/airflow/apache-airflow-1.8.2rc2+incubating.tar.gz.sha

*Keys to verify the signature of the release artifacts are available at:*
https://dist.apache.org/repos/dist/release/incubator/airflow/

* RAT License checks*

RAT is executed as part of the CI process (e.g.
https://travis-ci.org/apache/incubator-airflow/builds/226568140) but can
also be run manually by issuing “sh scripts/ci/check-license.sh” from the
top level.

Source code is always included, i.e. there is no binary release.
Compilation and installation will happen by standard Python practices, e.g.
pip install <> or python setup.py install.

The vote will be open for at least 72 hours or until necessary number of
votes are reached.

Members please be sure to indicate "(Binding)" with your vote which will
help in tallying the vote(s).

[ ] +1  approve
[ ] +0  no opinion
[ ] -1  disapprove (and reason why)

*Here is my +1 (non-binding)*

Cheers,

Max

Re: [PROPOSAL] Superset Proposal for Apache Incubator

[Maxime Beauchemin]

Hi Raphael, what kind of numbers are you expecting to see?

Max

On Tue, Apr 25, 2017 at 12:59 PM, Raphael Bircher <rbircherapa...@gmail.com>
wrote:

> Hi all
>
> There is no information about affiliation of the initial committers. The
> only information is, that they are from Airbnb inc and Hortonworks. But
> there are no numbers.
>
> Regards Raphael
>
>
> Am .04.2017, 09:17 Uhr, schrieb Jeff Feng <jeff.f...@gmail.com>:
>
> Thanks John and Max - I have updated the proposal wiki to reflect this
>> update.  It now reads:
>>
>> Source and Intellectual Property Submission Plan
>>
>> Airbnb will submit a Software Grant Agreement (SGA) as Superset joins the
>> incubator. We do not expect any complications for the submission of the
>> Superset code base. Our code is already in Github and there is only a
>> single code base.
>>
>>
>> On Mon, Apr 24, 2017 at 11:32 PM, Maxime Beauchemin <
>> maximebeauche...@gmail.com> wrote:
>>
>> "Airbnb will submit a Software Grant Agreement (SGA) as Superset joins the
>>> incubator."
>>>
>>> Should I add this sentence in the proposal?
>>>
>>> Max
>>>
>>> On Mon, Apr 24, 2017 at 5:48 AM, John D. Ament <johndam...@apache.org>
>>> wrote:
>>>
>>> > I missed this discussion.  In your IP section, you list out:
>>> >
>>> > == Source and Intellectual Property Submission Plan ==
>>> > We do not expect any complications for the submission of the Superset
>>> code
>>> > base.  Our code is already in Github and there is only a single code
>>> base.
>>> >
>>> > This IMHO not clear.  Does Airbnb plan to submit a SGA for Superset, or
>>> > expect that no SGA is required because its Apache licensed?
>>> >
>>> > John
>>> >
>>> > On Sun, Apr 2, 2017 at 4:09 PM Jeff Feng <jeff.f...@airbnb.com.invalid
>>> >
>>> > wrote:
>>> >
>>> > > Dear Apache Incubator Community,
>>> > >
>>> > > We are excited to share our proposal for discussion and feedback for
>>> > > entering Apache Incubation.  Superset is an enterprise-ready web
>>> > > application for data exploration, data visualization and
>>> dashboarding.
>>> > >
>>> > > Our Incubation proposal is at the following Wiki as well as copied in
>>> the
>>> > > email below:
>>> > >
>>> > > https://wiki.apache.org/incubator/SupersetProposal
>>> > >
>>> > > We have an active Superset community including 400+ members and
>>> nearly
>>> > 200
>>> > > topics.  The Google Group can be found below.  We plan to move the
>>> > > discussion to the ASF:
>>> > >
>>> > > https://groups.google.com/forum/#!forum/airbnb_superset
>>> > >
>>> > > Thank you and look forward to the discussion!
>>> > >
>>> > > Jeff, Max & Alanna
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > = Superset =
>>> > >
>>> > > == Abstract ==
>>> > >
>>> > > Superset is an enterprise-ready web application for data exploration,
>>> > data
>>> > > visualization and dashboarding.
>>> > >
>>> > > == Proposal ==
>>> > >
>>> > > Superset is business intelligence (BI) software that helps modern
>>> > > organizations visualize and interact with their data. Superset
>>> enables
>>> > > users explore data from a variety of databases, assemble beautiful
>>> > > dashboards and share their findings.  Superset works neatly with all
>>> > modern
>>> > > SQL-speaking databases, and integrates with Druid.io to provide
>>> > real-time,
>>> > > interactive, blazing fast data access to large datasets.
>>> > >
>>> > > == Background ==
>>> > >
>>> > > Data is mission critical. To succeed in this era, organizations need
>>> to
>>> > > provide low-friction, intuitive and interactive access to data. It is
>>> > > paramount for knowledge workers to be capable of answering their own
>>> > > questions by querying, exploring and visualizing data.
>>> > >
>>> > > The entire business intelligence industry h

Re: [PROPOSAL] Superset Proposal for Apache Incubator

[Maxime Beauchemin]

s that help fill a gap in current
> > solutions for organizations:
> >
> > * Easy, low friction access to data through a simple, web-based data
> > exploration interface.  Composing charts and dashboards are intuitive.
> > Eliminating the need to write code or SQL empowers anyone to use it.
> >
> > * Access to a wide array of rich, interactive data visualization types.
> >
> > * Enterprise-ready: Integration with different authentication mechanisms
> > and granular permissions centered around actions and data access.
> >
> > * Realtime & fast: Superset provides realtime analytics at the speed of
> > thought on very large datasets when integrated with Druid.io.
> >
> > * Broad data access: Consume data out of any SQL-speaking relational
> > database.
> >
> > * Extensible: Can be extended to talk to many noSQL databases like Apache
> > Drill, Elastic Search, and other popular database engines.
> >
> > * Fast loading dashboards with configurable web-scale caching.
> >
> > * Plug-in framework that enables organizations to build custom analytical
> > applications with new UI/UX interfaces.
> >
> > * SQL Lab, a state-of-the-art SQL IDE that empowers SQL-speaking users
> with
> > more flexibility.  SQL Lab integrates with the visualization engine
> > seamlessly.
> >
> > == Initial Goals ==
> >
> > The initial goals of the Superset project are several-fold:
> >
> > Move the existing codebase to Apache and integrate with the Apache
> > development process.
> >
> > Redesign the user interface and interaction model for creating
> > visualizations/dashboards and connecting to data sources
> >
> > Build robust support for security and governance of the tool including
> > popular authorization modules (including Apache Ranger and Apache Sentry)
> > and a more sophisticated permissions system
> >
> > Grow the extensibility of the project both in terms of enhanced
> > connectivity to NoSQL-based data sources and creating a plug-in framework
> > that enables organizations to build custom analytical applications which
> > require a new UI/UX
> >
> > == Current Status ==
> >
> > By many standards, Superset is already a successful open source project.
> As
> > of March 2017, Superset is officially used in production at about a dozen
> > companies, has received contributions from over one hundred contributors
> on
> > Github, 1500+ forks, and 12k+ stars.
> >
> > Sizeable companies like Airbnb, Yahoo! and Hortonworks have made
> > significant contributions, and expressed their commitment to the project.
> > The product is feature complete and has been viable for months. It
> already
> > serves as the main interface for consuming data at many companies of
> > different sizes.
> >
> > While the product is usable, there’s room for improvement across the
> board,
> > starting with providing a smoother user experience around content
> creation,
> > making sure all features work out-of-the-box on more platforms and
> > databases, providing better user training guides and videos, having a
> > predictable release process, and increasing the overall quality of the
> > Superset releases.
> >
> > === Meritocracy ===
> >
> > We plan to invest in supporting a meritocracy. We will discuss the
> > requirements in an open forum. Several companies have expressed interest
> in
> > this project, and we intend to invite additional developers to
> participate.
> > We will encourage and monitor community participation so that privileges
> > can be extended to those that contribute.
> >
> > === Community ===
> >
> > The need for an enterprise-ready data visualization and exploration
> > platform in the open source community is tremendous.  While Superset is
> > fairly well known, recognized and used within the Druid.io community,
> > adoption is currently limited outside of that niche. There is a huge
> > opportunity to grow the community to hundreds if not thousands of
> > organizations, and we are hoping that embracing “the Apache way” will
> > accelerate the growth of our community.
> >
> > We have already been active at seeking and inviting contributions, and
> are
> > planning to scale the project by investing time and growing the support
> > structure to grow the community.
> >
> > === Core Developers ===
> >
> > The initial committers for Superset include experienced full stack,
> > front-end and data engineers:
> >
> > * Maxime Beauchemin 

Re: [PROPOSAL] Superset Proposal for Apache Incubator

[Maxime Beauchemin]

Hi Jean-Baptiste,

We are indeed looking for more mentors.

Should I update the wiki and replace all references to PMC by PPMC?

Thanks,

Max

On Wed, Apr 12, 2017 at 12:51 PM, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:

> Hi Maxime,
>
> The proposal looks interesting.
>
> Just a note,  it's PPMC (not PMC) during incubation.
>
> Are you seeking for other mentor (I see you only have one mentor and one
> champion for now) ?
>
> Regards
> JB
>
>
> On 04/12/2017 09:41 PM, Maxime Beauchemin wrote:
>
>> Hi all,
>>
>> We would love feedback on the proposal. Do the veterans on this mailing
>> list think that the proposal is ready for a vote!?
>>
>> Thanks,
>>
>> Max
>>
>> On Tue, Apr 4, 2017 at 5:26 PM, Luke Han <luke...@gmail.com> wrote:
>>
>> Hi Jeff,
>>> This is great project which have been mentioned many times in
>>> community. It looks cool and fun for data works.
>>>
>>> Thanks to proposal Superset to be Apache Incubator Project, please
>>> let
>>> me know if there's anything I could help.
>>>
>>> Thanks.
>>> Luke
>>>
>>>
>>> Best Regards!
>>> -
>>>
>>> Luke Han
>>>
>>> On Sun, Apr 2, 2017 at 7:45 AM, Jeff Feng <jeff.f...@airbnb.com.invalid>
>>> wrote:
>>>
>>> Dear Apache Incubator Community,
>>>>
>>>> We are excited to share our proposal for discussion and feedback for
>>>> entering Apache Incubation.  Superset is an enterprise-ready web
>>>> application for data exploration, data visualization and dashboarding.
>>>>
>>>> Our Incubation proposal is at the following Wiki as well as copied in
>>>> the
>>>> email below:
>>>>
>>>> https://wiki.apache.org/incubator/SupersetProposal
>>>>
>>>> We have an active Superset community including 400+ members and nearly
>>>>
>>> 200
>>>
>>>> topics.  The Google Group can be found below.  We plan to move the
>>>> discussion to the ASF:
>>>>
>>>> https://groups.google.com/forum/#!forum/airbnb_superset
>>>>
>>>> Thank you and look forward to the discussion!
>>>>
>>>> Jeff, Max & Alanna
>>>>
>>>>
>>>>
>>>>
>>>> = Superset =
>>>>
>>>> == Abstract ==
>>>>
>>>> Superset is an enterprise-ready web application for data exploration,
>>>>
>>> data
>>>
>>>> visualization and dashboarding.
>>>>
>>>> == Proposal ==
>>>>
>>>> Superset is business intelligence (BI) software that helps modern
>>>> organizations visualize and interact with their data. Superset enables
>>>> users explore data from a variety of databases, assemble beautiful
>>>> dashboards and share their findings.  Superset works neatly with all
>>>>
>>> modern
>>>
>>>> SQL-speaking databases, and integrates with Druid.io to provide
>>>>
>>> real-time,
>>>
>>>> interactive, blazing fast data access to large datasets.
>>>>
>>>> == Background ==
>>>>
>>>> Data is mission critical. To succeed in this era, organizations need to
>>>> provide low-friction, intuitive and interactive access to data. It is
>>>> paramount for knowledge workers to be capable of answering their own
>>>> questions by querying, exploring and visualizing data.
>>>>
>>>> The entire business intelligence industry has pivoted from a model of
>>>> centralized top-down platforms driven by IT organizations to
>>>> self-service
>>>> analytics and agile workflows by any user.  This shift unblocks
>>>>
>>> centralized
>>>
>>>> service bottlenecks for creating data visualizations while also creating
>>>>
>>> an
>>>
>>>> environment that is iterative and fast-moving.  This means that business
>>>> intelligence software must also be easy and delightful to use.
>>>> Self-service analytics doesn’t mean that admin and governance features
>>>>
>>> are
>>>
>>>> not needed.
>>>>
>>>> Modern BI tools provide fine-grain access controls and auditing
>>>> capabilities to understand how data is being used.  Superset i

Re: [PROPOSAL] Superset Proposal for Apache Incubator

[Maxime Beauchemin]

t; > * Easy, low friction access to data through a simple, web-based data
> > exploration interface.  Composing charts and dashboards are intuitive.
> > Eliminating the need to write code or SQL empowers anyone to use it.
> >
> > * Access to a wide array of rich, interactive data visualization types.
> >
> > * Enterprise-ready: Integration with different authentication mechanisms
> > and granular permissions centered around actions and data access.
> >
> > * Realtime & fast: Superset provides realtime analytics at the speed of
> > thought on very large datasets when integrated with Druid.io.
> >
> > * Broad data access: Consume data out of any SQL-speaking relational
> > database.
> >
> > * Extensible: Can be extended to talk to many noSQL databases like Apache
> > Drill, Elastic Search, and other popular database engines.
> >
> > * Fast loading dashboards with configurable web-scale caching.
> >
> > * Plug-in framework that enables organizations to build custom analytical
> > applications with new UI/UX interfaces.
> >
> > * SQL Lab, a state-of-the-art SQL IDE that empowers SQL-speaking users
> with
> > more flexibility.  SQL Lab integrates with the visualization engine
> > seamlessly.
> >
> > == Initial Goals ==
> >
> > The initial goals of the Superset project are several-fold:
> >
> > Move the existing codebase to Apache and integrate with the Apache
> > development process.
> >
> > Redesign the user interface and interaction model for creating
> > visualizations/dashboards and connecting to data sources
> >
> > Build robust support for security and governance of the tool including
> > popular authorization modules (including Apache Ranger and Apache Sentry)
> > and a more sophisticated permissions system
> >
> > Grow the extensibility of the project both in terms of enhanced
> > connectivity to NoSQL-based data sources and creating a plug-in framework
> > that enables organizations to build custom analytical applications which
> > require a new UI/UX
> >
> > == Current Status ==
> >
> > By many standards, Superset is already a successful open source project.
> As
> > of March 2017, Superset is officially used in production at about a dozen
> > companies, has received contributions from over one hundred contributors
> on
> > Github, 1500+ forks, and 12k+ stars.
> >
> > Sizeable companies like Airbnb, Yahoo! and Hortonworks have made
> > significant contributions, and expressed their commitment to the project.
> > The product is feature complete and has been viable for months. It
> already
> > serves as the main interface for consuming data at many companies of
> > different sizes.
> >
> > While the product is usable, there’s room for improvement across the
> board,
> > starting with providing a smoother user experience around content
> creation,
> > making sure all features work out-of-the-box on more platforms and
> > databases, providing better user training guides and videos, having a
> > predictable release process, and increasing the overall quality of the
> > Superset releases.
> >
> > === Meritocracy ===
> >
> > We plan to invest in supporting a meritocracy. We will discuss the
> > requirements in an open forum. Several companies have expressed interest
> in
> > this project, and we intend to invite additional developers to
> participate.
> > We will encourage and monitor community participation so that privileges
> > can be extended to those that contribute.
> >
> > === Community ===
> >
> > The need for an enterprise-ready data visualization and exploration
> > platform in the open source community is tremendous.  While Superset is
> > fairly well known, recognized and used within the Druid.io community,
> > adoption is currently limited outside of that niche. There is a huge
> > opportunity to grow the community to hundreds if not thousands of
> > organizations, and we are hoping that embracing “the Apache way” will
> > accelerate the growth of our community.
> >
> > We have already been active at seeking and inviting contributions, and
> are
> > planning to scale the project by investing time and growing the support
> > structure to grow the community.
> >
> > === Core Developers ===
> >
> > The initial committers for Superset include experienced full stack,
> > front-end and data engineers:
> >
> > * Maxime Beauchemin (Airbnb)
> >
> > * Alanna Scott (Airbnb)
> >
> > * Bogdan Kyryli

requesting write access for "maximebeauchemin" on wiki.apache.org/incubator

[Maxime Beauchemin]

See subject ^^^

I'd like to submit a proposal to the incubator and I need wiki access to
proceed.

Thanks,

Max

Re: [VOTE] Release Apache Airflow 1.8.0 (incubating)

[Maxime Beauchemin]

+1 (non-binding)

On Thu, Mar 16, 2017 at 9:59 AM, Jeremiah Lowin  wrote:

> +1 (non-binding)
>
>
> On Thu, Mar 16, 2017 at 12:56 PM Arthur Wiedmer  wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Arthur
> >
> > On Thu, Mar 16, 2017 at 9:42 AM, Chris Riccomini 
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > On Thu, Mar 16, 2017 at 9:32 AM, Bolke de Bruin 
> > wrote:
> > >
> > > > Hello Incubator PMC’ers,
> > > >
> > > > The Apache Airflow community has voted and approved the proposal to
> > > > release Apache Airflow 1.8.0 (incubating) based on 1.8.0 Release
> > > Candidate
> > > > 5. We now kindly request the Incubator PMC members to review and vote
> > on
> > > > this incubator release. If the vote is successful we will rename
> > release
> > > > candidate 4 to final.
> > > >
> > > > Airflow is a platform to programmatically author, schedule and
> monitor
> > > > workflows. Use airflow to author workflows as directed acyclic graphs
> > > > (DAGs) of tasks. The airflow scheduler executes your tasks on an
> array
> > of
> > > > workers while following the specified dependencies. Rich command line
> > > > utilities make performing complex surgeries on DAGs a snap. The rich
> > user
> > > > interface makes it easy to visualize pipelines running in production,
> > > > monitor progress, and troubleshoot issues when needed. When workflows
> > are
> > > > defined as code, they become more maintainable, versionable,
> testable,
> > > and
> > > > collaborative.
> > > >
> > > > The Apache Airflow-1.8.0-incubating release candidate is now
> available
> > > > with the following artefacts for a project vote:
> > > >
> > > > * [VOTE] Thread:*
> > > > http://mail-archives.apache.org/mod_mbox/incubator-
> > > > airflow-dev/201703.mbox/%3cB1833A3A-05FB-4112-B395-
> > > > 135caf930...@gmail.com%3e  > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> > > 3CB1833A3A-05FB-4112-B395-
> > > > 135caf930...@gmail.com%3E>
> > > >
> > > > *[RESULT][VOTE] Thread:*
> > > > http://mail-archives.apache.org/mod_mbox/incubator-
> > > > airflow-dev/201703.mbox/%3c59BC8C2B-12E2-4DE3-9555-
> > > > b2273660a...@gmail.com%3e  > > > org/mod_mbox/incubator-airflow-dev/201703.mbox/%
> > > 3c59BC8C2B-12E2-4DE3-9555-
> > > > b2273660a...@gmail.com%3e>
> > > >
> > > > *The release candidate(s) to be voted on is available at:*
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/ <
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/> or
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > > airflow-1.8.0rc5+apache.incubating.tar.gz  > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > apache.incubating.tar.gz
> > > > >
> > > >
> > > > *Git branch*
> > > > https://github.com/apache/incubator-airflow/tree/v1-8-stable <
> > > > https://github.com/apache/incubator-airflow/tree/v1-8-stable> or
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> > > > git;a=tree;h=refs/heads/v1-8-stable;hb=refs/heads/v1-8-stable <
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> > > > airflow.git;a=tree;h=refs/heads/v1-8-stable;hb=refs/
> heads/v1-8-stable>
> > > >
> > > > *Git tag*
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.
> > > > git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2 <
> > > > https://git-wip-us.apache.org/repos/asf?p=incubator-
> > > > airflow.git;a=shortlog;h=f4760c320a29be62469799355e76efa42d0b6bb2>
> > > >
> > > > PGP signature
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.asc <
> > https://dist.apache.org/
> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > > apache.incubating.tar.gz.asc>
> > > >
> > > > MD5/SHA Hashes:
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.md5 <
> > https://dist.apache.org/
> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > > apache.incubating.tar.gz.md5>
> > > > https://dist.apache.org/repos/dist/dev/incubator/airflow/
> > > > airflow-1.8.0rc5+apache.incubating.tar.gz.sha <
> > https://dist.apache.org/
> > > > repos/dist/dev/incubator/airflow/airflow-1.8.0rc5+
> > > > apache.incubating.tar.gz.sha>
> > > >
> > > > *Keys to verify the signature of the release artifacts are available
> > at:*
> > > > https://dist.apache.org/repos/dist/release/incubator/airflow/ <
> > > > https://dist.apache.org/repos/dist/release/incubator/airflow/>
> > > >
> > > > * RAT License checks*
> > > >
> > > > RAT is executed as part of the CI process (e.g.
> > > > https://travis-ci.org/apache/incubator-airflow/builds/203106493 <
> > > > https://travis-ci.org/apache/incubator-airflow/builds/203106493>)
> but
> > > can
> > > > also be run manually by issuing “sh scripts/ci/check-license.sh” from

Re: Showcase your project at ApacheCON: consider Podling Shark Tank

[Maxime Beauchemin]

Hi Roman,

Actually I have to cancel, I won't be able to make it to Vancouver next
week.

I'm hoping I'll be able to make it next time around!

Thanks, and sorry about the last minute flip-flopping...

Max

On Sun, May 1, 2016 at 12:28 PM, Roman Shaposhnik  wrote:

> Hi!
>
> thank you all for an amazing response! At this point
> we've got 9-10 entires which is great and makes me
> think that perhaps we could spill some of the Big Data
> related podlings into the lighting talks slot of Big Data
> ApacheCON on Tuesday, May 10 5:10pm - 5:50pm
> http://apachebigdata2016.sched.org/event/6M1u/lightning-talks
>
> If your polding happens to be in Big Data space and you
> can present on Tue, please email me ASAP so I can make
> sure that both days can comfortably fit all the speakers.
>
> The format will remain the same!
>
> Thanks,
> Roman.
>
> On Mon, Apr 25, 2016 at 1:27 PM, Roman Shaposhnik  wrote:
> > Hi!
> >
> > I apologize for the wide distribution, but since my email to general@
> > didn't seem to have reached all of the podling communities, I took
> > the liberty of direct email. Here's the deal:
> >
> > If you are (or anybody you know who's passionate about your project is)
> > going to travel to Vancouver for ApacheCON we've got an awesome
> > opportunity for you to showcase your project. Even if you don't have
> > talks scheduled in the regular program, consider doing a lighting talk
> > at Podling Shark Tank:
> >  https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank
> >
> > You've got nothing to lose (in fact, the opposite: you're likely to get
> > a prize!) and you will get a chance to receive feedback that might
> > actually help you grow your community and ultimately graduate to the
> > TLP status. Given our awesome panel of judges:
> >  * Jim Jagielski
> >  * Shane Curcuru
> >  * Milind Bhandarkar
> > We guarantee this to be a fun and useful event for your community!
> >
> > Please sign up on the wiki ASAP. The time is running out!
> >
> > Thanks,
> > Roman.
> >
> > P.S. If you have *any* questions whatsoever, but especially if you have
> > questions on logistics please email me directly.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Showcase your project at ApacheCON: consider Podling Shark Tank

[Maxime Beauchemin]

I just added Airflow to the list and I'm looking forward to meet members of
the Apache community!

Max

On Wed, Apr 27, 2016 at 6:05 PM, DO YUNG YOON  wrote:

> Roam, Can you please  also add me. DoyungYoon.
> I would like to add Apache S2Graph (incubating) to the list. Thanks.
>
>
> On Tue, Apr 26, 2016 at 6:35 PM Peter Scanlon 
> wrote:
>
> > Roman. Would you also add me please. PeterScanlon.  I would like to add
> > Apache Milagro (incubating) to the list to talks.   Thank you.
> >
> > > On 26 Apr 2016, at 03:05, Roman Shaposhnik 
> wrote:
> > >
> > > I've just added AdamBordelon wiki ID to the access page.
> > >
> > > Thanks,
> > > Roman.
> > >
> > >> On Mon, Apr 25, 2016 at 4:39 PM, Adam Bordelon 
> > wrote:
> > >> Can somebody please grant me (Apache/wiki id 'me') write access to
> > >> https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank ?
> > >> I'd like to add myself and Mohit to the list to pitch Myriad
> > >>
> > >> -Adam-
> > >> me@
> > >>
> > >>> On Mon, Apr 25, 2016 at 1:27 PM, Roman Shaposhnik 
> > wrote:
> > >>>
> > >>> Hi!
> > >>>
> > >>> I apologize for the wide distribution, but since my email to general@
> > >>> didn't seem to have reached all of the podling communities, I took
> > >>> the liberty of direct email. Here's the deal:
> > >>>
> > >>> If you are (or anybody you know who's passionate about your project
> is)
> > >>> going to travel to Vancouver for ApacheCON we've got an awesome
> > >>> opportunity for you to showcase your project. Even if you don't have
> > >>> talks scheduled in the regular program, consider doing a lighting
> talk
> > >>> at Podling Shark Tank:
> > >>> https://wiki.apache.org/apachecon/ACEU16PodlingSharkTank
> > >>>
> > >>> You've got nothing to lose (in fact, the opposite: you're likely to
> get
> > >>> a prize!) and you will get a chance to receive feedback that might
> > >>> actually help you grow your community and ultimately graduate to the
> > >>> TLP status. Given our awesome panel of judges:
> > >>> * Jim Jagielski
> > >>> * Shane Curcuru
> > >>> * Milind Bhandarkar
> > >>> We guarantee this to be a fun and useful event for your community!
> > >>>
> > >>> Please sign up on the wiki ASAP. The time is running out!
> > >>>
> > >>> Thanks,
> > >>> Roman.
> > >>>
> > >>> P.S. If you have *any* questions whatsoever, but especially if you
> have
> > >>> questions on logistics please email me directly.
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Accept Airflow into the Incubator

[Maxime Beauchemin]

+1 (non-binding)

Max

On Thu, Mar 24, 2016 at 11:07 PM, Hitesh Shah <hit...@apache.org> wrote:

> +1 (binding)
>
> — HItesh
>
> On Mar 24, 2016, at 8:00 PM, Siddharth Anand <san...@agari.com.INVALID>
> wrote:
>
> > Following the discussion earlier:
> >https://s.apache.org/AirflowDiscussion
> >
> > I would like to call a VOTE for accepting Airflow as a new incubator
> project.
> >
> > The proposal is available at:
> https://wiki.apache.org/incubator/AirflowProposal
> >
> > The proposal is also included at the bottom of this email.
> >
> > Vote is open until at least Tues, 29 March 2016, 23:59:00 PDT
> > [ ] +1 accept Airflow into the Apache Incubator
> > [ ] ±0
> > [ ] -1 because...
> >
> > +1 (non-binding)
> >
> > Thanks,
> > -s (Sid)
> >
> >
> > == Abstract ==
> >
> > Airflow is a workflow automation and scheduling system that can be
> > used to author and manage data pipelines.
> >
> > == Proposal ==
> >
> > Airflow provides a system for authoring and managing workflows a.k.a.
> > data pipelines a.k.a. DAGs (Directed Acyclic Graphs). The developer
> > authors DAGs in Python using an Airflow-provided framework. He/She
> > then executes the DAG using Airflow’s scheduler or registers the DAG
> > for event-based execution. A web-based UI provides the developer with
> > a range of options for managing and viewing his/her data pipelines.
> > Background
> >
> > Airflow was developed at Airbnb to enable easier authorship and
> > management of DAGs than were possible with existing solutions such as
> > Oozie and Azkaban. For starters, both Oozie and Azkaban rely on one or
> > more XML or property files to be bundled together to define a
> > workflow. This separation of code and config can present a challenge
> > to understanding the DAG - in Azkaban, a DAG’s structure is reflected
> > by its file system tree and one can find himself/herself traversing
> > the file system when inspecting or changing the structure of the DAG.
> > Airflow workflows, on the other hand, are simply and elegantly defined
> > in Python code, often a single file. Airflow merges the powerful
> > Web-based management aspects of projects like Azkaban and Oozie with
> > the simplicity and elegance of defining workflows in Python. Airflow,
> > less than a year old in terms of its Open Source launch, is currently
> > used in production environments in more than 30 companies and boasts
> > an active contributor list of more than 100 developers, the vast
> > majority of which (>95%) are outside of Airbnb.
> >
> > We would like to share it with the ASF and begin developing a
> > community of developers and users within Apache.
> >
> > == Rationale ==
> >
> > Many organizations (>30) already benefit from running Airflow to
> > manage data pipelines. Our 100+ contributors continue to provide
> > integrations with 3rd party systems through the implementation of new
> > hooks and operators, both of which are used in defining the tasks that
> > compose workflows.
> >
> > == Current Status ==
> >
> > === Meritocracy ===
> >
> > Our intent with this incubator proposal is to start building a diverse
> > developer community around Airflow following the Apache meritocracy
> > model. Since Airflow was open-sourced in mid-2015, we have had fast
> > adoption and contributions by multiple organizations the world over.
> > We plan to continue to support new contributors and we will work to
> > actively promote those who contribute significantly to the project to
> > committers.
> >
> > === Community ===
> >
> > Airflow is currently being used in over 30 companies. We hope to
> > extend our contributor base significantly and invite all those who are
> > interested in building large-scale distributed systems to participate.
> >
> > === Core Developers ===
> >
> > Airflow is currently being developed by four engineers: Maxime
> > Beauchemin, Siddharth Anand, Bolke de Bruin, and Chris Riccomini.
> > Chris is a member of the Apache Samza PMC and a contributor to various
> > Apache projects, including Apache Kafka and Apache YARN. Maxime,
> > Siddharth, and Bolke have contributed to Airflow.
> >
> > === Alignment ===
> > The ASF is the natural choice to host the Airflow project as its goal
> > of encouraging community-driven open-source projects fits with our
> > vision for Airflow.
> >
> > == Known Risks ==
> >
> > === Orphaned Produ