<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<br>FYI I have granted Kyle svn access.<br><br>Kyle: branch is https://owslib.svn.sourceforge.net/svnroot/owslib/branches/kyle-github/, trunk is https://owslib.svn.sourceforge.net/svnroot/owslib/trunk/ (be sure to be current to trunk in the branch).<br><br>Once the branch is stabilized, we can more ahead with integration into trunk.<br><br>..Tom<br><br><br><div><div id="SkyDrivePlaceholder"></div>> From: KWilcox@asascience.com<br>> To: jachym.cepicky@gmail.com; Luca.Cinquini@jpl.nasa.gov<br>> CC: tomkralidis@hotmail.com; owslib-devel@lists.sourceforge.net; SCowan@asascience.com; derrick.snowden@noaa.gov<br>> Date: Mon, 11 Jun 2012 17:38:26 -0400<br>> Subject: RE: [owslib-devel] owslib fork on github<br>> <br>> I agree, this is getting out of control quickly.<br>> <br>> Can you grant me commit access to the kyle-github branch and I will get all of the tests passing? It is at a good place for integration<br>> <br>> > -----Original Message-----<br>> > From: Jachym Cepicky [mailto:jachym.cepicky@gmail.com]<br>> > Sent: Monday, June 11, 2012 4:18 PM<br>> > To: Cinquini, Luca (3880)<br>> > Cc: Kyle Wilcox; Tom Kralidis; owslib-devel@lists.sourceforge.net; Sean<br>> > Cowan; derrick.snowden@noaa.gov<br>> > Subject: Re: [owslib-devel] owslib fork on github<br>> > <br>> > Kyle,<br>> > <br>> > I'm glad, the tests are working and your work is approaching well, but if you<br>> > will continue with the development any further, we will never be able to<br>> > merge your useful changes back to SVN. Even I like GIT as well and see it's<br>> > advantages over SVN, please accept, that SVN is *the* repository, where<br>> > changes are made and GIT is only mirrored. If you want your patches to be<br>> > submitted, please work on the svn-created branch.<br>> > Once you (we all) consider it "done", we can move the changes between svn<br>> > branches easy.<br>> > <br>> > There was already proposal to move the main source code tree to GIT and I<br>> > think, once some finished release is out, nobody will be against it.<br>> > Till than, could you please merge your last changes back to the created svn-<br>> > branch, so we can evaluate the changes and put them to trunk?<br>> > <br>> > Thanks a lot for your work!<br>> > <br>> > Jachym<br>> > <br>> > P.S. There might be different way, how to track changes between two version<br>> > systems (svn and git in this case). But I do not know any other, beside of<br>> > making diffs manually in one (assuming, it is synchronized regular with the<br>> > trunk branch (or master)) and applying them - again manually to the other<br>> > system. This really takes all the advantage of distributed source code<br>> > management out. Not speaking about fun. So if anybody is aware about some<br>> > automatic way how to track those changes, please speak.<br>> > <br>> > Dne 11.6.2012 22:09, Cinquini, Luca (3880) napsal(a):<br>> > > Hi Kyle,<br>> > ><br>> > > On Jun 11, 2012, at 2:00 PM, Kyle Wilcox wrote:<br>> > ><br>> > >> Thanks Jachym<br>> > >><br>> > >> I just updated my 'trunk' branch on GitHub to be based on the most<br>> > >> recent SVN trunk (r1882)<br>> > >><br>> > >> Some of the commits to trunk in the past few days caused testing<br>> > >> errors so changes (additional commits) were needed<br>> > >><br>> > >> I also updated the WPS tests to go along with Tom's change to avoid parsing<br>> > a WPS's GetCaps on init.<br>> > ><br>> > > I actually had already updated the WPS tests in SVN trunk for the same<br>> > reason - it is likely to give you conflicts when merging, juts be aware...<br>> > ><br>> > > thanks, Luca<br>> > ><br>> > >><br>> > >> https://github.com/kwilcox/owslib/tree/trunk<br>> > >><br>> > >> 66/66 tests passing, /me is cheering<br>> > >><br>> > >>> -----Original Message-----<br>> > >>> From: Jachym Cepicky [mailto:jachym.cepicky@gmail.com]<br>> > >>> Sent: Sunday, June 10, 2012 3:45 PM<br>> > >>> To: Tom Kralidis<br>> > >>> Cc: Kyle Wilcox; dominic.lowe@stfc.ac.uk; owslib-<br>> > >>> devel@lists.sourceforge.net; derrick.snowden@noaa.gov; Sean Cowan<br>> > >>> Subject: Re: [owslib-devel] owslib fork on github<br>> > >>><br>> > >>> Hi Tom and Kyle,<br>> > >>><br>> > >>> one more commit, more stuff should be there, please check r1881<br>> > >>><br>> > >>> Hope, it looks well now<br>> > >>><br>> > >>> Jachym<br>> > >>><br>> > >>> Dne 8.6.2012 22:34, Tom Kralidis napsal(a):<br>> > >>>><br>> > >>>> Kyle: Jachym applied this patch in an svn branch<br>> > >>> (https://owslib.svn.sourceforge.net/svnroot/owslib/branches/kyle-git<br>> > >>> hub/), but it appears that some files did not get through/got<br>> > >>> deleted/got added.<br>> > >>>><br>> > >>>> Anyone know of other ways to successfully apply a git patch from<br>> > >>>> github to<br>> > >>> svn?<br>> > >>>><br>> > >>>> Kyle's fork provides some much needed test fixes and SensorML/SOS<br>> > >>> additions, and overall cleanup, so any advice here would be appreciated.<br>> > >>>><br>> > >>>> Thanks<br>> > >>>><br>> > >>>> ..Tom<br>> > >>>><br>> > >>>><br>> > >>>><br>> > >>>><br>> > >>>> From: KWilcox@asascience.com<br>> > >>>> To: tomkralidis@hotmail.com; jachym.cepicky@gmail.com<br>> > >>>> CC: dominic.lowe@stfc.ac.uk; owslib-devel@lists.sourceforge.net;<br>> > >>>> derrick.snowden@noaa.gov; SCowan@asascience.com<br>> > >>>> Date: Wed, 6 Jun 2012 17:53:42 -0400<br>> > >>>> Subject: RE: [owslib-devel] owslib fork on github<br>> > >>>><br>> > >>>> I’ve branched my code from master so it might be easier to<br>> > >>>> integrate into SVN. Here are the<br>> > >>>> commits:https://github.com/kwilcox/owslib/commits/trunk And the<br>> > >>>> diff from the current SVN trunk (r1873) is here:<br>> > >>>> https://github.com/downloads/kwilcox/owslib/diff From: Tom<br>> > >>>> Kralidis [mailto:tomkralidis@hotmail.com]<br>> > >>>> Sent: Wednesday, June 06, 2012 8:02 AM<br>> > >>>> To: jachym.cepicky@gmail.com<br>> > >>>> Cc: Kyle Wilcox; dominic.lowe@stfc.ac.uk;<br>> > >>>> owslib-devel@lists.sourceforge.net; derrick.snowden@noaa.gov; Sean<br>> > >>>> Cowan<br>> > >>>> Subject: RE: [owslib-devel] owslib fork on github<br>> > >>>> Jachym: agreed, although I've had my share of issues with git diffs in svn.<br>> > >>>><br>> > >>>> Kyle: can you provide a diff based on current git master?<br>> > >>>><br>> > >>>> Thanks<br>> > >>>><br>> > >>>> ..Tom<br>> > >>>><br>> > >>>>> Date: Tue, 5 Jun 2012 20:32:37 +0200<br>> > >>>>> From: jachym.cepicky@gmail.com<br>> > >>>>> To: tomkralidis@hotmail.com<br>> > >>>>> CC: kwilcox@asascience.com; dominic.lowe@stfc.ac.uk;<br>> > >>>>> owslib-devel@lists.sourceforge.net; derrick.snowden@noaa.gov;<br>> > >>>>> scowan@asascience.com<br>> > >>>>> Subject: Re: [owslib-devel] owslib fork on github<br>> > >>>>><br>> > >>>>> diff ?<br>> > >>>>><br>> > >>>>> J<br>> > >>>>><br>> > >>>>> Dne 5.6.2012 18:07, Tom Kralidis napsal(a):<br>> > >>>>>><br>> > >>>>>> Kyle: thanks for this valuable contribution.<br>> > >>>>>><br>> > >>>>>> Since the root codebase is on SVN, does anyone know how we can<br>> > >>>>>> make<br>> > >>> this into an SVN patch against which to review?<br>> > >>>>>><br>> > >>>>>> ..Tom<br>> > >>>>>><br>> > >>>>>><br>> > >>>>>>> From: KWilcox@asascience.com<br>> > >>>>>>> To: dominic.lowe@stfc.ac.uk<br>> > >>>>>>> Date: Tue, 22 May 2012 11:23:39 -0400<br>> > >>>>>>> CC: owslib-devel@lists.sourceforge.net;<br>> > >>>>>>> Derrick.Snowden@noaa.gov; SCowan@asascience.com<br>> > >>>>>>> Subject: Re: [owslib-devel] owslib fork on github<br>> > >>>>>>><br>> > >>>>>>> Tom pointed us at the two SOS branches in SVN and we reused what<br>> > >>> code was relevant. The SOS support follows the same design pattern<br>> > >>> as the other OWS services and should look familiar to the developers.<br>> > >>>>>>><br>> > >>>>>>>> -----Original Message-----<br>> > >>>>>>>> From: Dominic Lowe [mailto:dominic.lowe@stfc.ac.uk]<br>> > >>>>>>>> Sent: Tuesday, May 22, 2012 10:16 AM<br>> > >>>>>>>> To: Kyle Wilcox<br>> > >>>>>>>> Cc: owslib-devel@lists.sourceforge.net;<br>> > >>>>>>>> Derrick.Snowden@noaa.gov; Sean Cowan<br>> > >>>>>>>> Subject: Re: [owslib-devel] owslib fork on github<br>> > >>>>>>>><br>> > >>>>>>>> Hi,<br>> > >>>>>>>><br>> > >>>>>>>> This is great, it would be good to get this merged into the trunk.<br>> > >>>>>>>> Tom, didn't you start work on SOS support a while back?<br>> > >>>>>>>><br>> > >>>>>>>> Is this a completely new implementation or does it use some of<br>> > >>>>>>>> the old SOS code (which was in a branch).<br>> > >>>>>>>><br>> > >>>>>>>> Either way, I think it would be great to add SOS support to<br>> > >>>>>>>> OWSLib. And cleaning up the tests is a big favour...<br>> > >>>>>>>><br>> > >>>>>>>> Cheers,<br>> > >>>>>>>> Dom<br>> > >>>>>>>><br>> > >>>>>>>><br>> > >>>>>>>><br>> > >>>>>>>> On 18/05/12 16:42, KWilcox@asascience.com wrote:<br>> > >>>>>>>>> Hello all -<br>> > >>>>>>>>><br>> > >>>>>>>>> Thanks to funding from the NOAA IOOS Program we have been<br>> > able<br>> > >>> to<br>> > >>>>>>>>> do some work on owslib here: https://github.com/kwilcox/owslib<br>> > >>>>>>>>><br>> > >>>>>>>>> Some things that are on the fork:<br>> > >>>>>>>>><br>> > >>>>>>>>> 1.) Cleaned up the tests and made sure they are all passing<br>> > >>>>>>>>> 2.) Using py.test for the test runner<br>> > >>>>>>>>> 3.) Organized the tests and testing resources<br>> > >>>>>>>>> 4.) Support for SOS 1.0<br>> > >>>>>>>>> GetCapabilities/DescribeSensor/GetObservation<br>> > >>>>>>>>><br>> > >>>>>>>>> Some things that are planned in the next few weeks:<br>> > >>>>>>>>><br>> > >>>>>>>>> 5.) Support for SOS 2.0<br>> > >>>>>>>>> GetCapabilities/DescribeSensor/GetObservation<br>> > >>>>>>>>> 6.) Normalize the namespace lookup library wide<br>> > >>>>>>>>> 7.) Abstract all of the GetCapabilitiesReader classes into a<br>> > >>>>>>>>> parent class (WMSCapabilitiesReader, WFSCapabilitiesReader x<br>> > >>>>>>>>> 3, WCSCapabilitiesReader, SosCapabilitiesReader)<br>> > >>>>>>>>><br>> > >>>>>>>>><br>> > >>>>>>>>> We would like to eventually get this merged into trunk for<br>> > >>>>>>>>> everyone to<br>> > >>>>>>>> enjoy, comments or suggestions are welcome, thanks!<br>> > >>>>>>>>><br>> > >>>>>>>>><br>> > >>>>>>>>> --------------------------------------------------------------<br>> > >>>>>>>>> ---<br>> > >>>>>>>>> -----<br>> > >>>>>>>>> --------<br>> > >>>>>>>>> Live Security Virtual Conference Exclusive live event will<br>> > >>>>>>>>> cover all the ways today's security and threat landscape has<br>> > >>>>>>>>> changed and how IT managers can respond.<br>> > >>>>>>>>> Discussions will include endpoint security, mobile security<br>> > >>>>>>>>> and the latest in malware threats.<br>> > >>>>>>>>><br>> > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/<br>> > >>>>>>>>> _______________________________________________<br>> > >>>>>>>>> owslib-devel mailing list<br>> > >>>>>>>>> owslib-devel@lists.sourceforge.net<br>> > >>>>>>>>> https://lists.sourceforge.net/lists/listinfo/owslib-devel<br>> > >>>>>>>><br>> > >>>>>>>> --<br>> > >>>>>>>> Scanned by iCritical.<br>> > >>>>>>> ----------------------------------------------------------------<br>> > >>>>>>> ---<br>> > >>>>>>> -----------<br>> > >>>>>>> Live Security Virtual Conference Exclusive live event will cover<br>> > >>>>>>> all the ways today's security and threat landscape has changed<br>> > >>>>>>> and how IT managers can respond.<br>> > >>>>>>> Discussions will include endpoint security, mobile security and<br>> > >>>>>>> the latest in malware threats.<br>> > >>>>>>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/<br>> > >>>>>>> _______________________________________________<br>> > >>>>>>> owslib-devel mailing list<br>> > >>>>>>> owslib-devel@lists.sourceforge.net<br>> > >>>>>>> https://lists.sourceforge.net/lists/listinfo/owslib-devel<br>> > >>>>>><br>> > >>>>>><br>> > >>>>>><br>> > >>>>>><br>> > >>>>>> -----------------------------------------------------------------<br>> > >>>>>> ---<br>> > >>>>>> ----------<br>> > >>>>>> Live Security Virtual Conference<br>> > >>>>>> Exclusive live event will cover all the ways today's security and<br>> > >>>>>> threat landscape has changed and how IT managers can respond.<br>> > >>>>>> Discussions will include endpoint security, mobile security and<br>> > >>>>>> the latest in malware threats.<br>> > >>>>>> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/<br>> > >>>>>><br>> > >>>>>><br>> > >>>>>><br>> > >>>>>> _______________________________________________<br>> > >>>>>> owslib-devel mailing list<br>> > >>>>>> owslib-devel@lists.sourceforge.net<br>> > >>>>>> https://lists.sourceforge.net/lists/listinfo/owslib-devel<br>> > >>>>><br>> > >>>>> --<br>> > >>>>> Jachym Cepicky<br>> > >>>>> Help Service - Remote Sensing s.r.o.<br>> > >>>>> jachym.cepicky@gmail.com | jachym@hsrs.cz http://les-ejk.cz |<br>> > >>>>> http://bnhelp.cz<br>> > >>>>><br>> > >>><br>> > >>> --<br>> > >>> Jachym Cepicky<br>> > >>> Help Service - Remote Sensing s.r.o.<br>> > >>> jachym.cepicky@gmail.com | jachym@hsrs.cz http://les-ejk.cz |<br>> > >>> http://bnhelp.cz<br>> > >><br>> > >> ---------------------------------------------------------------------<br>> > >> ---------<br>> > >> Live Security Virtual Conference<br>> > >> Exclusive live event will cover all the ways today's security and<br>> > >> threat landscape has changed and how IT managers can respond.<br>> > >> Discussions will include endpoint security, mobile security and the<br>> > >> latest in malware threats.<br>> > >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/<br>> > >> _______________________________________________<br>> > >> owslib-devel mailing list<br>> > >> owslib-devel@lists.sourceforge.net<br>> > >> https://lists.sourceforge.net/lists/listinfo/owslib-devel<br>> > ><br>> > <br>> > --<br>> > Jachym Cepicky<br>> > Help Service - Remote Sensing s.r.o.<br>> > jachym.cepicky@gmail.com | jachym@hsrs.cz http://les-ejk.cz |<br>> > http://bnhelp.cz<br>> <br></div> </div></body>
</html>