Lukasz Gornicki
Lukasz Gornicki
@thulieblack please approve so we can merge. ### Summary of the vote Charter change requires 2/3 quorum: `A quorum of two-thirds is needed to amend this charter` 33 TSC members...
Communication almost ready: https://github.com/asyncapi/website/pull/4090 Preview link: https://deploy-preview-4090--asyncapi-website.netlify.app/blog/new-governance-board
@Nandgopal-R this is the issue you can work on, that I mentioned in https://github.com/asyncapi/community/pull/1776
@Nandgopal-R any progress?
go ahead - just sync with codeowners from diff, optimizer and bundler. but I believe it will significantly make work easier, updates easier, and collab easier. you will only have...
When you work on a final PR to move a project inside CLI, I recommend approach that I take in generator, to use https://github.com/newren/git-filter-repo to move the code with all...
yeah in case of server-api I would not be surprised if you actually rewrite it instead of migrating, but yeah, others like optimizer, diff, bundler definitely needs this approach
I like the idea. We should definitely not hide this info in any environment variables as this must be easy to update by anyone through PR. Maybe we could use...
ok, fragments will not work, this update of version is needed not only in docs like https://github.com/asyncapi/website/blob/master/pages/docs/concepts/protocol.md but also JS files. non, fragments nor env variables will really work 😞...
but how does it work in markdown files? JS is not a problem