Browse Source

New directory gsoc2012 added to org-contrib/ with 5 files related to
orgmodes participation in Google's Summer of Code 2012

tj 8 years ago
parent
commit
777becb689

+ 198 - 0
org-contrib/gsoc2012/orgmode-gsoc2012-admin.org

@@ -0,0 +1,198 @@
+#+OPTIONS:    H:3 num:nil toc:2 \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate hideblocks
+#+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c) noexport(n)
+#+TITLE:      Google Summer of Code (GSoC) 2012
+#+AUTHOR:     Thorsten Jolitz
+#+EMAIL:      tj[at]data-driven[dot]de
+#+LANGUAGE:   en
+#+STYLE:      <style type="text/css">#outline-container-introduction{ clear:both; }</style>
+#+LINK_UP:    ./orgmode-gsoc2012-main.php
+#+LINK_HOME:  http://orgmode.org/worg/
+#+EXPORT_EXCLUDE_TAGS: noexport
+
+
+#+name: banner
+#+begin_html
+  <div id="subtitle" style="float: center; text-align: center;">
+  <p>
+  Org Mode info-page for GNU's application to  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012">GSoC 2012</a>
+  </p>
+  <p>
+  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012"/>
+  <img src="http://t1.gstatic.com/images?q=tbn:ANd9GcRbAgQorAr3evNbItUq1iaF53LzPknqMme1frngxXS4XHpP1LWsBw" />
+  </a>
+  </p>
+  </div>
+#+end_html
+
+
+
+* Org Mode GSoC 2012 Admin Page
+
+#+BEGIN_QUOTE
+This page is selected content copied&pasted from Google's excellent [[http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/faqs][faq]]
+page. It summarizes all the information relevant for GSoC 2012
+organisation admins. "We" in the following text stands for "Google",
+not for "Org Mode" or "GNU". 
+#+END_QUOTE
+
+We'll begin accepting applications from open source mentoring
+organizations on February 27, 2012; we'll stop accepting organization
+applications on March 9th at 23:00 UTC.
+
+
+** What is a mentoring organization?
+
+A group running an active free/open source software project, e.g. the
+Python Software Foundation. The project does not need to be a legally
+incorporated entity. If you're looking for a broader picture, you can
+find a list of all mentoring organizations who have participated in
+the past on the Google Summer of Code 2005, 2006, 2007, 2008, 2009,
+2010, and 2011 pages. Mentoring organizations must produce and release
+software under an Open Source Initiative approved license in order to
+participate in the program. Mentors for their organizations must at
+least be committers for the corresponding project and their
+participation in Google Summer of Code on the organization’s behalf
+must be approved by the organization administrator via Melange.
+
+** What is the role of a mentoring organization?
+
+Each mentoring organization is expected to provide:
+
+ + A pool of project ideas for students to choose from, publicly
+   published by the mentoring organization as an Ideas list
+ 
+ + An organization administrator to act as the project's main point of
+   contact for Google
+ 
+ + A person or group responsible for review and ranking of student
+   applications, both those proposals which tie into the org's Ideas
+   list and "blue-sky" proposals
+  
+ + A person or group of people responsible for monitoring the progress
+   of each accepted student and to mentor her/him as the project
+   progresses
+
+ + A person or group responsible for taking over for a student's
+   assigned mentor in the event they are unable to continue mentoring,
+   e.g. take a vacation, have a family emergency
+ 
+ + A written evaluation of each student participant, including how
+   s/he worked with the group, whether you would want to work with
+   them again
+
+
+In addition to these responsibilities, a mentoring organization should
+actively encourage each student developer to participate in the
+project's community in whichever way makes the most sense for the
+project, be it development mailing lists, idling in the project's IRC
+channel, participating in the project's forum, etc. A truly successful
+mentoring organization will work diligently to ensure that as many of
+their students as possible remain active project participants long
+after the conclusion of the program.
+
+** What is the role of an organization administrator?
+
+An organization administrator oversees the overall progress of a
+mentoring organization and its students throughout the program.
+Organization administrators will have different responsibilities
+depending on the organization, but at the very least they will need
+to:
+
+1. Submit the organization's program application to Google
+2. Act as the main point of contact between Google and the organization
+3. Respond to any inquiries from Google within 48 hours
+4. Assign a back up mentor should a mentor be unable to work with a student
+5. Ensure all program evaluations are completed on time on or before the deadlines
+
+For some projects, the organization administrator also acted as an
+arbiter when disputes arose between students and mentors, but each
+project should individually decide how such situations should be
+handled.
+
+** Can a mentoring organization have more than one administrator?
+
+Yes, in fact it is required. It's good to have a back-up administrator
+identified who can cover for your administrator should s/he go out of
+town, etc. If your back-up administrator becomes the primary
+administrator, make sure to notify Google's program administrators.
+
+** What kind of mentoring organizations should apply?
+
+As you can see from the lists of our mentoring organizations for 2005,
+2006, 2007, 2008, 2009, 2010, and 2011 many different types of open
+source projects participate in Google Summer of Code. As long as your
+project can provide mentors and is releasing code under an Open Source
+Initiative approved license, you are welcome and encouraged to apply.
+Unfortunately, there are far more great open source projects than we
+can work with, so if your project is highly niche or has very few
+users, chances are that your application will not be accepted.
+
+** When will accepted mentoring organizations be announced?
+
+We will announce the list of accepted mentoring organizations on the
+Google Summer of Code 2012 homepage on March 16, 2012.
+
+** Are mentoring organizations required to use the code produced?
+
+No. While we hope that all the code that comes out of this program
+will find a happy home, we're not requiring organizations to use the
+students' code.
+
+** What are the eligibility requirements for mentoring organizations?
+
+Mentor organizations must be organizations or individuals running an
+active and viable open source or free software project whose
+applications are approved by Google's Open Source Programs Office.
+Organizations based in Iran, Syria, Cuba, Sudan, North Korea and
+Mynamar (Burma), with whom we are prohibited by U.S. law from engaging
+in commerce, are ineligible to participate.
+
+** Who owns the code produced by student developers?
+
+Each student (or her/his mentoring organization) must license all
+student Google Summer of Code code under an Open Source Initiative
+approved license palatable to the mentoring organization. Some
+organizations will require students to assign copyright to them, but
+many will allow them to retain copyright. If Google is a student's
+sponsoring organization, then the student keeps copyright to her/his
+code.
+
+** What licenses do I have choose from?
+
+That depends on your mentoring organization. All code created by
+student participants must be released under an Open Source Initiative
+approved license. It's also extremely likely that your mentoring
+organization will have a preferred license(s) and that you will need
+to release your code under the license(s) chosen by that organization.
+
+** Isn't it unusual for open source developers to be paid?
+
+Not really. Many of our mentors get paid to work on open source. Some
+run their own consultancies, others tinker for some cash on the side,
+others work for large companies. That said, we do know it is tricky to
+introduce cash into the mix of Free and Open Source, but that is why
+we're working with external organizations with years of collective
+experience in this kind of thing.
+
+
+** What tax related documentation is required from mentoring organizations?
+
+
+We will need the following tax related documentation from mentoring
+organizations or umbrella organizations:
+
+   + For organizations based in the United States, we will need a
+     completed IRS form W9.
+   
+   + For organizations based outside the United States, we will need a
+     completed IRS form W8-BEN.
+
+
+All organizations are paid via purchase order from Google, which will
+require registering as a vendor in our payments system. Detailed
+instructions for registering as a vendor and invoicing Google for
+payment will be sent to the private mentors' mailing list. We will
+need to have all required documentation on file before issuing payment
+to a particular mentoring organization.

+ 107 - 0
org-contrib/gsoc2012/orgmode-gsoc2012-ideas.org

@@ -0,0 +1,107 @@
+#+OPTIONS:    H:4 num:nil toc:2 \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate hideblocks
+#+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c) noexport(n)
+#+TITLE:      Google Summer of Code (GSoC) 2012
+#+AUTHOR:     Thorsten Jolitz
+#+EMAIL:      tj[at]data-driven[dot]de
+#+LANGUAGE:   en
+#+STYLE:      <style type="text/css">#outline-container-introduction{ clear:both; }</style>
+#+LINK_UP:    ./orgmode-gsoc2012-main.php
+#+LINK_HOME:  http://orgmode.org/worg/
+#+EXPORT_EXCLUDE_TAGS: noexport
+
+
+#+name: banner
+#+begin_html
+  <div id="subtitle" style="float: center; text-align: center;">
+  <p>
+  Org Mode ideas for GNU's application to  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012">GSoC 2012</a>
+  </p>
+  <p>
+  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012"/>
+  <img src="http://t1.gstatic.com/images?q=tbn:ANd9GcRbAgQorAr3evNbItUq1iaF53LzPknqMme1frngxXS4XHpP1LWsBw" />
+  </a>
+  </p>
+  </div>
+#+end_html
+
+
+* Org Mode GSoC 2012 Ideas Page
+
+**  What is an Ideas list?
+
+An Ideas list should be a list of suggested student projects. This
+list is meant to introduce contributors to your project's needs and to
+provide inspiration to would-be student applicants. It is useful to
+classify each idea as specifically as possible, e.g. "must know
+Python" or "easier project; good for a student with more limited
+experience with C++." If your organization plans to provide an
+application template, it would be good to include it on your Ideas
+list.
+
+Keep in mind that your Ideas list should be a starting point for
+student applications; we've heard from past mentoring organization
+participants that some of their best student projects are those that
+greatly expanded on a proposed idea or were blue-sky proposals not
+mentioned on the Ideas list at all. A link to a bug tracker for your
+open source organization is NOT an ideas list.
+
+
+** Org Mode project ideas for GSoC 2012
+*** Org Babel
+**** Real webprogramming with Org Mode and PicoLisp
+[[http://picolisp.com/5000/!wiki?home][PicoLisp]] is one out of many [[http://orgmode.org/worg/org-contrib/babel/languages.html][Org Babel languages]], but may be special in
+the sense that it does not only contribute to the static
+webpublishing capacities, but may introduce dynamic webprogramming on
+top of a real database into Org Mode. 
+
+Real interactive webprogramming frequently involves a (SQL) database
+like MySQL, a programming language like PHP or Python to build a MVC
+(Model-View-Controller) application on top of the database, a web
+framework for that programming language to make the programmers life
+easier (e.g. Django for Python), and a persistence layer that abstract
+away the conceptual mismatch between the SQL database and the (mostly)
+object-oriented application. Sometimes, a WYSIWYG html editor like MS
+Frontpage is invovled too, when webdesigners design the UI of the
+application. 
+
+Such an application needs user input (via <form> or <input> elements
+in the html pages) and needs to adapt dynamically to the users actions
+and queries by updating either the whole page or only parts of it
+(Javascript). For each user, a session is needed to keep track of the
+state of the application during his/her visit. 
+
+This kind of dynamic webprogramming can't be done with Org Mode.
+Typical webpages made with Org Mode are static in nature, even if they
+update their content frequently with some cron jobs on the server.
+There is no interaction with the user. 
+
+Considering the web stack for dynamic web apps described
+above, Org Mode really functions as a kind of 'Frontpage on steroids'
+for highly skilled academics. The project idea is to let PicoLisp
+replace all the other elements of the webstack and combine Org Mode
+and PicoLisp into an entirely Lisp-based framework for dynamic web
+programming. 
+
+In the PicoLisp application framework, UI and database are unified.
+Database objects are first class members of the language, and the UI
+elements act directly on this object-oriented lisp database (that is
+fast and scalable). No external SQL storage is needed, no persistence
+layer between the relational world of the DB and the object-oriented
+world of the application, and no glue code (controller) that connects
+the view to the model. 
+
+By merging PicoLisp's framework for rapid web-application development
+with Org Modes framework for rapid (web-) content production via Org
+Babel, new kinds of websites produced with Org Mode should become
+possible. 
+
+**** YOUR ORG BABEL PROJECT IDEA HERE
+
+*** ANOTHER TOPIC
+**** MORE PROJECT IDEAS
+**** MORE PROJECT IDEAS
+
+
+

+ 99 - 0
org-contrib/gsoc2012/orgmode-gsoc2012-main.org

@@ -0,0 +1,99 @@
+#+OPTIONS:    H:3 num:nil toc:2 \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate hideblocks
+#+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c) noexport(n)
+#+TITLE:      Google Summer of Code (GSoC) 2012
+#+AUTHOR:     Thorsten Jolitz
+#+EMAIL:      tj[at]data-driven[dot]de
+#+LANGUAGE:   en
+#+STYLE:      <style type="text/css">#outline-container-introduction{ clear:both; }</style>
+# #+LINK_UP:  http://orgmode.org/worg/org-faq.html
+#+LINK_HOME:  http://orgmode.org/worg/
+#+EXPORT_EXCLUDE_TAGS: noexport
+
+
+#+name: banner
+#+begin_html
+  <div id="subtitle" style="float: center; text-align: center;">
+  <p>
+  Org Mode info-page for GNU's application to  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012">GSoC 2012</a>
+  </p>
+  <p>
+  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012"/>
+  <img src="http://t1.gstatic.com/images?q=tbn:ANd9GcRbAgQorAr3evNbItUq1iaF53LzPknqMme1frngxXS4XHpP1LWsBw" />
+  </a>
+  </p>
+  </div>
+#+end_html
+
+
+* Google Summer of Code 2012
+** How Google describes it
+Google Summer of Code is a program that offers student developers
+stipends to write code for various open source projects (see the [[http://www.google-melange.com/gsoc/homepage/google/gsoc2012][faq]]
+for more information).
+
+Google Summer of Code has several goals:
+
+- Create and release open source code for the benefit of all
+- Inspire young developers to begin participating in open source development
+- Help open source projects identify and bring in new developers and committers
+- Provide students the opportunity to do work related to their
+  academic pursuits (think "flip bits, not burgers")
+- Give students more exposure to real-world software development
+  scenarios (e.g., distributed development, software licensing
+  questions, mailing-list etiquette)
+
+** Org Mode participates in GNU's application
+This year, the Org Mode community will participate with project ideas
+for GNU's application as mentoring organisation. 
+
+Students will love the opportunity to contribute to a software they
+might use on a daily basis anyway. Org Mode is not only one out of
+many interesting open-source projects out there, it is a software tool
+custom-made for the needs of students (and scientists in general).
+
+They can use Org Mode for organising their life, their studies and
+their finances. They can write their research papers with it as well
+as publish their website. Not to mention their spreadsheet
+calculations and their (literate) programming work in some 30 Org
+Babel languages. And they can do all this with the unsurpassed
+efficiency only offered by the combination of Emacs & Org Mode. 
+
+Working on an Org Mode project this summer not only will make the
+students better (Emacs) Lisp programmers, it will make them better
+students too, since skilled Elisp programmers are Emacs power users by
+definition and can make the most out of their exceptionally powerfull
+software tool. 
+
+The students will have the exciting opportunity to join one of the
+most dynamic open-source projects today with a big, active, skilled
+and very helpfull community. Since the Org Mode project is in such a
+dynamic momentum, there are plenty of usefull ideas for student
+projects around. In fact, some long desired features for Org Mode
+might finally be realized through students projects during the
+GSoC 2012.
+
+** Mentors, students and ideas
+Org Mode contributers that are not students anymore, but would like to
+see some of their ideas with regards to Org Mode come true, are
+invited to post these ideas on the [[orgmode-gsoc2012-ideas.org][ideas page]] and apply as mentors.
+Students are encouraged to either apply for one of the proposed
+projects on the ideas page or submit their own ideas and ask one of
+the experienced Org Mode contributors if he would like to mentor their
+project.
+
+** Info pages
+Although all related information can be found on the [[http://www.google-melange.com/gsoc/homepage/google/gsoc2012][GSoC 2012]] home
+page, we prepared an [[file:orgmode-gsoc2012-admin.org][admin page]], a [[file:orgmode-gsoc2012-mentor.org][mentor page]] and a [[orgmode-gsoc2012-student.org][student page]] that
+only gives the information relevant for the respective group. 
+
+The most important page is the [[orgmode-gsoc2012-ideas.org][ideas page]]. Since the application
+process is a two step process, first the organisation (GNU), then the
+students, all student projects depend on the successfull application
+of the mentoring organisation. 
+
+Therefore we should try to build a nice ideas page, grouping the
+proposals by topics, with a description for each idea. It
+would be nice to associate each idea with a mentor too. 
+

+ 121 - 0
org-contrib/gsoc2012/orgmode-gsoc2012-mentor.org

@@ -0,0 +1,121 @@
+#+OPTIONS:    H:3 num:nil toc:2 \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate hideblocks
+#+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c) noexport(n)
+#+TITLE:      Google Summer of Code (GSoC) 2012
+#+AUTHOR:     Thorsten Jolitz
+#+EMAIL:      tj[at]data-driven[dot]de
+#+LANGUAGE:   en
+#+STYLE:      <style type="text/css">#outline-container-introduction{ clear:both; }</style>
+#+LINK_UP:    ./orgmode-gsoc2012-main.php
+#+LINK_HOME:  http://orgmode.org/worg/
+#+EXPORT_EXCLUDE_TAGS: noexport
+
+
+#+name: banner
+#+begin_html
+  <div id="subtitle" style="float: center; text-align: center;">
+  <p>
+  Org Mode info-page for GNU's application to  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012">GSoC 2012</a>
+  </p>
+  <p>
+  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012"/>
+  <img src="http://t1.gstatic.com/images?q=tbn:ANd9GcRbAgQorAr3evNbItUq1iaF53LzPknqMme1frngxXS4XHpP1LWsBw" />
+  </a>
+  </p>
+  </div>
+#+end_html
+
+
+* Org Mode GSoC 2012 Mentor Page
+
+#+BEGIN_QUOTE
+This page is selected content copied&pasted from Google's excellent [[http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/faqs][faq]]
+page. It summarizes all the information relevant for GSoC 2012
+mentors. "We" in the following text stands for "Google",
+not for "Org Mode" or "GNU". 
+#+END_QUOTE
+
+** How do evaluations work?
+
+Google will pre-publish the evaluation questions for both students and
+mentors. Mentors will fill out mid-term and final evaluations for
+their students via the Google Summer of Code 2012 site. These
+evaluations will be visible in the system to the mentor and the
+mentoring organization's administrator(s). Students will fill out a
+mid-term and final evaluation of their mentors online as well, and
+their evaluations will only be visible in the system to the mentoring
+organization's administrator(s). Program administrators from Google
+will have access to all evaluation data.
+
+Any student who does not submit an evaluation by the evaluation
+deadline will fail that evaluation, regardless of the grade the mentor
+gives the student. If a student submits his or her evaluation on time
+but the mentor does not, then the student is in an “undecided” state
+until the program administrators can speak to the mentor and determine
+the student’s grade.
+
+Students who fail the mid-term are immediately removed from the
+program: it’s not possible to fail the mid-term, stay in the program,
+and then have a final evaluation.
+
+In almost all cases, students will never see their mentor's evaluation
+of their progress, nor will a mentor see a student's evaluation of
+her/his mentorship. However, in the case where the mentoring
+organization's administrator and a student's mentor are one and the
+same, the student's evaluation will be shared with the mentor. If you
+are a student in a situation where your mentor is also your
+organization’s administrator and you would like to discuss an issue
+with the program, please contact the Google Summer of Code program
+administrators. Organization administrators are expected to review
+mid-term and final evaluations and to provide course corrections where
+necessary. In some cases, Google's program administrators may need to
+share the results of evaluations with the student and mentor, such as
+to arbitrate when payment should not be made. Should this need arise,
+all parties will be notified in advance.
+
+In the unlikely event that a mentor and organization administrator do
+not agree on a student’s grade for any evaluation, the decision of the
+organization administrator is the final one.
+
+In the also unlikely event that a student does not agree with a
+mentoring organization’s evaluation decision at either the midterm or
+the final, the student may choose to submit his/her entire project
+plan, timeline and code sample to Google’s program administrators.
+Google will choose an independent engineer to review the code and
+arbitrate the decision. The decision of Google’s independent engineer
+is final.
+
+Finally, any mentor who misses a deadline for an evaluation of his/her
+student without notifying the program administrators beforehand will
+not be allowed to attend the Google Summer of Code mentor summit.
+Timely evaluations of Google Summer of Code students are crucial to
+us.
+
+** What are the eligibility requirements for mentors?
+
+Google does not have specific eligibility requirements for mentors, as
+we know our mentoring organizations will be best able to determine the
+selection criteria for their mentors.
+
+** I would like to participate in Google Summer of Code as both mentor and a student. Is this possible?
+
+We've given this question a lot of thought, and we've decided it is
+best not to allow participants to act as a mentor to another Google
+Summer of Code student while they are working on their own Google
+Summer of Code student project. We want to make sure that each project
+and student receives sufficient attention, and we're concerned that
+this split in focus could create a bad experience for those involved.
+Please choose whether participation as a mentor or a student is more
+appealing to you and plan to apply accordingly.
+
+** How much time is required to participate as a mentor in Google Summer of Code?
+
+While the answer to this question will vary widely depending on the
+number of students a mentor works with, the difficulty of the
+proposals, and the skill level of the students, most mentors have let
+us know that they underestimated the amount of time they would need to
+invest in Google Summer of Code. Five hours per student per week is a
+reasonable estimate.
+
+

+ 124 - 0
org-contrib/gsoc2012/orgmode-gsoc2012-student.org

@@ -0,0 +1,124 @@
+#+OPTIONS:    H:3 num:nil toc:2 \n:nil @:t ::t |:t ^:{} -:t f:t *:t TeX:t LaTeX:t skip:nil d:(HIDE) tags:not-in-toc
+#+STARTUP:    align fold nodlcheck hidestars oddeven lognotestate hideblocks
+#+SEQ_TODO:   TODO(t) INPROGRESS(i) WAITING(w@) | DONE(d) CANCELED(c@)
+#+TAGS:       Write(w) Update(u) Fix(f) Check(c) noexport(n)
+#+TITLE:      Google Summer of Code (GSoC) 2012
+#+AUTHOR:     Thorsten Jolitz
+#+EMAIL:      tj[at]data-driven[dot]de
+#+LANGUAGE:   en
+#+STYLE:      <style type="text/css">#outline-container-introduction{ clear:both; }</style>
+#+LINK_UP:    ./orgmode-gsoc2012-main.php
+#+LINK_HOME:  http://orgmode.org/worg/
+#+EXPORT_EXCLUDE_TAGS: noexport
+
+
+#+name: banner
+#+begin_html
+  <div id="subtitle" style="float: center; text-align: center;">
+  <p>
+  Org Mode info-page for GNU's application to  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012">GSoC 2012</a>
+  </p>
+  <p>
+  <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2012"/>
+  <img src="http://t1.gstatic.com/images?q=tbn:ANd9GcRbAgQorAr3evNbItUq1iaF53LzPknqMme1frngxXS4XHpP1LWsBw" />
+  </a>
+  </p>
+  </div>
+#+end_html
+
+
+* Org Mode GSoC 2012 Student Page
+
+#+BEGIN_QUOTE
+This page is selected content copied&pasted from Google's excellent [[http://www.google-melange.com/document/show/gsoc_program/google/gsoc2012/faqs][faq]]
+page. It summarizes all the information relevant for GSoC 2012
+students. "We" in the following text stands for "Google",
+not for "Org Mode" or "GNU". 
+#+END_QUOTE
+
+The student application period begins March 26, 2012 and ends April
+6th at 19:00 UTC. 
+
+** How does a student apply?
+
+Students can submit their applications via the Google Summer of Code
+2012 site from March 27 - April 9, 2012. We hear almost universally
+from our mentoring organizations that the best applications they
+receive are from students who took the time to interact and discuss
+their ideas before submitting an application, so make sure to check
+out each organization's Ideas list to get to know a particular open
+source organization better. In addition to an application, students
+will be required to sign a Student Participation Agreement.
+
+** What should a student application look like?
+
+Your application should include the following: your project proposal,
+why you'd like to execute on this particular project, and the reason
+you're the best individual to do so. Your proposal should also include
+details of your academic, industry, and/or open source development
+experience, and other details as you see fit. An explanation of your
+development methodology is a good idea, as well. It is always helpful
+to include contact information as well, as it will not be
+automatically shared with your would-be mentors as part of the
+application process. If the organization you want to work with has a
+specific application template they would like you to use, it will be
+made available to you to fill in when submitting your proposal via the
+Google Summer of Code web app. [note: the PicoLisp community has not
+specific application template]
+
+** Can a student submit more than one application?
+
+Yes, each student may submit up to twenty applications. However, only
+one application will be accepted. We've heard from our mentoring
+organizations that quality is better than quantity.
+
+** Can students already working on an open source project continue to work on it as part of Google Summer of Code?
+
+Yes, as long as they meet all other requirements for program
+eligibility. Students should be sure to note their previous
+relationship with the project in their applications. New work will
+need to be done for the project as part of participation in Google
+Summer of Code.
+
+** Should students begin working on their applications before Google begins accepting program applications?
+
+That's up to you. Keep in mind, though, that our mentoring
+organizations will be publishing a list of proposed project ideas, so
+you may find that you'll want to revamp your application later, or
+create an entirely new one to address one of those ideas.
+
+** Can a student work on more than one project?
+
+No, each participant may only work on one project and is only eligible
+for one stipend.
+
+** Can a group apply for and work on a single proposal?
+
+No, only an individual may work on a given project.
+
+** What happens if two students are accepted to work on the same project, e.g. from an organization's Ideas list?
+
+That's fine, a little duplication is par for the course in open
+source.
+
+** Are proposals for documentation work eligible for Google Summer of Code?
+
+While we greatly appreciate the value of documentation, this program
+is an exercise in developing code; we can't accept proposals for
+documentation-only work at this time.
+
+** How do payments work?
+
+Google will provide a stipend of 5500 USD per accepted student
+developer, of which 5000 USD goes to the student and 500 USD goes to
+the mentoring organization.
+
+Accepted students in good standing with their mentoring organization
+will receive a 500 USD stipend shortly after coding begins on May
+21, 2012. Students who receive passing mid-term evaluations will
+receive a 2250 USD stipend shortly after the mid-term evaluation
+deadline, July 13, 2012. Students who receive passing final
+evaluations and who have submitted their final program evaluations
+will receive a 2250 USD stipend shortly after the final evaluation
+deadline, August 24, 2012. Mentoring organizations must request their
+payments of 500 USD per student mentored by November 5, 2012.