-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
change ownership #218
Comments
Ok, no response @Pakisan do you join alone or someone from essential building blocks working group joins you? |
@derberg as I know, I'm the only one for now I have a plans to start working on TCK in May @jonaslagoni do you want?) |
As of now, not really no. Maybe in the future, but lets see 🙂 @asyncapi/essential_building_blocks_wg anyone interested? |
@Pakisan good luck mate |
I remember a bit the scope of the project as I contributed here few years ago, so know the idea behind it, in case you need some help - lemme know |
Hey @gutee @jstoiko @looseale
This repo was not maintained for very long time and we need it to evolve testing capabilities for parsers and json schema.
one of TSC members, @Pakisan, is open to jump in as maintainer
Pavel did a lot of work for v3 on java tooling side, working with custom examples to have good tests coverage -> https://github.com/asyncapi/jasyncapi/tree/master/asyncapi-core/src/test/resources/examples
From what I know @jstoiko is not involved in mulesoft and probably AsyncAPI as well so can be removed
I just do not know what is @gutee and @looseale status. I could not find you in slack. Will try to find you on LinkedIn.
Since this repo is not maintained for that long, I assume you do different things and @Pakisan can just take over the repository. We will wait 14days for your response
The text was updated successfully, but these errors were encountered: