It’s not science but you need to know

a few things

All the boring stuff you will forget after the slides have passed

• Stefan Daugaard Poulsen

• @cyberzeddk

• AP in Computer Science

• Developer/Architect at Atea Denmark

• Currently working on Atea Tele

• Been using OSS in different manners since 2001

• BSD

• Linux

• SQL

• .NET libraries

• Applications

• Document database

Open Source

What does the boss think?

• “We just don’t use open source”

• “Open source means free of charge software”

• “We have to use the same license model”

• “None of the big companies are doing it”

• “It is made by hippie sons,

that sit in their basement with their big beards”

The cultural cliff

• Lacking knowledge of what OSS is

• It is cheap just to say NO!

• No open source ambassador

• A dish served cold

• No team support

• A lone wolf doesn’t eat as often as the pack

• No legal department

• Is this really needed?

• Core functionalities are set as first migrators

• Small steps are a better start

• Thinks that OSS is not as secure as proprietary systems

• Are they, aren’t they?

• Tell him what OSS is

• Don’t do it as a lecture

• Talk about it over lunch

• Take the role as ambassador, and stick to it!

• Make sure that the team is ready

• Tell your boss about a few open source licenses

• Use the 3-layer model

• Tell him about the support options on some projects

• Start of with something non-critical to your business

• Eg. Add a logging library where there were no logging

Sometimes it does, but don’t always assume so

• Why is it assumed that open source means free?

• Open source means that the source is available

• Free means free to copy and reuse

• Does it have to be free of charge?

• Would you give everything you do away for free?

• Return of Investment

• Typical license models

• Dual-license

• Commercial + Open Source

• Eg. RavenDB

• Functional encapsulation

• SaaS

• Support, training and consulting

• Freemium

The endless jungle of OSS

• Simplification of the layers

• Give us credit for what we did for you

• APL, BSD, MIT

• If you fix something let us have the fix

• MPL, LGPL, CDDL

• Give us ALL THE THINGS!

• GPL

• Make sure you pick the right one from the get go

• Choose a loose license to have less worries in the beginning

• Many modern OSS libraries tend to go for

• Give us credit

• Give us fixes

• http://www.tldrlegal.com/

Have you tried searching with a few keywords?

• I do

• Private projects

• We do

• Atea

• He/She/It does

• DMI

• Cisco

• Google

• Microsoft

• BMW

• Mastercard

• Some do it on purpose

• Some can’t even avoid using it

• Be that political decided or not

• More and more use it

• 2550 responders

• Developers (52%), Architects (22%), Management level

• Organizations represented

• Apple

• Adobe

• Oracle

• Cisco

• SAP

• IBM

• Bank of America

• eBay

• Usage

• 34% consume only

• 66% give back in some form

• 9% even though the company policies prohibit it

• Policy

• 51% doesn’t have an OS policy

• 51% of those with a policy hates it

• Control

• 20% locked down to approved components

Sometimes it is…

• Krzysztof Koźmic

• Well-known speaker

• Good reputation in the community

• Embraced by his employer, Readify

• ~40 Contributers

• Quality markers

• Extensibility

• Ease of use

• Really helpful

• …but he does have the beard

• Demis Bellot

• Embraced by his employer, StackExchange

• ~100 Contributers

• Gaining in use

• Quality markers

• Mono support

• Speed

• Doesn’t have the beard :)

• Microsoft Open Technologies, Inc.

• The OSS branch of Microsoft

• Apache Hadoop Connector

• TypeScript Cross-Platform support

• CouchDB as a service

• Entity Framework

• ASP.NET MVC4

• WebAPI

• Node.js (Azure + Windows)

• Isn’t this corporate enough?

• NancyFX

• AutoFac

• RavenDB

• MongoDB

• Lucene (and Lucene.NET)

• Firefox

• Chromium

• Apache

• ALAC (Apple Lossless Audio Codec)

• Even hardware is OS

• Arduino

• Raspberry PI

Slow and steady

• Prototypes

• Helps you get started without boilerplate code

• Small internal projects

• Review a set of modules

• Build a set of verified components

• Why?• Visibility

• Standardization

• Heuristics

• Improved build time for package restore

• Package managers• NuGet

• OpenWrap

• Gems

• Etc.

• Corporate approved packages• Internal package feed

• Local copies

• But keep up to date!!!

• Lock it down

• Financial, Telco, Manufacturing, Government

• Watch out it doesn’t become a negative thing

• Give guidelines and see how it goes

• Keep an eye on it

• License pit trap if not cared about

• Allow creativity to grow freely

• Who has the responsibility?

• Committee

• App Dev Management

• Legal

• Etc.

• Approve a set of licenses

• Fast to see if a component can be used

• Be open to exceptions

• Decide what direction you want to go

• Credit us

• Give us fixes

• Give us all

• NuGet

• LMGTFY

• Advice

• What are other people using?

It’s not only about getting streetcred

• Quick service

• Might be more secure due to more eyes on the projects

• Attracts better workers

• In general people that use OSS are more aware of the tech development

• Faster innovation

• jQuery

• Twitter Bootstrap

• More responsive

• Flexible, prepare for BYOD

• Prepare for the GitHub generation

• Independence

• Twitter: @cyberzeddk

• Blog: http://cyberzed.dk

• Email: cyberzed@sleddog.dk

• GitHub: http://github.com/cyberzed/

Feel free to contact me with any questions