GSOC Doc Camp!

by evoeges

Exciting news! OpenMRS has been accepted to attend the 2013 Google Docs Camp,  and I’ll be one of the representatives. The docs camp is set up as a conference on free software documentation, and a hands-on production platform for attending organizations to write FLOSS manuals. We’re going to be concentrating specifically on updating and (re)writing guides for new developers. The conference takes place in California in October.

As we’re nearing the end of OPW, it’s so exciting for me to know that my work with OpenMRS will be continuing even after my internship is over.  Most exciting of all, I was contacted this week by someone interested in volunteering to write documentation for OpenMRS. I explained everything that we’re in the process of doing: sorting module pages, updating module pages, creating stub pages*, getting community feedback and input**, and finalizing the style and template guides***. I linked this person to the template and style guide to help them get started and I’m so pleased to know that my work is being put to use.

I’m happy to say that one of the original goals of the summer, sustainability, is being realized. Not only have I created useful ‘meta-documentation’ for future documentors (which is already being used!), but I myself am certainly staying around to help out with OpenMRS documentation even after OPW.

*This is a new task. A lot of modules exist in the repository, but don’t actually have a corresponding wiki page. The repository doesn’t really contain any documentation, just a short overview and a download link. As such, for each module that exists in the repository but not on the wiki, I’ve been creating a ‘stub’ page with just the module name, overview and download link. Once all stub pages have been created, we’ll start filling them in with information.

**A lot of great things have come out of sorting and commenting on each module page. Many people have provided great feedback, and even started updating their documentation pages.

***I’ve updated these so that they’re not just a guide but a reflection of the documentation. For example, the table of contents is an actual table of contents with hyperlinks, there are screen shots and example diagrams and links, etc. Check it out!