I've seen some cases where patreon.com is used to fund open source projects. Vue.js is founded there for example [1].

1: https://www.patreon.com/evanyou

Factorio, PlayerUnknown's Battlegrounds, Rocket League

I love their name, it clearly states what they want to achieve.

Spread disease, infest, smell, make my skin crawl?

Congratulations to the team on the relase!

Everything under "The Future" really excites me, especially the geo-partitioning features. That is something that I'm really looking forward to be using!

That might end up being an enterprise feature though.

This is great! Congrats to the team for delivering a great update!

If you have a marketing webpage, you might have a link to signup or login pages. If you can hijack the index page you'll also be able to hijack the links.

Even if you don't have signup or login pages, a MITM attacker can add them. Or they could add a "buy now!" link with a convenient entry form for the user's bank details. The relevant question isn't what your page has that's so important, but rather what an attacker could make it have that would cause trouble.

All development teams or products are not the same. Sometimes microservices can improve the quality, and sometimes the opposite.

It is important to know why you do some things, instead of applying Hype-Driven-Development.

Do what is best for you and your team, instead of what is best for someone else (with a different product, problem, and team).

Is there any technical reason for this? Because as far as I know the keywords still appear in Webmaster Tools.

I'm impressed by the speed of the releases here. 1.7 to 1.6 to 1.7.1 within a single day.

I wonder how many people at MS had to pull an all-nighter to make that happen.

It does help that Erich Gamma & team are in Zurich...

I get the distinct impression that they invested in good tooling, CI and CD, which probably enables all sorts of product engineering greatness. Hopefully it's a trend.

As someone who is effected by this:

Are there any good ways to push/pull from multiple upstreams for whole teams? That also works with your whole CI workflow?

So that you for example can have copies of the repository available on both Bitbucket, GitHub, and GitLab at the same time.

You could set up some "failover" upstreams that are mirrored using git's post-receive hooks. Or, you could define a particular git remote to have multiple URL's.

This post explains in greater detail:

http://stackoverflow.com/questions/6882017/git-hook-post-rec...