'This week long-time open source advocate Matt Asay warned employers
that the best way to keep their developers happy was to let them
contribute to open source projects:
SlashData recently surveyed over 16,000 developers to see what makes
them tick... what they care about. The data is collected in
SlashData's State of the Developer Nation, though let me give you the
tl;dr: 59% of developers contribute to open source software today. Why
do they contribute? The top two reasons are: To improve coding skills
and because they believe in open source.
Want to keep those developers happy and employed with you? Let them
[Y]our employees want to contribute both code and knowledge — they
want to be part of something. Talking to Bert Hubert, founder of
PowerDNS, a supplier of open source DNS software, services, and
support, he stressed that an open source project must be "a fun place
where people feel that they are learning things, that they're
contributing things, that they're being valued." Perhaps not
surprisingly, these are the same elements developers expect from their
employers. By making open source a valued part of workplace
expectations, employers tick both boxes.
Is it an absolute requirement that you encourage your developers to
contribute to open source projects? No. But many of your best
developers will chafe at keeping their talents locked up behind the
firewall, and other developers simply won't apply if you have a
reputation for being an open source scrooge.
The article was written by Matt Asay, a former COO of Canonical now
working at AWS. (Right before becoming Canonical's COO, Matt answered
questions from Slashdot readers).
The survey he cites also found that out of 17,000 developers they
talked to, just 3% said they were paid to contribute to open source.
The other 97% contributed for free.'
-- source: https://news.slashdot.org/story/20/05/03/1746244
Dept. of Computer Science
University of Waikato, NZ
+64 (7) 858-5174