Summit2012 proposal-sarah maddox
•
2 likes•734 views
The document discusses the process of publishing a book and how a wiki can help with collaboration. It outlines the typical 9 month phases of content creation and production that involve submitting proposals, writing, editing, artwork, and printing. It then describes how the author used Confluence wiki software along with plugins to collaborate with reviewers, editors, and publishers throughout the process. The wiki allowed for diagrams, export to PDF, and extended capabilities to meet their publishing needs.
![Summit track and target market ,[object Object],[object Object],[object Object],[object Object],Confluence The art of collaboration](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
More Related Content
Viewers also liked
Viewers also liked (10)
Similar to Summit2012 proposal-sarah maddox
Similar to Summit2012 proposal-sarah maddox (20)
More from Sarah Maddox
More from Sarah Maddox (16)
Recently uploaded
Recently uploaded (20)
Summit2012 proposal-sarah maddox
- 1. Publishing a book Need a wiki quick! Atlassian Summit May-June 2012, San Francisco
- 3. Any author or publisher can tell you There’s a book in everyone It’s hard to get it out of you Trouble is...
- 4. It’s a team activity, right from conception Author Artist Reviewers Editor Publisher Indexer
- 5. 9 months’ labour – the content phase 15 May Submit proposal 3 Jun 31 Dec Content deadline Writing 15 Feb Production 3 Dec
- 6. 9 months’ labour – the content phase 15 May Submit proposal 3 Jun 31 Dec 15 Jun 15 Feb Content deadline Writing Admin and technical setup Production 3 Dec
- 7. 9 months’ labour – the content phase 15 May Submit proposal 3 Jun 27 Nov 31 Dec 15 Jun Content deadline Writing Admin and technical setup 15 Feb Production 3 Dec Artwork and promotion
- 8. 9 months’ labour – the content phase 15 May Submit proposal 3 Jun 27 Nov 3 Dec 31 Dec 15 Jun Content deadline Writing Admin and technical setup Technical review 15 Feb Production Artwork and promotion
- 9. 9 months’ labour – the content phase 15 May Submit proposal 3 Jun 27 Nov 3 Dec 31 Dec 15 Jun 22 Dec Content deadline Writing Admin and technical setup Artwork and promotion Technical review Index, footnotes, etc 15 Feb Production
- 10. 9 months’ labour – the production phase 15 May Submit proposal 3 Jun 27 Nov 3 Dec 15 Jun 22 Dec 7 Jan 5 Feb Content deadline Copy edit Final proofs Printing 31 Dec 15 Feb Production
- 13. It’s not over ‘til the wiki sings The conversation continues on the wiki http://wikitechcomm.onconfluence.com
- 15. Bye
Editor's Notes
- Confluence – The art of collaboration. Aim is to attract a new customer segment: Publishers and publishing teams Authors Also a real-life example of: How Confluence is valuable to all sorts of teams – not just software development. One of the wiki's strongest advantages – Confluence as an extensible platform
- There’s a book in everyone. The trouble is, it's hard to get it out of you. It's a lot like having a baby. Having the idea is the fun part…
- … Then the project grows and grows. Getting the book out there is a multi-person project. It’s all about the people and collaboration. You work with a loose team. People join at the appropriate time: Author Publisher Artist Technical reviewers Copy editor Indexer Ward Cunningham reviewed the section about his most recent work. So yes, producing a book is a lot like having a baby. In fact, my book took 9 months of hard labour…
- We need a wiki, quick! In the presentation, I’ll go on to talk about: How the wiki helps the publishing team produce the book, from conception to production. The technical details of the wiki and plugins. The publisher’s use of DocBook in the print-on-demand publishing process. ============== MORE – THE PUBLISHER’s EXPERIENCE ============= I asked the publisher for some words about his experience of producing a book on a wiki. From the publisher: The main advantage of using a wiki is how it improves the review process. Here are a few ways this works: 1) Review comments can be kept in one place, making it easier to keep track of comments and make sure they are all addressed. 2) Each reviewer can see the comments from every other reviewer. This reduces duplicate comments and gives reviewers the opportunity to agree (or disagree) with each other's comments. 3) We also found with Alan's books that we got better participation when we used a wiki for review comments. I'm not exactly sure why, but I suspect it has to do with the public nature of comments; that is, when you see other people adding comments, you're more likely to participate so you don't look like a slacker:). Other advantages include: 1) Easier authoring than many alternatives (e.g., XML, and even Word (at least for folks like me:)). 2) Version control. You can go back to an earlier version easily and compare two versions. 3) You can set up reporting, so editors, publisher, and writer get email whenever a change is made. With your project, of course, we also had a very nice DocBook export with coding for lots of nice goodies, like indexes, footnotes, etc.
- Confluence as a platform In the presentation, I’ll go on to talk about: Scroll Wiki DocBook Exporter, and how we worked with K15t to enhance the plugin so that it could produce footnotes, index, image captions. How this makes Confluence a great platform – you can innovate, and get what you want into the product
- It’s not over ‘til the wiki sings. New in the publishing world: A book does not end at printing. The conversation continues, amongst readers and authors and the whole wide world. What better place than the wiki? http://wikitechcomm.onconfluence.com