From odf-commits-return-8-apmail-incubator-odf-commits-archive=incubator.apache.org@incubator.apache.org Wed Aug 24 01:46:20 2011 Return-Path: X-Original-To: apmail-incubator-odf-commits-archive@minotaur.apache.org Delivered-To: apmail-incubator-odf-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 144B6706C for ; Wed, 24 Aug 2011 01:46:20 +0000 (UTC) Received: (qmail 94551 invoked by uid 500); 24 Aug 2011 01:46:19 -0000 Delivered-To: apmail-incubator-odf-commits-archive@incubator.apache.org Received: (qmail 94520 invoked by uid 500); 24 Aug 2011 01:46:19 -0000 Mailing-List: contact odf-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: odf-dev@incubator.apache.org Delivered-To: mailing list odf-commits@incubator.apache.org Received: (qmail 94475 invoked by uid 99); 24 Aug 2011 01:46:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Aug 2011 01:46:19 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_FILL_THIS_FORM_SHORT X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Aug 2011 01:46:09 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 3DFD723889E5 for ; Wed, 24 Aug 2011 01:45:46 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r794776 [1/3] - in /websites/staging/odftoolkit/trunk/content: ./ odftoolkit/ odftoolkit/docs/ odftoolkit/docs/governance/ odftoolkit/images/ Date: Wed, 24 Aug 2011 01:45:45 -0000 To: odf-commits@incubator.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8 Message-Id: <20110824014546.3DFD723889E5@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Wed Aug 24 01:45:44 2011 New Revision: 794776 Log: Staging update by buildbot Added: websites/staging/odftoolkit/trunk/content/ websites/staging/odftoolkit/trunk/content/odftoolkit/ websites/staging/odftoolkit/trunk/content/odftoolkit/community-faqs.html websites/staging/odftoolkit/trunk/content/odftoolkit/contact.html websites/staging/odftoolkit/trunk/content/odftoolkit/developer-faqs.html websites/staging/odftoolkit/trunk/content/odftoolkit/docs/ websites/staging/odftoolkit/trunk/content/odftoolkit/docs/edit-cms.html websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/ websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/consensusBuilding.html websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/lazyConsensus.html websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/voting.html websites/staging/odftoolkit/trunk/content/odftoolkit/get-involved.html websites/staging/odftoolkit/trunk/content/odftoolkit/images/ websites/staging/odftoolkit/trunk/content/odftoolkit/images/apache-incubator-logo.png (with props) websites/staging/odftoolkit/trunk/content/odftoolkit/images/feather-small.gif (with props) websites/staging/odftoolkit/trunk/content/odftoolkit/index.html websites/staging/odftoolkit/trunk/content/odftoolkit/license.html websites/staging/odftoolkit/trunk/content/odftoolkit/mailing-lists.html websites/staging/odftoolkit/trunk/content/odftoolkit/people.html websites/staging/odftoolkit/trunk/content/odftoolkit/ppmc-faqs.html websites/staging/odftoolkit/trunk/content/odftoolkit/release-process.html websites/staging/odftoolkit/trunk/content/odftoolkit/source.html websites/staging/odftoolkit/trunk/content/odftoolkit/svn-basics.html websites/staging/odftoolkit/trunk/content/odftoolkit/website-local.html Added: websites/staging/odftoolkit/trunk/content/odftoolkit/community-faqs.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/community-faqs.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/community-faqs.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,97 @@ + + + + + + + +Community FAQs + + + + + + + + +
+ +

Community FAQs

+ +
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/odftoolkit/trunk/content/odftoolkit/contact.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/contact.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/contact.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,104 @@ + + + + + + + +Contact Us + + + + + + + + +
+ +

Contact Us

+

For any questions, comments, or concerns about this project or website please contact the project on the developer mailing list:

+ +

For private or legal matters, please contact the Podling Project Management Committee (PPMC):

+ +
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/odftoolkit/trunk/content/odftoolkit/developer-faqs.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/developer-faqs.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/developer-faqs.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,126 @@ + + + + + + + +Developer FAQs + + + + + + + + +
+ +

Developer FAQs

+

How do I edit this website?

+

The pages on this website are written in markdown syntax and stored in SVN at +https://svn.apache.org/repos/asf/incubator/odf/site

+

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 page.

+

Information on deeper website development is found on the Website Development 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 to Apache.
  2. +
  3. 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 section +on the Apache Committers page. This could take a couple of days, longer if you +submitted the ICLA via post.
  4. +
  5. Once the your ICLA has been recorded, you should send a note to the PPMC +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 +that your preferred userid is not already in use by another Apache Committer.
  6. +
  7. 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.
  8. +
  9. If you were also voted as a PPMC member, you should then subscribe to the +PPMC's private mailing list.
  10. +
  11. Finally, you should read the "Guide for new committers"
  12. +
+

How do I use Apache Subversion?

+

Instructions can be found on the Subversion Basics page.

+
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/odftoolkit/trunk/content/odftoolkit/docs/edit-cms.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/docs/edit-cms.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/docs/edit-cms.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,208 @@ + + + + + + + +How to edit the ODF Toolkit website + + + + + + + + +
+ +

How to edit the ODF Toolkit website

+

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.
  2. +
  3. There is your working copy of that page source, which you are editing.
  4. +
  5. There is the generated HTML from that source, in the staging directory.
  6. +
  7. There is the production version of the HTML, which is what the public sees.
  8. +
+

The general flow for updating the website is:

+
    +
  1. You check out the latest version of the web page's source.
  2. +
  3. You edit the page source using Markdown text syntax (mdtext).
  4. +
  5. You commit the source into the repository. (You will see the SVN commit mail with + your log message.)
  6. +
  7. 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.)
  8. +
  9. 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 " as log message.)
  10. +
+

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 JavaScript bookmarklet. Drag that +link to your browser's toolbar. For more information see here.

+

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.
  2. +
  3. Upper right shows the written text as a permanent preview or as HTML source code.
  4. +
  5. Below the editor you can enter a log message.
  6. +
  7. Enter a general header text, e.g., the license of the entered text.
  8. +
+

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.

+ +

CMS Documentation Reference

+
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/consensusBuilding.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/consensusBuilding.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/consensusBuilding.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,133 @@ + + + + + + + +Consensus Building + + + + + + + + +
+ +

Consensus Building

+

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 model.

+
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/lazyConsensus.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/lazyConsensus.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/lazyConsensus.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,137 @@ + + + + + + + +Lazy Consensus + + + + + + + + +
+ +

Lazy Consensus

+

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 and corrections to +the proposal before work begins.

+ +

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.

+
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/voting.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/voting.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/docs/governance/voting.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,177 @@ + + + + + + + +Voting + + + + + + + + +
+ +

Voting

+

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. 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
+See here for more mail templates

+
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/odftoolkit/trunk/content/odftoolkit/get-involved.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/get-involved.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/get-involved.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,147 @@ + + + + + + + +Get Involved + + + + + + + + +
+ +

Get Involved

+

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.

+

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 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 amongst the community.

+

Once there is a consensus people can proceed with the work under the lazy +consensus model.

+

Voting

+

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.

+
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/odftoolkit/trunk/content/odftoolkit/images/apache-incubator-logo.png ============================================================================== Binary file - no diff available. Propchange: websites/staging/odftoolkit/trunk/content/odftoolkit/images/apache-incubator-logo.png ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: websites/staging/odftoolkit/trunk/content/odftoolkit/images/feather-small.gif ============================================================================== Binary file - no diff available. Propchange: websites/staging/odftoolkit/trunk/content/odftoolkit/images/feather-small.gif ------------------------------------------------------------------------------ svn:mime-type = application/octet-stream Added: websites/staging/odftoolkit/trunk/content/odftoolkit/index.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/index.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/index.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,101 @@ + + + + + + + +Apache ODF Toolkit (Incubating) + + + + + + + + +
+ +

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.

+
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + + Added: websites/staging/odftoolkit/trunk/content/odftoolkit/license.html ============================================================================== --- websites/staging/odftoolkit/trunk/content/odftoolkit/license.html (added) +++ websites/staging/odftoolkit/trunk/content/odftoolkit/license.html Wed Aug 24 01:45:44 2011 @@ -0,0 +1,272 @@ + + + + + + + + + + + + + + + + +
+ + +

Apache License

Version 2.0, January 2004

+http://www.apache.org/licenses/

+

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

+

1. Definitions.

+

"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.

+

2. Grant of Copyright License. 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.

+

3. Grant of Patent License. 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.

+

4. Redistribution. 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

    +
  2. +
  3. +

    You must cause any modified files to carry prominent notices stating +that You changed the files; and

    +
  4. +
  5. +

    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

    +
  6. +
  7. +

    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.

    +
  8. +
+

5. Submission of Contributions. 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.

+

6. Trademarks. 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.

+

7. Disclaimer of Warranty. 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.

+

8. Limitation of Liability. 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.

+

9. Accepting Warranty or Additional Liability. +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

+

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.

+
   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.
+
+
+ +
+
+


Powered by the Apache CMS.

+
+
+

+ 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.

+

+ Copyright © 2011 The Apache Software Foundation Licensed under the Apache License, Version 2.0. + Contact Us +
Apache and the Apache feather logos are trademarks of The Apache Software Foundation. +
Other names appearing on the site may be trademarks of their respective owners. +

+
+
+ + +