AsyncAPI Initiative
Replies: 4 comments 4 replies
-
|
I like the idea @jonaslagoni suggested about using Cupid as the (or one of) source of truth for generating the visualization in the EDAVisualizer. I would also suggest we use Cupid's feature of generating a Mermaid diagram (plain text) as I believe it is a really great addition; people could embed generated diagrams all around in their markdown files for example, use it in presentations, etc. I don't know if I should vote 👍 or 👎 : I kinda agree to archive but only after integrated into EDAVisualizer. In addition, I would then suggest we add the effort of finding one more owner for EDAVisualizer. |
Beta Was this translation helpful? Give feedback.
-
why is this a condition? archive do not mean delete, code is still there, just in different organization.
please reach out EDAVisualizer maintainers - that is not related to
definitely mermaid and other features it already have are great! just to make it clear: the only reason to archive is not because the idea is bad, just there is noone who can drive it forward, and we need help cause now project is dead but being under our AsyncAPI org it adds credibility that I as added clarification to main description |
Beta Was this translation helpful? Give feedback.
-
👍 then, even though I don't like the fact they go into another org, but that's not the topic under discussion. I left my 👍 |
Beta Was this translation helpful? Give feedback.
-
|
@jonaslagoni there is no interest in taking over the project. I'm ready to move it to archive and we can bring it back whenever there are people that want to drive it forward on regular basis. I know you are interested in maintenance but not at the moment. I suggest we archive anyway. I really do not see point of keeping it here:
thoughts? |
Beta Was this translation helpful? Give feedback.
-
|
I saw that cupid was just mentioned in newsletter so suggest to wait max until the end of the month to make final decision so @jonaslagoni you also have time to figure out what you want to do |
Beta Was this translation helpful? Give feedback.
-
|
We can archive it, my only concern is that having it archived means more work whenever I do start focusing on it, and would probably just keep the code in EDAVisualizer... But yea, does not make much sense keeping it active when it's not for now. |
Beta Was this translation helpful? Give feedback.
-
|
yeah, tbh, I think all visualisation functionality, react or mermaid or anything else better to have in one repo as a lot of stuff will be shared anyway, and you will end up with some plugin concept so adding new formats, like plantUML or others will be a piece of cake |
Beta Was this translation helpful? Give feedback.
-
|
moved and archived -> https://github.com/asyncapi-archived-repos/cupid |
Beta Was this translation helpful? Give feedback.
-
The only maintainers of
cupidcan no longer support the project, this means we need to take action. More info: asyncapi-archived-repos/cupid#182Either we bring in new maintainers or move repository to https://github.com/asyncapi-archived-repos
the only reason to archive is not because the idea behind
cupidis bad, just there is nobody that can drive it forward and we need helpOnboarding new maintainers is possible as original creator is ready to support knowledge transfer.
We should have at least 2 new maintainers to push the project forward. And we need someone that understands EDA and AsyncAPI and can drive its development forward without mentoring.
@asyncapi/tsc_members Please react to this with 👍 if you agree, 👎 if you disagree or 👀 if you don't want to vote but want to signal that you're aware and have read this. Feedback is appreciated!
Also if you know someone that wants to be maintainers, or you know someone that depends on this library and wants to maybe sponsor it or I don't know. Just let us know.
Beta Was this translation helpful? Give feedback.
All reactions