> Some companies have a "20% time (or X hours) on open source" policy, which is great for the sort of issues mentioned above. We have this as an unwritten poli

> Some companies have a "20% time (or X hours) on open source" policy, which is great for the sort of issues mentioned above. We have this as an unwritten policy at the moment (... that I have been trying to get formalised for a while & need to follow up!). > It is a good idea to reword your employee contracts to mention the company policy on open source and give employees copyright over their contributions to open source projects. This is an excellent idea - thanks. > If you want more separation between your company software and open source software, an Open Source Program Office or just an internal "open source team" is a good idea, although it is always a good idea for lots of folks to have open source experience, so rotating other employees through the team for periods/percentages of time might be good too. We are not quite big enough (yet) for this, but something like this is already on our radar. We have a pretty major dependency in our stack that is starting to look a bit abandoned & have been idly discussing the possibility of hiring someone to maintain it. Appreciate the feedback!