But if you add them after the fact who vets for them? I imagine there must still be some checks to see that the binary was produced from a voted source and that the binary works or something. This means some sort of (P)PMC vote the least to me. Or do we handle this on private@?
--emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Thu, Dec 27, 2018 at 1:58 AM Daniel Gruno <humbed...@apache.org> wrote: > > On 12/26/18 11:56 AM, Emilian Bold wrote: > >>> 1. If we were to create an installer for installing Apache NetBeans (i.e., > >>> no JDK included, simply for installing NetBeans), could we distribute that > >>> from our Apache NetBeans site? > >> > >> See http://www.apache.org/legal/release-policy.html#compiled-packages > >> You can, with various notices and caveats in mind, create convenience > >> binaries, but the project cannot vote on them for obvious reasons, nor > >> do they count as an official release. There are signing options > >> available for packages as well. > > > > I read there that "binary/bytecode packages MAY be distributed > > alongside official Apache releases". So the packages must also be > > available on Apache infrastructure. > > > > It doesn't mention if we can publish binaries after a release. For > > example, we have another thread about publishing Ubuntu Snap packages, > > but those binaries were not part of the release email vote thread, nor > > are they on dist.apache.org. If we can't vote on new binaries, do we > > need another release to publish new binaries? > > Convenience binaries are not part of the official project release, you > could add them whenever, provided you remember to properly let people > know that they are not what we consider official releases. > > the TL;DR of this discussion is; you cannot vote on something you cannot > verify, so convenience binaries, while they may be distributed via our > mirror system, are not part of the official release, and as such, you > could add them after the fact. > > > > >>> 3. What's the status in legal terms of Emilian's CoolBeans, i.e., can > >>> anyone take Apache NetBeans source code at any point of the release and > >>> rename it and then provide it in their own way? (I'm assuming Yes here, > >>> but > >>> would be good to have that very clearly established.) > >> > >> Yes, provided they keep the notices intact and do their best to prevent > >> confusion between their fork and the official product. > > > > Cool! ;-) > > > > --emi > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
