Thread: github purchased by micro$oft
There is already a project on gitlab if we want to leave github.
I'm not suggesting we do, but if things go south with the new owner we may want to consider it
Dave Cramer
Well, it's too early to know the new direction of Github, and I don't really think that Microsoft will mess up Github (at least not in the short-mid term).
But anyway I like the idea of leave github for gitlab based the following reasons:
* Github is not open source, GitLab is.
* GitLab uses and promotes PostgreSQL, a perfect match to a PostgreSQL project.
* Big projects like GNOME choose GitLab.
* A more integrated CI and CD.
The only issue I see is that all the travis jobs must be "ported" to gitlab-ci.yml (which might be easy or difficult since pgjdbc uses some tweaks in jobs).
On Mon, Jun 4, 2018 at 12:09 PM Dave Cramer <davecramer@gmail.com> wrote:
There is already a project on gitlab if we want to leave github.I'm not suggesting we do, but if things go south with the new owner we may want to consider itDave Cramer
I don't have much fear that microsoft will break github in the sort-mid term and I don't have a strong opinion about moving. Just wanted to point out that gitlab now offers their Ultimate and Gold packages for free to open source projects https://about.gitlab.com/2018/06/05/gitlab-ultimate-and-gold-free-for-education-and-open-source/ best regards Alexander Kjäll Den mån 4 juni 2018 kl 23:48 skrev Jorge Solórzano <jorsol@gmail.com>: > > Well, it's too early to know the new direction of Github, and I don't really think that Microsoft will mess up Github (atleast not in the short-mid term). > > But anyway I like the idea of leave github for gitlab based the following reasons: > * Github is not open source, GitLab is. > * GitLab uses and promotes PostgreSQL, a perfect match to a PostgreSQL project. > * Big projects like GNOME choose GitLab. > * A more integrated CI and CD. > > The only issue I see is that all the travis jobs must be "ported" to gitlab-ci.yml (which might be easy or difficult sincepgjdbc uses some tweaks in jobs). > > On Mon, Jun 4, 2018 at 12:09 PM Dave Cramer <davecramer@gmail.com> wrote: >> >> There is already a project on gitlab if we want to leave github. >> >> I'm not suggesting we do, but if things go south with the new owner we may want to consider it >> >> >> Dave Cramer
+1 to not proactively changing anything. I really doubt there will be any negative issues so barring a compelling feature of a new platform seems like it'd be a bunch of work for no net gain.
What we should do though is have an alternate official git repo mirroring the primary pgjdbc repo. Everyone's local copy is essentially a backup as well but this would cover having a central agreed upon master to use as the base if we ever lost the primary on GitHub.
Looks like there's already an empty pgjdbc.git on the git.postgresql.org server (says the owner is Dave too!) so that seems the logical destination for this. Any chance we can set it up to mirror master from the GitHub repo? We never rewrite history on master so it could be purely additive mirror that rejects historical rewrites (i.e. can't be corrupted externally).