Hi,
Forwarding from the superset dev list where I was asking them what was going on
with their releases. [5]
> We have yet to come up with our first Apache release. We're having issues
> wrapping our heads around how to come up with our LICENSE file given the
> number of dependencies we have on
Hi,
> I started doing some work towards building a LICENSE.txt dynamically
> out of NPM and Pypi metadata. Superset's dependency tree is huge. It looks
> like this may need a fair amount of investigation and perhaps revising some
> dependencies that we can't have, or making some deps optional.
Hi,
> For context, Superset ships as a Python [Flask] backend and a Javascript
> frontend web app. Currently we distribute a package on Pypi that contains
> minified Javascript bundles.
Minified javascript may not be considered source code, which an Apache release
must contain.
> From my
Hi,
The incubator PMC would appreciated if you could complete the podling report on
time. It takes time to prepare the incubator report, have your mentors sign off
the report and for the board to review it, in order for all that to happen the
report is due in the next two days.
Thanks,
Justin
Hi,
It might be useful for the project to fill in [1] and see what they would need
to do in order to get to a state where the project could be considered for
graduation. Currently, and I could be wrong, I think this project has a long
way to go and it may not realise that. While this is not a
Hi,
Sorry ignore this as it was sent in error.
Thanks,
Justin
Hi,
Release policy [1] states:
"Projects MUST direct outsiders towards official releases rather than raw
source repositories, nightly builds, snapshots, release candidates, or any
other similar packages."
In this context an official release is an ASF source release vetted (usually by
voting)
Hi,
Sometimes images do make it through but the default is that they generally
don't. This can be changed by asking Infra.
You also note a comment on the most recent board report which also includes
similar advice.
"Please let superset know that their lists can be configured to allow image
Hi,
At the ASF projects release source code, a binary connivance release has to
match what is contained in that source release. [4][5] So you need to make a
source package that complies with ASF release policy [1][2][3] and vote on
that.Only then can you can then optionally release a binary
Hi,
> We do have a healthy flow of discussion at http://apache-superset.slack.com
> that anyone can join from our project page at
> https://github.com/apache/incubator-superset. My impression is that this
> has been a more effective forum for communication than the dev@ list.
While it's fine
Hi,
Projects at the ASF release source code. You make a release candidate that
complies with ASF release policy, vote on it and release it on ASF
infrastructure. You can optionally make a binary convenance release at the same
time.That binary release must match what's in the source release.
Hi,
Sorry for my double email there, I though the first one has not been sent, just
treat them as a single email as their contents are similar.
Thanks,
Justin
Hi,
> Justin - thanks for the reminder on bringing back discussion from the
> bi-weekly meetings back to the mailing list. It is sincerely
> unintentional.
The best solution would be to not have them and move all discussion to the
mailing list, that way all of the community curl be involved
Hi,
Thanks for submitting the report on time it does however raise a few other
questions.
Regards the email list not supporting images, it easy enough to link to an
image in email as a workaround and as you point out speaking to Infra may also
help.
On communication I still don't see any
Hi,
I notice you are consider using a tool (not rat) to bulk add the headers. Take
care that 3rd party headers are not removed and ASF headers are only added to
files that require it.
Thanks,
Justin
Hi,
> Thanks for the thoughtful notes here. I like the idea of sticking to
> release candidate or "devN" packages on pypi for this, personally I think
> that's acceptable.
I suggest you reread the links I posted above, making release candidates
available to the general public is not line line
Hi,
> https://www.linuxfoundation.org/press-release/2018/12/the-linux-foundation-to-launch-new-tooling-project-to-improve-open-source-compliance/
It's based on SPDX [1] and I'm guessing t's unlikely that all that 3rd party JS
files have SPDX IDs. In other word you need to create them which is
Hi,
> I have a question about "companion" convenience release. So say we make a
> source release and it gets voted on approved, signed and properly released.
> Now if we want to make a companion release to Pypi, how should we go about
> that?
There are a number of ways of dealing with it, what
Hi,
It's good to see that unapproved releases were discussed, however either the
notes are not extensive enough or perhaps the major point was missed i.e. in
that the PPMC needs to bless each release, usually this is done by voting on
it. [2] That may of been discussed but hard to tell from
Hi,
A better link on what's needed for a podling website. [1]
Thanks,
Justin
1. https://incubator.apache.org/guides/sites.html
Hi,
> I think we have most of what's required of podling websites already on the
> existing site.
I think a little more may be needed. [1]
> About Slack, I'd say most of the conversations are taking place on Github
> not Slack. I think other ASF projects use Slack as well.
Why aren't those
Hi,
> I have found many of our JS lib have unclear licenses. Strings like "MIT or
> GPL"
That probably OK as it's dual licensed and you can pick the most favourable one.
> or "BSD*" which when digging means something like "BSD with LLVM clause".
That may be an issue but we would need to look
Hi,
It's not the tag (so much) that's the issue it that it's marked as a release
and publicly visible and available for download on this page. [1] There is no
indication to anyone coming along and viewing that page that this is not a
release checked by the PPMC and IPMC.
Thanks,
Justin
1.
HI,
> We need binding votes from the committers... 3 being the minimum. Its common
> to make it clear that you are either voting binding or non binding. Binding
> votes can only be cast by committers.
Actually only the PMC votes are binding, committer votes are not binding on
releases. In the
Hi,
Anyone? It would be a shame for superset to start missing reports (which are
now overdue) given the recent progress.
Thanks,
Justin
Hi,
Thanks for submitting the report.
You just need to use your Apache credentials to log into confluence.
Next time can you please use the standard report text/headers and don’t modify
the formatting.
Thanks,
Justin
Hi,
Looks like a question about branding has been missed woful be good if you could
answer that. The template changes from time to time so alway best to grab the
bare bones one from the latest incubator report.
Thanks,
Justin
Hi,
> Thanks so much Justin! Quick confirmation that the update has been made.
Sorry I'm not seeing that update. [1]
Thanks,
Justin
1. https://cwiki.apache.org/confluence/display/INCUBATOR/December2019
HI,
> @Mentors -
> I am logged in, with an Apache email and do not have edit privileges for our
> Podling report. Is there something else I need to do in order to be able to
> Edit or is it just limited to committers or PMC members?
All committers and IPMC members can edit that page.
Thanks,
Hi,
Just a friendly reminder that the report is due on the 4th. Is the report being
worked on?
Thanks,
Justin
Hi,
Some podlings (BCCed) are not formatting the reports correctly. Please do not
remove or change the existing formatting when editing your report in the
incubator report.
In particular do not change the formatting of the sign-off area, we have tools
that work off this and they depend on it
31 matches
Mail list logo
