Important things to know about the API and the dev mailing 名簿（に載せる）／表（にあげる）
This is a 思い出の品 of important things to know about the API and the
dev@openoffice.apache.org mailing 名簿（に載せる）／表（にあげる）.
*** ====================================================================
*** Contents
*** --------------------------------------------------------------------
1. Appropriate Mailing 名簿（に載せる）／表（にあげる）
2. SDK + Developers Guide
3. Form of your Messages
4. Support Questions
5. 報告（する）／憶測ing Defects
6. 出資／貢献s
7. Newsletter
*** ====================================================================
*** 1. Appropriate Mailing 名簿（に載せる）／表（にあげる）
*** --------------------------------------------------------------------
Not all questions are really API 問題／発行するs. That said the former 事業／計画（する）s of
OOo are now 崩壊（する）d to the Apache OpenOffice 事業／計画（する）.
dev@openoffice.apache.org is always appropriate.
http://udk.openoffice.org
for questions about UNO 橋（渡しをする）s and language bindings
含むing StarBASIC/OOoBASIC
http://枠組み.openoffice.org/scripting/
for questions about the scripting 枠組み
http://xml.openoffice.org
for questions regarding our XML とじ込み／提出する 判型s
*** ====================================================================
*** 2. SDK + Developers Guide
*** --------------------------------------------------------------------
Please 任命する／導入する the SDK from the OOo download area and read at least the
一時期／支部s First Steps and the 一時期／支部 your question is about of the
Developers Guide. This is a 名簿（に載せる）／表（にあげる） of volunteers, not a support 会議.
We like to help you, but we cannot do the footwork for you.
An online 見解／翻訳／版 of the Developers Guide can be 設立する here:
http://api.openoffice.org/DevelopersGuide/DevelopersGuide.html
*** ====================================================================
*** 3. Form of your Messages
*** --------------------------------------------------------------------
Please use an appropriate form for your messages:
- 引用する as much as is necessary to make 状況 理解できる, NOT more
- do NOT put a 十分な 引用する below your message
- do NOT use HTML mails
- do NOT attach 文書s
- do NOT ask NEW questions in reply to 存在するing threads
By breaking these 支配するs, do not wonder if your question remains
unanswered, most likely even unseen 予定 to mail filters.
If you have 付加 data, like a 文書 or a longer source code,
please 供給する us a link where we can download these. You might upload
such 文書s to the とじ込み／提出する area:
http://api.openoffice.org/servlets/ProjectDownloadList
As far as I know, everybody can do that, you might need an
OpenOffice.org account. As the responsible 事業／計画（する） lead, I just have to
認可する the とじ込み／提出するs to get published. But keep in mind: the more a
volunteer has to read to 得る，とらえる your question, the lesser the change for
an answer.
*** ====================================================================
*** 4. Support Questions
*** --------------------------------------------------------------------
Please keep in mind that we developers cannot always answer 明確な／細部
questions or even 器具／実施する features for your 使用／適用. This is NOT
a support 会議 in the sense of 保証（人）d help. If we have a 解答
in mind, we will help you. But if it costs us too much time, and it is
a 明確な／細部 problem, we might not be able to spend the time on your 問題／発行する.
On the other 手渡す, we try to answer all questions. And we need the
support of other community members.
But even as somebody who has only questions yet, you can already
与える／捧げる to OOo: If you had a question and it was answered to your
satisfaction it would be 広大な／多数の／重要な if you 地位，任命する a 要約 in our 標準化するd
form:
http://api.openoffice.org/SDK/snippets/索引.html
This 避けるs using up the time of the volunteers to answer the same
questions over and over again. Thanks for your 出資／貢献!
If your question is 関係のある to your 使用／適用 code, please 含む a
minimalistic 見解／翻訳／版 of your source code with your question. And please
追加する all important （警察などへの）密告，告訴（状）. This 含むs mostly the 固める／コンクリート
構成要素 which you are using, the 壇・綱領・公約, 見解／翻訳／版 of OOo and OOo SDK
your programming language. There might be a big difference, if your
problem is with a Text 反対する in OOo/Writer or a Text 反対する in a
OOo/Draw 形態／調整. But keep your （警察などへの）密告，告訴（状） as short as possible. Do not
地位，任命する 完全にする programs! The better you 削減（する） it 負かす／撃墜する, to the 問題／発行する, the
higher the change for an volunteer who 選ぶs your question up and answers.
IMPORTANT: Please 避ける sending mails 本人自身で to the 事業／計画（する） developers,
unless you are explicitly asked to do so. We do not 申し込む／申し出 direct support
by personal email.
*** ====================================================================
*** 5. 報告（する）／憶測ing Defects
*** --------------------------------------------------------------------
If you are pretty sure that you 設立する a defect in either the
documentation or 実施, please とじ込み／提出する this 問題／発行する on OOos IssueZilla:
https://www.openoffice.org/project_issues.html
実施 bugs which do not only occur by API usage can be 報告（する）／憶測d
直接／まっすぐに to the appropriate 事業／計画（する） (like sw, sd, sc or 枠組み), API
specification an documentation 問題／発行するs or 行方不明の interfaces you can
とじ込み／提出する to the API 事業／計画（する）. StarBASIC/OOoBASIC 問題／発行するs 現実に belong to
the UDK 事業／計画（する）. If you choose the wrong 事業／計画（する）, your 問題／発行する might be
延期するd.
Please do not misuse IssueZilla as a support 道具. It is not and your
問題／発行する will 簡単に be 拒絶するd.
*** ====================================================================
*** 6. 出資／貢献s
*** --------------------------------------------------------------------
There are plenty 可能性s of 出資／貢献s to OOo, even for
"絶対の beginners". Here some ideas:
- Read the documentation and 報告（する）／憶測 問題／発行するs if you find any
(-> 5. 報告（する）／憶測ing Defects)
- Use the 使用／適用s and API and 報告（する）／憶測 問題／発行するs if you find any
(-> 5. 報告（する）／憶測ing Defects)
- 要約する answers which were given to your questions
(-> 4. Support questions)
- 与える／捧げる your larger API examples to our example collection
(http://api.openoffice.org/SDK/example_collection.html)
If you want to 供給する us with source code or documentation, we need a
copyright assignment:
http://www.openoffice.org/与える／捧げるing.html
Please read this 文書 to learn about how and why.
