upstream

We also have the lack of active upstream checks and any sort of upstream status reports.

The changes in GTK+ have become progressively less dramatic: this means that fixes for themes are now smaller/simpler, not that they don't need active upstream tracking.

After a while, some of them may even build entire businesses based on feeding user surveillance data upstream.

Because LAN-only doesn't save Microsoft as much money by using other people's upstream bandwidth instead of Microsoft's.

So when saying an older PHP version, it is about the upstream version, not the package version.

AMD pays a couple of people to maintain the upstream linux driver for their cards, NVidia doesn't.

Either you accept to keep up with upstream or you'd better stick to the default theme.

Isn't the whole point of Git that you can just go and setup an upstream somewhere else with a one-liner?

The whole point of having a stable Linux distribution is so that you can stop worrying about upstream EOL issues.

You only need to do this if you're going to try to push the packages upstream.

The tool used was our own scanner and it differentiates between package versions and 'upstream' versions.

They do really important work, and there are legal limits on how much revenue the corporation can send upstream to the foundation.

Mostly that reads like "follow these rules, update your processes and factories to these other specifications" - significant barriers themselves, just upstream from the actual trade.

Interesting with the highlight of differences between "forward" and "backward" defined workflows (let data/tasks flow forward on success vs require some of the most downstream tasks or targets, and let the engine figure out upstream targets), as these have profound implications for how easy some workflow constructs are implemented.