| Re: [geogig-dev] geogig project issue tracker |
Hi Scott,long time no see.I'd also prefer github issues, yet as Andrew stated looks like we got to wait a bit for that to be an option.If that's really going to happen in a rather short time (i.e. locationtech enabling github issues and porting bugzilla issues to github's), I'd chose that path, since the JIRA option is not supported either yet. That'd be a choice thinking on the project rather than personal preference, cause I too find bugzilla cumbersome.In any case, I've always advocated for not linking commit messages to github issues by including #<issue number>, but instead write comprehensive commit messages, exactly because of this kind of situations. Over the years we faced the same problems a couple times in geotools/geoserver and, though practical in principle, that proved to be a rather short sighted approach. I find it's much better to have concise commit messages that are complementary to the actual changes, so that you can look at the patch and the reasoning behind it at a single shot with a simple git log./rantGabriel--On Wed, Sep 2, 2015 at 6:38 PM, Scott <sctevl@xxxxxxxxx> wrote:As a consumer, and lead on a team that has contributed in the past, I place my vote squarely on GitHub Issues. It works well and it keeps the issues closely aligned with the code. It's also easy to browse and follow comments. Minimalism is good in this case. From a consumer point of view, it's a bit off-putting to have to go to a different site where I need another login to be able to browse through issues. I've never found Bugzilla good for browsing.I like to be able to see the state of a project, what's aligned against milestones, and who's been working the latest issues. The project seems much healthier and much more open when this is the case. Since the migration to LocationTech, we haven't been able to get a sense at all of where the GeoGig project stands or how close (or not) it is to a release. When we had issues in GitHub, it was much more transparent. The fact that the code is in GitHub is great. It's also easy enough to hook into their API for Issues upload and download. The GitHub team helped us with the first migration we did to go from Jira to GitHub Issues.My 2 cents: Please, please, go with GitHub Issues.Cheers,ScottOn Wed, Sep 2, 2015 at 4:18 PM, Jody Garnett <jgarnett@xxxxxxxxxxxxxxxx> wrote:_______________________________________________I think for now I will update the github website to point at that.
I suspect, given the crew here, that they would be interested in any other alternative :)On Wed, Sep 2, 2015 at 1:17 PM, Andrew Ross <andrew.ross@xxxxxxxxxxx> wrote:Jody,
Confirmed there is one bugzilla instance with different products for each project.
For example, you can raise a bug for GeoGig here:
https://locationtech.org/bugs/enter_bug.cgi?product=GeoGig
Hope this helps!
Andrew
On 02/09/15 15:04, Jody Garnett wrote:
One question about the bugzilla option, currently I linked to the general locationtech bugzilla selecting the geogig component - is that correct? Or do projects get independent bugzillas ... I am just wondering if there is some decent link we can provide for the geogig project page for visitors to see the currently open bugs.
On Wed, Sep 2, 2015 at 11:55 AM, Andrew Ross <andrew.ross@xxxxxxxxxxx> wrote:
Hi Everyone,
If the GeoGig project is willing, we could trial using JIRA for it. This is not officially endorsed or supported yet, and we may have to move off of it if things go badly. Personally, I am optimistic this will one day be officially supported.
Please be aware that there's a really nice integration between git, gerrit, and bugzilla at the Eclipse Foundation & its working groups like LocationTech. The same account works for all systems, and that's pretty nice to have.
Currently github issues are not yet supported for projects @ Eclipse and its working groups. That said, our IT team is working on a prototype that can sync issues from github automatically so that may be possible one day soon.
So to summarize the options:
- Bugzilla - too easy... nothing special to do
- JIRA - trial it with me... accepting you may be asked to move off of it
- Github issues - not there yet to offer a trial
Let me know what you want to do?
A
On 02/09/15 14:31, Jody Garnett wrote:
Taking this out from other email thread.
We do have an issue tracker available for use (that is in use):
Since that was set up there are two new options:
a) Set up a Jira (work with Andrew Ross on this one)
Say at atlassian.net or similar.
b) Make use of GitHub issue tracker
https://github.com/locationtech/geogig (we would need to turn it on)
When we decide on what to use we should login and update the project page links.
A big shout out to andrew ross for making this happen (it hinged on making sure that the eclipse foundation can grab a copy of the issue tracker in case the service we are using goes down).
While that may sound silly, it is a brutal reality (CodeHaus just shut down and GeoTools was using it for many years, and SourceForge was having weeks of downtime this year).--
Jody Garnett
Technical Lead | Boundless
jgarnett@xxxxxxxxxxxxxxxx
877-673-6436
@jodygarnett
--
--
Jody Garnett
Technical Lead | Boundless
jgarnett@xxxxxxxxxxxxxxxx
877-673-6436
@jodygarnett
geogig-dev mailing list
geogig-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geogig-dev
_______________________________________________
geogig-dev mailing list
geogig-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geogig-devGabriel Roldán
Software Developer | Boundless
groldan@xxxxxxxxxxxxxxxx
@boundlessgeo
_______________________________________________
geogig-dev mailing list
geogig-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geogig-dev