Difference between revisions of "Summer Milestone 2"
(→Research Engineering) |
(→Research Engineering) |
||
Line 35: | Line 35: | ||
== Research Engineering == | == Research Engineering == | ||
− | + | This week, we plan to build five features ([https://trello.com/b/Od3TnK42/summer-milestone-2 Trello lists]), each feature has multiple components ([https://trello.com/b/Od3TnK42/summer-milestone-2 Trello cards]). There are slack channels for each feature to help you coordinate: | |
+ | |||
+ | * Worker Profile: [https://crowdresearch.slack.com/messages/worker-profile/ #worker-profile Slack] | ||
+ | * Worker Task Portfolio Dashboard: [https://crowdresearch.slack.com/messages/worker-portfolio/details/ @worker-portfolio Slack] | ||
+ | * Requester Profile: [https://crowdresearch.slack.com/messages/requester-profile/details/ #requester-profile Slack] | ||
+ | * Requester Task Portfolio Dashboard: [https://crowdresearch.slack.com/messages/requester-portfolio/details/ #requester-portfolio Slack] | ||
+ | * Task Creation Operational Workflow: [https://crowdresearch.slack.com/messages/task-creation/details/ #task-creation Slack] | ||
If interested in working other issues, please check out the [https://github.com/crowdresearch/crowdsource-platform/issues 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. | If interested in working other issues, please check out the [https://github.com/crowdresearch/crowdsource-platform/issues 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. |
Revision as of 19:16, 29 May 2015
This is an overview of the tasks we wish to accomplish this week. You can do whichever ones you are interested in / have time for. They can be found as boards on Trello.
Focus areas for this week are Micro and 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?)
Contents
Micro and macro tasks
We want to have a clear vision of how 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 everything between.
Interface and Flow for Creating a Task
https://trello.com/c/LJrLPfiJ/3-task-creation-flow
Tracking tasks
https://trello.com/c/lT9ZCUXd/2-tracking-tasks
Monitoring progress, reviewing results, paying
Open governance
https://trello.com/c/QXEGUTVV/4-choose-a-side
We want to be able to make a reccomendation - will we use direct democracy or representative voting?
We need to get feedback on the two storyboards:
Please synthesize feedback votes and make a recommendation.
Research Engineering
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:
- 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
If 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.
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!
Submitting
Create a wiki page
For each of the submissions, please create a page on this wiki for your team's submission on this wiki. 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 username if you're going solo, and substituting TaskYouAreDoing with the name of the task you're submitting for)
Submission Categories
Submit at http://crowdresearch.meteor.com/ in the category according to which of the tasks you did
http://crowdresearch.meteor.com/category/week2-task-creation-flow
http://crowdresearch.meteor.com/category/week2-tracking-tasks
http://crowdresearch.meteor.com/category/week2-monitoring-progress
http://crowdresearch.meteor.com/category/week2-open-governance
After submitting, please post to the submission to the trello board as a comment, to notify others and get their feedback.
Vote 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!