Transform to the community repository

[yhatt]

Marp team has some mainstream projects to have to maintain, so we could not take time for substream projects such as Marp Web and React/Vue integrations.

And they had not received feedback as much as we had expected.

• Marp Web has seen as not valuable because we already have a polished Marp for VS Code. And user can try to use this extension through Web, powered by Visual Studio Codespaces.
• We expected to grow the developer community with React/Vue integrations but there are only a few enthusiastic people. Marp team is not using them in anywhere so they have no affect to our mainstream projects even if we stopped publish.

This fact shows in-development projects are not too have worth maintaining them as our mainstream. Thus, we are considering to translate in-development projects into the community repository.

Please leave a comment to this thread if you have interested in maintaining this as a community project.

Note

• To show our attitude, we have no longer accepted any pull requests into Marp Web/React/Vue in @marp-team organization.
• Marp team requires a constant quality to belong repository into our organization. We would rather create a fork in community-land than keep the repo at @marp-team.
• We will archive our substream repositories if a clarified community repository was created.

Looking for the community leader also in marp-team/marp-vue#14.

[exKAZUu]

Thank you for develpoing the great package.
For your information, I plan to maintain my fork of marp-react because it is still valuable in our work. But, I'm not sure it can be one of good community repositories. The fork will probably focus on satisfying our needs.