Hi All,

Of late I have not posted to the Ankur lists but have watched the
progress of the project from a distance.

One thing that has been the driving force of Ankur is that volunteers
who are involved in other L10n or like projects come forward to propose
their projects as part of Ankur - unwarranted assimilation does not
occur since it never has been a tradition at Ankur.

On the registration of bn-IN as Mozilla MLP for bn-IN, some unwarranted
comments have been passed and confusion created:

https://bugzilla.mozilla.org/show_bug.cgi?id=284578
https://bugzilla.mozilla.org/show_bug.cgi?id=267132

There are certain points that need to be addressed while discussing the
stand taken by Omi (on behalf of his projects Ankur and Ekushey)

[1] Omi registered bn-BD and not *bn* which is being championed by him
long before bn-IN request was put forward by me

[2] Sumit Ranjan Das put in a bn-IN request on 3rd March 2005 which is
much later than when I put in the request (the Mozilla MLP Status Page
will provide the exact details)

[3] The unequivocal declaration that bn-BD and bn-IN are similar and
thus bn-BD should be the default bn MLP is something that has been
stated without discussion at Ankur (or other suitable forums)

[4] There is precedence wherein en-GB and en-US are *different locales
and different projects* so where is the need to stridently go towards
bn-BD equals bn ?

[5] There is one comment that I do like to object to:

<quote>

Runa, I agree with you, but have a little question. What about all the
RedHat, KDE, Gnome translation you have done for us and we for you (I
mean together). You both work for RedHat and someone is paying you for
your translation. But we ware freelance contributors and our thoughts
and words should be free always not to hurt each other.

<quote>

So why did Omi not add all the SuSE, Mandrake, Gentoo translation to the
 list ? Just because both Runa and myself are employed by Red Hat
(incidentally, Runa's secondary responsibility includes interaction with
the community while her primary is working with the Red Hat Engineering
team, mine is more of a Technology Management for our bread-n-butter
products) there has been a recent trend of *you Red Hat, us volunteers*.

I would like an explanation of the line *you have done for us and we for
you* - it is deeply offending and reminds me of the comments which
Progga had made publicly (and then apologised privately).

For what it is worth Fedora Core has 2 different locales bn and bn_IN
with different maintainers and translators (even) - why can this model
be not adopted.

OO.o has not yet migrated towards a bn-IN and bn-BD model, but the Indic
NLP is a step in that direction.

Taking potshots at Red Hat (or any other company for that reason), by
volunteers is easy. What is difficult is for Company Employees to manage
the fine balancing act - and sometimes lumping all issues on Red Hat is
just a neat excuse to do stuff that on other days one would not like to do.

bn-IN Mozilla MLP was never intended to be an Ankur Project, just like
OO.o was initially never intended to be (politically convenient reasons
mandated that Ankur was shown to be working on an office suite).
Declaring that bn-IN is one without even talking to the person who
requested it is really crass.

Sometime back, it was discussed at Ankur that speaking on behalf of
Ankur at public fora would require notifying the Leads - I sincerely
hope that this time also the leads are aware of these statements.

Regards
Sankarshan



-- 

You see things; and you say 'Why?';
But I dream things that never were;
and I say 'Why not?' - George Bernard Shaw


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bengalinux-core mailing list
Bengalinux-core@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bengalinux-core

Reply via email to