This #wwg report will be our fourteenth, and also a look back at the past year's worth of work!

Growth

To recap some of what I've been writing about recently (#software-outreach), over the past year, we've seen a dramatic shift in how code is produced at Public Lab. We've received new contributions to the PublicLab.org code repository from 10 contributors having added code in the first 3 years of the project, to 54 in the past year. January has been a smaller month, but still huge compared to one year ago; more people contributed in the past 30 days than in our first three years:

Excluding merges, 14 authors have pushed 39 commits to master and 58 commits to all branches. On master, 105 files have changed and there have been 1,621 additions and 729 deletions.

Look at the activity in more depth at GitHub Pulse.

I've also been writing (at #software-outreach) about how we've achieved this community growth and our continuing refinements and initiatives to increase both the size of our contributor base, but its diversity, through #first-timers-only outreach strategies. Look at the spike in the past year on this graph!

Features and changes

Over the past year, the big projects we've launched include:

• the Rich Editor (now at https://publiclab.org/post, and code at https://github.com/publiclab/PublicLab.Editor)
• the Q&A system: https://publiclab.org/questions
• the new Dashboard
• Internationalization: https://github.com/publiclab/plots2#internationalization
• in the Spectral Workbench project, we were able to launch the Operations analysis tool suite: https://publiclab.org/wiki/spectral-workbench-operations
• we spun out Spectral Workbench's core JavaScript libraries as an independent module: https://github.com/publiclab/spectral-workbench.js

We've also:

• created a welcoming landing page for new contributors: https://github.com/publiclab/plots2/projects/2
• launched a REST API: https://github.com/publiclab/plots2/wiki/API
• gone from from 0% to 85% test coverage
• created a staging server to automatically test code on live data before publishing it
• launched a highly active Gitter chat channel: https://gitter.im/publiclab/publiclab

Even just in this past month, we've seen

• Lots of geographic features progress - see prototype at https://publiclab.org/locations/form
• Prompts/rich wikis work - see https://publiclab.org/wiki/power-tags#Prompts

Summer fellowships

After a fantastic 2016 Google Summer of Code with 5 great students (read more at https://opensource.googleblog.com/2016/12/google-summer-of-code-2016-wrap-up_21.html), we're now applying for the 2017 GSoC program, as well as the Rails Girls Summer of Code program; our project ideas are being compiled at:

https://publiclab.org/wiki/gsoc-ideas#Ideas

We also, with leadership and an **enormous amount of work **from @ananyo2012, participated in Google Code-In over December-January, where we helped dozens of high school students around the world to contribute to Public Lab code. Thanks!

Miscellaneous

We've also made lots of progress on better understanding and presenting how the Public Lab site works:

Diagramming: https://publiclab.org/notes/warren/01-27-2017/diagramming-knowledge-production-on-publiclab-org

Data model: https://github.com/publiclab/plots2/blob/master/doc/DATA_MODEL.md

Coming up

For the next few weeks, I'm focusing on the Rich Wikis project, with an emphasis on making our wiki pages more interactive. This may include "editable subsections" and commenting and subscriptions. I'm also helping shepherd along projects related to our upcoming Topics page, our planned Geographic features, and more.

What are you interested in seeing built, or helping out with?

And finally, a huge thanks to everybody for such a great year!

P.S. on a closing note, last week we passed 10,000 contributors on Spectral Workbench. What a milestone!