I'm for #2 as it fits more naturally in the github scheme. Github is a great gateway to attracting developers and imho there is no point in adopting conventions that steer us away from its workflow.<div><br></div><div>
Umberto<br><div><br><div class="gmail_quote">On Thu, May 10, 2012 at 2:34 PM, Alan Boudreault <span dir="ltr"><<a href="mailto:aboudreault@mapgears.com" target="_blank">aboudreault@mapgears.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi devs,<br>
<br>
An discussion raised up this morning on IRC. I was checking some issues and noticed that the github project mapserver/tinyows hadn't the issue tracker enabled, though mapserver/mapcache had one.<br>
<br>
We would need to clarify this for us and users and be consistent. Where should I create a ticket for tinyows, mapcache and even doc? There are two options:<br>
<br>
1: All issues are created in the github project mapserver/mapserver and committed in their appropriate github repo. This implies to set the LABEL to the appropriate component of the issue. This is similar to the way we worked with SVN (and selecting the component). This regroups everything at the same place, which is a good think. However, if we create an issue related to tinyows and commit a patch in the repo, it is not as straightforward to reference that commit or ticket. To get the automatic referencing in the ticket:<br>
<br>
- we need to commit with: git commit -m "bla bla bla mapserver/mapserver#1234"<br>
<br>
- in a ticket, we can refenrence a commit with: "this is a comment1 mapserver/tinyowns@1234567"<br>
<br>
There is proabably other referencing issues... ie... attaching a pull request with a ticket.<br>
<br>
2: All issues are created in their own github project and committed normally. This is (IMO) more easy and straightforward for users and devs as well.<br>
<br>
- commits are as we did in the pass, a simple #1234 , and @123456 to reference a changeset.<br>
<br>
- It is more easy to see ALL issues related to the specific project, since even if the label is missing, it has been created as the right place.<br>
<br>
- Also, the concept of *label* in github seems different than a trac component. I don't think we can specify a *owner* for a label. Correct me if I am wrong Thomas. At least, creating issues in MapCache/TinyOWS/Docs would clearly set the component to the project owner.<br>
<br>
As Thomas mentionned, both solutions have their strengths and weaknesses.<br>
<br>
What do you think?<span class="HOEnZb"><font color="#888888"><br>
<br>
Alan<br>
<br>
-- <br>
Alan Boudreault<br>
<a href="http://www.mapgears.com/" target="_blank">http://www.mapgears.com/</a><br>
______________________________<u></u>_________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/mapserver-dev</a><br>
</font></span></blockquote></div><br></div></div>