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:
+ The ikiwiki project aims to develop a general-purpose wiki engine, 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]].
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
+ Anyone can create an account on ikiwiki's own wiki. 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.
+ monitor RecentChanges closely, via the webpage, email, and [CIA](http://cia.navi.cx), and will respond in a timely fashion.
9. **What is the main IRC channel for your organization?**
- #ikiwiki on OFTC.
+ `#ikiwiki` on OFTC.
10. **Does your organization have an application template you would like to see students use? If so, please provide it now.**
16. **What steps will you take to encourage students to interact with your project's community before, during and after the program?**
+ Before the program, we will encourage any students interested in working on ikiwiki to contact us. We will advise them to create an account on the ikiwiki ikiwiki, look over the TODO items, add ideas of their own, and discuss existing ideas. We will also help them set up their own ikiwikis, both for experimentation and for actual use. We will suggest that students begin looking at the ikiwiki codebase and asking questions.
+ During the program, we would like all students working on projects to create a user page with an activity blog, and update that blog regularly with the status of their project. We will accept incremental patches towards a feature, or support students who wish to create their own branch.
+
+ After the program, we will continue to work towards integrating any projects that have not yet completed, and talk with students about their future plans regarding ikiwiki. If the students have started using ikiwiki for their own wikis, as we hope they will after we encourage them to experiment with it, then they will likely have a vested interest in ongoing ikiwiki development. Thus, we will encourage them to remain active by helping them become active and interested users.
17. **What will you do to ensure that your accepted students stick with the project after GSoC concludes?**
sipb-www / ikiwiki.git / blobdiff