web commit by JoshTriplett: Template of Google Summer of Code application, with first pass at content.

1 files changed, 80 insertions, 0 deletions

diff --git a/doc/soc/application.mdwn b/doc/soc/application.mdwn
new file mode 100644
index 000000000..8db54c55a
--- /dev/null
+++ b/doc/soc/application.mdwn
@@ -0,0 +1,80 @@
+Based on ["What should a mentoring organization application look like?"](http://code.google.com/support/bin/answer.py?answer=60303).
+
+1. **Describe your organization.**
+
+    The ikiwiki project aims to develop a general-purpose wiki, with particular emphasis on personal wikis, project wikis, blogs, and collaborative software development.  We provide several features unique or uncommon amongst wikis:
+
+    * Rather than inventing yet another simplistic, linear revision control system, ikiwiki makes use of standard version control systems such as [[Subversion]] and [[Git]].  You can edit a wiki by committing to your repository, as well as through a traditional web interface.  This makes ikiwiki ideal for collaborative software development; just keep your wiki in version control next to your software.  You can also take advantage of the features of these systems; for instance, you can keep a local branch of your wiki via [[Git]].
+
+    * You can turn any set of pages into an inline news feed, complete with RSS and Atom support.  You can run your weblog on ikiwiki (and many people do), run a Planet-like aggregator for external feeds, or keep a TODO and bug list with tags for completed items.
+
+    * ikiwiki provides a wiki compiler, designed to transform your wiki content into a set of static pages.  You can then serve these pages as static content.  ikiwiki will not fall over during a Slashdotting, because page views don't require the ikiwiki CGI; as long as Apache can keep up, your site will survive.  Furthermore, you can choose whether you want to run the ikiwiki CGI for web edits or only handle commits to the underlying version control system; you can even run ikiwiki privately and just manually copy the content to another server.  So if you want to put a wiki up on a server without installing any software on that server, try ikiwiki.
+
+2. **Why is your organization applying to participate in GSoC 2007? What do you hope to gain by participating?**
+
+    ikiwiki has had a strong positive response from several communities of software developers.  We believe we have filled a genuine need, unaddressed by previous software.  Many users have begun to take ikiwiki in unexpected directions, using it in ways we had not previously envisioned.
+
+    Thus, we believe ikiwiki has reached a stage where it would greatly benefit from more widespread exposure to the ingenuity of other developers.
+
+    Furthermore, we have a good list of existing projects on our TODO list.  The nature of ikiwiki, with its highly capable plugin system and broader focus than most wikis, results in far more ideas than implementation time.  We have a well-managed TODO list, ranging from minor items to major projects.  We would greatly appreciate contributions toward some of our more substantial feature ideas.  We believe we have a very low barrier to contribution.
+
+3. **Did your organization participate in GSoC 2005 or 2006? If so, please summarize your involvement and the successes and failures of your student projects.**
+
+    ikiwiki has not previously participated in Google Summer of Code.  
+
+4. **If your organization has not previously participated in GSoC, have you applied in the past? If so, for what year(s)?**
+
+    ikiwiki has not previously applied for Google Summer of Code.
+
+5. **Who will your organization administrator be? Please include Google Account information.**
+
+
+
+6. **What license does your project use?**
+
+    ikiwiki uses the GNU General Public License.  The basewiki, incorporated into users' wikis, uses an all-permissive license.  See [[FreeSoftware]] for details.
+
+7. **What is the URL for your ideas page?**
+
+    <http://ikiwiki.info/soc.html>
+
+8. **What is the main development mailing list for your organization?**
+
+    The ikiwiki project strongly encourages collaboration through ikiwiki itself, and thus does not have a mailing list.
+    Anyone can create an account on ikiwiki's own ikiwiki.  ikiwiki provides a bug tracker, a TODO list, and the ability
+    to create a weblog on any page.  ikiwiki also includes "discussion" sub-pages on every page.  The developers and mentors
+    monitor RecentChanges closely, both via the webpage and and will respond in a timely fashion.
+
+9. **What is the main IRC channel for your organization?**
+
+    #ikiwiki on OFTC.
+
+10. **Does your organization have an application template you would like to see students use? If so, please provide it now.**
+
+    No application template needed.
+
+11. **Who will be your backup organization administrator? Please include Google Account information.**
+
+
+
+12. **Who will your mentors be? Please include Google Account Information.**
+
+
+
+13. **What criteria did you use to select these individuals as mentors? Please be as specific as possible.**
+
+
+
+14. **What is your plan for dealing with disappearing students?**
+
+
+
+15. **What is your plan for dealing with disappearing mentors?**
+
+
+
+16. **What steps will you take to encourage students to interact with your project's community before, during and after the program?**
+
+
+
+17. **What will you do to ensure that your accepted students stick with the project after GSoC concludes?**