Difference between revisions of "Summer Milestone 2"

From crowdresearch
Jump to: navigation, search
(Make submissions and comment/vote on others')
(Create a wiki page)
 
(25 intermediate revisions by 3 users not shown)
Line 1: Line 1:
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 [https://trello.com/b/Od3TnK42/summer-milestone-2 Trello].
+
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 [https://trello.com/b/Od3TnK42/summer-milestone-2 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.
 +
 
 +
* Youtube link of the meeting today: [http://www.youtube.com/watch?v=TnE9t67WIxg watch]
 +
* Summer Meeting 1 slideshow: [[:Media:05-29-digging-in.pdf | digging in (pdf)]]
  
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?)
 
  
 
== Micro and macro tasks ==
 
== 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.
+
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 [https://crowdresearch.slack.com/messages/micro-macro/details/ #micro-macro channel on Slack]
  
 
=== Interface and Flow for Creating a Task ===
 
=== Interface and Flow for Creating a Task ===
Line 23: Line 31:
 
https://trello.com/c/QXEGUTVV/4-choose-a-side
 
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 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 need to get feedback on the two storyboards we have created previously:
  
 
[https://docs.google.com/presentation/d/1ylRmJZU-96COmQhLfNhJD_G8FmAtY4cAvcvwc20Lm8g/edit#slide=id.p Leadership Board]
 
[https://docs.google.com/presentation/d/1ylRmJZU-96COmQhLfNhJD_G8FmAtY4cAvcvwc20Lm8g/edit#slide=id.p Leadership Board]
Line 31: Line 39:
 
[https://docs.google.com/presentation/d/1qXQrAhiiGd1Mz0Z0Jb0LMRhEBnsTn4H8HIui8hboXVY/edit#slide=id.p Participatory Democracy]
 
[https://docs.google.com/presentation/d/1qXQrAhiiGd1Mz0Z0Jb0LMRhEBnsTn4H8HIui8hboXVY/edit#slide=id.p Participatory Democracy]
  
Please synthesize feedback votes and make a recommendation.
+
Please gather feedback as votes, synthesize the results, make a recommendation and write a short rationale for the rest of us.
  
 
== Research Engineering ==
 
== Research Engineering ==
  
Five issues will go here
+
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. 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!):
  
If interested in working other issues, please check out the [https://github.com/crowdresearch/crowdsource-platform/issues Github issues page]
+
* 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]
  
== Make submissions and comment/vote on others' ==
+
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 [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.
 +
 
 +
== Choose a name ==
 +
 
 +
After your multiple submissions and suggestions for the names, they are open for vote. Go [http://www.allourideas.org/crowdresearchname '''here'''] to vote.
 +
 
 +
== Submitting ==
  
 
=== Create a wiki page ===
 
=== 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 [https://www.mediawiki.org/wiki/Help:Starting_a_new_page 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)
+
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 [https://www.mediawiki.org/wiki/Help:Starting_a_new_page 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)
  
 
=== Submission Categories ===
 
=== Submission Categories ===
Line 57: Line 81:
 
http://crowdresearch.meteor.com/category/week2-open-governance
 
http://crowdresearch.meteor.com/category/week2-open-governance
  
== Old Notes ==
+
After submitting, please post to the submission to the trello board as a comment, to notify others and get their feedback.
 
+
Macro/micro
+
- Sketch out the interface and flow for creating a task. Needs to cover: payment, who is qualified, task interface (HTML editor?). Submit a sketch/storyboard with description. You can use paper, Illustrator, Balsamiq. Put it on a wiki page. Post it to Telescope.
+
    example. Page classification
+
    example. Copyedit my essay
+
 
+
- Brainstorm how we can prevent tasks from going off the rails for micro and macro (e.g., 10hrs of work and then rejected). Idea: milestones. 5%, or explicit. Or come up with your own. Sketch/storyboard with description. Paper/illustrator/balsamiq. Put on a wiki page. Post to telescope.
+
 
+
- Brainstorm how to monitor progress, review results and pay. Wiki—>telescope.
+
  
Open governance
+
=== Vote and comment on others' submissions ===
Make a recommendation — will we be using direct democracy or representative voting?
+
    . Get feedback on the two storyboards
+
    . Write up a couple paragraphs with the feedback votes, and your recommendation and reasoning
+
  
ResearchEng
+
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!
Make the five issues
+

Latest revision as of 16:04, 1 June 2015

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

https://trello.com/c/LJrLPfiJ/3-task-creation-flow

Tracking tasks

https://trello.com/c/lT9ZCUXd/2-tracking-tasks

Monitoring progress, reviewing results, paying

https://trello.com/c/5F39iUz5/1-brainstorm-how-to-monitor-progress-review-results-and-pay-create-a-wiki-page

Open governance

https://trello.com/c/QXEGUTVV/4-choose-a-side

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:

Leadership Board

Participatory Democracy

Please gather feedback as votes, synthesize the results, make a recommendation and write a short rationale for the rest of us.

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. 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!):

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.

Submitting

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)

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 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!