Re: No Issue Tracker - Say it Ain't So!
От | David Fetter |
---|---|
Тема | Re: No Issue Tracker - Say it Ain't So! |
Дата | |
Msg-id | 20150929141646.GF3322@fetter.org обсуждение исходный текст |
Ответ на | Re: No Issue Tracker - Say it Ain't So! (Steve Crawford <scrawford@pinpointresearch.com>) |
Ответы |
Re: No Issue Tracker - Say it Ain't So!
|
Список | pgsql-hackers |
On Tue, Sep 29, 2015 at 07:01:16AM -0700, Steve Crawford wrote: > On Mon, Sep 28, 2015 at 4:41 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote: > > > 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. > > > > > One of the issues identified with Github is that it is closed and > commercial which goes against the expressed desires of the PostgreSQL > community. As such, it's important to note that Gitlab seems to be in the > "freemium" model with a "community" and an "enterprise" version so for > comparison purposes we should only look at the features in the open-source > community version: > https://about.gitlab.com/features/#compare Pardon me for getting off in the weeds here, but the PostgreSQL community is just fine with proprietary closed-source software. There are probably more billion-dollar proprietary closed-source forks of PostgreSQL than of any other open source software, certainly if you normalize to the number of contributors. We fully intend to continue spawning those proprietary closed-source forks. What we're not fine with is depending on a proprietary system, no matter what type of license, as infrastructure. We've been burned that way before, and we have no intention of getting burned again that way again. Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
В списке pgsql-hackers по дате отправления: