[OWSLib-devel] github migration

[Jachym Cepicky]

IMHO that is question of if the level of transparency vs. speed.

It would be mayebe cleaner, if core commiters would make pull requests
as well. Github can then visualize the approach of each person in very
nice way

https://github.com/openlayers/openlayers/graphs

Maybe even cross-checking of the code would be nice as well, but IMHO
there are not so many developers around the project (test should be
enough).

So basic approach for core commiters would be

1 - fork
2 - changes
3 - pull request
4 - (wait till somebody review it, if nobody would (usual case)), accept
your own pull request

j

Dne 20.6.2012 23:33, Tom Kralidis napsal(a):
> 
> 
> Jachym: I'm +1 with this approach.
> 
> So the OWSLib is our core committer list.  What happens when one of us makes a change/feature/fix/etc.?  Do we fork and branch and do pull request?  Do we just commit straight to the repo?
> 
> ..Tom
> 
> 
> 
> 
> ----------------------------------------
>> Date: Wed, 20 Jun 2012 23:24:48 +0200
>> From: jachym.cepicky at gmail.com
>> To: tomkralidis at hotmail.com
>> CC: owslib-devel at lists.osgeo.org
>> Subject: Re: [OWSLib-devel] github migration
>>
>> Hi,
>>
>> I have to say, that after some time, I really like the openlayers-github
>> approach:
>>
>> 1) each developer creates fork of the master branch of the source
>> 2) after chnages are done, deloper asks for pull request
>> 3) discussion happens. once the code is polished, pull request is
>> accepted by the core-committer
>>
>> detailed description here https://help.github.com/articles/fork-a-repo
>>
>> Example of such process:
>>
>> https://github.com/openlayers/openlayers/pull/523
>>
>> Works nice
>>
>> +1 for such approach
>>
>> Jachym
>>
>> P.S. Sorry, if this was clear to everybody and everybody is fine with that.
>>
>> Dne 20.6.2012 23:15, Tom Kralidis napsal(a):
>>>
>>>
>>> Devs: FYI I've ported the svn repo (with tags/branches) to github:
>>>
>>> https://github.com/geopython/OWSLib
>>>
>>> I've made a geopython organization, under which is an OWSLib team, which all committers to OWSLib are part of. If you are a committer are not a part of this team, please let me know. I'm also in the midst of porting the trac tickets to github as well.
>>>
>>> Dom: FYI I need a github username from yourself to add to the team.
>>>
>>> Can folks take a look at the new git repo and ensure everything is ok? I'd like, by next week, to make this the official repo and issue tracker, and update the codebase docs/etc. to reflect this.
>>>
>>> Do folks think this should warrant a 0.5.1 release? This would update our docs/etc. on pypi as well.
>>>
>>> If possible, please refrain from commits to svn and work off github.
>>>
>>> Thanks
>>>
>>> ..Tom
>>>
>>> _______________________________________________
>>> OWSLib-devel mailing list
>>> OWSLib-devel at lists.osgeo.org
>>> http://lists.osgeo.org/cgi-bin/mailman/listinfo/owslib-devel
>>
>> --
>> Jachym Cepicky
>> Help Service - Remote Sensing s.r.o.
>> jachym.cepicky at gmail.com
>> HS-RS: jachym at hsrs.cz http://bnhelp.cz
>> http://les-ejk.cz
>>
>  		 	   		  

-- 
Jachym Cepicky
Help Service - Remote Sensing s.r.o.
jachym.cepicky at gmail.com
HS-RS: jachym at hsrs.cz http://bnhelp.cz
http://les-ejk.cz

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: OpenPGP digital signature
URL: <http://lists.osgeo.org/pipermail/owslib-devel/attachments/20120621/b1d26974/attachment-0001.pgp>