curious: why use own hosting rather than github?

[Amir Yalon]

Hi, adding a couple more cents here.

On Fri, 22 May 2020, at 19:11, yanchenko.igor at gmail.com wrote:
> Just wanted to add my 2 cents into discussion.  The beauty of open
> source that anyone who has enough resources can create a fork and
> maintain it, and send patches to upstream, eventually the repository
> which has more contributors will become upstream itself. Those who
> want to prove that github will help project can create a fork there,
> and synchronize changes with upstream. If you succeed and you would
> have more contributors than original project, the fork will become new
> upstream,  everyone will benefit from that, If not than it will prove
> that github doesn't provide any benefits.
> 
> Cheers.

I just saw this comment on LWN[1], and I thought it might be relevant to this
old discussion, so I will quote it here in full:
> I began using 'neomutt' because it had the sidebar patch merged; I think it is
> now also available in vanilla Mutt. Their "What have you achieved, so far?" FAQ
> says: "Lots of old Mutt patches have been brought up-to-date, tidied and
> documented."
> 
> And points to this page: https://neomutt.org/feature.html, which says:
> 
> [quote]
> NeoMutt has brought together lots of Mutt patches, many of which were useful,
> but had been abandoned.
> 
> Before each patch is marked stable:
> 
> - The code is brought up-to-date with Mutt-1.8.0
> - The code is tidied up, comments added, checks done
> - Documentation is written
> - A sample muttrc is created
> - The feature is tested
> [/quote]

This “friendly fork” approach is similar to yanchenko.igor’s suggestion quoted
above, which is why I replied to it. Its only base requirement is for someone to
step up, create that fork (on Github, if that is their wish), start curating
patches there, tidy them up, and collaborate on it here on the mailing list.

I also heard a similar story about how developments in Deno create ripple
effects in the Javascript ecosystem, which end up pushing the same improvements
into Nodejs as well. (Deno is a “friendly competitior” rather than a fork of
Nodejs.)

[1]: https://lwn.net/Articles/837498/