| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, David Fetter <david(at)fetter(dot)org>, YUriy Zhuravlev <u(dot)zhuravlev(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: No Issue Tracker - Say it Ain't So! |
| Date: | 2015-09-28 22:40:47 |
| Message-ID: | 20150928224047.GA295765@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Now, running gitlab on community-owned hardware would potentially be an
> option, if we find gitlab attractive from a functionality standpoint.
> The question I'd have about that is whether it has a real development
> community, or is open-source in name only. If github did go belly up,
> would we find ourselves maintaining the gitlab code all by ourselves?
> That might not be the end of the world, but it wouldn't be a good use
> of community time either.
>
> Fundamentally, we're playing the long game here. We do not want to make
> a choice of tools that we're going to regret ten years from now.
We already made a similar choice some years ago when we started
depending on the then-recently open sourced SourceForge code for
pgFoundry. That didn't turn out all that well in the long run.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Pedela | 2015-09-28 22:43:31 | Re: No Issue Tracker - Say it Ain't So! |
| Previous Message | Tom Lane | 2015-09-28 22:34:24 | Re: No Issue Tracker - Say it Ain't So! |