public inbox for [email protected]
help / color / mirror / Atom feedFrom: Josh Berkus <[email protected]>
To: [email protected]
Subject: Updated summerofcode pages
Date: Fri, 9 Mar 2007 14:51:37 -0800
Message-ID: <[email protected]> (raw)
Robert, Magnus,
Attached are updated Summer of Code pages. I edited a little on the main
page, added two more mentors. More prominently, I've got a second
"Advice to Students Submitting" page, which was based on our experience
with evaluating the Summer of Code applications last year. I've already
linked it in.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
Attachments:
[text/html] summerofcodeadvice.html (2.9K, 2-summerofcodeadvice.html)
download | inline:
<h1>Advice to Students on Submitting SoC Applications</h1>
<p>
<strong>Be Foresighted:</strong> Include a full plan of action with your proposal, about one half to a full page of what you're going to do and how you think you will do it, and possibly even what you will do if your initial approach does not work.
</p><p>
<strong>Be Documented:</strong> Include academic references, as links or brief quotes, which back up your ideas. That kind of stuff impresses us. On the other hand, do <i>not</i> include 15 pages of reference materials; we won't read it. Summarize.
</p><p>
<strong>Be Known:</strong> If you know anyone in open source who can vouch for your code quality
and/or diligence, use them as a reference.
</p><p>
<strong>Begin:</strong> Projects related to research already in progress at your school are good; it allows us to evaluate your approach, as well as giving us the assurance that you are serious about your topic and have already done background work.
</p><p>
<strong>Be Involved:</strong> Several students have already pitched their ideas to the pgsql-hackers mailing list. We like this; it shows that the student already understands how our community works, and is more likely to get their patches accepted.
</p><p>
<strong>Be Early:</strong> We expect to receive 50 to 100 applications for five to eight spots. Applications which we get on the first day of the application period will get more attention from the mentors, and thus more chance of being accepted, than applications which show up on the last day.
</p><p>
<strong>Be Specific:</strong> Your proposal should include specific, well-defined deliverables and timelines. "Fix the query planner" is bad. "I expect to take 10 weeks implementing a new n-distict algorithm for better rowcount estimation and integrating it into the PostgreSQL planner." is good.
</p><p>
<strong>Be Bold:</strong> suggest innovative and ambitious approaches to solve hard
problems. Ultimately, we're looking for new major contributors for our
projects and a bold proposal makes us think you might be a candidate. Yes,
we offered up the TODO list as ideas, but stuff that we'd never thought of
before got moderated up even if it didn't get accepted.
</p><p>
<strong>Be Realistic:</strong> SoC requires you to <i>complete</i> a project in 3 months or less. So don't be so bold that your proposal can't be finished. One proposal we
rejected almost immediately said "As a whole, I think this idea is too large
to be pulled off by one person in 3 months." We agreed.
</p><p>
<strong>Be Original:</strong> Many students submitted nearly-identical proposals based on
recent "hot" papers on ACM and similar academic publications. For example,
we got 3 separate proposals for an XML datatype using CTrees. If you do make
a proposal based on a current "hot area" in CS/DBMS design, the make sure to
make another unrelated proposal as well, because you'll have plenty of
competitors.
</p>
[text/html] summerofcode.html (8.2K, 3-summerofcode.html)
download | inline:
<div id="CONTENTWRAP">
<h1>PostgreSQL Summer Projects</h1>
<p>The PostgreSQL Project is excited to take part in the Google <a
href="http://code.google.com/summerofcode.html">Summer of Code 2007</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>
<li><a href="#past">Previously Accepted Projects</a></li>
<li><a href="#faq">Frequently Answered Questions</a></li>
</ul>
<a id="ideas" name="ideas"></a>
<h2>Example Proposal Ideas</h2>
<p>The PostgreSQL Project has a wide range of opinions on what it feels are acceptable SoC 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 thier 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://wwwmaster.postgresql.org/docs/faqs.TODO.html">TODO</a> list, they will be marked with a percent sign (%).
</li>
<li><strong>PITR Improvements</strong>: Allow point-in-time recovery to archive partially filled write-ahead logs and automatically archiving them when pg_stop_backup() is called or the server is shutdown. Allow stand-by server to allow read-only queries to be run concurrently while replaying wal logs</li>
<li><strong>ECPG Enhancments</strong>: Enable ECPG to generate calls directly for libpq rather than calls to its own libraries.</li>
<li><strong>DDL Functions</strong>: Create a SQL-callable function capable of generating DDL scripts for objects within the database.</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 continuosly 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>
</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 thier own TODO lists and compatability issues with the core PotgreSQL that need development.</li>
<li><strong>Procedural Language Improvments</strong>: PostgreSQL provides support for more than a dozen different procedural languaes, however the level of support varies depending on the language implementation. Enhancing support of these procedual 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 assistence with building against different versions of PostgreSQL, installation and setup, administrative tools, and general bugfixing.</li>
</ul>
<p>Additional projects may be found by browsing the <a href="http://projects.postgresql.org">PostgreSQL Development Projects</a> website.</p>
<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 liasons below about writing a proposal.</p>
<ul>
<li>Andrew Dunstan (andrew @t dunslane.net), PostgreSQL Community, USA</li>
<li>Dave Page (dpage @t pgadmin.org), EnterpriseDB, England</li>
<li>Josh Berkus (josh @t agliodbs.com), Sun Microsystems, USA</li>
<li>Oleg Bartunov (oleg @t sai.msu.su), DeltaSoft, Russia </li>
<li>Robert Treat (xzilla @t users.sourceforge.net), OmniTI Inc., USA</li>
<li>Zdenec Kotala (zdenec.kotata @t sun.com), Sun Microsystems, Czech Republic</li>
<li>Mark Wong (markwm @t gmail.com), PosrgreSQL benchmarking, USA</li>
</ul>
<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:[email protected]">[email protected]</a>.</p>
<a id="proposals" name="proposals"></a>
<h2>Proposal Guidelines</h2>
<p>Students are responsible for writing a proposal and submitting it to Google before the
application deadline. The following outline was adapted from the Perl Foundation <a
href="http://www.perlfoundation.org/gc/grants/proposals.html">open source proposal
HOWTO</a>. A strong proposal will include:</p>
<ul>
<li><strong>Benefits to the PostgreSQL Community</strong> - a good project will not just be
fun to work on, but also generally useful to others.</li>
<li><strong>Deliverables</strong> - It is very important to list quantifiable results
here</li>
<li><strong>Project Schedule</strong> - How long will the project take? When can you
begin work?</li>
<li><strong>Bio</strong> - Who are you? What makes you the best person to work on this
project?</li>
</ul>
Please also see our additional <a href="/developer/summerofcodeadvice.html/">Advice to Students</a> <strong>before</strong> submitting a proposal.
<p>We would prefer that development discussion occur on our project mailing lists when possible, with special recognition being given to those students who vett thier proposal with community developers before submitting thier proposal to Google SoC. This is not required, but can have a largeimpact on the chances of your proposal being accepted, so please don't be shy. In any case, you will be required to keep open lines of communication with your mentor should you be accepted, so if you have circumstances that may effect this, please explain them up front in your proposal.</p>
<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 improvements</li>
<li>xlog viewer</li>
</ul>
<p>More information on these projects can be found on Google's <a href="http://code.google.com/soc/pgsql/about.html">PostgreSQL SoC page</a>.</p>
<a id="faq" name="faq"></a>
<h2>Frequently Asked Questions</h2>
<ul>
<li>
<p><strong>Am I eligible?</strong></p>
<p>Please see the Google <a href="http://code.google.com/summfaq.html">Participant
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://code.google.com/soc/studentfaq.html">Google Summer of Code page</a>, the deadline for submitting student proposals is March 24th, 2007. 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>
</div>
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: Updated summerofcode pages
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox