public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: github password policy
Date: Wed, 18 Aug 2021 19:12:50 +0200	[thread overview]
Message-ID: <4de3ba75-8619-26fb-f6d1-0281f83bdc22@towo.net> (raw)
In-Reply-To: <bca18bf3-caf9-059c-a992-a80c8eb2c7fc@SystematicSw.ab.ca>



Am 17.08.2021 um 05:00 schrieb Brian Inglis:
> On 2021-08-16 17:59, Doug Henderson via Cygwin-apps wrote:
>> On Mon, 16 Aug 2021 at 07:45, ASSI <Stromeko@nexgo.de> wrote:
>>>
>>> Thomas Wolff writes:
>>>> As I cannot update mintty anymore right now from the git command line,
>> Yes, I use SSH for all repos now.
>>
>>> Do. Not. Use. GitHub.
>>>
>>> The raison raison d'être for GitHub is and always has been to subvert
>>> the fully distributed workflow that Git was designed to provide and
>>> replace it with their centralized lock-in "solution".
>>
>> As well as GitHub for several public repos, I have used BitBucket for
>> several private repositories, as they allowed several, while GitHub
>> only allowed one. They also have a large number of add on features
>> around the Git repositories, aimed at lock-in.
>>
>> Does anyone have online Git servers they use and can recommend? BTW, I
>> have done Google searches, etc. I'm looking for enthusiastic personal
>> endorsements.
>
> Used the same as you, but I recently also joined Gitlab, run as a 
> virtual cooperative corp, as some of my recent adopted upstreams are 
> hosted there, and getting redundant release announcements is never a 
> bad thing. I haven't yet added any projects there.
When I adopted mintty, I looked at several platforms and also liked 
Gitlab more, but at that time Github was the only platform that offered 
seamless migration from Google Code (where mintty was hosted before) 
including the complete issue history, which was an unbeatable advantage.

>
> GNOME projects are now hosted there, and Alibaba, IBM, and SpaceX use 
> it, but as Gitlab servers are on Google Cloud, and subject to US 
> embargos like BitBucket, GitHub, and SourceForge, a European mirror 
> https://framagit.org/ (part of the Framasoft non-profit network) on 
> Debian infrastructure, has been set up to bypass Google and the US, as 
> well as allow access to/from embargoed countries.
>
> https://about.gitlab.com/blog/2018/05/31/welcome-gnome-to-gitlab/
> https://about.gitlab.com/blog/2020/09/08/gnome-follow-up/
> https://framagit.org/explore/projects?name=gnome-&sort=latest_activity_desc 
>
>


  reply	other threads:[~2021-08-18 17:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 12:13 Thomas Wolff
2021-08-16 13:44 ` ASSI
2021-08-16 23:59   ` Doug Henderson
2021-08-17  3:00     ` Brian Inglis
2021-08-18 17:12       ` Thomas Wolff [this message]
2021-08-16 14:44 ` Corinna Vinschen
2021-08-16 14:46 ` Lee
2021-08-16 17:51   ` Thomas Wolff
2021-08-16 17:59     ` Yaakov Selkowitz
2021-08-17  6:39       ` Thomas Wolff
2021-08-16 18:33     ` Jonathan Yong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4de3ba75-8619-26fb-f6d1-0281f83bdc22@towo.net \
    --to=towo@towo.net \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).