The future of Mantine DataTable #450
Pinned
icflorescu
announced in
Announcements
Replies: 1 comment 4 replies
-
Hello ! |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear community members,
As most of you already know, Mantine v7 came up with a significant number of breaking changes, most of them referring to how styling is implemented.
As some of you know,
mantine-datatable
is one of my dearest open-source projects, has quite a large code-base, and while it has nearly 700 GitHub stars and 40k npm downloads per month as of November 2nd 2023, I'm still struggling with raising enough funds to be able to dedicate as much time as I'd like to the project, despite the fact that it's being used by lots of startups and developers worldwide.A lot of you were looking forward for the new version supporting Mantine V7, which, after more than a month of assiduous work, finally came out yesterday, partly due to the generosity of some members who were kind enough to contribute financially towards the goal.
I must, however, point out the fact that - according to my calculations - less than 25% of the effort behind the upgrade process was financially compensated one way or the other. That's without even taking into consideration the entire 13 months long project lifespan prior to that.
I've been around a while, so I know that all open-source creators face similar issues. I also know it from my own experience. Mantine DataTable is one of my dearest open-source projects, but not the only one. I'm also the guy behind Mantine ContextMenu, tRPC-SvelteKit, PocketBaseUML, Expose-WSL, IISExpress-Proxy and a few others, not to mention the contributions I'm constantly making to other people's or organizations' repos. While I don't do it primarily for money, I need money to support my existence, as everyone else does.
Please understand that this is not a rant - I'm simply pointing the facts here. I'll do my best to keep maintaining the package, come up with new features and fixing bugs as they emerge, but I can't do it without your support.
I need your help.
A couple of companies backing up the project on a monthly basis, or one company that uses the component and hires my services would do wonders for future of the project on the longer term.
Code contributions are also welcome, and hopefully contributing should be easier starting with V7, following the major repo overhaul.
Thank you all for your patience and support!
Huge thanks to @john-latham for being the major financial contributor to support the V7 release 🙏❤️🙏
Special thanks to @KevinVandy, @hughfitzgerald, @simeq, @onlyice, @grahampcharles, @DoubleJ-G, @otobot1, @Mikkelzu, @blentz100, @beeman, @ericschmar, @aniravi24, @JitPackJoyride, @johnzanussi, @rakutek, @petrvecera, @usequantumai, @israelins85, @ecatugy, @zeitderforschung, @Emil-Sorensen, @stefanomarra, @alexcastrodev, @samueldobbie and other people who sponsored me in the past, plan to sponsor me in the future, or contributed code to the repository (apologies if I omitted anyone).
Beta Was this translation helpful? Give feedback.
All reactions