Why use GitHub discussions? And how?

[IshitaTakeshi]

1. I made a chart to clarify the usage of Issue and GitHub Discussions. Is this correct? Still the last part "???" is ambiguous for me though...
2. Why do you use both GitHub Discussions and Issues? I think most of the existing OSS projects (such as Rust) use only issues and assign labels based on the issue category

Did you find a software bug?
    -> Yes
        Open an issue
    -> No
        Do you want to add new features to Autoware?
        Yes ->
            Do you have a clear vision of the function you want to add?
            Yes ->
                Make a feature request
            No ->
                Ask in Q&A
        No ->
            ???

[kenji-miyake]

@IshitaTakeshi

I made a chart to clarify the usage of Issue and GitHub Discussions. Is this correct?

It's explained here.
https://autowarefoundation.github.io/autoware-documentation/main/help/support-guidelines/

I think it's not correct.
If it's a feature request, please open a feature request thread, not Q&A.

Still the last part "???" is ambiguous for me though...

So what do you want to do here? 🤔
It's not a bug and not a feature request, what's that? I couldn't understand it.

Why do you use both GitHub Discussions and Issues?

Autoware.Auto used GitLab Issues for bugs and ROS Answers for questions.
https://autowarefoundation.gitlab.io/autoware.auto/AutowareAuto/support-guidelines.html

I've just replaced ROS Answers with GitHub Discussions.

Why Autoware.Auto did so is, I guess, it's in order to filter issues/questions without adding labels, which makes the maintenance easier.

I think most of the existing OSS projects (such as Rust) use only issues and assign labels based on the issue category

Do you believe you can find out an appropriate issue from the numerous numbers of issues?
I don't think so. Fewer issues are more maintainable.

[kenji-miyake]

And if you google for example "github discussions vs issues", you can find some articles.
Please refer to them as well.

https://resources.github.com/devops/process/planning/discussions/

[IshitaTakeshi]

So does it become like this?

Did you find a software bug? -> Open an issue in the corresponding software repository

Did you find strange behavior? -> Ask in Q&A

Do you have questions about Autoware functionality? ->  Ask in Q&A

Do you want to add new features to Autoware? -> Make a feature request

[kenji-miyake]

@IshitaTakeshi Yeah, exactly!

[IshitaTakeshi]

Can I add the chart above to the contribution guideline?
The current guideline page shows what Autoware has for the support (Discussions, Issues), but I think contributors want to know what they should choose based on the contribution type.

[kenji-miyake]

Sorry, but I think it's not good to add chats to the documentation.
Instead, could you update the documentation if you feel it's unclear?

I think it's already explained here. What is missing? 🤔
https://autowarefoundation.github.io/autoware-documentation/main/help/support-guidelines/

[IshitaTakeshi]

I mean a chart not in an image but in text like above.
The current guideline already has what contributors can use, but it doesn't say how they should choose from Q&A or feature requests.
Also, the chart above can more clearly show them what they should choose from Issues, Q&A, and feature requests from their contribution request.

[kenji-miyake]

Hmm? Then, you can send a pull request to update the documentation. 👍

[IshitaTakeshi]

Resolved in autowarefoundation/autoware-documentation#91