On Thu, Aug 23, 2018 at 5:10 AM, Bertrand Delacretaz <[email protected] > wrote:
> Yes - I think the only requirement at this point is that the > *ownership* of the domains is transferred to Apache, moving the > content is a separate concern. > Is it even possible for the Apache foundation to distribute older artifacts if they have, for example, GPL licensed parts within them? Can they do it from "netbeans.org" as some sort of "off shore shell company" kind of thing? (since it's "not Apache", yes I know I'm splitting hairs). The NetBeans Apache Git server contains GPL code (since, as I understand it, it has direct donations from the Oracle contribution that were committed before the license change). It's pedantic, but how does this licensed code stand under Apache policies. Is it allowed as a "legacy" component? Can the original netbeans.org content also be grandfathered in under a similar exemption? One of the issues, to me, is the impact of having a large, established web presence just vanish in to the ether, which is what would happen were netbeans.org to either just "go away" or be significantly refactored. The destruction of java.net was, and still is, a painful event to the Java community. If netbeans.org is to be significantly redone, is there a reason for it at all beyond a redirect to netbeans.apache.org? Are there other Apache projects that have any significant web presence outside of the *.apache.org system? There is a LOT of stuff and history at netbeans.org. It would be nice (IMHO) if it were to remain mostly intact, and even maintained, as an anchor within the NetBeans community, especially the old artifacts and releases but also all of the documentation and tutorials. I'd hate for it to have to be a project to port all of those pages to someplace else. But I just don't know how much of a brand presence NetBeans can have out side of Apache. Not sure what the governance guidelines are like for that. Regards, Will Hartung
