20:03:41 <jsmith> #startmeeting Flock Docs Talk
20:03:41 <zodbot> Meeting started Wed Aug 12 20:03:41 2015 UTC.  The chair is jsmith. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:03:41 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
20:04:08 <jsmith> #topic Introduction by Brian Exelbierd and Pete Travis
20:04:26 <jsmith> Will talk about new workflows and tools and new contributor experience
20:04:34 <jsmith> #topic New Contributor Experience
20:05:16 <jsmith> What should I do?  How do I get started?  (Blank list -- no engagement there from the beginning)
20:05:29 <jsmith> Some people stick around... and then ask "What should I do, really?"
20:05:48 <jsmith> Start by writing about what you'd like to write about.
20:06:32 <jsmith> But that doesn't keep people enthused -- it's overwhelming.
20:06:41 <jsmith> They don't want to pick the wrong thing, or something within the right scope, etc.
20:09:02 <jsmith> Where does my writing go?
20:09:09 <jsmith> Wherever it fits... or not.
20:09:17 <jsmith> Established guides have a well-defined scope.
20:09:28 <jsmith> Started a new Guide (with a capital G) is a big deal.
20:09:32 <jsmith> Publishing is delayed.
20:10:35 <jsmith> Who can help me?  We can!
20:10:41 <jsmith> We've got a great team on standby
20:10:49 <jsmith> Broadly responsive mailing list
20:10:53 <jsmith> Active and friendly IRC channel
20:11:04 <jsmith> Workshops available twice a week during "office hours" on IRC
20:12:36 <jsmith> What do I need?
20:12:46 <jsmith> Tools... publican, docbook, editors, xmllint, git
20:12:59 <jsmith> DocBook is not easy to become familiar with, harder to be proficient in
20:13:06 <jsmith> Publican renders well, but can be confusing
20:13:28 <jsmith> Syntax highlighting?  Tag completion? Validation? Be prepared to spend time on setup with your editor
20:13:37 <jsmith> xmllint error report isn't exactly intuitive
20:13:44 <jsmith> Legacy website, broken deps....
20:13:56 <jsmith> Git allows collaboration, peer review, change management, and more.
20:16:57 <jsmith> Ideal solution...
20:17:07 <jsmith> Documents go through a predictable, staged life cycle
20:17:14 <jsmith> We want to support multiple markup formats
20:17:23 <jsmith> Peer review focuses on content quality
20:17:32 <jsmith> Publishing should (and can) happen automagically
20:17:45 <jsmith> SIGs and other teams can "own" content and get support
20:17:58 <jsmith> Provides a home for internally facing content
20:24:08 <jsmith> #info Document Life Cycle
20:24:37 <jsmith> Idea -> Draft -> Review -> Revision -> Translation -> Publication
20:25:31 <jsmith> #topic The New Model
20:25:39 <jsmith> How do I contribute?
20:25:44 <jsmith> The drive-by submission
20:26:04 <jsmith> Modular -- pick up what you can -- low commitment threshold
20:26:15 <jsmith> The other is the "You're the owner of this content" model
20:26:57 <jsmith> The Protégé -- In-depth, comprehensive writing
20:28:11 <jsmith> #topic Summary
20:28:18 <jsmith> Contributor experience needs to be improved
20:28:25 <jsmith> Tooing is insufficient
20:28:38 <jsmith> Drive-by/low commitment contributions are critical to Fedora Docs success
20:30:50 <jsmith> #info Help us make the tools to support the model on Friday at 5pm
20:30:58 <jsmith> We'll be working on:
20:31:12 <jsmith> * git structure (pagure - may mostly be confirming functionality/config)
20:31:25 <jsmith> * process for triggered publish/testing (this has been started with buildbot)
20:31:43 <jsmith> * sub tasks to create builders based on the specific markup (DocBook first)
20:31:56 <jsmith> * Visual design and meta site builder (needs help)
20:32:30 <jsmith> #topic Questions
20:37:39 <jsmith> Question about the style guide, and are we open to changes?
20:37:51 <jsmith> Short answer is "of course"
20:46:33 <jsmith> #endmeeting