AsyncAPI GitHub Organization cleanup - some repos should be archived

[derberg]

There are some repositories that are not active for very long, have no active maintainership, and we need to archive them:

• https://github.com/asyncapi/template-for-go-projects
  Reason: no active Go development, last active maintainer left the project

• https://github.com/asyncapi/parser-go and https://github.com/asyncapi/converter-go
  Reason: nobody contributes and maintains them actively. They were donated to AsyncAPI by my old team when I worked at SAP 6 years ago. I know the project I worked on do not use them. It is better to archive than keep such old projects that no other AsyncAPI project depends on.

• https://github.com/asyncapi/raml-dt-schema-parser
  Reason: we already did outreach on social media and newsletter for volunteers to take over, no luck, more info: I suggest we archive this repo raml-dt-schema-parser#255)

• https://github.com/asyncapi/simulator
  Reason: I tried to reach the maintainer multiple times on different channels, including LinkedIn. Last activity from the maintainer in repo was January 2024.

• https://github.com/asyncapi/glee
  Reason: Project has not been actively maintained for a few months. There was a discussion on its future but it didn't bring much: https://github.com/orgs/asyncapi/discussions/1861. Maintianers Fran and Souvik confirmed that probably the best is to archive the project.

What they have in common: No other AsyncAPI repo depends on the above repos. Except the RAML parser, but RAML is anyway in public archive for a year (https://github.com/raml-org/raml-spec) and not an open standard, and we gave lots of time to the community to voice their opinion that it is needed.

We would:

• archive them
• move to https://github.com/asyncapi-archived-repos

Remember: archive does not mean removal. Of course, if some projects are on NPM, they can still be used as dependencies (will be just marked as archived). And for go dependencies, it is even easier, as GitHub handles redirects like a pro.

---

@asyncapi/tsc_members I will not start with voting first. I will leave this issue open for next 2 weeks:

• so you can review the list
• you have time to talk with your managers (if you have one), if you want to invest in the project

Please do not suggest more repos to archive in this issue as it will cause communication chaos. As you can see in my explanation above, the repos I report here were carefully checked. Maintainers are aware (or I tried hard to reach them). These are "specific" projects and strategically not important.

If you think some other repo is not active, maintainers are away, then please start from an issue in the repo, like I did with asyncapi/raml-dt-schema-parser#255

[derberg]

It looks like no one is interested in taking over these repositories.

@asyncapi/tsc_members – please vote on the following proposal:

We move these repos to https://github.com/asyncapi-archived-repos

If any of the repos have packages published (e.g., on npm), we'll mark those packages as "deprecated" (unless there's a more appropriate status)

We’re not deleting the code — just moving it out of the main AsyncAPI GitHub organization. Anyone can still use it or continue working on it. If someone eventually maintains a project consistently and wants to join the AsyncAPI organization, they can apply and go through the usual review process.

/vote

[git-vote]

Vote created

@derberg has called for a vote on AsyncAPI GitHub Organization cleanup - some repos should be archived (#1948).

The members of the following teams have binding votes:

Team
@asyncapi/tsc_members

Non-binding votes are also appreciated as a sign of support!

How to vote

You can cast your vote by reacting to this comment. The following reactions are supported:

In favor	Against	Abstain
👍	👎	👀

Please note that voting for multiple options is not allowed and those votes won't be counted.

The vote will be open for 28days. It will pass if at least 51% of the users with binding votes vote In favor 👍. Once it's closed, results will be published here as a new comment.