Summer Milestone 3
This is an overview of the milestones we wish to accomplish this week. The goal is for each person or team to complete at least one milestone. You can choose whichever ones you are interested in and can dedicate the time to. They can be found as boards on Trello.
Add yourself as a member on Trello to any milestone that you plan to complete this week.
This week we are continuing to focus on Micro/Macro (how can we make our platform scale the whole spectrum of crowd work, from mTurk-like microtasks to oDesk-like macrotasks?) and open governance (how can our platform adapt itself to respond to the needs of users over time?) as well as engineering our platform. We are also starting the collaborative writing process for our paper submission.
We need to submit all milestones for this week by 11:59pm Pacific Daylight Time on Thursday 11th June.
- Youtube link of the meeting today: watch
- Summer Meeting 2 slideshow: exploring next steps for open-gov and micro-macro (pdf)
We need to get feedback from requesters on the two storyboards we have created previously:
Please gather feedback as votes, open-ended question on why?, synthesize the results, make a recommendation and write a short rationale for the rest of us. Michael will provide emails of requesters to speak to. Please use this slack channel to communicate and coordinate.
Macro + Micro
Convergence and HTML prototype
Aim for consensus on the various ideas generated for each of the 3 Micro/Macro design ideas and produce an HTML mockup of each one of them. Try and integrate the critique from the Saturday Hangout Meeting to guide your prototypes.
Analysis and addressing questions
Test our progress against our goals for macro/micro. More information can be found here.
This week, we plan to continue building on the five features from last week (Trello lists). Each feature has multiple components (Trello cards). There are Slack channels for each feature to help you coordinate. We encourage you to collaborate and work together, form a task-based team, or coordinate however you'd like - just join in the relevant Slack channel!):
- Worker Profile: #worker-profile Slack
- Worker Task Portfolio Dashboard: #worker-portfolio Slack
- Requester Profile: #requester-profile Slack
- Requester Task Portfolio Dashboard: #requester-portfolio Slack
- Task Creation Operational Workflow: #task-creation Slack
Add yourself to this item if you'll be working on this milestone this week. If there's just one of you, you're the Directly Responsible Individual ("DRI") for make sure it gets done. (DRIs are a technique we're borrowing from Apple.) If there are multiple of you, the first person is by default the DRI, but you can decide on anyone!
Make sure to coordinate using Slack so that you don't duplicate code effort! We aim to collaborate. Join the same forked repo and work together!
If you are interested in working other issues, please check out the Github issues page. When you start working on an issue, link to your fork on the github issues page. If it is a large issue that may require collaboration, create a slack channel for it so others can discuss and collaborate with you, and link to it from the github issue.
We will upload a basic skeleton of the paper with pre-defined sections. You can choose to participate in the paper writing process in the following way:
- figures - Choose and create one or more figures that needs to be drawn for the paper.
- (sub)section summaries - Write a 1-2 sentence summary to describe/summarize the work done for a particular section or subsection.
Please use this slack channel to help you coordinate.
Choose a name
Votes for names are still open! Go here to vote.
Submitting and Peer Feedback
Create a wiki page
For each of the submissions (with the exception of Research Engineering - with Research Engineering you're submitting pull requests on Github), please create a page on this wiki for your submission.
See here for instructions on creating new pages. Name your wiki page "Summer Milestone 2 YourTeamName TaskYouAreDoing" (substituting YourTeamName with your team name, or your Slack username if you're going solo, and substituting TaskYouAreDoing with the name of the task you're submitting for)
Submit at http://crowdresearch.meteor.com/ in the category according to which of the tasks you did
http://crowdresearch.meteor.com/category/week3-backend (link it to your pull request on GitHub)
http://crowdresearch.meteor.com/category/week3-frontend (create a wiki with screenshots and some description)
After submitting, please post to the submission to the trello board as a comment, to notify others and get their feedback.
Vote and comment on others' submissions
Please look through the submissions at http://crowdresearch.meteor.com/ and vote and comment on others' submissions! Comment as much as you can - constructive feedback is valuable!
In meeting on Saturday, we will critique a bunch of micro/macro prototypes. Take notes and try to incorporate the necessary to your ideas/prototypes.