community-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r944212 - in /websites/staging/community/trunk/content: ./ gsoc.html
Date Wed, 18 Mar 2015 13:05:03 GMT
Author: buildbot
Date: Wed Mar 18 13:05:03 2015
New Revision: 944212

Log:
Staging update by buildbot for community

Modified:
    websites/staging/community/trunk/content/   (props changed)
    websites/staging/community/trunk/content/gsoc.html

Propchange: websites/staging/community/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Wed Mar 18 13:05:03 2015
@@ -1 +1 @@
-1667528
+1667529

Modified: websites/staging/community/trunk/content/gsoc.html
==============================================================================
--- websites/staging/community/trunk/content/gsoc.html (original)
+++ websites/staging/community/trunk/content/gsoc.html Wed Mar 18 13:05:03 2015
@@ -200,7 +200,7 @@ and the commitment you need to make to y
 <p><em>What relevant experience have you got, including university, work and
hobby activities?</em></p>
 <h4 id="background">Background</h4>
 <p><em>What exists already? What is the identified need? What can you reuse,
what needs to he replaced?</em></p>
-<p><em>Example: Apache Foo has already got support for HTTP client requests,
but this does not work well with OAuth-based services. The main interface for requests can
be reused, but this project proposes to replace the backend code with a modular approach based
no Apache Bar.</em></p>
+<p><em>Example: Apache Foo has already got support for HTTP client requests,
but this does not work well with OAuth-based services. The main interface for requests can
be reused, but this project proposes to replace the backend code with a modular approach based
on Apache Bar.</em></p>
 <h4 id="design-description-of-work">Design / description of work</h4>
 <p><em>Brief list of things you will do / create, in some rough chronological
order.</em></p>
 <p><em>Show which bits are essential, and which are optional. Highlight what
is new, what are modifications, and how your work fits into the existing architecture.</em></p>



Mime
View raw message