flex-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r846229 - in /websites/staging/flex/trunk: cgi-bin/ content/ content/v2/community-getinvolved.html
Date Fri, 11 Jan 2013 22:07:48 GMT
Author: buildbot
Date: Fri Jan 11 22:07:48 2013
New Revision: 846229

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/community-getinvolved.html

Propchange: websites/staging/flex/trunk/cgi-bin/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 11 22:07:48 2013
@@ -1 +1 @@
-1432245
+1432310

Propchange: websites/staging/flex/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 11 22:07:48 2013
@@ -1 +1 @@
-1432245
+1432310

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 22:07:48
2013
@@ -179,13 +179,27 @@ that you give us as much information on 
 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>
 
+<p>Bugs happen, and you might know how to fix one!  Because we don't allow everybody
write access to the official code repository
+(everybody has access to read, though!), there is an additional process that has to occur
to get fixes in.  To help us
+squash bugs, do the following :</p>
+<ol>
+<li>Find a bug you want to work on, or submit one into <a href="https://issues.apache.org/jira/browse/FLEX">JIRA</a>.
 We have some marked as "easy" if you play with the JIRA filters if you want to start with
an easy one.  Make a comment on the ticket that you plan on working on it so others don't
duplicate your work.</li>
+<li>Check out the source code from SVN.  You may want to use an IDE like Eclipse or
IntelliJ with the proper plugins to do this
+for you.  More information is available on the <a href="dev-sourcecode.html">Source</a>
page.</li>
+<li>Setup your build enviroment.  Check out the README included in the source code
on how to do this.  You will want to make sure that you can perform a compile before you go
much further.</li>
+<li>Fix the bug.  If you need help, ask the dev@flex.apache.org mailing list.  I'm
sure we have pointers to help you out.</li>
+<li>(optional) Run the functional test suite called [Mustella][5] on your code.  The
[Mustella tests][5] are available from the ANT script, but make sure you set it up first.</li>
+<li>Create a .patch file.  If you are using an IDE, check your SVN, VCS or Source Control
menus for this option.  If you are using svn from the command line, use 'svn diff &gt;
myPatch.patch'.</li>
+<li>Attach the .patch file to the JIRA ticket you noted earlier.  A committer will
review the patch and make sure it dosen't break anything else.</li>
+<li>Sit back and bask in the glory that you helped make Flex better!</li>
+</ol>
 <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
+To do this, create a new issue that describes what the code you are contibuting, and submit
a .patch 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>



Mime
View raw message