[Geany-Devel] Removing of orphaned plugins
elextr at xxxxx
Sat Apr 6 20:35:39 UTC 2013
On 7 April 2013 06:19, Matthew Brush <mbrush at codebrainz.ca> wrote:
> On 13-04-06 09:26 AM, Frank Lanitz wrote:
>> Hi folks,
>> Unfortunately we still have a number of orphaned plugins. To get this
>> thing cleaned up I've created a branch at
>> to remove orphaned plugins. I'm going to apply this patchset to master
>> if there will nobody adopt the plugin.
> I have to agree with Thomas, it seems silly to remove fully functional
> plugins that users (probably) like and use just because the status of the
> author/maintainer is unknown.
> IMO, it'd make more sense to only remove them if they have some critical
> unfixed bug that no on will step up to fix, or if they become obsoleted by
> other plugins (like GeanyGDB).
> My $0.02
> Matthew Brush
Well, I can understand both points of view. Yes users may be ahppy with
plugins as they are.
That is, *if* they work ok, thats fine, but plugins can affect the whole of
Geany, unless they are checked reasonably often with the Git Geany by
"someone" then we don't know even if they compile, if they segfault or have
a bazillion bugs. Finding all this out at the last minute before a release
puts too much stress on the release team and results in poorer releases
And despite all the good contributions of GTK3 code, if nobody is stepping
up and testing it, then the plugins have indeed bitrotted relative to the
Also the documentation of many of them is poor and out of date.
So overall I agree with Frank that, for the good of the overall plugins
package unmaintained plugins need to be removed. If someone makes a github
fork, I'm sure that an "external plugin" link can be made from the g-p
> Devel mailing list
> Devel at lists.geany.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel