Hi all.
Any taker?
All the best.

Il 19/05/2014 11:15, Nathan Woodrow ha scritto:
> Good idea. I like it.
> 
> On May 19, 2014 7:08 PM, "Paolo Cavallini" <[email protected]
> <mailto:[email protected]>> wrote:
> 
>     Hi all.
>     Why not adding a CONTRIBUTING.md file, following the suggestions from 
> Jody?
>     All the best.
> 
> 
>     -------- Messaggio originale --------
>     Oggetto:        Re: [OSGeo-Discuss] How not to suck at github - handling 
> drive by
>     commits
>     Data:   Fri, 16 May 2014 13:02:11 -0700
>     Mittente:       Jody Garnett <[email protected] 
> <mailto:[email protected]>>
>     A:      OSGeo Discussions <[email protected] 
> <mailto:[email protected]>>
> 
> 
> 
>     Here is a description on how to use
>     CONTRIBUTING.md https://github.com/blog/1184-contributing-guidelines
> 
>     Jody Garnett
> 
> 
>     On Fri, May 16, 2014 at 12:48 PM, Jody Garnett <[email protected]
>     <mailto:[email protected]>
>     <mailto:[email protected] <mailto:[email protected]>>> wrote:
> 
>         I have mentioned this in email/blog posts, but with the recent 
> discussion on
>         GitHub I would like to send a reminder.
> 
>         If your project is operating on GitHub please include an 
> CONTRIBUTING.md file.
>         This link will provided on the pull-request page for potential 
> contributors.
> 
>         Here are some examples:
> 
>         - https://github.com/geotools/geotools/blob/master/CONTRIBUTING.md
>         - https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md
> 
>         GitHub provides excellent documentation (the reason uDig migrated for 
> Gitourious)
>         and the fork/pull-request workflow makes "drive by commits" very 
> easy. This
>         CONTRIBUTIONS.md gives your team a chance to communicate any terms 
> (include a
>         test case, sign a contribution agreement) clear.
> 
>         Many of us are comfortable with open source as a user, understanding 
> the
>         difference between GPL and BSD for example. The outline the terms for 
> users of
>         the software. There is a second level of open source licenses 
> outlining the terms
>         the project team requires when accepting contributions back into the 
> "core"
>     codebase.
> 
>         For an example "Apache Style" contributor license agreements are 
> available for
>         OSGeo Projects here:Â 
> http://www.osgeo.org/content/foundation/legal/licenses.html


-- 
Paolo Cavallini - www.faunalia.eu
Corsi QGIS e PostGIS: http://www.faunalia.eu/training.html
_______________________________________________
Qgis-developer mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to