Top Banner
The Future of 96Boards Documentation Robert Wolff
30

LAS16-506: The future of 96Boards documentation

Jan 12, 2017

Download

Technology

Linaro
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: LAS16-506: The future of 96Boards documentation

The Future of 96Boards DocumentationRobert Wolff

Page 2: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICES

WORKING TOGETHER

Who am I?

● Robert Wolff

● Engineer - Technical Writer

● Team: 96Boards at Linaro

Twitter: @sdrobertw and @96Boards

IRC: sdrobertw

Email: [email protected]

Coursera - IoT Specialization for DragonBoard 410c

Github - 96Boards and Linaro documentation repositories

OpenHours - www.96Boards.org/OpenHours

Author: Robert Wolff - [email protected] (09/30/16)

Page 3: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Outline - The Future of 96Boards Docs

● Current Documentation

● The Old Ways

● New Approach

● Document “Contribution Cycle”

● Rethinking the Cycle

● The Process

Author: Robert Wolff - [email protected] (09/30/16)

Page 4: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Current DocumentationWhat’s so special about any of it?

Author: Robert Wolff - [email protected] (09/30/16)

Page 5: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICES

WORKING TOGETHER

Current Documentation - Types

● PDF○ User Guides

○ Hardware Manuals

○ “How to” Guides

○ More...

● Wiki○ 96Boards

○ Linaro

○ Board specific

● Github Documentation Repositories○ 96Boards

○ Linaro

○ Other...

Author: Robert Wolff - [email protected] (09/30/16)

Page 6: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Current Documentation - Initial thoughts?

● Scattered

● Repeated

● Out dated

● Inconsistent

● Lack of ownership

● Consolidate

● Remove (if possible)

● Maintain

● Build out / template

● Assign ownership

Author: Robert Wolff - [email protected] (09/30/16)

Page 7: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Current Documentation - Initial thoughts?

Organize

Structure

Set/Use Conventions

Author: Robert Wolff - [email protected] (09/30/16)

Page 8: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

The Old WaysA current approach

Author: Robert Wolff - [email protected] (09/30/16)

Page 9: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

The Old Ways - A good start...

● SoC programmer’s Technical Reference Manual - PDF

● Hardware User Manual - PDF

● Schematics - PDF

● Getting Started Guide - PDF

➢ What happens when users want more?

➢ What happens when something needs to be changed?

Author: Robert Wolff - [email protected] (09/30/16)

Page 10: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

The Old Ways - New doc?

Create a document

Throw it anywhere on the Internet

Don’t tell anyone

Never updateAuthor: Robert Wolff - [email protected] (09/30/16)

Page 11: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

The Old Ways - Change doc?

Make a new doc,

put it anywhere,

without telling anyone...

Author: Robert Wolff - [email protected] (09/30/16)

Page 12: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

New ApproachHow much better can it be?

Author: Robert Wolff - [email protected] (09/30/16)

Page 13: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

New Approach - Goals

● Reduce static documentation

● Increase dynamic documentation

● Allow Vendor contribution and ownership

● Encourage community contribution and ownership

● Reduce points of contact

➢ What happens when users want more?

➢ What happens when something needs to be changed?

Author: Robert Wolff - [email protected] (09/30/16)

Page 14: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Document “Contribution Cycle”The hours add up and cost everyone $$$

Author: Robert Wolff - [email protected] (09/30/16)

Page 15: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Document “Contribution Cycle”

Community

Static Document

Document Owner

Use

Report

Report Raw Document

Fix

New Version

Error

Upload

96Boards

Inform

Fix

Author: Robert Wolff - [email protected] (09/30/16)

Page 16: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Rethinking the CycleResource allocation with minimal points of contact

Author: Robert Wolff - [email protected] (09/30/16)

Page 17: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Rethinking the Cycle

Community

Dynamic Document

New Document

Use

Report

Fix

Error UploadFix New

Document96Boards

Author: Robert Wolff - [email protected] (09/30/16)

Page 18: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Rethinking the Cycle

● Quick and easy document modifications

● Straightforward document creation

● Community driven

● 96Boards maintained

● Website rendered

Author: Robert Wolff - [email protected] (09/30/16)

Page 19: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICES

WORKING TOGETHER

Rethinking the Cycle

96Boards will:

● Buffer

● Share

● Contribute

● Expand

● Maintain

With help from:

● Linaro

● Vendors

● Manufacturers

● Community

● Anyone...

Author: Robert Wolff - [email protected] (09/30/16)

Page 20: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

The ProcessWorkflow, tools, methods, execution

Author: Robert Wolff - [email protected] (09/30/16)

Page 21: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Consistency

Author: Robert Wolff - [email protected] (09/30/16)

Page 22: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICES

WORKING TOGETHER

The Process - Tools

Welcome to 96Boards:

● Landing page with core material

● Core Material and Setup

● Templates and instructions

● Support and Community

Author: Robert Wolff - [email protected] (09/30/16)

Page 23: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICES

WORKING TOGETHER

The Process - Tools

Github:

● Git for command line

● Using Markdown and reStructured

● Downloadable PDFs are welcome

● Hosting images

● Share all 96Boards generic docs

Author: Robert Wolff - [email protected] (09/30/16)

Page 24: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICES

WORKING TOGETHER

In Conclusion

We aim to provide:

● Dynamic

● Streamlined

● Consistent

● Well Maintained

● Robust

Documents

Created and supported by:

● 96Boards

● Linaro

● Vendors

● Manufacturers

● Community

Author: Robert Wolff - [email protected] (09/30/16)

Page 26: LAS16-506: The future of 96Boards documentation

Thank You

#LAS16For further information: www.linaro.org

LAS16 keynotes and videos on: connect.linaro.org

Page 27: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Extra Slides

Page 28: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

Useful Logos

Download Hi Res logos from here* to use on your slides

*http://link.linaro.org/logos

Page 29: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICESWORKING TOGETHER

This Slide is for when Two Columns are Needed● You can use this for two columns of

bullets

● Or you can replace one column

with an image or diagram

● This could be a second column of

bullets

● Or it could be a table, image or

graphic

Page 30: LAS16-506: The future of 96Boards documentation

ENGINEERS AND DEVICES

WORKING TOGETHER

Alternative Content Slide● If you have a more succinct message, use this slide