Re: [Gimp-developer] Fwd: Gimp Registry Future

[Pat David <patdavid gmail com>]

What are the current statistics of uploaded scripts/plugins?  It might help
us to formulate a plan if we knew a little better what the current state of
influx is.  (Are we seeing ~5 uploads a week?  10?  20?).

Also, I'm of the opinion that the registry, whatever it ends up becoming,
should be focused on the task of hosting the plugins/scripts.  Right now
there is a sort of forum module bolted on (which is clumsy and hard to use
in Drupal, imo).  Do we intend the site to also be a forum?  Do we just
want the ability to comment on specific plugins/scripts?

Ideally, I think it would be nice to see a single-purpose page focused on
the scripts/plugins only.  (If we think we want to institute a forum for
other purposes, perhaps it could be broken out into a separate discussion
for consideration?).

My gut feeling is that we are not getting overwhelmed with the number of
submissions to the site, and it's something that might be reasonably
handled by a few volunteers to vet the entries (and yes, I am volunteering
to help with this if we go this route).

There would be a nasty workload up front porting old entries, but after
that I think things would calm down to a reasonable workload.


On Wed, Apr 9, 2014 at 8:20 AM, Joao S. O. Bueno <gwidion gmail com> wrote:

> Hi Sven -
>
> It is nice to read this -
> I am very interested in having it working on "the client side" - that is, a
> GIMP plug-in that
> could make one-click download of plug-ins, scripts and other resources
> (brushes, tool settings, gradients and so on).
>
> Having an API SPEC for the registry would be something great, because if
> the current
> implementation is found lacking in some aspects, it could later be changed
> with
> relative little pain, provided the API is respected.
>
> We could build-up something that would allow users with different roles
> (that is, system known " to individuals who are
> reasonably well-known and accepted within their respective communities" )
> who can sign plug-ins, resources, and we should mostly try to get the build
> of plug-in binaries
> for windows and mac, and possibly even some distributions, automated in
> some form (Jenkins
> can do the building for testing purposes, I suppose we could fetch the
> binaries it generates in
> some form?).
>
> To get working going on the registry API itself, maybe we could start work
> on it in
> a wiki page, and in a later state consolidate that into a more stable
> document that
> can be rendered into code.
>
>
> Regards,
>
>   js
>  -><-
>
>
>
>
>
> On 9 April 2014 09:57, Michael Schumacher <schumaml gmx de> wrote:
>
> > On 09.04.2014 14:51, Alexandre Prokoudine wrote:
> >
> > > The expected effect of that will be a huge increase of deployed
> > > extensions and, as a consequence, an increased interest to GIMP from
> > > people who write exploits. My concern is how this interest can
> > > realistically be handled, because we shall be paying for a better
> > > technology with an increased reputation risk.
> >
> > The idea here is to cut down the number of people who may contribute
> > binaries, from about everyone right now to individuals who are
> > reasonably well-known and accepted within their respective communities
> > (for example, the various IRC channels or forums around GIMP).
> >
> >
> > --
> > Regards,
> > Michael
> > GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
> > _______________________________________________
> > gimp-developer-list mailing list
> > List address:    gimp-developer-list gnome org
> > List membership:
> > https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> > List archives:   https://mail.gnome.org/archives/gimp-developer-list
> _______________________________________________
> gimp-developer-list mailing list
> List address:    gimp-developer-list gnome org
> List membership:
> https://mail.gnome.org/mailman/listinfo/gimp-developer-list
> List archives:   https://mail.gnome.org/archives/gimp-developer-list



-- 
pat david
http://blog.patdavid.net