Here's where all proposed 2016 proposals can be seen: http://publiclab.org/notes/warren/03-10-201...
Public Lab is an open community which collaboratively develops accessible, open source, Do-It-Yourself technologies for investigating local environmental health and justice issues.
Public Lab chatroom
Reset your password
Here's where all proposed 2016 proposals can be seen: http://publiclab.org/notes/warren/03-10-2016/google-summer-of-code-2016-draft-proposals
Link to accepted proposal: https://publiclab.org/notes/Lalithr95/03-23-2016/rich-profile-tags-and-improving-the-performance-of-publiclab-org
Part of: PublicLab.org
Description: A major build-out of profile pages on PublicLab.org. Implement profile tagging for geographic data, role, tools, skills, and barnstars -- all highly requested features by the Public Lab community! Including:
Prerequisites: Ruby on Rails
Difficulty level: hard
Potential mentors: Bronwen Densmore, Jeff Warren, Liz Barry, Bryan Bonvallet.
Link to accepted proposal: https://publiclab.org/notes/Ujitha/03-12-2016/advanced-searching-and-sorting-tool-for-publiclab-org
Description: This project is to develop searching and sorting tools to help organize Public Lab's open science and technology knowledge base. These features will also be used by community managers to help people develop their projects and connect to others. Longer story: The search box is located in the top bar and at this URL: https://publiclab.org/search/. It does not search through the content on profile pages, which is the primary place that people communicate their research interests when they first join the site. Tags are hugely important to knowledge organization on the site: tags create relationships between pages by linking bodies of research, and powertags add hierarchy (parenting), trigger inclusion on metapages like /places, or change graphic styling as in /blog, and much more. The top level tag page needs the ability to sort alphabetically and by frequency of use. Tag sorting will also be a big help for moderating inappropriate content in terms of streamlining batch tag deletion. Currently even when spam is removed, any spam tags used remain in autosuggest which means users are shown offensive words nearly every time they begin typing to add a tag to a page or post. Sorting will also be useful on https://publiclab.org/people.
Potential mentors: Jeff Warren, Liz Barry, Bryan Bonvallet, Dan Henry
Link to accepted proposal: https://publiclab.org/notes/rmeister/03-24-2016/browser-based-arduino-sensor-data-transfer-using-webrtc-and-headphone-jack
Description: A way to read data off of sensors from a website, using only an audio cable, building on modem.js and SoftModem (see links). Dramatically eases connecting to a sensor using a laptop or smartphone directly from a web page, no software installation necessary.
If you can, as a first step, see if you can connect a SoftModem-enabled arduino to a speaker and read the data into the modem.js demo.
List: email@example.com - Main discussion thread here
Update: it seems that modem.js and SoftModem use different encodings, and there is discussion about using or modifying Firmata as the protocol. Read more here
Difficulty level: medium/hard
Potential mentors: Jeff Warren
Link to accepted proposal: https://publiclab.org/notes/ananyo2012/03-25-2016/expanded-q-a-system-for-publiclab-org
Description: This is a critical step for moving from a separated email and website structure towards clearly answered questions prominently featured as the knowledge base of Public Lab. This project features a posting form, styling for presentation, answering feature, more outreach display for recruiting, integration with Rich Profiles to feature helpful people, displays of common questions. Longer story: Currently as things stand now, the same questions get asked again and again on the email forums, which is totally fine but we think we can do a little better. Often the questions are the same "getting started" questions that are commonly compiled into an FAQ, however, in our experience, static FAQs quickly expire as new developments outpace documentation. A "Stack Overflow" model would allow questions to be re-answered over time, while preserving links into the wikis and notes of PublicLab.org. Adding a Q&A layer over publiclab.org/research and publiclab.org/wiki would give a question-asker confidence that a particular bit of documentation answers a particular question they have.
More on implementation
One resource for Q&A is to look at existing questions, even if the prototype system we have is very crudely made. https://publiclab.org/tag/question:* will show you all questions currently asked, and any tag page, for example, https://publiclab.org/tag/balloon-mapping will show the "Ask a question" button and current minimal interface.
Currently, questions are implemented as DrupalNodes with tags marking them as a question:foo on topic foo. We think this is fine, as the tagging system is robust, user-moddable without code, and quite flexible. This probably means that Questions don't need their own model, unless it simply inherits from DrupalNode but uses the same db table.
Informally, some questions are tagged answered once they're answered, but currently that doesn't do anything extra -- but it could be used to mark a question as answered, or a tag like answered:<cid> with the comment id could be used to indicate which question caused the answer, or perhaps answered:<uid> for who answered it.
If a student takes on the "Search/sorting" project, the Sunspot integration may be something they do, and you'd have to work with them on integration with your module. Establishing an API around the current search methods, perhaps with a Search model, would be a good way to compartmentalize this work, and some simple automated unit tests of the Search model would ensure that the other student's work would have to meet basic functionality before it was pulled in.
Other things that could be great add-ons for this project are some better way to alert subscribers who've signed up to answer questions on a topic, as currently we rely on the posted questions being well tagged at publication time. But if they aren't (and question askers may not be familiar with our tagging, so they may not be), there's no additional trigger for tags added later to trigger notifications. Perhaps some way to scan the question body could trigger this.
A way to view how many questions people have answered is also interesting, as it may incentivize people to answer lots of questions in order to gain some kind of visible "reputation". Considering how "helpful" people are, and how that's displayed on the site, is also an exciting direction.
Difficulty level: easy
Potential mentors: Liz, Dan Henry
Link to accepted proposal: https://publiclab.org/notes/jiteshxyz/03-20-2016/internationalization-of-publiclab-org
Description: Internationalizing the plots2 codebase is the step required so that publiclab.org can be translated into other languages. Longer story: Internationalization is the process of designing a software application so that it can potentially be adapted to various languages and regions without engineering changes. Localization is the process of adapting internationalized software for a specific region or language by adding locale-specific components and translating text. Localization (which is performed multiple times, for different locales) uses the infrastructure or flexibility provided by internationalization (which is ideally performed only once, or as an integral part of ongoing development). So far, all we have is that you can tag a post or wiki with "lang:es" for spanish, you can see all content in Spanish by going to https://publiclab.org/tag/lang:es . You could do the same with any language code, like "lang:fr". We have also made sure all character sets work in page content, although are not sure about titles, due to URL generation. What would success look like for this project? Once internationalization is in place, people can localize the footer, header, sidebars, menus, posting forms, etc. A related project is to figure out which crowdtranslation platform would be good -- it would be simplest for the existing publiclab community to use github to track changes and versions, however, there are existing really successful platforms for translation especially in Chinese for video content. Finally, we would be able to have subdomains for each language like es.publiclab.org (for espanol) etc.
Difficulty level: easy to tackle the header and footer, but beyond that possibly hard because it would eventually touch almost every part of the template code.
Mentor: Liz Barry