We should decide this now, so that Peter J can plan
accordingly. If the NLC meeting is willing to host
the wiki discussion I'd be fine to have it there.

The NLC meeting is currently scheduled to be 60 mins,
we should have the option to extend a bit if we're
running over. Discussion around the wiki may take
some time.

Frank

So? Should we rather be using the NLC meeting as a forum for
the wiki discussion?



Frank

Why we can't discuss these topics during the NLC meeting, which is planned later in the day and is supposed to cover the subject of documentation and community tools? If we set up too many meetings, then

Is there an agenda out for the NLC meeting yet?

each of them is going to have just a few attendants and we will miss the necessary consensus to get forward on issues. In addition, the wiki is interesting also for Marcon, that should be discussing similar subjects at the same time.

The wiki meeting is supposed to cover questions very specific to the
Documentation and NLC part of the wiki (and possibly usage of CMS, but
that would be future discussions). If this is interesting for marcon,
I don't know. My view is focussed on the Docs part of the wiki although
I think that a Docs/NLC approach to wiki usage may be of value
for other groups using the wiki, too.

I am fine with discussing that in the course of the NLC meeting but
it will not only be around NLC issues, but also general technical
and organizational issues. Being quite an extensive topic it will
need some time. If we have that in the NLC meeting, that's fine. But
I wouldn't want to squeeze that into 10 minutes. So could we extend
the NLC meeting if necessary?




--
Frank Peters
Documentation Project Co-Lead

The OOo Documentation Project:
SIGN UP - PARTICIPATE - CONTRIBUTE
IT'S FREE! NO OBLIGATIONS!
http://documentation.openoffice.org
http://wiki.services.openoffice.org/wiki/Documentation


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to