Here’s another idea along these lines: What about a Github repository for “Flex Support” or “Flex Extensions”? We could build installers and host them there without “official blessings”. Any non Apache license compliant extensions (such as flexmojo) might go there as well.
This might just be a workable solution and side-step this whole issue. Would it be okay to link to such a repository on the Flex download page with a disclaimer that the installers are not blessed by Apache? Harbs On Oct 23, 2014, at 12:34 PM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > Hi, > > On Thu, Oct 23, 2014 at 11:14 AM, Harbs <harbs.li...@gmail.com> wrote: >> JBurg can be installed manually by the end user, but the Flex community has >> tried to simplify >> the setup process by downloading JBurg by an installer script... > > The easiest might be to host the Flex installer outside of Apache > Flex, as a separate project where its contributors are free to do > whatever. This would make it clearer that the installer is not an > Apache thing, and that it might not offer the same level of confidence > that our source releases, not the same clean "nothing worse than > Apache license inside" guarantee. > > We used to have http://community.apache.org/apache-extras/faq.html for > such things but AFAIK people cannot host downloads there anymore so it > might not be useful here. But the idea is the same - cleanly separate > the Apache project from extras that might be useful to some people, > but don't give the same guarantees. > > -Bertrand > > --------------------------------------------------------------------- > 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
