We talked about this here: Keycloak Plugin - #8 by javahippie
I think there should be two types of projects:
- Extensions maintained by Operaton, they inherit the existing operaton-release-parent, as they will be deployed in the org.operaton Namespace in central Nexus, which we control. They are hosted in the GitHub org of Operaton, so they can access secrets for automated deployment from GitHub Workflows (later in time)
- Extensions from the community. These won’t have any requirements for a parent pom, as it is the maintainers decision how and where they will be published. The Operaton GitHub org has no responsibilities or rights on those repositories, they are 100% under the control of the maintainer.
If a maintainer decides to move a library / plugin to the Operaton org, this can be discussed, imho. Does this sound like a sensible approach?