On Wed, 11 Jan 2012 19:05:30 -0800
Matthew Brush <mbr...@codebrainz.ca> wrote:

> On 01/11/2012 05:13 AM, Frank Lanitz wrote:
> > Am 10.01.2012 23:46, schrieb Matthew Brush:
> >> On 01/07/2012 07:20 AM, Colomban Wendling wrote:
> >>> Le 07/01/2012 16:00, Frank Lanitz a écrit :
> >>>> On Fri, 6 Jan 2012 23:42:39 +0100
> >>>> Frank Lanitz<fr...@frank.uvena.de>  wrote:
> >>>>
> >>>>>> * What's the exact difference between Supported and
> >>>>>> Maintained? The only difference I see is that "supported" has
> >>>>>> the word "paid" in the description, but I doubt that most of
> >>>>>> us get paid for this in particular, and I also doubt it
> >>>>>> changes anything on how good is the support (hobby vs. job).
> >>>>>
> >>>>> My fault. I wanted to change this but missed it. I wanted to
> >>>>> s/supported/paid for ... (Even I don't know anybody at the
> >>>>> moment who is getting paid with Geany stuff ;) )
> >>>>
> >>>> I suggest to use paid instead of supported and change current
> >>>> usage of supported to maintained.
> >>>
> >>> I'm still not sure what that fact someone is paid or not changes,
> >>> but otherwise it looks fine and clearer to me.
> >>
> >> +1
> >>
> >> Whether paid or volunteer, it's still "Maintained".
> >>
> >> I suggest dropping the "Paid" status altogether if no one has used
> >> it by the time all the plugins' info is filled in.
> >
> > I disagree. Currently there might be no plugin maintainer being
> > paid to work on a plugin, but:
> > - this might change (...)
> > - is something user should be able to see to resynch there
> > demandings with reality.
> >
> 
> Hehehe, well said. OK, it's not a big deal, though I still feel it's
> not very useful for Geany-Plugins.

Well, I will purge it for the meanwhile. We can add it once it comes
back up again. 

Cheers, 
Frank
-- 
http://frank.uvena.de/en/

Attachment: pgp3xlRoFRnD0.pgp
Description: PGP signature

_______________________________________________
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel

Reply via email to