Hello Ryan, Thanks for the proposal.
>Native-Lang project: English >Project code: en >Project level: Level II >Project lead: Ryan Singer >Project co-lead: Ian Lynch > >This is a proposal to start an English Native-Lang Project. This NL >project is intended to cover all variations of English. That is, it is >not specific to either US or British English, or any other variant. Okay... I have some questions below. > >The reason to start this project at Level II is that all of the >localisation work is already done for English, allowing the project to >immediately get started with grass-roots marketing. For every other >language, the respective NL project looks after grass roots marketing >efforts (banners, flyers, handing out CDs, etc) and the global >marketing goals (like the SMP) are left to the marketing project. >Since the MP operates in English, the English language doesn't have an >NL project dedicated to this sort of grass roots effort. This creates >an unusual burden on English-speaking MarCons and results in missed >opportunities in English speaking countries. Uhm. Actually, my impression differs, at leat wrt anglophone marcons. I don't mean to discount or ignore the work done, and would be delighted to imagine that an EN NLC would produce the environment for them to be more effective. Out of curiosity, what would the relationship be then between these anglophone marcons and the MP? Right now, the MP has succeeded in representing all of the OOo project. > >An English NL project would also help lower the disparity between >projects. Right now the OOo project is roughly divided into "English" >and "everyone else". An English NL project is a first step towards, >eventually, having all languages on the same level, with English as a >modular part of the whole, like every other language. Put another way, you seem to say in the first breath that English has a privileged spot, and it does. Development ideas are discussed in English, and many marketing ideas are also discussed in English. But those discussions are in English so that all understand. If we all spoke French as a second language, they'd be in French. An EN project, however, would have discussions only in English and focus for marketing on those regions where English is the native language. (But even in this, it could get interesting, as the general popularity of English blurs the distinction between "native" and "official".) In the second breath, it seems as if anglophone work suffers because it lacks the committed focus or is doing too much (not sure which obtains here). I think having an EN project could work. But my concern is simply this: That the existing functional dominance of English would be strengthened by an NLC for English, unless it were clear that: * MP represents the entire project, all languages. * Other global projects, though they have discussions in English, also represent the entire project, eg, Documentation, tech projects, etc. * As work is already being done in English for Documentation, presumably the focus of this EN project would be what, regarding Documentation, at least? Would the EN project organize anglophone documentation writers? * EN (NLC EN) marketing efforts execute MP directives while also allowing the creation of local endeavors, such as FR has. In short, these provisions seek to make clear that NLC EN is not privileged and that though discussions in the global projects are in English they are not ipso facto part of any EN project. Best Louis --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
