14 |
15 | Click "(more)" in Issues > Milestones to see the details of a space.
16 |
17 | 
18 |
19 | You can edit the description of your space at any time.
20 |
21 | You can click on the name of a space to see all the associated pathways and sessions. You can modify sessions to be part of your space by adding them to the appropriate "milestone."
22 |
23 | ### Pathways
24 |
25 | Each pathway is represented as a Github ["label."](https://github.com/mozilla/mozfest-program/labels). You can add new labels, change the color and change the name:
26 |
27 | 
28 |
29 | Labels can be applied to sessions (i.e. individual Github issues) to indicate that the session is part of that pathway. You can then search for and see all the sessions that are part of that pathway. There's not limit to the number of labels you can apply to a session. That's great -- we love things that are cross-listed.
30 |
31 | 
32 |
33 | Ideally, each pathway also has what's called a "tracking issue" that provides more information about the pathway.
34 |
35 | 
36 |
37 |
38 | ### Sessions
39 |
40 | Each session is a [Github Issue](https://github.com/mozilla/mozfest-program/issues). They can be easily labeled to be part of a pathway. You can also comment on them, edit them, and "close" them if they are not a good fit for Mozfest.
41 |
42 |
43 |
44 | ## Why we're using Github Issues for Mozfest
45 |
46 | This year we're using Github to manage, review and curate sessions for Mozfest. This tool will allow us to better collaborate and coordinate across the program, as well as provide a record for how the program came together.
47 |
48 | It is new for us to use Github Issues in this way, but based on some other events who've used it effectively, we think it's a great solution for Mozfest.
49 |
50 |
51 | We are here to help in case you get stuck or need help at anytime. Don't worry -- you can't break anything!
52 |
53 | ## Who is using Github Issues for Mozfest
54 |
55 | For Mozfest, we are inviting any Space Wrangler, Pathway Finder or core Mozfest team member to use Github Issues.
56 |
57 | If you are not in one of these roles but are interested to be active in Github Issues with us, please email festival@mozilla.org. Due to the sometimes sensitive nature of our conversations on this platform, please be aware that an invitation to participate is not guaranteed.
58 |
59 | If you are using Github Issues, please be advised that your comments will be recorded and may be viewed publicly at sometime. We will not publish anyone's personal information, and we ask you to be respectful in your comments, both towards the people who submitted sessions and to your fellow program team members.
60 |
61 | ## Getting started with Github Issues
62 |
63 | Github Issues is a powerful way to collaborate on Github. It was originally designed as an "issue tracker" or project management tool for editing code. However, its simple interface allows us to adapt it for Mozfest's program curation.
64 |
65 | To get started, you'll first have to [create a Github account.](https://github.com/join)
66 |
67 | Once you've created your account, send your Github user name to festival@mozilla.org. You will then be notified that you have access to the Mozfest repository.
68 |
69 | ## Learning how to use Github Issues
70 |
71 | The Mozfest team will offer support for you to use Github Issues in the following ways:
72 |
73 | * **This tutorial!** Is there anything missing or unclear? Let us know how to improve it by emailing: festival@mozilla.org
74 | * **Orientations on the Mozfest program call.** During our regular weekly calls, we will walk the group through the major features and workflows in Github Issues. We'll answer questions and troubleshoot.
75 | * **1:1 Conversations.** We'll also offer timeslots for anyone interested in having a more in-depth conversation about how to use Github Issues effectively. In addition, we'll be available for any urgent Github questions via email (festival@mozilla.org), Twitter (#mozfest) or on Skype.
76 |
77 | ## How to review sessions
78 |
79 | Be mindful about what you comment. People who are submitting a session are putting themselves out there. We are invested in ensuring they have a good experience with us, regardless whether their session is accepted or not. Let's be respective and constructive.
80 |
81 | Also note: This is a public Github repo. If you need to say something sensitive about a session or a facilitator, you can use the sessions@ mailing list.
82 |
83 | * 1. Read through the sessions. You can search for key words.
84 | * 2. Signal your interest in the sessions you want to take on:
85 | ** A. Apply a pathway label to indicate you want to include it in your pathway. A session can have multiple labels.
86 | ** B. Apply your space milestone to all your pathways and sessions that you want included within your space. Note: in Github, a session can only be assigned to one space milestone.
87 | ** C. CC yourself in the comment section of a session if you want to be notified about changes to this session and otherwise be involved in deciding to keep or tweak it.
88 |
89 | * 3. Accepting and declining sessions.
90 | ** **How to accept a session:** Add a pathway label and/or space milestone. This indicates you are taking responsibility for the session's inclusion and success at Mozfest. The issue will remain open.
91 | ** **How to suggest declining a session:** Any session issue that is unlabeled and without a space milestone will be perceived as not accepted for this year's festival.
92 |
93 | After September 30 if the session remains unlabeled and without a space milestone, the issue will be closed by the Mozfest team. The session facilitator will be notified by the program team that their session has not be accepted to Mozfest.
94 |
95 | ## Improving this process
96 |
97 | Ideas? Let us know: festival@mozilla.org.
98 |
99 |
--------------------------------------------------------------------------------
/assets/img/tutorial-labels.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/mozilla/mozfest-program/3ec21e4e6a7011944755c9fc624bcf9c49383331/assets/img/tutorial-labels.png
--------------------------------------------------------------------------------
/assets/img/tutorial-pathway-details.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/mozilla/mozfest-program/3ec21e4e6a7011944755c9fc624bcf9c49383331/assets/img/tutorial-pathway-details.png
--------------------------------------------------------------------------------
/assets/img/tutorial-session-details.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/mozilla/mozfest-program/3ec21e4e6a7011944755c9fc624bcf9c49383331/assets/img/tutorial-session-details.png
--------------------------------------------------------------------------------
/assets/img/tutorial-spaces-details.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/mozilla/mozfest-program/3ec21e4e6a7011944755c9fc624bcf9c49383331/assets/img/tutorial-spaces-details.png
--------------------------------------------------------------------------------
/assets/img/tutorial-spaces.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/mozilla/mozfest-program/3ec21e4e6a7011944755c9fc624bcf9c49383331/assets/img/tutorial-spaces.png
--------------------------------------------------------------------------------
/mozfest_pathways_explanation.md:
--------------------------------------------------------------------------------
1 | # Mozfest Pathways: It’s like the London Tube
2 |
3 | To illustrate how Mozfest is evolving its program to be more participant-centric, we thought to do quick, visual walk-through using the analogy of the London Underground.
4 | 5 |
When you first look at what’s on offer at Mozfest, it can look a bit daunting. Hundreds of sessions, activity all across the building, and seeming jumble of places to go.
10 | 11 |That feeling is just like seeing a map of the London tube for the first time. Look at all those stations and lines! How crazy. Where am I? Where do I want to go?
12 | 13 |The good news is that there is a method to the madness. Mozfest, like the London tube, is there to serve you. It’s designed to help you get to go where you want to go, to achieve what you want to achieve.
14 | 15 |Some travelers like to get quickly to a specific destination. Some like to stop and get out at different stations, to have a look around and meet a friend. Others will start a journey wanting to go to one place, but then decide to change lines and end up somewhere else. Travel how you want to.
16 | 17 |Your journey is in your control. You decide where you want to go and how you want to get there. The organizers just create some infrastructure to enable that journey and if needed, can assist you along the way.
18 | 19 |This is what it could feel like.
20 | 21 |
When you first arrive at Mozfest, you’ll be greeted by a friendly ambassador. They will welcome you and talk to you about what you’d like to get out of the festival.
26 | 27 |They can orient you to the schedule and identify places or sessions that might be of interest.
28 | 29 |
For example, you may be a data scientist interested in learning about how to teach data literacy in your university. There will be a series of sessions to help you achieve this. We’re calling them “pathways.”
34 | 35 |Like an underground line, these stops will be clearly laid out for you.
36 | 37 |Because this is your journey, you can change direction anytime.
40 | 41 |So you may have started off on the data literacy path, but then realized there’s this amazing opportunity to learn how to advocate for open data and web standards in your local government.
42 | 43 |That’s fantastic! You can switch pathways easily at any time.
44 | 45 |
And off you go on a new path!
48 | 49 |
It will be clearly signposted at the venue and online how to switch and get on your new path.
52 | 53 |
Of course, like any great trip, you want to enjoy both the journey and the destination. Hop off anytime to linger, have a coffee, meet a friend. Diversions and side-trips are a beautiful way to explore.
62 | 63 |
The tube is a simple analogy to help participants and Mozfest organizers alike better understand how the participant-centric experience can work.
68 | 69 |We can then easily imagine how these journeys and pathways will map across a single building.
70 | 71 |
Even when the festival is humming along, with lots of actions across many floors:
74 | 75 |
We can signpost in very clear ways how to continue along your journey, what’s available to do now, or where to find assistance.
78 | 79 |
Sound like fun?
90 | 91 |Consider proposing a session for Mozfest or just grabbing a ticket and join us over the weekend.
92 | 93 |Images by: Payload93, JRC Design, Rail Adventure, Google Doodle, Midlandstande.
94 | --------------------------------------------------------------------------------
