settingsLogin | Registersettings

[openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

0 votes

This is a thread for anyone that participated in the onboarding rooms,
on either the presenter or audience side. Because we all went into this
creating things from whole cloth, I'm sure there are lots of lessons
learned.

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

Hopefully we can consolidate some of that feedback for best practices
going forward.

-Sean

--
Sean Dague
http://dague.net


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Jun 1, 2017 in openstack-dev by Sean_Dague (66,200 points)   4 8 14

20 Responses

0 votes

On 05/19/2017 09:22 AM, Sean Dague wrote:
If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

Project: Nova
Attendees: 25 - 30
Notes: (this conflicted with Baremetal/VM platform part 1, may have
impacted attendance)
Etherpad: https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding

What we did:

To get the room warmed up (it was the first post keynote session), we
prepared a document which was an annotated flow of the logs of booting
up a server with openstack client -
https://github.com/sdague/nova-boot-flow/blob/master/flow.rst - and
talked through all of that, fielding questions along the way. That
actually took about 45 minutes because 20 minutes in the room had warmed
up and started asking a bunch of questions (especially around scheduling
which always seems like a hot area).

We used the back half of the session for just audience questions. Some
of the more interesting ones were diving into what a context really is
(that's a pretty core concept in multiple projects, but one we forget is
new to people).

We did an adhoc diagramming of the basic api.py -> rpcapi.py ->
manager.py pattern in the code that hits all the different daemons. And
even looked at some of the directory structures on how this is organized.

There was a good conversation towards the end on debug strategies. Most
of us are print/log debuggers, but guru mediation was news to most folks
in the room. Definitely clear that there is a need for a pdb guide for
OpenStack (by someone that regularly uses it).

There was also a good discussion around types of arguments in Nova
function calls, and how much one can trust they know what a variable
named "instance" really is.

What worked:

It was really good to have some interactive technical content pre canned
to get the conversation going. Rooms start cold, and you need to get
people interactive.

Questions phase turned out really good. They also seemed pretty spread
around the audience.

Do differently next time:

Recording would have been great.

We did a poor job of fielding questions off the etherpad because my
laptop was being used show flows or answers. Next time it would be good
to have 2 computers up, one on the etherpad watching for questions from
quieter people there, while we have other relevant answer material on
the projector.

-Sean

--
Sean Dague
http://dague.net


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 19, 2017 by Sean_Dague (66,200 points)   4 8 14
0 votes

Thank you so much for getting this started Sean!

I have gotten a lot of feedback that people liked the on-boarding rooms,
but I would be interested to know more about what people did so we can
coordinate better next time. This round I left a lot of the decisions up to
the different teams since this was a new type of session for the Summit so
we could figure out what works best.

I started a resource collection here[1] to round up materials. I am trying
to find a place to post them so that people that weren't able to attend to
look at since we weren't able to get recordings in the room this time-
definitely something to try to coordinate next round!

Thanks again,

-Kendall (diablo_rojo)

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-May/116513.html

On Fri, May 19, 2017 at 8:40 AM Sean Dague sean@dague.net wrote:

On 05/19/2017 09:22 AM, Sean Dague wrote:

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

Project: Nova
Attendees: 25 - 30
Notes: (this conflicted with Baremetal/VM platform part 1, may have
impacted attendance)
Etherpad:
https://etherpad.openstack.org/p/BOS-forum-nova-project-onboarding

What we did:

To get the room warmed up (it was the first post keynote session), we
prepared a document which was an annotated flow of the logs of booting
up a server with openstack client -
https://github.com/sdague/nova-boot-flow/blob/master/flow.rst - and
talked through all of that, fielding questions along the way. That
actually took about 45 minutes because 20 minutes in the room had warmed
up and started asking a bunch of questions (especially around scheduling
which always seems like a hot area).

We used the back half of the session for just audience questions. Some
of the more interesting ones were diving into what a context really is
(that's a pretty core concept in multiple projects, but one we forget is
new to people).

We did an adhoc diagramming of the basic api.py -> rpcapi.py ->
manager.py pattern in the code that hits all the different daemons. And
even looked at some of the directory structures on how this is organized.

There was a good conversation towards the end on debug strategies. Most
of us are print/log debuggers, but guru mediation was news to most folks
in the room. Definitely clear that there is a need for a pdb guide for
OpenStack (by someone that regularly uses it).

There was also a good discussion around types of arguments in Nova
function calls, and how much one can trust they know what a variable
named "instance" really is.

What worked:

It was really good to have some interactive technical content pre canned
to get the conversation going. Rooms start cold, and you need to get
people interactive.

Questions phase turned out really good. They also seemed pretty spread
around the audience.

Do differently next time:

Recording would have been great.

We did a poor job of fielding questions off the etherpad because my
laptop was being used show flows or answers. Next time it would be good
to have 2 computers up, one on the etherpad watching for questions from
quieter people there, while we have other relevant answer material on
the projector.

    -Sean

--
Sean Dague
http://dague.net


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 19, 2017 by Kendall_Nelson (3,720 points)   1 2 3
0 votes

On Fri, May 19 2017, Sean Dague wrote:

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

We shared a room for Telemetry and CloudKitty for 90 minutes.
I was there with Gordon Chung for Telemetry.
Christophe Sauthier was there for CloudKitty.

We only had 3 people showing up in the session. One wanted to read his
emails in a quiet room, the two others had a couple of question on
Telemetry – though it was not really related to contribution as far as I
can recall.

I had to leave after 45 minutes because they was an overlap with a talk
I was doing and rescheduling did not seem possible. And everybody left a
few minutes after I left apparently.

--
Julien Danjou
-- Free Software hacker
-- https://julien.danjou.info


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

responded May 19, 2017 by Julien_Danjou (20,500 points)   2 4 6
0 votes

Kolla:
Attendees - full room (20-30?)
Notes - Conflict with kolla-k8s demo probably didn't help

While we didn't have etherpad, slides, recording (and video dongle
that could fit my laptop), we had great session with analog tools
(whiteboard and my voice chords). We walked through architecture of
each Kolla project, how they relate to each other and so on.

Couple things to take out from our onboarding:
1. Bring dongles
2. We could've used bigger room - people were leaving because we had
no chairs left
3. Recording would be awesome
4. Low tech is not a bad tech

All and all, when we started session I didn't know what to expect or
what people will expect so we just...rolled with it, and people seemed
to be happy with it:) I think onboarding rooms were great idea (kudos
to whoever came up with it)! I'll be happy to run it again in Sydney.

Cheers,
Michal

On 19 May 2017 at 08:12, Julien Danjou julien@danjou.info wrote:
On Fri, May 19 2017, Sean Dague wrote:

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

We shared a room for Telemetry and CloudKitty for 90 minutes.
I was there with Gordon Chung for Telemetry.
Christophe Sauthier was there for CloudKitty.

We only had 3 people showing up in the session. One wanted to read his
emails in a quiet room, the two others had a couple of question on
Telemetry – though it was not really related to contribution as far as I
can recall.

I had to leave after 45 minutes because they was an overlap with a talk
I was doing and rescheduling did not seem possible. And everybody left a
few minutes after I left apparently.

--
Julien Danjou
-- Free Software hacker
-- https://julien.danjou.info


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 19, 2017 by Michał_Jastrzębski (9,220 points)   1 5 5
0 votes

Project: Keystone
Attendees: 12 - 15

We conflicted with one of the Baremetal/VM sessions

I attempted to document most of the session in my recap [0].

We started out by doing a round-the-room of introductions so that folks
could put IRC nicks to faces (we also didn't have a packed room so this
went pretty quick). After that we cruised through a summary of keystone,
the format of the projects, and the various processes we use. All of this
took maybe 30 minutes.

From there we had an open discussion and things evolved organically. We
ended up going through:

  • the differences between the v2.0 and v3 APIs
  • keystonemiddleware architecture, how it aids services, and how it
    interacts with keystone

    • we essentially followed an API call for creating a instance from
      keystone -> nova -> glance
  • how authentication scoping works and why it works that way
  • how federation works and why it's setup the way it is
  • how federated authentication works (https://goo.gl/NfY3mr)

All of this was pretty well-received and generated a lot of productive
discussion. We also had several seasoned keystone contributors in the room,
which helped a lot. Most of the attendees were all curious about similar
topics, which was great, but we totally could have split into separate
groups given the experience we had in the room (we'll save that in our back
pocket for next time).

[0] https://www.lbragstad.com/blog/openstack-boston-summit-recap
[1] https://www.slideshare.net/LanceBragstad/keystone-project-onboarding

On Fri, May 19, 2017 at 10:37 AM, Michał Jastrzębski inc007@gmail.com
wrote:

Kolla:
Attendees - full room (20-30?)
Notes - Conflict with kolla-k8s demo probably didn't help

While we didn't have etherpad, slides, recording (and video dongle
that could fit my laptop), we had great session with analog tools
(whiteboard and my voice chords). We walked through architecture of
each Kolla project, how they relate to each other and so on.

Couple things to take out from our onboarding:
1. Bring dongles
2. We could've used bigger room - people were leaving because we had
no chairs left
3. Recording would be awesome
4. Low tech is not a bad tech

All and all, when we started session I didn't know what to expect or
what people will expect so we just...rolled with it, and people seemed
to be happy with it:) I think onboarding rooms were great idea (kudos
to whoever came up with it)! I'll be happy to run it again in Sydney.

Cheers,
Michal

On 19 May 2017 at 08:12, Julien Danjou julien@danjou.info wrote:

On Fri, May 19 2017, Sean Dague wrote:

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

We shared a room for Telemetry and CloudKitty for 90 minutes.
I was there with Gordon Chung for Telemetry.
Christophe Sauthier was there for CloudKitty.

We only had 3 people showing up in the session. One wanted to read his
emails in a quiet room, the two others had a couple of question on
Telemetry – though it was not really related to contribution as far as I
can recall.

I had to leave after 45 minutes because they was an overlap with a talk
I was doing and rescheduling did not seem possible. And everybody left a
few minutes after I left apparently.

--
Julien Danjou
-- Free Software hacker
-- https://julien.danjou.info



OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:
unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 19, 2017 by Lance_Bragstad (11,080 points)   2 3 6
0 votes

Tricircle shared a room with Sahara, and stay there for the first half.

Around 6 persons joined the session. Due to the network issue(on the lab side) I am not able to logon to my environment to do the training based on live environment. I have to play some recorded clips, during the playing, we discussed a lot of topics, from the overall architecture and functionalities, and whether it support cross Neutron L2 network, and how to setup the environment to experience it. I can't remember all detail information. It seems 45 minutes is too short for on-boarding session, lots of other topics have not been discussed. We leave the room after Sahara began their session, two projects in same room will be quite noise, many people will talk at the same time. After the session, one guy continue to talk with me about Tricircle for around half an hour.

Obviously, on-boarding session is necessary for a project, some may be contributors, some may be not, but there are lots of people want to learn a project in more detail, it'll help a project to grow contributors and (potential) operators.

Best Regards
Chaoyi Huang (joehuang)


From: Sean Dague [sean@dague.net]
Sent: 19 May 2017 21:22
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

This is a thread for anyone that participated in the onboarding rooms,
on either the presenter or audience side. Because we all went into this
creating things from whole cloth, I'm sure there are lots of lessons
learned.

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

Hopefully we can consolidate some of that feedback for best practices
going forward.

    -Sean

--
Sean Dague
http://dague.net


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 22, 2017 by joehuang (17,140 points)   2 6 9
0 votes

On Fri, May 19, 2017 at 09:22:07AM -0400, Sean Dague wrote:
This is a thread for anyone that participated in the onboarding rooms,
on either the presenter or audience side. Because we all went into this
creating things from whole cloth, I'm sure there are lots of lessons
learned.

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

TripleO:
Attendees - nearly full room (~30 people?)

We took an informal approach to our session, we polled the room asking for
questions, and on request gave an architectural overview and some
code/template walkthroughs, then had open questions/discussion for the
remainder of the session.

Overall it worked quite well, but next time I would like visibility of
some specific questions/topics ahead of time to enable better preparation
of demo/slide content, and also we should have prepared a demo environment
prior to the session to enable easier hands-on examples/demos.

Overall I thought the new track was a good idea, and the feedback I got
from those attending was positive.

The slides we used are linked from this blog post:

http://hardysteven.blogspot.co.uk/2017/05/openstack-summit-tripleo-project.html

Steve


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 22, 2017 by Steven_Hardy (16,900 points)   2 7 11
0 votes

Project: Sahara
Attendees: 6-8 (1 never involved in Sahara)

We worked on a quick overview of how Sahara works and planned to work a
little on code. Since most of the people there worked on Sahara already the
code introduction didn't make a lot of sense since the only rookie was most
interested in how to deploy and use sahara on his environment. So the
conversation took an unexpected turn and we talked more on how Sahara could
be a solution for an specific use case.

Overwall it worked well, but not as we planned from the beggining.

On Mon, May 22, 2017 at 5:20 AM Steven Hardy shardy@redhat.com wrote:

On Fri, May 19, 2017 at 09:22:07AM -0400, Sean Dague wrote:

This is a thread for anyone that participated in the onboarding rooms,
on either the presenter or audience side. Because we all went into this
creating things from whole cloth, I'm sure there are lots of lessons
learned.

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

TripleO:
Attendees - nearly full room (~30 people?)

We took an informal approach to our session, we polled the room asking for
questions, and on request gave an architectural overview and some
code/template walkthroughs, then had open questions/discussion for the
remainder of the session.

Overall it worked quite well, but next time I would like visibility of
some specific questions/topics ahead of time to enable better preparation
of demo/slide content, and also we should have prepared a demo environment
prior to the session to enable easier hands-on examples/demos.

Overall I thought the new track was a good idea, and the feedback I got
from those attending was positive.

The slides we used are linked from this blog post:

http://hardysteven.blogspot.co.uk/2017/05/openstack-summit-tripleo-project.html

Steve


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--

TELLES NOBREGA

SOFTWARE ENGINEER

Red Hat I https://www.redhat.com/

tenobreg@redhat.com

TRIED. TESTED. TRUSTED. https://redhat.com/trusted


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 22, 2017 by tenobreg_at_redhat.c (1,580 points)   1 1
0 votes

Project: Documentation and I18N
Attendees: 3-5 (maybe?)
Etherpad: https://etherpad.openstack.org/p/doc-onboarding

What we did:

We ran the session informally based off whoever was there. Due to the small attendance, we just ran through how the project works (docs like code and all that).
Discussed the docs ML, IRC, and how best to get started (find some low hanging fruit). Ian also took the group through the translation team process, and gave a little demo on how the Zanata translation tool was used.

We gave everyone back 30 minutes of their lives.

On 5/19/17, 2:22 PM, "Sean Dague" sean@dague.net wrote:

This is a thread for anyone that participated in the onboarding rooms,
on either the presenter or audience side. Because we all went into this
creating things from whole cloth, I'm sure there are lots of lessons
learned.

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side of
the table.

Hopefully we can consolidate some of that feedback for best practices
going forward.

  -Sean

-- 
Sean Dague
http://dague.net

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 22, 2017 by a.settle_at_outlook. (3,220 points)   2 2
0 votes

Project: Neutron
Attendees: ~15

Neutron's session was a combination of a slide presentation (
https://www.slideshare.net/MiguelLavalle/openstack-neutron-new-developers-on-boarding)
with predefined exercises on the DevStack VM that was used during the
OpenStack Upstream Institute the weekend prior to the Summit. This is what
we did in more detail:

  • Introduce team members present in the room: Kevin Benton, Armando
    Migliaccio, Swaminathan Vasudevan and Brian Haley, We thought this was
    important to send the message that we are an open and welcoming community /
    project / team.
  • Quick overview of Neutron team organization, IRC meetings and the
    concept of the Neutron Stadium of related projects. We also showed the
    project's mascot and handed out stickers.
  • We didn't want to make any assumptions as to prior knowledge of the
    attendees, so we started from the beginning. We reviewed the concepts
    associated to ReST APIs from the point of view of Neutron. We gave them the
    exercise to create and update a port using the OpenStack client with the
    --debug option and then we reviewed the different pieces of the requests
    and responses: HTTP verb, Neutron endpoint, URI, response code, etc. We
    used annotated slides with examples to show these pieces.
  • Neutron's plug-in based architecture, core resources, core plug-in,
    extensions and service plug-ins. The exercise was to list the extensions
    configured in their DevStacks, set-up a new extension in the configuration
    files, re-start the Neutron server and see the attributes added by the new
    extension to ports using the client.
  • Back-end implementation: L2 agent. With graphic slides we reviewed how
    a port is connected to a virtual network using the integration bridge, the
    other bridges that are part of the landscape and we followed the flow of
    the L2 agent wiring a port for Nova. The exercise was to boot an instance,
    use ovs-vsctl and brctl to see how the port was wired and looked at related
    pieces of code in the OVS agent and RPC classes.
  • Back-end implementation: L3 agent. With graphic slides we reviewed how
    routers and floating ips are processed and the different types of routers
    (legacy, DVR, HA, etc.). The exercise was to associate a floating ip to the
    port of the instance created in the previous exercise and using
    iptables-save, examine the entries added by the floating ip creation. We
    also looked at relevant code in the agent and RPC classes.
  • The ML2 plug-in. We reviewed the relationship of the ML2 plug-in and
    the DB plug-in and then, using slides with annotated pseudo-code, went over
    the inner working of the ML2 plug-in: the initiation of the DB transaction,
    pre-commit and post-commit mechanism driver methods, network and port
    contexts, type drivers, port binding, the creation of the response
    dictionary and how all these elements contribute and can affect the DB
    performance. The exercise was to review actual code and then add a
    LOG.debug statement to log the vif_type attribute resulting from a port
    binding.

It is important to mention that the 90 minutes originally scheduled weren't
long enough to cover all these topics. Since the level of interest was so
high among the audience, we decided to try to get together the following
day. With the help of the Foundation support team, we were able to schedule
a 1 hour follow up session that was attended by about a third of the
audience and where we were able to finish all the agenda.

What went well:

  • Current Neutron team members welcoming the on-boarding attendees.
  • The fact that audience members actually showed up for a follow up
    session on Thursday at 3pm and their comments at the end (there was even
    some clapping), suggests that the combination of practical exercises and
    the slides did a good job training the prospective new team team members.
  • The prompt response of the Foundation team to schedule a follow up
    session.

What needs improvement:

  • Make the OpenStack Up-Stream Institute DevStack an explicit requisite
    for the on-boarding session. While many of our attendees had the VM, many
    didn't. I think the importance of this is illustrated by the fact that the
    people motivated enough to show up for the follow up session all had the VM
    in their laptops and followed the exercise to the very end.
  • More time. In our experience, a 3 hours session with a break would be
    ideal. Given the importance for the community of bringing in new developers
    and the fact that our audience was willing to attend a follow up session, a
    3 hours up front investment in new talent seems reasonable.

On Mon, May 22, 2017 at 8:11 AM, Alexandra Settle a.settle@outlook.com
wrote:

Project: Documentation and I18N
Attendees: 3-5 (maybe?)
Etherpad: https://etherpad.openstack.org/p/doc-onboarding

What we did:

We ran the session informally based off whoever was there. Due to the
small attendance, we just ran through how the project works (docs like code
and all that).
Discussed the docs ML, IRC, and how best to get started (find some low
hanging fruit). Ian also took the group through the translation team
process, and gave a little demo on how the Zanata translation tool was used.

We gave everyone back 30 minutes of their lives.

On 5/19/17, 2:22 PM, "Sean Dague" sean@dague.net wrote:

This is a thread for anyone that participated in the onboarding rooms,
on either the presenter or audience side. Because we all went into this
creating things from whole cloth, I'm sure there are lots of lessons
learned.

If you ran a room, please post the project, what you did in the room,
what you think worked, what you would have done differently. If you
attended a room you didn't run, please provide feedback about which one
it was, and what you thought worked / didn't work from the other side

of
the table.

Hopefully we can consolidate some of that feedback for best practices
going forward.

    -Sean

--
Sean Dague
http://dague.net

____________________________________________________________


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:
unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 22, 2017 by Miguel_Lavalle (2,460 points)   1 4
...