Merge branch 'master' of github.com:nikiroo/gofetch
[gofetch.git] / test / expected / LWN / 0000764321.header.html
CommitLineData
1aaa6ba3
NR
1<!DOCTYPE html>
2<html>
3<head>
4 <meta http-equiv='content-type' content='text/html; charset=utf-8'>
5 <meta name='viewport' content='width=device-width, initial-scale=1.0'>
6 <style type='text/css'>
7 body { margin: 1em 15%; }
8 </style>
9</head>
10<body>
11<div class='story-header'>
c715ea02 12 <h2><a href='0000764321.html'>The Hidden Benefit of Giving Back to Open Source Software (Working Knowledge)</a></h2>
1aaa6ba3
NR
13 <div class='details'>([Briefs] Sep 6, 2018 16:56 UTC (Thu) (corbet))</div>
14 <br/>
15 <div class='content' style='text-align: justify'>
e818d449 16 The Harvard Business School&#x27;s &quot;Working Knowledge&quot; site has [1]an article arguing that it can pay for companies to allow their developers to contribute back to the projects whose software they use. &quot; And that presents an interesting dilemma for firms that rely heavily on open source. Should they allow employees on company time to make updates and edits to the software for community use that could be used by competitors? New research by Assistant Professor Frank Nagle, a member of the Strategy Unit at Harvard Business School, shows that paying employees to contribute to such software boosts the company’s productivity from using the software by as much as 100 percent, when compared with free-riding competitors. &quot;<br/><br/><br/><br/>[1] https://hbswk.hbs.edu/item/the-hidden-benefit-of-giving-back-to-open-source-software
1aaa6ba3
NR
17 </div>
18<hr/>
19</div>
20</body>