<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Mar 6, 2014 at 11:11 PM, Aleix Pol <span dir="ltr"><<a href="mailto:aleixpol@kde.org" target="_blank">aleixpol@kde.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><div class="h5">On Thu, Mar 6, 2014 at 10:16 PM, John5342 <span dir="ltr"><<a href="mailto:john5342@gmail.com" target="_blank">john5342@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">Has anyone put any consideration into collecting the status of the various plugins?<div>
<br></div><div>
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.</div>
<div><br></div><div>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.</div>
<div><br></div><div>Apologies in advance if this already exists but i missed it.</div></div></div></div></blockquote></div></div><div class="gmail_extra">Hi,</div><div class="gmail_extra">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.</div>
</div></blockquote><div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">A very valid point but if it brings more contributors then that could tip the balance and a "last updated date" would at least show how out of date any particular entry is.</span><br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">
Usually people send an e-mail to this list asking for feedback, and I would say it's fine.</div><div class="gmail_extra">Do you have any special needs?</div></div></blockquote></div><div class="gmail_extra"><br></div>
<div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">I wasn't after anything specific. More of a missed opportunity that i thought was worth bringing up.</div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">
<br></div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">That said, i am curious about the state of kdev-clang since i use clang almost exclusively at the moment:</div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">
- How does it compare, in completeness/stability/etc, to the current built in c++ parser?</div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">- What was decided on whether to parse per file or per translation unit?</div>
<div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">- If "per file", will "per translation unit" be an option at some point?</div><div class="gmail_extra" style="font-family:arial,sans-serif;font-size:13px">
- Have you got a running list of tasks so i can work out how best to help?</div><div><br></div><div><br></div><div>On Fri, Mar 7, 2014 at 3:32 PM, Aleix Pol <span dir="ltr"><<a href="mailto:aleixpol@kde.org" target="_blank">aleixpol@kde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Please answer to the mailing list, as there's other people with better information on kdev-clang support.</div>
</blockquote><div><br></div><div>My apologies. All the other mailing lists i post on have a reply-to header so "Reply" just does the right thing. I will be more careful in the future. </div></div><div><br></div>
-- <br>There are 10 kinds of people in the world: Those who understand binary and those who don't...
</div></div>