KDev Plugin Status

[Kevin Funk]

Am Freitag, 7. März 2014, 00:11:40 schrieb Aleix Pol:
> On Thu, Mar 6, 2014 at 10:16 PM, John5342 <john5342 at gmail.com> wrote:
> > Has anyone put any consideration into collecting the status of the various
> > plugins?
> > 
> > I have used a few plugins such as kdev-python and kdev-custombuildsystem
> > (before it was merged) but, aside from kdev-python which was mentioned on
> > list, i only really discovered them indirectly by browsing quickgit.
> > Looking through them i notice some have had virtually zero activity for
> > some time and others seem quite active but it is not clear which ones are
> > supposed to be stable(ish), experiments or even whether they are supposed
> > to build. Keeping plugins as something to be stumbled on by end users
> > reduces users for plugins that are mostly stable, testers/reporters for
> > ones that are mostly working and contributors for ones that are active but
> > still need real work.
> > 
> > So in short it would be great to see a place (a wiki page?) listing the
> > plugins, description, current status (and last updated date) and
> > optionally
> > a bugzilla link for bugs and task list for possible contributors.
> > Hopefully
> > all maintained by the owner of each plugin.
> > 
> > Apologies in advance if this already exists but i missed it.
> > 
> > --
> > There are 10 kinds of people in the world: Those who understand binary and
> > those who don't...
> > 
> > _______________________________________________
> > KDevelop-devel mailing list
> > KDevelop-devel at kde.org
> > https://mail.kde.org/mailman/listinfo/kdevelop-devel
> 
> Hi,
> I agree that there definitely is a lacking in this area. On the other hand,
> keeping wikis updated where the people involved doesn't need (most
> developers don't need to keep track of such things in a wiki) tend to go
> out of date.

Hey,

I have to object (a bit).

I think it would be really beneficial for all parties to have a wiki entry 
that maintains a list of available KDevelop plugins associated with their 
current status and (if applicable) their respective maintainer(s).

For packagers: Admittedly, there's pko or git.kde.org right now, but it isn't 
really that useful nor holds the amount of information about the plugins you'd 
need. Nor does it tell us anything about the current status of that particular 
plugin.

For us to coordinate/assign issues: I work a lot on bko, and sometimes issues 
just as today's [1] show up, indicating an issue in an 3rdparty plugin I don't 
even know yet. I have to to fire up Google in order to get the repository URL 
(if there's any) and find the original author just to properly handle the 
issue. A central list would help.

> Usually people send an e-mail to this list asking for feedback, and I would
> say it's fine.
> Do you have any special needs?
> 
> Aleix

I'd also volunteer for setting up that list. I think that also gives us a 
chance to re-evaluate some plugins, checking in what state they are, etc. pp.

Cheers

[1] https://bugs.kde.org/show_bug.cgi?id=331957

-- 
Kevin Funk