Merge branch, melt brain

Merge Branch: Imagining new version control systems

for writers and editors

David Yee @tangentialism Blaine Cook @blaine

http://shoutkey.com/feverish (https://etherpad.mozilla.org/9bLEN5FXl6)

Who are we all?

We can do this!

• Hilariously quick overview of Version Control Systems • 15-minute sprint: Properties • Share • 15-minute sprint: Newsrooms • Share

What is Version Control?

Why do we need it?

Where did it come from?

Why is it broken?

Granularity

Resilience

Collaboration

Authority

Visibility of Change

Chairman Kaga

Granularity

Resilience

Collaboration

Authority

Visibility of Change

What is an atomic change in your version control system? How do you create a change? Roll it back? What is the story your want your document to tell you about how it came to exist?

How much history do you need to store? What kind of history? What changes do you need to keep? Which to dispose of? How will you store it all?

How does your version control system manage collaboration between users? Can users work simultaneously? Can you work in secret? How is conflict resolved?

How do you manage authority? Who can make changes, and how are those changes credited? To the reporter? The editor? 3rd-party sources? Whose changes trump?

Can you use this system to surface the life of a story to readers? How? Who can see your history, and what parts? How is that change visualized—to readers and inside the newsroom?

Mix it up!

Long form / serial —Secret

Long form / serial —Sourced / Public

Breaking news

Wikipedia

High velocity, short form

Merge Branch: Imagining new version control systems

for writers and editors

David Yee @tangentialism Blaine Cook @blaine

http://shoutkey.com/feverish (https://etherpad.mozilla.org/9bLEN5FXl6)