niko.sams at gmail.com
Wed Mar 10 20:12:30 UTC 2010
On Wed, Mar 10, 2010 at 21:01, Andreas Pakulat <apaku at gmx.de> wrote:
> On 09.03.10 22:02:45, Niko Sams wrote:
>> I just pushed kdevelop-plugin-rules, afaics they are in pretty good
>> shape. (it's all very basic
>> as no branches at all are involved)
>> ...please review
>> Andreas you said you want to convert python plugin, drop mine if you
>> manage to import the
>> parser properly.
> I'm asking myself wether we should add plugins to that or not, i.e.
> should the ruleset cover all playground kdev4 plugins? The reason I'm
> asking is because that would mean converting stuff to git that is
> possibly unmaintained and maybe should just be left in playground until
> someone wants to pick it up and actually work on it. Would allow to drop
> some old cruft that doesn't even compile anymore and makes the
> kdevelop-project less cluttered.
> For example the java and python plugin fall into the category of "hardly
> maintained at all".
You want to let them die in svn? If we don't convert them their code
is kind of hidden.
And at least java gets picked up by harmish once in a while.
Oh - and I didn't write rules all plugins - just for the actively
developed ones and
the bigger ones.
More information about the KDevelop-devel