3 ms·
We haven't established any official open-source policy, per se. Our software (mostly ruby and python with some C firmware and Objective-C for iOS) does make co
by what-no-tests 11y ago
We haven't established any official open-source policy, per se.
Our software (mostly ruby and python with some C firmware and Objective-C for iOS) does make considerable use of many open-source libraries.
While working, I often find bugs in these upstream dependencies and will:
* Find the project on github
* Search existing issues for the problem I've encountered.
* If found, see if there's an existing patch (and use it).
* If no existing issue is found, I'll open one, then try
my hand at supplying a pull request that addresses said
issue.
My PRs aren't always accepted.
* I generally fork -> PR under my personal github account,
since I'm not acting at an official level for my company.
* I don't mention my company in the PR.