Re: [Gimp-web] Getting involved with the "Get Involved" web page

[Andrew Toskin]

 

On 2015-10-23 06:35, Pat David wrote: 

> It seems that the list may have stripped out your attachment?

Huh. I'll try attaching it again, but just in case, here's the patch
file pasted below. 

>From 580337e443bcca55b1e70bae72fcebcf9cdc50e6 Mon Sep 17 00:00:00 2001
From: Andrew Toskin <and...@tosk.in>
Date: Thu, 22 Oct 2015 20:59:41 -0700
Subject: [PATCH] Explain *how* to contribute to the GIMP projects.

The "Development Status", "Bug Reports" and "Web Development" headings
seemed to
me like they were really subsections of "How You Can Help," so I set
those to be
h3 headings.

A couple times, in the "Hacking" and "How To Submit Your Changes"
sections, I
tried to borrow the tone of Wikipedia's "Be Bold" guidelines.
<https://en.wikipedia.org/wiki/Wikipedia:Be_bold>

I added a list of links to the most important GIMP repositories. I was
going to
mention gimp-web-devel in this list, but it looks like no one has pushed
any
commits there since 2013. Perhaps that repo should be archived?
---
 content/develop/index.md | 30 +-
 1 file changed, 25 insertions(+), 5 deletions(-)

diff --git a/content/develop/index.md b/content/develop/index.md
index 0c9df4a..1502c76 100644
--- a/content/develop/index.md
+++ b/content/develop/index.md
@@ -31,7 +31,7 @@ Ways in which you can help:

 As you can see, anyone can help. 

-## Development Status 
+### Development Status 

 The team is currently busy working on v2.10. This will be the first
release of GIMP featuring a new, advanced image processing engine, high
bit depth editing, as well as new and improved transformation and
selection tools. 

@@ -39,19 +39,34 @@ Porting internals of GIMP to GEGL is mostly done,
but more plugins have to be po

 To get a better understanding of where the project is heading to, which
features are planned etc., please visit the
[Roadmap](http://wiki.gimp.org/index.php/Roadmap) page. 

-## Bug Reports 
+### Bug Reports 

 GIMP is not a bug-free application nor is any other application so
reporting the bugs that you will encounter is very important to the
development, it helps the developers to make GIMP more stable and more
bug free. 

 You don't have to be a developer or a everyday user to report bugs. It
can be hard to report a bug the first time you try it out but don't just
quit the whole bug report if you think it is hard. Instead, look at the
[bugs](/bugs/) page you will find some very good help about this. 

-## Web Development 
+### Web Development 

 Creating websites that contain useful information is very important. It
is actually just as important as doing bug reports. A website contains a
lot of information that is needed for the development to move on and it
also contains information that will help the public to understand what
the application is all about. 

 ## Hacking 

-This is the part where people are always needed to help with the
development, and this is also the part that is the hardest to start
with. Though there are websites and files to give you a good look at how
hacking is being done in GIMP. 
+GIMP uses [git](https://git-scm.com/) as its revision control system,
and the [GNOME Foundation](https://www.gnome.org/) hosts all of our code
repositories: 
+ 
+* [`gimp`](https://git.gnome.org/browse/gimp/) - the GIMP application
itself 
+* [`gimp-web`](https://git.gnome.org/browse/gimp-web/) - repo for this
website 
+* [`gimp-web-devel`](https://git.gnome.org/browse/gimp-web-devel/) -
repo for the developer site at <http://developer.gnome.org> 
+* [`gimp-help-2`](https://git.gnome.org/browse/gimp-help-2/) - the GIMP
user manual 
+* [plus several others](https://git.gnome.org/browse/?q=gimp) 
+ 
+New contributors should first introduce themselves on IRC (the #gimp
channel at irc.gimp.org) and/or the relevant mailing lists: 
+ 
+* [GIMP Developers mailing list, for those who work on the core GIMP
application and
plugins](https://mail.gnome.org/mailman/listinfo/gimp-developer-lists) 
+* [GEGL Developers mailing list for developers of the GEGL
library](https://mail.gnome.org/mailman/listinfo/gegl-developer-list) 
+* [GIMP Web Developers mailing list, for working on this
website](https://mail.gnome.org/mailman/listinfo/gimp-web-list) 
+* [GIMP Documentation mailing list, for working on the user
manual](https://mail.gnome.org/mailman/listinfo/gimp-docs-list) 
+ 
+This way you can announce the changes you intend to make, ask
questions, and discuss which changes would be best. It's generally
better to focus on one thing at a time. Contributing to a software
project for the first time is always the hardest part, which is why
we're here to help each other. There are also websites to give you a
good look at how hacking is being done in GIMP. 

 The site you should keep updated with and the site that is updated all
the time with new development help guides is located at
[http://wiki.gimp.org/](http://wiki.

Re: [Gimp-web] Getting involved with the "Get Involved" web page

[Andrew Toskin]

I installed the git send-email module (listed as `git-email` on
Fedora), but I don't understand it. I can't get it to send anything in
my tests. I'm probably not the first person to complain about this, but
GitHub/GitLab-style pull requests really seem like the better way to do
this sort of thing...

Whatever. Try downloading the patch from my website. <https://andrew.to
sk.in/patches/2015-10-22--explain-how-to-contribute-to-the-gimp
-projects.patch>

~Andrew


On Mon, 2015-10-26 at 20:49 -0700, Andrew Toskin wrote:
> On Mon, 2015-10-26 at 19:12 +, Pat David wrote:
> > Andrew,
> > 
> > I think the email mangled your patch data - was it a webmail client
> > that did this, or did you use the sendmail/git feature?
> > 
> > I'm trying to apply your patch and getting errors about a corrupt
> > patch file.
> The first time I sent it with Evolution, the default email client in
> GNOME. Then I did it from my webmail, RoundCube.
> 
> Will it only work with git send-email? I see it documented at git
> -scm.com, but it's not an available git command (on my system,
> running git 2.4.3 on Fedora 22).
> 
> ~Andrew
> 
> 
> > On Sat, Oct 24, 2015 at 3:18 PM Andrew Toskin <and...@tosk.in>
> > wrote:
> > > 
> > > On 2015-10-23 06:35, Pat David wrote:
> > > 
> > > > It seems that the list may have stripped out your attachment?
> > > 
> > > Huh. I'll try attaching it again, but just in case, here's the
> > > patch
> > > file pasted below.
> > > 
> > > From 580337e443bcca55b1e70bae72fcebcf9cdc50e6 Mon Sep 17 00:00:00
> > > 2001
> > > From: Andrew Toskin <and...@tosk.in>
> > > Date: Thu, 22 Oct 2015 20:59:41 -0700
> > > Subject: [PATCH] Explain *how* to contribute to the GIMP
> > > projects.
> > > 
> > > The "Development Status", "Bug Reports" and "Web Development"
> > > headings
> > > seemed to
> > > me like they were really subsections of "How You Can Help," so I
> > > set
> > > those to be
> > > h3 headings.
> > > 
> > > A couple times, in the "Hacking" and "How To Submit Your Changes"
> > > sections, I
> > > tried to borrow the tone of Wikipedia's "Be Bold" guidelines.
> > > <https://en.wikipedia.org/wiki/Wikipedia:Be_bold>
> > > 
> > > I added a list of links to the most important GIMP repositories.
> > > I was
> > > going to
> > > mention gimp-web-devel in this list, but it looks like no one has
> > > pushed
> > > any
> > > commits there since 2013. Perhaps that repo should be archived?
> > > ---
> > >  content/develop/index.md | 30 +-
> > >  1 file changed, 25 insertions(+), 5 deletions(-)
> > > 
> > > diff --git a/content/develop/index.md b/content/develop/index.md
> > > index 0c9df4a..1502c76 100644
> > > --- a/content/develop/index.md
> > > +++ b/content/develop/index.md
> > > @@ -31,7 +31,7 @@ Ways in which you can help:
> > > 
> > >  As you can see, anyone can help.
> > > 
> > > -## Development Status
> > > +### Development Status
> > > 
> > >  The team is currently busy working on v2.10. This will be the
> > > first
> > > release of GIMP featuring a new, advanced image processing
> > > engine, high
> > > bit depth editing, as well as new and improved transformation and
> > > selection tools.
> > > 
> > > @@ -39,19 +39,34 @@ Porting internals of GIMP to GEGL is mostly
> > > done,
> > > but more plugins have to be po
> > > 
> > >  To get a better understanding of where the project is heading
> > > to, which
> > > features are planned etc., please visit the
> > > [Roadmap](http://wiki.gimp.org/index.php/Roadmap) page.
> > > 
> > > -## Bug Reports
> > > +### Bug Reports
> > > 
> > >  GIMP is not a bug-free application nor is any other application
> > > so
> > > reporting the bugs that you will encounter is very important to
> > > the
> > > development, it helps the developers to make GIMP more stable and
> > > more
> > > bug free.
> > > 
> > >  You don't have to be a developer or a everyday user to report
> > > bugs. It
> > > can be hard to report a bug the first time you try it out but
> > > don't just
> > > quit the whole bug report if you think it is h

Re: [Gimp-web] Getting involved with the "Get Involved" web page

[Andrew Toskin]

On Mon, 2015-10-26 at 19:12 +, Pat David wrote:
> Andrew,
> 
> I think the email mangled your patch data - was it a webmail client
> that did this, or did you use the sendmail/git feature?
> 
> I'm trying to apply your patch and getting errors about a corrupt
> patch file.
The first time I sent it with Evolution, the default email client in
GNOME. Then I did it from my webmail, RoundCube.
Will it only work with git send-email? I see it documented at git
-scm.com, but it's not an available git command (on my system, running
git 2.4.3 on Fedora 22).
~Andrew

> On Sat, Oct 24, 2015 at 3:18 PM Andrew Toskin <and...@tosk.in> wrote:
> > 

> > 
> > On 2015-10-23 06:35, Pat David wrote:
> > 

> > 
> > > It seems that the list may have stripped out your attachment?
> > 

> > 
> > Huh. I'll try attaching it again, but just in case, here's the patch
> > 
> > file pasted below.
> > 

> > 
> > From 580337e443bcca55b1e70bae72fcebcf9cdc50e6 Mon Sep 17 00:00:00 2001
> > 
> > From: Andrew Toskin <and...@tosk.in>
> > 
> > Date: Thu, 22 Oct 2015 20:59:41 -0700
> > 
> > Subject: [PATCH] Explain *how* to contribute to the GIMP projects.
> > 

> > 
> > The "Development Status", "Bug Reports" and "Web Development" headings
> > 
> > seemed to
> > 
> > me like they were really subsections of "How You Can Help," so I set
> > 
> > those to be
> > 
> > h3 headings.
> > 

> > 
> > A couple times, in the "Hacking" and "How To Submit Your Changes"
> > 
> > sections, I
> > 
> > tried to borrow the tone of Wikipedia's "Be Bold" guidelines.
> > 
> > <https://en.wikipedia.org/wiki/Wikipedia:Be_bold>
> > 

> > 
> > I added a list of links to the most important GIMP repositories. I was
> > 
> > going to
> > 
> > mention gimp-web-devel in this list, but it looks like no one has pushed
> > 
> > any
> > 
> > commits there since 2013. Perhaps that repo should be archived?
> > 
> > ---
> > 
> >  content/develop/index.md | 30 +-
> > 
> >  1 file changed, 25 insertions(+), 5 deletions(-)
> > 

> > 
> > diff --git a/content/develop/index.md b/content/develop/index.md
> > 
> > index 0c9df4a..1502c76 100644
> > 
> > --- a/content/develop/index.md
> > 
> > +++ b/content/develop/index.md
> > 
> > @@ -31,7 +31,7 @@ Ways in which you can help:
> > 

> > 
> >  As you can see, anyone can help.
> > 

> > 
> > -## Development Status
> > 
> > +### Development Status
> > 

> > 
> >  The team is currently busy working on v2.10. This will be the first
> > 
> > release of GIMP featuring a new, advanced image processing engine, high
> > 
> > bit depth editing, as well as new and improved transformation and
> > 
> > selection tools.
> > 

> > 
> > @@ -39,19 +39,34 @@ Porting internals of GIMP to GEGL is mostly done,
> > 
> > but more plugins have to be po
> > 

> > 
> >  To get a better understanding of where the project is heading to, which
> > 
> > features are planned etc., please visit the
> > 
> > [Roadmap](http://wiki.gimp.org/index.php/Roadmap) page.
> > 

> > 
> > -## Bug Reports
> > 
> > +### Bug Reports
> > 

> > 
> >  GIMP is not a bug-free application nor is any other application so
> > 
> > reporting the bugs that you will encounter is very important to the
> > 
> > development, it helps the developers to make GIMP more stable and more
> > 
> > bug free.
> > 

> > 
> >  You don't have to be a developer or a everyday user to report bugs. It
> > 
> > can be hard to report a bug the first time you try it out but don't just
> > 
> > quit the whole bug report if you think it is hard. Instead, look at the
> > 
> > [bugs](/bugs/) page you will find some very good help about this.
> > 

> > 
> > -## Web Development
> > 
> > +### Web Development
> > 

> > 
> >  Creating websites that contain useful information is very important. It
> > 
> > is actually just as important as doing bug reports. A website contains a
> > 
> > lot of information that is needed for the development to move on and it
> > 
> > also contains information that will help the public to understand what
> > 
> > the application is all about.
> >

Re: [Gimp-web] Getting involved with the "Get Involved" web page

[Andrew Toskin]

Okay, I'm glad we got it through.

I'll send another patch *about* using Bugzilla to the Bugzilla :P

~Andrew


On Tue, 2015-10-27 at 14:46 +, Pat David wrote:
> Ok, finally got the patch uncorrupted and merged/applied.  (The
> changes should be live shortly, if they aren't already).
> 
> I also should be reprimanded for not pointing out earlier that we can
> should also probably take patches through bugzilla:
> 
> https://bugzilla.gnome.org/enter_bug.cgi?product=gimp-web
> 
> where you can actually attach the patch.
> 
> Thank you very much for being patient and re-sending.  Helping to
> ease the process of contributions is definitely something we'll look
> at soon, but for now if you want to submit any other patches, please
> attach them in bugzilla.
> 
> On Mon, Oct 26, 2015 at 11:27 PM Andrew Toskin <and...@tosk.in>
> wrote:
> > I installed the git send-email module (listed as `git-email` on
> > Fedora), but I don't understand it. I can't get it to send anything
> > in
> > my tests. I'm probably not the first person to complain about this,
> > but
> > GitHub/GitLab-style pull requests really seem like the better way
> > to do
> > this sort of thing...
> > 
> > Whatever. Try downloading the patch from my website. <
> > https://andrew.to
> > sk.in/patches/2015-10-22--explain-how-to-contribute-to-the-gimp
> > -projects.patch>
> > 
> > ~Andrew
> > 
> > 
> > On Mon, 2015-10-26 at 20:49 -0700, Andrew Toskin wrote:
> > > On Mon, 2015-10-26 at 19:12 +, Pat David wrote:
> > > > Andrew,
> > > >
> > > > I think the email mangled your patch data - was it a webmail
> > client
> > > > that did this, or did you use the sendmail/git feature?
> > > >
> > > > I'm trying to apply your patch and getting errors about a
> > corrupt
> > > > patch file.
> > > The first time I sent it with Evolution, the default email client
> > in
> > > GNOME. Then I did it from my webmail, RoundCube.
> > >
> > > Will it only work with git send-email? I see it documented at git
> > > -scm.com, but it's not an available git command (on my system,
> > > running git 2.4.3 on Fedora 22).
> > >
> > > ~Andrew
> > >
> > >
> > > > On Sat, Oct 24, 2015 at 3:18 PM Andrew Toskin <and...@tosk.in>
> > > > wrote:
> > > > >
> > > > > On 2015-10-23 06:35, Pat David wrote:
> > > > >
> > > > > > It seems that the list may have stripped out your
> > attachment?
> > > > >
> > > > > Huh. I'll try attaching it again, but just in case, here's
> > the
> > > > > patch
> > > > > file pasted below.
> > > > >
> > > > > From 580337e443bcca55b1e70bae72fcebcf9cdc50e6 Mon Sep 17
> > 00:00:00
> > > > > 2001
> > > > > From: Andrew Toskin <and...@tosk.in>
> > > > > Date: Thu, 22 Oct 2015 20:59:41 -0700
> > > > > Subject: [PATCH] Explain *how* to contribute to the GIMP
> > > > > projects.
> > > > >
> > > > > The "Development Status", "Bug Reports" and "Web Development"
> > > > > headings
> > > > > seemed to
> > > > > me like they were really subsections of "How You Can Help,"
> > so I
> > > > > set
> > > > > those to be
> > > > > h3 headings.
> > > > >
> > > > > A couple times, in the "Hacking" and "How To Submit Your
> > Changes"
> > > > > sections, I
> > > > > tried to borrow the tone of Wikipedia's "Be Bold" guidelines.
> > > > > <https://en.wikipedia.org/wiki/Wikipedia:Be_bold>
> > > > >
> > > > > I added a list of links to the most important GIMP
> > repositories.
> > > > > I was
> > > > > going to
> > > > > mention gimp-web-devel in this list, but it looks like no one
> > has
> > > > > pushed
> > > > > any
> > > > > commits there since 2013. Perhaps that repo should be
> > archived?
> > > > > ---
> > > > >  content/develop/index.md | 30 +-
> > > > >  1 file changed, 25 insertions(+), 5 deletions(-)
> > > > >
> > > > > diff --git a/content/develop/index.md
> > b/content/develop/index.md
> > &

Re: [Gimp-web] Getting involved with the "Get Involved" web page

[Andrew Toskin]

...Oh, never mind, I see you already added a line about the Bugzilla.
So we're good, then.

I'll probably go straight to the Bugzilla for the next patch, though.

Thanks,
~Andrew


On Tue, 2015-10-27 at 13:07 -0700, Andrew Toskin wrote:
> Okay, I'm glad we got it through.
> 
> I'll send another patch *about* using Bugzilla to the Bugzilla :P
> 
> ~Andrew
> 
> 
> On Tue, 2015-10-27 at 14:46 +, Pat David wrote:
> > Ok, finally got the patch uncorrupted and merged/applied.  (The
> > changes should be live shortly, if they aren't already).
> > 
> > I also should be reprimanded for not pointing out earlier that we
> > can
> > should also probably take patches through bugzilla:
> > 
> > https://bugzilla.gnome.org/enter_bug.cgi?product=gimp-web
> > 
> > where you can actually attach the patch.
> > 
> > Thank you very much for being patient and re-sending.  Helping to
> > ease the process of contributions is definitely something we'll
> > look
> > at soon, but for now if you want to submit any other patches,
> > please
> > attach them in bugzilla.
> > 
> > On Mon, Oct 26, 2015 at 11:27 PM Andrew Toskin <and...@tosk.in>
> > wrote:
> > > I installed the git send-email module (listed as `git-email` on
> > > Fedora), but I don't understand it. I can't get it to send
> > > anything
> > > in
> > > my tests. I'm probably not the first person to complain about
> > > this,
> > > but
> > > GitHub/GitLab-style pull requests really seem like the better way
> > > to do
> > > this sort of thing...
> > > 
> > > Whatever. Try downloading the patch from my website. <
> > > https://andrew.to
> > > sk.in/patches/2015-10-22--explain-how-to-contribute-to-the-gimp
> > > -projects.patch>
> > > 
> > > ~Andrew
> > > 
> > > 
> > > On Mon, 2015-10-26 at 20:49 -0700, Andrew Toskin wrote:
> > > > On Mon, 2015-10-26 at 19:12 +, Pat David wrote:
> > > > > Andrew,
> > > > > 
> > > > > I think the email mangled your patch data - was it a webmail
> > > client
> > > > > that did this, or did you use the sendmail/git feature?
> > > > > 
> > > > > I'm trying to apply your patch and getting errors about a
> > > corrupt
> > > > > patch file.
> > > > The first time I sent it with Evolution, the default email
> > > > client
> > > in
> > > > GNOME. Then I did it from my webmail, RoundCube.
> > > > 
> > > > Will it only work with git send-email? I see it documented at
> > > > git
> > > > -scm.com, but it's not an available git command (on my system,
> > > > running git 2.4.3 on Fedora 22).
> > > > 
> > > > ~Andrew
> > > > 
> > > > 
> > > > > On Sat, Oct 24, 2015 at 3:18 PM Andrew Toskin <and...@tosk.in
> > > > > >
> > > > > wrote:
> > > > > > 
> > > > > > On 2015-10-23 06:35, Pat David wrote:
> > > > > > 
> > > > > > > It seems that the list may have stripped out your
> > > attachment?
> > > > > > 
> > > > > > Huh. I'll try attaching it again, but just in case, here's
> > > the
> > > > > > patch
> > > > > > file pasted below.
> > > > > > 
> > > > > > From 580337e443bcca55b1e70bae72fcebcf9cdc50e6 Mon Sep 17
> > > 00:00:00
> > > > > > 2001
> > > > > > From: Andrew Toskin <and...@tosk.in>
> > > > > > Date: Thu, 22 Oct 2015 20:59:41 -0700
> > > > > > Subject: [PATCH] Explain *how* to contribute to the GIMP
> > > > > > projects.
> > > > > > 
> > > > > > The "Development Status", "Bug Reports" and "Web
> > > > > > Development"
> > > > > > headings
> > > > > > seemed to
> > > > > > me like they were really subsections of "How You Can Help,"
> > > so I
> > > > > > set
> > > > > > those to be
> > > > > > h3 headings.
> > > > > > 
> > > > > > A couple times, in the "Hacking" and "How To Submit Your
> > > Changes"
> > > > > > sections, I
> > > > > > tried to borrow the tone of Wikipe

Re: [Gimp-web] Microdata markup formats

[Andrew Toskin]

You can definitely mix and match microdata formats without causing any
issues, unless maybe you accidentally put conflicting information
between the different formats. Changes to metadata in one format will
need to be updated in all other formats. Shouldn't be too hard to keep
straight.
Microformats might be a good choice too -- http://microformats.org/wiki
/Main_Page -- its markup only uses class and rel attributes, so it
neatly blends in with normal HTML. And if we applied CSS based on the
Microformats class attributes (which could be appropriate, for example,
with the h-card class for GIMP contact information), then we could
actually minimize how much extra markup the microdata adds to every
page.
I like OpenGraph too, because it's the easiest to understand and
implement -- just add a few  tags to the document  instead
of trying to incorporate microdata throughout the page -- and pretty
widely supported.
~Andrew
On Wed, 2015-11-25 at 18:09 +, Pat David wrote:
> I'm in the middle of adding micordata markup the WGO and was
> wondering if
> anyone had any input concerning implementation, types, or formats.
> 
> At the moment I'm going to focus on both schema.org microdata
> (considering
> JSON-LD, but likely microdata atm) and opengraph.  I can't seem to
> find any
> issues with using both at the same time.  If someone knows, please
> chime in.
> ___
> gimp-web-list mailing list
> gimp-web-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-web-list
___
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Re: [Gimp-web] Social media: consolidation of comments

[Andrew Toskin]

 

For consolidating discussions: on Twitter I don't think it's too hard to
follow posts that tag #gimp or refer to the @gimp account. On Facebook,
people could comment on the GIMP page's "wall." If what you really want
is for people to be able to talk together in a single place, then
probably a forum would be better. 

Discourse may or may not have been the appropriate choice for a plugin
registry type site, I dunno. But it makes for an *excellent* forum. 

Note: There actually already is an unofficial GIMP forum
. It's just a little slow, and the web design
isn't nearly as beautiful and feature-rich as a Discourse site would
be... I've only given it a cursory look, but Discourse has tools for
importing existing forums, so we might possibly conserve some effort if
we wanted to see if the people at gimpforums.com were receptive to
switching to a more lovely and more advanced forum application... Or,
y'know, just leave the forum as it is, and link to their site from
gimp.org. 

Starting a new forum, or linking to (and revitalizing) the existing
unofficial forum, could possibly reinvigorate the community discussion,
though. 

~Andrew / terrycloth 

On 2016-01-21 06:51, Pat David wrote: 

> Not sure how to consolidate things. None of these services is exactly open
> to aggregating their content in a single place (and it's not in their best
> interest to do so).
> 
> With that being said, I suppose there's always the possibility of setting
> up a central place for users to congregate. A forum perhaps? (I've had
> good results with discourse for pixls.us so far). Though I feel like this
> might require an inordinately large amount of time policing and we may not
> have the interest/manpower available to handle it. :( (Not just spam -
> that's already reasonably well handled by default).
> 
> Actually, this was also part of an idea I had for transitioning the plugin
> registry to something else as well. I had put this on hold but can
> certainly re-visit the idea...
> 
> On Thu, Jan 21, 2016 at 12:18 AM Alexandre Prokoudine <
> alexandre.prokoud...@gmail.com> wrote:
> Sven Claussner wrote: Now that we are also on Facebook and Twitter I find a 
> bit inconvenient to check each single social media site for discussions and 
> comments on posts from our eager public relations people. Would it be 
> possible that they are consolidated in a single place? How do you expect this 
> to work? Alex ___ gimp-web-list 
> mailing list gimp-web-list@gnome.org 
> https://mail.gnome.org/mailman/listinfo/gimp-web-list [1]
 

Links:
--
[1] https://mail.gnome.org/mailman/listinfo/gimp-web-list
___
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Re: [Gimp-web] Gitlab as a replacement for registry.gimp.org

[Andrew Toskin]

 

I rather like GitLab, and this seems like at least as good a solution
for a plugin registry as any other solution we've considered so far. 

In fact, I think GitLab (or some similar solution) would also be a major
improvement for tracking the core GIMP software. As an occasional
contributor just to the documentation, I find Bugzilla, and the process
of creating and uploading patch files, cumbersome and weirdly
old-fashioned. GitLab could do everything Bugzilla or cgit can, and much
more, _and_ it's got a much better UI and workflow. 

~Andrew 

On 2016-04-01 13:32, Pat David wrote: 

> Continuing on some discussions from irc...
> 
> Registry.gimp.org is down for the count.
> 
> I was thinking recently about some ideas for a possible replacement.
> Mostly thinking along the lines of what made the registry work well for
> folks.
> 
> In the rest of this email, I'll use the term "asset(s)" to refer to things
> like plug-ins, scripts, or brushes/gradients/curves/other assets.
> 
> Some essential functionality based on the old registry drupal instance:
> 
> 1. Upload/Download assets for GIMP.
> 2. Describe the asset (usually by the uploader).
> 3. Comment on the assets.
> 
> This was handled previously by using drupal, which treated each entry as a
> post/node that included the ability to upload files, write about the files
> as a post, and had comment threads below it.
> 
> Keeping this functionality would be good, I think. The ability to post an
> asset is a given, but the ability to interact around it helps foster the
> community (and provides nice feedback for the authors).
> 
> From those thoughts, what would be nice to have in a replacement:
> 
> 1. Provide at least the same previous functionality (as listed above).
> 2. Managed or easier to manage and keep updated.
> 3. Easier account management.
> 4. Collaborative environment for shared assets
> 5. Support possible GIMP integration in the future (one-click asset
> install?).
> 
> GitLab?
> ==
> 
> Initially, I had thought Github might be a good option for this but given
> its closed-source nature decided to investigate something like GitLab
> instead.
> 
> I like this idea personally due to some nice infrastructure:
> 
> 1. The service is hosted + managed (and available as Free Software just in
> case we felt we needed to break out and host it ourselves).
> 2. The service integrates OAuth sign-in using a few different account types
> (lowers barrier to entry to participate).
> a. they use accounts, Google, Twitter, Github, or bitbucket accounts
> for sign-in.
> 3. Projects maintain all the git-goodness for control and tracking
> 4. Projects created as a git project can have a full description/README
> along with issue tracking integrated in the site
> 
> So, we can fulfill the original registry functionality and get the added
> benefit of a git infrastructure for those wanting to contribute, user
> accounts using OAuth to make it easy to participate, and the ability to do
> some interesting things (git submodules).
> 
> In speaking with Jehan about this, we should also consider what might be
> needed to support the ability to install assets from within GIMP in the
> future easily.
> 
> Organization
> =
> 
> Jehan suggested that each script/plugin/asset have it's own git repo.
> This would be handy, particularly if script authors did this as well (as it
> considerably eases the inclusion of external repos as submodules).
> However, akk points out that many folks don't (won't?) organize their repos
> in this way (it gets a little... unwieldy pretty quickly if you have many
> scripts).
> 
> I'd like some input on what would make the most sense or work best for
> possible organization of repos.
> 
> I was also thinking that we could include some simple metadata in both any
> script files and the README.md files as a means to possibly help parsing
> relevant information for automated inclusion at a later date (GIMP plug-ins
> installer type of idea).
> 
> Curation
> ==
> 
> Initially I was thinking that curating the scripts for inclusion would be
> important. It's certainly possible for a smaller subset of all of the
> available scripts from the registry now to pick out ones that we use and
> check that they're not malicious and properly tagged/included. For
> instance, there's a handful of scripts that I personally find myself using
> often and can help validate/curate for inclusion. I don't mind doing more
> as needed.
> 
> I just wanted to get a discussion started about how we might consider
> moving forward on something like this. I think the scripts/plug-ins are
> important enough to users that it would be good to try and get something up
> and running soon.
> 
> I have started experimenting with including submodules from other author
> repos and how it might look here:
> 
> https://gitlab.com/GIMP/GIMP-Scripts/tree/master [1]
> 
> I look forward to hearing some thoughts on this!
> 
> pat
 

Links:
--
[1] 

Re: [Gimp-web] Gitlab as a replacement for registry.gimp.org

[Andrew Toskin]

 

> On 2016-04-01 13:32, Pat David wrote: 
> 
> Organization
> =
> 
> Jehan suggested that each script/plugin/asset have it's own git repo.
> This would be handy, particularly if script authors did this as well (as it
> considerably eases the inclusion of external repos as submodules).
> However, akk points out that many folks don't (won't?) organize their repos
> in this way (it gets a little... unwieldy pretty quickly if you have many
> scripts).

Whether or not we can get plugin developers to follow it, separating
scripts and plugins into different repositories seems like a good
recommendation, for a number of reasons. For plugin and script authors,
it would make managing bugs and user feedback easier. For end users,
it's also annoying to clone a large repository when you're only
interested in a small subset of its contents. If authors are really
going to lump together their plugins and scripts, we could at least
recommend that they try to only group together the things that are most
closely related. Create several smaller collections of scripts, instead
of one giant collection. 
___
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list