starting premise is that majority of working groups will require few same pages. soon, if current proposals on imc-process and imc-finance pass, writing summaries will be mandatory for global working groups too.

as we did in the past, letting things to develop on their own and then looking at the patterns that emerge seemed to work. here is what we have so far: TechStatus^?, TechHowto^?, TechSummary^?, Active2DevSummary, Active2DevTodo

which brings us to this naming convention: for working groups (WG)

- Global web - it is known that it's a global WG, so names can be: SomegroupSummary^?, SomegroupHowto^?, SomegroupTasks^?, etc (eg PrintSummary^?,PrintHowto,PrintTasks, etc)

- Indydocs^? web - here we need additional element, the name of the imc: SomeimcSomegroupSummary^?, SomeimcSomegroupHowto^?, etc (eg BelgiumFinanceSummary^?, BelgiumFinanceHowto^?, etc)

- Sysadmin web - it's tech, global and sysadmin, so it has more fine grained, and a different convention then other webs, more tasks/project oriented, and in general more messy, since patterns are less obvious: TechPanic^?, TechStatus^?, Listwork, Stallman, Inglis

- Devel web - tech, global, coding, so it's mainly for Open Publishing systems and other tools that we develop: SomesoftwareHowto^?,SomesoftwareTasks, etc (eg look for Aacctive2Dev pages on wiki)

please concrete your proposals on NamingSchemeConcrete

-- MatZe - 22 Apr 2002
to top