[Bf-committers] i18n maintenance is on hold

Campbell Barton ideasman42 at gmail.com
Thu Mar 28 23:57:21 CET 2013


On Fri, Mar 29, 2013 at 8:43 AM, Thomas Dinges <blender at dingto.org> wrote:
> Who said something about "every commit"? ;)
> I talk about bigger changes, and I talk about continuous i18 change
> commits even though I raised objections in the past about that.
>
> Let's not twist the facts here. :)
>
> Am 28.03.2013 22:37, schrieb Daniel Genrich:
>> As far as I know, the devs don't need the "green light" from the module
>> owner for every commit they do.
>>
>> mont29 also did several commits to fluids and cloth, too without running
>> by me first. That was fine, no big changes.
>> I don't think we should encourage "blocking type" commits (everything
>> needs to get "green light" first). We're not Sun with Open Office who
>> scares devs away, right? :-)
>>
>> I was under the impression, that the "module owner" is about bigger
>> things. No idea, I am wrong? ^^
>> Just my 2 cents.
>>
>> Daniel / Genscher
>>
>>
>> Am 28.03.2013 22:13, schrieb Thomas Dinges:
>>> So all in all, it's all about communication. We have the module owner
>>> list for a reason. Please respect that.
>>>
>>> Best regards,
>>> Thomas
>>>
>>>
>>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>
>
> --
> Thomas Dinges
> Blender Developer, Artist and Musician
>
> www.dingto.org

>From what I can tell Bastien is working on his own with translation
code which is no small task and touches
gettext/blenfont/boost/ui/python/rna so I think we should try be
supportive of providing a good API's rather then asking Bastien to
stop.

Thomas, can you give an alternative you think would be acceptable?

-- 
- Campbell


More information about the Bf-committers mailing list