[Live-demo] Presentation workflow

Angelos Tzotsos gcpp.kalxas at gmail.com
Thu Sep 5 02:57:49 PDT 2013

Hi Brian,

The basic GitHub workflow is the following:
1. Fork a project in your account
2. git clone your fork
3. Make local changes to source
4. git commit your changes to your local copy
5. git push your changes to your online fork
6. issue a pull request to the original project in order to merge your
changes. Yes, this can happen via a plain e-mail too if you want to avoid
the GitHub UI.

As Cameron said, there is work in progress to have the presentation merged
into the main docs for 7.5. Translations can happen in svn then.


On Wed, Sep 4, 2013 at 7:38 PM, Brian Hamlin <maplabs at light42.com> wrote:

> Angelos -
>   could you explain to me again the workflow with the presentation ?  I
> know you did once.. sometimes I am slow..
> *  I have made a clone of the GitHub repository  in my GitHub account, and
> then clone again from that to my local machine.
> *  When I change the presentation on my local machine, and I am satisfied
> with the changes, I "pull" from my own machine to my GitHub account.
> * At that point, I can either
>   - push the GitHub button to send a "pull request" to the "Master" of
> this clone (which results in a record of all my actions at GitHub), OR
>   - I can send an email, or in IRC, ask an owner of the GitHub "master" to
> pull from my github account
> Is this accurate?
> Are all international translators going to use the same method?
> Is the svn version of the presentation a "cold copy" of the GitHub master?
>  or what ...
> thanks for your patience
> --
> Brian M Hamlin
> OSGeo California Chapter

Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/osgeolive/attachments/20130905/6991528d/attachment.html>

More information about the Osgeolive mailing list