Re: [DISCUSS] Frontend distro of NetBeans

[Wade Chandler]

> 
> On Apr 20, 2019, at 10:31 AM, Kenneth Fogel  
> wrote:
> 
> This may have been brought up before but is there any talk about a python 
> enabled NetBeans. My program at Dawson is planning to drop PHP because the 
> job market demand here has dropped while requests for Python have increased. 
> I know there is a plug-in but could it be more? I agree with continuing 
> targeted NetBeans and having a PHP version. Then there is Go, Rust and for 
> April Fools we will need a GW-Basic version. Extra points if you know what GW 
> stands for.

Well there has been Python support in NetBeans in the past, and that has been 
supported by nbPython:
http://nbpython.org/buildnbpython.html 

Who have just kept the contrib modules up to date as noted on the above page; 
see this:
http://hg.netbeans.org/main/contrib/file 


Go there and search for Python. As these actually belong to NetBeans and Oracle 
and have continued to live with the project, then there should be nothing 
really keeping this from now being moved over to Apache. I’m sure the nbPython 
guys could use some help and would appreciate it:
https://cwiki.apache.org/confluence/display/NETBEANS/2017+Release 
 (not sure 
if this happened)

But, I suggest we do get this moved to Apache and the repos, but too, that 
anyone interested in this to please help out. I suggest we start a separate 
thread for this being sure not to sue reply.

Thanks,

Wade

Re: [DISCUSS] Frontend distro of NetBeans

[Junichi Yamamoto]

> I like something like "Apache NetBeans: PHP Edition", or something of the 
> like.

I agree with this. I prefer to use the same name(i.e. not xxBeans but
NetBeans).

Plus we should run unit tests(especially php.editor) if possible. I
didn't notice for a long time that unit tests fail after GraalJS
parser was removed...

Thanks,
Junichi

On Sat, Apr 20, 2019 at 11:11 PM Josh Juneau  wrote:
>
> I agree that a separate "lite" distribution would be useful for those who do 
> not wish to deal with Java.  I also agree with Wade that such a release 
> should provide the option to automatically download and install a JRE 
> distribution if one wishes to do so.
>
> Around naming, it seems to make sense to continue to build off the Apache 
> NetBeans brand, but perhaps create new "editions".  I like something like 
> "Apache NetBeans: PHP Edition", or something of the like.
>
>
> Josh Juneau
> juneau...@gmail.com
> http://jj-blogger.blogspot.com
> https://www.apress.com/us/search?query=Juneau
>
> > On Apr 20, 2019, at 7:03 AM, Eric Barboni  wrote:
> >
> > Hi
> > I would keep Apache NetBeans in the name,  Apache PhpBeans looks like a TLP 
> > of Apache not something from Apache NetBeans.
> > And its misleading to existing Apache TPL like OpenWebBeans,XMLBeans.
> >
> > But making several branding sounds a good idea.
> >
> > Jenkins release build should be make more complex but this will not change 
> > the vote and release except more file to sign and to review. It will be in 
> > the convenience libraries part of the voting thread.
> > For Apache Netbeans 12.0 we would have Apache NetBeans 12.0 "PhpBeans"  at 
> > the same time.
> >
> > The above link all the branding to official Apache NetBeans release to 
> > limit effort.
> >
> > Best Regards
> > Eric
> >
> > -Message d'origine-
> > De : Wade Chandler 
> > Envoyé : samedi 20 avril 2019 13:08
> > À : dev@netbeans.apache.org
> > Objet : Re: [DISCUSS] Frontend distro of NetBeans
> >
> >> On Fri, Apr 19, 2019, 21:57 Geertjan Wielenga  wrote:
> >>
> >> Hi all,
> >>
> >> I think one of the coolest things we could do together is spin out a
> >> separate distro specifically for PHP/JS type developers.
> >>
> >> We had that before, it only requires JRE, not JDK, and would mean the
> >> potential for a small snappy editor-focused tool (that as a side
> >> effect could be interesting for users of a few comparable editors we
> >> can all think of).
> >>
> >> And that would bring in new contributions too since we’d be targeting
> >> a different type of developer.
> >>
> >> What would need for this to be done and where? Probably something
> >> would need to be tweaked on Jenkins?
> >>
> >
> > This seems like a release build step.
> >
> > One thing though, would we want to do any special branding like a different 
> > splash screen, icon, and name? Something like "WebBeans" (sounds like
> > webbings) or could do some other things like "PhpBeans"/"PhBean"/"PhBeans"
> > and "PyBeans"/"BeanPy"/"BeansPy" and "CBeans"/"SeaBeans"/"Beans++" or 
> > "CyBeans" for C, C++, and Python or given all the Machine Learning bits at 
> > Apache "MLBeans" with C, C++, Python, Java, and Groovy with some new 
> > wizards for Spark and TensorFlow related items. Later with some of the new 
> > mobile and native techs we could even have "MoBeans" (please).
> >
> > It would be handy if the installer offered to download and install a JDK 
> > for the user as well from some where like AdoptOpenJDK. Those devs often 
> > don't know about Java tools. And if we setup a JDK, and if they ever 
> > install any Java, Groovy, or Gradle tools, then they'd be ready to work 
> > with them.
> >
> > I like the base idea plus all the play I think we can do like mentioned 
> > above. I think for me personally I would rather focus on hardening, adding 
> > features, and making more robust first, and then circle back, but laying 
> > some foundation for it at the same time I think would be great; 
> > names/branding/config steps etc/requirements from which to build features 
> > or harden.
> >
> > Thanks
> >
> > Wade
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [DISCUSS] Frontend distro of NetBeans

[Geertjan Wielenga]

I don't see that as a requirement. In the same way as the experimental
installer we have right now, we could create an installer for this which,
if no JRE is present, a message would appear that it needs to be obtained
from some specific place -- what that place is is the question.

Gj

On Sun, Apr 21, 2019 at 6:53 AM Laszlo Kishalmi 
wrote:

> Well,
>
> I do not know how dead JRE is, however this distro would have only
> meaningful if we can actually pack the JRE along the code and yes
> probably installable with a proper installer.
>
> I could probably make a Snap for such a distro for Linux without too
> much hustle, though I do not think I legally ship/distribute it as
> Apache NetBeans. Or maybe as it would be an unofficial convenience
> binary which would not be hosted on Apache infra...
>
> I do not really know.
>
> On 4/20/19 1:12 PM, Matthias Bläsing wrote:
> > Hi,
> >
> > at this point in time I don't see any benefit in producing a bunch of
> > different netbeans releases.
> >
> > Am Freitag, den 19.04.2019, 21:57 -0400 schrieb Geertjan Wielenga:
> >> I think one of the coolest things we could do together is spin out a
> >> separate distro specifically for PHP/JS type developers.
> > what is the use case of that special distribution?
> >
> >> We had that before, it only requires JRE, not JDK, and would mean the
> >> potential for a small snappy editor-focused tool (that as a side effect
> >> could be interesting for users of a few comparable editors we can all
> think
> >> of).
> > The JRE is dead (for any Java version >= 9), at least that is what
> > every java vendor is telling. You can either get a JDK from Azul or Red
> > Hat and/or Amazon or stay in the past with JRE derived from JDK 8.
> >
> > If we could build a fully runnable NetBeans for people not interested
> > in Java, ok, but neigther the ASF, nor Oracle do anything visible to
> > resolve the big problem in the room:
> >
> > GPLv2+CPE at this time is not acceptable as a dependency for the ASF at
> > this time (there is an open issue, that asks for moving GPLv2+CPE to
> > Category B, but the ASF side raised concers and noone stood up to calm
> > them.
> >
> > I don't think, that random comments will help here:
> >
> > https://issues.apache.org/jira/browse/LEGAL-336
> >
> > But comments from lawyers, preferable from oracle, could help to
> > resolve this. Mayber it would be possible to reword the CPE to make it
> > compatible with the ASFs requirements for dependencies.
> >
> > That would help _many_ apache projects, as many apache projects are
> > Java projects and so implicitly depend on OpenJDK (if I'm not mistaken
> > there is _no_ other open source Java distribution out there, that is
> > even remotely as up-to-date and open as OpenJDK).
> >
> > Just my 2 cents.
> >
> > Greetings
> >
> > Matthias
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.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.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: [DISCUSS] Frontend distro of NetBeans

[Laszlo Kishalmi]

Well,

I do not know how dead JRE is, however this distro would have only 
meaningful if we can actually pack the JRE along the code and yes 
probably installable with a proper installer.


I could probably make a Snap for such a distro for Linux without too 
much hustle, though I do not think I legally ship/distribute it as 
Apache NetBeans. Or maybe as it would be an unofficial convenience 
binary which would not be hosted on Apache infra...


I do not really know.

On 4/20/19 1:12 PM, Matthias Bläsing wrote:

Hi,

at this point in time I don't see any benefit in producing a bunch of
different netbeans releases.

Am Freitag, den 19.04.2019, 21:57 -0400 schrieb Geertjan Wielenga:

I think one of the coolest things we could do together is spin out a
separate distro specifically for PHP/JS type developers.

what is the use case of that special distribution?


We had that before, it only requires JRE, not JDK, and would mean the
potential for a small snappy editor-focused tool (that as a side effect
could be interesting for users of a few comparable editors we can all think
of).

The JRE is dead (for any Java version >= 9), at least that is what
every java vendor is telling. You can either get a JDK from Azul or Red
Hat and/or Amazon or stay in the past with JRE derived from JDK 8.

If we could build a fully runnable NetBeans for people not interested
in Java, ok, but neigther the ASF, nor Oracle do anything visible to
resolve the big problem in the room:

GPLv2+CPE at this time is not acceptable as a dependency for the ASF at
this time (there is an open issue, that asks for moving GPLv2+CPE to
Category B, but the ASF side raised concers and noone stood up to calm
them.

I don't think, that random comments will help here:

https://issues.apache.org/jira/browse/LEGAL-336

But comments from lawyers, preferable from oracle, could help to
resolve this. Mayber it would be possible to reword the CPE to make it
compatible with the ASFs requirements for dependencies.

That would help _many_ apache projects, as many apache projects are
Java projects and so implicitly depend on OpenJDK (if I'm not mistaken
there is _no_ other open source Java distribution out there, that is
even remotely as up-to-date and open as OpenJDK).

Just my 2 cents.

Greetings

Matthias


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [DISCUSS] Frontend distro of NetBeans

[Matthias Bläsing]

Hi,

at this point in time I don't see any benefit in producing a bunch of
different netbeans releases.

Am Freitag, den 19.04.2019, 21:57 -0400 schrieb Geertjan Wielenga:
> 
> I think one of the coolest things we could do together is spin out a
> separate distro specifically for PHP/JS type developers.

what is the use case of that special distribution? 

> We had that before, it only requires JRE, not JDK, and would mean the
> potential for a small snappy editor-focused tool (that as a side effect
> could be interesting for users of a few comparable editors we can all think
> of).

The JRE is dead (for any Java version >= 9), at least that is what
every java vendor is telling. You can either get a JDK from Azul or Red
Hat and/or Amazon or stay in the past with JRE derived from JDK 8.

If we could build a fully runnable NetBeans for people not interested
in Java, ok, but neigther the ASF, nor Oracle do anything visible to
resolve the big problem in the room:

GPLv2+CPE at this time is not acceptable as a dependency for the ASF at
this time (there is an open issue, that asks for moving GPLv2+CPE to
Category B, but the ASF side raised concers and noone stood up to calm
them.

I don't think, that random comments will help here:

https://issues.apache.org/jira/browse/LEGAL-336

But comments from lawyers, preferable from oracle, could help to
resolve this. Mayber it would be possible to reword the CPE to make it
compatible with the ASFs requirements for dependencies.

That would help _many_ apache projects, as many apache projects are
Java projects and so implicitly depend on OpenJDK (if I'm not mistaken
there is _no_ other open source Java distribution out there, that is
even remotely as up-to-date and open as OpenJDK).

Just my 2 cents.

Greetings

Matthias


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [DISCUSS] Frontend distro of NetBeans

[Kenneth Fogel]

This may have been brought up before but is there any talk about a python 
enabled NetBeans. My program at Dawson is planning to drop PHP because the job 
market demand here has dropped while requests for Python have increased. I know 
there is a plug-in but could it be more? I agree with continuing targeted 
NetBeans and having a PHP version. Then there is Go, Rust and for April Fools 
we will need a GW-Basic version. Extra points if you know what GW stands for.

Ken Fogel
Co-Chairperson and Co-Program Coordinater
Computer Science Technology
Dawson College
3040 Sherbrooke St. W
Westmount, Quebec
H3Z 1A4, Canada
Tel: 514-931-8731 x 4799
Twitter: @omniprof

From: Josh Juneau 
Sent: Saturday, April 20, 2019 10:11 AM
To: dev@netbeans.apache.org
Cc: wadechand...@apache.org
Subject: Re: [DISCUSS] Frontend distro of NetBeans

I agree that a separate "lite" distribution would be useful for those who do 
not wish to deal with Java. I also agree with Wade that such a release should 
provide the option to automatically download and install a JRE distribution if 
one wishes to do so.

Around naming, it seems to make sense to continue to build off the Apache 
NetBeans brand, but perhaps create new "editions". I like something like 
"Apache NetBeans: PHP Edition", or something of the like.


Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau

> On Apr 20, 2019, at 7:03 AM, Eric Barboni  wrote:
>
> Hi
> I would keep Apache NetBeans in the name, Apache PhpBeans looks like a TLP of 
> Apache not something from Apache NetBeans.
> And its misleading to existing Apache TPL like OpenWebBeans,XMLBeans.
>
> But making several branding sounds a good idea.
>
> Jenkins release build should be make more complex but this will not change 
> the vote and release except more file to sign and to review. It will be in 
> the convenience libraries part of the voting thread.
> For Apache Netbeans 12.0 we would have Apache NetBeans 12.0 "PhpBeans" at the 
> same time.
>
> The above link all the branding to official Apache NetBeans release to limit 
> effort.
>
> Best Regards
> Eric
>
> -Message d'origine-
> De : Wade Chandler 
> Envoyé : samedi 20 avril 2019 13:08
> À : dev@netbeans.apache.org
> Objet : Re: [DISCUSS] Frontend distro of NetBeans
>
>> On Fri, Apr 19, 2019, 21:57 Geertjan Wielenga  wrote:
>>
>> Hi all,
>>
>> I think one of the coolest things we could do together is spin out a
>> separate distro specifically for PHP/JS type developers.
>>
>> We had that before, it only requires JRE, not JDK, and would mean the
>> potential for a small snappy editor-focused tool (that as a side
>> effect could be interesting for users of a few comparable editors we
>> can all think of).
>>
>> And that would bring in new contributions too since we’d be targeting
>> a different type of developer.
>>
>> What would need for this to be done and where? Probably something
>> would need to be tweaked on Jenkins?
>>
>
> This seems like a release build step.
>
> One thing though, would we want to do any special branding like a different 
> splash screen, icon, and name? Something like "WebBeans" (sounds like
> webbings) or could do some other things like "PhpBeans"/"PhBean"/"PhBeans"
> and "PyBeans"/"BeanPy"/"BeansPy" and "CBeans"/"SeaBeans"/"Beans++" or 
> "CyBeans" for C, C++, and Python or given all the Machine Learning bits at 
> Apache "MLBeans" with C, C++, Python, Java, and Groovy with some new wizards 
> for Spark and TensorFlow related items. Later with some of the new mobile and 
> native techs we could even have "MoBeans" (please).
>
> It would be handy if the installer offered to download and install a JDK for 
> the user as well from some where like AdoptOpenJDK. Those devs often don't 
> know about Java tools. And if we setup a JDK, and if they ever install any 
> Java, Groovy, or Gradle tools, then they'd be ready to work with them.
>
> I like the base idea plus all the play I think we can do like mentioned 
> above. I think for me personally I would rather focus on hardening, adding 
> features, and making more robust first, and then circle back, but laying some 
> foundation for it at the same time I think would be great; 
> names/branding/config steps etc/requirements from which to build features or 
> harden.
>
> Thanks
>
> Wade
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

Re: [DISCUSS] Frontend distro of NetBeans

[Josh Juneau]

I agree that a separate "lite" distribution would be useful for those who do 
not wish to deal with Java.  I also agree with Wade that such a release should 
provide the option to automatically download and install a JRE distribution if 
one wishes to do so.

Around naming, it seems to make sense to continue to build off the Apache 
NetBeans brand, but perhaps create new "editions".  I like something like 
"Apache NetBeans: PHP Edition", or something of the like.


Josh Juneau
juneau...@gmail.com
http://jj-blogger.blogspot.com
https://www.apress.com/us/search?query=Juneau

> On Apr 20, 2019, at 7:03 AM, Eric Barboni  wrote:
> 
> Hi
> I would keep Apache NetBeans in the name,  Apache PhpBeans looks like a TLP 
> of Apache not something from Apache NetBeans.
> And its misleading to existing Apache TPL like OpenWebBeans,XMLBeans. 
> 
> But making several branding sounds a good idea. 
> 
> Jenkins release build should be make more complex but this will not change 
> the vote and release except more file to sign and to review. It will be in 
> the convenience libraries part of the voting thread. 
> For Apache Netbeans 12.0 we would have Apache NetBeans 12.0 "PhpBeans"  at 
> the same time. 
> 
> The above link all the branding to official Apache NetBeans release to limit 
> effort.
> 
> Best Regards
> Eric
> 
> -Message d'origine-
> De : Wade Chandler  
> Envoyé : samedi 20 avril 2019 13:08
> À : dev@netbeans.apache.org
> Objet : Re: [DISCUSS] Frontend distro of NetBeans
> 
>> On Fri, Apr 19, 2019, 21:57 Geertjan Wielenga  wrote:
>> 
>> Hi all,
>> 
>> I think one of the coolest things we could do together is spin out a 
>> separate distro specifically for PHP/JS type developers.
>> 
>> We had that before, it only requires JRE, not JDK, and would mean the 
>> potential for a small snappy editor-focused tool (that as a side 
>> effect could be interesting for users of a few comparable editors we 
>> can all think of).
>> 
>> And that would bring in new contributions too since we’d be targeting 
>> a different type of developer.
>> 
>> What would need for this to be done and where? Probably something 
>> would need to be tweaked on Jenkins?
>> 
> 
> This seems like a release build step.
> 
> One thing though, would we want to do any special branding like a different 
> splash screen, icon, and name? Something like "WebBeans" (sounds like
> webbings) or could do some other things like "PhpBeans"/"PhBean"/"PhBeans"
> and "PyBeans"/"BeanPy"/"BeansPy" and "CBeans"/"SeaBeans"/"Beans++" or 
> "CyBeans" for C, C++, and Python or given all the Machine Learning bits at 
> Apache "MLBeans" with C, C++, Python, Java, and Groovy with some new wizards 
> for Spark and TensorFlow related items. Later with some of the new mobile and 
> native techs we could even have "MoBeans" (please).
> 
> It would be handy if the installer offered to download and install a JDK for 
> the user as well from some where like AdoptOpenJDK. Those devs often don't 
> know about Java tools. And if we setup a JDK, and if they ever install any 
> Java, Groovy, or Gradle tools, then they'd be ready to work with them.
> 
> I like the base idea plus all the play I think we can do like mentioned 
> above. I think for me personally I would rather focus on hardening, adding 
> features, and making more robust first, and then circle back, but laying some 
> foundation for it at the same time I think would be great; 
> names/branding/config steps etc/requirements from which to build features or 
> harden.
> 
> Thanks
> 
> Wade
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 

RE: [DISCUSS] Frontend distro of NetBeans

[Eric Barboni]

Hi
 I would keep Apache NetBeans in the name,  Apache PhpBeans looks like a TLP of 
Apache not something from Apache NetBeans.
 And its misleading to existing Apache TPL like OpenWebBeans,XMLBeans. 

 But making several branding sounds a good idea. 

 Jenkins release build should be make more complex but this will not change the 
vote and release except more file to sign and to review. It will be in the 
convenience libraries part of the voting thread. 
 For Apache Netbeans 12.0 we would have Apache NetBeans 12.0 "PhpBeans"  at the 
same time. 

 The above link all the branding to official Apache NetBeans release to limit 
effort.
 
Best Regards
Eric

-Message d'origine-
De : Wade Chandler  
Envoyé : samedi 20 avril 2019 13:08
À : dev@netbeans.apache.org
Objet : Re: [DISCUSS] Frontend distro of NetBeans

On Fri, Apr 19, 2019, 21:57 Geertjan Wielenga  wrote:

> Hi all,
>
> I think one of the coolest things we could do together is spin out a 
> separate distro specifically for PHP/JS type developers.
>
> We had that before, it only requires JRE, not JDK, and would mean the 
> potential for a small snappy editor-focused tool (that as a side 
> effect could be interesting for users of a few comparable editors we 
> can all think of).
>
> And that would bring in new contributions too since we’d be targeting 
> a different type of developer.
>
> What would need for this to be done and where? Probably something 
> would need to be tweaked on Jenkins?
>

This seems like a release build step.

One thing though, would we want to do any special branding like a different 
splash screen, icon, and name? Something like "WebBeans" (sounds like
webbings) or could do some other things like "PhpBeans"/"PhBean"/"PhBeans"
and "PyBeans"/"BeanPy"/"BeansPy" and "CBeans"/"SeaBeans"/"Beans++" or "CyBeans" 
for C, C++, and Python or given all the Machine Learning bits at Apache 
"MLBeans" with C, C++, Python, Java, and Groovy with some new wizards for Spark 
and TensorFlow related items. Later with some of the new mobile and native 
techs we could even have "MoBeans" (please).

It would be handy if the installer offered to download and install a JDK for 
the user as well from some where like AdoptOpenJDK. Those devs often don't know 
about Java tools. And if we setup a JDK, and if they ever install any Java, 
Groovy, or Gradle tools, then they'd be ready to work with them.

I like the base idea plus all the play I think we can do like mentioned above. 
I think for me personally I would rather focus on hardening, adding features, 
and making more robust first, and then circle back, but laying some foundation 
for it at the same time I think would be great; names/branding/config steps 
etc/requirements from which to build features or harden.

Thanks

Wade


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [DISCUSS] Frontend distro of NetBeans

[Wade Chandler]

On Fri, Apr 19, 2019, 21:57 Geertjan Wielenga  wrote:

> Hi all,
>
> I think one of the coolest things we could do together is spin out a
> separate distro specifically for PHP/JS type developers.
>
> We had that before, it only requires JRE, not JDK, and would mean the
> potential for a small snappy editor-focused tool (that as a side effect
> could be interesting for users of a few comparable editors we can all think
> of).
>
> And that would bring in new contributions too since we’d be targeting a
> different type of developer.
>
> What would need for this to be done and where? Probably something would
> need to be tweaked on Jenkins?
>

This seems like a release build step.

One thing though, would we want to do any special branding like a different
splash screen, icon, and name? Something like "WebBeans" (sounds like
webbings) or could do some other things like "PhpBeans"/"PhBean"/"PhBeans"
and "PyBeans"/"BeanPy"/"BeansPy" and "CBeans"/"SeaBeans"/"Beans++" or
"CyBeans" for C, C++, and Python or given all the Machine Learning bits at
Apache "MLBeans" with C, C++, Python, Java, and Groovy with some new
wizards for Spark and TensorFlow related items. Later with some of the new
mobile and native techs we could even have "MoBeans" (please).

It would be handy if the installer offered to download and install a JDK
for the user as well from some where like AdoptOpenJDK. Those devs often
don't know about Java tools. And if we setup a JDK, and if they ever
install any Java, Groovy, or Gradle tools, then they'd be ready to work
with them.

I like the base idea plus all the play I think we can do like mentioned
above. I think for me personally I would rather focus on hardening, adding
features, and making more robust first, and then circle back, but laying
some foundation for it at the same time I think would be great;
names/branding/config steps etc/requirements from which to build features
or harden.

Thanks

Wade

[DISCUSS] Frontend distro of NetBeans

[Geertjan Wielenga]

Hi all,

I think one of the coolest things we could do together is spin out a
separate distro specifically for PHP/JS type developers.

We had that before, it only requires JRE, not JDK, and would mean the
potential for a small snappy editor-focused tool (that as a side effect
could be interesting for users of a few comparable editors we can all think
of).

And that would bring in new contributions too since we’d be targeting a
different type of developer.

What would need for this to be done and where? Probably something would
need to be tweaked on Jenkins?

Thanks,

Gj