[Geany-devel] Ideas on increasing quality of plugins

Lex Trotman elextr at xxxxx
Wed Feb 23 10:31:59 UTC 2011


Hey Thomas,

On 23 February 2011 21:10, Thomas Martitz
<thomas.martitz at student.htw-berlin.de> wrote:
> Am 23.02.2011 04:01, schrieb Lex Trotman:
>>
>> Of course on the other hand because the maintainers are volunteers
>> with limited time this process slows changes, but IMHO this is
>> necessary.  Having more maintainers for a piece of code is of course
>> the solution, but as we are finding, its hard to actually do for a
>> small project.  Even for core there was a deafening silence when I
>> recently suggested that more people volunteer to be maintainers.
>>
>
> I don't think that silence meant anything other than the people that can
> decide haven't read it yet.

Well it was a while ago, so either they missed it, or don't intend to offer.

But yea, I would welcome a discussion about this
> in the core. There's great potential contributors on this list, but they're
> all sitting on their patches and nothing moves forward.


Hope things improve too.

>
>
>> Of course the Geany community also has a responsibility to Geany users
>> (not least ourselves :-) to make sure that the whole Geany ecosystem
>> offered as an "official" release meets reliability and usability
>> standards.  On this basis, Frank's concern that some plugins don't
>> meet those standards is important, but I don't think that it is
>> reasonable for the community to impose work on maintainers without
>> discussion (thats this thread) and a reasonable period for improving
>> things, otherwise the community is undermining the maintainers
>> responsibility, and I certainly would get upset if I were a
>> maintainer.
>
> You seem to have misunderstood that letting other people help fix bugs is
> voluntary is has nothing to do with undermining.

Agree, apologies if I wasn't clear, I was saying *forcing* something
on maintainers without discussion or reasonable time to do it is the
sort of thing that gets people upset.

For example if its decided that plugins need to run extra tools then
the maintainers have to install, learn, tune the tool etc all of which
is extra work that can be annoying if you want to get on with coding
features or fixes.  And its still annoying no matter how useful its is
:-)

And I didn't suggest to
> share maintainership completely, but just accept help to fix the most
> immediate bugs (such as crashes) in a timely manner. Nobody wants to take
> plugins away from developers.

Right, its up to the individuals how they handle it, fully shared
maintainership, lead maintainer and secondary maintainers, patch
providers or just testers/reviewers all are useful arrangements that
can work.


Cheers
Lex
>
> Best regards.
> _______________________________________________
> Geany-devel mailing list
> Geany-devel at uvena.de
> http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
>



More information about the Devel mailing list