Difference between revisions of "Winter Milestone 10"
(→Task Feed) |
|||
| Line 8: | Line 8: | ||
== Task Feed == | == Task Feed == | ||
| − | Great work last week | + | Great work last week! |
This week we are continuing our push for the UIST submission. Our goals for this week are the following: | This week we are continuing our push for the UIST submission. Our goals for this week are the following: | ||
| − | * | + | *Finish of our timer/data collection mock - @sehgalvibhor. |
| − | *Design review of | + | *Design review of taskfeed system - '''@christopher.diemert @hizai @mathiasburton''' |
| − | * | + | *Finish task time backend: |
| − | ** | + | **Handle time scaling factor @dmorina. |
| − | + | *Finish Backend update of Boomerang: | |
| − | *Backend update of Boomerang: | + | **Use the new data from the rejection rate to modify the cascade: @aginzberg |
| − | **Use the new data from the | + | *Design Study 2: extended Boomerang for requesters |
| − | ** | + | *Sharelatex started: draft introduction |
| − | * | + | *Prepare system for studies |
| − | * | + | **Handle various treatments |
| + | **Collect many tasks | ||
'''We will be having a very brief hangout on Tuesday at 10AM Pacific to divide up work and discuss any questions about this week's milestones.''' | '''We will be having a very brief hangout on Tuesday at 10AM Pacific to divide up work and discuss any questions about this week's milestones.''' | ||
Revision as of 18:18, 14 March 2016
Due date (PST): 8:00 pm 20th March 2016 for submission, 12 pm 21st March 2016 for peer-evaluation.
This week, we will refine methods and systems proposed last week further:
- Youtube link of the meeting today: watch
- Winter Meeting 10 slideshow: coming soon...
Task Feed
Great work last week!
This week we are continuing our push for the UIST submission. Our goals for this week are the following:
- Finish of our timer/data collection mock - @sehgalvibhor.
- Design review of taskfeed system - @christopher.diemert @hizai @mathiasburton
- Finish task time backend:
- Handle time scaling factor @dmorina.
- Finish Backend update of Boomerang:
- Use the new data from the rejection rate to modify the cascade: @aginzberg
- Design Study 2: extended Boomerang for requesters
- Sharelatex started: draft introduction
- Prepare system for studies
- Handle various treatments
- Collect many tasks
We will be having a very brief hangout on Tuesday at 10AM Pacific to divide up work and discuss any questions about this week's milestones.
With the internal deadline on April 3rd, we are going to need all hands on deck for the next month. Whether you are a developer, designer, writer, thinker, etc. there will always be something for you to work on. Please pick up anything and give a yell in the channel so everyone knows who is working on what and so that we can help and guide each other. As always, feel free to reach out to @aginzberg or @dmorina individually with any questions.
Topic background
Check out our system proposal, mainly first few pages and comments to catch up on what we've been working on and thinking about.
The task feed hangouts from previous weeks:
- Youtube link of the task feed meeting 1: watch
- Youtube link of the task feed meeting 2: watch
- Youtube link of the task feed meeting 3: watch
Michael's synthesized needs:
- to find new tasks that will maximize income (reduce uncertainty in payment, rejection, maximize certainty in what will be asked of me and how quickly I can do it)
- to find new tasks that fit my expertise profile
- to refind old requesters' new tasks, since I know I like them
In addition...
- to identify tasks I can do on my own time
- to learn new skills
Task Authoring
Our goal for this week is to run our second pilot study to observe the variance between task authorship and task quality.
Watch last week's task authoring meeting here
First half of this week (Volunteer to be a requester): Please message @catherine.mullings for that. Instructions will be released by Wednesday/Thursday.
By Wednesday, brainstorm a task or find dataset to give to requesters in our pilot study. Think of tasks that are more complex than image labeling or doing sentiment judgements. For example, one task might be to transcribe Youtube videos. Transcription is a much more involved task for workers and final results are subjective and up to interpretation.
By Saturday/Sunday, analyze results: After the task results are received, we will analyze the results from the experiment during a Google Hangout on Saturday/Sunday.
The analysis for the study will be formally written here on Google doc.
Open Gov and Design
We will spend the first half of this week to answer the questions below and @michaelbernstein highlighted in this doc for us:
- Q1 what is the social process for leveling in guilds?
- Q2 what is the effect of getting promoted in guilds?
- Q3 what is the minimum viable product of a social space for a guild?
We will then spend the second half of the week focusing on updating the existing mocks and storyboards we have in order to include those changes. Hopefully we can also get some new ones as it looks like we have a few new designers in the channel.
To do this we are going to have a few mid week hangouts. We don’t have a final schedule yet but @trygve and @markwhitting are aiming to do one around 4 or 5 AM EST on Wednesday Morning so that people from other parts of the world can more easily join in. We will then have another one with @michaelbernstein some time on Thursday.
Helpful links:
- Michael's vision for the Guilds
- Google doc paper
- Guilds and computational compatibility...The system
- Guilds Milestone 6
You can use balsamic or Google slides or just pencil/paper drawing to give shape to your ideas. Design folks, come join and help move this effort forward. Once you're done, post here: http://crowdresearch.meteor.com/category/open-gov
