+1000 for using the GitHub tracker over trac<br><br><div class="gmail_quote">On Thu, Oct 13, 2011 at 10:03 AM, Tim Schaub <span dir="ltr"><<a href="mailto:tschaub@opengeo.org">tschaub@opengeo.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Andreas and I have been evaluating the GitHub issue tracker (as I know<br>
others have as well). While using it, we're still opening Trac<br>
tickets.<br>
<br>
For example, here's an issue related to improving dateline handling<br>
for vector features:<br>
<br>
In Trac <a href="http://trac.osgeo.org/openlayers/ticket/3526" target="_blank">http://trac.osgeo.org/openlayers/ticket/3526</a><br>
<br>
And GitHub <a href="https://github.com/openlayers/openlayers/pull/11" target="_blank">https://github.com/openlayers/openlayers/pull/11</a> (with<br>
history <a href="https://github.com/openlayers/openlayers/pull/11/commits" target="_blank">https://github.com/openlayers/openlayers/pull/11/commits</a> and a<br>
summary diff <a href="https://github.com/openlayers/openlayers/pull/11/commits" target="_blank">https://github.com/openlayers/openlayers/pull/11/commits</a>).<br>
<br>
The benefits of the GitHub tracker are plain to me (but I've been sold<br>
for a couple years). There's not any inline commenting going on here,<br>
but it's a feature we use frequently elsewhere. I'll let the Trac<br>
stalwarts extol its virtues.<br>
<br>
Tim<br>
<br>
On Fri, Oct 7, 2011 at 6:07 AM, Eric Lemoine<br>
<<a href="mailto:eric.lemoine@camptocamp.com">eric.lemoine@camptocamp.com</a>> wrote:<br>
> On Thu, Oct 6, 2011 at 9:18 PM, <<a href="mailto:christopher.schmidt@nokia.com">christopher.schmidt@nokia.com</a>> wrote:<br>
>> The SVN repository being out of date is because there are bugs in<br>
>> git-svn that break everything. Figuring out a fix for this is still<br>
>> soemthing I'm working on; I have a couple other tools that I'm trying<br>
>> to get started with, but it is not being as trivial as it's supposed<br>
>> to be. (ahocevar also offered me some advice as to how to get git to<br>
>> do what I want.)<br>
>><br>
>> In the end, the problem we are trying to solve is not so hard that I can't<br>
>> hack it with my own code if we have to get there; I know that it's<br>
>> annoying, and I do want to fix it, I just haven't had a chance to yet.<br>
>><br>
>> Regarding reporting tickets -- that is something I will let other people<br>
>> comment on. I don't have any specific views.<br>
><br>
><br>
> At this point, and until we have decided otherwise, I think trac<br>
> tickets should be created. Pull requests, referenced in tickets with<br>
> URLs, can replace patches attached to tickets though.<br>
><br>
> --<br>
> Eric Lemoine<br>
><br>
> Camptocamp France SAS<br>
> Savoie Technolac, BP 352<br>
> 73377 Le Bourget du Lac, Cedex<br>
><br>
> Tel : 00 33 4 79 44 44 96<br>
> Mail : <a href="mailto:eric.lemoine@camptocamp.com">eric.lemoine@camptocamp.com</a><br>
> <a href="http://www.camptocamp.com" target="_blank">http://www.camptocamp.com</a><br>
> _______________________________________________<br>
> Dev mailing list<br>
> <a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br>
><br>
<font color="#888888"><br>
<br>
<br>
--<br>
Tim Schaub<br>
OpenGeo <a href="http://opengeo.org/" target="_blank">http://opengeo.org/</a><br>
Expert service straight from the developers.<br>
_______________________________________________<br>
Dev mailing list<br>
<a href="mailto:Dev@lists.osgeo.org">Dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/openlayers-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/openlayers-dev</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Zac Spitzer <br>Solution Architect / Director<br>Ennoble Consultancy Australia<br><a href="http://www.ennoble.com.au">http://www.ennoble.com.au</a><br><a href="http://zacster.blogspot.com">http://zacster.blogspot.com</a><br>
+61 405 847 168<br><br><br><br>