accumulo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bhava...@apache.org
Subject svn commit: r1586324 - in /accumulo/site/branches/redesign14: ./ content/bylaws.mdtext content/doap_Accumulo.rdf content/downloads/index.mdtext content/git.mdtext content/governance/releasing.mdtext content/people.mdtext content/release_notes/1.6.0.mdtext
Date Thu, 10 Apr 2014 15:01:48 GMT
Author: bhavanki
Date: Thu Apr 10 15:01:47 2014
New Revision: 1586324

URL: http://svn.apache.org/r1586324
Log:
Merged 1579719:1586319 of trunk into redesign14 branch.

Added:
    accumulo/site/branches/redesign14/content/release_notes/1.6.0.mdtext
      - copied unchanged from r1586319, accumulo/site/trunk/content/release_notes/1.6.0.mdtext
Modified:
    accumulo/site/branches/redesign14/   (props changed)
    accumulo/site/branches/redesign14/content/bylaws.mdtext
    accumulo/site/branches/redesign14/content/doap_Accumulo.rdf
    accumulo/site/branches/redesign14/content/downloads/index.mdtext
    accumulo/site/branches/redesign14/content/git.mdtext
    accumulo/site/branches/redesign14/content/governance/releasing.mdtext
    accumulo/site/branches/redesign14/content/people.mdtext

Propchange: accumulo/site/branches/redesign14/
------------------------------------------------------------------------------
  Merged /accumulo/site/trunk:r1579719-1586319

Modified: accumulo/site/branches/redesign14/content/bylaws.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/branches/redesign14/content/bylaws.mdtext?rev=1586324&r1=1586323&r2=1586324&view=diff
==============================================================================
--- accumulo/site/branches/redesign14/content/bylaws.mdtext (original)
+++ accumulo/site/branches/redesign14/content/bylaws.mdtext Thu Apr 10 15:01:47 2014
@@ -16,7 +16,7 @@ Notice:    Licensed to the Apache Softwa
            specific language governing permissions and limitations
            under the License.
 
-This is version 0 of the bylaws. This draft has not yet been accepted by the Accumulo Project
and only exists for voting purposes.
+This is version 1 of the bylaws. Community work actively continues on the bylaws, and so
key segments of them are subject to change.
 
 # Introduction
 
@@ -42,9 +42,9 @@ All of the volunteers who are contributi
 
 ## Committers
 
-The project's committers are responsible for the project's technical management. Committers
have write access to the project's code repositories and may cast binding votes on any technical
discussion regarding Accumulo. Committer access is by invitation only and must be approved
by consensus approval of the active PMC members. Upon acceptance of the invitation to become
a committer, it is the accepting member’s responsibility to update his/her status on
the Accumulo web page accordingly.
+The project's committers are responsible for the project's technical management. Committers
have write access to the project's code repositories and may cast binding votes on any technical
discussion regarding Accumulo. Committer access is by invitation only and must be approved
by consensus approval of the active PMC members. Upon acceptance of the invitation to become
a committer, it is the accepting member’s responsibility to update their status on the
Accumulo web page accordingly.
 
-A committer is considered emeritus, meaning inactive, by his or her own declaration or by
not reviewing patches or committing patches to the project for over six months. Emeritus members
will be recognized by the PMC on the Accumulo web page, in honor of their past contributions.
Emeritus members retain all voting and commit rights associated with their former designation
and can move themselves out of emeritus status by sending an announcement of their return
to the developer mailing list. It will be the returning member's responsibility to update
his/her status on the web page accordingly.
+A committer is considered emeritus, meaning inactive, by their own declaration or by not
reviewing patches or committing patches to the project for over six months. Emeritus members
will be recognized by the PMC on the Accumulo web page, in honor of their past contributions.
Emeritus members retain all voting and commit rights associated with their former designation
and can move themselves out of emeritus status by sending an announcement of their return
to the developer mailing list. It will be the returning member's responsibility to update
their status on the web page accordingly.
 
 An emeritus committer’s commit access may be disabled as part of routine security. Access
shall not be removed without notifying the committer, and access shall be maintained if the
committer wishes to leave it active. A committer’s commit access shall be reactivated
upon the committer’s request to the PMC.
 
@@ -71,16 +71,17 @@ The responsibilities of the PMC include:
 
 * Deciding what is distributed as products of the Apache Accumulo project.
 * Maintaining the project's shared resources, including the code repository, mailing lists,
and websites.
+* Protecting and ensuring proper use of Apache trademarks by the project and by other parties.
 * Speaking on behalf of the project.
-* Resolving license disputes regarding products of the project.
 * Nominating new PMC members and committers.
 * Maintaining these bylaws and other guidelines of the project.
 
 In particular, PMC members must understand both our project's criteria and ASF criteria for
voting on a [release](http://www.apache.org/dev/release.html#management).
+See the [PMC Guide](http://www.apache.org/dev/pmc.html) for more information on PMC responsibilities.
 
-Membership of the PMC is by invitation only and must be approved by a consensus approval
of active PMC members. Upon acceptance of the invitation to become a PMC member, it is the
accepting member’s responsibility to update his/her status on the Accumulo web page accordingly.
+Membership of the PMC is by invitation only and must be approved by a consensus approval
of active PMC members. Upon acceptance of the invitation to become a PMC member, it is the
accepting member’s responsibility to update their status on the Accumulo web page accordingly.
 
-A PMC member is considered emeritus, meaning inactive, by his or her own declaration or by
not contributing in any form to the project for over six months. Emeritus members will be
recognized by the PMC on the Accumulo web page, in honor of their past contributions. Emeritus
members retain all voting and commit rights associated with their former designation and can
move themselves out of emeritus status by sending an announcement of their return to the developer
mailing list. It will be the returning member's responsibility to update his/her status on
the web page accordingly.
+A PMC member is considered emeritus, meaning inactive, by their own declaration or by not
contributing in any form to the project for over six months. Emeritus members will be recognized
by the PMC on the Accumulo web page, in honor of their past contributions. Emeritus members
retain all voting and commit rights associated with their former designation and can move
themselves out of emeritus status by sending an announcement of their return to the developer
mailing list. It will be the returning member's responsibility to update their status on the
web page accordingly.
 
 The chair of the PMC is appointed by the ASF board. The chair is an office holder of the
Apache Software Foundation (Vice President, Apache Accumulo) and has primary responsibility
to the board for the management of the projects within the scope of the Accumulo PMC. The
chair reports to the board quarterly on developments within the Accumulo project.
 
@@ -99,7 +100,7 @@ At a minimum, a release manager is respo
 * determine if a re-plan may be needed and, if so, call a vote
 * call votes on release candidates
 
-[Release guidelines](http://accumulo.apache.org/releasing.html) and [details on the mechanics
of creating an Accumulo release](http://accumulo.apache.org/releasing.html) are available
on the Accumulo project site.
+[Release guidelines](http://accumulo.apache.org/governance/releasing.html) and [details on
the mechanics of creating an Accumulo release](http://accumulo.apache.org/releasing.html)
are available on the Accumulo project site.
 
 # Decision Making
 
@@ -128,7 +129,7 @@ Voting can also be applied to changes to
 
 ## Approvals
 
-There are the types of approvals that can be sought. Different actions require different
types of approvals.
+These are the types of approvals that can be sought. Different actions require different
types of approvals.
 
 <table>
 <tr><th>Approval Type</th>
@@ -145,11 +146,11 @@ There are the types of approvals that ca
 
 A valid, binding veto cannot be overruled. If a veto is cast, it must be accompanied by a
valid reason explaining the veto. The validity of a veto, if challenged, can be confirmed
by anyone who has a binding vote. This does not necessarily signify agreement with the veto,
but merely that the veto is valid.
 
-If you disagree with a valid veto, you must lobby the person casting the veto to withdraw
his or her veto. If a veto is not withdrawn, the action that has been vetoed must be reversed
in a timely manner.
+If you disagree with a valid veto, you must lobby the person casting the veto to withdraw
their veto. If a veto is not withdrawn, the action that has been vetoed must be reversed in
a timely manner.
 
 ## Actions
 
-This section describes the various actions which are undertaken within the project, the corresponding
approval required for that action and those who have binding votes over the action. It also
specifies the minimum length of time that a vote must remain open, measured in days. In general
votes should not be called at times when it is known that interested members of the project
will be unavailable.
+This section describes the various actions which are undertaken within the project, the corresponding
approval required for that action and those who have binding votes over the action. It also
specifies the minimum length of time that a vote must remain open, measured in days. In general,
votes should not be called at times when it is known that interested members of the project
will be unavailable.
 
 <table>
 <tr><th>Action</th>
@@ -192,6 +193,11 @@ This section describes the various actio
     <td>Consensus approval</td>
     <td>Active PMC members</td>
     <td>3</td>
+<tr><td>New PMC Chair</td>
+    <td>When a new PMC chair is chosen to succeed an outgoing chair.</td>
+    <td>Consensus approval</td>
+    <td>Active PMC members</td>
+    <td>3</td>
 <tr><td>Modifying Bylaws</td>
     <td>Modifying this document.</td>
     <td>Majority approval</td>
@@ -199,11 +205,11 @@ This section describes the various actio
     <td>7</td>
 </table>
 
-No other voting actions are defined. If a new one is found to be needed, it should be added
to these bylaws.
+No other voting actions are defined; all other actions should presume Lazy Approval (defaulting
to Consensus Approval upon veto). If an action is voted on multiple times, or if a different
approval type is desired, these bylaws should be amended to include the action.
 
 For the purposes of the "Adoption of New Codebase" action, the Accumulo codebase is defined
as the Accumulo site content, primary project code, and all contributed code ("contribs")
as they exist in their respective repositories. Adoption of a new codebase generally refers
to the creation of a new contrib repository, but could cover, for example, a rework of the
project site, or merging a contrib project into the primary codebase.
 
-Voting actions for the removal of a committer or PMC member are intentionally not defined.
According to ASF rules, [committer status never expires](http://www.apache.org/dev/committers.html#committer-set-term)
and [the ASF board removes PMC members](http://www.apache.org/dev/pmc.html#pmc-removal).
+Voting actions for the removal of a committer or PMC member are intentionally not defined.
According to ASF rules, [committer status never expires](http://www.apache.org/dev/committers.html#committer-set-term)
and [PMC members can only be removed with approval from the ASF Board](http://www.apache.org/dev/pmc.html#pmc-removal).
 
 # Release Plans
 

Modified: accumulo/site/branches/redesign14/content/doap_Accumulo.rdf
URL: http://svn.apache.org/viewvc/accumulo/site/branches/redesign14/content/doap_Accumulo.rdf?rev=1586324&r1=1586323&r2=1586324&view=diff
==============================================================================
--- accumulo/site/branches/redesign14/content/doap_Accumulo.rdf (original)
+++ accumulo/site/branches/redesign14/content/doap_Accumulo.rdf Thu Apr 10 15:01:47 2014
@@ -41,8 +41,8 @@
       </Version>
       <Version>
         <name>Apache Accumulo</name>
-        <created>2013-08-23</created>
-        <revision>1.4.4</revision>
+        <created>2014-04-03</created>
+        <revision>1.4.5</revision>
       </Version>
       <Version>
         <name>Apache Accumulo</name>

Modified: accumulo/site/branches/redesign14/content/downloads/index.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/branches/redesign14/content/downloads/index.mdtext?rev=1586324&r1=1586323&r2=1586324&view=diff
==============================================================================
--- accumulo/site/branches/redesign14/content/downloads/index.mdtext (original)
+++ accumulo/site/branches/redesign14/content/downloads/index.mdtext Thu Apr 10 15:01:47 2014
@@ -43,13 +43,13 @@ For convenience, [MD5][22] and [SHA1][23
   * <a href=/1.5/apidocs onClick="javascript: _gaq.push(['_trackPageview', '/1.5/apidocs']);">javadoc</a>
   * [examples][32]
 
-## 1.4.4 (stable)
-The most recent 1.4 release is 1.4.4.  See the [Release Notes][12].  
+## 1.4.5 (stable)
+The most recent 1.4 release is 1.4.5.  See the [Release Notes][12].  
 Be sure to verify your downloads by these [procedures][1] using these [KEYS][2].
 
-  * Download Binaries: accumulo-1.4.4-dist.tar.gz <a href=http://www.apache.org/dyn/closer.cgi/accumulo/1.4.4/accumulo-1.4.4-dist.tar.gz
onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.4.4-dist.tar.gz']);">mirrors</a>
([asc][16], [md5][17], [sha][18])
-  * Download Source: accumulo-1.4.4-src.tar.gz <a href=http://www.apache.org/dyn/closer.cgi/accumulo/1.4.4/accumulo-1.4.4-src.tar.gz
onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.4.4-src.tar.gz']);">mirrors</a>
([asc][13], [md5][14], [sha][15])
-  * Read Documentation: <a href="https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=README;hb=419aacc45279a3cd6b3b5bf61baf486f082a450a"
onClick="javascript: _gaq.push(['_trackPageview', '/1.4/README']);">README</a>, [html
manual][19], <a href=/1.4/accumulo_user_manual.pdf onClick="javascript: _gaq.push(['_trackPageview',
'/1.4/accumulo_user_manual.pdf']);">pdf manual</a>, [examples][20]
+  * Download Binaries: accumulo-1.4.5-dist.tar.gz <a href=http://www.apache.org/dyn/closer.cgi/accumulo/1.4.5/accumulo-1.4.5-dist.tar.gz
onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.4.5-dist.tar.gz']);">mirrors</a>
([asc][16], [md5][17], [sha][18])
+  * Download Source: accumulo-1.4.5-src.tar.gz <a href=http://www.apache.org/dyn/closer.cgi/accumulo/1.4.5/accumulo-1.4.5-src.tar.gz
onClick="javascript: _gaq.push(['_trackPageview', '/downloads/accumulo-1.4.5-src.tar.gz']);">mirrors</a>
([asc][13], [md5][14], [sha][15])
+  * Read Documentation: <a href="https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=README;hb=f7d87b6e407de6597b6c0ca60ca1b6a321faf237"
onClick="javascript: _gaq.push(['_trackPageview', '/1.4/README']);">README</a>, [html
manual][19], <a href=/1.4/accumulo_user_manual.pdf onClick="javascript: _gaq.push(['_trackPageview',
'/1.4/accumulo_user_manual.pdf']);">pdf manual</a>, [examples][20]
 
 ## 1.3.6
 The most recent 1.3 release is 1.3.6.  See the [Release Notes][3].  
@@ -69,13 +69,13 @@ Be sure to verify your downloads by thes
 [10]: http://www.apache.org/dist/accumulo/1.3.6/accumulo-1.3.6-dist.tar.gz.md5   "1.3.6 dist
md5"
 [11]: http://www.apache.org/dist/accumulo/1.3.6/accumulo-1.3.6-dist.tar.gz.sha   "1.3.6 dist
sha"
 
-[12]: https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=CHANGES;hb=419aacc45279a3cd6b3b5bf61baf486f082a450a
  "1.4.4 Release Notes"
-[13]: http://www.apache.org/dist/accumulo/1.4.4/accumulo-1.4.4-src.tar.gz.asc   "1.4.4 src
asc"
-[14]: http://www.apache.org/dist/accumulo/1.4.4/accumulo-1.4.4-src.tar.gz.md5   "1.4.4 src
md5"
-[15]: http://www.apache.org/dist/accumulo/1.4.4/accumulo-1.4.4-src.tar.gz.sha   "1.4.4 src
sha"
-[16]: http://www.apache.org/dist/accumulo/1.4.4/accumulo-1.4.4-dist.tar.gz.asc   "1.4.4 dist
asc"
-[17]: http://www.apache.org/dist/accumulo/1.4.4/accumulo-1.4.4-dist.tar.gz.md5   "1.4.4 dist
md5"
-[18]: http://www.apache.org/dist/accumulo/1.4.4/accumulo-1.4.4-dist.tar.gz.sha   "1.4.4 dist
sha"
+[12]: https://git-wip-us.apache.org/repos/asf?p=accumulo.git;a=blob_plain;f=CHANGES;hb=f7d87b6e407de6597b6c0ca60ca1b6a321faf237
  "1.4.5 Release Notes"
+[13]: http://www.apache.org/dist/accumulo/1.4.5/accumulo-1.4.5-src.tar.gz.asc   "1.4.5 src
asc"
+[14]: http://www.apache.org/dist/accumulo/1.4.5/accumulo-1.4.5-src.tar.gz.md5   "1.4.5 src
md5"
+[15]: http://www.apache.org/dist/accumulo/1.4.5/accumulo-1.4.5-src.tar.gz.sha   "1.4.5 src
sha"
+[16]: http://www.apache.org/dist/accumulo/1.4.5/accumulo-1.4.5-dist.tar.gz.asc   "1.4.5 dist
asc"
+[17]: http://www.apache.org/dist/accumulo/1.4.5/accumulo-1.4.5-dist.tar.gz.md5   "1.4.5 dist
md5"
+[18]: http://www.apache.org/dist/accumulo/1.4.5/accumulo-1.4.5-dist.tar.gz.sha   "1.4.5 dist
sha"
 [19]: /1.4/user_manual
 [20]: /1.4/examples
 

Modified: accumulo/site/branches/redesign14/content/git.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/branches/redesign14/content/git.mdtext?rev=1586324&r1=1586323&r2=1586324&view=diff
==============================================================================
--- accumulo/site/branches/redesign14/content/git.mdtext (original)
+++ accumulo/site/branches/redesign14/content/git.mdtext Thu Apr 10 15:01:47 2014
@@ -114,7 +114,7 @@ explanation is clear.
 
 Use the following steps, original derived from Apache Kafka's [simple
 contributor
-workflow](https://cwiki.apache.org/confluence/display/KAFKA/Git+Workflow#GitWorkflow-Simplecontributorworkflow).
+workflow][1].
 
 To be specific, let's consider a contributor wanting to work on a fix for the
 Jira issue ACCUMULO-12345 that affects 1.5.0 release.
@@ -133,25 +133,43 @@ Jira issue ACCUMULO-12345 that affects 1
     `git fetch && git fetch --tags`
 
 4. For the given issue you intend to work on, choose the 'lowest' fixVersion
-   and create a branch for yourself to work in.
+   and create a branch for yourself to work in. This example is against fixVersion 1.5.2.
 
-    `git checkout -b ACCUMULO-12345-my-work origin/1.5.1-SNAPSHOT`
+    `git checkout -b ACCUMULO-12345-my-work origin/1.5.2-SNAPSHOT`
 
 5. Make commits as you see fit as you fix the issue, referencing the issue name
    in the commit message:
 
     `git commit -av`
 
+    Please include the ticket number at the beginning of the log message, and
+    in the first line, as it's easier to parse quickly. For example:
+
+    `ACCUMULO-2428 throw exception when rename fails after compaction`
+
+    Consider following the git log message format described in
+    [Zach Holman's talk](http://zachholman.com/talk/more-git-and-github-secrets/)
+    (specifically slides 78-98, beginning at 15:20 into the video). Essentially,
+    leave a short descriptive message in the first line, skip a line, and write
+    more detailed stuff there, if you need to. For example:
+
+    `ACCUMULO-2194 Add delay for randomwalk Security teardown`
+
+    `If two Security randomwalk tests run back-to-back, the second test may see that the
+    table user still exists even though it was removed when the first test was torn down.
+    This can happen if the user drop does not propagate through Zookeeper quickly enough.
+    This commit adds a delay to the end of the Security test to give ZK some time.`
+
 6. Assuming others are developing against the version you also are, as you
    work, or before you create your patch, rebase your branch against the remote
-   to lift your changes to the top of your branch.
+   to lift your changes to the top of your branch. The branch specified here should be the
same one you used in step 4.
 
-    `git pull --rebase origin 1.5.1-SNAPSHOT`
+    `git pull --rebase origin 1.5.2-SNAPSHOT`
 
 7. At this point, you can create a patch file from the upstream branch to
-   attach to the ACCUMULO-12345 Jira issue.
+   attach to the ACCUMULO-12345 Jira issue. The branch specified here should be teh same
one you used in step 4.
 
-    `git format-patch 1.5.1-SNAPSHOT --stdout > ACCUMULO-12345.patch`
+    `git format-patch --stdout origin/1.5.2-SNAPSHOT > ACCUMULO-12345.patch`
 
 An alternative to creating a patch is submitting a request to pull your changes
 from some repository, e.g. Github. Please include the repository and branch
@@ -486,3 +504,4 @@ For the sake of clarity, some examples o
 
     `git checkout 1.6.1-SNAPSHOT && git merge 1.5.1-SNAPSHOT`
 
+ [1]: https://cwiki.apache.org/confluence/display/KAFKA/Patch+submission+and+review#Patchsubmissionandreview-Simplecontributorworkflow
\ No newline at end of file

Modified: accumulo/site/branches/redesign14/content/governance/releasing.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/branches/redesign14/content/governance/releasing.mdtext?rev=1586324&r1=1586323&r2=1586324&view=diff
==============================================================================
--- accumulo/site/branches/redesign14/content/governance/releasing.mdtext (original)
+++ accumulo/site/branches/redesign14/content/governance/releasing.mdtext Thu Apr 10 15:01:47
2014
@@ -62,15 +62,15 @@ The following steps can be taken without
     - Use "mvn -Dhadoop.profile=1 verify" to run the functional tests against the Hadoop
1 profile
 
 ### Cluster based
-The following tests require a Hadoop cluster running a minimum of HDFS, MapReduce, and ZooKeeper.
The cluster MAY have any number of worker nodes; it can even be a single node in psuedo-distributed
mode. A cluster with multiple tablet servers SHOULD be used so that more of the code base
will be exercised. For the purposes of release testing, you should note the number of nodes
and versions used. See the Releasing section for more details.
+The following tests require a Hadoop cluster running a minimum of HDFS, MapReduce, and ZooKeeper.
The cluster MAY have any number of worker nodes; it can even be a single node in pseudo-distributed
mode. A cluster with multiple tablet servers SHOULD be used so that more of the code base
will be exercised. For the purposes of release testing, you should note the number of nodes
and versions used. See the Releasing section for more details.
 
   1. For versions prior to 1.6, all functional tests must complete successfully.
     - See $ACCUMULO_HOME/test/system/auto/README for details on running the functional tests.
-  - Two 24-hour periods of the randomwalk LongClean test with and without agitation need
to be run successfully.
+  - Two 24-hour periods of the LongClean module of the RandomWalk test need to be run successfully.
One of them must use agitation and the other should not.
     - See $ACCUMULO_HOME/test/system/randomwalk/README for details on running the LongClean
module.
-  - Two 24-hour periods of continuous ingest with and without agitation need to be validated
successfully.
-    - See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying
the continous ingest test.
-  - Two 72-hour periods of continuous ingest with and without agitation. No validation is
necessary but the cluster should be checked to ensure it is still functional.
+  - Two 24-hour periods of the continuous ingest test must be validated successfully. One
test period must use agitation and the other should not.
+    - See $ACCUMULO_HOME/test/system/continuous/README for details on running and verifying
the continuous ingest test.
+  - Two 72-hour periods of continuous ingest must run. One test period must use agitation
and the other should not. No validation is necessary but the cluster should be checked to
ensure it is still functional.
 
 ## Releasing
 

Modified: accumulo/site/branches/redesign14/content/people.mdtext
URL: http://svn.apache.org/viewvc/accumulo/site/branches/redesign14/content/people.mdtext?rev=1586324&r1=1586323&r2=1586324&view=diff
==============================================================================
--- accumulo/site/branches/redesign14/content/people.mdtext (original)
+++ accumulo/site/branches/redesign14/content/people.mdtext Thu Apr 10 15:01:47 2014
@@ -76,7 +76,9 @@ Contributors
 <table>
   <tr><th>username</th><th>name</th><th>organization</th><th>timezone</th></tr>
   <tr><td></td><td>Aaron Glahe</td><td><a href=http://www.data-tactics.com/>Data
Tatics</a></td><td>ET (<a href=http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5</a>
/ <a href=http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4</a>)</td></tr>
+  <tr><td></td><td>Al Krinker</td><td></td><td>ET
(<a href=http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5</a>
/ <a href=http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4</a>)</td></tr>
   <tr><td></td><td>Alex Moundalexis</td><td><a href="http://www.cloudera.com">Cloudera</a></td><td>ET
(<a href=http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5</a>
/ <a href=http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4</a>)</td></tr>
+  <tr><td></td><td>Andrew George Wells</td><td><a
href="http://clearedgeit.com/">ClearEdgeIT</a></td><td>ET (<a href=http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5</a>
/ <a href=http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4</a>)</td></tr>
   <tr><td></td><td>Arshak Navruzyan</td><td><a href="http://www.argyledata.com/">Argyle
Data</a></td><td></td></tr>
   <tr><td></td><td>Chris Bennight</td><td></td><td></td></tr>
   <tr><td></td><td>Chris McCubbin</td><td><a href=http://sqrrl.com/>sqrrl</a></td><td>ET
(<a href=http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5</a>
/ <a href=http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4</a>)</td></tr>
@@ -106,6 +108,7 @@ Contributors
   <tr><td></td><td>Michael Berman</td><td><a href=http://sqrrl.com/>sqrrl</a></td><td>ET
(<a href=http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5</a>
/ <a href=http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4</a>)</td></tr>
   <tr><td></td><td>Michael Wall</td><td></td><td></td></tr>
   <tr><td></td><td>Miguel Pereira</td><td><a href="http://sra.com">SRA
International, Inc</a></td><td>ET (<a href=http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5</a>
/ <a href=http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4</a>)</td></tr>
+  <tr><td></td><td>Mike Fagan</td><td><a href="http://www.arcus-research.com">Arcus
Research</a></td><td>MT (<a href="http://www.timeanddate.com/library/abbreviations/timezones/na/mst.html">-7</a>
/ <a href="http://www.timeanddate.com/library/abbreviations/timezones/na/mdt.html">-6</a>)</td></tr>
   <tr><td></td><td>Morgan Haskel</td><td></td><td></td></tr>
   <tr><td></td><td>Nguessan Kouame</td><td></td><td></td></tr>
   <tr><td></td><td>Oren Falkowitz</td><td><a href=http://sqrrl.com/>sqrrl</a></td><td>ET
(<a href=http://www.timeanddate.com/library/abbreviations/timezones/na/est.html>-5</a>
/ <a href=http://www.timeanddate.com/library/abbreviations/timezones/na/edt.html>-4</a>)</td></tr>



Mime
View raw message