bugs.kde.org product/component for plugins

[Andreas Pakulat]

Hi,

On Sat, Nov 10, 2012 at 8:09 PM, Niko Sams <niko.sams at gmail.com> wrote:
> where should users report bugs for plugins like kdev-upload,
> kdev-xdebug and so on?
> - kdev-python has it's own product
> - there was a upload/xdebug component in quanta (but quanta is not
> open for new bugs and it's confusing anyway)
> - php has it's own component in kdevelop (well actually two)
>
> How do we want to handle this?

I can see benefits for having components inside the KDevelop product
as well as having a new separate KDevPlatform Plugins product. The
latter would make it easier to see the state of KDevelop itself,
ignoring all those "third party" plugins, but it also produces a bit
more work since bugs will end up in KDevelop/General when reported
through the "Report a Bug" link and those need to be moved then.
Having them inside KDevelop may avoid that, but "pollute" the product
with third-party-plugins. So I guess it boils down to whatever the
people actively moving bugs around prefer :)

Andreas