Google Git
Sign in
apache/uima-site/refs/heads/main/./docs/decisions.html
blob: ebba2cf8fed6639e5c61513418fd2a140dedefbd [file]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "https://www.w3.org/TR/html4/loose.dtd">
<!-- ====================================================================== -->
<!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
<!-- ====================================================================== -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<style type="text/css">@import "stylesheets/base.css";</style>
<meta name="author" value=" UIMA Documentation
Team">
<meta name="email" value="dev@uima.apache.org">
<title>Apache UIMA - Apache UIMA&trade; Project Guidelines</title>
<!-- Begin Cookie Consent plugin by Silktide - https://silktide.com/cookieconsent -->
<!-- Commented out because implied consent is not compatible with GDPR -->
<!--
<script type="text/javascript">
window.cookieconsent_options = {"message":"This website uses cookies to ensure you get the best experience on our website","dismiss":"Got it!","learnMore":"More info","link":"https://uima.apache.org/privacy-policy.html","theme":"dark-bottom"};
</script>
<script type="text/javascript" src="/cookieconsent2/cookieconsent.min.js"></script>
-->
<!-- End Cookie Consent plugin -->
<!-- Begin Google Analytics -->
<!-- Commented out because GA requires consent according to GDPR -->
<!--
<script>
(function(i,s,o,g,r,a,m){i['GoogleAnalyticsObject']=r;i[r]=i[r]||function(){
(i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
m=s.getElementsByTagName(o)[0];a.async=1;a.src=g;m.parentNode.insertBefore(a,m)
})(window,document,'script','//www.google-analytics.com/analytics.js','ga');
ga('create', 'UA-70846351-1', 'auto');
ga('set', 'anonymizeIp', true);
ga('send', 'pageview');
</script>
-->
<!-- End Google Analytics -->
</head>
<body>
<div class="topLogos">
<table border="0" width="100%" cellspacing="0">
<!-- TOP IMAGE -->
<tr>
<td align='LEFT'>
<a href="index.html">
<img style="border: 1px solid black;" src="./images/UIMA_banner2tlpTm.png" alt="UIMA project logo" border="0"/>
</a>
</td>
<td align='CENTER'>
<div class="pageBanner">Apache UIMA&trade; Project Guidelines</div>
</td>
<td align='RIGHT'>
<a href="https://www.apache.org">
<img src="./images/asf-logo-on-white-smallTm.png" alt="Apache UIMA" border="0"/>
</a>
</td>
</tr>
</table>
<hr noshade="" size="1"/>
</div>
<table border="0" width="100%" cellspacing="4">
<tr>
<td align='RIGHT' colspan="2">
<form method="get" action="https://www.google.com/search">
Search the site
<input type="text" name="q" size="25" maxlength="255" value="" />
<input type="hidden" name="sitesearch" value="https://uima.apache.org/" />
<input name="Search" value="Search Site" type="submit"/>
</form>
</td>
</tr>
<tr> <!-- LEFT SIDE NAVIGATION -->
<td width="20%" valign="top">
<!-- regular menu -->
<div class="navBar">
<br/>
<div class="navBarItem"> <div class="navPartHeading">General</div>
</div>
<div class="navBar">
<div class="navBarItem"> <a href="./index.html">Home</a>
</div>
<div class="navBarItem"> <a href="./downloads.cgi">Downloads</a>
</div>
<div class="navBarItem"> <a href="./documentation.html">Documentation</a>
</div>
<div class="navBarItem"> <a href="./news.html">News</a>
</div>
<div class="navBarItem"> <a href="./publications.html">Publications</a>
</div>
<br style="line-height: .5em"/>
<div class="navBarItem"> <a href="https://issues.apache.org/jira/browse/uima" target="_blank" rel="noopener">Issue tracker <img src="images/offsitelink.png"/></a>
</div>
<div class="navBarItem"> <a href="https://cwiki.apache.org/confluence/display/UIMA/" target="_blank" rel="noopener">Wiki <img src="images/offsitelink.png"/></a>
</div>
<br style="line-height: .5em"/>
<div class="navBarItem"> <a href="https://cwiki.apache.org/confluence/display/UIMA/Powered+by+Apache+UIMA" target="_blank" rel="noopener">Powered By UIMA <img src="images/offsitelink.png"/></a>
</div>
</div>
<br/>
<div class="navBarItem"> <div class="navPartHeading">Community</div>
</div>
<div class="navBar">
<div class="navBarItem"> <a href="./get-involved.html">Get Involved</a>
</div>
<div class="navBarItem"> <a href="./mail-lists.html">Mailing Lists</a>
</div>
<div class="navBarItem"> <a href="./contribution-policy.html">Contribution Policies</a>
</div>
<div class="navBarItem"> <a href="./faq.html">FAQ</a>
</div>
<div class="navBarItem"> <a href="./project-guidelines.html">Project Guidelines</a>
</div>
</div>
<br/>
<div class="navBarItem"> <div class="navPartHeading">Components & Tools</div>
</div>
<div class="navBar">
<div class="navBarItem"> <a href="./sandbox.html#uima-addons-annotators">Annotators</a>
</div>
<div class="navBarItem"> <a href="./toolsServers.html">Tools & Servers</a>
</div>
<div class="navBarItem"> <a href="./sandbox.html">Addons and Sandbox</a>
</div>
<div class="navBarItem"> <a href="./ruta.html">UIMA Ruta</a>
</div>
<div class="navBarItem"> <a href="https://github.com/apache/uima-uimafit" target="_blank" rel="noopener">uimaFIT <img src="images/offsitelink.png"/></a>
</div>
<div class="navBarItem"> <a href="./external-resources.html">External Resources</a>
</div>
</div>
<br/>
<div class="navBarItem"> <div class="navPartHeading">Development</div>
</div>
<div class="navBar">
<div class="navBarItem"> <a href="./dev-quick.html">Quick Start: building</a>
</div>
<div class="navBarItem"> <a href="./building-uima.html">Building from Source</a>
</div>
<div class="navBarItem"> <a href="./one-time-setup.html">One-time setups</a>
</div>
<div class="navBarItem"> <a href="./svn.html">Source Code</a>
</div>
<div class="navBarItem"> <a href="./release.html">Doing a UIMA release</a>
</div>
<div class="navBarItem"> <a href="https://www.apache.org/security/committers.html" target="_blank" rel="noopener">Doing a CVE (Apache) <img src="images/offsitelink.png"/></a>
</div>
<div class="navBarItem"> <a href="./eclipse-update-site.html">Eclipse Update Sites</a>
</div>
<div class="navBarItem"> <a href="./git.html">GIT</a>
</div>
<div class="navBarItem"> <a href="./codeConventions.html">Code Conventions</a>
</div>
<div class="navBarItem"> <a href="./uima-specification.html">UIMA Specification (OASIS)</a>
</div>
<div class="navBarItem"> <a href="./team-list.html">Project Team</a>
</div>
<div class="navBarItem"> <a href="./maven-design.html">Maven Use</a>
</div>
<div class="navBarItem"> <a href="./updating-website.html">Updating this Website</a>
</div>
</div>
<br/>
<div class="navBarItem"> <div class="navPartHeading">Events and Conferences</div>
</div>
<div class="navBar">
<div class="navBarItem"> <a href="./coling14.html">COLING 2014</a>
</div>
<div class="navBarItem"> <a href="./gscl13.html">GSCL 2013</a>
</div>
<div class="navBarItem"> <a href="./iks09.html">IKS 2009</a>
</div>
<div class="navBarItem"> <a href="./gscl09.html">GSCL 2009</a>
</div>
<div class="navBarItem"> <a href="./lsm09.html">LSM 2009</a>
</div>
<div class="navBarItem"> <a href="./lrec08.html">LREC 2008</a>
</div>
<div class="navBarItem"> <a href="./gldv07.html">GLDV 2007</a>
</div>
</div>
<br/>
<div class="navBarItem"> <div class="navPartHeading">ASF</div>
</div>
<div class="navBar">
<div class="navBarItem"> <a href="https://www.apache.org/licenses/" target="_blank" rel="noopener">License <img src="images/offsitelink.png"/></a>
</div>
<div class="navBarItem"> <a href="https://www.apache.org/foundation/thanks.html" target="_blank" rel="noopener">ASF Sponsors <img src="images/offsitelink.png"/></a>
</div>
<div class="navBarItem"> <a href="https://www.apache.org/foundation/sponsorship.html" target="_blank" rel="noopener">ASF Sponsorship <img src="images/offsitelink.png"/></a>
</div>
<div class="navBarItem"> <a href="./security_report">Security</a>
</div>
</div>
</div>
</td>
<td width="80%" align="left" valign="top">
<div class="sectionTable">
<table class="sectionTable">
<tr><td>
<a name="Decision Making"><h1><img src="images/UIMA_4sq50tightCropSolid.png"/>&nbsp;Decision Making</h1></a>
</td></tr>
<tr><td>
<blockquote class="sectionBody">
<h3 align="center"><font color="#FF0000"><b>Note: This is a working draft
document.</b>
</font></h3>
<p align="center">Discussion of this document is occuring on the uima-dev mailing list.</p>
<br />
<p> All
<a href="roles.html">Contributors</a> are encouraged to participate in
decisions, but the decision itself is made by those that have
<a href="roles.html">Committer</a> status in the Project. In other words, the
Project is a
"
<em>Minimum Threshold Meritocracy</em>". In addition, release voting
makes a distinction between binding votes and other votes - binding votes being
those made by official members of the PMC (Project Management Committee).
</p>
<h2>Voting</h2>
<p> The act of voting carries certain obligations. Voting members are not only stating
their opinion, they are also agreeing to help do the work.
</p>
<p> Any subscriber to the list may vote on any issue or action item. However, the only
binding votes are those cast by a Committer (non release votes),
or a PMC member (for release votes). <!--If the vote is about a change to the source code or
documentation and the primary author is a Contributor and not a
Committer, the primary author of what is being changed may also
cast a binding vote on that issue. -->
</p>
<p> Any Contributor or Committer ("member") may call for an action-item vote on the
uima-dev mailing list. It is preferred that a vote be preceded by a formal proposal
offered for discussion purposes. The message announcing a vote should contain a
Subject beginning with "[VOTE]", and a distinctive one-line summary corresponding
to the action item for the vote.
</p>
<p>Each vote can be made in one of three flavors:</p>
<table>
<tr>
<td>
<strong>+1</strong>
</td>
<td>
"Yes," "Agree," or "the action should be
performed." On some issues this is only binding if the voter has tested the
action on their own system(s).
</td>
</tr>
<tr>
<td>
<strong>+/-0</strong>
</td>
<td>
"Abstain," "no opinion". An abstention may have
detrimental effects if too many people abstain. -0 can indicate lack of support,
but without any alternative being proposed.
</td>
</tr>
<tr>
<td>
<strong>-1</strong>
</td>
<td>
"No" On issues where consensus is required, this vote counts as a
<strong>veto</strong>. All vetos must contain an explanation of why the veto is
appropriate, and possibly, an alternative. Vetos with no explanation are void.
No veto can be overruled. If you disagree with the veto, you should lobby the
person who cast the veto. Voters intending to veto an action item should make
their opinions known to the group immediately so that the problem can be remedied
as early as possible.
</td>
</tr>
</table>
<p>An action item may need one of two types of approval.</p>
<blockquote>
<p> An action requiring consensus approval must receive at least
<strong>3 binding +1</strong> votes and
<strong>no binding vetos</strong>.
</p>
<p> An action requiring majority approval must receive at least
<strong>3 binding +1</strong> votes and more
<strong>+1</strong> votes than
<strong>-1</strong> votes.
</p>
</blockquote>
<p> Except for a public release, All other action items are considered to have lazy
approval until somebody votes
<strong>-1</strong>, at which point the action item is converted to a formal
consensus or majority vote, depending on the type of action item.</p>
<blockquote><p>Note: "Lazy" means the action item has immediate tacit approval, and
it is not necessary to tally the vote until a -1 reply is posted. Once a -1 reply is
posted, the vote must be tallied and reported before the action item is considered
approved. All action-item votes are lazy except for a public release vote.
</p></blockquote>
<h3>Voting Caveats</h3>
<ul>
<!--
<li>A +1 vote regarding product code is only can only be made binding
if the voter has tested the action on their own system(s) equipment.</li>
<li>A binding +1 vote on a public release means the (sub)project's Committer
agrees to provide ongoing support for that release while it is current.</li>
Members who wish to discuss a vote before replying, may open another thread to help avoid premature vetos. Any +/-1's or +/-0's posted to an alternate thread, or any other thread not labeled "[VOTE]", are considered conversational, and do not qualify as an valid action-item vote. A "lazy item" remains subject to lazy approval until a valid -1 reply is posted to the "[VOTE]" thread.
-->
<li>An abstention may have detrimental effects if too many people abstain.</li>
<li>Vetos with no explanation are void. No veto can be overruled. If you disagree with
the veto, you should lobby the person who cast the veto. Voters intending to veto an
action item should make their opinions known to the group immediately so that the
problem can be remedied as early as possible.</li>
<!--
<li>If a Committer believes the explanation for a veto is invalid,
an affirmation of the veto can be requested. If some other
Committer does not affirm that the explanation for the veto is
valid, the veto shall be void.</li>
<li>If a dispute over a veto becomes intractable, the PMC may consent to arbitrate
the matter, and, if appropriate, rescind the veto with a 3/4
majority vote of the PMC members.</li>
-->
<li>Members who wish to discuss a vote before replying, may open another thread to
help avoid premature vetos. Any +/-1's or +/-0's posted to an alternate thread, or
any other thread not labeled "[VOTE]", are considered conversational, and do not
qualify as an valid action-item vote. A "lazy item" remains subject to lazy
approval until a valid -1 reply is posted to the "[VOTE]" thread.</li>
</ul>
<h2>Action Items</h2>
<p> All decisions revolve around "
<em>Action Items.</em>" Action Items consist of the following:
</p>
<ul>
<li><a href="#long_term_plans">Long Term Plans</a></li>
<li><a href="#short_term_plans">Short Term Plans</a></li>
<li><a href="#release_plan">Release Plan</a></li>
<li><a href="#release_testing">Release Testing</a></li>
<li><a href="#public_testing">Public Release</a></li>
<li><a href="#showstoppers">Showstoppers</a></li>
<li><a href="#software_changes">Software Changes</a></li>
</ul>
<h3><a id="long_term_plans">Long Term Plans</a></h3>
<p> Long term plans are simply announcements that group members are working on
particular issues related to the Project. These are not voted on, but Committers who
do not agree with a particular plan, or think that an alternative plan would be better,
are obligated to inform the group of their feelings.
</p>
<h3><a id="short_term_plans">Short Term Plans</a></h3>
<p> Short term plans are announcements that a volunteer is working on a particular set of
documentation or code files with the implication that other volunteers should avoid
them or try to coordinate their changes.
</p>
<h3><a id="release_plan">Release Plan</a></h3>
<p> A release plan is used to keep all volunteers aware of when a release is desired, who
will be the release manager, when the repository will be frozen to create a release,
and other assorted information to keep volunteers from tripping over each other.
Lazy majority decides each issue in a release plan.
</p>
<h3><a id="release_testing">Release Testing</a></h3>
<p> After a new release is built, it must be tested before being released to the public.
The Release Manager will announce that a release is ready for testing.
</p>
<h3><a id="public_release">Public Release</a></h3>
<p>Once the Release Manager determines that testing is complete, and all showstoppers
for the release have been resolved, the Release Manager shall call for a vote on the
public release. Release voting is governed by the
<a href="https://www.apache.org/dev/release.html#approving-a-release">ASF requirements on release voting.</a>
Majority approval is required before the public release can be made.
Voters who approve a public release (vote +1) are expected to provide ongoing
support for that release while it is current. The Release Manager must summarize the
outcome of the vote before the public release becomes final.
</p>
<h3><a id="showstoppers">Showstoppers</a></h3>
<p> Showstoppers are issues that require a fix be in place before the next public
release. They are listed in the project's JIRA tracking system, categorized as
"blockers" in order to focus special attention on
these problems. An issue becomes a showstopper when it is listed as such in the project's
JIRA tracking system and remains so by lazy consensus.
</p>
<h3><a id="software_changes">Software Changes</a></h3>
<p> Changes to the software of the Project, including code and documentation, will
appear as action items in the project's JIRA tracking system. All software changes to the currently active
repository are subject to lazy consensus.
</p>
</blockquote>
</p>
</td></tr>
</table>
</td>
</tr>
<!-- FOOTER -->
<tr><td colspan="2">
<hr noshade="" size="1"/>
</td></tr>
<tr><td colspan="2">
<table class="pageFooter">
<tr>
<td><a href="index.html">Home</a></td>
<td><a href="privacy-policy.html">Privacy Policy</a></td>
<td style="font-size:75%">
Copyright &#169; 2006-2024, The Apache Software Foundation.<br/>
Apache UIMA, UIMA, the Apache UIMA logo and the Apache Feather logo are trademarks of The Apache Software Foundation.<br/>
All other marks mentioned may be trademarks or registered trademarks of their respective owners.
</td>
<td><a href="mailto:dev@uima.apache.org">Contact us</a></td>
</tr>
</table>
</td></tr>
</table>
</body>
</html>