Moving kdevelop4-custom-buildsystem to g.k.o

Nicolás Alvarez nicolas.alvarez at
Thu Nov 25 22:45:35 UTC 2010

On 25/11/2010, David Nolden <zwabel at> wrote:
> 2010/11/25 Milian Wolff <mail at>:
>> David Nolden, 25.11.2010:
>>> 2010/11/23 Milian Wolff <mail at>:
>>> > Imo all of this should be met for a plugin in the "plugins" folder:
>>> >
>>> > a) active maintainer who cares about bug fixes etc.
>>> > b) a first release, since that makes it clear that the maintainer is
>>> > confident it is in a "production ready" state
>>> c) stable, meet some quality standards (we should release stuff that
>>> works, not stuff that _might_ work)
>>> Or alternatively, the plugin should be important enough to be
>>> considered a crucial part of the IDE. What does this plugin do?
>> Hehe, I find that one quite funny. What do you mean with "stable"? Who
>> decides
>> that? And why must it be stable to be in it's own git repo (we are not
>> talking
>> about merging it into either kdevelop or kdevplatform repository here, are
>> we?).
>> It's the maintainer who is responsible for that plugin, if he releases it
>> and
>> it's utter crap, people will note that and report it to him.
> Sorry, I'm talking about merging it into KDevelop/KDevplatform of
> course. Every somewhat maintained plugin should ideally be somewhere
> in our git repository.

They were talking of putting it in its own repository, under KDevelop/Plugins:

Not the 'plugins' directory in the KDevPlatform repository.


More information about the KDevelop-devel mailing list