On 2014年10月14日 12:52, Christopher Yeoh wrote:
On Mon, 13 Oct 2014 22:20:32 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/13/2014 07:11 PM, Christopher Yeoh wrote:
On Mon, 13 Oct 2014 10:52:26 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/10/2014 02:05 AM, Christopher Yeoh wrote:
I
On 10/14/2014 12:52 AM, Christopher Yeoh wrote:
On Mon, 13 Oct 2014 22:20:32 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/13/2014 07:11 PM, Christopher Yeoh wrote:
On Mon, 13 Oct 2014 10:52:26 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/10/2014 02:05 AM, Christopher Yeoh wrote:
I
On Oct 14, 2014, at 8:57 AM, Jay Pipes jaypi...@gmail.com wrote:
I personally think proposing patches to an openstack-api repository is the
most effective way to make those proposals. Etherpads and wiki pages are fine
for dumping content, but IMO, we don't need to dump content -- we already
I found a couple of free times available for a weekly meeting if people are
interested:
https://review.openstack.org/#/c/128332/2
Not sure if a meeting time has been hashed out already or not, and if it
has I'll change the patch accordingly. If not, we can iterate on possible
meeting times in
On 10/14/14, 10:22 AM, Everett Toews everett.to...@rackspace.com wrote:
On Oct 14, 2014, at 8:57 AM, Jay Pipes jaypi...@gmail.com wrote:
I personally think proposing patches to an openstack-api repository is
the most effective way to make those proposals. Etherpads and wiki pages
are fine for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/14/2014 10:22 AM, Everett Toews wrote:
I personally think proposing patches to an openstack-api repository is the
most effective way to make those proposals. Etherpads and wiki pages are
fine for dumping content, but IMO, we don't need to
On Tue, 14 Oct 2014 09:57:01 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/14/2014 05:04 AM, Alex Xu wrote:
There is one reason to think about what projects *currently* do.
When we choice which convention we want.
For example, the CamelCase and snake_case, if the most project use
On Tue, 14 Oct 2014 10:29:34 -0500
Lance Bragstad lbrags...@gmail.com wrote:
I found a couple of free times available for a weekly meeting if
people are interested:
https://review.openstack.org/#/c/128332/2
Not sure if a meeting time has been hashed out already or not, and if
it has I'll
On Tue, Oct 14, 2014 at 4:29 PM, Christopher Yeoh cbky...@gmail.com wrote:
On Tue, 14 Oct 2014 10:29:34 -0500
Lance Bragstad lbrags...@gmail.com wrote:
I found a couple of free times available for a weekly meeting if
people are interested:
https://review.openstack.org/#/c/128332/2
On Tue, 14 Oct 2014 09:45:44 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/14/2014 12:52 AM, Christopher Yeoh wrote:
On Mon, 13 Oct 2014 22:20:32 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/13/2014 07:11 PM, Christopher Yeoh wrote:
On Mon, 13 Oct 2014 10:52:26 -0400
And whilst
On Oct 14, 2014, at 6:00 PM, Lance Bragstad lbrags...@gmail.com wrote:
On Tue, Oct 14, 2014 at 4:29 PM, Christopher Yeoh cbky...@gmail.com wrote:
On Tue, 14 Oct 2014 10:29:34 -0500
Lance Bragstad lbrags...@gmail.com wrote:
I found a couple of free times available for a weekly meeting
Hi all, to my understanding we certainly don't want developers to
arbitrarily extend APIs which would lead to a lot of mess, however we still
need to find a way to standardize how we augment existing APIs since they
are not perfect either.
On Wed, Oct 15, 2014 at 7:02 AM, Doug Hellmann
On 2014年10月14日 21:57, Jay Pipes wrote:
On 10/14/2014 05:04 AM, Alex Xu wrote:
There is one reason to think about what projects *currently* do. When we
choice which convention we want.
For example, the CamelCase and snake_case, if the most project use
snake_case, then choice snake_case style
On Wed, Oct 15, 2014 at 7:44 AM, Christopher Yeoh cbky...@gmail.com wrote:
On Tue, 14 Oct 2014 09:45:44 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/14/2014 12:52 AM, Christopher Yeoh wrote:
On Mon, 13 Oct 2014 22:20:32 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/13/2014
Zhipeng Huang wrote:
HI all, will we have a discussion on this issun at Paris Summit?
I expect the API WG to propose API discussions within the Cross-project
workshops track and get space granted to them.
https://etherpad.openstack.org/p/kilo-crossproject-summit-topics
Cheers,
--
Thierry
On 10/10/2014 02:05 AM, Christopher Yeoh wrote:
I agree with what you've written on the wiki page. I think our priority
needs to be to flesh out
https://wiki.openstack.org/wiki/Governance/Proposed/APIGuidelines
so we have something to reference when reviewing specs. At the moment I
see that
On 10/10/2014 12:09 PM, Jay Pipes wrote:
Thanks for getting this going, Everett! Comments inline...
On 10/08/2014 07:05 PM, Everett Toews wrote:
https://wiki.openstack.org/wiki/API_Working_Group
This is the start of the API Working Group (API WG).
yay! :)
To avoid bike shedding over
On 10/13/2014 11:10 AM, Russell Bryant wrote:
On 10/10/2014 12:09 PM, Jay Pipes wrote:
Thanks for getting this going, Everett! Comments inline...
On 10/08/2014 07:05 PM, Everett Toews wrote:
https://wiki.openstack.org/wiki/API_Working_Group
This is the start of the API Working Group (API
Zhipeng Huang wrote:
THX for the link ! So we will have the workshop on Nov 3th at Meridien
Etoile Hotel?
The workshops happen on the 4th (Tuesday).
--
Thierry Carrez (ttx)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On Mon, 13 Oct 2014 10:52:26 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/10/2014 02:05 AM, Christopher Yeoh wrote:
I agree with what you've written on the wiki page. I think our
priority needs to be to flesh out
https://wiki.openstack.org/wiki/Governance/Proposed/APIGuidelines
so we
On 10/13/2014 07:11 PM, Christopher Yeoh wrote:
On Mon, 13 Oct 2014 10:52:26 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/10/2014 02:05 AM, Christopher Yeoh wrote:
I agree with what you've written on the wiki page. I think our
priority needs to be to flesh out
2014-10-13 16:52 GMT+02:00 Jay Pipes jaypi...@gmail.com:
On 10/10/2014 02:05 AM, Christopher Yeoh wrote:
I agree with what you've written on the wiki page. I think our priority
needs to be to flesh out
https://wiki.openstack.org/wiki/Governance/Proposed/APIGuidelines
so we have something to
On Mon, 13 Oct 2014 22:20:32 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/13/2014 07:11 PM, Christopher Yeoh wrote:
On Mon, 13 Oct 2014 10:52:26 -0400
Jay Pipes jaypi...@gmail.com wrote:
On 10/10/2014 02:05 AM, Christopher Yeoh wrote:
I agree with what you've written on the wiki
HI all, will we have a discussion on this issun at Paris Summit?
On Sun, Oct 12, 2014 at 8:32 AM, Preston L. Bannister pres...@bannister.us
wrote:
Tricky. First, I am new to OpenStack, and as such tend to want to shut-up
and listen.
Second, I have done APIs for distributed systems for over
Thanks for getting this going, Everett! Comments inline...
On 10/08/2014 07:05 PM, Everett Toews wrote:
https://wiki.openstack.org/wiki/API_Working_Group
This is the start of the API Working Group (API WG).
yay! :)
To avoid bike shedding over the name of the working group, I decided
to
Hi Everett,
Great to see things moving with the API Working Group!
On Thu, Oct 9, 2014 at 9:35 AM, Everett Toews everett.to...@rackspace.com
wrote:
https://wiki.openstack.org/wiki/API_Working_Group
This is the start of the API Working Group (API WG).
To avoid bike shedding over the name of
26 matches
Mail list logo
