© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Open-Source Resources

Austen Collins, Nadia Eghbal, Andrew Glover

November 28, 2016

DCS201

Developer Community Summit

Speakers

Nadia Eghbal

GITHUB

Austen Collins

SERVERLESS

Andy Glover

NETFLIX

© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Best Practices for New Open

Source ProjectsNadia Eghbal, GitHub (@nayafia)

What to

expect

from this

session

Introduction to running an open

source project

Best practices for building

healthy communities

Why start an open source project?

Reasons to

open

source

your workCode

transparencyCollaboration Build new

ecosystem

As your project grows, your

community needs more than

just code

Your

users

need...

Roadmap Tutorials & Examples

Documentation Timely response

Your

contributors

need...

Code review Feedback on new ideas

Issue triage Formal recognition

How to make these tasks easier?

Set your project up

for success

All new

projects

need: Contributing

License

Readme

Document

everything

Keep documentation updated!

● Install instructions

● Tutorials and examples

● How to contribute

● Project conversations +

discussions

● Policies + governance

● Keep issues updated

Use the

botsCLAs PR review

and triage

Code

coverage,

releases

Communicate expectations

Be responsive!

It’s ok to say no

Leverage your community

Share work with others

Don’t tolerate bad actors

Thank you!

Nadia Eghbal, GitHub (@nayafia)

© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Austen Collins

@austencollins – serverless.com

Hearing Your PeopleGuiding the Serverless Framework

with Feedback and Data

What to Expect from this Session

Learn how to optimize feedback

collection for open-source projects with

little resources.

Learn pitfalls

to avoid.

The Morning After

Going Viral

The Morning After Going Viral

The Serverless

Framework

(formerly JAWS)

hit 1,000 Github

stars in ~2 days.

Immediately

swamped with

feedback and

feature requests

on all channels.

That data is

valuable, but

inaccessible. How

do we fix this?

Pitfalls

Pitfalls

Broken Process

Poor process

misleads and is

susceptible to

bias.

Bad Feedback

It’s everywhere. Even

from smart people.

Demotes Intuition

This will cause a

cultural shift that wants

to overrule instincts

and experience.Look out.

Don’t let this happen.

Scrappy Solutions

Scrappy Solutions

Boring Surveys

Data must be accessible, or it’s worthless.

Everybody’s doing this. Be transparent. Opt-out-able.

Character is action.

Google Surveys. Easy, accessible, powerful.

Open-Source Tracking

Single Dashboard

Scrappy Solutions

Lambda, DynamoDB, Quicksight, Google Surveys.Future

Segment, Redshift, Chartio, Google Surveys.Current Set-Up

Tips

Tips

When something is great, users say

so. When something is bad, many

users won’t say anything.

Be data-informed,

not data-driven.

Thank you!

@austencollins – serverless.com

© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Netflix & OSS

Andy Glover, Netflix

Recruiting

Validation

Innovation

netflix.github.io

spinnaker.io

Thank you!

aglover@netflix.com

@aglover

© 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

Questions?

Thank you!

Remember to complete

your evaluations!

Related Developer Community Pre-day Sessions

DCS202: AWS Training Opportunities [2:20PM-3:20PM]

DCS203: Building and Growing an AWS User Group [3:40PM-4:40PM]

DCS204: Developer Lightning Talks & Happy Hour [5:00PM-6:00PM]