or usage
questions)" <openstack-dev@lists.openstack.org>
Sent: Tuesday, April 5, 2016 11:09:38 AM
Subject: RE: [openstack-dev] [Tricircle] Naming convention
Hi, Shinobu,
Fully agree with you that this is a dilemma situation: If we use full word, for
example "availaibility_zone_aggre
t: Tuesday, April 05, 2016 9:46 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Tricircle] Naming convention
Hi Chaoyi,
Thank you for your reply.
How about this:
# tricircle/api/pod.py
94 aggregate = az_ag.create_ag_
ang )
>
>
> -Original Message-
> From: Shinobu Kinjo [mailto:shinobu...@gmail.com]
> Sent: Saturday, April 02, 2016 7:40 AM
> To: joehuang; OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Tricircle] Naming convention
Huang )
-Original Message-
From: Shinobu Kinjo [mailto:shinobu...@gmail.com]
Sent: Saturday, April 02, 2016 7:40 AM
To: joehuang; OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Tricircle] Naming convention
One of examples is:
"""
t;joehu...@huawei.com> wrote:
> yes, good idea, could you point out or
> report a bug which are not good naming.
>
> thanks.
>
> Sent from HUAWEI AnyOffice
> 发件人：shinobu.kj
> 收件人：openstack-dev,
> 时间：2016-04-02 06:21:50
> 主题:[openstack-dev] [Tricircle] Naming co
Hi Team,
Probably it's worth thinking of naming convention for classes, methods
or whatever we define in source codes.
Some names are lengthy and there might be no consistency. At the
moment it's fine. But once this project gets growing, situation would
become chaotic and could cause bugs.
What
