>> November has been a busy month so far, with the highlight being the >> OOoCon2008 in Beijing. The "Day Zero" NLC meeting was very interesting. >> We talked in depth about the needs of the NLC group with respect to >> Documentation, the Wiki and NLC project goals. The meetings of that >> meeting will be posted soon... when I find the minutes, I will post them >> here so that none misses out on them. > > I would like to help with the organization of the NLC pages, and may be > begin by the FR ones, but I don't know how to do so or where to begin. > So if you have any hints for me, I would be happy and will write a short > how-to for the NLC list also.
I have been thinking about how to do this from the technical side. One of the things we discussed was the idea of using the ISO language codes to identify the language groups and to give each NLC community their "own" area to work in. This means we will need to shuffle a few things and move some pages. I know that we can move pages using the Wiki Bot, so that will take the load off everyone :-) I can manage the Wiki Bot once we have a clear outline of what is required. What I would like to do first is outline the proposed changes on a Wiki page that has yet to be created. I know we discussed it once a while back, and again at the NLC meeting, but I would like to set it all out clearly regarding what is needed/expected etc., and set up some kind of plan or timetable (since thsi will take a bit of co-ordination to make it all transition smoothly). This will give Elizabeth a chance to catch up and get a feel for where we are going as well. I would also like to investigate using Wiki namespaces - this is the more "correct" way of handling multiple language content in the Wiki. We may or may not be able to use Namespaces since the Wiki has evolved for so long without this feature implemented... C. -- Clayton Cornell [EMAIL PROTECTED] StarOffice - Sun Microsystems, Inc. - Hamburg, Germany --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
