My advice is two-fold: - No need to wait for the blueprint to be approved before submitting a review - put a review up and let people see the details, then respond to the discussion as necessary - Drop into the Wednesday (16:00 UTC) IRC meeting for Cinder - most if not all of the core team are usually on and we can answer any specific questions then. The Agenda is on the wiki if you want to add to it. All welcome On 3 April 2014 11:37, Lingxian Kong <anlin.kong at gmail.com> wrote: > Thanks Duncan for your answer. > > I am very interested in making a contribution towards this effort, but > what to do next? Waiting for approving for this blueprint? Or see > others' opinions on this before we putting more efforts in achieving > this? I just want to make sure that we could handle other people's use > cases and not just our own. > > > > > 2014-04-03 18:12 GMT+08:00 Duncan Thomas <duncan.thomas at gmail.com>: >> >> On 3 April 2014 08:28, 王宏 <w.wanghong1 at gmail.com> wrote: >> > I agree. Actually, I already have a BP on it: >> > https://blueprints.launchpad.net/cinder/+spec/restore-image. >> > I am happy for any suggestion. >> >> Needs a little thought since container_format and some other fields >> will need to be regenerated (e.g. we can source for a QCOW image, but >> we always upload raw), but as long as these are dealt with it seems >> like a useful feature >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > -- > --------------------------------------- > Lingxian Kong > Huawei Technologies Co.,LTD. > IT Product Line CloudOS PDU > China, Xi'an > Mobile: +86-18602962792 > Email: konglingxian at huawei.com; anlin.kong at gmail.com > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Duncan Thomas