Re: [openstack-dev] [Tricircle] Original Blueprint

2016-04-07 Thread Shinobu Kinjo
All clear.

Cheers,
Shinobu

On Thu, Apr 7, 2016 at 5:21 PM, joehuang <joehu...@huawei.com> wrote:
> Yes, of course.
>
> And in Newton release, we want to use BP + spec for review and approve for 
> new features, just like https://review.openstack.org/#/c/282180/.
>
> Best Regards
> Chaoyi Huang ( Joe Huang )
>
>
> -Original Message-
> From: Shinobu Kinjo [mailto:shinobu...@gmail.com]
> Sent: Thursday, April 07, 2016 4:16 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Tricircle] Original Blueprint
>
> Hi Chaoyi,
>
> Just to clarify more.
>
> On Thu, Apr 7, 2016 at 5:02 PM, joehuang <joehu...@huawei.com> wrote:
>> Hi, Shinobu,
>>
>> Thanks for your review. Just replied in the google doc, that the table is 
>> the latest design, not old one, and some fields need to be implemented in 
>> new patches.
>
> I'm now expecting that *blueprint* is always master; meaning that anyone who 
> would contribute to the Tricircle need to refer, follow *blueprint*.
>
> Is it same of what you are thinking of?
>
> Cheers,
> Shinobu
>
>>
>> Best Regards
>> Chaoyi Huang ( Joe Huang )
>>
>>
>> -Original Message-
>> From: Shinobu Kinjo [mailto:shinobu...@gmail.com]
>> Sent: Thursday, April 07, 2016 12:44 PM
>> To: OpenStack Development Mailing List (not for usage questions)
>> Subject: [openstack-dev] [Tricircle] Original Blueprint
>>
>> Hi Chaoyi,
>>
>> In blueprint you described for PoC, there are information of tables. [1] 
>> They seem to out-to-date.
>>
>> Do you think that those information need to be up-to-date in your blueprint?
>> If it's not necessary, it's better to move those information to different 
>> sheet or put some comment like "Won't be updated", I think.
>>
>> [1]
>> https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l
>> 2zNqMEd3g
>>
>> Cheers,
>> Shinobu
>>
>> --
>> Email:
>> shin...@linux.com
>> GitHub:
>> shinobu-x
>> Blog:
>> Life with Distributed Computational System based on OpenSource
>>
>> __
>>  OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> Email:
> shin...@linux.com
> GitHub:
> shinobu-x
> Blog:
> Life with Distributed Computational System based on OpenSource
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Email:
shin...@linux.com
GitHub:
shinobu-x
Blog:
Life with Distributed Computational System based on OpenSource

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


Re: [openstack-dev] [Tricircle] Original Blueprint

2016-04-07 Thread joehuang
Yes, of course. 

And in Newton release, we want to use BP + spec for review and approve for new 
features, just like https://review.openstack.org/#/c/282180/.

Best Regards
Chaoyi Huang ( Joe Huang )


-Original Message-
From: Shinobu Kinjo [mailto:shinobu...@gmail.com] 
Sent: Thursday, April 07, 2016 4:16 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Tricircle] Original Blueprint

Hi Chaoyi,

Just to clarify more.

On Thu, Apr 7, 2016 at 5:02 PM, joehuang <joehu...@huawei.com> wrote:
> Hi, Shinobu,
>
> Thanks for your review. Just replied in the google doc, that the table is the 
> latest design, not old one, and some fields need to be implemented in new 
> patches.

I'm now expecting that *blueprint* is always master; meaning that anyone who 
would contribute to the Tricircle need to refer, follow *blueprint*.

Is it same of what you are thinking of?

Cheers,
Shinobu

>
> Best Regards
> Chaoyi Huang ( Joe Huang )
>
>
> -Original Message-
> From: Shinobu Kinjo [mailto:shinobu...@gmail.com]
> Sent: Thursday, April 07, 2016 12:44 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [Tricircle] Original Blueprint
>
> Hi Chaoyi,
>
> In blueprint you described for PoC, there are information of tables. [1] They 
> seem to out-to-date.
>
> Do you think that those information need to be up-to-date in your blueprint?
> If it's not necessary, it's better to move those information to different 
> sheet or put some comment like "Won't be updated", I think.
>
> [1] 
> https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l
> 2zNqMEd3g
>
> Cheers,
> Shinobu
>
> --
> Email:
> shin...@linux.com
> GitHub:
> shinobu-x
> Blog:
> Life with Distributed Computational System based on OpenSource
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Email:
shin...@linux.com
GitHub:
shinobu-x
Blog:
Life with Distributed Computational System based on OpenSource

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Tricircle] Original Blueprint

2016-04-07 Thread Shinobu Kinjo
Hi Chaoyi,

Just to clarify more.

On Thu, Apr 7, 2016 at 5:02 PM, joehuang <joehu...@huawei.com> wrote:
> Hi, Shinobu,
>
> Thanks for your review. Just replied in the google doc, that the table is the 
> latest design, not old one, and some fields need to be implemented in new 
> patches.

I'm now expecting that *blueprint* is always master; meaning that
anyone who would contribute to the Tricircle need to refer, follow
*blueprint*.

Is it same of what you are thinking of?

Cheers,
Shinobu

>
> Best Regards
> Chaoyi Huang ( Joe Huang )
>
>
> -Original Message-
> From: Shinobu Kinjo [mailto:shinobu...@gmail.com]
> Sent: Thursday, April 07, 2016 12:44 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [Tricircle] Original Blueprint
>
> Hi Chaoyi,
>
> In blueprint you described for PoC, there are information of tables. [1] They 
> seem to out-to-date.
>
> Do you think that those information need to be up-to-date in your blueprint?
> If it's not necessary, it's better to move those information to different 
> sheet or put some comment like "Won't be updated", I think.
>
> [1] 
> https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g
>
> Cheers,
> Shinobu
>
> --
> Email:
> shin...@linux.com
> GitHub:
> shinobu-x
> Blog:
> Life with Distributed Computational System based on OpenSource
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Email:
shin...@linux.com
GitHub:
shinobu-x
Blog:
Life with Distributed Computational System based on OpenSource

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


Re: [openstack-dev] [Tricircle] Original Blueprint

2016-04-07 Thread joehuang
Hi, Shinobu,

Thanks for your review. Just replied in the google doc, that the table is the 
latest design, not old one, and some fields need to be implemented in new 
patches.

Best Regards
Chaoyi Huang ( Joe Huang )


-Original Message-
From: Shinobu Kinjo [mailto:shinobu...@gmail.com] 
Sent: Thursday, April 07, 2016 12:44 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Tricircle] Original Blueprint

Hi Chaoyi,

In blueprint you described for PoC, there are information of tables. [1] They 
seem to out-to-date.

Do you think that those information need to be up-to-date in your blueprint?
If it's not necessary, it's better to move those information to different sheet 
or put some comment like "Won't be updated", I think.

[1] 
https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g

Cheers,
Shinobu

--
Email:
shin...@linux.com
GitHub:
shinobu-x
Blog:
Life with Distributed Computational System based on OpenSource

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


[openstack-dev] [Tricircle] Original Blueprint

2016-04-06 Thread Shinobu Kinjo
Hi Chaoyi,

In blueprint you described for PoC, there are information of tables. [1]
They seem to out-to-date.

Do you think that those information need to be up-to-date in your blueprint?
If it's not necessary, it's better to move those information to
different sheet or put some comment like "Won't be updated", I think.

[1] 
https://docs.google.com/document/d/18kZZ1snMOCD9IQvUKI5NVDzSASpw-QKj7l2zNqMEd3g

Cheers,
Shinobu

-- 
Email:
shin...@linux.com
GitHub:
shinobu-x
Blog:
Life with Distributed Computational System based on OpenSource

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