Hi, > The board member who has been trying to follow the project recommends we > put the issue of US vs Int’l English to a vote.
Where was this recommended? If it didn't happen on the mailing list it didn't happen. > Apparently, the HTTP project did so in the past (and decided on US English). Could you provide links to the discussion and vote around this? It may be helpful to look at that. > Personally, I don’t want to just choose one over the other But seem to be pushing that everything must be en_US? > The proposal is: > > 1) Release package documents will be written in US English As previously discussed I'd prefer we try to be more inclusive and use international English. > Interested community members can post translated copies of READMEs and > RELEASE_NOTES (but not the others like LICENSE and NOTICE) on our wiki. For other non English locales, IMO it would be better if they are included with the release in a separate file. eg README-zn We've not had anyone step forward and volunteer to do this yet so perhaps better to discuss that if and when it arises. > 2) API Names will use US English spellings, especially since the W3C is > already using “color”. Other than for backwards compatibility reasons I don't see why we need to be strict about this. > 3) ASDoc and JavaDoc comments will use US English. Again I don't se the need for being so strict about this. Given that a significant proportion of current contributors (and potential contributors) either speak English as a second language or come from non en_US backgrounds, why try make it harder for them? > The overall principle is that things in 1, 2 and 3 all end up in a release > package. Because the official Apache LICENSE uses US English, it will > appear more consistent to have all of the other things in the package use > US English. I don't think that follows, the LICENSE is written in a legalese style of English, should the readme and release notes be written in the same style just for consistency? :-) I'd assume the answer is no there. Thanks, Justin
