Comments (7)
I do not think it is good solution for this repository.
Same for bindings
and spec-json-schemas
.
All these 3 are interconnected - if someone becomes a maintainer in spec
, they are also maintainers in bindings
an spec-json-schemas
. This is a complex setup, not as simple as in website
or asyncapi-react
repos.
also, stuff we started in website
is pretty fresh, and we do not even know if it works: asyncapi/asyncapi-react#928 (comment)
In my opinion we need a different approach here and in related repos. Maintainers should be responsible for triage to give proper attention of someone who is experienced with AsyncAPI:
- we can do triage duty schedule, every month different maintainer does triage, and than hands over to another one with report of issues that were closed or something like that
- we can have a regular monthly triage call that would actually put us in sync and enable more regular and proactive approach to minor releases
- maybe we even should consider merging
bindings
,spec-json-schemas
and evenextensions-catalog
intospec
repo. We discarded it some time ago and pulledspec-json-schemas
outsidespec
because we were afraid of complexity of releases but I think recent years showed, we did not remove release complexity and only introduced maintenance complexity
spec
is the backbone on AsyncAPI Initiative and if we want to make changes like that, I prefer to have a meeting first and discussion.
And if you still want Triagers
and Committers
then please provide examples how that would look like. Is there even a candidate that we could onboard? and would that be triager for all repos? what about bindings, where we have "champions-like" setup similar to Modelina. I just do not see what problem it is solving.
from spec.
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
from spec.
I love this idea. As a maintainer, this has my +1! 🙌
Pinging other maintainers of this repo: @fmvilas @derberg @dalelane @char0n @GreenRover
Additionally, once this gets accepted, I volunteer to create the PR with the changes needed in the CODEOWNERS file.
from spec.
we did not remove release complexity and only introduced maintenance complexity
😆
All these 3 are interconnected - if someone becomes a maintainer in spec, they are also maintainers in bindings an spec-json-schemas.
Ahh, got it, makes complete sense why you don't feel it's a similar example to the website repo. Def more complex.
side note... @derberg it sounds like you lost enthusiasm in your triager/committer proposal idea, do you regret proposing it originally for website repo? hehe 😄
from spec.
I retract my vote. Reasons and discussion regarding my vote retraction can be found in asyncapi/spec-json-schemas#492 (comment)
from spec.
side note... @derberg it sounds like you lost enthusiasm in your triager/committer proposal idea, do you regret proposing it originally for website repo? hehe 😄
no, I love it, I just do not think it is a silver bullet solution for all. And anyway, we just started in website, we need to see some numbers, get feedback from participants, etc and then we can promote it
from spec.
It sounds like we didn't get the number of votes, so this motion won't pass this time around 😸
Closing.
from spec.
Related Issues (20)
- Invite Heiko Henning to join as code owner HOT 11
- Should the Reply Object extend from the Operation Object? HOT 5
- Channel parameter type HOT 2
- Send/Receive again confusion HOT 3
- AsyncAPI v3 retrospective HOT 1
- Undefined description when using `OneOf`, `AllOf` or `AnyOf` HOT 3
- Undefined behaviour of "messageId" for Message Traits and Messages defined in components. HOT 4
- Avro specification inside AsycnApi file HOT 4
- Server Object host field compatibility with protocols HOT 3
- testing -input command not found HOT 2
- Possible bug with example - adeo-kafka-request-reply-asyncapi HOT 18
- Decide what to do with OAS schema properties HOT 5
- Allow plain `string` in Message Example Object field payload for non-json payloads (like xml, yaml) HOT 7
- when to finish amqp serverBindings HOT 2
- How to define MQTT User Properties in an AsyncAPI document? HOT 2
- Extend Avro and OpenAPI schema versions HOT 13
- Multiple reply addresses HOT 2
- Can i document an endpoint for a cron job? HOT 2
- trait vs. allOf ref vs. component ref - CloudEvents HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spec.