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

[Pat David]

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  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.  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 
> > > 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 
> > > > 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.
> > > > 
> > > >
> > > > 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

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 
> 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 
> > > > 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 
> > > > > 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.
> > > > > 
> > > > >
> > > > > 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
>