Sounds like a good idea to me. I started a few years ago requesting the ownership of the project from James and Gleb to give it extra life, mostly with the migration to NETCore. I am sorry I could not continue to maintain it, and that's mostly because I'm not using hibernate in the projects I'm working on right now. I would be delighted and I think I speak on behalf of James and Gleb to share ownership with someone who can give continuity to the project, and if it were directly in NHibernate organisation, much better.Best Regards,
I just read an excellent post from the Moment.js team about their plans for their library: https://momentjs.com/docs/#/-project-status/ and was reminded of this discussion.
I’d recommend taking a similar approach. NHibernate takes over the repo, but declares it in maintenance-mode and will only provide critical patching. All users are encouraged to migrate away, and new users are directed elsewhere. That's done explicitly so there's no risk of people accidentally adopting an end-of-life library.Cheers
If you think there is a community of contributors just ready to get going, great!
The GitHub repository and the NuGet package are a pair. I will hand over both of them to the NHibernate organisation. But to be clear, I won’t hand over just the NuGet package on its own. Please let me know who from NHibernate I should speak to to get this started.
If the NHibernate organisation does not want to take ownership of the GitHub repository, then I won’t be changing ownership of the NuGet package either. In that case, I suggest you hard fork Fluent NHibernate, form your community of contributors and publish a new open source project (“New Fluent NHibernate”) with its own repository and NuGet package. Once you’ve done that, I will officially declare my packages and repositories archived and forward any users to your new package.
I know this sounds painful and that I'm being obstinate, but there have been many instances in recent years of naive package maintainers (me in this scenario) handing over ownership of abandoned open-source projects only to have the new maintainers use the existing install-base as an attack vector. For example, event-stream was exactly like this. So I want to either move everything to the official organisation where our users can trust it's being handled responsibly, or declare the project done and refer people to a successor.
For what it's worth, I'm sure you're all very trust worthy. But I don't know you. And the responsibility is on me if I hand this over to someone who abuses that privilege.
So for actions:
1. I need someone from the NHibernate organisation to declare that they will (or won't) take ownership of the GitHub repository and the NuGet package. I'm sorry, I don't know who that is now so you'll have to make it clear to me.
To view this discussion on the web visit https://groups.google.com/d/msgid/nhibernate-development/0930a7b9-1e7e-413a-afde-d5249eb65f3an%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nhibernate-development/CAMKuk26OTc%2BM8uWRd_Eg3URpujQLz0zTn9-P64fnZsW4iHp83A%40mail.gmail.com.
You received this message because you are subscribed to a topic in the Google Groups "nhibernate-development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/nhibernate-development/lhNOJuUatWA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to nhibernate-develo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nhibernate-development/5ed0f8de-4e46-4479-8aab-2d42367fc48an%40googlegroups.com.