Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove all JSON Schema files after spec 3.0 release #183

Closed
jonaslagoni opened this issue Feb 2, 2023 · 10 comments · Fixed by #184
Closed

Remove all JSON Schema files after spec 3.0 release #183

jonaslagoni opened this issue Feb 2, 2023 · 10 comments · Fixed by #184
Labels
enhancement New feature or request stale

Comments

@jonaslagoni
Copy link
Member

Reason/Context

After spec 3.0 release all schema files will be located in the spec-json-schema repository, where all codeowners for the bindings will also become codeowners for their respectful bindings.

https://github.com/asyncapi/spec-json-schemas/tree/next-major-spec/bindings

Therefore we need to remove the schema files from this repository.

@jonaslagoni jonaslagoni added the enhancement New feature or request label Feb 2, 2023
@jonaslagoni
Copy link
Member Author

This issue closes #113 as well.

@sambhavgupta0705
Copy link
Member

Hi Jonas I would like to work on this one.

@sambhavgupta0705
Copy link
Member

sambhavgupta0705 commented Feb 5, 2023

@jonaslagoni to resolve this issue I need to remove folders like this
https://github.com/asyncapi/bindings/tree/master/ibmmq/json_schemas?

@jonaslagoni
Copy link
Member Author

Yes exactly 👍

Remember this will most likely not be merged until after the spec 3.0 release in June 🙂

@sambhavgupta0705
Copy link
Member

okay so you are saying that this will be merged after spec 3.0 release in June?

@jonaslagoni
Copy link
Member Author

Yes, so you can start the PR up with no problem, but don't expect much activity before that 🙂

@sambhavgupta0705
Copy link
Member

okay no issues with that.

@github-actions
Copy link

github-actions bot commented Jun 6, 2023

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale label Jun 6, 2023
@sambhavgupta0705
Copy link
Member

Still relevant

@github-actions github-actions bot removed the stale label Jun 7, 2023
@github-actions
Copy link

github-actions bot commented Oct 6, 2023

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants