Add @remcohaszing as a merger of several orgs

[remcohaszing]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and couldn’t find anything (or linked relevant results below)
• If applicable, I’ve added docs and tests

Problem

See Motion to nominate a maintainer for more information.

See recent work

I also maintain a couple of unified related projects outside of unified.

• remcohaszing/estree-util-module-to-function
• remcohaszing/estree-util-value-to-estree
• remcohaszing/monaco-unified
• remcohaszing/recma-nextjs-static-props
• remcohaszing/rehype-mdx-title
• remcohaszing/remark-mdx-code-meta
• remcohaszing/remark-mdx-images
• remcohaszing/remark-mdx-frontmatter
• remcohaszing/remark-mermaidjs
• Add mdx language microsoft/monaco-editor#3096

Solution

@unifiedjs/core Please vote (up/downvote this issue or leave a comment)

Alternatives

n/a

[wooorm]

Exciting! You’ll get the proper rights everywhere somewhere in the next 24 hours!
Please let me know if you have any questions :)

[JounQin]

I also maintain a couple of unified related projects outside of unified.

Maybe some related projects can also be transferred into organizations? (You'll lose the release permissions if you do so, like un-ts/remark-preset-prettier#96)

[wooorm]

Maybe some related projects can also be transferred into organizations

Definitely up for that: some project can indeed be moved into the organizations.

I do want to note that projects can be maintained, very well, outside of organizations.

A little bit about that is written in organizations.md:

Projects relating to the areas covered by the collective can be governed inside or outside of the collective: anyone can develop, maintain, manage, and self-govern projects.

Projects can flourish whether they are governed by the collective or not. But wilting projects reflect badly on the collective as they provide a bad user experience. Signs of a wilting project are, for example, that issues are left unanswered or that dependencies are outdated.

https://github.com/unifiedjs/collective/blob/main/organizations.md#projects

---

For example, I maintain remark-preset-wooorm on my own user account. I also maintain many other packages myself that are also used in unified.

Joun, as you mention, permissions are indeed pretty strict inside unified: not everyone has them.

Other than permissions, there are also some style choices that correspond with being inside unified. Most projects inside unified are very consistent, use the same tooling, use the same sections and fields. Use TypeScript through JSDoc. Are maintained for 10+ year already and are very stable.

While not all of these are required, I think it is very important for everything inside unified to be:

• consistent
• documented the same
• maintained the same
• use the same tools

If someone wants to do things their own way, they can maintain things outside of the organizations, and that’s fine!

This helps users figure out what they need. And it helps other maintainers to come in and make changes if needed.

[JounQin]

@wooorm The big difference between remark-preset-wooorm vs remark-preset-prettier is that remark-preset-wooorm is absolutely a personal preset while remark-preset-prettier is a standard and user independent.

So in my eyes, projects without personal taste should all be included into the organizations. Loosing permissions is always fine to me because we trust between each other.

For maintaining, the active maintainer's preference should be considered first IMO. And tools can change later if new maintainer want to help.

Because, the current workflow of unified is actually still your preference, that does make sense because you're maintaining most of the repositories.