<p>In <a href="https://github.com/geany/geany-plugins/pull/435#discussion_r66627616">MAINTAINERS</a>:</p>
<pre style='color:#555'>> @@ -138,10 +138,10 @@ W: http://plugins.geany.org/geanyprj.html
>  S: Odd Fixes
>  
>  geanypy
> -P: Lex Trotman <elextr@gmail.com>
> -M: Lex Trotman <elextr@gmail.com>
</pre>
<blockquote>
<p>IMO it would be best having Matthew Brush at the "+" side of the patch if <a href="https://github.com/codebrainz" class="user-mention">@codebrainz</a> is willing to maintain it. </p>
</blockquote>

<p>I like having separate repo/issues/build system, etc, which is why I kept GeanyPy as external to Geany-Plugins. I don't think every plugin people write should be forced to be in Geany-Plugins. I don't mind formatting patches for changes to upstream so they can be applied to the fork in Geany-Plugins, but it's going to get harder and harder as the fork has diverged significantly from my repo (ex. the proxy plugin stuff, the geany_functions commit, etc).</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany-plugins/pull/435/files/e0d77167b2d9550fbd2e689347a80fb97371004b#r66627616">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe/ABDrJ4x-XyQ20kSSG4hP_V_jzVjbKsKRks5qKXtbgaJpZM4Ix325">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABDrJ15XKx_J6UJLiDZY1nEX3iHgwB9uks5qKXtbgaJpZM4Ix325.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/geany/geany-plugins/pull/435/files/e0d77167b2d9550fbd2e689347a80fb97371004b#r66627616"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>