You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@community.apache.org by gi...@apache.org on 2020/12/09 19:24:24 UTC
[comdev-site] branch asf-site updated: Updated asf-site from master
at d474c4bb76b7a5643ec976013267a1b1d2144dbd using
https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/61/
This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/comdev-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new b5fc6e3 Updated asf-site from master at d474c4bb76b7a5643ec976013267a1b1d2144dbd using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/61/
b5fc6e3 is described below
commit b5fc6e39d98ad0f62fd90b9c25a280e0e4618bbb
Author: jenkins <bu...@apache.org>
AuthorDate: Wed Dec 9 19:24:18 2020 +0000
Updated asf-site from master at d474c4bb76b7a5643ec976013267a1b1d2144dbd using https://ci-builds.apache.org/job/Community%20Development/job/site/job/master/61/
---
content/committers/index.xml | 4 ++--
content/committers/voting.html | 24 ++++++++++++------------
content/index.xml | 4 ++--
content/sitemap.xml | 4 ++--
4 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/content/committers/index.xml b/content/committers/index.xml
index 880d424..64579cd 100644
--- a/content/committers/index.xml
+++ b/content/committers/index.xml
@@ -69,8 +69,8 @@ If you have any question about this, feel free to ask on our dev@community.</des
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/committers/voting.html</guid>
- <description>Occasionally a &ldquo;feel&rdquo; for consensus is not enough. Sometimes we need to have a measurable consensus. For example, when voting in new committers or to approve a release.
-Preparing for a Vote Before calling a vote it is important to ensure that the community is given time to discuss the upcoming vote. This will be done by posting an email to the list indicating the intention to call a vote and the options available.</description>
+ <description>Occasionally a &ldquo;feel&rdquo; for consensus is not enough. Sometimes we need to have a measurable consensus, for example, when voting to invite new committers or to approve a release.
+Preparing for a Vote Before calling a vote it is important to ensure that the community has time to discuss the issue before voting. To do this, post an email to the list indicating the intention to call a vote and the options available.</description>
</item>
</channel>
diff --git a/content/committers/voting.html b/content/committers/voting.html
index 5c6d2e6..85fdbac 100644
--- a/content/committers/voting.html
+++ b/content/committers/voting.html
@@ -7,12 +7,12 @@
<meta name="keywords" content="apache, apache community, community development, opensource"/>
<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1" />
<meta property="og:title" content="Voting" />
-<meta property="og:description" content="Occasionally a “feel” for consensus is not enough. Sometimes we need to have a measurable consensus. For example, when voting in new committers or to approve a release.
-Preparing for a Vote Before calling a vote it is important to ensure that the community is given time to discuss the upcoming vote. This will be done by posting an email to the list indicating the intention to call a vote and the options available." />
+<meta property="og:description" content="Occasionally a “feel” for consensus is not enough. Sometimes we need to have a measurable consensus, for example, when voting to invite new committers or to approve a release.
+Preparing for a Vote Before calling a vote it is important to ensure that the community has time to discuss the issue before voting. To do this, post an email to the list indicating the intention to call a vote and the options available." />
<meta property="og:type" content="article" />
<meta property="og:url" content="https://community.apache.org/committers/voting.html" />
<meta property="og:image" content="https://community.apache.org/images/aceu19_1.jpg"/>
-<meta property="article:modified_time" content="2020-03-24T15:03:46+01:00" /><meta property="og:site_name" content="Apache Community Development" />
+<meta property="article:modified_time" content="2020-12-04T09:58:51-04:00" /><meta property="og:site_name" content="Apache Community Development" />
<title>Apache Community Development - Voting</title>
@@ -191,23 +191,23 @@ Preparing for a Vote Before calling a vote it is important to ensure that the co
<hr>
<p>Occasionally a “feel” for consensus is not enough. Sometimes we need to
-have a measurable consensus. For example, when voting in new committers or
+have a measurable consensus, for example, when voting to invite new committers or
to approve a release.</p>
<h2 id="preparing-for-a-vote">Preparing for a Vote</h2>
-<p>Before calling a vote it is important to ensure that the community is given time to
-discuss the upcoming vote. This will be done by posting an email to the list
+<p>Before calling a vote it is important to ensure that the community has time to
+discuss the issue before voting. To do this, post an email to the list
indicating the intention to call a vote and the options available. By the time
-a vote is called there should already be <a href="/committers/consensusBuilding.mdtext">consensus in the community</a>. The vote
-itself is, normally, a formality.</p>
+a vote takes place there usually is <a href="/committers/consensusBuilding.mdtext">consensus in the community</a> on what path to take. The vote
+itself is, normally, a formality; however, it is important as part of the record of the decisions of the PMC and the development of the project.</p>
<h2 id="calling-a-vote">Calling a Vote</h2>
-<p>Once it is time to call the vote a mail is posted with a subject starting
-with <strong>[VOTE]</strong>. This enables the community members to ensure they do not miss
-an important vote thread. It also indicates that this is not consensus building
+<p>Once it is time to call the vote, the proposer or a member of the PMC posts an email with the subject line starting
+with <strong>[VOTE]</strong>. This helps community members not miss
+an important vote thread. It also indicates that this is not a consensus-building conversation
but a formal vote.</p>
<h3 id="casting-your-vote">Casting Your Vote</h3>
<p>The notation used in voting is:</p>
<ul>
-<li>+1 Yes I agree</li>
+<li>+1 Yes, I agree</li>
<li>0 I have no strong opinion</li>
<li>-1 I object on the following grounds</li>
</ul>
diff --git a/content/index.xml b/content/index.xml
index 9695d9f..ffd4e06 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -510,8 +510,8 @@ Finding Speakers You can use our &ldquo;Find People&rdquo; application t
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<guid>https://community.apache.org/committers/voting.html</guid>
- <description>Occasionally a &ldquo;feel&rdquo; for consensus is not enough. Sometimes we need to have a measurable consensus. For example, when voting in new committers or to approve a release.
-Preparing for a Vote Before calling a vote it is important to ensure that the community is given time to discuss the upcoming vote. This will be done by posting an email to the list indicating the intention to call a vote and the options available.</description>
+ <description>Occasionally a &ldquo;feel&rdquo; for consensus is not enough. Sometimes we need to have a measurable consensus, for example, when voting to invite new committers or to approve a release.
+Preparing for a Vote Before calling a vote it is important to ensure that the community has time to discuss the issue before voting. To do this, post an email to the list indicating the intention to call a vote and the options available.</description>
</item>
<item>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index c7550af..265ad34 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -89,7 +89,7 @@
<url>
<loc>https://community.apache.org/committers.html</loc>
- <lastmod>2020-12-02T10:18:35-04:00</lastmod>
+ <lastmod>2020-12-04T09:58:51-04:00</lastmod>
</url>
<url>
@@ -298,7 +298,7 @@
<url>
<loc>https://community.apache.org/committers/voting.html</loc>
- <lastmod>2020-03-24T15:03:46+01:00</lastmod>
+ <lastmod>2020-12-04T09:58:51-04:00</lastmod>
</url>
<url>