seeking maintainers

[swyxio]

using TS-in-node is often quoted as a pain point for folks. as a beginning, it'd be good to just be the go-to resource for that, and then document next steps.

i'd also like to think about several categories of Node usecases from serverless node to node CLIs and so forth. we are more useful the more specific we are. our advantage is the flexibility and capability of documenting common user issues faster because of our dedication to TS, which is often not well covered in docs

[trivikr]

Interested ✋

[swyxio]

i gave you and @bnb admin rights, feel free to take as much leadership as you'd like on this one, i'm still focused on the react + TS cheatsheet but i can definitely be available for opinions and stuff.

[nerdeveloper]

I am also interested 💯

[swyxio]

done!

[KovacZan]

I am also interested in this. Looking forward to contribute to this organization's repositories.
I can also help you guys maintain this projects.

[sayantandasgupta]

Hello! I am interested in becoming a maintainer, and contribute to this organisation's repositories

[swyxio]

make a PR for the main things you'd change and i'll give it to you!

[sayantandasgupta]

Any particular format I should follow for listing the things I want to change/add? @sw-yx

[ronaldosc]

Interested here.. I see some new features become to Node.js that are not covered here,