Summer Milestone 2
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.
Focus areas for this week are 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?)
We need to submit all milestones for this week by 11:59pm Pacific Daylight Time on Friday 5th June.
Micro and macro tasks
We envision that our platform can span the whole spectrum of crowd work tasks between mTurk-like micro tasks (ex: image/page classification), through oDesk-like macro tasks (ex: here's my 10 page essay, please proofread and edit it), and even new types of crowd-labor tasks that neither were designed for for (ex: getting English speakers interested in learning Chinese to do an online user study testing my new language-learning website). Check out the new #micro-macro channel on Slack
Interface and Flow for Creating a Task
Monitoring progress, reviewing results, paying
We want to be able to make a recommendation - will we use direct democracy or representative voting?
We need to get feedback on the two storyboards we have created previously:
Please gather feedback as votes, synthesize the results, make a recommendation and write a short rationale for the rest of us.
This week, we plan to build five features (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.
Choose a name
After your multiple submissions and suggestions for the names, they are open for vote. Go here to vote.
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
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!