incubator-odf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From w...@apache.org
Subject svn commit: r1160503 [1/2] - in /incubator/odf/site/trunk: ./ cgi-bin/ content/ content/odftoolkit/ content/odftoolkit/css/ content/odftoolkit/docs/ content/odftoolkit/docs/governance/ content/odftoolkit/images/ lib/ templates/
Date Mon, 22 Aug 2011 23:48:05 GMT
Author: wave
Date: Mon Aug 22 23:48:04 2011
New Revision: 1160503

URL: http://svn.apache.org/viewvc?rev=1160503&view=rev
Log:
Basic website copied from AOOo podling. No logo yet.

Added:
    incubator/odf/site/trunk/
    incubator/odf/site/trunk/cgi-bin/
    incubator/odf/site/trunk/content/
    incubator/odf/site/trunk/content/odftoolkit/
    incubator/odf/site/trunk/content/odftoolkit/community-faqs.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/contact.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/css/
    incubator/odf/site/trunk/content/odftoolkit/developer-faqs.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/docs/
    incubator/odf/site/trunk/content/odftoolkit/docs/edit-cms.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/docs/governance/
    incubator/odf/site/trunk/content/odftoolkit/docs/governance/consensusBuilding.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/docs/governance/lazyConsensus.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/docs/governance/voting.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/get-involved.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/images/
    incubator/odf/site/trunk/content/odftoolkit/images/apache-incubator-logo.png   (with props)
    incubator/odf/site/trunk/content/odftoolkit/images/feather-small.gif   (with props)
    incubator/odf/site/trunk/content/odftoolkit/index.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/license.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/mailing-lists.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/people.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/ppmc-faqs.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/release-process.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/source.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/svn-basics.mdtext   (with props)
    incubator/odf/site/trunk/content/odftoolkit/website-local.mdtext   (with props)
    incubator/odf/site/trunk/lib/
    incubator/odf/site/trunk/lib/path.pm   (with props)
    incubator/odf/site/trunk/lib/view.pm   (with props)
    incubator/odf/site/trunk/templates/
    incubator/odf/site/trunk/templates/html_page.html   (with props)
    incubator/odf/site/trunk/templates/sidenav.mdtext   (with props)
    incubator/odf/site/trunk/templates/single_narrative.html   (with props)
    incubator/odf/site/trunk/templates/skeleton.html   (with props)

Added: incubator/odf/site/trunk/content/odftoolkit/community-faqs.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/community-faqs.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/community-faqs.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/community-faqs.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,20 @@
+Title: Community FAQs
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+
+

Propchange: incubator/odf/site/trunk/content/odftoolkit/community-faqs.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/contact.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/contact.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/contact.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/contact.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,28 @@
+Title: Contact Us
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+For any questions, comments, or concerns about this project or website please contact the project on the developer mailing list:
+
+  - [odf-dev@incubator.apache.org][1].
+
+For private or legal matters, please contact the Podling Project Management Committee (PPMC):
+
+  - [odf-private@incubator.apache.org][2].
+
+  [1]:  mailto:ooo-dev@incubator.apache.org
+  [2]:  mailto:ooo-private@incubator.apache.org

Propchange: incubator/odf/site/trunk/content/odftoolkit/contact.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/developer-faqs.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/developer-faqs.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/developer-faqs.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/developer-faqs.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,68 @@
+Title: Developer FAQs
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+##How do I edit this website?
+
+The pages on this website are written in [markdown syntax][1] and stored in SVN at 
+[https://svn.apache.org/repos/asf/incubator/odf/site][2]
+
+Via integration with the Apache CMS, it is possible to edit, stage and publish 
+website updates from the command line, or by using a web-based interface.
+
+Detailed information can be found in the [How to edit the ODF website][3] page.
+
+Information on deeper website development is found on the [Website Development][10] page.
+
+##I've just been voted in as a Committer.  What do I need to do?
+
+First, congratulations.  Your contributions to the project have been noted and we 
+hope that as a Committer you will be even more active.
+
+But before you are officially given Committer permissions, there are a few 
+administrative steps that you will need to complete. 
+
+ 1. Submit a signed [ICLA] [4] to Apache.
+ 1. Wait for the ICLA to be received and recorded by Apache.  You will know 
+when this has occurred when your name appears in the [Unlisted ICLAs] [5] section 
+on the Apache Committers page.  This could take a couple of days, longer if you
+submitted the ICLA via post.
+ 1. Once the your ICLA has been recorded, you should send a note to the [PPMC] [6] 
+and request an Apache account.  You will want to include your full name and email address, 
+as you entered in the ICLA, as well as your preferred userid.  Please [check first] [7] 
+that your preferred userid is not already in use by another Apache Committer.
+ 1. Once your Apache account has been created, you will receive an email with
+further instructions for setting up your account.  This may take a couple of days.
+ 1. If you were also voted as a PPMC member, you should then [subscribe] [8] to the 
+PPMC's private mailing list.
+ 1. Finally, you should read the ["Guide for new committers"] [9]
+
+##How do I use Apache Subversion?
+
+Instructions can be found on the [Subversion Basics] [11] page.
+
+  [1]: http://www.simpleeditions.com/59001/markdown-an-introduction
+  [2]: https://svn.apache.org/repos/asf/incubator/odf/site
+  [3]: http://incubator.apache.org/odftoolkit/docs/edit-cms.html
+  [4]: http://www.apache.org/licenses/icla.txt
+  [5]: http://people.apache.org/committer-index.html#unlistedclas
+  [6]: mailto:odf-private@incubator.apache.org
+  [7]: http://people.apache.org/committer-index.html
+  [8]: mailto:odf-private-subscribe@incubator.apache.org
+  [9]: http://www.apache.org/dev/new-committers-guide.html
+  [10]: website-local.html
+  [11]: http://incubator.apache.org/odftoolkit/svn-basics.html
\ No newline at end of file

Propchange: incubator/odf/site/trunk/content/odftoolkit/developer-faqs.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/docs/edit-cms.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/docs/edit-cms.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/docs/edit-cms.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/docs/edit-cms.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,162 @@
+Title:     How to edit the ODF Toolkit website
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+This documentation shows how to edit the Apache ODF Toolkit
+website. This includes creation of new pages, modification, and deletion - for files
+and sub-directories.
+
+## How it works in general
+
+The website is hosted in a Content Management System (CMS). When you edit a web page
+there are potentially four different versions of it to think about:
+
+ 1. There is the latest version of the page source stored in subversion.
+ 1. There is your working copy of that page source, which you are editing.
+ 1. There is the generated HTML from that source, in the staging directory.
+ 1. There is the production version of the HTML, which is what the public sees.
+
+
+The general flow for updating the website is:
+
+ 1. You check out the latest version of the web page's source.
+ 1. You edit the page source using [Markdown text syntax][1] (mdtext).
+ 1. You commit the source into the repository.  (You will see the SVN commit mail with
+    your log message.)
+ 1. The commit automatically triggers a build that converts the markdown files 
+    into HTML files in the staging directory.  (You will see a commit mail with "Staging
+    update by buildbot" as log message.)
+ 1. You verify that the staged webpage is correct and then tell the CMS to publish 
+    the changes to the production directory.  (You will see a commit mail with "Publishing
+    merge to odftoolkit site by <your Apache ID>" as log message.)
+
+The intent of this workflow is to allow committers flexibility in changing 
+webpages and testing changes on a staging website, before moving these changes to
+the public web site.
+
+## Command line editing workflow
+
+It is assumed that you have already checked out the code from the SVN repository
+(https://svn.apache.org/repos/asf/incubator/odf).
+
+Edit the file via your favorite editor like vi and finally commit via SVN:
+
+     vi myfile.mdtext
+     svn ci -m"My log message" myfile.mdtext
+
+Now wait a few seconds so that the entire website can be rebuilt.
+Verify the staged webpage in a web browser at:
+
+     http://odftoolkit.staging.apache.org/odftoolkit/myfile.html
+
+ Then publish the site:
+
+    curl -sL http://s.apache.org/cms-cli | perl
+
+If this does not work on your local machine just do it on "people.apache.org" by
+executing this:
+
+    ssh -t <user>@people.apache.org publish.pl odftoolkit <your Apache ID>
+
+## Browser-based editing workflow
+
+### Prerequisites
+
+#### Browser bookmark
+
+Normally you see the webpage in your browser. To update this page with an
+inline-editor and little preview you use the [Apache CMS] [3] JavaScript bookmarklet.  Drag that 
+link to your browser's toolbar.  For more information see [here][2].
+
+#### Apache ID
+
+Furthermore, you need an Apache ID to authenticate to the system.
+
+### Starting
+
+Browse to the webpage or directory you would like to edit and click on
+the bookmarklet. Now click on the [Edit this directory] link on the top. The following
+is displayed as content from the CMS.
+
+### Edit an existing webpage
+
+Click on the actions link [Edit] in the appropriate table cell for editing the
+current file. If the file is not in this directory but in a subdirectory, just click on
+the directory name (e.g., "docs/") to enter this directory.
+
+Now you should see a new webpage with four fields:
+
+ 1. Upper left is the inline editor for text in markdown syntax.
+ 1. Upper right shows the written text as a permanent preview or as HTML source code.
+ 1. Below the editor you can enter a log message.
+ 1. Enter a general header text, e.g., the license of the entered text.
+
+When you have finished writing your text, check the "Quick Commit" box, enter a
+commit message and click on [Submit].  This commits your changes to the Subversion 
+repository.
+
+### Verifying the staged web site
+
+As noted above, committing your changes triggers a build of the markdown files
+into HTML in the staging directory.  Wait a few
+seconds and then click the [Staged] link to view your web page as staged.
+
+At this point you should test your web page.  Does it look right?  Any spelling 
+errors? Do the links work?  If you've made substantial changes, perhaps test in
+more than one browser.
+
+Once you are satisfied that the page is correct, you are ready to publish it
+to the production site.
+
+### Publishing to the production directory
+
+After you have edited your files and/or directories, you need now to publish your
+modifications into production. For this please click on the link
+[Publish site] on the top of the webpage. Enter a commit message on click 
+on [Submit].  After a few seconds you can check the [Production] link to see the
+live version of your changes.  
+
+
+### Create a new webpage
+
+When in the correct directory, at the top enter a name for the new text file (e.g.,
+"my-file.mdtext"). Now you enter your text (see topic above).
+
+### Create new subdirectory
+
+When in the correct directory, at the top enter a name for the new directory (e.g.,
+"my-dir/"). Make sure you entered a trailing "/"!
+
+### Delete a webpage or subdirectory
+
+When in the correct directory, click on the actions link [Delete] in the appropriate
+table cell and enter a commit message. Finally click on [Submit].  Generally speaking
+it is always a good idea to use the CMS to delete files and directories over using
+the command-line svn interface, as the CMS will ensure everything gets deleted from
+the staging (and eventually production) repository on commit.  If you use the command-
+line interface instead, you will also need to manually delete the corresponding entities
+in the staging repository in order for those changes to propagate to the production site.
+
+
+## Links
+
+[CMS Documentation Reference][4]
+
+  [1]:  http://daringfireball.net/projects/markdown/syntax
+  [2]:  https://cms.apache.org/#bookmark
+  [3]:  javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))
+  [4]:  http://www.apache.org/dev/cmsref.html

Propchange: incubator/odf/site/trunk/content/odftoolkit/docs/edit-cms.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/docs/governance/consensusBuilding.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/docs/governance/consensusBuilding.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/docs/governance/consensusBuilding.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/docs/governance/consensusBuilding.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,66 @@
+Title:     Consensus Building
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+In some cases there is no obvious path to take, or you might be a new community, 
+or a new member of an existing community. In these cases people will often 
+need to build consensus by making proposals and eliciting responses.
+
+We want to avoid unnecessary discussion and the creation of significant
+amounts of unnecessary mail that everyone in the community needs to read. 
+That is not to say that we want to avoid constructive discussion. This is 
+the lifeblood of a successful project. However, many ASF projects adopt a 
+shorthand notation for showing support, or otherwise, for a proposal.
+
+## Expressing support (or otherwise)
+
+The notation used is "+1", "-1" and "0". It's also common to see "+0" and "-0".
+
+So, what do these notations mean?
+
+  - +1 means "I agree with this and will help make it happen"
+  - +0 means "I agree with this but probably won't make it happen, so my 
+opinion is not that important"
+  - -0 means "I don't agree with this, but I'm offering no alternative so 
+my opinion is not that important"
+  - -1 means "I don't agree and I am offering an alternative that I am able 
+to help implement"
+
+Many people will use fractions to indicate the strength of their feelings,
+ e.g. "+0.5". Some will even indicate this is a "no brainer" with something 
+like "+1000".
+
+The important thing is that this is not an exact science. It's just a shorthand 
+way of communicating strength of feeling.
+
+## Consensus Building is Not Voting
+
+The confusing thing about this notation is that it is the same notation
+used in a formal vote. Knowing when something is a vote and when it is a 
+preference is important. It's easy to tell though, if the subject does not have 
+"[Vote]" at the start then it's just an opinion. We try not to call votes,
+consensus building is much more inclusive.
+
+The reasons for this notation being common is 
+that when someone wants to summarise a discussion thread they can mentally 
+add up the strength of feeling of the community and decide if there is consensus
+or not.
+
+Once there is a clear consensus members of the community can proceed with 
+the work under the [lazy consensus][1] model.
+
+  [1]: /odftoolkit/docs/governance/lazyConsensus.html
\ No newline at end of file

Propchange: incubator/odf/site/trunk/content/odftoolkit/docs/governance/consensusBuilding.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/docs/governance/lazyConsensus.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/docs/governance/lazyConsensus.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/docs/governance/lazyConsensus.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/docs/governance/lazyConsensus.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,71 @@
+Title:     Lazy Consensus
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+The concept of "Lazy Consensus" is very important in our project. Lazy
+Consensus means that when you are convinced that you know what the community
+would like to see happen you can simply assume that you already have consensus
+and get on with the work. You don't have to insist people discuss and/or
+approve your plan, and you certainly don't need to call a vote to get approval.
+You just assume you have the community's support unless someone says otherwise.
+
+We have a time machine (Subversion), this means that as long as you commit 
+(or submit patches) early and often the community has plenty of opportunity 
+to indicate disapproval. If you believe the community will support your action
+you can operate on lazy consensus as long as you are prepared to roll back 
+any work should a valid objection is raised.
+
+## Avoiding Unnecessary Discussion
+
+The key thing about lazy consensus is that it's easier for people to agree,
+by doing nothing, than it is to object, which requires an
+alternative to be proposed. This has two effects, firstly people are less 
+likely to object for the sake of it and secondly it cuts down on the amount 
+of unnecessary mail traffic and discussion.
+
+Lazy consensus means we can avoid waiting for a community based decision 
+before proceeding. However, it does require everyone who cares for the health
+of the project to watch what is happening, as it is happening. Objecting too 
+far down the road will cause upset, but objecting (or asking for clarification 
+of intent) early is likely to be greeted with relief that someone is watching
+and cares.
+
+## Stating Lazy Consensus
+
+Sometimes a member of the community will believe a specific action is the correct 
+one for the community but are not sure enough to proceed with the work under the 
+lazy consensus model. In these circumstances they can state Lazy Consensus is in 
+operation.
+
+What this means is that they make a proposal and state that they will start 
+implementing it in 72 hours unless someone objects. 72 hours is chosen because
+it accounts for different timezones and non-apache commitments.
+
+In this approach the original proposal is not insisting that there is a discussion
+around their proposal, nor are they requesting that the community explicitly 
+supports their actions. However, this differs from assuming lazy consensus 
+since it allows space and time to [express support or objections][1] and corrections to 
+the proposal before work begins. 
+
+## Silence is consent
+
+People may choose to indicate their support for the actions taken with a +1 
+mail - quick and easy to read and reassuring for the implementer. However, 
+remember, in a lazy consensus world silence is the equivalent to support. This
+can take some time to get used to.
+
+  [1]: /odftoolkit/docs/governance/consensusBuilding.html
\ No newline at end of file

Propchange: incubator/odf/site/trunk/content/odftoolkit/docs/governance/lazyConsensus.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/docs/governance/voting.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/docs/governance/voting.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/docs/governance/voting.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/docs/governance/voting.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,112 @@
+Title:     Voting
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+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. By the time a
+vote is called there should already be [consensus in the community][1]. The vote 
+itself is, normally, a formality.
+
+## Calling a Vote
+
+Once it is time to call the vote a mail is posted with a subject starting with
+"[VOTE]". This enables the community members to ensure they do not miss an important
+vote thread. It also indicates that this is not consensus building but a formal
+vote. The initiator is responsible for the vote. That means also to count the votes
+and present the results. Everyone has 1 vote.
+
+### Casting Your Vote
+
+The notation used in voting is:
+
++1 (means I vote positive)
+   You can say why you vote positive but it's not a must-have.
+
+ 0 (means vote abstention and nothing else)
+
+-1 (means I vote negative because of the following reason)
+   Yes, you must support your objection and provide an alternative course of action
+   that you are willing and able to implement (where appropriate).
+
+#### Example for a vote mail:
+
+    Address: private@
+    Subject: [VOTE] John Doe should become a regular committer
+    
+    Text:
+    "I would like to propose to vote in John Doe as committer. John has showed in
+    the last months that he has the skills and oversight for improving things (think
+    about the last UI change of the "Find" dialog)."
+    
+    +1 (means I vote for John)
+     0 (means vote abstention)
+    -1 (means I vote against John because of the following reason:
+    
+    Voting time frame is finished 72 hours from now until June 30, 12:00 PM UTC.
+
+#### Example for a reply mail:
+
+    Text:
+    +1
+    
+    I like his work and want him to stay and to go on with his good improvements.
+
+
+#### Example for a result mail:
+
+    Subject: [VOTE][RESULTS] John Doe should become a regular committer
+    
+    Text:
+    Vote started Thu, Jun 27, 2011 at 12:00 PM UTC, voting is now closed.
+    
+    Voting results:
+    
+    --- Numbers ---
+    
+    +1: 12
+     0: 0
+    -1: 0
+    
+    --- Details ---
+    
+    +1 John Low
+    +1 Marc
+    +1 David
+    +1 Robert
+    +1 Steve
+    +1 Chris
+    +1 Stefan
+    +1 Andrew
+    +1 Dennis
+    +1 Karl
+    +1 Simon
+    +1 Greg
+
+[See here for more information][2] <br>
+[See here for more mail templates][3]
+
+
+  [1]: http://incubator.apache.org/odftoolkit/docs/governance/consensusBuilding.html
+  [2]: http://incubator.apache.org/rave/docs/governance/voting.html
+  [3]: http://community.apache.org/newcommitter.html

Propchange: incubator/odf/site/trunk/content/odftoolkit/docs/governance/voting.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/get-involved.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/get-involved.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/get-involved.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/get-involved.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,101 @@
+Title: Get Involved
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+You don't need to be a software developer to contribute to 
+Apache ODF Toolkit. To be successful this project 
+requires a range of different skills, levels of involvement and degrees of 
+technical expertise. So, if you want to get involved in Apache ODF Toolkit, there 
+is almost certainly a role for you. 
+
+We are looking for people to:
+
+  - provide feedback
+  - write or update documentation
+  - help new users
+  - recommend the project to others
+  - test the code and report bugs
+  - fix bugs
+  - give us feedback on required features
+  - write and update the software
+  - create artwork
+  - anything you can see that needs doing
+
+All of these contributions help to keep a project active and strengthen 
+the community. The project team and the broader community will 
+therefore welcome and encourage participation, and attempt to make it 
+as easy as possible for people to get involved. 
+
+We maintain a list of specific areas where we need volunteers on our [Help Wanted] [15] page of the wiki.
+
+## Mailing lists
+
+Your first engagement with the project should be to subscribe to our
+[mailing lists][14].
+
+## Decision Making
+
+The most important thing about engaging with any Apache project is that everyone
+is equal. All people with an opinion are entitled to express that opinion and, where 
+appropriate, have it considered by the community.
+
+To some the idea of having to establish consensus in a large and distributed team 
+sounds inefficient and frustrating. Don't despair though, The Apache Way has a
+set of simple processes to ensure things proceed at a good pace.
+
+In ASF projects we don't like to vote. We reserve that for the few things that need 
+official approval for legal or process reasons (e.g. a release or a new committer). 
+Most of the time we work with the consensus building techniques documented below.
+
+
+### Lazy Consensus
+
+[Lazy consensus][10] is the first, and possibly the most important, consensus building 
+tool we have. Essentially lazy consensus means that you don't need to get explicit
+approval to proceed, but you need to be prepared to listen if someone objects.
+
+### Consensus Building
+
+Sometimes lazy consensus is not appropriate. In such cases it is necessary to
+make a proposal to the mailing list and discuss options. There are mechanisms
+for quickly showing your support or otherwise for a proposal and 
+[building consensus][11] amongst the community.
+
+Once there is a consensus people can proceed with the work under the [lazy 
+consensus][12] model.
+
+### Voting
+
+Occasionally a "feel" for consensus is not enough. Sometimes we need to 
+have a measurable consensus. For example, when [voting][13] in new committers or 
+to approve a release. 
+
+
+  [1]: mailto:odf-dev-subscribe@incubator.apache.org
+  [2]: mailto:odf-dev@incubator.apache.org
+  [3]: mailto:odf-dev-unsubscribe@incubator.apache.org
+  [4]: http://markmail.org/search/+list:org.apache.incubator.odf-dev
+  [5]: http://mail-archives.apache.org/mod_mbox/incubator-odf-dev/
+  [6]: mailto:odf-commits-subscribe@incubator.apache.org
+  [7]: mailto:odf-commmits-unsubscribe@incubator.apache.org
+  [8]: http://markmail.org/search/+list:org.apache.incubator.odf-commits
+  [9]: http://mail-archives.apache.org/mod_mbox/incubator-odf-commits/
+  [10]: /odftoolkit/docs/governance/lazyConsensus.html
+  [11]: /odftoolkit/docs/governance/consensusBuilding.html
+  [12]: /odftoolkit/docs/governance/lazyConsensus.html
+  [13]: /odftoolkit/docs/governance/voting.html
+  [14]:/odftoolkit/mailing-lists.html

Propchange: incubator/odf/site/trunk/content/odftoolkit/get-involved.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/images/apache-incubator-logo.png
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/images/apache-incubator-logo.png?rev=1160503&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/odf/site/trunk/content/odftoolkit/images/apache-incubator-logo.png
------------------------------------------------------------------------------
    svn:mime-type = image/png

Added: incubator/odf/site/trunk/content/odftoolkit/images/feather-small.gif
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/images/feather-small.gif?rev=1160503&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/odf/site/trunk/content/odftoolkit/images/feather-small.gif
------------------------------------------------------------------------------
    svn:mime-type = image/gif

Added: incubator/odf/site/trunk/content/odftoolkit/index.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/index.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/index.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/index.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,8 @@
+Title: Apache ODF Toolkit (Incubating)
+
+Apache "ODF Toolkit" is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator.
+Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and
+decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is
+not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has
+yet to be fully endorsed by the ASF.
+

Propchange: incubator/odf/site/trunk/content/odftoolkit/index.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/license.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/license.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/license.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/license.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,213 @@
+Title:
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+Apache License<br></br>Version 2.0, January 2004<br></br>
+[http://www.apache.org/licenses/](http://www.apache.org/licenses/) 
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+**<a name="definitions">1. Definitions</a>**.
+
+"License" shall mean the terms and conditions for use, reproduction, and
+distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the
+copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other
+entities that control, are controlled by, or are under common control with
+that entity. For the purposes of this definition, "control" means (i) the
+power, direct or indirect, to cause the direction or management of such
+entity, whether by contract or otherwise, or (ii) ownership of fifty
+percent (50%) or more of the outstanding shares, or (iii) beneficial
+ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising
+permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation source,
+and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation
+or translation of a Source form, including but not limited to compiled
+object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form,
+made available under the License, as indicated by a copyright notice that
+is included in or attached to the work (an example is provided in the
+Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form,
+that is based on (or derived from) the Work and for which the editorial
+revisions, annotations, elaborations, or other modifications represent, as
+a whole, an original work of authorship. For the purposes of this License,
+Derivative Works shall not include works that remain separable from, or
+merely link (or bind by name) to the interfaces of, the Work and Derivative
+Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original
+version of the Work and any modifications or additions to that Work or
+Derivative Works thereof, that is intentionally submitted to Licensor for
+inclusion in the Work by the copyright owner or by an individual or Legal
+Entity authorized to submit on behalf of the copyright owner. For the
+purposes of this definition, "submitted" means any form of electronic,
+verbal, or written communication sent to the Licensor or its
+representatives, including but not limited to communication on electronic
+mailing lists, source code control systems, and issue tracking systems that
+are managed by, or on behalf of, the Licensor for the purpose of discussing
+and improving the Work, but excluding communication that is conspicuously
+marked or otherwise designated in writing by the copyright owner as "Not a
+Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on
+behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+**<a name="copyright">2. Grant of Copyright License</a>**. Subject to the
+terms and conditions of this License, each Contributor hereby grants to You
+a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of, publicly
+display, publicly perform, sublicense, and distribute the Work and such
+Derivative Works in Source or Object form.
+
+**<a name="patent">3. Grant of Patent License</a>**. Subject to the terms
+and conditions of this License, each Contributor hereby grants to You a
+perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made, use,
+offer to sell, sell, import, and otherwise transfer the Work, where such
+license applies only to those patent claims licensable by such Contributor
+that are necessarily infringed by their Contribution(s) alone or by
+combination of their Contribution(s) with the Work to which such
+Contribution(s) was submitted. If You institute patent litigation against
+any entity (including a cross-claim or counterclaim in a lawsuit) alleging
+that the Work or a Contribution incorporated within the Work constitutes
+direct or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate as of the
+date such litigation is filed.
+
+**<a name="redistribution">4. Redistribution</a>**. You may reproduce and
+distribute copies of the Work or Derivative Works thereof in any medium,
+with or without modifications, and in Source or Object form, provided that
+You meet the following conditions:
+
+1. You must give any other recipients of the Work or Derivative Works a
+copy of this License; and
+
+1. You must cause any modified files to carry prominent notices stating
+that You changed the files; and
+
+1. You must retain, in the Source form of any Derivative Works that You
+distribute, all copyright, patent, trademark, and attribution notices from
+the Source form of the Work, excluding those notices that do not pertain to
+any part of the Derivative Works; and
+
+1. If the Work includes a "NOTICE" text file as part of its distribution,
+then any Derivative Works that You distribute must include a readable copy
+of the attribution notices contained within such NOTICE file, excluding
+those notices that do not pertain to any part of the Derivative Works, in
+at least one of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or documentation,
+if provided along with the Derivative Works; or, within a display generated
+by the Derivative Works, if and wherever such third-party notices normally
+appear. The contents of the NOTICE file are for informational purposes only
+and do not modify the License. You may add Your own attribution notices
+within Derivative Works that You distribute, alongside or as an addendum to
+the NOTICE text from the Work, provided that such additional attribution
+notices cannot be construed as modifying the License.
+You may add Your own copyright statement to Your modifications and may
+provide additional or different license terms and conditions for use,
+reproduction, or distribution of Your modifications, or for any such
+Derivative Works as a whole, provided Your use, reproduction, and
+distribution of the Work otherwise complies with the conditions stated in
+this License.
+
+**<a name="contributions">5. Submission of Contributions</a>**. Unless You
+explicitly state otherwise, any Contribution intentionally submitted for
+inclusion in the Work by You to the Licensor shall be under the terms and
+conditions of this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify the
+terms of any separate license agreement you may have executed with Licensor
+regarding such Contributions.
+
+**<a name="trademarks">6. Trademarks</a>**. This License does not grant
+permission to use the trade names, trademarks, service marks, or product
+names of the Licensor, except as required for reasonable and customary use
+in describing the origin of the Work and reproducing the content of the
+NOTICE file.
+
+**<a name="no-warranty">7. Disclaimer of Warranty</a>**. Unless required by
+applicable law or agreed to in writing, Licensor provides the Work (and
+each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT
+WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including,
+without limitation, any warranties or conditions of TITLE,
+NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You
+are solely responsible for determining the appropriateness of using or
+redistributing the Work and assume any risks associated with Your exercise
+of permissions under this License.
+
+**<a name="no-liability">8. Limitation of Liability</a>**. In no event and
+under no legal theory, whether in tort (including negligence), contract, or
+otherwise, unless required by applicable law (such as deliberate and
+grossly negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a result
+of this License or out of the use or inability to use the Work (including
+but not limited to damages for loss of goodwill, work stoppage, computer
+failure or malfunction, or any and all other commercial damages or losses),
+even if such Contributor has been advised of the possibility of such
+damages.
+
+**<a name="additional">9. Accepting Warranty or Additional Liability</a>**.
+While redistributing the Work or Derivative Works thereof, You may choose
+to offer, and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this License.
+However, in accepting such obligations, You may act only on Your own behalf
+and on Your sole responsibility, not on behalf of any other Contributor,
+and only if You agree to indemnify, defend, and hold each Contributor
+harmless for any liability incurred by, or claims asserted against, such
+Contributor by reason of your accepting any such warranty or additional
+liability.
+
+END OF TERMS AND CONDITIONS
+
+# APPENDIX: How to apply the Apache License to your work # {#apply}
+
+To apply the Apache License to your work, attach the following boilerplate
+notice, with the fields enclosed by brackets "[]" replaced with your own
+identifying information. (Don't include the brackets!) The text should be
+enclosed in the appropriate comment syntax for the file format. We also
+recommend that a file or class name and description of purpose be included
+on the same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+       :::text
+       Copyright [yyyy] [name of copyright owner]
+
+       Licensed under the Apache License, Version 2.0 (the "License");
+       you may not use this file except in compliance with the License.
+       You may obtain a copy of the License at
+
+           http://www.apache.org/licenses/LICENSE-2.0
+
+       Unless required by applicable law or agreed to in writing, software
+       distributed under the License is distributed on an "AS IS" BASIS,
+       WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+       See the License for the specific language governing permissions and
+       limitations under the License.
+

Propchange: incubator/odf/site/trunk/content/odftoolkit/license.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/mailing-lists.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/mailing-lists.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/mailing-lists.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/mailing-lists.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,82 @@
+Title: Mailing Lists
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+## ODF Toolkit Mailing Lists
+
+We welcome you to join our mailing lists and let us know about your thoughts or
+ideas about Apache ODF Toolkit
+
+## Participation Guidelines
+We ask all mailing list participants to observe [these guidelines][11]. 
+
+Specifically note the request "Use sensible and concise email subject headings".
+
+Some subject tags to consider include:
+
+ - [www] for posts related to the website
+ - [Repo] for posts related to the source code repository
+
+Other useful topic tags can be found by observing traffic on the list or by looking at the list archives.
+
+In addition to the topic subject tags, there are also tags used to indicate a request:
+
+ - [DISCUSS] indicates a rough idea is being floated, and input is welcome
+ - [PROPOSAL] indicates a specific proposal is being made, and often that Lazy Consensus is being sought.
+ - [VOTE] indicates that a formal vote is being called.  This is rare.
+
+Note: it is common for a topic tag and an action tag to be combined, e.g.:
+
+ - [PROPOSAL][Repo] Migration of legacy repository to SVN
+ - [DISCUSS][download] What are our options of mirroring legacy releases?
+
+
+## Development Mailing List
+
+This is where the community hangs out. This list is used to coordinate
+activities and ensure we are all pulling in the same direction.  This is a high traffic list, with an average of 57 posts/day.
+
+  - Subscribe: [odf-dev-subscribe@incubator.apache.org][1]
+  - Post (after subscription): [odf-dev@incubator.apache.org][2]
+  - Unsubscribe: [odf-dev-unsubscribe@incubator.apache.org][3]
+  - Archives
+    - [Markmail][4]
+    - [Gmane][5]
+    - [Apache][6]
+
+## Commits Mailing List
+
+This is where the community receives automated notifications of any changes to the
+ODF Toolkit code and documentation.  This is a moderate traffic list, with an average of 10 posts/day.
+
+  - Subscribe: [odf-commits-subscribe@incubator.apache.org][7]
+  - Unsubscribe: [odf-commmits-unsubscribe@incubator.apache.org][8]
+  - Archives
+    - [Markmail][9]
+    - [Apache][10]
+
+  [1]:  mailto:odf-dev-subscribe@incubator.apache.org
+  [2]:  mailto:odf-dev@incubator.apache.org
+  [3]:  mailto:odf-dev-unsubscribe@incubator.apache.org
+  [4]:  http://markmail.org/search/+list:org.apache.incubator.odf-dev
+  [5]:  http://dir.gmane.org/gmane.comp.apache.incubator.ooo.devel/
+  [6]:  http://mail-archives.apache.org/mod_mbox/incubator-odf-dev/
+  [7]:  mailto:odf-commits-subscribe@incubator.apache.org
+  [8]:  mailto:odf-commmits-unsubscribe@incubator.apache.org
+  [9]:  http://markmail.org/search/+list:org.apache.incubator.odf-commits
+  [10]: http://mail-archives.apache.org/mod_mbox/incubator-odf-commits/
+  [11]: http://www.apache.org/dev/contrib-email-tips.html

Propchange: incubator/odf/site/trunk/content/odftoolkit/mailing-lists.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/people.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/people.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/people.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/people.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,28 @@
+Title:     Some of our contributors
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+Apache ODF Toolkit (Incubating) is a community developed project. The list below
+is a partial list of contributors to the project, for a complete list you'd have
+to look at all contributors to our issue tracker, mailing list and version control.
+
+| Apache ID | Name                                      # {.w160}| Home            # {.w180}| Skills/Interests |
+|^----------|----------------------------------------------------|--------------------------|------------------|
+| wave      | David Fisher                                       | San Francisco, CA, USA   | Document Generation and Workflow, Java, Postscript, PDF, Apache POI, Web Services |
+| dpharbison | Don Harbison                                      | Chelmsford, MA USA       | Trademark, Branding, Communications, Community Development |
+| robweir   | [Rob Weir](http://www.robweir.com/blog)            | Westford, MA, USA        | C/C++, Java, Python, XML, ODF, Performance tuning |
+| orcmid    | [Dennis E. Hamilton](http://nfoworks.org/diary/)  | Seattle, WA  | C/C++, Java, Interoperability, ODF, security, architecture, web |
\ No newline at end of file

Propchange: incubator/odf/site/trunk/content/odftoolkit/people.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/ppmc-faqs.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/ppmc-faqs.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/ppmc-faqs.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/ppmc-faqs.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,123 @@
+Title:     PPMC FAQs
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+### What is the PPMC?
+
+The Podling Project Management Committee (PPMC) is the government of the project. It
+consists of ASF mentors and initial committers. The committee is responsible for the
+project and decides what to do and which direction to go.
+<br> ([see here for more information][1])
+
+### How to participate?
+
+First of all you have to think how you want to participate as we have different kind
+of roles like user, developer, committer. The easiest way is to use what we build as
+user. If you want to improve parts of the software, or documentation, write to our
+[mailing lists][2] what should be modified and how it should be done.
+
+The following are conditions to become a committer:
+
+ 1. You have sent in patches that were well-respected to improve the software.
+ 2. You have added documentation to the Wiki or website that were well-respected to
+    improve the non-code part of the project.
+ 3. You have shown that you can discuss in the mailing lists and that this has
+    brought us forward.
+ 4. You are well known to the established members, who you are and what you have
+    done in the past. Regarding this project, a former-one or another project.
+
+If 1 of the 4 statements above are true, then you can be voted in as committer.
+
+When the vote result is positive, you will be asked for some information to setup
+your committer status.
+<br> ([see here for more information][4])
+
+### I was invited/voted as committer, so whats next?
+
+The following is a brief summary of what to expect as committer:
+
+ 1. After your (individual Contributor License Agreement ([iCLA][5]) has been
+    received and registered, you will be invited to specify one or more preferred
+    Apache user names.
+
+    **Important**: <br>
+    The e-mail address you provide in your iCLA will be used for the following
+    communications with you.
+
+    Please note that there is also a [Corporate Contributor License Agreement
+    (CCLA)][6] if you want/have to commit in the name of a company or organization.
+
+ 2. Choose one or more user name(s) that would be acceptable to you. These are short
+    names or abbreviation that will be used for a Unix account login.
+
+    **Example:** <br>
+    Your name is "John Doe", so an ID could be "johnd" or "jdoe". [Here you can see
+    if the ID is still free][7] or already given to another committer.
+    
+    Supply all other information that is requested. Return the ID requests as
+    instructed.
+
+ 3. When your choices are returned, the first request that does not conflict with
+    an already-issued ID will be used to generate an Apache ID. Write them in
+    the order you would like to have, so the first one is the most wanted.
+
+ 4. You will receive an e-mail, from "root@apache.org", that confirms the Apache
+    user name for you and also provides you with an initial password. There are also
+    instructions for changing your password. Please be patient as this mail can take
+    some days.
+
+ 5. The ID will also be your Apache e-mail address. Note that the account will be
+    set up to forward all received mails to the e-mail address you supplied on your
+    iCLA. It is not a normal mail account but just for forwarding. After you have
+    the account there is also a way to associate your Apache e-mail address with
+    additional e-mail addresses that you have. (**ToDo**: Add a link to a how-to)
+
+ 6. The ID and password will allow you to check in changes and new additions on the
+    Apache SVN repository for the ODF Toolkit incubator repository. The ability
+    to check in material on the SVN repository is important for more than code. All
+    committers will have an use for it.
+
+ 7. The ID and password will allow you to login to a personal Unix account on the
+    Apache server "people.apache.org". You can produce a personal website at this
+    account as well as use it as a regular Unix (specifically, FreeBSD) account. You
+    do not need to be able to use this account. You may find it useful as you become
+    more accomplished as a committer.  
+
+ 8. Being a committer also grants access to some non-public resources and mailing
+    lists. There are details in the [private committers SVN tree][8].
+
+See the [Guide for new committers][9] and the [Committers' FAQ][10] for more information.
+
+### How and when to vote?
+
+Voting is done when a formal decision has to be made or due to legal reasons, e.g.,
+to vote in new members as committers. In any case avoid voting as the normal way is
+to come to a decision by discussions. The initiator is responsible for the vote,
+that means also to count the votes and present the result. Every member has 1 vote.
+<br> ([see here for more information][11])
+
+  [1]: http://incubator.apache.org/guides/ppmc.html
+  [2]: http://incubator.apache.org/odftoolkit/mailing-lists.html
+  [4]: http://incubator.apache.org/guides/participation.html
+  [5]: http://www.apache.org/licenses/icla.txt
+  [6]: http://www.apache.org/licenses/cla-corporate.txt
+  [7]: http://people.apache.org/committer-index.html
+  [8]: https://svn.apache.org/repos/private/committers
+  [9]: http://www.apache.org/dev/new-committers-guide.html
+  [10]: http://www.apache.org/dev/committers.html
+  [11]: http://incubator.apache.org/odftoolkit/docs/governance/voting.html
+

Propchange: incubator/odf/site/trunk/content/odftoolkit/ppmc-faqs.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/release-process.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/release-process.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/release-process.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/release-process.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,193 @@
+Title: Release Process
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+###Incubator Release Steps
+
+1. Environment setup for releasing artifacts (same for SNAPSHOTs and releases) -
+  1. Increase the default Java heap available to Maven (required for Java SE 6)  
+
+        export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"
+  2. Use the latest Sun 1.6.0 JDK
+  3. Use Maven 3.0.3 or later
+  4. Make sure the [Release Setup](release-setup.html) steps have been performed.
+
+2. Prepare the source for release:     
+     1. Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly. Also, transition any Resolved issues to the Closed state.
+     2. Update the text files in a working copy of the project root -
+         1. Update the CHANGELOG based on the Text release reports from JIRA.
+         2. Review and update README.txt if needed.
+         3. Commit any changes back to svn 
+     3. Stage any Roadmap or Release landing pages on the site.
+
+3. Checkout a clean copy of the trunk to release using command line svn.   
+
+   *Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse throws off the rat:check processing.*
+
+4. Use `mvn -P pedantic verify` to verify the source has the required headers before trying to release.
+
+5. Do a dry run of the release:prepare step:  
+       
+        $ mvn -Papache-release release:prepare -DdryRun=true
+
+   The dry run will not commit any changes back to SVN and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :
+      * Release version - take the default 
+      * SCM release tag - *DO NOT TAKE THE DEFAULT*  -: : 0.1-incubating
+      * New development version - take the default
+      * GPG Passprhase  
+
+  *If you cancel a release:prepare before it updates the pom.xml versions, then use the release:clean goal to just remove the extra files that were created.*
+
+6. Verify that the release process completed as expected
+    1. The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding pom.xml file should be the version number.
+    2. If other formatting changes have been made you should review the changes and then commit them -   
+
+            $ svn commit -m "fixing formatting for release"
+    3. Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.
+    4. Verify signatures ([Verifying release signatures](http://incubator.apache.org/rave/release-process.html#verify_signatures))
+
+7. Once any failures or required updates have been committed to svn, rollback the release prepare files:  
+
+        $ mvn -Papache-release release:rollback
+
+8. Prepare the release
+   1. Run the "release:prepare" step for real this time. You'll be prompted for the same version information.
+	
+          $ mvn release:prepare -Papache-release -DpreparationGoals="clean install cargo:package"
+
+   2. Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.
+
+9. Perform the release
+
+  This step will create a maven staging repository and site for use in testing and voting. 
+
+        $ mvn release:perform -Papache-release -Duser.name=<your_apache_uid>
+   
+    *If your local OS userid doesn't match your Apache userid, then you'll have to also override the value provided by the OS to Maven for the site-deploy step to work. This is known to work for Linux, but not for Mac and unknown for Windows.*
+    *The maven-release-plugin is configured with goals "deploy site site:deploy" and will deploy the site files to a staging-site directory on people.apache.org.*
+10. Verify the release artifacts
+   1. Verify the HTML links in site are correct
+   2. Verify the staged artifacts in the nexus repo          
+           1. https://repository.apache.org/index.html
+           2. Enterprise --> Staging
+           3. Staging tab --> Name column --> org.apache.rave
+           4. Navigate through the artifact tree and make sure that all javadoc, sources, tests, jars, ... have .asc (GPG signature) and .md5 files. See http://people.apache.org/~henkp/repo/faq.html and http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig
+   3. Close the nexus staging repo
+     1. https://repository.apache.org/index.html
+     2. Enterprise --> Staging
+     3. Staging tab --> Name column --> org.apache.rave
+     4. Right click on the open staging repo (org.apache.rave-XXX) and select Close.
+11. Put the release candidate up for a vote
+     1. Create a VOTE email thread on rave-dev@ to record votes as replies, like [this](release-vote.txt)
+     2. Create a DISCUSS email thread on rave-dev@ for any vote questions, [this](release-discuss.txt)
+     3. Perform a review of the release and cast your vote. See the following for more details on Apache releases 
+
+     [http://www.apache.org/dev/release.html](http://www.apache.org/dev/release.html)  
+     [http://incubator.apache.org/guides/releasemanagement.html](http://incubator.apache.org/guides/releasemanagement.html)
+
+     4. A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. See - Recovering from a vetoed release
+     5. After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then post the results to the vote thread by -
+         1. reply to the initial email and prepend to the original subject -
+
+         [RESULTS]
+
+         2. Include a list of everyone who voted +1, 0 or -1.
+
+12. Put the release candidate up for an Incubator PMC vote
+    1. Create a VOTE email thread on general@incubator to record votes as replies, like [this](vote-ipmc.txt)
+
+    2. After the vote has been open for at least 72 hours, has at least three +1 Incubator PMC votes and no -1 votes, then post the results to the vote thread by -
+        1. replying to the initial email and prepend to the original subject -
+
+         [RESULTS]
+
+        2. Include a list of everyone who voted +1, 0 or -1.
+
+13. Finalizing a release
+   1. Promote the staged nexus artifacts -
+       1. https://repository.apache.org/index.html
+       2. Enterprise --> Staging
+       3. Staging tab --> Name column --> org.apache.rave
+       4. Right click on the closed staging repo (org.apache.rave-XXX) and select Promote.
+
+    2. Copy the distribution artifacts over to the distribution area
+
+          $ ssh ${user.name}@people.apache.org  
+          $ mkdir /www/www.apache.org/dist/incubator/rave/${project.version}   
+          $ cd /www/www.apache.org/dist/incubator/rave/${project.version}   
+          $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip    
+          $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.asc   
+          $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.md5   
+          $ wget https://repository.apache.org/content/repositories/releases/org/apache/rave/rave-parent/${project.version}/rave-parent-${project.version}-source-release.zip.sha1    
+
+     **Make sure all the copied files have g+rw set and only o+r set**
+
+          $ find . -user ${user.name} -type f | xargs chmod 664
+          $ find . -user ${user.name} -type d | xargs chmod 775
+
+     *Note: All of the artifacts are in the maven repos, but we may create an assembly to publish in future releases*
+    
+    3. Publish the staged website 
+
+14. Update the JIRA versions page to mark the version as "released", and set the date to the date that the release was approved. You may also need to make a new release entry for the next release.
+15. Announcing the release
+   1. After the mirrors have had time to update (24 hours to be on the safe side) update the wiki with pointers to the new release
+   2. Make a news announcement on the Rave homepage.
+   3. Make an announcement about the release on the rave-users@incubator.apache.org, rave-dev@incubator.apache.org, general@incubator.apache.org, and announce@apache.org list as per the Apache Announcement Mailing Lists page)
+
+
+####Recovering from a vetoed release
+
+1. Reply to the initial vote email and prepend to the original subject -
+
+     [CANCELED]
+
+2. Rollback the version upgrades in trunk by either -
+    1. Restore the 0.1-rc1.tar.gz and run
+    
+        $ mvn -Papache-release release:rollback
+
+    2. Manually revert the versions in trunk to the prior version and commit
+
+3. Delete the svn tag created by the release:perform step -
+
+       $ svn del https://svn.apache.org/repos/asf/incubator/rave/tags/0.1-incubating -m "deleting tag from rolled back release"
+
+4. Drop the nexus staging repo
+    1. https://repository.apache.org/index.html
+    2. Enterprise --> Staging
+    3. Staging tab --> Name column --> org.apache.rave
+    4. Right click on the closed staging repo (org.apache.rave-XXX) and select Drop.
+
+5. Remote the staged site
+
+6. Make the required updates that caused the vote to be canceled
+7. Spin another release candidate!
+
+
+####Verifying release signatures
+On unix platforms the following command can be executed -
+
+      for file in `find . -type f -iname '*.asc'`
+      do
+          gpg --verify ${file} 
+      done
+
+You'll need to look at the output to ensure it contains only good signatures -
+
+gpg: Good signature from ...
+gpg: Signature made ...

Propchange: incubator/odf/site/trunk/content/odftoolkit/release-process.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native

Added: incubator/odf/site/trunk/content/odftoolkit/source.mdtext
URL: http://svn.apache.org/viewvc/incubator/odf/site/trunk/content/odftoolkit/source.mdtext?rev=1160503&view=auto
==============================================================================
--- incubator/odf/site/trunk/content/odftoolkit/source.mdtext (added)
+++ incubator/odf/site/trunk/content/odftoolkit/source.mdtext Mon Aug 22 23:48:04 2011
@@ -0,0 +1,38 @@
+Title: Source Control
+Notice:    Licensed to the Apache Software Foundation (ASF) under one
+           or more contributor license agreements.  See the NOTICE file
+           distributed with this work for additional information
+           regarding copyright ownership.  The ASF licenses this file
+           to you under the Apache License, Version 2.0 (the
+           "License"); you may not use this file except in compliance
+           with the License.  You may obtain a copy of the License at
+           .
+             http://www.apache.org/licenses/LICENSE-2.0
+           .
+           Unless required by applicable law or agreed to in writing,
+           software distributed under the License is distributed on an
+           "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+           KIND, either express or implied.  See the License for the
+           specific language governing permissions and limitations
+           under the License.
+
+We use [Apache Subversion][1] for version control. You can [browse our 
+repository][2] in your web browser.
+
+## Getting the source code
+
+    svn co https://svn.apache.org/repos/asf/incubator/odf/trunk odf
+
+## Building and Running
+
+Coming soon
+
+### Requirements:
+
+Coming soon
+
+For further information see the [Apache Source Code Repository][3] page.
+
+[1]: http://subversion.apache.org
+[2]: http://svn.apache.org/viewvc/incubator/odf/trunk
+[3]: http://www.apache.org/dev/version-control.html

Propchange: incubator/odf/site/trunk/content/odftoolkit/source.mdtext
------------------------------------------------------------------------------
    svn:eol-style = native



Mime
View raw message