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 <wadechand...@apache.org> 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 <geert...@apache.org> 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
