Engagement/Developer Engagement/Collusion Plan

Developer Engagement Plan for Collusion

Summary

Collusion is an experimental add-on for Firefox and allows you to see all the third parties that are tracking your movements across the Web. It will show, in real time, how that data creates a spider-web of interaction between companies and other trackers. 

Public link for the project can be found here: [www.mozilla.org/en-US/collusion/ Collusion]

Target Audience

The project is targeted towards the general public and those that are interested in the behind-the-scenes information gathering that happens during web browsing.


Type of Developers Needed

Since the project is still in early stages there are many different opportunities for developer contributions.   A roadmap is in the works and a list of updates and next steps includes:

  • An API that would allow developers to customize how the data is tied to Firefox.
  • becoming a standard feature within Firefox.
  • data visualization, 3D/2D representation of the node graph
  • data/cookie management - direct connection to preferences? enhancement to site-by-site support?
  • filtering of user actions and how it relates to the node graph
  • interaction(s) with the node graph
  • information discovery - how is collusion better integrated within Firefox
  • trace route to any of the tracking servers.
  • better favicon support - integrated with how Firefox places the icon in the URL bar

Community Outreach

  • anonymous way to share tracking data/graph to help optimize information
  • allow the information to be more understandable to the general population rather than just "nerds"

Speaking Opportunities

  • data visualization conferences 
  • security conferences
  • data tracking conferences
  • Unconferences

Goals

  • integrate into Firefox beyond the add-on
  • further user control over graph

Source Code

Since the information this project gathers & displays a better place to store the source code is needed. There are projects underway that are separating the GitHub repository from the secure development of the code to mitigate in the case that GitHub gets hacked.  

A serious security vulnerability could be created if those contributing to the code are not properly screened. How do we best keep the code secure?

Code repository is here:  <a href="https://github.com/toolness/collusion/">Collusion GitHub</a>

Timing

The Ford Foundation has contributed money for development and outreach. Exact milestones and deliverables have yet to be solidified.