Invitation to move to official `eslint-community` org about eslint-plugin-markdown HOT 8 CLOSED

Yeah, I don’t think it’s worth moving eslint-community under Open JS. There’s not a lot of value there.

from eslint-plugin-markdown.

I’m not sure we actually can transfer this over. Because this is part of the Open JS IP, it requires the Open JS CLA be signed for all contributions, and that bot only works on a per-org basis, not a per-repo basis.

So we either need to leave the repo where it is or else create a separate fork in the eslint-community org that would effectively be a different package. For the time being, it seems like leaving things as-is is the best choice.

from eslint-plugin-markdown.

@MichaelDeBoey when other folks extract code from our repo and set up a different repo (which they are allowed to do by the license), that becomes a separate project that can be run separately. It’s the transferring of an existing repo that brings over all the overhead.

@snitin315 my understanding is that the Open JS CLA checker applied to every repo in an org, you can’t just pick one or two.

from eslint-plugin-markdown.

How would this impact extracting things for the main repo, like we did in v8 with eslint-formatter-codeframe & eslint-formatter-table?

from eslint-plugin-markdown.

@nzakas @MichaelDeBoey For webpack, we have set up Open JS CLA for both webpack and webpack-contrib organization. Maybe we can enable the CLA bot for eslint-community similarly.

from eslint-plugin-markdown.

@nzakas yes it'll be applied to all repositories. @MichaelDeBoey Is it possible to move other repositories under Open JS?

from eslint-plugin-markdown.

@snitin315 If you mean if it's possible to add @eslint-community under Open JS, I don't know if we want that tbh.
That is something we should discuss together with the ESLint team

from eslint-plugin-markdown.

Let's close this one then.

from eslint-plugin-markdown.