svn commit: r846212 - in /websites/staging/flex/trunk: cgi-bin/ content/ content/v2/about-people.html content/v2/community-getinvolved.html

[bu...@apache.org]

Author: buildbot
Date: Fri Jan 11 19:37:23 2013
New Revision: 846212

Log:
Staging update by buildbot for flex

Modified:
    websites/staging/flex/trunk/cgi-bin/   (props changed)
    websites/staging/flex/trunk/content/   (props changed)
    websites/staging/flex/trunk/content/v2/about-people.html
    websites/staging/flex/trunk/content/v2/community-getinvolved.html

Propchange: websites/staging/flex/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 11 19:37:23 2013
@@ -1 +1 @@
-1432244
+1432245

Propchange: websites/staging/flex/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 11 19:37:23 2013
@@ -1 +1 @@
-1432244
+1432245

Modified: websites/staging/flex/trunk/content/v2/about-people.html
==============================================================================
--- websites/staging/flex/trunk/content/v2/about-people.html (original)
+++ websites/staging/flex/trunk/content/v2/about-people.html Fri Jan 11 19:37:23 2013
@@ -387,7 +387,7 @@
 <div class="span3">
 <img src="images/staff-1.jpg" alt="" class="img-circle"/>
 <div class="staff"><h5>Douglas Arthur</h5> <span><i class="icon-tag"></i> dougarthur</span></div>
-<div class="team-about"><p>Consectetur dolor ipsum quiam dolor adipisci velit, aenean at lorem vel est posuere feugiat sed quia noneas numquasa mode tempora incidunt ipsum.</p></div>
+<div class="team-about"><p>Douglas passed away in May, 2012.  He is deeply missed within our community.</p></div>
 
 <!-- Social Icons -->
 <ul class="social-icons ">

Modified: websites/staging/flex/trunk/content/v2/community-getinvolved.html
==============================================================================
--- websites/staging/flex/trunk/content/v2/community-getinvolved.html (original)
+++ websites/staging/flex/trunk/content/v2/community-getinvolved.html Fri Jan 11 19:37:23 2013
@@ -152,7 +152,43 @@
 <!-- Home Page Exception -->
 
 
-<p>get invoved page</p>
+<p>Getting involved with the Apache Flex® Community is easy!</p>
+<p>We are an open-source community governed by the Apache Software Foundation.  Everything we do is out in the open with
+the entire community involved.  All decisions are made on our mailing lists, and all source code is developed
+within our source control system.</p>
+<div><h4>Find out what is going on</h4></div>
+
+<p>If you are interested in what is going on with the project, subscribe to our mailing lists.  Our <a href="community-mailinglists.html">dev@flex.apache.org</a> mailing
+list is where additions and changes to the SDK are discussed.  The list is open to everybody and everybody is encouraged
+to give their opinions on anything discussed on the list.  This is a great place to introduce yourself and let us know
+how you can help.</p>
+<p>If you are interested in helping end-users of the SDK, we also host the <a href="community-mailinglists.html">users@flex.apache.org</a> mailing list.  This list
+is designed for end-users to talk about how to use the SDK and how to build applications that utilize the SDK.</p>
+<div><h4>Contributing Documentation</h4></div>
+
+<p>If you are ready to help us document code, provide tips and tricks, or anything else that is not straight-up code, we
+have a <a href="https://cwiki.apache.org/confluence/display/FLEX/Apache+Flex+Wiki">WIKI</a> that allows for community contribution.  Simply let us know on the dev@flex.apache.org mailing list
+that you wish to get write access to the WIKI.  If you would like to let us know about any blog entries, videos,
+screencasts, etc. that you have created, we would love to help publicize them!</p>
+<div><h4>Reporting Bugs</h4></div>
+
+<p>All of the bugs that we are aware of are housed in the Apache Foundation's JIRA system.  You can take a look at everything
+we have in the system on <a href="https://issues.apache.org/jira/browse/FLEX">Flex JIRA</a>.  To let us know about a bug, create an issue in the JIRA system.  The JIRA
+system automatically emails the dev mailing list and hopefully somebody will take a look at it.  It is really important
+that you give us as much information on the bug as possible.  Even better, if you have a way to reproduce the bug, submit
+a code sample that can help us reproduce it.  Feel free to contribute to the comments as the bug gets worked on.</p>
+<div><h4>Squashing Bugs</h4></div>
+
+<div><h4>Contributing Code</h4></div>
+
+<p>Due to leagal reasons, only a select group of people have access to update or contibute code directly to the project.
+We at Apache take the legality of code seriously, and nothing would be worse than somebody contibuting code that
+they don't own and a 3rd party having a legal claim to our framework.</p>
+<p>That being said, if you are interested in contributing code, you can submit patches to the project via <a href="https://issues.apache.org/jira/browse/FLEX">JIRA</a>.
+To do this, create a new issue that describes what the code you are contibuting, and submit a .path file with your
+code changes, just like from the bug squashing directions above.  If you submit a few patches that meet the Apache
+standards, you will probably be contacted by the PMC to get you direct access to the SVN and for you to be reconized
+for your work as a committer.</p>
 
 <!-- Home Page Exception -->