Adding KDevelop developers for their comments on this.

Question is if "kdev-go" should become a component "Language Support: Go" below kdevelop:
https://bugs.kde.org/describecomponents.cgi?product=kdevelop
or be a complete own products, with own components, like kdev-python:
https://bugs.kde.org/describecomponents.cgi?product=kdev-python

Adding them as components is the way to go. I'd love to have kdev-python in their as component there (for consistency reasons), but I think I once talked to Sven about it and he didn't like the idea.

My reasons *for* adding plugins as components:
- Scales much better (we don't have to maintain one product per plugin, and we also don't need to keep the versions/milestones in sync)
- Plugins are "part of KDevelop", IMO. When reporting bugs the user will think of reporting the bug against the 'kdevelop' product first -- which part it happened in is secondary.

I've added a "Language Support: Go" component to the kdevelop product.

"Plugins are "part of KDevelop", IMO. When reporting bugs the user will think of reporting the bug against the 'kdevelop' product first -- which part it happened in is secondary."

I agree with you about this one. This is also the reason, why i think that KDevelop should stop to hide its features and mention Go and QML support also on this page: https://www.kdevelop.org/

I can open another report for it

QML can be mentioned but not Go, it has no released stable version yet.

Updated the website title, front page heading and Features page. Hope that helps.

Thanks for the hints!

Sure, thanks a lot for the quick fix.