This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improving the communication with the community in a more transparently way #5719
Comments
I want to express gratitude for the incredible work you've done in maintaining Lodash over the years. It's no small feat, and Lodash remains an essential utility for countless developers. I understand that dealing with a large number of GitHub issues can be overwhelming, especially when many of them are discussions rather than actual bug reports. To help maintain a productive community around Lodash, I may offer some suggestions: Communication Channels: Automate Repetitive Tasks: Moderation and Labeling: Issue Templates: By the way, I'd like to point out that Lodash is still recognized as the number one JavaScript utility library according to lodash vs underscore vs ramda. This reflects its importance within the JavaScript ecosystem. Thank you for your hard work to the Lodash project. |
As @Shinigami92 and @cwtuan said. lodash has been the missing utilities lib that I use in all of my projects. Much love and appreciation for all the hard work and thankless contributions. Hoping to see v5 and would be glad to contribute into having discussions around optimisations for various runtime flavours. Keep up the good work everyone! |
Improving engagement is a great goal. Realistically I'll be
Lodash 4 will get surgical, handcrafted updates that will aim to preserve existing compat. A lot of benefit can be had for making non-breaking tweaks there. Lodash 5 (main branch) will be where the newer work occurs. |
Thanks for the kind words y'all ❤️ |
I've turned on the "discussion" feature ✅ |
I didn't know that and I feel sorry for you that you ran into a burnout But let me tell you: try to built up a community and find people that help you in the project A Discord-Server is a first good start (=> #5722) At first it might sound like a lot of work to build up a community, but some day it pays back I know what I'm talking about, because I'm in huge ecosystems like Vite, Faker, the Antfu-universe and also I participate in other Vue related communities like Quasar and so on Another idea should be to open up a https://opencollective.com page so the community can pay some money for the great work Sadly it looks like someone already claimed https://opencollective.com/lodash so you would need to claim that back or just name it differently An example of what you could use opencollective: also here is a doc for how to pin an issue: https://docs.github.com/en/issues/tracking-your-work-with-issues/pinning-an-issue-to-your-repository |
Lodash is a widely used front-end library, thanks to the hard work of @jdalton! I'm glad lodash has plans for a new version! In fact, my team is also heavily using lodash, so we're very happy to see that. |
I recommend checking out Dosu. Dosu helps open source maintainers encourage contributors, organize issues, triage bugs, answer questions, and more. See it in action: run-llama/llama_index#7666 (comment) |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hello @jdalton 👋
I would like to suggest to improve the communication with the lodash community with some more or less simple changes
I just assume and find out that lodash is now working on a full rewrite on v5 driven by Bun support
I support that! lodash is used by MANY packages and nearly every project feels like having a 50% that any sub-dependency contains lodash somehow.
With that responsibility the lodash maintainers should try to not mess with their community.
Maybe I'm biased about such radical changes due to I'm the maintainer of a repo that we took over due to a radical situation... but I just want a healthy community 🤗
The text was updated successfully, but these errors were encountered: