path: root/locales/ja/LC_MESSAGES/ap-process.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) 1996, 1997, 1998 Ian Jackson, Christian Schwarz, 1998-2017,
# The Debian Policy Mailing List
# This file is distributed under the same license as the Debian Policy
# Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2018.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Debian Policy Manual 4.1.6.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-08-02 11:56+0800\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.4.0\n"

#: ../../ap-process.rst:2
msgid "Debian Policy changes process"
msgstr ""

#: ../../ap-process.rst:7
msgid "Introduction"
msgstr ""

#: ../../ap-process.rst:9
msgid ""
"To introduce a change in the current Debian Policy, the change proposal "
"has to go through a certain process.  [#]_"
msgstr ""

#: ../../ap-process.rst:15
msgid "Change Goals"
msgstr ""

#: ../../ap-process.rst:17
msgid ""
"The change should be technically correct, and consistent with the rest of"
" the policy document. This means no legislating the value of π. This also"
" means that the proposed solution be known to work; iterative design "
"processes do not belong in policy."
msgstr ""

#: ../../ap-process.rst:22
msgid ""
"The change should not be too disruptive; if very many packages become "
"instantly buggy, then instead there should be a transition plan. "
"Exceptions should be rare (only if the current state is really "
"untenable), and probably blessed by the TC."
msgstr ""

#: ../../ap-process.rst:27
msgid ""
"The change has to be reviewed in depth, in the open, where any one may "
"contribute; a publicly accessible, archived, open mailing list."
msgstr ""

#: ../../ap-process.rst:30
msgid "Proposal should be addressed in a timely fashion."
msgstr ""

#: ../../ap-process.rst:32
msgid ""
"Any domain experts should be consulted, since not every policy mailing "
"list subscriber is an expert on everything, including policy maintainers."
msgstr ""

#: ../../ap-process.rst:36
msgid ""
"The goal is rough consensus on the change, which should not be hard if "
"the matter is technical. Technical issues where there is no agreement "
"should be referred to the TC; non-technical issues should be referred to "
"the whole developer body, and perhaps general resolutions lie down that "
"path."
msgstr ""

#: ../../ap-process.rst:42
msgid ""
"Package maintainers whose packages may be impacted should have access to "
"policy change proposals, even if they do not subscribe to policy mailing "
"lists (policy gazette?)."
msgstr ""

#: ../../ap-process.rst:49
msgid "Current Process"
msgstr ""

#: ../../ap-process.rst:51
msgid ""
"Each suggested change goes through different states. These states are "
"denoted through either usertags of the debian-policy@packages.debian.org "
"user or, for ``moreinfo``, ``patch``, ``pending``, and ``wontfix``, "
"regular tags."
msgstr ""

#: ../../ap-process.rst:56
msgid ""
"`Current list of bugs <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src"
"=debian-policy&pend-exc=done>`_"
msgstr ""

#: ../../ap-process.rst:59
msgid ""
"The Policy delegates are responsible for managing the tags on bugs and "
"will update tags as new bugs are submitted or as activity happens on "
"bugs. All Debian Developers should feel free to add the seconded tag as "
"described below. Other tags should be changed with the coordination of "
"the Policy Team."
msgstr ""

#: ../../ap-process.rst:68
msgid "State A: More information required"
msgstr ""

#: ../../ap-process.rst:70
msgid ""
"The Policy delegates are unable to determine whether the bug is really a "
"Policy matter, or judge that there are missing details that would prevent"
" a fruitful discussion (and may result in a confused and unhelpful "
"discussion)."
msgstr ""

#: ../../ap-process.rst:75
msgid ""
"Policy delegates ask the original submitter to provide the missing "
"details.  Others are asked to refrain from discussing whatever they take "
"the issue to be, limiting their postings to attempts to supply the "
"missing details."
msgstr ""

#: ../../ap-process.rst:80
msgid ""
"`TAG: moreinfo <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-"
"policy&pend-exc=done&tag=moreinfo>`_"
msgstr ""

#: ../../ap-process.rst:82
msgid ""
"What needs to happen next: Submitter (or someone else) provides the "
"requested information within 30 days, or the bug is closed."
msgstr ""

#: ../../ap-process.rst:85
msgid "The majority of bugs will skip this stage."
msgstr ""

#: ../../ap-process.rst:90
msgid "State B: Discussion"
msgstr ""

#: ../../ap-process.rst:92
msgid ""
"Discuss remedy. Alternate proposals. Discussion guided by delegates. "
"There should be a clear time limit to this stage, but as yet we have not "
"set one."
msgstr ""

#: ../../ap-process.rst:96
msgid ""
"`TAG: discussion <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src"
"=debian-policy&pend-exc=done&tag=discussion>`_"
msgstr ""

#: ../../ap-process.rst:99
msgid ""
"What needs to happen next: Reach a conclusion and consensus in the "
"discussion and make a final proposal for what should be changed (if "
"anything), moving to the proposal tag."
msgstr ""

#: ../../ap-process.rst:106
msgid "State C: Proposal"
msgstr ""

#: ../../ap-process.rst:108
msgid ""
"A final proposal has emerged from the discussion, and there is a rough "
"consensus on how to proceed to resolve the issue."
msgstr ""

#: ../../ap-process.rst:111
msgid ""
"`TAG: proposal <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-"
"policy&pend-exc=done&tag=proposal>`_"
msgstr ""

#: ../../ap-process.rst:114
msgid ""
"What needs to happen next: Provided that the rough consensus persists, "
"develop a patch against the current Policy document with specific wording"
" of the change. Often this is done in conjunction with the proposal, in "
"which case one may skip this step and move directly to patch tag."
msgstr ""

#: ../../ap-process.rst:123
msgid "State D: Wording proposed"
msgstr ""

#: ../../ap-process.rst:125
msgid ""
"A patch against the Policy document reflecting the consensus has been "
"created and is waiting for formal seconds. The standard patch tag is used"
" for this state, since it's essentially equivalent to the standard "
"meaning of that tag."
msgstr ""

#: ../../ap-process.rst:130
msgid ""
"`TAG: patch <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-"
"policy&pend-exc=done&tag=patch>`_"
msgstr ""

#: ../../ap-process.rst:133
msgid ""
"What needs to happen next: The proposal needs to be reviewed and "
"seconded. Any Debian developer who agrees with the change and the "
"conclusion of rough consensus from the discussion should say so in the "
"bug log by seconding the proposal."
msgstr ""

#: ../../ap-process.rst:141
msgid "State E: Seconded"
msgstr ""

#: ../../ap-process.rst:143
msgid ""
"The proposal is signed off on by N Debian Developers. To start with, "
"we're going with N=3, meaning that if three Debian Developers agree, not "
"just with the proposal but with the conclusion that it reflects consensus"
" and addresses the original issue -- it is considered eligible for "
"inclusion in the next version of Policy. Since Policy is partly a "
"technical project governance method, one must be a Debian Developer to "
"formally second, although review and discussion is welcome from anyone. "
"Once this tag has been applied, the bug is waiting for a Policy team "
"member to apply the patch to the package repository."
msgstr ""

#: ../../ap-process.rst:153
msgid ""
"`TAG: seconded <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-"
"policy&pend-exc=done&tag=seconded>`_"
msgstr ""

#: ../../ap-process.rst:156
msgid ""
"What needs to happen next: A Policy maintainer does the final review and "
"confirmation, and then applies the patch for the next Policy release."
msgstr ""

#: ../../ap-process.rst:159
msgid ""
"This tag is not used very much because normally a Policy maintainer "
"applies the patch and moves the proposal to the next state once enough "
"seconds are reached."
msgstr ""

#: ../../ap-process.rst:166
msgid "State F: Accepted"
msgstr ""

#: ../../ap-process.rst:168
msgid ""
"Change accepted, will be in next upload. The standard pending tag is used"
" for this state since it matches the regular meaning of pending."
msgstr ""

#: ../../ap-process.rst:171
msgid ""
"`TAG: pending <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-"
"policy&pend-exc=done&tag=pending>`_"
msgstr ""

#: ../../ap-process.rst:174
msgid ""
"What needs to happen next: The bug is now in the waiting queue for the "
"next Policy release, and there's nothing left to do except for upload a "
"new version of Policy."
msgstr ""

#: ../../ap-process.rst:181
msgid "State G: Reject"
msgstr ""

#: ../../ap-process.rst:183
msgid ""
"Rejected proposals. The standard wontfix is used for this state. "
"Normally, bugs in this state will not remain open; instead, a Policy team"
" member will close them with an explanation. The submitter may then "
"appeal to the tech-ctte if they so desire. Alternately, issues appealed "
"to the tech-ctte may remain open with this tag while that appeal "
"proceeds."
msgstr ""

#: ../../ap-process.rst:190
msgid ""
"`TAG: wontfix <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-"
"policy&pend-exc=done&tag=rejected>`_"
msgstr ""

#: ../../ap-process.rst:193
msgid ""
"We may use one of the following tags here, but to date we have only used "
"dubious and ctte. It's not clear whether we need more tags for this "
"stage."
msgstr ""

#: ../../ap-process.rst:198
msgid "**dubious**"
msgstr ""

#: ../../ap-process.rst:198
msgid "Not a policy matter"
msgstr ""

#: ../../ap-process.rst:201
msgid "**ctte**"
msgstr ""

#: ../../ap-process.rst:201
msgid "Referred to the Technical Committee (tech-ctte)"
msgstr ""

#: ../../ap-process.rst:204
msgid "**devel**"
msgstr ""

#: ../../ap-process.rst:204
msgid "Referred to the developer body"
msgstr ""

#: ../../ap-process.rst:207
msgid "**delegate**"
msgstr ""

#: ../../ap-process.rst:207
msgid "Rejected by a Policy delegate"
msgstr ""

#: ../../ap-process.rst:210
msgid "**obsolete**"
msgstr ""

#: ../../ap-process.rst:210
msgid "The proposal timed out without a conclusion"
msgstr ""

#: ../../ap-process.rst:212
msgid ""
"What needs to happen next: The bug should be closed once a final "
"resolution is reached, or retagged to an appropriate state if that final "
"resolution reverses the decision to reject the proposal."
msgstr ""

#: ../../ap-process.rst:219
msgid "Other Tags"
msgstr ""

#: ../../ap-process.rst:221
msgid "All Policy bugs are additionally categorized by class of bug."
msgstr ""

#: ../../ap-process.rst:223
msgid ""
"The normative tag is used for bugs that make normative changes to Policy,"
" meaning that the dictates of Policy will change in some fashion as part "
"of the resolution of the bug if the proposal is accepted. The full "
"process is followed for such bugs."
msgstr ""

#: ../../ap-process.rst:228
msgid ""
"`TAG: normative <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src"
"=debian-policy&pend-exc=done&tag=normative>`_"
msgstr ""

#: ../../ap-process.rst:231
msgid ""
"The informative tag is used for bugs about wording issues, typos, "
"informative footnotes, or other changes that do not affect the formal "
"dictates of Policy, just the presentation. The same tags are used for "
"these bugs for convenience, but the Policy maintainers may make "
"informative changes without following the full process. Informative bugs "
"fall under their discretion."
msgstr ""

#: ../../ap-process.rst:238
msgid ""
"`TAG: informative <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src"
"=debian-policy&pend-exc=done&tag=informative>`_"
msgstr ""

#: ../../ap-process.rst:241
msgid ""
"The packaging tag is used for bugs about the packaging and build process "
"of the debian-policy Debian package. These bugs do not follow the normal "
"process and will not have the other tags except for pending and wontfix "
"(used with their normal meanings)."
msgstr ""

#: ../../ap-process.rst:246
msgid ""
"`TAG: packaging <https://bugs.debian.org/cgi-bin/pkgreport.cgi?src"
"=debian-policy&pend-exc=done&tag=packaging>`_"
msgstr ""

#: ../../ap-process.rst:250
msgid ""
"This process was originally developed by Margarita Manterola, Clint "
"Adams, Russ Allbery and Manoj Srivastava.  In 2017, Sean Whitton "
"deprecated the 'issue' usertag and added use of the 'moreinfo' tag, after"
" discussions at DebConf17."
msgstr ""