Open Stack

Le 09/04/2015 20:56, Stefano Maffulli a écrit :
> Hello folks (especially upstream trainers and mentors)
>
> I'm planning on sending a notification to all people who registered for
> Upstream Training Vancouver, telling them the next steps.
>
> In the past we've asked people to start sharing their thoughts and plans
> ahead of the training and engage with the mentors, so they can help
> students pick a low-hanging-fruit bug and get their dev-environment
> ready for the live sessions.
>
> I'll send all applicants something along the lines below, with
> instructions to contact the alias upstream-training at openstack.org (me
> and Chris Ricker are the recipients, so far, but adding Sylvain and Tim
> for sure; any more volunteers?)

Sure, count me in. You can add me to the list.


> Expect traffic to increase in the next weeks :)
>
> Cheers,
> stef
>
>          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 ?
>          

Maybe a note saying that it's worth picking a bug rather than a 
blueprint is easier for them ? (and provide some guidance to point 
what's Launchpad and how to pick ?)
Also, I wonder if it would be a good opportunity to ask the new PTLs if 
they're looking for some help
Also the GSoC mentors were happy to provide some items for students.

Just remembering when I started to contribute 2 1/2 years ago, it was 
already difficult to jump into big projects without having a clear view 
on the project itself. Of course, it's not the same for all of us, as 
some are having already some features to provide, but I think it would 
be good to make sure that main contributors would agree on the direction 
the student is taking.

Of course, if the student is picking a low-hanging-fruit, it should be 
easy enough for implementing it.

Note : in Nova, we're triaging the bugs that way :
  - New : nobody looked at it yet
  - Confirmed : someone did
  - Triaged : the discussed led to findind a solution or at least a 
direction waiting to be implented

So, by looking at triaged bugs with no assignee, there are already some 
really great information that the owner could use.

-Sylvain



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