Re: [openstack-dev] [Nova] Thoughts from the PTL
On Tue, Apr 15, 2014 at 10:01:32AM -0500, Brian Elliott wrote: * specs review. The new blueprint process is a work of genius, and I think its already working better than what we've had in previous releases. However, there are a lot of blueprints there in review, and we need to focus on making sure these get looked at sooner rather than later. I'd especially like to encourage operators to take a look at blueprints relevant to their interests. Phil Day from HP has been doing a really good job at this, and I'd like to see more of it. I have mixed feelings about the nova-specs repo. I dig the open collaboration of the blueprints process, but I also think there is a danger of getting too process-oriented here. Are these design documents expected to call out every detail of a feature? Ideally, I’d like to see only very high level documentation in the specs repo. Basically, the spec could include just enough detail for people to agree that they think a feature is worth inclusion. More detailed discussion could remain on the code reviews since they are the actual end work product. Having design discussions via gerrit comments on the actual code has been a really ineffective approach, because the stuff being discussed is often spread across multiple files and across multiple separate gerrit changes. That makes it hard to have a coherant discussion on the broad picture. The discussions get buried under the avalanche of comments from the many CI systems we have now too. The latter is IMHO one of the biggest problems I face in reviewing code changes in gerrit in general today. I think it is really beneficial to have a fleshed out design proposal right from the start. I've reviewed many patches where the feature overall made sense, but the implementation approach taken was total madness, needing a major/total rewrite. This was a major waste of time for the person submitting the patch, as well as for all the reviewers before me. A lot of people providing blueprints to Nova don't neccessarily have the domain knowledge to realize there are better ways of achieving their desired goals. So having them provide a high level design, allows for those who are knowledgable to guide them before they go down the wrong road. I've also come across cases where patches claimed to address a particular use case, but when you look at it in detail you find its actually missing the goal. A detailed blueprint makes it easier for reviewers to actually see if the proposed code is satisfying the original goals or not, as well as allowing people who later test the feature to evaluate whether it is working as intended or not. Finally the docs people have to writeup all these new features, and often struggle with the woefully under-specified blueprints we've had in previous releases. These better fleshed out blueprints should serve as a good basis for the docs people to writeup new features. IOW I think the nova specs design repo is going to be a significant win for everyone involved in Nova across the board. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL -- possible mid cycle meetup dates
I think it's important to remember that not all mid cycle meetups are the same kind of thing. - the infra / havana one was a bootstrapping event - the nova / icehouse one was a mini design summit - the neutron / icehouse one was specifically focused on QA improvement - the tripleo / icehouse one was a sprint Collocating mid cycle events only seems to make sense if the 2 events are the same kind of thing, the audience for different kinds of events will be somewhat different. And, honestly, I don't see much value in collocating overlapping events for mid cycle meetups. We already do that twice a year, it's called design summit. :) -Sean On 04/16/2014 01:27 AM, Chris Jones wrote: Hey Co-locating still has the option to partially overlap the two sprints. Cheers, -- Chris Jones On 16 Apr 2014, at 02:38, Michael Still mi...@stillhq.com wrote: On Wed, Apr 16, 2014 at 10:01 AM, Robert Collins robe...@robertcollins.net wrote: On 16 April 2014 11:28, Michael Still mi...@stillhq.com wrote: On Wed, Apr 16, 2014 at 7:57 AM, Hugh O. Brock hbr...@redhat.com wrote: On Wed, Apr 16, 2014 at 09:30:45AM +1200, Robert Collins wrote: Redhat offered to host the next TripleO midcycle meetup in Raleigh, I don't know if they have space for Nova TripleO at once, but I'd love to get more collaboration time betwixt Nova and TripleO. The TripleO midcycle meetups are 'doing' meetings, not planning meetings - but plenty of planning does still happen ;) Date wise, how about before OSCON ? PyConAU which often gets a heavy openstack contingent is august 1-5. I am sure we have enough space, we would be very happy to host both at the same time. I envision at the same time being back to back to be honest, as I think running two in parallel would be a bit bonkers. I can't travel for a single 2 week trip - my daughter doesn't cope super well with me being gone, and I don't want to subject her to a 2 week trip. Doing a 2-or-3 day meetup for TripleO is pointless IMO - folk spend a day getting there in the first place. Last cycle TripleO and Ironic co-located and it was productive for all involved. This may mean that co-locating is an idea which doesn't work out. Based on the way the last nova meetup went, there will be little time to dig into the deeper specifics of tripleo (ironic especially) if its in time that's also allocated to other nova discussion -- I think the absolute longest we spent on a single topic last time was in the order of a couple of hours. The nova meetup also wasn't a hackfest -- it was more about design review and progress tracking, and I think that was a model that worked well for us. I see a need for a lot of sync between ironic and nova for Juno, mostly around the replacement of the baremetal driver. Perhaps instead we should go back to trying to have these events separately, and try and get a few key nova people to the the tripleo meetup. Michael -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On Apr 13, 2014, at 11:58 PM, Michael Still mi...@stillhq.com wrote: First off, thanks for electing me as the Nova PTL for Juno. I find the outcome of the election both flattering and daunting. I'd like to thank Dan and John for running as PTL candidates as well -- I strongly believe that a solid democratic process is part of what makes OpenStack so successful, and that isn't possible without people being will to stand up during the election cycle. Congrats! I'm hoping to send out regular emails to this list with my thoughts about our current position in the release process. Its early in the cycle, so the ideas here aren't fully formed yet -- however I'd rather get feedback early and often, in case I'm off on the wrong path. What am I thinking about at the moment? The following things: * a mid cycle meetup. I think the Icehouse meetup was a great success, and I'd like to see us do this again in Juno. I'd also like to get the location and venue nailed down as early as possible, so that people who have complex travel approval processes have a chance to get travel sorted out. I think its pretty much a foregone conclusion this meetup will be somewhere in the continental US. If you're interested in hosting a meetup in approximately August, please mail me privately so we can chat. Yeah this was a great opportunity to collaborate and keep the project pointed in the right direction during Icehouse. * specs review. The new blueprint process is a work of genius, and I think its already working better than what we've had in previous releases. However, there are a lot of blueprints there in review, and we need to focus on making sure these get looked at sooner rather than later. I'd especially like to encourage operators to take a look at blueprints relevant to their interests. Phil Day from HP has been doing a really good job at this, and I'd like to see more of it. I have mixed feelings about the nova-specs repo. I dig the open collaboration of the blueprints process, but I also think there is a danger of getting too process-oriented here. Are these design documents expected to call out every detail of a feature? Ideally, I’d like to see only very high level documentation in the specs repo. Basically, the spec could include just enough detail for people to agree that they think a feature is worth inclusion. More detailed discussion could remain on the code reviews since they are the actual end work product. Thanks, Brian ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On Mon, Apr 14, 2014 at 7:06 PM, Stefano Maffulli stef...@openstack.org wrote: On 04/14/2014 06:58 AM, Michael Still wrote: First off, thanks for electing me as the Nova PTL for Juno. Congratulations Michael. * I promised to look at mentoring newcomers. The first step there is working out how to identify what newcomers to mentor, and who mentors them. I'm very interested in the mentoring topic, too. As many may know, the Foundation will host an Upstream Training session in Atlanta. This is first attempt at formalizing the process to become a *good* contributor to OpenStack. Mentorship is a crucial part of that training, which is made of in-person classes and online mentorship (before and after the in-person training). OpenStack project has also two other programs where mentorship is crucial: Outreach Program for Women (it's been running for almost 2 years now) and we added also Google Summer of Code. Mentoring is now becoming a thing we do among the other things we do. I think the easy targets to mentor are Upstream students, OPW and GSoC candidates. I'd be happy to have a session at the summit about this. Sounds good to me. The goal here from the nova side is to have nova be a fun project to contribute to so that we don't shed the developers we need to sustain our growth over time. Adding new developers is important because people do leave nova in a natural process of moving onto other problems, so we need to be growing new developers to replace attrition. I'm intending to drop in on the Upstream University stuff happening the weekend before the summit and see if there's any way I can help. Cheers, Michael -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On 14 April 2014 16:58, Michael Still mi...@stillhq.com wrote: First off, thanks for electing me as the Nova PTL for Juno. I find the outcome of the election both flattering and daunting. I'd like to thank Dan and John for running as PTL candidates as well -- I strongly believe that a solid democratic process is part of what makes OpenStack so successful, and that isn't possible without people being will to stand up during the election cycle. +1 - me too, it was great to see James Slagle stand up and volunteer this cycle. * a mid cycle meetup. I think the Icehouse meetup was a great success, and I'd like to see us do this again in Juno. I'd also like to get the location and venue nailed down as early as possible, so that people who have complex travel approval processes have a chance to get travel sorted out. I think its pretty much a foregone conclusion this meetup will be somewhere in the continental US. If you're interested in hosting a meetup in approximately August, please mail me privately so we can chat. Redhat offered to host the next TripleO midcycle meetup in Raleigh, I don't know if they have space for Nova TripleO at once, but I'd love to get more collaboration time betwixt Nova and TripleO. The TripleO midcycle meetups are 'doing' meetings, not planning meetings - but plenty of planning does still happen ;) Date wise, how about before OSCON ? PyConAU which often gets a heavy openstack contingent is august 1-5. -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On Wed, Apr 16, 2014 at 09:30:45AM +1200, Robert Collins wrote: On 14 April 2014 16:58, Michael Still mi...@stillhq.com wrote: First off, thanks for electing me as the Nova PTL for Juno. I find the outcome of the election both flattering and daunting. I'd like to thank Dan and John for running as PTL candidates as well -- I strongly believe that a solid democratic process is part of what makes OpenStack so successful, and that isn't possible without people being will to stand up during the election cycle. +1 - me too, it was great to see James Slagle stand up and volunteer this cycle. * a mid cycle meetup. I think the Icehouse meetup was a great success, and I'd like to see us do this again in Juno. I'd also like to get the location and venue nailed down as early as possible, so that people who have complex travel approval processes have a chance to get travel sorted out. I think its pretty much a foregone conclusion this meetup will be somewhere in the continental US. If you're interested in hosting a meetup in approximately August, please mail me privately so we can chat. Redhat offered to host the next TripleO midcycle meetup in Raleigh, I don't know if they have space for Nova TripleO at once, but I'd love to get more collaboration time betwixt Nova and TripleO. The TripleO midcycle meetups are 'doing' meetings, not planning meetings - but plenty of planning does still happen ;) Date wise, how about before OSCON ? PyConAU which often gets a heavy openstack contingent is august 1-5. I am sure we have enough space, we would be very happy to host both at the same time. --Hugh -- == Hugh Brock, hbr...@redhat.com == == Senior Engineering Manager, Cloud Engineering == == Tuskar: Elastic Scaling for OpenStack == == http://github.com/tuskar== I know that you believe you understand what you think I said, but I’m not sure you realize that what you heard is not what I meant. --Robert McCloskey ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On 2014-04-16 09:30:45 +1200 (+1200), Robert Collins wrote: Redhat offered to host the next TripleO midcycle meetup in Raleigh, [...] Neat--I live in that town! We definitely need more OpenStack happening in it. ;) -- Jeremy Stanley ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL -- possible mid cycle meetup dates
On Wed, Apr 16, 2014 at 7:57 AM, Hugh O. Brock hbr...@redhat.com wrote: On Wed, Apr 16, 2014 at 09:30:45AM +1200, Robert Collins wrote: Redhat offered to host the next TripleO midcycle meetup in Raleigh, I don't know if they have space for Nova TripleO at once, but I'd love to get more collaboration time betwixt Nova and TripleO. The TripleO midcycle meetups are 'doing' meetings, not planning meetings - but plenty of planning does still happen ;) Date wise, how about before OSCON ? PyConAU which often gets a heavy openstack contingent is august 1-5. I am sure we have enough space, we would be very happy to host both at the same time. I envision at the same time being back to back to be honest, as I think running two in parallel would be a bit bonkers. I'm now sitting on a list of about four or five offered venues, with no plan for how to select which one to use. Perhaps what we should do is pick the dates, then ask each venue if they're available in that window, and then come up with some way to select from the remaining venues. I deeply appreciate all the offers of hosting -- its a great way for companies to contribute to OpenStack, and makes a real difference to our ability to deliver great software. Perhaps what we should do with the venues that offer and don't get selected is keep them on a list of venues to use for future meetups? That will make those meetups easier to organise, and recognises the kind offers from the venues. Cheers, Michael -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL -- possible mid cycle meetup dates
On 16 April 2014 11:28, Michael Still mi...@stillhq.com wrote: On Wed, Apr 16, 2014 at 7:57 AM, Hugh O. Brock hbr...@redhat.com wrote: On Wed, Apr 16, 2014 at 09:30:45AM +1200, Robert Collins wrote: Redhat offered to host the next TripleO midcycle meetup in Raleigh, I don't know if they have space for Nova TripleO at once, but I'd love to get more collaboration time betwixt Nova and TripleO. The TripleO midcycle meetups are 'doing' meetings, not planning meetings - but plenty of planning does still happen ;) Date wise, how about before OSCON ? PyConAU which often gets a heavy openstack contingent is august 1-5. I am sure we have enough space, we would be very happy to host both at the same time. I envision at the same time being back to back to be honest, as I think running two in parallel would be a bit bonkers. I can't travel for a single 2 week trip - my daughter doesn't cope super well with me being gone, and I don't want to subject her to a 2 week trip. Doing a 2-or-3 day meetup for TripleO is pointless IMO - folk spend a day getting there in the first place. Last cycle TripleO and Ironic co-located and it was productive for all involved. I'm now sitting on a list of about four or five offered venues, with no plan for how to select which one to use. Perhaps what we should do is pick the dates, then ask each venue if they're available in that window, and then come up with some way to select from the remaining venues. I deeply appreciate all the offers of hosting -- its a great way for companies to contribute to OpenStack, and makes a real difference to our ability to deliver great software. Perhaps what we should do with the venues that offer and don't get selected is keep them on a list of venues to use for future meetups? That will make those meetups easier to organise, and recognises the kind offers from the venues. Not a bad idea ;) -Rob -- Robert Collins rbtcoll...@hp.com Distinguished Technologist HP Converged Cloud ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL -- possible mid cycle meetup dates
On Wed, Apr 16, 2014 at 10:01 AM, Robert Collins robe...@robertcollins.net wrote: On 16 April 2014 11:28, Michael Still mi...@stillhq.com wrote: On Wed, Apr 16, 2014 at 7:57 AM, Hugh O. Brock hbr...@redhat.com wrote: On Wed, Apr 16, 2014 at 09:30:45AM +1200, Robert Collins wrote: Redhat offered to host the next TripleO midcycle meetup in Raleigh, I don't know if they have space for Nova TripleO at once, but I'd love to get more collaboration time betwixt Nova and TripleO. The TripleO midcycle meetups are 'doing' meetings, not planning meetings - but plenty of planning does still happen ;) Date wise, how about before OSCON ? PyConAU which often gets a heavy openstack contingent is august 1-5. I am sure we have enough space, we would be very happy to host both at the same time. I envision at the same time being back to back to be honest, as I think running two in parallel would be a bit bonkers. I can't travel for a single 2 week trip - my daughter doesn't cope super well with me being gone, and I don't want to subject her to a 2 week trip. Doing a 2-or-3 day meetup for TripleO is pointless IMO - folk spend a day getting there in the first place. Last cycle TripleO and Ironic co-located and it was productive for all involved. This may mean that co-locating is an idea which doesn't work out. Based on the way the last nova meetup went, there will be little time to dig into the deeper specifics of tripleo (ironic especially) if its in time that's also allocated to other nova discussion -- I think the absolute longest we spent on a single topic last time was in the order of a couple of hours. The nova meetup also wasn't a hackfest -- it was more about design review and progress tracking, and I think that was a model that worked well for us. I see a need for a lot of sync between ironic and nova for Juno, mostly around the replacement of the baremetal driver. Perhaps instead we should go back to trying to have these events separately, and try and get a few key nova people to the the tripleo meetup. Michael -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL -- possible mid cycle meetup dates
Hey Co-locating still has the option to partially overlap the two sprints. Cheers, -- Chris Jones On 16 Apr 2014, at 02:38, Michael Still mi...@stillhq.com wrote: On Wed, Apr 16, 2014 at 10:01 AM, Robert Collins robe...@robertcollins.net wrote: On 16 April 2014 11:28, Michael Still mi...@stillhq.com wrote: On Wed, Apr 16, 2014 at 7:57 AM, Hugh O. Brock hbr...@redhat.com wrote: On Wed, Apr 16, 2014 at 09:30:45AM +1200, Robert Collins wrote: Redhat offered to host the next TripleO midcycle meetup in Raleigh, I don't know if they have space for Nova TripleO at once, but I'd love to get more collaboration time betwixt Nova and TripleO. The TripleO midcycle meetups are 'doing' meetings, not planning meetings - but plenty of planning does still happen ;) Date wise, how about before OSCON ? PyConAU which often gets a heavy openstack contingent is august 1-5. I am sure we have enough space, we would be very happy to host both at the same time. I envision at the same time being back to back to be honest, as I think running two in parallel would be a bit bonkers. I can't travel for a single 2 week trip - my daughter doesn't cope super well with me being gone, and I don't want to subject her to a 2 week trip. Doing a 2-or-3 day meetup for TripleO is pointless IMO - folk spend a day getting there in the first place. Last cycle TripleO and Ironic co-located and it was productive for all involved. This may mean that co-locating is an idea which doesn't work out. Based on the way the last nova meetup went, there will be little time to dig into the deeper specifics of tripleo (ironic especially) if its in time that's also allocated to other nova discussion -- I think the absolute longest we spent on a single topic last time was in the order of a couple of hours. The nova meetup also wasn't a hackfest -- it was more about design review and progress tracking, and I think that was a model that worked well for us. I see a need for a lot of sync between ironic and nova for Juno, mostly around the replacement of the baremetal driver. Perhaps instead we should go back to trying to have these events separately, and try and get a few key nova people to the the tripleo meetup. Michael -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On Apr 13, 2014, at 9:58 PM, Michael Still mi...@stillhq.com wrote: First off, thanks for electing me as the Nova PTL for Juno. I find the First off, congrats! * a mid cycle meetup. I think the Icehouse meetup was a great success, and I'd like to see us do this again in Juno. I'd also like to get the location and venue nailed down as early as possible, so that people who have complex travel approval processes have a chance to get travel sorted out. I think its pretty much a foregone conclusion this meetup will be somewhere in the continental US. If you're interested in hosting a meetup in approximately August, please mail me privately so we can chat. I think one of the outcomes from the first one was that we should try to do it earlier. Feature freeze would be somewhere around first week of September. I’d like to see us do it the last week of July at the latest, I think. That is still ‘approximately August’, I guess. :) Thoughts? - Chris ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On 04/14/2014 06:58 AM, Michael Still wrote: First off, thanks for electing me as the Nova PTL for Juno. Congratulations Michael. * I promised to look at mentoring newcomers. The first step there is working out how to identify what newcomers to mentor, and who mentors them. I'm very interested in the mentoring topic, too. As many may know, the Foundation will host an Upstream Training session in Atlanta. This is first attempt at formalizing the process to become a *good* contributor to OpenStack. Mentorship is a crucial part of that training, which is made of in-person classes and online mentorship (before and after the in-person training). OpenStack project has also two other programs where mentorship is crucial: Outreach Program for Women (it's been running for almost 2 years now) and we added also Google Summer of Code. Mentoring is now becoming a thing we do among the other things we do. I think the easy targets to mentor are Upstream students, OPW and GSoC candidates. I'd be happy to have a session at the summit about this. /stef -- Ask and answer questions on https://ask.openstack.org ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On 04/14/2014 08:58 AM, Chris Behrens wrote: On Apr 13, 2014, at 9:58 PM, Michael Still mi...@stillhq.com wrote: First off, thanks for electing me as the Nova PTL for Juno. I find the First off, congrats! Congrats Michael. And good luck! * a mid cycle meetup. I think the Icehouse meetup was a great success, and I'd like to see us do this again in Juno. I'd also like to get the location and venue nailed down as early as possible, so that people who have complex travel approval processes have a chance to get travel sorted out. I think its pretty much a foregone conclusion this meetup will be somewhere in the continental US. If you're interested in hosting a meetup in approximately August, please mail me privately so we can chat. I think one of the outcomes from the first one was that we should try to do it earlier. Feature freeze would be somewhere around first week of September. I’d like to see us do it the last week of July at the latest, I think. That is still ‘approximately August’, I guess. :) Thoughts? Agreed - although there was time to get things in for I after the meetup in Provo, and indeed some of the discussed things did get in, it felt like all of the discussions had a but probably not for Icehouse at this point disclaimer. Also consider that we should be thinking about the feature proposal freeze rather then the feature freeze, and also that the bar for BPs has been raised, as praised in the original email :) N. - Chris ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On Mon, Apr 14, 2014 at 4:58 PM, Chris Behrens cbehr...@codestud.com wrote: On Apr 13, 2014, at 9:58 PM, Michael Still mi...@stillhq.com wrote: First off, thanks for electing me as the Nova PTL for Juno. I find the First off, congrats! Thanks! * a mid cycle meetup. I think the Icehouse meetup was a great success, and I'd like to see us do this again in Juno. I'd also like to get the location and venue nailed down as early as possible, so that people who have complex travel approval processes have a chance to get travel sorted out. I think its pretty much a foregone conclusion this meetup will be somewhere in the continental US. If you're interested in hosting a meetup in approximately August, please mail me privately so we can chat. I think one of the outcomes from the first one was that we should try to do it earlier. Feature freeze would be somewhere around first week of September. I’d like to see us do it the last week of July at the latest, I think. That is still ‘approximately August’, I guess. :) That's a fair point. I'd put it in the middle of the six month release cycle, but you're right that we should not include FFE in that period. I guess that means sometime in July would be the winner. However, we'd need to work around OSCON and have to somehow find a balance between it being well placed and it also not being absurdly close to the summit in May. Let me stare at a calendar tomorrow and come up with a more concrete proposal. Cheers, Michael -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On 04/14/2014 05:06 AM, Stefano Maffulli wrote: On 04/14/2014 06:58 AM, Michael Still wrote: First off, thanks for electing me as the Nova PTL for Juno. Congratulations Michael. * I promised to look at mentoring newcomers. The first step there is working out how to identify what newcomers to mentor, and who mentors them. I agree that identifying which newcomers to mentor is key. I have found that I don't always get it right, and am disappointed when I spend time and energy on someone who then disappears but for the most part the first thing I look for is consistency, do they show up everyday in a given week? If yes, they get more of my time. Then I look for quality of questions and willingness to take suggestions. Mostly I work on a gut feeling here, if I am mentoring someone I need to feel like my time is well spent. I find it hard to articulate but I do know when I have found someone worthy of mentoring. Then I look at failure communication, we all feel dumb. Does this person stop communicating when they hit an obstacle? Do they use tools like paste and etherpad to show me what they are seeing? The better the person communicates, or is willing to be taught to communicate, the better I can help them. Then I look at personal characteristics, like trust, honesty and integrity. If this person disagrees with me or has a different perspective, will they tell me? If something comes up for them in their personal life or if management has thrown them a curve, will they tell me? Life happens to all of us, what is this person's ability to share what I need to know to make the best use of my time? These are just some thoughts off the top of my head. I hope they are useful to you. I support this direction. Oh and congrats on the PTLship, Anita. I'm very interested in the mentoring topic, too. As many may know, the Foundation will host an Upstream Training session in Atlanta. This is first attempt at formalizing the process to become a *good* contributor to OpenStack. Mentorship is a crucial part of that training, which is made of in-person classes and online mentorship (before and after the in-person training). OpenStack project has also two other programs where mentorship is crucial: Outreach Program for Women (it's been running for almost 2 years now) and we added also Google Summer of Code. Mentoring is now becoming a thing we do among the other things we do. I think the easy targets to mentor are Upstream students, OPW and GSoC candidates. I'd be happy to have a session at the summit about this. /stef ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On 04/14/2014 10:52 AM, Anita Kuno wrote: On 04/14/2014 05:06 AM, Stefano Maffulli wrote: On 04/14/2014 06:58 AM, Michael Still wrote: First off, thanks for electing me as the Nova PTL for Juno. Congratulations Michael. * I promised to look at mentoring newcomers. The first step there is working out how to identify what newcomers to mentor, and who mentors them. I agree that identifying which newcomers to mentor is key. I have found that I don't always get it right, and am disappointed when I spend time and energy on someone who then disappears but for the most part the first thing I look for is consistency, do they show up everyday in a given week? If yes, they get more of my time. Then I look for quality of questions and willingness to take suggestions. Mostly I work on a gut feeling here, if I am mentoring someone I need to feel like my time is well spent. I find it hard to articulate but I do know when I have found someone worthy of mentoring. Then I look at failure communication, we all feel dumb. Does this person stop communicating when they hit an obstacle? Do they use tools like paste and etherpad to show me what they are seeing? The better the person communicates, or is willing to be taught to communicate, the better I can help them. Then I look at personal characteristics, like trust, honesty and integrity. If this person disagrees with me or has a different perspective, will they tell me? If something comes up for them in their personal life or if management has thrown them a curve, will they tell me? Life happens to all of us, what is this person's ability to share what I need to know to make the best use of my time? These are just some thoughts off the top of my head. I hope they are useful to you. I support this direction. Oh and congrats on the PTLship, Anita. I should add the other quality I really like in someone I mentor. I teach in a style that is reproducible and expect who I work with to be able to mentor others once they are ready. So one of the questions at the back of my mind is, is this person willing to take what I give them and share with others? This is usually a question that gets answered over time, as I encourage them to share and then gauge their response. Thanks, Anita. I'm very interested in the mentoring topic, too. As many may know, the Foundation will host an Upstream Training session in Atlanta. This is first attempt at formalizing the process to become a *good* contributor to OpenStack. Mentorship is a crucial part of that training, which is made of in-person classes and online mentorship (before and after the in-person training). OpenStack project has also two other programs where mentorship is crucial: Outreach Program for Women (it's been running for almost 2 years now) and we added also Google Summer of Code. Mentoring is now becoming a thing we do among the other things we do. I think the easy targets to mentor are Upstream students, OPW and GSoC candidates. I'd be happy to have a session at the summit about this. /stef ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On Mon, Apr 14, 2014 at 2:58 PM, Michael Still mi...@stillhq.com wrote: Thanks for taking the time to read this email, and please do let me know if you think this sort of communication is useful. Hi. I just want to thank the ten or so people who've privately replied to this email with questions... I'm going to reply to them all, but it might take a little while. I hope to get through them all today. So -- I just want people to know they're not being ignored, they're just in a queue. Please hold, your email is important to us! Michael -- Rackspace Australia ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Nova] Thoughts from the PTL
On 4/13/14 11:58 PM, Michael Still mi...@stillhq.com wrote: * specs review. The new blueprint process is a work of genius, and I think its already working better than what we've had in previous releases. However, there are a lot of blueprints there in review, and we need to focus on making sure these get looked at sooner rather than later. I'd especially like to encourage operators to take a look at blueprints relevant to their interests. Phil Day from HP has been doing a really good job at this, and I'd like to see more of it. Agreed! We are trying to get more Operators to comment and review, because very few of us have to date. I'll try to drop a gentle reminder to the list. I know that Tom Fifield has been plugging it every chance he gets. You are right, though, Phil really has been shouldering a load for the lot of us. :) I'm sure we'll highlight it a lot at the ATL summit - especially with the extra Ops focused sessions. Congrats again! Matt ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
