feat: blog: ESLint Community org announcement

src/_data/all_authors.json

@@ -163,5 +163,16 @@
         "twitter_username": null,
         "github_username": "sanjeetsuhag",
         "location": "United States"
+    },
+    "MichaelDeBoey": {
+        "username": "MichaelDeBoey",
+        "name": "Michaël De Boey",
+        "title": "ESLint Community core team",
+        "website": "https://michaeldeboey.be",
+        "avatar_url": "https://avatars.githubusercontent.com/u/6643991?v=4",
+        "bio": "👨‍💻 Freelance full stack JavaScript/TypeScript & React engineer",
+        "twitter_username": "MichaelDeBoey93",
+        "github_username": "MichaelDeBoey",
+        "location": "Sint-Niklaas, Belgium"
     }
 }

src/_includes/partials/author_bios/MichaelDeBoey.md

@@ -0,0 +1 @@
+👨‍💻 Freelance full stack JavaScript/TypeScript & React engineer

src/content/drafts/eslint-community-org.md

@@ -0,0 +1,131 @@
+---
+layout: post
+title: Announcing the ESLint Community GitHub organization
+teaser: >-
+  The ESLint Community GitHub organization is a place for important ecosystem
+  projects to get the attention and support they deserve.
+tags:
+  - eslint-community
+  - Updates
+authors:
+  - MichaelDeBoey
+categories:
+  - Announcements
+---
+
+In our
+[2022 year in review](https://eslint.org/blog/2023/01/eslint-2022-year-review),
+we briefly mentioned a couple of project kickoffs, and we're excited to now
+announce the official
+[ESLint Community GitHub organization](https://github.com/eslint-community).
+
+The strength of ESLint is in its ecosystem, and we continue to investigate
+different ways of further supporting that community. We began by
+[donating to community projects](https://eslint.org/blog/2022/02/paying-contributors-sponsoring-projects/#supporting-the-community),
+to ensure that high-value projects were receiving the funds they needed to
+continue with ongoing maintenance and development. Our next step is to create
+the `@eslint-community` GitHub organization as a home for high-value projects in
+the ESLint ecosystem.
+
+As you can read in the
+["`@eslint-community` GitHub organization" RFC](https://github.com/eslint/rfcs/tree/main/designs/2022-community-eslint-org),
+the goal of this new 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.  
+The Community Core team (which currently consists of
+[`@aladdin-add`](https://github.com/aladdin-add),
+[`@ota-meshi`](https://github.com/ota-meshi),
+[`@voxpelli`](https://github.com/voxpelli) & myself
+[`@MichaelDeBoey`](https://github.com/MichaelDeBoey)) & all package maintainers
+will make sure these packages stay up-to-date with newer ESLint releases, and
+they don't hold the wider community back by depending on a single person's
+GitHub or npm Registry account.
+
+You might have noticed that some of your most beloved ESLint-related packages
+have already been moved over to or been forked by the `eslint-community`
+organization. A full list of the current projects include:
+
+* [`eslint-formatter-codeframe`](https://github.com/eslint-community/eslint-formatter-codeframe)
+  &
+  [`eslint-formatter-table`](https://github.com/eslint-community/eslint-formatter-table)  
+  We took these over from [@fregante](https://github.com/fregante)
+* [`eslint-plugin-eslint-plugin`](https://github.com/eslint-community/eslint-plugin-eslint-plugin)  
+  [@aladdin-add](https://github.com/aladdin-add),
+  [@bmish](https://github.com/bmish) &
+  [@not-an-aardvark](https://github.com/not-an-aardvark) transferred this repo
+  to the new org, but they're still maintaining it
+* [`eslint-plugin-promise`](https://github.com/eslint-community/eslint-plugin-promise)  
+  We took this one over from [@xjamundx](https://github.com/xjamundx)
+* [`eslint-plugin-security`](https://github.com/eslint-community/eslint-plugin-security)  
+  We took this one over from the
+  [@nodesecurity](https://github.com/nodesecurity) team, but
+  [@nzakas](https://github.com/nzakas) is still maintaining it
+* [`eslint-plugin-eslint-comments`](https://github.com/mysticatea/eslint-plugin-eslint-comments),
+  [`eslint-utils`](https://github.com/eslint-community/eslint-utils) &
+  [`regexpp`](https://github.com/eslint-community/regexpp)  
+  We created a fork from [@mysticatea](https://github.com/mysticatea)'s repos &
+  published them under the
+  [`@eslint-community` npm Registry organization](https://npmjs.com/org/eslint-community).
+
+We also intend to fork, bring up to date, and publish the following packages
+originally authored by [@mysticatea](https://github.com/mysticatea) as well:
+
+* [`eslint-plugin-es`](https://github.com/mysticatea/eslint-plugin-es)  
+  We'll work on getting all
+  [`eslint-plugin-es-x`](https://github.com/eslint-community/eslint-plugin-es-x)
+  features merged as well
+* [`eslint-plugin-node`](https://github.com/mysticatea/eslint-plugin-node)  
+  We'll work on getting all
+  [`eslint-plugin-n`](https://github.com/eslint-community/eslint-plugin-n)
+  features merged as well
+
+Of course, we don't want to stop there.
+
+If you think your project would be a good fit for the new community org, *or*
+you're depending on a project that's currently unmaintained & want to have the
+community to take it over, you can contact the Community Core team on
+[the official ESLint Discord](https://eslint.org/chat).
+
+Keep in mind that we'll only be able to take over projects that are adhering to
+the following acceptance criteria:
+
+* Is it a package that is ESLint-related?  
+  Mostly this will be ESLint plugins, but (unmaintained) dependencies of such
+  packages, closely related packages or packages split from the main ESLint repo
+  (like
+  [`eslint-formatter-codeframe`](https://github.com/eslint-community/eslint-formatter-codeframe)
+  or
+  [`eslint-formatter-table`](https://github.com/eslint-community/eslint-formatter-table))
+  or used by the main repo (like
+  [`eslint-utils`](https://github.com/mysticatea/eslint-utils) &
+  [`regexpp`](https://github.com/mysticatea/regexpp)) could go in the
+  `@eslint-community` GitHub organization as well.
+
+  Because plugins can expose their own (recommended) configs, we already accept
+  config packages in some way.  
+  However, the community core team won't be eager to accept shared ESLint config
+  packages, as they can be very opinionated.
+
+  It also doesn't matter if the package is purely TypeScript-related or not, as
+  we don't want to fragment the ESLint community more without any real benefit.
+
+* Is it widely depended upon throughout the ESLint community?  
+  We don't have a real number in mind here, but the packages we currently took
+  over (or that we're planning to take over) almost all have at least 3M
+  downloads/week.
+
+* Is it currently unmaintained?  
+  We don't want to take over packages that are still maintained by their
+  original author(s), as that would be a waste of time for everyone involved.
+
+These criteria aren't written in stone, but they're good guidelines to see if we
+should take over a package or not.
+
+If we decide to take over a package, but we can't get into contact with the
+owner of the repo to transfer ownership over to the new GitHub organization, we
+will (temporarily) fork the repo & publish it under the `@eslint-community` npm
+Registry organization. However, the ultimate goal will always be to transfer the
+original repo.
+
+If you have any further questions, feel free to ask them on
+[the official ESLint Discord](https://eslint.org/chat).