Long ong-term p pla lans ns for or the the D DIT ITA-OT p - - PowerPoint PPT Presentation

long ong term p pla lans ns for or the the d dit ita ot p
SMART_READER_LITE
LIVE PREVIEW

Long ong-term p pla lans ns for or the the D DIT ITA-OT p - - PowerPoint PPT Presentation

Long ong-term p pla lans ns for or the the D DIT ITA-OT p proje oject How do we ensure the long-term health of the project? Kristen James Eberlein Eberlein Consulting LLC About m out me DITA geek with an open source and


slide-1
SLIDE 1

Long

  • ng-term p

pla lans ns for

  • r the

the D DIT ITA-OT p proje

  • ject

How do we ensure the long-term health

  • f the project?

Kristen James Eberlein Eberlein Consulting LLC

slide-2
SLIDE 2

About m

  • ut me
  • DITA geek with an open source and standards

habit

  • Four four-legged companions
slide-3
SLIDE 3

Agen genda

1.

Who uses the DITA-OT?

2.

Who supports the DITA-OT?

3.

Is this sustainable?

4.

The DITA-OT as vital digital infrastructure

5.

Thoughts about ways to move forward

slide-4
SLIDE 4

Who ho uses ses the the DIT ITA-OT?

  • Companies that produce and deliver DITA-based content
  • Companies that use the DITA-OT in their products:
  • Authoring tools
  • DITA-enabled component content management systems
  • Delivery applications
  • Translation management systems that render content for review
  • DITA-OT plug-ins
  • Consultants and consulting firms
slide-5
SLIDE 5

More

  • re tha

than 630+ com

  • mpanies

es use se DIT ITA

Image created by Keith Schengili- Roberts @IXIASOFT

slide-6
SLIDE 6

Authoring tools

  • Adobe FrameMaker
  • oXygen XML Editor
  • Xmetal Author Enterprise
slide-7
SLIDE 7

CCM CCM syst system ems

  • Astoria CMS
  • Componize
  • DitaExchange Dx4
  • DITAToo DITA CMS
  • DITAworks
  • DocZone DITA CMS
  • easyDITA
  • IXIASOFT DITA CMS
  • RSI Content Solutions Rsuite
  • SDL LiveContent Architect
  • Smart Content (Empolis)
  • Vasont DITA CMS
  • Xdocs CCMS
  • XML Documentation Add-on for

Adobe Experience Manager

  • XPLM Publisher
slide-8
SLIDE 8

Del eliver ery

  • DITAweb
  • FluidTopics
  • Oxygen XML WebHelp
  • WebWorks ePublisher
  • Zoomin’ products
  • SuiteHelp
slide-9
SLIDE 9

Consu sultan ants

  • Eberlein Consulting
  • Tagsmiths
  • Parsons
  • Scriptorium
  • infotexture
  • Contrext
  • Suite Solutions
  • SDL Professional Services
  • IXIASOFT Professional Services
  • Mekon
  • Mark Giffin Consulting
  • And many, many more …
slide-10
SLIDE 10

Wh Who s

  • sup

uppor

  • rted th

the D DITA-OT T in t n the he old da d days?

  • IBM
  • Originally two developers in IBM China, plus

time from Robert Anderson and Don Day

  • Support dwindled …
  • Since 2012 or so, minimal development

resources from IBM (no specific time allocation)

slide-11
SLIDE 11

Who ho su supports s the the DIT ITA-OT n now?

  • Very, very few people
  • Fewer than you think …
slide-12
SLIDE 12

Let’s t’s l look

  • ok a

at t how th the wor

  • rk breaks

do down … n …

slide-13
SLIDE 13

GitHub c commi mmits t s to dita ta-ot

  • t: 2005

2005-presen esent

Na Name Company ny Number of c commits

  • 1. Jarno Elovirta

2,171

  • 2. Robert D. Anderson

IBM 241

  • 3. Roger Fienhold Sheen

45

  • 4. Kristen James Eberlein

32

  • 5. Radu Coravu

Syncro Soft 20

  • 6. Eric Sirois

IBM 13

  • 7. Eliot Kimber

12

  • 8. Eero Helenius

7

  • 9. Shane Taylor

4

  • 10. George Bina

Syncro Soft 4 As of 12 November 2016, 13:00 PM in Munich

slide-14
SLIDE 14

GitHub c commi mmits t s to docs: s: 2 2013-presen esent

Na Name Company ny Number of c commits

  • 1. Roger Fienhold Sheen

702

  • 2. Jarno Elovirta

129

  • 3. Kristen James Eberlein

33

  • 4. Shane Taylor

16

  • 5. Robert Anderson

IBM 5

  • 6. Mark Giffin

2

  • 7. bbg3

2

  • 8. George Bina

Syncro Soft 2

  • 9. Eliot Kimber

1

  • 10. Erlend Leganger

1 As of 12 November 2016, 18:40 PM in Munich

slide-15
SLIDE 15

Issu Issue e tra tracki king

  • Read and understand the issue
  • Create test files to reproduce the issue
  • Check whether a fix has shipped in more recent

version

  • Respond to issue; explain resolution
  • For backlog: Regularly check whether fixes have

shipped

  • Kudos to Eero and Radu Coravu!
slide-16
SLIDE 16

Attendance a e at proje ject c call lls s in 2 2016

  • Representatives from the

following companies

  • IBM
  • IXIASOFT
  • SyncroSoft
  • Vasont
  • Astoria
  • Individuals
  • Jarno Elovirta
  • Kristen James Eberlein
  • Roger Fienhold Sheen,

infotexture

  • Shane Taylor, WebAssign
  • Lief Erikson, Viavi Solutions
  • Bob Johnson, EBSCO
  • Eliot Kimber, Contrext
slide-17
SLIDE 17

Suppor pport fr from co compa panies

  • Syncro Soft (oXygen XML editor)
  • Sponsors Web conferencing for the monthly calls
  • Provides oXygen XML Web Author
  • Organizes DITA-OT Day (2014 - present)
  • IBM
  • Time from Robert Anderson to chair monthly project calls.
  • Eberlein Consulting LLC
  • Sponsors Web conferencing for the monthly documentation

calls

slide-18
SLIDE 18

Unoffic icia ial l contrib tribut utio ions ns

  • People respond to e-mails on dita-users …
slide-19
SLIDE 19

Is Is thi this s su sust stainable? e?

  • It’s precarious …
  • What happens if Jarno is hit by a

double-decker bus?

  • What happens if Robert

becomes a full-time daddy? And steps on a Lego and falls down the stairs

  • What happens if Roger devotes

himself to aikido full-time?

  • What happens if Kris burns out

and starts a new career as a caterer?

slide-20
SLIDE 20

DITA-OT a as vital al digit ital i al infrast structure

slide-21
SLIDE 21

Probl

  • blem

em stat atemen ent

“Our modern society runs on software. But the tools that we use to build software are buckling under increased demand. … Nearly all software today relies on free, public code, written and maintained by communities of developers and other talent. … Just like physical infrastructure, digital infrastructure needs regular upkeep and

  • maintenance. But financial support for digital infrastructure is much harder to come
  • by. …

No individual company or organization is incentivized to address the public good problem alone. In order to support our digital infrastructure, we must find ways to work together.”

Roads and Bridges: The Unseen Labor Behind Our Digital Infrastructure

slide-22
SLIDE 22

Finan ancing f for i infrast astructure p e projec jects

  • Roads, sewer systems, and power
  • Operated by government and utility companies
  • Funded by taxes
  • People are penalized if they do not pay taxes
  • Civic and cultural institutions
  • Operated by the civic and cultural organizations
  • Funded by grants and donations, usually tax-deductible
  • People and organizations give voluntarily
  • Churches and religious institutions
  • Funded by tithing/contributions by member base
slide-23
SLIDE 23

Fina nanci ncing ng f for inst stras astructure (co (cont nt.)

  • All these examples have something in common;

they are entities that can deal with money.

  • The DITA-OT project …
  • Has no bank account
  • No legal structure or associated foundation
  • No way for people to contribute other than in-kind
slide-24
SLIDE 24

If If we e ha had a leg egal enti entity …

  • We’d have a mechanism for accepting

financial contributions :

  • Contributions from companies that rely on the DITA-

OT

  • Foundation support
  • We could consider funding some work items …
slide-25
SLIDE 25

Though

  • ughts a

about

  • ut m

moving g for

  • rward …

slide-26
SLIDE 26

Consider w ways o ys of f ad adding in institu tutional

suppor

  • rt
  • Investigate the foundations and groups that

currently support open source projects

  • Investigate forming a legal entity for the DITA-

OT project

  • Perhaps a legal entity that could support both

DITA and the DITA-OT

slide-27
SLIDE 27

Other ther lon

  • ng-term iss

ssues es

  • Raise awareness of the role the DITA-OT plays as infrastructure
  • Develop metrics about DITA-OT usage and its economic impact
  • Expand the pool of contributors
  • Continue to value non-code contributions (community, documentation,

evangelism)

slide-28
SLIDE 28

Infor

  • rmation
  • n a

about D

  • ut DITA-OT u

usag sage

  • How many companies use DITA-OT?
  • Are they satisfied?
  • What are pain points?
  • How have they extended the toolkit?
slide-29
SLIDE 29

Economic imp impact of DI DITA-OT

  • What is the financial value of the

DITA-OT?

  • How much money do companies

make from the DITA-OT?

  • If the DITA-OT did not exist – or

stopped development – how much would it cost companies?

  • Is there a way to compute this?
slide-30
SLIDE 30

What at d does es the e projec ect n need eed f from vendors a and c consu sult ltin ing firms ms?

  • Mor
  • re participation.
  • n. Much more.
  • Attend contributor meetings
  • Try out the development code and provide feedback.
  • Please don’t wait until after the code is released …
  • If we can do anything to make this easier, let us know.
  • Consider making a donation or sponsoring
  • Fund Slack for the project
  • Sponsor an employee’s time for formal work on the project
  • Organize a DITA-OT day in North America, maybe Canada 
slide-31
SLIDE 31

What at d does es the e projec ect n need eed f from individ idual als? s?

  • If you customize the DITA-OT [tools smiths, consultants]
  • Participate!
  • If you don’t:
  • Ask your vendors and consultants to participate, contribute

fixes, etc.

  • If your vendor or consultant says “This is a bug in the DITA-

OT; here’s how to fix it” – ask if they have reported the issue.

  • If you have technical writing skills, help with the

documentation

  • If you have project management or business analyst skills …
slide-32
SLIDE 32

We e also so need need hel help to

  • Develop some statistics about DITA-OT

usage and its economic impact

  • Investigate ways of adding institutional

support

  • Consider setting up a legal entity
slide-33
SLIDE 33

Resou

  • urces

es

  • Roads and Bridges: The Unseen Labor Behind

Our Digital Infrastructure 14 July 2016.

slide-34
SLIDE 34

So,

  • , who

who su supported ed the the DIT ITA-OT?

  • IBM
  • 2004-~2008: Two developers in IBM China, plus

time from Robert Anderson and Don Day.

  • 2008-~2010: One-one and half developers in China,

plus small (and inefficient) test team.

  • 2012/2013: Developer in China leaves IBM; he is

not replaced. Without an IBM developer, the test team has nothing to do and ceases work.

  • 2013-2016: Robert Anderson organizes and chairs

the monthly project calls.