I think those things get dated quickly. People tend to like to have recognition IMO, and is why to me the plugin portal grew, and contrib faded off. It would also mean folks putting code there have to keep it up, and we have to rely on them to do so, and they have to be all in on the Apache process and license if it is a project repo.
It seems it would make more sense to get the plugin portal working, and have it be able to pull from binaries and archives which could be stored any where; such as Github releases. If folks then want to contribute a plugin to NetBeans, it seems we’d figure out which cluster it made sense to be in, and then look at it as a code donation, and then put it in the proper repository for Apache NB (incubating). Otherwise, they’d just register with the portal. I think for the plugin portal, we could have a real simple registration scheme that is a repository that has a particular structure for a publisher with YAML files and images in it for plugin registration, and have a static site generator for it. We could protect to a reasonable degree the publishers files from anyone outside the Apache contributor organization by validating the userid of the commit matches the folder structure of the “publisher” or the publisher belongs to a GH organization. We could take that a step further, and allow links to other repositories of similar layout for publishers. We could easily pull in someones master repository during build time of a static repository. Anyways, I think that would be a better approach than facilitating contrib which gets odd considering the way Apache works versus how NB worked (the project). Contrib was a lighter more relaxed model where one did not need commit access to everything. Apache has no such model; contributors must be contributors. Wade > On May 28, 2018, at 4:33 AM, Christian Lenz <[email protected]> wrote: > > Hey Devs, > > long time ago, there was mail thread (private) with Geertjan and a guy who > created an „organization“ on GitHub for NetBeans Plugins, where I wanted to > join and added all of my plugins to this repo, to have it under a global, > public (official) repo for NetBeans. I don’t know what happened, I couldn’t > figure out the guy who created it, maybe have a look into my mails. > > Anyway, the Thing is that it doesn’t work out, maybe lack of time, only one > person was responsible for this or whatever. So why I wanted to bring this up > again is, that in my opinion, it would be nice if we can have a GitHub > repo/organization (Maybe Apache/NetBeans-Plugins) where we can add all of our > 3rd-party-plugins, which are not part of the core and/or a contrib repo again > or whatever. I don’t know the history of the contrib repo anymore, since we > don’t have it atm? > > I don’t know how the contrib repo was handled, but afaik, Maybe we don’t Need > it anymore or so? The contrib repo still exists with a lot of features (some > are old, some are strill working) who are still not part of the core but part > of a Plugin but to add it, you have to add the contrib repo as a dependency > to the Plugins section. > > So what do you think, do we still need a contrib repo? If yes, how could it > be handled? As a GitHub or Apache git repo with a GitHub Mirror? Should we > have an official Apache/netbeans-plugins repo like JetBrains have it for > there community Plugins? https://github.com/JetBrains/intellij-plugins > > Thread is kind of brainstorming. > > > Cheers > > Chris
