提案するd approach for 強固にする／合併する／制圧するing IssueTracker RFEs (request for enhancement) into 製品 必要物／必要条件s
Introduction
The goal of this 演習 is to 変える a 抱擁する number of unqualified IssueTracker (以前は known as IssueZilla) RFEs into a smaller number of cleaned-up (marketing) 製品 必要物／必要条件s that can be understood both by 使用者s and developers.
The goal of this 演習 is to:
-
除去する duplicate RFEs
-
増加する 質 of RFEs
-
Get to a manageable number of 必要物／必要条件s that the community can 投票（する） on and that a 商業の contributor (e.g. Sun) can 扱う as part of a 製品 鮮明度／定義 過程
In this 過程 description we distinguish between RFEs submitted by community members and the (marketing) 製品 必要物／必要条件s that are derived from the 初めの RFEs. The RFEs can be high-level or low-level, very 詳細（に述べる）d or vague, can 含む examples or not, etc. The new 必要物／必要条件s however should be 平易な to understand and coherent.
All 必要物／必要条件s should also 含む （警察などへの）密告，告訴（状） about the importance of a 必要物／必要条件 to a 明確な／細部 使用者 group 同様に as 関連した market data. For example, a 明確な／細部 use 事例／患者 how a feature would be used by a 使用者 would help to understand why a feature is needed and what the significance to the market is.
Since the 実施 is up to the developer who 結局 選ぶs up a 必要物／必要条件, it is more important to 述べる the 願望（する）d functionality and typical use 事例／患者s instead of explaining how something should be 器具／実施するd.
Overview Diagram
Query RFEs submitted by community members
The さまざまな RFEs will be sorted, 評価するd and 強固にする／合併する／制圧するd by topic, i.e. by 構成要素. A 始める，決める of pre-defined queries will be 供給するd by the QA and RFE team, but ーするために 見解（をとる） all open RFEs, the に引き続いて fields are important:
| Field | 選択 |
| Issuetype | Enhancement and Feature |
| Status | Unconfirmed, New, Started and 再開するd |
| IssueTracker queries can be saved. It is also possible to search for submitters using the fields Username and Reporter. The query can be 狭くするd 負かす／撃墜する using the fields 構成要素, 的 Milestone, Date, etc. | |
変える low-level RFEs into high-level 必要物／必要条件s
Different IssueTracker RFEs that belong together because they talk about the same 必要物／必要条件 will be 合併するd into one NEW 必要物／必要条件 in IssueTracker, by 割り当てるing the 初めの RFE's to a 完全に new “meta” 問題／発行する, i.e. the 必要物／必要条件. The 要約 of the new 必要物／必要条件 should 要約する the 重要な elements of the old RFEs.
For example Writer RFE's like “器具／実施する styles preview in the Stylist”, “dynamic styles” and “追加する default shortcuts to 増加する/減少（する） font size” could be 合併するd into a (要約) 必要物／必要条件 like “簡単にする formatting and font 扱うing in Writer”.
使用者s, developers and marketing 事業／計画（する） members should be able to understand the 必要物／必要条件 要約 without having to read all the old RFEs. However, the new 必要物／必要条件 should 含む／封じ込める links to the old RFEs (i.e. the RFE 入ること／参加（者）s should 封鎖する the 必要物／必要条件 入ること／参加（者） in IssueTracker), because the old RFE's 供給する more 詳細（に述べる）d （警察などへの）密告，告訴（状） about the 必要物／必要条件 and the use 事例／患者s.
The Issuetype of the new 必要物／必要条件 should be "Feature". It should be 割り当てるd to someone from the 必要物／必要条件s team, e.g. Erwin Tenhumberg (erwint). Since this is a marketing 仕事, the 必要物／必要条件s should not be 割り当てるd to the engineers 直接／まっすぐに.
The 優先 should be left at the default value (3), and the 的 milestone will not be 始める，決める for the new 必要物／必要条件s. The 優先 will be 決定するd through the OpenOffice.org 投票（する）ing 機械装置 once all 必要物／必要条件s are known. The 的 milestone can only be 始める，決める by the party/developer that 約束s to work on the 必要物／必要条件.
The status has to be “New”. It will be 始める，決める to “Started” as soon as someone 約束s to 器具／実施する a particular 必要物／必要条件. A special keyword "必要物／必要条件" has to be 始める，決める. The description should also start with "必要物／必要条件:". It also 許すs to search for the word "必要物／必要条件" in the description.
必要物／必要条件s ARE NOT the same as the 正規の／正選手 RFEs submitted by the community members as FEATUREs and ENHANCEMENTs. If an RFE is 井戸／弁護士席 written it should be very 平易な to turn it into a 必要物／必要条件, but in many 事例／患者s this will 要求する some clean-up work.
For the 初めの/old RFEs the 問題／発行する ID of the new 必要物／必要条件 will be 始める，決める in the “問題／発行する xxx 封鎖するs” field. This 確実にするs that no data gets lost and that 進歩 can be 監視するd on a high level.
At this 行う／開催する／段階 we have a 名簿（に載せる）／表（にあげる） of 必要物／必要条件s that is much shorter than the 初めの RFE's.
Prioritization of 必要物／必要条件s
Once all old RFEs have been 変えるd into "clean and polished" 必要物／必要条件s the new 必要物／必要条件s get a 優先. This is a separate step because prioritization is difficult or even impossible when the total number of 必要物／必要条件s is unknown. 予定 to the fact that 工学 資源s are 限られた／立憲的な, a "first come first serve" approach does not work. In 新規加入, using something like 投票（する）ing on the 初めの RFEs does not work because they are either hard to understand by the people who are supposed to 投票（する） or there are 多重の RFEs for 正確に／まさに the same 製品 必要物／必要条件. The prioritization will happen through the IssueTracker 投票（する）ing 機械装置.
At this 行う／開催する／段階 we have a 名簿（に載せる）／表（にあげる） of 必要物／必要条件s that also 含む （警察などへの）密告，告訴（状） about the 優先 from a 使用者 point of 見解（をとる）.
実施 of the 必要物／必要条件s
Sun as one of the 重要な code contributors to the OpenOffice.org 事業／計画（する） will decide to work on 必要物／必要条件s that have a high 優先 and are 提携させるd with Sun's 製品 and 戦略 goals. However, that also means that some 必要物／必要条件s will not be 演説（する）／住所d by Sun. This can even happen with 優先s with a 比較して high 使用者 優先 if they don't fit into Sun's 戦略.
For all 必要物／必要条件s that Sun decides to 器具／実施する, Sun will create a PCD item in IssueTracker, i.e. the 要約 含む／封じ込めるs the abbreviation “PCD” and also a keyword “PCD” will be 始める，決める (PCD is short for 製品 概念 文書). The 初めの 必要物／必要条件 has to get a comment referring to the new PCD item.
A PCD item explains the 概念 what our 工学 team will 器具／実施する. Thus, a PCD item does not talk about the “nitty gritty” 実施 詳細（に述べる）s, but 輪郭（を描く）s the functionality that will get 器具／実施するd.
Since Sun might decide not to fully 器具／実施する a 製品 必要物／必要条件, the 初めの 必要物／必要条件 will stay open. The PCD item will however depend on the 必要物／必要条件 for 跡をつけるing 目的s.
The 存在 of a PCD item makes it possible to 跡をつける the 進歩 on a particular 必要物／必要条件. The (可能性のある) difference between a 必要物／必要条件 and its corresponding PCD item is the gap between the 必要物／必要条件 and its 実施.
Someone can either fill the gap by 器具／実施するing the 残り／休憩（する） or creating a 完全に 独立した・無所属 second 実施 that covers everything.
At this point we have a 名簿（に載せる）／表（にあげる） of 必要物／必要条件s and a 名簿（に載せる）／表（にあげる） of PCD items. Every PCD item must have a corresponding 必要物／必要条件, but there will also be 必要物／必要条件s that don't have a PCD item yet.
の近くにing 必要物／必要条件s
Once the 工学 work on the PCD items has been 完全にするd (i.e. a working build can be downloaded and 実験（する）d) the PCD item will be の近くにd. If the PCD item fully 器具／実施するs a 必要物／必要条件 the 必要物／必要条件 will also be の近くにd. If the PCD item only partly 器具／実施するd the 必要物／必要条件, the 初めの submitters have to decide if the 必要物／必要条件 should stay open or if the 存在するing 実施 is 十分な.
Depending on the number, open 必要物／必要条件s will stay open until the next 解放（する） cycle. If still nobody wants to 演説（する）／住所 it, it will either get の近くにd or transferred to some 肉親，親類d of general to-do 名簿（に載せる）／表（にあげる）.
An example
John 服従させる／提出するs an RFE with IssueTracker ID 00001 説 that “It should be 平易な to 交流 とじ込み／提出するs in a 井戸／弁護士席 known and 広範囲にわたって used read-only とじ込み／提出する 判型.”
Peter 服従させる／提出するs an RFE with IssueTracker ID 00002 需要・要求するing that “It should be easier to 生成する PDF とじ込み／提出するs”.
Jane creates yet another RFE with IssueTracker ID 00003 asking for “PDF 輸出（する） 解答 that is 100% 両立できる with Acrobat Distiller”.
Finally, Susy opens an RFE with IssueTracker ID 00004 説 that “My friend should be able to read my とじ込み／提出するs without having to download OpenOffice.org”.
All these 独立した・無所属 RFEs can be 合併するd into just one 製品 必要物／必要条件. Thus, the 必要物／必要条件s team creates a new 必要物／必要条件 that looks like this: “OpenOffice.org should have a PDF 輸出（する） feature that is 100% 両立できる with Acrobat Distiller 見解／翻訳／版 XYZ”.
After some 投票（する）ing Sun would decide to work on the 必要物／必要条件 and thus create a PCD item. However, since Sun does not have enough 資源s, Sun decides not to created a Distiller clone (at least not in the first step). Instead the PCD item says “OpenOffice.org will get basic PDF 輸出（する） support for all 使用／適用s. The functionality will cover X, Y, and Z, but not 器具／実施する the に引き続いて Acrobat Distiller features: ....”
As a consequence, someone else can create a PCD item for the “残り／休憩（する） 必要物／必要条件”, create a 完全に 独立した・無所属 付加 実施 or just live with the fact that the 必要物／必要条件 might never get fully 器具／実施するd.
