Aggregating call to action sites into a single application.
Slack: #indivisible
Project Description: A variety of civic activism organizations have sprung up in the wake of the election to help mobilize and empower people. The organizations often operate by sending out daily or weekly “actions” that their supporters partake in – whether calling a Member of Congress’s office, attending an event, or reading a key piece of information. As these sites proliferate, it becomes difficult to effectively signal boost and target actions appropriately. For this project, we will build tools to
- Identify various actions available for users by aggregating different sources of data
- Provide a clean user interface to filter and select actions they are interested in
- Build a dashboard and track action progress/effectiveness over time
- Engage user interest through social media or similar means to identify tasks for more effective actions
Project Lead:
Maintainers (people with write access): We need people; please ping @pg or @bonfiam for your interest. Scroll down for an overview of current issues!
Data: https://data.world/data4democracy/indivisible
Note: Create dataset for project in data.world and link it here.
- We welcome contributions from first timers
- Browse our help wanted issues, which are summarized below. See if there is anything that interests you. Tag Definitions
- Core maintainers and project leads are responsible for reviewing and merging all pull requests. In order to prevent frustrations with your first PR we recommend you reach out to our core maintainers who can help you through your first PR.
- Need to practice working with github in a group setting? Checkout github-playground
- Updates to documentation or readme are greatly appreciated and make for a great first PR. They do not need to be discussed in advance and will be merged as soon as possible.
- Create an Anaconda virtual environment.
- Clone the repository and work on the modules.
- Use Pylint for code formatting.
Docker infrastructure for development (#6) is needed.
After that, the first priority is to handle data ingestion.
- Establish polling service for incoming emails. See #10 and
ingest/listener.py. - Consume incoming emails for persistence and feature extraction.
See #1, #8, and
ingest/scraper.py. - Implement storage.
- See #3 and #9 for discussion of schema.
- See #13 for related implementation details.
- Develop feature extraction pipeline to support classification of email contents. See #2 for general discussion on this.
- #7 Discuss potential features of interest.
- #11 Actual implementation of feature extraction.
- #12 Classification strategies. Requires completion of #7 and #11.
See the github wiki update guide.
- When picking up an issue leave a comment/ mark as in progress and assign yourself.
- Issue comments can be used for communication
- The wiki should be used for different documentation purposes. That will include
- Meeting minutes
- Design choices
- Further reading/tutorials
- Python : backend for ingesting data that is built in Python.
- JavaScript : the website is built with JavaScript.