Hello, I am thinking about re-releasing a grade plugin that has existed but not received an update in a while (3y9m) into Gradle Plugin Portal or the github project codebase. Have been maintaining a github hosted fork with my own maintenance updates. These updates have been presented to upstream repo and maintainer over the past 18months to solicit interest from original maintainer. There is no public active communication from the original maintainer around this project over the past few years, while their other projects have received a code update. So in the essence of open source succession are there any general guidelines for such successor maintenance efforts ? I would welcome a high-level review of the project by anyone who understands aspects of plugin development or future Gradle ecosystem direction to allow addressing of concerns ahead of an initial release on Gradle Plugin Portal. Should I also publish a Maven Central version at the same time? It is my intention to publish in the next few months while I iron out the processes and changes (one being the namespace to use) as well as CI procedures for release engineering. The original plugin is the gradle-xjc-plugin and my fork is over at https://github.com/dlmiles/gradle-xjc-plugin