On 12/6/15, 2:43 PM, "Justin Mclean" <justinmcl...@me.com> wrote:
>Hi, > >> Christophe Herreman, who also happens to be on our PMC, and one of the >> major contributors to AS3Commons, is interested in having Apache Flex >> adopt the AS3Commons code. I think this would be a good move for Apache >> Flex because we use some of AS3Commons in the Installer already so it >> would be good to have this code in a place we can control, especially if >> we want to see how much of it will work in FlexJS. > >I assume an IP review would still be required, while the risk is low I >think it’s still a concern. How do we work out if someone has for >instanced copied some GPL or other license code in there? Looking at the >code bases there about 50 different copyright owners in the code (some >variations of the same) including Adobe. The Adobe stuff may be MPL >licensed? There's also some MIT and possibly other licensed code in there. Yes, we should run some sort of an IP review. I believe we won't be strict about the SGA line-item. IMO, it is good to know what there might be issues in the dependencies. It is interesting that initial code drops in a new podling can hit the repo with IP issues and get clean up after the fact, but after that all other code drops need to be reviewed first. It would be easier to grab every repo and clean it later, but since most of them are on GitHub, I suppose we could just IP review each repo as we take it in. I don't think we need to do it all at once. > >> So, first we should discuss whether we want to adopt AS3Commons > >Do we have anyone who is willing to be active maintainers of this code? >(Or at least more active than it is currently). Is any existing committer >willing to put up a friendly notice redirecting users and devs to it's >new home? What committers are willing to clean up the code base and >integrate it into the SDK including looking into updating license and >notice? Yeah, well I'd prefer that we don't integrate it into the SDK but we need to understand the entire dependencies picture before deciding it can live on its own. I'd like to know more about what the Maven packages are for this code base. If it is one Maven package per repo, we might just start with ones we are most interested in and release each repo on its own schedule instead of one huge release. I'm mostly interested in the zip code which is not on GitHub as we use it in the Installer. -Alex
