Nor have I. As a manager/co-owner I can't think of a reasonable business-friendl...

Deestan · on Sept 10, 2017

> I would love to, of course

If you did, you'd have found a way for it to work.

Making a pretty cool deploy script? Document it and put it out there as OSS.

Making a class/module to sort items semantically? Make it OSS.

Someone made an IDE extension to syntax highlight WebVTT files? Make i OSS.

Made a file lister/selector for JQuery? OSS.

Integrating 3rd party X with 3rd party Y? Opensource your module for it.

Unless all your developers do is hack stuff badly together in a monolithic mess, some of it can be opensourced.

bdcravens · on Sept 11, 2017

It's one thing to write the code, but another thing to publish as open source. There's overhead: coordinating the PR in an existing project, responding to issues, writing a decent README, looking at PRs, etc in your own.

tedmiston · on Sept 10, 2017

I read parent comment as referring to contributing to an existing active open source project vs just making things you've built open source.

rcfox · on Sept 10, 2017

The majority of my contributions have been around projects I use for work. Bug fixes, extending functionality, performance enhancements, etc.

adekok · on Sept 10, 2017

That's the real answer.

If you spent 1/10 of an engineer on an open source product, and 100 other companies do the same, your company gets much more than it puts in. And because it's open source, you know how to fix it, and you can fix it.

I know of multiple billion-dollar companies who can't get the time of day from Cisco, HP, etc. for bug fixes or new features.

The vendors attitude is: Bought 10M of product in the past year? Meh... piss off. We're working on important customers.