Re: [Gimp-web] GIMP Plugin registry suggestions and volunteering

[Pat David <patdavid gmail com>]

Hi Jake!

Yeah, the registry has been dead for quite a while.  We nabbed a wget dump
before it was sunsetted here:
https://github.com/pixlsus/registry.gimp.org_static

A new plugin registry would be nice but it needs to be done in the context
of the main project - Jehan has some ideas around an integrated
plugin/extension solution that is probably the best path going forward.

For my own ideas I would probably consider generating a static site for the
plugins and manage the submissions/etc through git or some other mechanism
(if it were to be curated manually).

On Tue, May 24, 2022 at 5:42 PM Jake Gustafson via gimp-web-list <
gimp-web-list gnome org> wrote:

> Hello,
>
> I want to help revive the plugin registry
> (https://www.gimp.org/registry/). However, after reading
> https://www.gimp.org/develop/ I'm still not sure who to contact. On that
> page:
>
>   * The "Web Development" section isn't clear on how to get involved.
>   * The "GIMP developers" link in "GIMP developers The main GIMP
>     development website" results in page not found (https://wiki.gimp.org/
> ).
>
>
> https://mail.gnome.org/mailman/listinfo/gimp-web-list) says "To post a
> message to all the list members, send email to gimp-web-list gnome org."
> but I'm not sure I'd have that permission automatically so let me know
> if this works.
>
> I have Drupal experience but only version 9 (and instance with some
> leftover issues from 8, but not 8 itself nor any earlier version).
> Still, I may be able to poke around with it or convert your data to
> something else that is easier to maintain.
>
> After understanding Drupal in a professional setting, I can say it is
> overkill for a plugin site. In fact, I'd say that Drupal should only be
> used by an organization that has a team of web developers. Complex
> issues with upgrades can cause services to fail. Upgrades can cause
> plugins to fail. Many things require custom plugins. It is a no-code
> solution that requires lots of code to do anything significant. It is a
> well-supported solution that requires lots of support. Overall, it is
> rather slow and difficult to maintain. I suggest converting the data to
> something like Django+mezzanine and I'd be happy to help with that if I
> could get a copy of the backend data. Barring Django+mezzanine we could
> pick something that is easy to maintain: Something that is
> well-supported but doesn't require lots of support; perhaps a no-code
> solution that doesn't require custom code for significant customization,
> like artgen.io. If there is a better place to discuss this, please let
> me know.
>
> Thanks,
>
> Jake Gustafson ("Poikilos")
>
> https://github.com/poikilos <https://github.com/poikilos>
>
> https://poikilos.org <https://poikilos.org>
>
> _______________________________________________
> gimp-web-list mailing list
> gimp-web-list gnome org
> https://mail.gnome.org/mailman/listinfo/gimp-web-list


-- 
https://patdavid.net
GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC