Hi!

I am an Apache CouchDB committer (active some years ago). That was also a core 
primary system but with all-but-essential dependencies, e.g. SpiderMonkey JVM, 
and also React for the GUI.


I recommend looking at how their release process works. I'm happy to help how I 
can!


________________________________
From: Maxime Beauchemin <[email protected]>
Sent: Wednesday, September 5, 2018 12:42:41 PM
To: [email protected]
Cc: [email protected]
Subject: [EXT]Re: Our first Superset Apache release

Justin thanks for the input.

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. The product can't really work do much without
the Javascript, only the "data access layer" works, but that's a very small
portion of what Superset has to offer.

>From my understanding we can't really ship just our code or binaries and
have people fetch the rest of the deps and build/install it, can we? If
that was the case, the Superset Apache release could really just be a
tarball with source and and an installation script that would fetch all the
deps and build the JS. Would that work?

Max

On Tue, Sep 4, 2018 at 2:01 PM Justin Mclean <[email protected]>
wrote:

> 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.
>
> Remember it's not dependancies that are mentioned in LICENSE only what is
> bundled within the release, I notice some build tool and the like in that
> list that probably don't need to be mentioned. [1] Note as well that the
> LICENSE may be different for the source release and the convenience binary
> release.
>
> Thanks,
> Justin
>
> 1. 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.apache.org_dev_licensing-2Dhowto.html-23guiding-2Dprinciple&d=DwIBaQ&c=yIH1_-b1hO27QV_BdDph9suDL0Jq0WcgndLmIuQXoms&r=v5OT9PpHbzZyYVJ71cjuc9T3ru5rnKvhOFpmVKJtxmU&m=yoDuiGiL03RZ5-cG7r6GoMGpoQsI37H6wMCOIqEbhNg&s=qZeMa06LW9HpkrL7Ey9lOL2SR1tl0D-NcTISwHb_5hk&e=

+========================================================================+
This email is confidential and may be privileged. If you have received it
in error, please notify us immediately and then delete it.  Please do not
copy it, disclose its contents or use it for any purpose.
+========================================================================+

Reply via email to