NAKATA Maho's OOo blog

In former blog entires, I asked Andre and Sophie for the secrets
of their fastest 解放（する） QA. Fujimaki Haruyuki-san transltated
into Japanese. His translations were very nice, IMHO.
Andre's e-mail
Sophie's e-mail

To my surprise, Fujimaki-san is very new about QA 過程 but
translations was perfect! He seems to understand better than I now :)

Okay, not so many languages are QA'ed and 解放（する）d compared
to 名簿（に載せる）／表（にあげる）d on solenv/inc/postset.mk :). Hope my interviews help
other native language teams. I should ask all the leads or QA
責任／義務s for each languages...本人自身で I'm 利益／興味d
in the ch-TW, ch-CN, pt-BR and cs (Pavel!) team.

Anyway,

QA 跡をつける
http://qatrack.services.openoffice.org/見解（をとる）.php?status=DISTRIBUTED&type=All&lg=All
helps because the native lang teams that have 解放（する）d 一括s
must be very active. I should ask them first.

But I'd like take some days off. Even Japanese want to take
some vacations.

Here what I thought about problems of QA of 2.2.1 ja 見解／翻訳／版,
as a QA/解放（する） 経営者／支配人.

* Very few 核心 testers.
Even though I realized matuaki-san is 極端に QA oriented person,
and I send him a 調書をとる／予約する about QA. He is very smart and it seems
now he understands more than me. 明らかに he is a good 候補者
for QA 経営者／支配人. But - I 恐れる whether he exhausts or not. We need more QA oriented person.
Andre and Sophie also について言及するd
that `核心' members with high 動機づけ are important.
IMHO `helping QA' does not 改善する the 質 of OOo. But person
with high 動機づけ like `I'll find bugs in OOo. That's why I'm here' really helps.

* 需要・要求するing for knowledge and 過程s in OOo.
QA 経営者／支配人 must know a lot of knowledge about QA 過程,
開発 過程 etc. However 予定 to language 障壁 etc,
all the QA testers do not know much about it. Then I'm just
命令（する）ing to them. It is not a good 状況／情勢.

* Lang pack QA
GNU/Linux 見解／翻訳／版 and Windows 見解／翻訳／版 of lang pack have been QA'ed. This is a good news.

* 合意 took very long time...
The idea of IRC 会合 is very nice IMHO, but 現実に I'm not an experienced as a 議長，司会を務める. bluedwarf pointed out my problems. I really thank his sincere but very 厳しい :) advices.

* Not solid/（疑いを）晴らす 過程 for new comers
That's why we created a wiki.

* No Solaris i386/Sparc, MacOSX Intel testers.

Maybe Solaris is not so popular, MacOSX is not suitable for casual 使用者. and there are input method problems
(I wrote a 文書 about it but IMHO it is very very difficult if s/he is not a geek).
and font problems in MacOSX (we must 任命する／導入する TrueType Japanese fonts and we cannot use 極端に high 質 Hiragino fonts), so MacOSX OOo X11 is not so popular.

* MacOSX Panther
Active QA testers often use old 壇・綱領・公約. But I 辞職するd.

* 安全 直す／買収する，八百長をするs
If 2.2 is 解放（する）d then we 推定する／予想する 2.2.1 同様に because it may 含む／封じ込める 安全 直す／買収する，八百長をするs. Once some 一括s are 解放（する）d, we should
never stop. But how?

* TCM costs. People becomes quickly loves TestTool.
* TCM l10n 実験（する） skipped
* l10n translation review is not 組織するd ...Saito-san did a 広大な／多数の／重要な 職業.
http://wiki.services.openoffice.org/wiki/2.3_Japanese_Translation_and_Checking

Next, Sophie Gautier. She is also very 肉親，親類d to answer
my questions, and also - permitted to publish.
I thank them very much!!

支配する: QA of OOO
From: Maho NAKATA
To: sgautier
Date: Tue, 17 Jul 2007 15:56:53 +0900 (JST)
X-Mailer: Mew 見解／翻訳／版 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)

Hi Sophie,

I think francophone 事業／計画（する） is one of the very active
NL in the world, esp. I'm intersted in your fastest QA.
How do you do that? How many QA testers you can find?
What are the problems of your community? Japanese must learn
a lot from you ;)

Thanks
-- Nakata Maho (maho@FreeBSD.org)
-------------------------------------------------------


支配する: Re: QA of OOO
From: sophie
To: Maho NAKATA
Date: Mon, 23 Jul 2007 11:54:11 +0200
使用者-スパイ／執行官: Thunderbird 1.5.0.12 (X11/20070509)

Hi Maho,

Maho NAKATA wrote:
> From: sophie
> 支配する: Re: QA of OOO
> Date: Thu, 19 Jul 2007 15:12:53 +0200
>
> Hi Sophie, thanks for 肉親，親類d and fastest reply!
>
>> Thank you :) In fact I think I spend a lot of time on it. During those
>> periods of QA, I'm checking all the 問題／発行するs filled and the 発言／述べるs made
>> by the FR testers. I 実験（する） again all what they 報告（する）／憶測.
>
> Oh! That's very 需要・要求するing!

Yes,
>
>> How many QA testers you can find?
>>
>> In the best periods, I can have around 30 persons, but usually it's
>> about 15.
>
> So many. We are 5-6 testers.
>
>> There is still several problems :
>> - new testers each time : it's very time 消費するing for the lead of the
>> group and I'm afraid that in some time, the TCM will have to manage
>> thousand of accounts.
> yes.
>
>> - most of the contributers were 動機づけるd by the testtool 実験（する）s. Now
>> that Sun has take this 役割 (which I think it was good at first), lot of
>> them have gone away. Even if they used the testtool, they make some
>> 手動式の 実験（する）s when the testtool fails and were able to 報告（する）／憶測 some 問題／発行するs.
>>
> Why they gone away? Does it mean they only use TestTool?

They prefer to use testtool, 手動式の 実験（する）s on TCM are boring ;)
>
>> - like for all the 事業／計画（する）s I think, finding 動機づけるd people is hard,
>> and when there is 4 or 7 RC to 実験（する）, they get bored and don't want to
>> come 支援する the next time.
>
> 権利.
>
>> For example, I would like to have more people to 実験（する） the developer
>> 解放（する）s. But as this is the same team as the testers of the RC, they
>
> 絶対.
>
>> get tired of the 実験（する）s and go away. To bring some 動機づけ, I've
>> translated all the new functionalities in my blog, but it doesn't seems
>> to work a lot.
>
>> So for the moment I'm still trying to find ways to 動機づける people with
>> 手動式の 実験（する） and TCM. May be send them a t-shirt or a goodies, something
>> like that but I'm not sure it's good.
> :)
>
> Thanks we can 株 many parts of the QA problem...

I think so, don't hesitate if you have その上の questions or 株ing.

肉親，親類d regards
Sophie

-------------------------------------------------------------
支配する: Re: QA of OOO
From: Maho NAKATA
To: sgautier
Date: Fri, 20 Jul 2007 11:36:16 +0900 (JST)
X-Mailer: Mew 見解／翻訳／版 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI)

From: sophie
支配する: Re: QA of OOO
Date: Thu, 19 Jul 2007 15:12:53 +0200

Hi Sophie, thanks for 肉親，親類d and fastest reply!

> Thank you :) In fact I think I spend a lot of time on it. During those
> periods of QA, I'm checking all the 問題／発行するs filled and the 発言／述べるs made
> by the FR testers. I 実験（する） again all what they 報告（する）／憶測.

Oh! That's very 需要・要求するing!

> How many QA testers you can find?
>
> In the best periods, I can have around 30 persons, but usually it's
> about 15.

So many. We are 5-6 testers.

> There is still several problems :
> - new testers each time : it's very time 消費するing for the lead of the
> group and I'm afraid that in some time, the TCM will have to manage
> thousand of accounts.
yes.

> - most of the contributers were 動機づけるd by the testtool 実験（する）s. Now
> that Sun has take this 役割 (which I think it was good at first), lot of
> them have gone away. Even if they used the testtool, they make some
> 手動式の 実験（する）s when the testtool fails and were able to 報告（する）／憶測 some 問題／発行するs.
>
Why they gone away? Does it mean they only use TestTool?

> - like for all the 事業／計画（する）s I think, finding 動機づけるd people is hard,
> and when there is 4 or 7 RC to 実験（する）, they get bored and don't want to
> come 支援する the next time.

権利.

> For example, I would like to have more people to 実験（する） the developer
> 解放（する）s. But as this is the same team as the testers of the RC, they

絶対.

> get tired of the 実験（する）s and go away. To bring some 動機づけ, I've
> translated all the new functionalities in my blog, but it doesn't seems
> to work a lot.

> So for the moment I'm still trying to find ways to 動機づける people with
> 手動式の 実験（する） and TCM. May be send them a t-shirt or a goodies, something
> like that but I'm not sure it's good.
:)

Thanks we can 株 many parts of the QA problem...

thanks,
-- Nakata Maho (maho@FreeBSD.org)
------------------------------------------------------------------
支配する: Re: QA of OOO
From: sophie
To: Maho NAKATA
Date: Mon, 23 Jul 2007 11:54:11 +0200
使用者-スパイ／執行官: Thunderbird 1.5.0.12 (X11/20070509)

Hi Maho,

Maho NAKATA wrote:
> From: sophie
> 支配する: Re: QA of OOO
> Date: Thu, 19 Jul 2007 15:12:53 +0200
>
> Hi Sophie, thanks for 肉親，親類d and fastest reply!
>
>> Thank you :) In fact I think I spend a lot of time on it. During those
>> periods of QA, I'm checking all the 問題／発行するs filled and the 発言／述べるs made
>> by the FR testers. I 実験（する） again all what they 報告（する）／憶測.
>
> Oh! That's very 需要・要求するing!

Yes,
>
>> How many QA testers you can find?
>>
>> In the best periods, I can have around 30 persons, but usually it's
>> about 15.
>
> So many. We are 5-6 testers.
>
>> There is still several problems :
>> - new testers each time : it's very time 消費するing for the lead of the
>> group and I'm afraid that in some time, the TCM will have to manage
>> thousand of accounts.
> yes.
>
>> - most of the contributers were 動機づけるd by the testtool 実験（する）s. Now
>> that Sun has take this 役割 (which I think it was good at first), lot of
>> them have gone away. Even if they used the testtool, they make some
>> 手動式の 実験（する）s when the testtool fails and were able to 報告（する）／憶測 some 問題／発行するs.
>>
> Why they gone away? Does it mean they only use TestTool?

They prefer to use testtool, 手動式の 実験（する）s on TCM are boring ;)
>
>> - like for all the 事業／計画（する）s I think, finding 動機づけるd people is hard,
>> and when there is 4 or 7 RC to 実験（する）, they get bored and don't want to
>> come 支援する the next time.
>
> 権利.
>
>> For example, I would like to have more people to 実験（する） the developer
>> 解放（する）s. But as this is the same team as the testers of the RC, they
>
> 絶対.
>
>> get tired of the 実験（する）s and go away. To bring some 動機づけ, I've
>> translated all the new functionalities in my blog, but it doesn't seems
>> to work a lot.
>
>> So for the moment I'm still trying to find ways to 動機づける people with
>> 手動式の 実験（する） and TCM. May be send them a t-shirt or a goodies, something
>> like that but I'm not sure it's good.
> :)
>
> Thanks we can 株 many parts of the QA problem...

I think so, don't hesitate if you have その上の questions or 株ing.

肉親，親類d regards
Sophie

Andre is very 肉親，親類d so that he 許すs me to publish our
私的な e-mails to public. Ah - but my first question e-mail
becomes public and Andre and Sophie will notice I send almost
the same e-mail to them. Please 許す me for my laziness.
Also it has already been 今後d to [ja-discuss] 名簿（に載せる）／表（にあげる）.
Andre(1)
Andre(2)
Sophie
But I repeat it here:
---------------------------------------------------------------
From: Maho NAKATA
支配する: QA of OOO
Date: Tue, 17 Jul 2007 16:02:08 +0900 (JST)

Hi Andre Schnabel,

I think Germanophone 事業／計画（する） is one of the very active
NL in the world, esp. I'm intersted in your fastest QA.
How do you do that? How many QA testers you can find?
What are the problems of your community? Japanese must learn
a lot from you ;)

Thanks
---------------------------------------------------------------
Andre replied

支配する: Re: QA of OOO
From: Andr?円Schnabel
To: Maho NAKATA
Date: 結婚する, 18 Jul 2007 17:24:30 +0200
使用者-スパイ／執行官: Thunderbird 2.0.0.4 (X11/20070604)

Hi Maho,

Maho NAKATA schrieb:
> Hi Andre Schnabel,
>
> I think Germanophone 事業／計画（する） is one of the very active
> NL in the world, esp. I'm intersted in your fastest QA.
>
I'd be 利益／興味d in that too ;-)

> How do you do that?
Hmmm .. not 平易な to 述べる. It is a 過程, not a 仕事. Our QA relies
on two types of contributors.
1st ... the experienced and long-称する，呼ぶ／期間／用語 team members.
2nd ..the "new" members

the 2nd group is that group, that will likely to work with TCM or do
simple 自動化するd 実験（する）s (means runs the 実験（する）s but will not 分析する the
results) To find such people, we are used to "advertize" the 関連した
QA-仕事s (e.g. we send an "inivitation" mail to our German 名簿（に載せる）／表（にあげる）s when
localization 実験（する）s or 解放（する） 実験（する）s start. For those 仕事s, a wiki-page
is 用意が出来ている with （警察などへの）密告，告訴（状） about the 道具s, who to ask for help, where
to 報告（する）／憶測 problems, where to get the 訂正する builds ... and a 名簿（に載せる）／表（にあげる） of
persons who is doing waht 肉親，親類d of 実験（する）s.
By doing this, we get about 1 to 4 new testers per 解放（する）.Some of them
will leave the team for the next 解放（する） - so the 結果 is not really
high .. but it is at least better than nothing.

The more importand group of testers is indeed the 1st group - experience
long 称する，呼ぶ／期間／用語 team-members. We are happy, to have "a lot" of such members
(compared to other native lang 事業／計画（する）s). But only a handfull is
参加するing inthe "公式の／役人" 解放（する） QA. This is おもに me and
Mechtilde, 調整するing the 過程. We have one tester per 壇・綱領・公約 (me
for 勝利，勝つ, Mechtilde for Linux / deb, Jacqueline for Linux / RPM, Marko
for Solaris x86 .. and changing members for Mac).
But speaking of the 公式の／役人 過程 .. 非，不，無 of those persons is able to
do a 完全にする QA (eg, we are not able to do *all* TCM-実験（する）s before a
解放（する） and run all 自動化するd scripts on every 壇・綱領・公約). For most of
the 解放（する）s I tried to make sure, that at least a 最小限 of thest is
run (完全にする 自動化するd update 実験（する）s on at least one 壇・綱領・公約,
TCM-解放（する） Sanity シナリオ on each 壇・綱領・公約 .. but not for every RC.)

一方／合間 I even tell some people "don't stick to の近くに with TCM 実験（する）
事例／患者s". Experience show that it is not likely, that someone who is doing
TCM-実験（する）s the third time will find any bugs. It is better to have
experienced people work at their favorite 使用／適用 area.
Unfortunately this is nothing I could 令状 負かす／撃墜する as a golden 支配する ...
because this depends on the people you are working with. E.g. I know,
that Mechtilde would 位置／汚点／見つけ出す bugs in Base very 早期に - Jacqueline will
check Writer, because this is her own 商売／仕事 利益／興味. We have on or
two people using Basic .. they are no real testers, but will 実験（する） teir
own 開発s with a new RC as soon as this arrives.

But you need someone who knows all those people, knows who is really
using the new 見解／翻訳／版 and after all decides if it is ready to relase.
This is a whole lot of work.

What is becoming more and more important within the last months is that
we do "a lot" of work in an 早期に 行う／開催する／段階. E.g. we had a IRC-party to
の近くに 問題／発行するs in the new Chart module (get the 名簿（に載せる）／表（にあげる） of 直す／買収する，八百長をするd 問題／発行するs, 選ぶ
one, see if it is really 直す／買収する，八百長をするd and の近くに it). By doing such things, we
設立する a lot of knowledge for the 解放（する） QA. With that knowledge, we
do not need so much time for the 解放（する） QA itself.
We are in a lucky 状況／情勢 for such parties indeed. We had three chart
developers on IRC yesterday ... all speaking German. This is almost
impossible for other native lang teams.
But one of the 重要なs is Jacqueline. She is 広大な／多数の／重要な in working with people
(Sun staff at the one 手渡す and new community members at the other). She
is 極端に 患者 with new members. But I'd guess she's spendin about
25%of her office hours for OOo community-work ..what is やめる a lot.
(Hours of 解放する／自由な time for OOo is still on 最高の，を越す of that).


> How many QA testers you can find?
>

The numbers ar not that high. For 解放（する）-QA we have one tester per
壇・綱領・公約 加える 2 or three new testers. Maybe 5 people extra, who
expressthat tey have at least 任命する／導入するs an RC and worked for some days
with this new 見解／翻訳／版.

> What are the problems of your community?

The problem is to 調整する all those things. As we try to attrackt
new people, we need to teach them every time. As not all work with the
道具 and 報告（する）／憶測 problems the formal way, someone needs to collect all
the （警察などへの）密告，告訴（状） (and someone needs to 今後 all the （警察などへの）密告，告訴（状） from
全世界の 事業／計画（する）s to our 地元の one).
The 解放（する） 過程 is still very コンビナート／複合体 .. so unfortunately not 平易な
to understand for newmembers.

One problem is, that it is not 平易な to 取って代わる some "重要な members". So we
had troubles with 2.2.1 解放（する）, as I've not been 利用できる and many
other team mambers were buy. Mechtilde jumped in and tried to manage the
過程 ... she did some mistakes, but after all it worked.


hope, that helps ...

Andr?閏br> ------------------------------------------------------------------

Christoph Lukasiak 示唆するd me to create a self introduction page.
I was not good at wiki and 極端に lazy about it. Yesterday I learned how to upload my photo :)

Of course, I have already have one at MacOSX developer page , but it seems editing wiki is lot easier :)

Thanks Chirstoph!

2.2.1 of Ja 見解／翻訳／版 has been 解放（する）d (in Japanese), It took very long time after the English 見解／翻訳／版
has been 解放（する）d. But I believe, our community made a 広大な／多数の／重要な 進歩.
First, Mira-san created a wiki for 2.2.1 解放（する） 時刻表／予定表
Second, IRC discussion の中で testers.

We aware a lot of problems, and I asked Andre Schnabel and Sophie
Gautier for their advices. They are 極端に 肉親，親類d and sincere for answering our questions. I just 今後d our e-mails to ja-discuss 名簿（に載せる）／表（にあげる）, asked for translation. I'll 地位，任命する a 要約 later.
I thank them very much. I'm very happy to have such a good friends
around the world!

What we need for 解放（する）, what can be a problem doing QA in community, etc.

I should ask all the Native language leads for advices, or problems,
and collect them. This is a 未来 仕事 as the QA 事業／計画（する） lead.

Thanks!

MacOSX

PPC AQUA, PPC X11, Intel X11 builds of SRC680_m221

Intel AQUA builds of SRC680_m221

They 占領する 40Gbytes for each snapshot! Generously, Maeda-san,
CEO of Good-Day. Inc
昇格 the 金物類／武器類, 追加するing more HDD space! thanks! Good-Day
and Maeda-san, and Nishiyama-san!!

You can download at
ftp://ooopackages.good-day.逮捕する/pub/OpenOffice.org/MacOSX/SRC680_m221/

BTW: it will 負かす／撃墜する from 15:00(JST=UTC+9) to 昇格 金物類／武器類 :)

によれば:
http://people.freebsd.org/~peter/ports.window.txt

現在の time: Fri Jul 20 05:12:35 UTC 2007

NOTE: this 含むs the ports cvs tree only

This time the （米）棚上げする／（英）提議する is sorted by commits within the cutoff window.
LAST STATE RANK COUNT NAME
20070716 ok 1 4344 miwi
20070718 ok 2 2165 clsung
20070719 ok 3 1694 rafan
20070719 ok 4 1344 sat
20070719 ok 5 972 pav
20070617 ok 6 915 kris
20070719 ok 7 792 dinoex
20070713 ok 8 740 alepulver
20070717 ok 9 654 marcus
20070714 ok 10 646 ahze
20070718 ok 11 607 maho

Yeah, I'm 階級d at 11th. Of course, my commits can be
合併するd into one for some 事例／患者s, and the number of commits
*DOES NOT* 反映する its 質, though.

As a part of MacOSX porting team, I asked Shaun and Eric to
追加する my photo and short 再開する 同様に.
developers
Please send me a fan letter if you like :)

Thank Shaun and Eric