[openstack-community] Setting up Upstream Training in Tokyo [upstream]

Sylvain Bauza sbauza at redhat.com
Thu Jul 30 08:25:56 UTC 2015



Le 30/07/2015 04:23, Stefano Maffulli a écrit :
> On 07/29/2015 01:29 PM, Tim Freund wrote:
>> I started a Google form to collect information.  What am I missing and
>> what should I change?
>>
>> http://goo.gl/forms/qAr3N8rdYs
> I would add business title below organization, so we know if we're
> dealing with developer, operator, product/project manager, etc.
>
> I also collected the salutation (and gender), so we can address the
> person in their favorite pronoun.
>
> I like the 'area of interest', which is more precise than what I used to
> collect.
>
> We also asked in the past (but I wonder if we really need them):
>
>   - What is your level of proficiency with Free Software in general and
> its development processes?
>   - Have you ever attempted submitting patches to a Free Software
> project? If so, please describe how it went:
>   - Please summarize your professional experience, as a developer or
> otherwise:
>
> and to set the expectations:
>
>   - What would you like to learn from this training program?

I'd emphasize the very different situations I saw during the sessions 
where some people were not even knowing Linux, some others not yet using 
any DVS like SVN or git and some others really using them but just not 
listening to the sessions because they were playing with DevStack while 
others were trying to understand Git.

Here, I just wonder if it would maybe be better to either ask for a 
certain level of technical proficiency before the Training, or split 
people in groups based on mutual skills ?

>> One thought when we open registration:  we can change the text of that
>> form to warn students that we are putting them on a waiting list once we
>> have exhausted all of our open positions.
> Makes sense, we can keep a counter on Trello
>
>> I'll get something started that will let us sync the form results to
>> trello for progress tracking.
> let me know if you need anything. Zapier was a pretty neat tool,
> although it may require a professional account (we can ask the
> foundation to pay for it, it's not that expensive).
>
>> Concerning mentors:  should the automation automatically assign a mentor
>> based on student interest area and mentor load?  (Perhaps allow mentors
>> to say how many students they are comfortable working with, and
>> auto-assign up to that number.)
> That's the biggest area of concern: we don't have a culture of mentors
> already established so for all the people who expressed interest in
> helping, they need to be trained to read this mailing list, be on IRC
> (which channel?) and follow the trello board and more.
>
> I'm not sure how to best manage the volunteers who have expressed the
> intention to help.

I'd rather try to consider what mentors are able to propose, and give 
that information to students so they could pick one, like we do for GSoC.

Sometimes, picking low-hanging-fruits is really hard and leads to 
confusion, I'd rather make a call to volunteers to see what they can 
give time for mentoring.

-Sylvain

> /stef
>
> _______________________________________________
> Community mailing list
> Community at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/community




More information about the Community mailing list