Replies: 7 comments
-
I would use our domain but the package would be |
Beta Was this translation helpful? Give feedback.
-
I've updated the title since for now it's really the package name I'd need, however, conventionally the artifact group name matches the package name prefix, so if we used |
Beta Was this translation helpful? Give feedback.
-
Yes I'd move everything (package and artifacts) under |
Beta Was this translation helpful? Give feedback.
-
Only this:
Also someone to maintain. I know this isn't an issue at the moment but I don't know who has access to either the funds or to the domain name registration etc. so I'm not sure what our bus factor is. That's not a problem with Maybe it doesn't matter once the initial publishing is done under the new group name. I'm not familiar with publishing to Maven Central. |
Beta Was this translation helpful? Give feedback.
-
It is not. We will not have problems for this. |
Beta Was this translation helpful? Give feedback.
-
And the idea behind open the donations was to make sure that the founds to keep that founds running is not tied to any of us. The permissions and transfer should be handled but I hope that would not be a problem to maintain that in the future regardless who are the maintainers. |
Beta Was this translation helpful? Give feedback.
-
Sorry I missunderstood you mean 'money', I thought |
Beta Was this translation helpful? Give feedback.
-
Should it be
detekt.dev
? If we want the artifact group name to match, it does tie us to a specific domain name which requires $, but the only realistic alternatives would becom.github.detekt
orio.github.detekt
(which could be a contender as it's already used in the package name for some classes etc. in the current plugin).I'm exploring some backwards compatible changes in the detekt plugin, but they'd introduce new interfaces for public use, so it would be good to align with whatever the package/artifact group names will be.
Beta Was this translation helpful? Give feedback.
All reactions