Greasemonkey development has stopped; time for 1.0?

Hi all,

I have noticed that greasemonkey development activity has
stopped - 
apart from the refactoring which aaron did when merging back
into the 
trunk, nothing has changed in over a year.

I think this is due to a combination of two factors
    1) Greasemonkey is "perfect" - that is it has
a stable set of 
features that cover all the major use-cases for people
wanting to write 
"simple site extensions", new features would be
considered bloat.
    2) The greasemonkey development team no longer wants to
develop 
greasemonkey.  I can't speak for any of them, but I guess it
is because 
either they believe (1) or they are too busy/have moved on
to greener 
pastures.

While these are both valid reasons, I would not like to see
greasemonkey 
development stop for good. 

As I see it one way forward might be to create a 1.0 release
of 
greasemonkey, this version would be maintained with
bug-fixes, extra 
locales etc, but the feature set and api would be frozen as
it is now.  
Maintenance of this version should be a relatively
low-effort task.

This would free us up to talk about greasemonkey 2.0, which
would be the 
release containing any new features.  I would like to have a

conversation about what user script developers might like to
see in a 
new greasemonkey, my wishlist would be:
1) Greasemonkey Imports
2) A better storage solution
3) Access to some chrome privileged methods especially =
canvas.drawWindow()

In order to build greasemonkey2 the project will have to
encourage more 
developers to take part in developing greasemonkey.  I think
one of the 
things that might make this easier is to draw up a
democratic process 
(eg. [2]) so that it is easier for new blood to be
incorporated into the 
greasemonkey team.

Thoughts anyone? Aaron?

Gareth.

[1] - 
http://deve
loper.mozilla.org/en/docs/Drawing_Graphics_with_Canvas#Rende
ring_Web_Content_Into_A_Canvas
[2] - I particularly like the apache jakarta groups's
process - 
http://
jakarta.apache.org/site/decisions.html
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey

As a userscripts author, this is what I would like to see in
a new
version of greasemonkey, plus your suggestions:

1) A few new GM_* API:s, like GM_get/setClipboard,
GM_closeTab (maybe useful)
2) Regexp includes, with the ability to see what regex
include was matched.
3) Some kind of webstorage?

On 10/7/06, Gareth Andrew <freegafreegarethandrew.org>
wrote:
> Hi all,
>
> I have noticed that greasemonkey development activity
has stopped -
> apart from the refactoring which aaron did when merging
back into the
> trunk, nothing has changed in over a year.
>
> I think this is due to a combination of two factors
>     1) Greasemonkey is "perfect" - that is it
has a stable set of
> features that cover all the major use-cases for people
wanting to write
> "simple site extensions", new features would
be considered bloat.
>     2) The greasemonkey development team no longer
wants to develop
> greasemonkey.  I can't speak for any of them, but I
guess it is because
> either they believe (1) or they are too busy/have moved
on to greener
> pastures.
>
> While these are both valid reasons, I would not like to
see greasemonkey
> development stop for good.
>
> As I see it one way forward might be to create a 1.0
release of
> greasemonkey, this version would be maintained with
bug-fixes, extra
> locales etc, but the feature set and api would be
frozen as it is now.
> Maintenance of this version should be a relatively
low-effort task.
>
> This would free us up to talk about greasemonkey 2.0,
which would be the
> release containing any new features.  I would like to
have a
> conversation about what user script developers might
like to see in a
> new greasemonkey, my wishlist would be:
> 1) Greasemonkey Imports
> 2) A better storage solution
> 3) Access to some chrome privileged methods especially
= canvas.drawWindow()
>
> In order to build greasemonkey2 the project will have
to encourage more
> developers to take part in developing greasemonkey.  I
think one of the
> things that might make this easier is to draw up a
democratic process
> (eg. [2]) so that it is easier for new blood to be
incorporated into the
> greasemonkey team.
>
> Thoughts anyone? Aaron?
>
> Gareth.
>
> [1] -
> http://deve
loper.mozilla.org/en/docs/Drawing_Graphics_with_Canvas#Rende
ring_Web_Content_Into_A_Canvas
> [2] - I particularly like the apache jakarta groups's
process -
> http://
jakarta.apache.org/site/decisions.html
> _______________________________________________
> Greasemonkey mailing list
> Greasemonkeymozdev.org
> http:
//mozdev.org/mailman/listinfo/greasemonkey
>
_______________________________________________
Greasemonkey mailing list
Greasemonkeymozdev.org
http:
//mozdev.org/mailman/listinfo/greasemonkey