Regarding slack, there is the “#plugin-developers” channel on the Netbean slack ( https://netbeans.slack.com/ ) if that helps.
How should these language (or any) plugins be managed from a organization, namespace, and repository perspective? Assume they could fall under a subproject under given organization similar to existing things under https://github.com/apache (or other organizations like https://github.com/eclipse) or could be independent of these all together. If under apache org, what involvement by apache would be needed (i.e. if make it an “apache language plugin” how is that sanctioned and accepted? Assume some sort of “incubator project” like netbeans went through but not sure all the overhead for a small project would be worth it)? Should they be “sub-projects” under “apache/netbeans” repository code base? Assume not give it would grow the code base but could provides better integrated language solution to baseline netbeans proper [i.e. “Netbeans release x.y.z supports, Java, PHP, <new Language here>“ upon release). But if it was, what would be necessary to include them within the core baseline (i.e. new cluster, compatible licenses, establish dependencies [external/internal], etc.)? Assume preferred would be a new repository (or repositories) and package namespace would be created for given language which provides more independent development and control on plugin publication activities. Should some sort of bundle of plugins be developed together (i.e. org.apache.netbeans.contrib, org.apache.netbeans.plugin, or org.apache.netbeans.lang, etc.)with multiple language plugins [i.e. build all languages included in language bundle] (kind of like gcc which adds new language sometimes as part of main but others as independent separate libraries). Or a completely non-apache namespace of whomever chooses to create and maintain them (i.e. org.some.organization.netbean.plugin or com.some.company.netbeans.plugin, etc.)? A more radical change would be to move many of existing language and integrated plugins out of core netbeans to focus more on the basic IDE but I’m sure that would be too risky a change. Eric ________________________________ > From: John Kostaras <jkosta...@gmail.com> > Sent: Friday, December 31, 2021 10:41 PM > To: dev@netbeans.apache.org <dev@netbeans.apache.org> > Subject: Add support for other programming languages > > If you are interested in contributing in maintaining other programming > languages support for NetBeans, please reply to this thread. > > There are many programming languages that have been dropped from Apache > NetBeans, for various reasons. A list can be found here > <https://cwiki.apache.org/confluence/display/NETBEANS/Community+plugins>. > Some of them need little effort to provide at least some basic > functionality. > > The task is not easy, as there are different technologies (JavaCC, ANTLR, > LSP) that these plugins have been written into, and the NetBeans APIs have > been changed during time. A draft wiki page on how to add language support > to NetBeans can be found here > < > https://cwiki.apache.org/confluence/display/NETBEANS/Adding+New+Language+Support > > > . > > We could have a separate thread or organise in slack, e.g. to create a > better overview of what needs to be done and how to proceed. > > Thank you in advance. > > K/r, > > John. > -- Eric Bresie ebre...@gmail.com
