[ossig] Re: [myoss] OpenOffice.org Community Marketing Contact

[Bustamam Harun <bustamam98@yahoo.com>]

My posting didn't show up, so I'm resending and CCing to interested party:

----------  Forwarded Message  ----------

Subject: Re: [myoss]OpenOffice.org Community Marketing Contact
Date: Sun, 24 Aug 2003 21:13:41 -0700
From: Bustamam Harun <bustamam98@yahoo.com>
To: myoss@my-opensource.org

Why too much email traffic for such a simple issue?  Let me clarify without 
putting anyone down.

Localization of OpenOffice to Malaysian language has been officially my 
responsibility since about 2 years ago:
http://l10n.openoffice.org/localization_responsibilities.html

Am I looking for publicity in doing this OOo localization project?  Compared
to other OOo project I've contributed, localization is probably the least
contribution I've made.  Most of the work is being done by team members,
which I think is how an Open Source project should work.  Look at other OOo
components that I've contributed like:
Hijri Calendar support:
http://l10n.openoffice.org/source/browse/l10n/i18npool/source/calendar/calendar_hijri.cxx

Regular Expression search and replace:
http://www.openoffice.org/servlets/ReadMsg?msgId=415675&listName=dev

Unicode Collation:
http://l10n.openoffice.org/source/browse/l10n/i18npool/source/collator/collator_unicode.cxx

Plus a few other projects including Linux/Sparc port of OpenOffice.org, which 
they acknowledge on the OpenOffice credit page for my contribution, I even 
received a T-shirt :) (the animated scrolling thingy in the "about" box is 
all gone now mnajem :)):
http://www.openoffice.org/welcome/credits.html#h

In OpenOffice localization project, there's no files need to be commited
into CVS, except for the locale data file (1 xml file).  You could commit
the GSI file if you want to, but so far none of the GSI on CVS is updated to
the latest release just look at the source tree, there are a few old GSI
files:
http://l10n.openoffice.org/source/browse/l10n/translation/
The localized resources (binaries) are generated on the fly while building
 OOo and OOo is not multi-lingual, ie: each locale has to be a separate build
 (that breaks the concept of I18n).

OpenOffice related project does not have to be hosted on CollabNet to be an
official OOo project like I did with my Perl UNO binding project:
http://www.openoffice.org/servlets/ReadMsg?msgId=790783&listName=dev
I personally think sf have superior service and support compared to
 CollabNet.

When I said "unofficial" translation, I was referring to the translated 
messages was "unofficial" since it has not being completely reviewed by the 
team members.

We maintain high quality translation by doing linguistic reviews for
 accuracy. We won't be releasing any complete localized bundled OOo software
 until the review is completed.  The "unofficial" tar-ball is just for people
 who wish to see how the translated OOo looks like so far and for our review
 members. If the software is released it's not because someone need localized
 OOo software by certain date or for certain demos in some expo.  It may 
change depending on the situation.

All that said, I think there should only be 1 localization project for 
Malaysian Languages anyone who wish to contribute may join the Singa Emas 
project.  I value the members contribution and input and if they think I need 
to change my management style I would try to accomodate the request.  The 
same applies if they like to see a new leader, we can do an election.  There 
are a lot more qualified people in the team and I'm just providing them an 
environment where they can contribute to the project productively.

I may also delegate some tasks to a different group if we don't have the 
expertise to handle like the localization group for Kelabit and Iban 
languages.

I don't intend to clog this OSS mailing list with this discussion unless if
 it's pretaining to OSS in general.  Any other issues should be in the form
 of personal email CCing only to interested party.

Salam
Bustamam



------------------------------------------------------------
To unsubscribe: send mail to ossig-request@mncc.com.my
with "unsubscribe ossig" in the body of the message