[Asterisk-doc] Minutes of the first "conferece call"

[Steven Critchfield]

On Sun, 2004-05-16 at 22:02, Leif Madsen wrote:
> Comments inline
> 
> > -----Original Message-----
> > From: asterisk-doc-admin@lists.digium.com [mailto:asterisk-doc-
> > admin@lists.digium.com] On Behalf Of Jared Smith
> > Sent: Sunday, May 16, 2004 10:30 PM
> > To: Asterisk-Doc@lists.digium.com
> > Subject: [Asterisk-doc] Minutes of the first "conferece call"

> > Here are the things we discussed:
> > 
> > Project goals:  We discussed the goals of our project, and agreed that
> > our first priority is getting some good "dead tree" documentation for
> > Asterisk.  A secondary goal should be to try to get the book published
> > if possible.  Along those same lines, we agreed that the book should be
> > published under an "open" license.
> 
> I agree.  I think we need to start thinking about doing something like
> Digium does and have people sign a waiver or something to release the
> documentation to the group.  If we are ever going to have this published, we
> obviously need to have some sort or legalities figured out before we get too
> much further.

If it helps, I was under the impression that we where using an open
license for this before I submitted any content.

> > Focus:  We discussed whether to focus on finishing the layout before we
> > start writing chapters, or to just get the chapters written and then
> > finish worrying about the layout.  At this point, we've got a fairly
> > good layout, and we really need to start writing some documentation.
> > The decision was made to start writing docs, and to review the layout at
> > a later time, when we could view it in the context of having at least a
> > few chapters completely fleshed out.
> 
> Should we at least have a look over the book and see if there are sections
> we don't want to keep?  I'm wondering if some of the sections we have setup
> to have written are maybe a little too advanced, or slightly off the topic
> of Asterisk use?  Mostly the programming section... how indepth are we going
> to get?

Whether a chapter is too advanced depends fully on if we place a
limitation on how advance we want to go or if we wish to limit ourselves
to a certain page count. If we an't worried about page count, I would
suggest we cover some of the advance sections as well so we can appeal
to a wider audience and possibly make it easier to get published later
on. 

> > Communication:  We discussed having regular meetings to keep up interest
> > and discuss the state of the project.  We're hoping to make meetings
> > such as this a regular event.  Should we get together every week?  Every
> > two weeks?
> 
> I suggest we have one at least once a week just to keep people thinking
> about it, and fresh things in our minds.  I agree that even if it's just a
> short meeting, anything is better than nothing.  What day and time seems
> good, as I'd like to be able to get people in all time zones able to
> participate... any suggestions? (especially by people from "the old world")

I'm not interested in giving up specific times for this. I will pledge
however to dedicate more time to filling in chapters where needed.
Between my work, my emerging art career, and other family work, I don't
have time to dedicate on a specific time schedule. So far everything,
work included, have totally flexible time so I can get what I need done.
-- 
Steven Critchfield <critch@basesys.com>