It’s time for another project update. We’ve been hard at work on the core of the software that will power LocalWiki. We’ve also been spending time running around meeting people passionate about local media and planning out many things to come.

Basic groundwork laid

i-1c3a1d24e265dce0a40c6039f8a088cc-whiteboard_small.jpg

Many of you know about the Davis Wiki, but what you may not know is that we developed the custom software that powers it ourselves. Back in 2004, there was just nothing else that could do everything you see on the Davis Wiki while being easy enough for most people to use. Developing the custom software was well worth the effort, but the more we learned along the way, the more we wished we could change some of the choices we had made early on and build on a better foundation.

When we got the opportunity to embark on the LocalWiki project, we knew this was our chance to take another look at the core of wiki software and rebuild it using today’s technology and the lessons we learned from years of experience and analyzing our other wiki engines’ code. At the most basic level, one of the things we learned was that providing even simple wiki features like editing and versioning pages was difficult and cumbersome. What’s worse, if done wrong these things make it downright painful for developers to add more complex features. For instance, while there may have been lots of code to help save and track versions of pages, that code couldn’t be used to help someone save and track versions of map points.

By laying a solid foundation for the LocalWiki software, we’ll not only make it easier for others to create basic wiki-like systems but that code will also allow us to go farther with our vision of making the best software for local communities to collaborate on information. In the past couple of months we’ve written an extensive versioning system for the Django framework that will allow us to simplify later development; explored and refined ways to show changes between different objects, especially rendered HTML pages; began the work on our graphic editor interface; and did lots and lots of research on different technologies.

Opening up our development process

We want the LocalWiki project to have an open-from-the-start development process. As such, while the code isn’t ready for casual contributors quite yet, we are fully opening our development process. While we have experience working in the open-source world, one thing we’re new at is working full-time alongside other folks. We’ll probably make some mistakes, but we want to get this right.

Are you an experienced developer who wants to get involved? Please sign up for our developer mailing list. We’ll be sending out a super-geeky developer update in the next day or two.

A (tiny) space to call our own

i-283f3805b7907a68414a3f9ec990f684-philip_painting_small.jpg

A little over a week ago, we moved into a little hole-in-the-wall office space. After working out of a coworking space for the first two months, we felt we could be more productive without the distractions that come with sharing a space with so many (admittedly, incredibly nice and professional) people. The space in San Francisco’s Mission District is tiny and barely fits two desks, but it’s quiet, it’s convenient, and we can stay here late into the night working. After spending a weekend furnishing it, the new space has made a huge difference in our comfort, communication, and ability to work for hours on end without interruptions. It also turns out to be cheaper than the coworking setup, which is a nice bonus.

What about the Kickstarter funds?

Several months ago, we faced a serious issue: The Knight Foundation committed funding to the software development aspects of the LocalWiki project, but essential outreach and education aspects were unfunded. With your help, we raised an absolutely essential fund through Kickstarter.com to support outreach and education in pilot communities.

Our plan for the Kickstarter fund is to hold on to it until we begin the outreach and education phase of the project, which will happen shortly after the first pilot community is selected.