Slide 1

Slide 1 text

Open Source for Closed Source Companies Amanda Folson Developer Advocate @ GitLab @AmbassadorAwsum

Slide 2

Slide 2 text

Who Am I? ● Developer Advocate @ GitLab ● Tinkerer ● Owe my career to OSS

Slide 3

Slide 3 text

What is Open Source? ● Releasing source code under a permissive license for greater good ○ Allows adaptation and re-release ● Facilitates global maintenance and collaboration ○ Usually for free! ○ Offers more diverse opinions than any company can sustain internally

Slide 4

Slide 4 text

What Open Source Isn’t ● Giving it all away for nothing ○ Giving it away in exchange for out of house development ○ Giving it away in hopes someone else finds it useful ● Giving away your business

Slide 5

Slide 5 text

“WE CAN’T DO THAT!!!”

Slide 6

Slide 6 text

“There’s no value to OSS…”

Slide 7

Slide 7 text

“We have to hire someone to maintain it.”

Slide 8

Slide 8 text

“What about my bottom line?” ● Truly great ideas will be built on ● Leechers are probably not as successful as you ● There’s more to a product than the code

Slide 9

Slide 9 text

“Someone will steal my idea!” ● Your idea is probably not unique ○ Are you reinventing the wheel? ● People don’t care about your idea as much as you think ○ If they did, they’d build it themselves ○ Value is subjective

Slide 10

Slide 10 text

How Open Source Helps

Slide 11

Slide 11 text

Try Before You Buy ● Everyone loves this ○ They don’t all want to talk to sales reps just to get critical info ● If people know what they’re getting, they’ll tell you how it will/won’t work for them ○ You win either way ■ Product improvements ■ Revenue

Slide 12

Slide 12 text

One Size Doesn’t Fit All

Slide 13

Slide 13 text

Silos

Slide 14

Slide 14 text

Sooner or later... ● …someone will make an open source alternative to your product. ● It may as well be you from the start. ○ Keep that marketshare

Slide 15

Slide 15 text

I’m not convinced.

Slide 16

Slide 16 text

Internal Transparency ● Internal documentation ● Open-invitation meetings ● Open training ● Office hours

Slide 17

Slide 17 text

Open Information

Slide 18

Slide 18 text

Cross-Team Functionality ● Anyone can contribute to anything ○ Obviously not saying anyone can be CEO for a day ● Teams own specific projects ○ Establish contribution guidelines ○ Keep bug queue organized ○ Handle feature requests

Slide 19

Slide 19 text

Learn From Failure ● Everyone makes mistakes ● Someone’s failure is some else’s lesson ● Blameless post-mortems

Slide 20

Slide 20 text

What Else Can We Open Up? ● Documentation ● Libraries/tools ● SDKs ● Frameworks ● Modules

Slide 21

Slide 21 text

Thank You! Amanda Folson - Developer Advocate at GitLab [email protected]