On 9/28/15 6:06 PM, Tom Lane wrote:
> Josh Berkus <josh@agliodbs.com> writes:
>> The infra team seems to be good with debbugs, and several committers
>> seem to like it, why not go with it?
>
> It certainly seems like debbugs is the proposal to beat at this point.
>
> In the end though, what matters is somebody doing the dogwork to make
> it happen: connecting some tool up to our workflow and populating it
> with an initial collection of items. Until that happens, we're just
> arguing in a vacuum with no way to see whether a proposal will really
> work.
Note that since they also offer a hosted solution we should use that to
play with instead of trying to install it at this point.
Integrating the issue tracker looks like it's just a call to this API:
http://doc.gitlab.com/ce/api/issues.html#new-issue. I don't normally do
web development myself so I'd rather not figuring out how to setup a
copy of the website to hack on, but if no one else wants to try it I can
take a stab at it.
Presumably mirroring our git repository would work the same as it does
for mirroring to GitHub. My guess is that would be enough to get the
basic git/issue tracker integration working.
Commitfest could be tied in as well. Presumably each commitfest would be
a milestone (http://doc.gitlab.com/ce/api/milestones.html) and each
submission an issue.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
