Administrator
|
Dear Asciidoctor Community,
It's time to review the Asciidoctor Project's infrastructure and integrations and discuss new ideas, changes, and solutions to current problems in order to keep the project lean, mean, and focused like a hungry hawk. To jump start this discussion, we're going to have a meeting in the #asciidoctor IRC channel. (If you want to see the discussion that spawned the need for a meeting, checkout this snippet from the #asciidoctor IRC log.) Don't worry, this meeting will have a ruthlessly-honed, hardcore agenda that will be posted prior to the meeting time. I know your time is extremely valuable, and meetings are typically the last place we want to be. First, we need to choose a time when the majority of the community who would like to help with the project's infrastructure and integrations, can meet. I've set up a scheduling poll on Doodle where you can check off the times you're available. Since the majority of the community is in Europe, I set the poll up in the Brussels time zone. The poll will close at 11:59 MST on Monday, and then I'll announce the meeting time here. In the next 24 hours, I'll also post the meeting agenda. Please, don't hesitate to post ideas, concerns, questions, etc. to this thread. If possible and appropriate, I'll wrestle them into the agenda. Cheers, Sarah |
Administrator
|
Hello Asciidoctor Community!
The meeting will be held on January 16, 2014. Start time: 7:15 PM CET (18:15 UTC) End time: 8:30 PM CET This time range allows the most people to attend at least part of the meeting. Location: #asciidoctor IRC channel Agenda: I'll post it as soon as Dan and I are done arm wrestling over the fate of item #7 (score: Sarah: 2, Dan: 1.5, Pint glass: 1, Sneeze: 1). Cheers, Sarah |
Administrator
|
Hey everyone!
I've prepared notes and an agenda (the open questions) for the meeting. I've saved it as a gist and copied the content into this message. We aren't looking to solve every problem. The main focus of the meeting, as I say in the notes, is to make sure we are asking the right questions and to get on the same page about where we are headed.
Feel free to suggestion revisions or other items. This won't be the only meeting we'll ever have, so if we don't get to everything, don't panic :) Notes and Agenda The focus of this meeting will be to gather requirements for a frontend tool whose purpose is to manage and build a documentation project based on software and design assets primarily from the Asciidoctor ecosystem. Ultimately, these requirements should address these two outstanding questions:
We want to set out on a course to mindfully create a specialized build tool (or tools) for the Asciidoctor ecosystem that allows teams to productively and efficiently write, collaborate on and publish their documentation. In other words, we need start the process of gathering and shaping the requirements (probably on the wiki). Down below are some open questions. We don’t need to answer them all in one day. We do, however, want to make sure we are asking the right questions. Preconditions
Open Questions
List of Assets
User needs
Talk to you soon! -Dan
-- Dan Allen | http://google.com/profiles/dan.j.allen |
Free forum by Nabble | Edit this page |