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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
