Public Lab Research note

Web Working Group Update 19: June 2017

by warren | July 03, 2017 21:22 03 Jul 21:22 | #14614 | #14614

Shorter update this month -- I was VERY late on last month's, so it's only been a bit over 2 weeks :-/

For our repository: 7 authors have pushed 29 commits to master and 88 commits to all branches. On master, 59 files have changed and there have been 492 additions and 1,362 deletions

Above -- our graph now shows 90 contributors to the project.This of course doesn't count coding happening in adjacent repositories like:

New features

A few new things have gone live -- a beta release of the Inline Rich Wiki editor, which you can activate using the green "pencil" icon on all wiki pages. It looks like this:

image description

There's also a beta new Questions form, which looks like this:

image description

Summer of Code

Just to recap, students in our Summer of Code program have been cranking away; you can see their planning issues here:

Student project updates

First, @mridulnagpal writes:

Live demo working at

Input listeners added which changes the map locations

A new feature called precision added and many new methods with tests added

An element integrated which shows the current location of map in text using geocoding API

Will start working with Graticule plugin now, and integrate it to the map.

Then, @stella writes:

I have worked on a method called notify_tag_added() that is used to email users of new tagging on notes they don't already follow. I have also written tests to ensure that the method is working properly.

Demos to show: You can pull from my branch and play around with the emails(

Next steps: Move to phase 2, where I will be working on active jobs.

Also, @ryzokuken writes:

On the bot project, I have come close to finish up the FTO feature, which would allow users to check out the current first-timers-only issues for any publiclab repositories. As this was the first behaviour implemented using the new and shiny promise-based model, I did find a few shortcomings and have patched them and I hope we will strengthen the model quite a bit over the course of the next few PRs.

We also thought a lot over how to implement shared state/dependencies among multiple behaviours and ended up using the "factory function" approach, which I am quite satisfied with. Not to mention, the documentation has consistently grown and has become quite reliable.

We had our first new contributor recently, and they added the Travis Status badge to our README, which was super helpful.

We have been discussing recently to take away the core chatbot logic of the bot and make it a separate npm module. This would go a long way towards making the project much more successful, I think.

Next, I will start working on another feature or on a WeChat interface, whichever would be a higher priority for the organization at that point of time. Also, I feel the help behaviour needs an update.

Thanks to everybody (@ryzokuken, @stella, @ccpandhare, @mridulnagpal, @Ashan, @david-days, @ananyo2012, @Ujitha, @stevie, @liz, @icarito) for all your hard work! Please post any recent demos or completed projects in the comments.



On the Image Sequencer project, I have completed the core functionality of the module and will now be working on Unit tests for the same and Module Input/Output and building a Node.js as well as browser UI.

The functionality is in place and can be tested as written in the by pulling

Reply to this comment...

Hi, Chinmay- thanks!! I'm curious if you can test things on the gh-pages branch of your project, where the demo is running from. Could you try merging your changes into there as well so people can try it out without having to download anything?

Is this a question? Click here to post it to the Questions page.

Reply to this comment...

@mridulnagpal has done this and can advise.

Also I like your project page for organizing you progress!

Reply to this comment...

Thanks! And sure, @warren, I will modify the gh-pages branch at the soonest.

Reply to this comment...

Login to comment.