2011/8/21 Rob Weir <[email protected]>: > Moving to its own thread. > > On Sun, Aug 21, 2011 at 1:09 PM, RGB ES <[email protected]> wrote: >>
[...] > There are language-specific lists for other Apache projects. We can > do that as well. Maybe not 160 different language lists. But we can > create a handful of them, as needed. We do that already, for > example, with the support forums. So, ooo-users-es, would be fine. > > The thing we need to think about is how we coordinate in project work. > Obviously if there was an ooo-dev-es list and an ooo-dev-pt-br list > and an ooo-dev-de list, as well as the existing ooo-dev list, then > committers would have difficulty reviewing code, etc. So for some > project areas we'll need to agree on a single language, and that will > probably be English. I assume this means a single ooo-dev list, a > single ooo-private list, and a single ooo-security list. - only one ooo-dev list and this one in english > > Where do we need language-specific lists, beyond the support forum? > In previous discussions I've heard the locale-specific translation > lists would be needed. > > I also heard mentioned "local marketing lists', but I'm not sure how > such activities map to the way Apache projects are run. Events, > publicity, press, etc., are coordinated at the Apache level. So I'm > not sure how much we can devolve such activities to sub-project lists. to start "local groups" we need for each required local group (i. e. with german you cover Germany, Austria and parts of Switzerland, but you need for portuguese you nedd a pt-pt and a pt-br) 1. one list for coordination 2. one list for user-support you can call any ot them whatever you like, but I would strongly recommend to keep "internal business" separate from the users. cheers M.
