From: Devrim GÜNDÜZ <devrim@gunduz.org>
Date: Wed, 9 Mar 2011 21:44:58 +0000 (+0000)
Subject: Updates for 2011 GSoC, per Josh.
X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=26a66cdaf86d079b7e4bb428ddce2ceed1524d75;p=pgweb-old.git

Updates for 2011 GSoC, per Josh.


git-svn-id: file:///Users/dpage/pgweb/svn-repo/trunk@2815 8f5c7a92-453e-0410-a47f-ad33c8a6b003
---

diff --git a/portal/template/en/developer/summerofcode.html b/portal/template/en/developer/summerofcode.html
index 0f21b7a0..f3bc2b2f 100644
--- a/portal/template/en/developer/summerofcode.html
+++ b/portal/template/en/developer/summerofcode.html
@@ -5,22 +5,12 @@ Google Summer of Code Program
 <div id="CONTENTWRAP">
 <h1>PostgreSQL and Google Summer of Code</h1>
 
-<p>The PostgreSQL Project is participating in the Google <a
-href="http://socghop.appspot.com/">Summer of Code 2010</a> program. This program endeavors to fund students to contribute to an open source project over the summer break.</p>
+<p>The PostgreSQL Project hopes to participate in the Google <a
+href="http://socghop.appspot.com/">Summer of Code 2011</a> program. This program endeavors to fund students to contribute to an open source project over the summer break.</p>
 
 <ul>
 <li><a href="#ideas">Example Proposal Ideas</a>
 
-<ul>
-
-<li><a href="#todo">Core Code / TODO Items</a></li>
-
-<li><a href="#infrastructure">Infrastructure</a></li>
-
-<li><a href="#extapps">External Applications</a></li>
-</ul>
-</li>
-
 <li><a href="#mentors">Possible Mentors</a></li>
 
 <li><a href="#proposals">Proposal Guidelines</a></li>
@@ -34,46 +24,24 @@ href="http://socghop.appspot.com/">Summer of Code 2010</a> program. This program
 <h2>Example Proposal Ideas</h2>
 <p>The PostgreSQL Project has a wide range of opinions on what it feels are acceptable GSoC projects. The examples listed here are meant only as a suggestion of things we would likely find useful, but you should not feel obligated to pick from this list by any means. If you have just discovered a new algorithm as part of your thesis work, we would love to see a proposal implementing that in PostgreSQL. The point is that all proposals will be evaluated on their own merits, so be creative.
 
-<a id="todo" name="todo"></a>
-<h3>Core Source Code</h3>
 <ul>
 <li><strong>TODO Items</strong>: A number of the items on our TODO list have been marked as good projects for beginners who are new to the PostgreSQL code. Items on this list have the advantage of already having general community agreement that the feature is desireable. These items should also have some general discussion available in the mailing list archives to help get you started. You can find these items on the <a href="http://wiki.postgresql.org/wiki/Todo">TODO</a> list, they will be marked with an [E].
 </li>
-<li><strong>DDL Functions</strong>: Create a SQL-callable function capable of generating DDL scripts for objects within the database.</li>
-<li><strong>EXPLAIN Enhancements</strong>: Add information to EXPLAIN documenting I/O activity, discarded plans, costing detail, memory usage and more.</li>
-<li><strong>Text-Array Indexing</strong>: Add support for indexing text or multi-typed array data, capable of supporting indexed queries, similar to intarray.</li>
-</ul>
-
-<a id="infrastructure" name="infrastructure"></a>
-<h3>Infrastructure</h3>
-<ul>
-<li><strong>Enhance Buildfarm to test external packages, patches, or performance</strong>: The PostgreSQL project maintains a public buildfarm that continuously communicates with several machines that checkout and build the PostgreSQL source on a regular basis. The idea behind this project is to extend the current buildfarm code to allow it download external modules and report back on their build status, to download unapplied patches and test them, or to run performance tests. </li>
-<li><strong>Create "Performance-Farm" framework for continuous performance regression testing</strong>: Similar to the buildfarm, the idea behind this project is to create a public infrastructure that continuously communicates with several machines that checkout and build the PostgreSQL source on a regular basis, running and reporting on agreed performance benchmarks. </li>  
-</ul>
-
-<a id="extapps" name="extapps"></a>
-<h3>External Applications</h3>
-<ul>
-<li><strong>pgAdmin III / phpPgAdmin Enhancements</strong>: PostgreSQL supports a number of popular GUI Tools that are not distributed with the core project. Projects like these often have their own TODO lists and compatibility issues with the core PotgreSQL that need development. We welcome ideas for these projects as well.</li>
-<li><strong>Procedural Language Improvements</strong>: PostgreSQL provides support for more than a dozen different procedural languages, however the level of support varies depending on the language implementation. Enhancing support of these procedural languages might include fixing build issues, adding SPI support, adding trigger support, adding support for IN/OUT parameters and more.</li>
-<li><strong>Replication</strong>: PostgreSQL provides a wide range of replication solutions for varying types of replication needs. Many of these projects need assistance with building against different versions of PostgreSQL, installation and setup, administrative tools, and general bugfixing.</li>
-<li><strong>Teaching & Learning Tools</strong>: External tools to help in teaching the internals of PostgreSQL such as enhanced visual EXPLAIN, graphical models of the query engine, educational guides to the code, and interactive tools to demonstrate various query types.
-<li><strong>PostGIS & GEOS</strong>: Add performance and feature enhancements to PostgreSQL's geographic data support.</li>
-</ul>
-<p>Additional projects may be found by browsing the <a href="http://projects.postgresql.org">PostgreSQL Development Projects</a> website.</p>
+<li><strong>Other Ideas</strong>: are given on our <a href="http://wiki.postgresql.org/wiki/GSoC_2011#Project_Ideas">GSOC2011 Wiki Page</a></li>
 
 <a id="mentors" name="mentors"></a>
 <h2>Mentors</h2>
 
 <p>PostgreSQL follows an open community development model, so student projects are likely to be reviewed and commented on by any and all members of the PostgreSQL community. This also means that we may be able to find mentors for additional projects by reaching out to this community. If you are interested in working on a project not explicitly mentioned above, you may want to contact one of the Summer of Code liaisons below about writing a proposal.</p>
 
-
 <ul>
-	<li>Robert Treat &lt;xzilla @t users.sourceforge.net&gt;, OmniTI Inc., PHP-based projects and infrastructure</li>
-	<li>Selena Deckelmann &lt;selenamarie @t gmail.com&gt;, End Point Inc., user groups and applications</li>
+	<li>Selena Deckelmann &lt;selenamarie @t gmail.com&gt;, Emma.com, user groups and applications</li>
+	<li>Josh Berkus &lt;josh @t postgresql.org&gt;, PostgreSQL Experts, performance engineering</li>
 	<li>Dave Page &lt;dpage @t pgadmin.org&gt;, EnterpriseDB, pgAdmin, GUI tools, and Windows</li>
 </ul>
 
+<p>A list of prospective mentors is provided on our <a href="http://wiki.postgresql.org/wiki/GSoC_2011#2011_Mentors">GSOC2011 Wiki Page</a></p>
+
 <p>If your project is not selected for funding by Google, but you still think you have a
 feasible project proposal, then please email our developers mailing list at <a
 href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>.</p>
@@ -113,17 +81,15 @@ Can you supply us with an email/IM/phone method for being contacted, in case of
 <a id="past" name="past"></a>
 <h2>Previously Accepted Projects</h2>
 <ul>
-	<li>Enhanced Aggregate Support</li>
-	<li>Full Disjunctions</li>
-	<li>Hashing DISTINCT Clause Implementation</li>
-	<li>ECPG Cleanup</li>
-	<li>Initial support of XMLType for PostgreSQL </li>
-	<li>phpPgAdmin FTS support and other improvements</li>
-	<li>pgAdmin graphical query tool and TSQL-like client scripting support</li>
-	<li>xlog viewer</li>
+	<li>Improve pgPHPAdmin user experience</li>
+	<li>Add MERGE command</li>
+	<li>pgAdmin database designer</li>
+	<li>Materialized Views</li>
+	<li>Database schema difference visualizer</li>
+	<li>Add JSON data type</li>
 </ul>
 
-<p>More information on these projects can be found on Google's PostgreSQL SoC pages: (<a href="http://code.google.com/soc/2008/postgres/about.html">2008</a> | <a href="http://code.google.com/soc/2008/postgres/about.html">2007</a> | <a href="http://code.google.com/soc/2006/pgsql/about.html">2006</a>)</p>
+<p>More information on these projects can be found on Google's PostgreSQL SoC pages: (<a href="http://wiki.postgresql.org/wiki/GSoC_2010">2010</a> | <a href="http://code.google.com/soc/2008/postgres/about.html">2008</a> | <a href="http://code.google.com/soc/2008/postgres/about.html">2007</a> | <a href="http://code.google.com/soc/2006/pgsql/about.html">2006</a>)</p>
 
 
 <a id="faq" name="faq"></a>
@@ -134,14 +100,14 @@ Can you supply us with an email/IM/phone method for being contacted, in case of
 <li>
 <p><strong>Am I eligible?</strong></p>
 
-<p>Please see the Google <a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#eligibility">Eligibility FAQ</a> for all questions about eligibility.</p>
+<p>Please see the Google <a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/faqs#eligibility">Eligibility FAQ</a> for all questions about eligibility.</p>
 
 </li>
 
 <li>
 <p><strong>When is the proposal deadline?</strong></p>
 
-<p>According to the <a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#timeline">Summer of Code FAQ</a>, the deadline for submitting student proposals is April 9th, 2010 (19:00 UTC). Please remember that proposals must submitted to Google themselves<!-- (via the <a href="http://code.google.com/soc/student_step1.html">student application form</a>) -->, although we are happy to discuss any proposals with you ahead of time.</p>
+<p>According to the <a href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/faqs#timeline">Summer of Code FAQ</a>, the deadline for submitting student proposals is April 8th, 2011 (19:00 UTC). Please remember that proposals must submitted to Google themselves<!-- (via the <a href="http://code.google.com/soc/student_step1.html">student application form</a>) -->, although we are happy to discuss any proposals with you ahead of time.</p>
 </li>
 
 </ul>