Project maintenance status / migrating to an org

[kachkaev]

Is your feature request related to a problem? Please describe.

👋 @francoismassart! I wonder what your thoughts are on moving this repo to @eslint-community:

The goal of this organization is to have a place where community members can help ensure widely depended upon ESLint-related packages live and never fall out of maintenance.

Describe the solution you'd like

It’d be great to see this repo actively maintained – it’s highly valuable and rather popular on npm!

At the time of writing, it’s been nearly half a year since the the latest release (v3.13.0). There are a several issues where folks struggle to get support from the maintainer (e.g. #276 (comment), #280 (comment), etc.).

Describe alternatives you've considered

• Pinging @francoismassart in [Feature request] Automatic whitespace removal #263 (comment)

• Forking (but that’s worse than moving this repo to @eslint-community in collaboration with @francoismassart).

Additional context

@francoismassart, please don’t treat this issue as a complaint about your unavailability. This package is open-source and you owe people nothing; there is no obligation to be actively involved in it. We all have duties in our lives, and it’s impressive when someone manages to kick off an amazing project like this one. eslint-plugin-tailwindcss is one of my favourite discoveries of 2023. Huge kudos to you!

---

cc @aladdin-add, @MichaelDeBoey, @ota-meshi and @voxpelli (from @eslint-community description)

[voxpelli]

This would be a first for a framework specific plugin I think for the ESLint Community, but I guess that's still possible

Requires some additional knowledge in the framework itself and on the continued popularity of the framework itself

Another possibility I guess would be for the tailwind community to maintain this? Maybe that would be even better?

[kachkaev]

Another possibility I guess would be for the tailwind community to maintain this? Maybe that would be even better?

@tailwindlabs / @adamwathan WDYT?

[ferdicus]

kind of unrelated, but i just want to commend you @kachkaev on the wording of this ticket 🙇🏿

[hasparus]

would be nice to make it community maintained.

Maintaining open source can be quite a time sink, and sharing the burden helps everybody.

It is a great plugin. Huge thanks to @francoismassart for building it!

[hyoban]

@francoismassart Hi. I am very willing to join the maintenance of this plug-in, whether it is transferred to the eslint community organisation or not.

• I have created two pr to solve the problem I encountered in using this plug-in. fix: no-custom-classname false negatives with nativewind #392 fix: load correct tailwind config in monorepo #389
• I am very familiar with how to use tailwind api. I created a vscode plug-in for highlighting classname, which supports both v3 and v4. https://github.com/hyoban/tailwindcss-classname-highlight
• I rely on this plug-in in the project, so I have enough motivation to maintain it. I can handle daily pr and issue, and I can also provide v4 support for this plug-in.

I am looking forward to your reply.

[ziyuang]

What will happen if we never receive the response from François?

[hyoban]

I am currently trying to support Tailwind v4 in my forked repository (it also supports v3). You are welcome to try and give feedback.

• refactor!: move to tailwind api utils, tailwind v4 support hyoban/eslint-plugin-tailwindcss#3