Project Status
Opened this issue · 7 comments
Is this project still alive? The last commit to main was 2 years ago and there are a bunch of open PRs that haven't been accepted since then.
I've found this project really useful and it shortcut some work I was going to have to do for some code wrapping Locales.
I'm asking as we can commit some time during work to useful projects and had considered this one when I saw there were gaps in testing and some missing countries etc. I don't want to spend time on submissions if the project is frozen and not accepting changes though.
I hope an organization will take over this repository. I don't mind even if the package name of the library is changed. I'm too busy to maintain nv-* libraries...
Sad to hear it but good to have confirmation of the roadmap for it.
I think it is sad that this project doesn't receive more attention nowadays.
May be it would be a good idea then to give some other people the possibility to maintain it too? May be we can just create a github organization, and transfer this to that? Or may be it's possible to just leave it here. Whatever gives the least amount of hassle.
I'm prepared to at least arrange the github actions to arrange building and releasing. I think that if we want to keep the maven coordinates it is sufficient if you help filling in the secrets for sonatype (or whatever route it chosen to publish to maven central)
Some open pull-requests are quite straight-forward, and can be accepted without much ado then, I think.
I made a little bit of progress on creating an org for a domain with sonatype etc, but have zero experience at maintaining a java project which is public, with maven. I'd intend to contribute to an active project if an individual or a group took on maintaining this.
I have some experience with that, though once set up, this kind of knowledge tends to be forgotten.
But IIRC, to be able to deploy to sonatype/maven central for a certain artifact you need to proof that you own the domain of the groupid. I suppose @TakahikoKawasaki once did that. If we leave the coordinates and want to automate the process, we just need some assistance of Takahiko to provide associated credentials in secrets of github actions.
@TakahikoKawasaki would you be comfortable with handing this over to a new, dedicated GitHub organisation?
I imagine we could create an organisation nv-i18n, whose sole purpose would be to maintain nv-i18n. So the new GitHub url would be https://github.com/nv-i18n/nv-i18n.
My employer uses nv-i18n in several places and could do the initial work of reviving the project and at the same time add community members to the new GitHub organisation to help maintain the project and reduce single point of failure.
Community members: would you be interested in participating in actively maintaining this project?
Thank you, all. I would be very happy to hand over this project to a trustworthy person or organization. You are welcome to change the package name com.neovisionaries and the library name nv-i18n as well. Unfortunately, I have no time to dedicate to this project anymore. Please let me know the procedures I need to follow to hand over the project.