OpenStack Upstream Training/Admin - Revision history

Timfreund at 03:13, 10 August 2015

2015-08-10T03:13:58Z

Smaffulli: updated with latest content of 'get ready email'

2015-05-06T17:19:14Z

updated with latest content of 'get ready email'

Smaffulli: /* Engagement */

2015-04-17T18:09:11Z

‎Engagement

Smaffulli: /* Engagement */

2015-04-17T18:08:15Z

‎Engagement

Smaffulli: /* Email messages */

2015-04-13T23:12:05Z

‎Email messages

Smaffulli: first draft at administration tasks

2015-04-09T19:07:55Z

first draft at administration tasks

New page

= Administration tasks for Upstream Training =

== Engagement ==

Used to create the event. The signup process requires applicants to specify their intentions, which areas to focus on.

Engage with applicants at regular intervals to make sure they are fully engaged and understand what they sign up for. 4 weeks before the event send them a notification to start engaging with teachers and mentors. 2 weeks before the event, remind them to pick a bug and setup their development environment.

=== Email messages ===

First welcome email:
<pre>
Nice to e-meet you and thanks for subscribing to the OpenStack
University course.

I see from your submission that you're willing to start to
improve your Free Software contribution skills. This is exactly
what it is about, although most people think it is just for
beginners :-) Could you send me a few URLs of your past
contributions ?

A week before the course, we will choose a contribution that
matches
your expectations. Something not too easy so you get to learn as
much as possible. But not too difficult either so you can
complete it in a reasonable timeframe. Do you already have
something in mind ? Or a specific contribution skill that you
would like to improve ?

Don't hesitate to ask if you have questions regarding the
training program.
</pre>

Second email

<pre>TL;DR: pick three bugs from [3] and mail them asap :-)

The OpenStack Upstream Training[1] is just one week away, in Atlanta[2].
Time flies !

Could you please pick a few (3 or so) bugs (from the low hanging fruit
list[3] or elsewhere, it is up to you) that look like good candidates
for you to work on during the training ? Send me your choice by mail as
soon as possible and I'll help you pick one. The goal of the training
will be to get your work accepted upstream. It is best to chose a
contribution that looks easy. Even the simplest work is an opportunity
to learn. Keep in mind that we will get started next week-end (10/11 may
2014) and that we will meet online afterwards, a few times a week, until
the work is complete.

During the training you will need:

* A laptop with Wifi
* A virtual machine running Ubuntu (or any other operating system you
feel confortable with when working on OpenStack)

It is worth double checking that this works well in advance.

Cheers

[1] OpenStack Upstream Training
https://wiki.openstack.org/wiki/OpenStack_Upstream_Training/Info
[2] May 10/11 session in Atlanta
http://www.eventbrite.com/e/openstack-upstream-training-tickets-2769119511
[3] low hanging fruit
https://bugs.launchpad.net/openstack/+bugs?field.tag=low-hanging-fruit

A link to all Low Hanging Fruit bugs
https://bugs.launchpad.net/openstack/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.tag=low-hanging-fruit&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on
</pre>

== Lego management ==

The Lego need to be shipped weeks ahead of time to volunteers near the convention center. They will help assemble the buildings and bring them to the facility the morning when the training starts, or the evening before, as soon as the rooms are ready.

After the class, the Lego can be displayed in the expo floor.

After the show, the Lego need to be packaged and shipped back to FNTech facilities.

=== Lego material ===

* estimate per student 750g of assorted bulk Lego bricks for the creative session
* at least two buildings per classroom of the Lego City series

Currently the Foundation owns London Bridge, Sidney Opera House, Pet Store, Cinema, French Restaurant.

@@ Line 1: / Line 1: @@
 = Administration tasks for Upstream Training =
 == Engagement ==
@@ Line 7: / Line 16: @@
 Engage with applicants at regular intervals to make sure they are fully engaged and understand what they sign up for. 4 weeks before the event send them a notification to start engaging with teachers and mentors. 2 weeks before the event, remind them to pick a bug and setup their development environment.
-Volunteer staff ask to be added to the [https://trello.com/b/iuJab0VH Trello board]. From the board, staff picks one card from the '''Applicants''' list, move the card to next list '''Mentor picked''' and send the applicant the engagement email (suggested text below).
+Volunteer staff should fill out the [http://goo.gl/forms/fczq3NZ16g mentor form], then they will be added to the [https://trello.com/b/j7TX9oUw Trello board]. From the board, staff picks one card from the '''Applicants''' list, move the card to next list '''Mentor picked''' and send the applicant the engagement email (suggested text below).
 Mentors should help the applicants select a simple bug to fix or another very simple work item, based on the interests and objectives of the applicant. The work item will be executed '''after''' the training in classroom.
@@ Line 70: / Line 79: @@
 Currently the Foundation owns London Bridge, Sidney Opera House, Pet Store, Cinema, French Restaurant.

@@ Line 28: / Line 28: @@
 ===== Engagement email, sent by mentor =====
-<pre>TL;DR: pick three bugs from [3] and mail them asap :-)
+<pre>
-The OpenStack Upstream Training[1] is just one week away, in Atlanta[2].
+The OpenStack Upstream Training is just a few days away, in Vancouver Convention Centre. We will meet on Saturday, May 16, 2015 at 9:30am and will continue on Sunday May 17, until 5pm.
-Could you please pick a few (3 or so) bugs (from the low hanging fruit
+To make the best out of the training, please select three bugs from the list OpenStack's known bugs that are simple to fix (Low Hanging Fruit): https://goo.gl/HX9Nxa  and assign to you at least one that you feel comfortable working on, based on your interests and experience.
-During the training you will need:
+The goal of the training will be to get your work accepted upstream. It is best to chose a contribution that is easy so you can focus on learning the contribution process, tools and social rules of OpenStack community. Remember that Upstream Training will continue with mentoring sessions online after the class until the work you choose is complete.
-  * A laptop with Wifi
+If you have doubts on how to pick and assign a bug to you, please reply to this email and we'll help you out.
-It is worth double checking that this works well in advance.
+Setup your laptop to be able to follow the training. You will need:
 Cheers
-[1] OpenStack Upstream Training
+note: If your laptop is not powerful enough to run devstack we'll try to provide openstack-based virtual machines in public clouds.
 </pre>

@@ Line 7: / Line 7: @@
 Engage with applicants at regular intervals to make sure they are fully engaged and understand what they sign up for. 4 weeks before the event send them a notification to start engaging with teachers and mentors. 2 weeks before the event, remind them to pick a bug and setup their development environment.
-Volunteer staff ask to be added to the [https://trello.com/b/iuJab0VH Trello board]. From the board, staff picks one card from the **Applicants** list, move the card to next list **Mentor picked** and send the applicant the engagement email (suggested text below).
+Volunteer staff ask to be added to the [https://trello.com/b/iuJab0VH Trello board]. From the board, staff picks one card from the '''Applicants''' list, move the card to next list '''Mentor picked''' and send the applicant the engagement email (suggested text below).
-Mentors should help the applicants select a simple bug to fix or another very simple work item, based on the interests and objectives of the applicant. The work item will be executed *after* the training in classroom.
+Mentors should help the applicants select a simple bug to fix or another very simple work item, based on the interests and objectives of the applicant. The work item will be executed '''after''' the training in classroom.
 === Email messages ===

@@ Line 7: / Line 7: @@
 Engage with applicants at regular intervals to make sure they are fully engaged and understand what they sign up for. 4 weeks before the event send them a notification to start engaging with teachers and mentors. 2 weeks before the event, remind them to pick a bug and setup their development environment.
 === Email messages ===
-First welcome email:
+===== Welcome email, at signup =====
 <pre>
 Subject: Welcome to OpenStack Upstream Training
@@ Line 23: / Line 26: @@
 </pre>
-Second email
+===== Engagement email, sent by mentor =====
 <pre>TL;DR: pick three bugs from [3] and mail them asap :-)
@@ Line 57: / Line 60: @@
 https://bugs.launchpad.net/openstack/+bugs?field.tag=low-hanging-fruit
 </pre>
 == Lego management ==

@@ Line 12: / Line 12: @@
 First welcome email:
 <pre>
-       Nice to e-meet you and thanks for subscribing to the OpenStack
+Subject: Welcome to OpenStack Upstream Training
-        University course.
+Nice to e-meet you and thanks for subscribing to the OpenStack Upstream Training. The objective of the two day session is to improve your understanding of OpenStack's contribution process and help you become more effective at merging code in OpenStack. The training is designed to be practical, it begins *now* before and will continue after, with mentoring sessions until your first contribution is completed.
-        I see from your submission that you're willing to start to
-        improve your Free Software contribution skills. This is exactly
+If you haven't done it already, get familiar with OpenStack Upstream Training [OpenStack_Upstream_Training/Info#Objectives objectives],  [OpenStack_Upstream_Training/Info#Course_Outline schedule] and [OpenStack_Upstream_Training/Info#Prerequisites pre-requisites].
-        what it is about, although most people think it is just for
-        beginners :-) Could you send me a few URLs of your past
+Please start engaging with your mentor by replying to this message, explaining what you would like to work on and what your personal objectives are for this class. The mentor will help you select a low hanging fruit bug to fix and send you further instructions.
-        contributions ?
+Don't hesitate to ask if you have questions regarding the  training program.
 </pre>