community-commits mailing list archives

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

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 12:58:55 2015
@@ -1 +1 @@
-1666763
+1667528

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 12:58:55 2015
@@ -194,6 +194,34 @@ community.</p>
 with the community to ensure that you understand the needs of the project
 and the commitment you need to make to your mentors.</p>
 <p>Once open applications are made through the <a href="http://www.google-melange.com/">GSoC
site</a></p>
+<h3 id="application-template">Application template</h3>
+<p><em>This is just a suggested template, feel free to add and remove sections
as appropriate. Be brief, don't write a large essay!</em></p>
+<h4 id="about-me">About me</h4>
+<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>
+<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>
+<p><em>Example:</em></p>
+<ul>
+<li><em>Investigate REST client libraries</em></li>
+<li><em>Develop JavaScript functions for browsing files (optional)</em></li>
+<li><em>Integrate with Apache Foo's request system (essential)</em></li>
+</ul>
+<h4 id="results-for-the-apache-community">Results for the Apache community</h4>
+<p><em>Benefit of your work to Apache $Project users and developers. What will
be the legacy of your work after you finish?</em></p>
+<h4 id="deliverables">Deliverables</h4>
+<p><em>Including milestones, components, documentation, tests.</em></p>
+<h4 id="scheduling">Scheduling</h4>
+<p><em>Not too detailed, but some milestones and checkpoints. Rough estimates
per work item (weeks/days). Remember to leave time for slack and bugfixing!</em></p>
+<h4 id="other-commitments">Other commitments</h4>
+<p><em>Exams, part time work, holidays, lectures.</em></p>
+<h4 id="community-engagement">Community engagement</h4>
+<p><em>In particular with Apache $Project, including project mailing lists, wikis,
issue trackers, test systems.</em></p>
+<p><em>This should show a rough understanding of working with open source communities.
You should be engaged with the rest of the community both before coding start (e.g. to develop
this proposal) and during the project.</em></p>
+<p><em>Include any planned user testing, prototypes, code review.</em></p>
 <p><a name="GSoC-ContactingtheASF"></a></p>
 <h2 id="contacting-the-asf">Contacting the ASF</h2>
 <p>The ASF is not just one project, it is a federation of projects, see the



Mime
View raw message