[Geany-Devel] Removing of orphaned plugins

Thomas Martitz thomas.martitz at xxxxx
Sat Apr 6 21:36:39 UTC 2013

Am 06.04.2013 22:35, schrieb Lex Trotman:
> On 7 April 2013 06:19, Matthew Brush <mbrush at codebrainz.ca 
> <mailto: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
>         https://github.com/frlan/geany-plugins/commits/Removing_orphaned_plugins
>         to remove orphaned plugins. I'm going to apply this patchset
>         to master
>         if there will nobody adopt the plugin.
>     Hi,
>     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
>     Cheers,
>     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 overall.

I think they do work. I can tell for sure for treeviewer, and recent 
threads on the ML have shown that geanylua also still works just fine. 
For the others, they clearly still at least comile.

Let me ask the other way around. Are there known bugs caused by the 
plugins in question, i.e. a bug report against one of those plugins or 
Geany where the root cause is one of those plugins? I'm not aware of 
any, so it should be assumed that they work since there was no radical 
change in neither the plugins nor the plugin API.

As for poorer releases, I find a release that removes functionality 
(i.e. one or more fine working plugin) for no reason much poorer.

Best regards.

More information about the Devel mailing list