AsyncAPI Initiative
Replies: 12 comments 5 replies
-
|
Do you need a torch? 😄
|
Beta Was this translation helpful? Give feedback.
-
|
I need a YES or NO, please. I don't understand your message. Is it pass the torch to burn the shape-up-process repo or pass the torch to burn Fran for trying to get rid of the shape-up-process repo? |
Beta Was this translation helpful? Give feedback.
-
|
I mean, no matter what you burn, a torch will be handy 😆 just do not accidentally burn the roadmap 😉 |
Beta Was this translation helpful? Give feedback.
-
|
YES. Please proceed. |
Beta Was this translation helpful? Give feedback.
-
|
YES. RIP shape-up-process 😢 |
Beta Was this translation helpful? Give feedback.
-
|
Yes 👌🏼 |
Beta Was this translation helpful? Give feedback.
-
|
@fmvilas Where will these issues go? Will there be a new repo, a |
Beta Was this translation helpful? Give feedback.
-
|
They will be in their respective repos or in the community one if it doesn't make sense anywhere else. |
Beta Was this translation helpful? Give feedback.
-
|
Yes 👍, you can proceed. But to be honest, it was a good project to track down the goals and set the priority of goals on what to achieve first in the community. Although I also agree on the point that we can't make these strict deadlines in open-source, therefore we lost the progress and track on it. |
Beta Was this translation helpful? Give feedback.
-
|
Agree. That's going to be my next goal, Akshat. Giving y'all a clear vision of what's happening in the initiative. In the meantime, some folks are publishing updates of specific "areas", these may be helpful for you. |
Beta Was this translation helpful? Give feedback.
-
@asyncapi/tsc_members I would love to get rid of https://github.com/asyncapi/shape-up-process/ and https://shapeup.asyncapi.io. It was a great experiment but it failed miserably taking into account we want to involve the community in the development of the project and not everyone has the luxury to dedicate full-time to AsyncAPI. So hard deadlines are usually too much and have the opposite effect of what we want to achieve.
That said, I think it's a useful tool but definitely not related to AsyncAPI so I'm proposing here that we get rid of it and I'll keep a copy of it under my personal Github profile. I still want to use it for my personal to-do list.
It's not as easy as it sounds though. The roadmap is linked to this repo so, if we approve deleting this repo, I'll have to work on the migration.
❓ Do you accept that we get rid of it? Please comment with YES or NO, and feel free to ask any further questions.
As usual, I'll leave this question here for —at least— a week so everyone has a chance to reply.
Beta Was this translation helpful? Give feedback.
All reactions