ウィキメディア財団理事会コミュニティ事案委員会/きょうだいプロジェクトのライフサイクル手順

ウィキメディア財団コミュニティ事案委員会

• メイン
• タスクフォース
  • 本来のメッセージ
  • 手順の評価
  • コメントと評価の投稿ページ
  • よくある質問

ウィキメディア財団コミュニティ事案委員会（「CAC」＝Community Affairs Committee）のタスクフォースは2023年より、プロジェクトの創始と終了の手順に取り組んできました。この作業は直接、運動戦略の勧告事項として「無料の知識を革新」、「影響力のある主題を特定」、「評価、反復、適応」などに関連しており、既存のプロジェクト群に寄せるサポートを維持し継続しながら、革新的なアイデアが流入する空間を確保します。新しいものに投資するか、現在のプロジェクトを維持するかを決定する際は、トレードオフの理解が重要です。

Some new project proposals may require significant new technical work (for example, Wikifunctions), while others can use existing tools with a different content scope, and mainly need maintenance and an active community. Evaluating a new application to validate the concept, and estimate its up-front and maintenance costs, has generally taken both community and staff time.

同時に、既存のきょうだいプロジェクトの成功と持続可能性の評価も重要です。また採用類の需要として、プロジェクトの分割や統合や廃止、独自のコミュニティを備えた外部プロジェクトの統合の場合、またはきょうだいプロジェクトを整えて外部組織との統合もしくは所属変更をする場合があります。

参加者の皆さんには当プロセスへの意見提供を呼びかけておりトーク ページへの投稿や署名して生配信の会議参加を介してするなど、意見の共有にお招きしています。さらにまた皆さんには話し合い：2024中に対話をリクエストして意見の共有もご検討ください。

はじめに

This procedure outlines the steps and requirements for opening new Wikimedia projects. Wikimedia projects aim to create, curate, and disseminate free knowledge to the world. Before initiating a new project, the committee will ensure that it aligns with Wikimedia's mission and values, as well as evaluate the financial & technical resources required by the Wikimedia Foundation and communities to support it.

プロジェクトの提案

公式なプロジェクト企画案を準備し、以下の情報を盛り込みます：

1. List the responsible initiative group(s), including those who did not design the proposal but are interested in contributing - usernames, length of involvement in the Wikimedia projects, and extended user rights, if any. It is unlikely that the project proposal by one person will be accepted.
2. Description: A description of the project, its scope, goals, & objectives. Explain how it aligns with the mission and integrates into existing projects (if possible).
3. Community Evaluation: Document community activity and assess the number of active editors and editors with extended rights (if any).
4. Content Scope: Define the scope of the project's content, including formats (e.g., text, media, data), languages (monolingual or multilingual), and topics.
5. Technical Requirements: Infrastructure and tools required to host and maintain the project.
   1. (optional) Support from an established affiliate or Hub will increase the chances of project opening/adoption.
6. Link to a working pilot or demo site (if one exists). This can be supported by a Project incubator (such as WikiSpore)
7. Publish documentation on Meta and submit the proposal on [PAGE].

新提案の討議

• Research and Feasibility Study: Conduct thorough research to ascertain the need and potential impact of the proposed project. Assess whether an existing Wikimedia project can accommodate the proposed content. Assess the main alternative non-Wikimedia projects.
• Legal and Copyright Compliance: Ensure the proposed project meets legal and copyright requirements. Determine the licensing and copyright status of content to be included.
• Financial assessment: Assess projected costs for setting it up and projected upkeep for the first few years
• Engage with Community: Engage with the Wikimedia communities, including editors, volunteers, and stakeholders. Seek input and feedback on the proposed project idea to ensure community support.

If all requirements are met, recommend to the CAC for consideration.

プロジェクトの予備承認

Submit the project proposal to the CAC for review and approval based on the following criteria:

• Alignment with Mission: Ensure the project aligns with the Wikimedia Foundation's mission of promoting free knowledge.
• Community Support: Assess the level of support and engagement from the Wikimedia community.
• Legal and Copyright Compliance: Verify that the project complies with legal and copyright requirements.
• Technical Feasibility: Confirm the technical feasibility of hosting and maintaining the project.
• Financial Feasibility: Ensure it is financially possible to support the project over time.

Recommend an outcome to the CAC:

• 否決、提案されたプロジェクトは新きょうだいプロジェクトの設立要件を満たしていません。
• Recommend in principle, but propose hosting outside Wikimedia, for indicated reasons.
• 新規のウィキメディアきょうだいプロジェクトとして開設を推薦

If everything above is positive, CAC will recommend the proposal for Board approval.

プロジェクトの終了

In general, closing a project will result in its content remaining publicly available (e.g., by making the wiki read-only); no content will disappear unless there are legal concerns (e.g., systematic copyright infringements).

Prepare a formal project proposal that includes the following information:

1. List the responsible initiative group(s) - usernames, length of involvement in the Wikimedia projects, and user rights. Application by one user may be speedily declined.
2. Identify the need: Determine the specific reasons for considering the closure of a Wikimedia project. The need to close a project should be based on compelling reasons, such as
   • Lack of impact on other Wikimedia projects and wider Internet infrastructure
   • Severe lack of community activity
   • Legal issues that cannot otherwise be resolved
   • Significant misuse that cannot otherwise be resolved
   • Strong external project to merge with
3. Community consultation: Before closing a Wikimedia project, extensive consultation with the affected community is crucial. This consultation should be open and transparent, allowing all stakeholders to express their opinions and concerns.

In case of the final decision of the “project closure,” the project can be

• 他のきょうだいプロジェクトと統合
• Retained with limited access for editing
• Archived
• Supported in moving to a different host
• In extreme cases (close to 100% copyright violation or misleading information) - deleted

作業用の用語集

• Adoption: Wikimedia Foundation hosts a new project based on MediaWiki software (or not, considering tech support projects: wikistats, wikitech,etc.), with a standalone domain and fully linked with the other projects (i.e. not only in wikilabs).
• CAC (Community Affairs Committee): a Wikimedia Foundation Board of Trustees committee.
• Closing/Sunsetting/Archiving: disable the edit function in a project, or restraint it to a very small number of curators/maintainers.
• Closing checklist: 1. Timeline for transitioning (stop new accounts, stop edits, redirect urls); 2. Choosing target to transition to (closed archive, merge, spin out); 3. Discussion with a potential merge target / maintainer; 4. Migration (technical + social support); 5. Archiving (producing a final archive of our last version).
• Language Committee: a Board advising committee of volunteer Wikimedians, which makes decisions about opening and closing of the different language variants of the same projects, aka Sister Projects.
• Project: almost everything is a project. Wikipedia is a project, English Wikipedia is a project, there are wikiprojects in Wikipedia… this word is ambiguous and is not a good way to conceptualize the global scheme.
• Product : technical projects such as Wikistats or Wikibase are usually considered as products rather than projects.
• きょうだいプロジェクト：ウィキメディア財団が承認する既存の MediaWiki ベースのプロジェクト類で、一例としてウィキペディア（en.wikipedia.org、pl.wikipedia.org、de.wikipedia.org などを含む）、ウィクショナリー、ウィキソースに加えて候補の新しいプロジェクトとして WikiJournal や Vikidia など。私たちの呼称は他に、グローバル・プロジェクト、高次プロジェクトまたは包括的なアイデンティティなどがあります。
• 姉妹プロジェクト：さまざまな言語のウィキプロジェクト類のことで、例として英語版ウィキペディアやヨルバ語版ウィキペディアなど。
• 分割：下位プロジェクトだった新プロジェクトのために新規空間を作成すること。英語版ウィクショナリーは当初、英語版ウィキペディアの一部でした。
• Wikistats：例：ウィキメディア統計 - 英語版ウィキクオート（統計ウィキ）