Re: [Gimp-docs] Hello!

2017-09-14 Thread Julien Hardelin 

Welcome,


Many chapters have to be updated, rebuilt or created. There is no 
complete list of what is to be done. You can find some indications in 
the "bug" list of Bugzila 
:https://bugzilla.gnome.org/buglist.cgi?bug_status=__open__=gimp%20manual_redirect=1=Importance=GIMP-manual_format=specific. 
Also when you have built the html files of the work in progress, you 
will find a What's new in GIMP-2.10 section.


But the main way is to compare gimp-2.9.6 with the help html files.

The Gimp manual has a long history. Unless you want to create a 
completely new manual, your work has to fit the existing document.


I attach a How to contribute html file that summarizes my experience.


Julien Hardelin


Le 14/09/2017 à 17:27, Famiglietti, Andrew A a écrit :


Hi Gimp Documentation List!


I'm a professor in the English Department at West Chester University 
of Pennsylvania, and I'm planning to use Open Source Software 
documentation as a "real world" writing task for my Technical Writing 
Students this semester. I noticed your project was looking for 
documentation help and thought I would reach out. Some things you 
should know:


- I'm not going to swamp you with student pull requests. Students will 
file their drafts with me, first, and then I will pass them on to you 
only if I think they have a reasonably good end product, and I have an 
ok from the project


I was wondering:

- If you would be interested in seeing the documentation drafts 
students produce
- If there was any particular area of documentation you were 
particularly in need of


Thanks so much for your time!

​

---
Andy Famiglietti, PhD
Assistant Professor of English, West Chester University
http://copyvillain.org 


___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list


Title: 6. How to Contribute



  
  

  

  6. How to Contribute


  

  

  
  Chapter 3. First Steps with Wilber
   

  
  


  

  
6. How to Contribute
  

  
  
  
Welcome to the GIMP-Help team!
  
  
This tutorial is intended for writing documentation. If you want to 
translate the documentation or the user interface, 
please go to "https://l10n.gnome.org/teams/xx" where "xx"  
is your language code: ISO 639-1 language codes can be found at
http://www.loc.gov/standards/iso639-2/php/code_list.php.
  
  

  Prerequisite


  
Join our mailing list>
  
  
You can join our mailing list at
  https://mail.gnome.org/mailman/listinfo/gimp-docs-list.
  Please, feel free to ask questions.

  
  
Create a Local Working Copy of Code
  
  

  The GIMP help Manual is lodged in a central repository at
  http://git.gnome.org. Creating a local copy of this repository to work
  on makes sure that everyone can work on his own without fuzzing around
  into works of other contributors.


  As a newbie, you will access the git repository anonymously (without 
  an account). Open a terminal and type:
  git clone git://git.gnome.org/gimp-help-2.


  If you have a GNOME account, the command is:
  git clone ssh://yourusername>@git.gnome.org/git/gimp-help-2
  .


  This will create a “gimp-help-2” folder in your current
  directory. Be patient! That's a big download: about 700 MB.

  
  
Installing your sandbox
  
  

  After downloading your local copy, run:
  cd gimp-help-2 then
  ./autogen.sh --without-gimp.


  When running ./autogen.sh, you can notice some not found packages, for
  example “checking for dblatex... no”. Most of them are
  related to PDF files and you have to install them before running
  ./autogen.sh again if you want to create PDF files.

  
  
The gimp-help-2 folder
  
  

  The GIMP User Manual is maintained in the xml files of the
  “src” folder. These xml files are used by developers. 

  

  
  

  Workflow


  
Writing
  
  

  The language is English (USA).


  To edit XML files, use your preferred text editor. Personally I use 
  Kate. You must set the editor for:

Re: [Gimp-docs] Hello!

2017-09-14 Thread Famiglietti, Andrew A 
Thanks for all the interest!

I'd work with students to try to find a narrow issue to address, in whatever 
category they choose to work in.

I find that students can have useful things to contribute when it comes to the 
onboarding process, since they are often newer users themselves and can think 
about what they needed to know getting started.

As for video, I'm not planning a video assignment this time around, but perhaps 
in the next iteration of the class...?



---
Andy Famiglietti, PhD
Assistant Professor of English, West Chester University
http://copyvillain.org

From: gimp-docs-list  on behalf of Bill 
Skaggs 
Sent: Thursday, September 14, 2017 12:28 PM
To: Alexandre Prokoudine
Cc: gimp-docs-list@gnome.org
Subject: Re: [Gimp-docs] Hello!

Maybe broad is not quite the right term, but I believe both would be hard for 
students to write about effectively, unless they have had quite a bit of 
experience using the software.

Bill

On Thu, Sep 14, 2017 at 9:21 AM, Alexandre Prokoudine 
> wrote:
On Thu, Sep 14, 2017 at 7:15 PM, Bill Skaggs 
> wrote:
> It's very difficult for students to write about broad topics like that.

Which of the two areas of concern that I mentioned do you find broad? :)

Alex
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list

___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list

Re: [Gimp-docs] gimp-docs-list Digest, Vol 57, Issue 1

2017-09-14 Thread Gayle CDer via gimp-docs-list 
Get Bent!

  From: "gimp-docs-list-requ...@gnome.org" 
<gimp-docs-list-requ...@gnome.org>
 To: gimp-docs-list@gnome.org 
 Sent: Thursday, September 14, 2017 12:22 PM
 Subject: gimp-docs-list Digest, Vol 57, Issue 1
   
Send gimp-docs-list mailing list submissions to
    gimp-docs-list@gnome.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://mail.gnome.org/mailman/listinfo/gimp-docs-list
or, via email, send a message with subject or body 'help' to
    gimp-docs-list-requ...@gnome.org

You can reach the person managing the list at
    gimp-docs-list-ow...@gnome.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of gimp-docs-list digest..."


Today's Topics:

  1.  Hello! (Famiglietti, Andrew A)
  2. Re:  Hello! (Alexandre Prokoudine)
  3. Re:  Hello! (dana thurston)
  4. Re:  Hello! (Bill Skaggs)
  5. Re:  Hello! (Alexandre Prokoudine)


--

Message: 1
Date: Thu, 14 Sep 2017 15:27:34 +
From: "Famiglietti, Andrew A" <afamiglie...@wcupa.edu>
To: "gimp-docs-list@gnome.org" <gimp-docs-list@gnome.org>
Subject: [Gimp-docs] Hello!
Message-ID: <0cfe99db258e4fe5914ae797acfe6...@wcuxchp07.passhe.lcl>
Content-Type: text/plain; charset="iso-8859-1"

Hi Gimp Documentation List!


I'm a professor in the English Department at West Chester University of 
Pennsylvania, and I'm planning to use Open Source Software documentation as a 
"real world" writing task for my Technical Writing Students this semester. I 
noticed your project was looking for documentation help and thought I would 
reach out. Some things you should know:

- I'm not going to swamp you with student pull requests. Students will file 
their drafts with me, first, and then I will pass them on to you only if I 
think they have a reasonably good end product, and I have an ok from the project

I was wondering:

- If you would be interested in seeing the documentation drafts students produce
- If there was any particular area of documentation you were particularly in 
need of

Thanks so much for your time!

?

---
Andy Famiglietti, PhD
Assistant Professor of English, West Chester University
http://copyvillain.org<http://copyvillain.org/>
-- next part --
An HTML attachment was scrubbed...
URL: 
<https://mail.gnome.org/archives/gimp-docs-list/attachments/20170914/8aeb0dcd/attachment.html>

--

Message: 2
Date: Thu, 14 Sep 2017 19:05:14 +0300
From: Alexandre Prokoudine <alexandre.prokoud...@gmail.com>
To: "gimp-docs-list@gnome.org" <gimp-docs-list@gnome.org>
Subject: Re: [Gimp-docs] Hello!
Message-ID:
    <cafjkzc0esa-+1pz0b58mt02es2b-w89gc+ybbxdaxhg7oxi...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

On Thu, Sep 14, 2017 at 6:27 PM, Famiglietti, Andrew A wrote:
> Hi Gimp Documentation List!
>
>
> I'm a professor in the English Department at West Chester University of
> Pennsylvania, and I'm planning to use Open Source Software documentation as
> a "real world" writing task for my Technical Writing Students this semester.
> I noticed your project was looking for documentation help and thought I
> would reach out. Some things you should know:
>
> - I'm not going to swamp you with student pull requests. Students will file
> their drafts with me, first, and then I will pass them on to you only if I
> think they have a reasonably good end product, and I have an ok from the
> project
>
> I was wondering:
>
> - If you would be interested in seeing the documentation drafts students
> produce

Yes, definitely!

> - If there was any particular area of documentation you were particularly in
> need of

Personally, I think that both "Getting Started" and "How do I Become a
GIMP Wizard?" sections need revisiting, because a lot of chapters from
the latter one belong to the foremr one really.

Moreover, the user manual is still missing updates for the upcoming
v2.10. Julien Hardelin would be a better judge of that though.

Alex


--

Message: 3
Date: Thu, 14 Sep 2017 12:15:38 -0400
From: dana thurston <danathurs...@gmail.com>
To: Alexandre Prokoudine <alexandre.prokoud...@gmail.com>
Cc: "gimp-docs-list@gnome.org" <gimp-docs-list@gnome.org>
Subject: Re: [Gimp-docs] Hello!
Message-ID:
   

Re: [Gimp-docs] Hello!

2017-09-14 Thread Bill Skaggs 
Maybe broad is not quite the right term, but I believe both would be hard
for students to write about effectively, unless they have had quite a bit
of experience using the software.

Bill

On Thu, Sep 14, 2017 at 9:21 AM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:

> On Thu, Sep 14, 2017 at 7:15 PM, Bill Skaggs  wrote:
> > It's very difficult for students to write about broad topics like that.
>
> Which of the two areas of concern that I mentioned do you find broad? :)
>
> Alex
> ___
> gimp-docs-list mailing list
> gimp-docs-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-docs-list
>
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list

Re: [Gimp-docs] Hello!

2017-09-14 Thread Alexandre Prokoudine 
On Thu, Sep 14, 2017 at 7:15 PM, Bill Skaggs  wrote:
> It's very difficult for students to write about broad topics like that.

Which of the two areas of concern that I mentioned do you find broad? :)

Alex
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list

Re: [Gimp-docs] Hello!

2017-09-14 Thread Bill Skaggs 
It's very difficult for students to write about broad topics like that.
The chances of getting a useful result are much higher if they focus on
limited domains such as tools, plug-ins, resources, etc.

On Thu, Sep 14, 2017 at 9:05 AM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:

> On Thu, Sep 14, 2017 at 6:27 PM, Famiglietti, Andrew A wrote:
> > Hi Gimp Documentation List!
> >
> >
> > I'm a professor in the English Department at West Chester University of
> > Pennsylvania, and I'm planning to use Open Source Software documentation
> as
> > a "real world" writing task for my Technical Writing Students this
> semester.
> > I noticed your project was looking for documentation help and thought I
> > would reach out. Some things you should know:
> >
> > - I'm not going to swamp you with student pull requests. Students will
> file
> > their drafts with me, first, and then I will pass them on to you only if
> I
> > think they have a reasonably good end product, and I have an ok from the
> > project
> >
> > I was wondering:
> >
> > - If you would be interested in seeing the documentation drafts students
> > produce
>
> Yes, definitely!
>
> > - If there was any particular area of documentation you were
> particularly in
> > need of
>
> Personally, I think that both "Getting Started" and "How do I Become a
> GIMP Wizard?" sections need revisiting, because a lot of chapters from
> the latter one belong to the foremr one really.
>
> Moreover, the user manual is still missing updates for the upcoming
> v2.10. Julien Hardelin would be a better judge of that though.
>
> Alex
> ___
> gimp-docs-list mailing list
> gimp-docs-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-docs-list
>
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list

Re: [Gimp-docs] Hello!

2017-09-14 Thread dana thurston 
That is really cool, Professor!

Do you have your own YouTube/Vidme/Minds channel? I find that individuals
put up videos and that is how I learn (and re-learn) techniques in GIMP.

Loyal user for 6 years.

Dana

On Thu, Sep 14, 2017 at 12:05 PM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:

> On Thu, Sep 14, 2017 at 6:27 PM, Famiglietti, Andrew A wrote:
> > Hi Gimp Documentation List!
> >
> >
> > I'm a professor in the English Department at West Chester University of
> > Pennsylvania, and I'm planning to use Open Source Software documentation
> as
> > a "real world" writing task for my Technical Writing Students this
> semester.
> > I noticed your project was looking for documentation help and thought I
> > would reach out. Some things you should know:
> >
> > - I'm not going to swamp you with student pull requests. Students will
> file
> > their drafts with me, first, and then I will pass them on to you only if
> I
> > think they have a reasonably good end product, and I have an ok from the
> > project
> >
> > I was wondering:
> >
> > - If you would be interested in seeing the documentation drafts students
> > produce
>
> Yes, definitely!
>
> > - If there was any particular area of documentation you were
> particularly in
> > need of
>
> Personally, I think that both "Getting Started" and "How do I Become a
> GIMP Wizard?" sections need revisiting, because a lot of chapters from
> the latter one belong to the foremr one really.
>
> Moreover, the user manual is still missing updates for the upcoming
> v2.10. Julien Hardelin would be a better judge of that though.
>
> Alex
> ___
> gimp-docs-list mailing list
> gimp-docs-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-docs-list
>
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list

Re: [Gimp-docs] Hello!

2017-09-14 Thread Alexandre Prokoudine 
On Thu, Sep 14, 2017 at 6:27 PM, Famiglietti, Andrew A wrote:
> Hi Gimp Documentation List!
>
>
> I'm a professor in the English Department at West Chester University of
> Pennsylvania, and I'm planning to use Open Source Software documentation as
> a "real world" writing task for my Technical Writing Students this semester.
> I noticed your project was looking for documentation help and thought I
> would reach out. Some things you should know:
>
> - I'm not going to swamp you with student pull requests. Students will file
> their drafts with me, first, and then I will pass them on to you only if I
> think they have a reasonably good end product, and I have an ok from the
> project
>
> I was wondering:
>
> - If you would be interested in seeing the documentation drafts students
> produce

Yes, definitely!

> - If there was any particular area of documentation you were particularly in
> need of

Personally, I think that both "Getting Started" and "How do I Become a
GIMP Wizard?" sections need revisiting, because a lot of chapters from
the latter one belong to the foremr one really.

Moreover, the user manual is still missing updates for the upcoming
v2.10. Julien Hardelin would be a better judge of that though.

Alex
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list

[Gimp-docs] Hello!

2017-09-14 Thread Famiglietti, Andrew A 
Hi Gimp Documentation List!


I'm a professor in the English Department at West Chester University of 
Pennsylvania, and I'm planning to use Open Source Software documentation as a 
"real world" writing task for my Technical Writing Students this semester. I 
noticed your project was looking for documentation help and thought I would 
reach out. Some things you should know:

- I'm not going to swamp you with student pull requests. Students will file 
their drafts with me, first, and then I will pass them on to you only if I 
think they have a reasonably good end product, and I have an ok from the project

I was wondering:

- If you would be interested in seeing the documentation drafts students produce
- If there was any particular area of documentation you were particularly in 
need of

Thanks so much for your time!

?

---
Andy Famiglietti, PhD
Assistant Professor of English, West Chester University
http://copyvillain.org
___
gimp-docs-list mailing list
gimp-docs-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-docs-list