Adding a nhibernate/fluent-nhibernate repository seems to me a good option, as long as you are ready to handle it, and since contributors would be many, also as long as you are ready to share merging/releasing access with people most worthy of it.
May you have a way to attract the attention of such potential would-be contributors here, to let them share their thoughts? Is there also any opened issue on the current Fluent-Nhibernate repo, asking the owner to take action for giving available contributors the required rights for replacing current owners? About the NuGet package, you may be able to reclaim it, as NuGet has a procedure for abandoned packages, which I have already used successfully. It is quite lengthy, but well worth it, especially for a popular package. They call it dispute resolution, but this does also apply for abandoned packages. https://docs.microsoft.com/en-us/nuget/nuget-org/policies/dispute-resolution If current owners of the package do not answer at all, and you can explain why you should get ownership of it, it should work. Of course you will have more weight in reclaiming it if you already have an active fork of the project. Le samedi 12 septembre 2020 à 21:24:07 UTC+2, bredinh...@gmail.com a écrit : > From issue: https://github.com/nhibernate/nhibernate-core/issues/2531 > > I believe that many nhibernate developers know about FluentNhibernate at > least in some project. > > To understand the size of fluent-nhibernate adopters, they have 80% of the > stars in the nhibernate github. > > I use it in several of my projects, but lately, the project is dying, due > to the lack of support from the creators of the project. > - lack of reviewers with merge right > - lack of reviewers with ability to release > - no nugget access (need to create a new one as a lot of forks are doing) > > We have a lot of problems using the latest versions of nhibernate due to > lack of maintenance. > Here are some sample issues and pullrequests. > FluentNHibernate/fluent-nhibernate#430 > <https://github.com/FluentNHibernate/fluent-nhibernate/issues/430> > FluentNHibernate/fluent-nhibernate#429 > <https://github.com/FluentNHibernate/fluent-nhibernate/issues/429> > FluentNHibernate/fluent-nhibernate#456 > <https://github.com/FluentNHibernate/fluent-nhibernate/issues/456> > FluentNHibernate/fluent-nhibernate#432 > <https://github.com/FluentNHibernate/fluent-nhibernate/pull/432> > FluentNHibernate/fluent-nhibernate#453 > <https://github.com/FluentNHibernate/fluent-nhibernate/pull/453> > > This creates a very big problem with the community and a huge hole in the > continued use of new versions of nhibernate, since fluent-nhibernate is no > longer updated (issues of the problems above) > > Interesting to understand that the contributors are not missing, many pull > requests raised are not even viewed. > > The idea is forking fluent-nhibernate, eventually in the nhibernate > repository <https://github.com/nhibernate> (not inside nhibernate-core). > To continue to have the necessary support for at least nhibernate version > updates. > > I'm sure the community would cooperate a lot and be very happy about it. > > > -- --- You received this message because you are subscribed to the Google Groups "nhibernate-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to nhibernate-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nhibernate-development/59eb4946-db8f-4b32-ab89-ef4dca138d08n%40googlegroups.com.
