we strive to heed upstream's recommendations on how they intend for their software to be consumed.

Version bumps and security fixes should be attended to in a timely manner.

If you do not represent upstream and upstream becomes interested in maintaining the image, steps should be taken to ensure a smooth transition of image maintainership over to upstream.

When we have our git rev-parse examine our Git repository to view our origin/HEAD, what we see is whatever we have stored in this origin/HEAD. That need not match what is in their HEAD at this time. It might match! It might not.

It means that when having a type guard:TypeScript and JavaScript runtime are tied to the same behaviour.

Inside the if statement, TypeScript will assume that amount cannot be anything else than a string, which is true also at the runtime thanks to typeof JavaScript operator.

Keeping bootstrap-sass in sync with upstream changes from Bootstrap used to be an error prone and time consuming manual process. With Bootstrap 3 we have introduced a converter that automates this.

I personally think that starting from google's components makes easier to keeping update to material specs updates.

in order to track the always-improving upstream project, we continuously rebase our patches on top of the upstream master