Public Lab Research note

Expanding Public Lab's community stats system

by romrod | November 06, 2018 04:36 06 Nov 04:36 | #17476 | #17476

(This template is for students applying to code outreach programs with Public Lab. Use this link to start writing a post:,outreachy,outreachy-2018,outreachy-2018-proposals You can delete this line once you've started filling it out.)

About me

Affiliation: Outreachy

Location: US

Project description

Expansion of Public Lab's community stats system for improved accessibility and information density.


The need of a more detailed statistical information and its accessibility for different use cases.


Back-end projects:
Week 1: downloadable data from stats pages: #963 (break-me-up issue)
Week 2:
statistics on questions answered versus asked (from

Week 3:
caching of data weekly (noting this in interface so people know) to reduce loadconsolidation/standardization of "range pages" like with main stats page at,%202017%2022:43
Week 4:
tags most used in this period (linking into per-tag stats, below)
Week 5:
Add display of Total Contributors "for all time" as default for main /stats - #3499

Stats per tag:
Week 6:
subscribers for each tag:
Week 7:
closer mirroring between stats pages and tag pages
Week 8: stats as above, but per-tag?Week 9: script to go back through posts and tag first-timer posts with first-time-poster tag, retroactively so they show up at, to improve stats on first-time posting

Interface design projects:
Week 10: small "bar graph" icons around site which lead to appropriate pages in the stats system (using
Week 11:
date range selector for stats ranges (calendar or draggable date ranges like
Week 12:
ability to click bar graphs to open that actual collection of items in a view such as

Stretch goals:
Since some of the tasks outlined in the timeline might take less than a week to complete, it might be feasible to accomplish the following stretch goals:

Extra 1: make statistics system compatible with GrimoireLab using

Extra 2: retroactively apply the first-time-poster tag ( to previous posts so that we can retroactively graph newcomer posting rate over time


Mentoring from the main collaborators to point me in the right direction whenever needed. In terms of documentation, I believe most can be found online,but it would be good to have the support to acquire certain materials to produce better solutions for the project. The availability of a server to test things out would be useful, too, yet not strictly necessary.

First-time contribution

My first merged pull request for Public Lab: solved Issue #3451:


My experience is in JavaScript, Python, and a little bit of Ruby on Rails and C. I know HTML and CSS and I am comfortable learning frameworks, libraries and tools whenever necessary. I am mostly self-taught, and have participated in a few structured courses to speed up my learning. My GitHub Profile contains several examples of said learning.


I have written documentation and blog posts for open source projects collaborating with their leads. My favorite ones have been the Beaker Browser, and the CLI tool tldr. I mentored students at Udacity after being a student myself. I like to hang around the FreeCodeCamp,, and Codenewbies communities.


I'd like to help solve the very real problems that are affecting so many people around the world. I am passionate about purpose-driven social networks that bring the best out of us instead of the worst. Public Lab provides such a community and the opportunity to shape an important area in a possitive way.


A better understanding of the project's metrics brings more resources and popularity for Public Lab to keep on growing and providing access to tools for scientists, environmentalists, or anyone trying to get the right things done under constraining circumstances.


Login to comment.