Re: [mentors] Can we keep a reference to the Plugin Portal?
Great. I've updated https://issues.apache.org/jira/browse/NETBEANS-163 : > Add disclaimer for the Plugin Portal in the IDE --emi > Original Message >Subject: Re: [mentors] Can we keep a reference to the Plugin Portal? >Local Time: November 27, 2017 4:36 PM >UTC Time: November 27, 2017 2:36 PM >From: bdelacre...@apache.org >To: dev@netbeans.incubator.apache.org > >Hi, > > On Sun, Nov 26, 2017 at 6:50 PM, Emilian Bold >emilian.b...@protonmail.ch wrote: >>...can Apache NetBeans still refer new users to the Plugin Portal?... >> >> Providing a way to install non-Apache plugins at runtime is fine IMO, >> as long as there's no confusion regarding their provenance. >> >> NetBeans should have a visible disclaimer that such plugins are not >> endorsed by Apache and installed at the user's own risk. I suppose >> there's a dialog for accepting the plugin's licences, that disclaimer >> could be there. >> >> -Bertrand >
AW: [mentors] Can we keep a reference to the Plugin Portal?
That sounds good. Gesendet von Mail für Windows 10 Von: Bertrand Delacretaz Gesendet: Montag, 27. November 2017 15:36 An: dev@netbeans.incubator.apache.org Betreff: Re: [mentors] Can we keep a reference to the Plugin Portal? Hi, On Sun, Nov 26, 2017 at 6:50 PM, Emilian Bold wrote: > ...can Apache NetBeans still refer new users to the Plugin Portal?... Providing a way to install non-Apache plugins at runtime is fine IMO, as long as there's no confusion regarding their provenance. NetBeans should have a visible disclaimer that such plugins are not endorsed by Apache and installed at the user's own risk. I suppose there's a dialog for accepting the plugin's licences, that disclaimer could be there. -Bertrand
Re: [mentors] Can we keep a reference to the Plugin Portal?
Hi, On Sun, Nov 26, 2017 at 6:50 PM, Emilian Bold wrote: > ...can Apache NetBeans still refer new users to the Plugin Portal?... Providing a way to install non-Apache plugins at runtime is fine IMO, as long as there's no confusion regarding their provenance. NetBeans should have a visible disclaimer that such plugins are not endorsed by Apache and installed at the user's own risk. I suppose there's a dialog for accepting the plugin's licences, that disclaimer could be there. -Bertrand
AW: [mentors] Can we keep a reference to the Plugin Portal?
I see and feel the pain here too. I don’t have any idea about that, only worries atm. Maybe github, tags could be a good idea or an Apache Marketplace as for IntelliJ, Visual Studio, Visual Studio Code or Sublime etc. But it is a shame that it is not possible host 3rd-party-plugins with another license than Apache but ok maybe there is much more legal stuff behind it that I don’t understand. But is shouldn’t be so strict. The plugin developers should Change the license for sure but should be responsible for there own plugins. Gesendet von Mail für Windows 10 Von: Neil C Smith Gesendet: Montag, 27. November 2017 15:20 An: dev@netbeans.incubator.apache.org; Emilian Bold Betreff: Re: [mentors] Can we keep a reference to the Plugin Portal? On Sun, Nov 26, 2017 at 6:02 PM Emilian Bold wrote: > PS: I assume this will also depend on who officially manages the Plugin > Portal going forward. > Why do I get the idea that we're making lives difficult for ourselves there?! As I understand it, there are two issues with the current plugin website with regard to Apache infrastructure - web infrastructure needs to be statically generated, and we can't host binaries that aren't Apache licensed? But, all the IDE needs is the catalog.xml? And that can contain absolute URL's? In which case can we just statically host the catalog via Apache linking to binaries elsewhere (eg. GitHub release tags)? Review process then becomes more like a PR to the catalog (or to the files used to generate the catalog)? Just a thought - if there's a way to keep as much of this within Apache infrastructure centrally even if it requires rethinking things a bit, I personally think that's more sustainable. Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: [mentors] Can we keep a reference to the Plugin Portal?
On Sun, Nov 26, 2017 at 6:02 PM Emilian Bold wrote: > PS: I assume this will also depend on who officially manages the Plugin > Portal going forward. > Why do I get the idea that we're making lives difficult for ourselves there?! As I understand it, there are two issues with the current plugin website with regard to Apache infrastructure - web infrastructure needs to be statically generated, and we can't host binaries that aren't Apache licensed? But, all the IDE needs is the catalog.xml? And that can contain absolute URL's? In which case can we just statically host the catalog via Apache linking to binaries elsewhere (eg. GitHub release tags)? Review process then becomes more like a PR to the catalog (or to the files used to generate the catalog)? Just a thought - if there's a way to keep as much of this within Apache infrastructure centrally even if it requires rethinking things a bit, I personally think that's more sustainable. Best wishes, Neil -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: [mentors] Can we keep a reference to the Plugin Portal?
PS: I assume this will also depend on who officially manages the Plugin Portal going forward. --emi > Original Message >Subject: [mentors] Can we keep a reference to the Plugin Portal? >Local Time: November 26, 2017 7:50 PM >UTC Time: November 26, 2017 5:50 PM >From: emilian.b...@protonmail.ch >To: dev@netbeans.incubator.apache.org > >Hello, > > Right now NetBeans users may easily install verified 3rd party plugins from > an update center called Plugin Portal, with the site > http://plugins.netbeans.org > > The whole Plugin Portal will be moved outside Oracle (and outside Apache) > soon. > > My question is: can Apache NetBeans still refer new users to the Plugin > Portal? > > This is quite similar to the way Apache Maven refers users to Maven Central > which is hosted by Sonatype, Inc. > > Note that the Plugin Portal is a bit better than Maven Central because > plugins need to be validated by at least 2 authorised people before being > shown to users. > > Initially I had assumed that we have to delete Plugin Portal from a default > build and I created https://issues.apache.org/jira/browse/NETBEANS-163 but > now, in light of the Apache Maven precedent, I believe we might still keep it. > > Can we keep it? > > --emi >
[mentors] Can we keep a reference to the Plugin Portal?
Hello, Right now NetBeans users may easily install verified 3rd party plugins from an update center called Plugin Portal, with the site http://plugins.netbeans.org The whole Plugin Portal will be moved outside Oracle (and outside Apache) soon. My question is: can Apache NetBeans still refer new users to the Plugin Portal? This is quite similar to the way Apache Maven refers users to Maven Central which is hosted by Sonatype, Inc. Note that the Plugin Portal is a bit better than Maven Central because plugins need to be validated by at least 2 authorised people before being shown to users. Initially I had assumed that we have to delete Plugin Portal from a default build and I created https://issues.apache.org/jira/browse/NETBEANS-163 but now, in light of the Apache Maven precedent, I believe we might still keep it. Can we keep it? --emi
