-
-
Notifications
You must be signed in to change notification settings - Fork 639
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
Introducing a Dedicated Design Issues Section on the AsyncAPI GitHub Issue Page #1721
Comments
@Mayaleeeee |
I think it makes sense, just please define what content you'd like to have in it, and if you want normal view like with |
Hi @derberg
|
yes, exactly, so do you want just classic text with explanation, or the form-like approach |
The two look good, but I prefer the form-like as it is more specific and direct. What do you think? |
@Mayaleeeee if you need project board then do it, but I'm not very helpful here as I do not use it. Check with @alequetzalli that does it for docs or @fmvilas that also used it in the past I think |
Thanks @derberg |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
still valid? @Mayaleeeee |
Yeah. |
@Mayaleeeee what's the udpdate of this issue? |
Thanks for the pinging @sambhavgupta0705 @AnimeshKumar923, you showed interest earlier, and I'm following up to see if you've had a chance to work on it. If not, no worries, just wanted to check in. |
Hi @Mayaleeeee 👋 I was checking up earlier because I got the stale notification brought up by the bot comment. Regardless, I find this as a new addition to the issue section. I would be happy to work on this if you can describe what I've to do in order to setup a new design section in the As far as I've understood, we need to add a new YAML file here containing the requirements for Please elaborate on this further and we can get started on this issue... 👍 |
@AnimeshKumar923 this will work |
Will do this. Currently on a break due to final end semester exams till 25 May. |
Thanks for the update @AnimeshKumar923 |
Hello @AnimeshKumar923 |
Thanks for the ping @Mayaleeeee 👍 |
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Reason/Context
I propose the addition of a dedicated Design Issues section on the AsyncAPI Issue page hosted on GitHub. This section serves as a platform for addressing and discussing design-related concerns within the AsyncAPI project. By incorporating this dedicated section, we can efficiently gather and collaborate on design issues, ensuring their visibility and fostering constructive conversations among contributors.
One of the key motivations behind this proposal is to alleviate the confusion when reporting design-related problems. Currently, while creating an issue on the platform, there are options for bugs, documentation reports, and other categories. However, a more straightforward choice for reporting design issues that require attention is needed. This poses challenges for both new and experienced contributors.
Introducing a dedicated design issue section aims to streamline the process, making it easier for all contributors to report design-related concerns. It will provide a clear and accessible option for raising design issues that require resolution. Ultimately, this addition will enhance the overall user experience, promoting effective collaboration and problem-solving in design.
Description
What changes have to be introduced?
The proposed change is to include a section specifically dedicated to Design Issues on the AsyncAPI Issue page on GitHub.
Will this be a breaking change?
No, this change is not expected to be a breaking change. It aims to enhance the issue page by adding a dedicated section for design-related concerns.
How could it be implemented/designed?
The implementation would involve modifying the structure of the AsyncAPI Issue page on GitHub to incorporate a distinct section for Design Issues. This section would allow contributors to raise and discuss design-related matters, providing a platform for collaboration and problem-solving in that specific area.
@thulieblack @derberg @AceTheCreator @fmvilas @akshatnema
The text was updated successfully, but these errors were encountered: