mozillascience / fellows-class-2015 Goto Github PK

Mon Feb 01, 2016 (travel day) - Sat Feb 06 (after 6pm) or Sunday 2016 -> Egencia

Mon Feb 01, 2016 (travel day) - Sat Feb 06 (after 6pm) or Sunday 2016 -> Egencia

Mon Feb 01, 2016 (travel day) - Sat Feb 06 (after 6pm) or Sunday 2016 -> Egencia

Hi,

I was reading the file "explore/1-challenge_post.md" and the link "challenge exercise" is broken.

Maybe the name of the file was changed.

Best,

this should come up in the gitter room

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

Instructions on Challenge Post are here! Don't publish your post just yet... we'll publish the interviews first, then the challenge posts... First round should go out sometime week of 12/7. Check yourself off when you're done!

• Christie
• Joey
• Jason
• Richard

Complete your assigned interview and upload the audio file to Dropbox. We'll have the interview transcribed and get back to you with the transcript file as soon as it's ready.

• Christie Interviews Joey, uploads file
• Joey Interviews Richard, uploads file
• Richard Interviews Jason, uploads file
• Jason Interviews Christie, uploads file

I'm looking over the roadmap and trying to map the tasks/deliverables to the sprint model of working. In particular, my feeling is that the deadlines might need to be changed to account for sprints - and this only really applies to the explore phase (the prototype phase is already sprint-adapted!).

Here's what I've got:

Explore phase

• Intro and Exploring Problems/Challenges [OK]
  • the interview is independent of the project model
  • we've interpreted the writing exercise and blog post so that they describe higher-level ideas rather than specific projects
• Idea Development [questions]
  • Describing and testing your idea. We've written up the general idea of doing sprints, and several sprint project ideas. Does this satisfy this task?
  • User/Collaborator personas & pathways exercise. This would be a great task to do for each sprint project - is it OK for us to do it that way? So the product for this task will be created as we start each sprint.
  • Resource requirements & sustainability plan. As above, this seems suited to a per-sprint document, written at the start of each sprint.
• Project Planning and Pitching [questions]
  • All of these seem to me like sprint-specific things. Is that a reasonable interpretation?

cc @joeyklee

Mon Feb 01, 2016 (travel day) - Sat Feb 06 (after 6pm) or Sunday 2016 -> Egencia