Hi all the plan I have is to stay up to the 10, unfortunately I cannot stay on Friday.. is there an option where we could meet after some meetings during the 4 days? Thanks
On Mar 16, 2017, at 08:24, Alexandra Settle <a.settle@outlook.com> wrote:
Hey everyone,
Look out for our project onboarding room at the summit!
If you are available, please come and help out Ian and I :)
Thanks,
Alex
From: Kendall Nelson <kennelson11@gmail.com <mailto:kennelson11@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org <mailto:openstack-dev@lists.openstack.org>> Date: Thursday, March 16, 2017 at 3:10 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org <mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [ptls] Project On-Boarding Rooms
Hello All!
I am pleased to see how much interest there is in these onboarding rooms. As of right now I can accommodate all the official projects (sorry Cyborg) that have requested a room to make all the requests fit, I have combined docs and i18n and taken Thierry's suggestion to combine Infra/QA/RelMgmt/Regs/Stable.
These are the projects that have requested a slot:
Solum Tricircle Karbor Freezer Kuryr Mistral Dragonflow Coudkitty Designate Trove Watcher Magnum Barbican Charms Tacker Zun Swift Watcher Kolla Horizon Keystone Nova Cinder Telemetry Infra/QA/RelMgmt/Regs/Stable Docs/i18n
If there are any other projects willing to share a slot together please let me know!
-Kendall Nelson (diablo_rojo)
On Thu, Mar 16, 2017 at 8:49 AM Jeremy Stanley <fungi@yuggoth.org <mailto:fungi@yuggoth.org>> wrote: On 2017-03-16 10:31:49 +0100 (+0100), Thierry Carrez wrote: [...]
I think we could share a 90-min slot between a number of the supporting teams:
Infrastructure, QA, Release Management, Requirements, Stable maint
Those teams are all under-staffed and wanting to grow new members, but 90 min is both too long and too short for them. I feel like regrouping them in a single slot and give each of those teams ~15 min to explain what they do, their process and tooling, and a pointer to next steps / mentors would be immensely useful.
I can see this working okay for the Infra team. Pretty sure I can't come up with anything useful (to our team) we could get through in a 90-minute slot given our new contributor learning curve, so would feel bad wasting a full session. A "this is who we are and what we do, if you're interested in these sorts of things and want to find out more on getting involved go here, thank you for your time" over 10 minutes with an additional 5 for questions could at least be minimally valuable for us, on the other hand. -- Jeremy Stanley
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe <http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>!DSPAM:58caae586371145111504! __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request@lists.openstack.org <mailto:OpenStack-dev-request@lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev> _______________________________________________ OpenStack-I18n mailing list OpenStack-I18n@lists.openstack.org <mailto:OpenStack-I18n@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n>
!DSPAM:58caae586371145111504!