Looking for a maintainer

tldr: We are looking for a new maintainer to provide support to hive project. If you're interested please comment bellow.

A bit of backstory if you're interested

I (@themisir) was doing some light maintenance for last year and a few months maybe. I wanted to keep hive alive and provide stability to existing feature set, because back in time I have been running a small company that was using hive on its mobile apps, and I thought why not provide support instead of moving away, actually eventually I moved away from hive on those apps to store data on server side, but I still wanted to provide support to give back some value to the community I'm myself getting value from. But we had to close that company alongside with apps and a few months ago I moved away to work on another company with different tech stacks. After moving away I lost my interested in flutter ecosystem as I am mainly working on much low level programming with different toolset.

Hive was actually pretty interesting project for me, It had taught me really interesting concepts, and forced me to explore more about stuff like serialization and working with binary data, data recovery, encryption and other "fun" stuff. But that's not enough to keep myself engaged with this project and I no longer able to provide required support to this project.

I am sorry for not being able to provide value this project deserves, so after talking to Simon we decided to look for another maintainer. If you're interested, you think you can provide some value please comment below.

My personal suggestions to the future maintainer:

- Please make sure API stays stable, If you need hive-2.0 call it something else and release as a separate project, but I don't think any user would enjoy process of migrating from one database to another one. Even if you keep core features same, changing a simple API will break someone else's workflow, so be sure to keep public api stable. [check this out](https://youtu.be/Pzl1B7nB9Kc?t=174) also [related xkcd](https://xkcd.com/1172/)
- You don't have to add new features to keep hive alive. I know a new shinny feature will boost popularity, but I think as a database hive is currently in a good spot right now. It can store data, and it can serialize complex objects. If you want to implement a new feature (eg let's say cloud sync), adding it as an extension / additional package would be more fit than modifying core package. So users can able to opt-in / opt-out if they want to.

Please note that those are just my personal thoughts, not any sort of strong rules to follow.

No files, tests, or entry points are named. Start by reviewing the Hive project and its open maintenance needs, then assess whether you can provide ongoing support while preserving the public API; done means taking responsibility as a maintainer rather than completing a discrete patch.

Written by the indexing model from the issue text.