One of the main challenge/blocker to date has been around crafting our LICENSE.txt file, and keeping it up to date as our JS dependency tree is massive, deep and very dynamic. It seemed like we have to do this programmatically. I started writing a script to do so a little while back and was looking for more mentor guidance as to how to handle the special cases. There are many libs under "MIT*" or "BSD*" where the "*" needs to be investigated and personally I'm not qualified to know whether "MIT with LLVM clause" is ok or not... So while I can commit time to this, I can only raise questions in the process. Also there have been questions around convenience releases and whether it's ok to have grey-zone license if they're fetched at build time. We need mentor and legal guidance here. https://github.com/apache/incubator-superset/pull/5801
I also have filled in the "The Apache Project Maturity Checklist" last month in the GH issue bellow, and it seems like we're doing fairly well: https://github.com/apache/incubator-superset/issues/5951 I believe that the issues around having discussions off-lists can be addressed easily, but we need to clarify what's acceptable or not. Is Slack ok? Are in-person operational community meetings ok if everyone is welcomed to attend, minutes are posted and no important decisions are taken? Personally I'm committed to align with "the Apache Way" and do a significant portion of the work that we have to do in order to graduate, but I would love support and help from committers and mentors to make it happen. Max On Thu, Oct 25, 2018 at 3:43 PM Jason Smith <jason_sm...@mckinsey.com> wrote: > I worked on releasing Apache CouchDB a few years back. > > > I would like to get involved in making a Superset release. I think > Superset is similar to CouchDB in that it only works correctly when > bundling large subcomponents, such as the JavaScript runtime and lots of > JavaScript code. > > ________________________________ > From: Alan Gates <alanfga...@gmail.com> > Sent: Thursday, October 25, 2018 5:40:15 PM > To: d...@superset.apache.org > Subject: [EXT]Helping Superset grow into an Apache community > > All, there are concerns in the Incubator that Superset is not learning the > Apache Way as it should. > It is still doing non-Apache releases. Some have pointed out evidence that > decisions may be being taken off list and corporate allegiance may be > determining peoples choices. If Superset is going to move through the > Incubator and eventually graduate it needs to begin addressing these issues > immediately, as the Incubator PMC is loosing patience. Alternatively, > maybe Apache isn't the best home for Superset, and if so, that's ok. > > The purpose of this email is to start a discussion around what the > community needs to do to address these issues. > > Alan. > > +========================================================================+ > 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. > +========================================================================+ >
