[VOIPSA Best Practices] Expectation setting - can we agree on a document structure before the holidays?

[dan_york at Mitel.com]

Best Practices list,

One final message from me tonight...  I want to just set an expectation of 
what we can realistically accomplish before the end of the year.  I 
realize we have a global membership but I can say that here in North 
America, most companies will be either shut down or running very minimally 
after next Friday and through the end of the year in celebration of the 
Christmas and New Years holidays.  I expect the same is true in most of 
Europe and many other parts of the world.  I know I personally will be 
spending time with family and won't be doing a whole lot online during 
that time.

So we have about a week left in 2006.  In that time what I would like to 
do is see if we can come to closure on how we want to structure the actual 
Best Practices document.  In my mind, this structure is key as it drives 
how we organize ourselves, the information, etc.  If we can agree on a 
structure, we can start off 2007 going into actual development.  (And we 
can revise the wiki, get section leaders signed up, etc.)

If you look at the Development Process page:

  http://wiki.voipsa.org/tiki-index.php?page=Development+Process

under the heading "Document Structure", you will see the current 
proposals.  Note that I have added the suggestion from Eugene Nechamkin 
about segmenting it on interfaces. (Thanks, Eugene, for offering the 
suggestion) 

So far I have only seen interest in #2, Segmenting into Functional Areas, 
and then Eugene's suggestion which I have now labelled #4.  Therefore at 
the current time I am going to suggest we delete #1 (align with Threat 
Taxonomy) and #3 (technology components) unless someone speaks up now.

NOW IS THE TIME TO SPEAK UP if you think either #1 or #3 are better ideas. 
  It's also the time to speak up if you have another suggestion that you 
think would be even better.  (Note that I'm NOT saying we *need* more 
choices... )

If you have issues or concerns with either #2 (functional areas) or #4 
(interfaces), I would definitely like to hear those issues/concerns raised 
to the list. 

What I'd like to do is see if we can come to closure by the middle of next 
week... either through (eloquent and reasoned) discussions here or I can 
always run a quick poll.

Thanks for whatever feedback you all may have on this important aspect of 
the project.

Thanks,
Dan

-- 
Dan York, CISSP
Dir of IP Technology, Office of the CTO
Mitel Corp.     http://www.mitel.com
dan_york at mitel.com +1-613-592-2122
PGP key (F7E3C3B4) available for 
secure communication

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://voipsa.org/pipermail/bestpractices_voipsa.org/attachments/20061214/2370d531/attachment.htm>