On Wed, Sep 14, 2016 at 9:10 AM, Bertrand Delacretaz <bdelacre...@apache.org> wrote: > Hi, > > On Wed, Sep 14, 2016 at 2:57 PM, Geertjan Wielenga > <geertjan.wiele...@googlemail.com> wrote: >> ...there is no code on plugins.netbeans.org at all. No one can donate >> any code from anywhere on plugins.netbeans.org to anyone else. It simply >> contains binaries... > > Thanks for the clarification. > > This confirms my view, I don't think we should make hosting > plugins.netbeans.org part of the incubation plan. That hosting might > happen later, separately, but it's IMO not a condition for a > successful move of NetBeans to Apache and much better discussed > separately, once the project starts. > > -Bertrand >
While it may not be a requirement to enter incubation, I do want us to understand plugins.netbeans.org (and any other pieces of their infrastructure) I admit it's been some years since I have used Netbeans in anger, but plugins are (or were) pretty important to the user community. I don't want us to defer the discussion for it to come back some years down the road, especially for something that I perceive is important for the user community. I think this is similar to Maven Central - yes, we license maven central to a third party and they administer the service. However, if the time comes that either Sonatype or the PMC kill that off, Maven Central can't just 'go away' - either a second third-party would have to come in, or the ASF will have to bear the responsibility. So even if someone else is licensed the ability to run plugins.netbeans.org - we need to understand the responsibilities, as it may come home to roost.[1] --David [1] http://idioms.thefreedictionary.com/come+home+to+roost - My apologies for the idiom. --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
