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]].
+ * Rather than inventing yet another simplistic, linear revision control system, ikiwiki uses a standard version control system such as [[Subversion]] or [[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.
14. **What is your plan for dealing with disappearing students?**
-
+ We will strongly encourage 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 use these blogs to closely monitor the progress of each student on their projects. If a student mentions problems they have encountered, we will work with them to resolve those problems. If we see no activity from a student for longer than their usual status-reporting interval, we will check with them directly to determine their status.
15. **What is your plan for dealing with disappearing mentors?**
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.
+ 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 also plan to aggregate these blogs into a single Summer of Code newsfeed, and suggest that students subscribe to this feed; this will allow them to observe the activity of their fellow students, to spur each other forward and help each other along the way. We plan to 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.
sipb-www / ikiwiki.git / blobdiff