Re: [openstack-dev] [all] The future of the integrated release

On 08/08/2014 02:37 AM, Thierry Carrez wrote: > I agree with Eoghan here. The main goal of an agile/lean system is to > maximize a development team productivity. The main goal of Open source > project management is not to maximize productivity. It’s to maximize > contributions. I wrote about that a

Re: [openstack-dev] [all] The future of the integrated release

On 08/13/2014 07:33 AM, Ian Wells wrote: > I have no great answer to this, but is there a way - perhaps via team > sponsorship from cores to ensure that the general direction is right, > and cloned repositories for purpose-specific changes, as one example - > that we can get an audience of people t

Re: [openstack-dev] Fwd: FW: [Neutron] Group Based Policy and the way forward

On 08/12/2014 06:46 PM, Wuhongning wrote: > I couldn't have been at the IRC meeting for the time difference, are > there any conclusion for this topic, or is it still open? I, the PTL, some core reviewers and many in the GBP team are actively working on a proposal to send to the list for quick eva

Re: [openstack-dev] [Octavia] Minutes from 8/13/2014 meeting

Thanks for the summary Trevor. On 08/18/2014 01:25 PM, Trevor Vardeman wrote: > 1) Discuss future of Octavia in light of Neutron-incubator project proposal. > a) There are many problems with Neutron-Incubator as currently described Let's be specific, enumerate the problems and address them, p

[openstack-dev] Network/Incubator proposal (was Re: [Octavia] Minutes from 8/13/2014 meeting)

On 08/19/2014 08:39 AM, Eichberger, German wrote: > Just to be clear: We all think the incubator is a great idea and if > some things are ironed out will be a good way to onboard new projects > to Neutron. What bothers me is the timing. Without warning we were > put in an incubator in the span of l

Re: [openstack-dev] [all] The future of the integrated release

On 08/19/2014 07:37 AM, Jay Pipes wrote: > All of these projects should be able to live in the Program, in the > openstack/ code namespace, for as long as the project is actively > developed, and let the contributor communities in these competing > projects *naturally* work to do any of the followi

Re: [openstack-dev] generate Windows exe

Hi Szepe, On Wed 20 Aug 2014 11:33:47 AM PDT, Szépe Viktor wrote: > Thank you for your answer. > That workflow seems a huge job for me. > > I leave this patch up to you. thanks for sending this fix. You've stumbled upon one of the known issues of OpenStack's way to deal with small patches like yo

Re: [openstack-dev] [Octavia] IRC meetings

On 08/21/2014 10:14 AM, Doug Wiegley wrote: > We made the voice/IRC decision in the very format that favors voice. So > in the interest of putting the discussion to bed, voice your opinions here > in a non-voice way: I was about to voice (ha!) my opinion there but I stopped because I don't think

Re: [openstack-dev] New feature on Nova

On 08/21/2014 08:00 AM, thomas.pessi...@orange.com wrote: > Sorry if I am not on the right mailing list. I would like to get some > information. No problem, this is the correct mailing list as this message is about discussing the "future" of an openstack component. > I would like to know if I am

Re: [openstack-dev] [all] The future of the integrated release

I think we can't throw Ceilometer and Triple-O in the same discussion: they're two separate issues IMHO, with different root causes and therefore different solutions. On 08/21/2014 06:27 AM, Jay Pipes wrote: > The point I've been making is > that by the TC continuing to bless only the Ceilometer p

Re: [openstack-dev] What does NASA not using OpenStack mean to OS's future

On 08/25/2014 02:36 PM, Joshua Harlow wrote: > So to see if we can get something useful from this thread. not on this mailing list. Move it somewhere else: this thread is off topic here. /stef ___ OpenStack-dev mailing list OpenStack-dev@lists.openstac

Re: [openstack-dev] [all] [ptls] The Czar system, or how to scale PTLs

On Mon 25 Aug 2014 03:38:18 PM CDT, Zane Bitter wrote: > I'd say we've done fairly well, but I would attribute that at least in > part to the fact that we've treated the PTL as effectively the > temporary "release management contact" more than the "guy who will > resolve disputes for us". In other

Re: [openstack-dev] [all] [ptls] The Czar system, or how to scale PTLs

On 08/22/2014 08:19 PM, John Dickinson wrote: > I think Anne makes some excellent points about the pattern being > proposed being unlikely to be commonly implemented across all the > programs (or, at best, very difficult). Let's not try to formalize > another "best practice" that works many times a

Re: [openstack-dev] [neutron] Incubator concerns from packaging perspective

On 08/21/2014 03:12 AM, Ihar Hrachyshka wrote: > I wonder where discussion around the proposal is running. Is it public? Yes, it's public, and this thread is part of it. Look at the dates of the wiki: this is a recent proposal (first appearance Aug 11), came out to address the GBP issue, quickly i

Re: [openstack-dev] [neutron][lbaas][octavia]

On 08/28/2014 03:04 PM, Susanne Balle wrote: > Just for us to learn about the incubator status, here are some of the > info on incubation: > > https://wiki.openstack.org/wiki/Governance/Approved/Incubation > https://wiki.openstack.org/wiki/Governance/NewProjects These are not the correct document

Re: [openstack-dev] [OpenStack-Infra] [third-party] [infra] New mailing lists for third party announcements and account requests

On Fri 29 Aug 2014 12:47:00 PM PDT, Elizabeth K. Joseph wrote: > Third-party-request > > This list is the new place to request the creation or modification of > your third party account. Note that old requests sent to the > openstack-infra mailing list don't need to be resubmitted, they are > alrea

Re: [openstack-dev] [OpenStack-Infra] [third-party] [infra] New mailing lists for third party announcements and account requests

On Fri 29 Aug 2014 03:03:34 PM PDT, James E. Blair wrote: > It's the best way we have right now, until we have time to make it more > self-service. We received one third-party CI request in 2 years, then > we received 88 more in 6 months. Our current process is built around > the old conditions.

[openstack-dev] znc as a service (was Re: [nova] Is the BP approval process broken?)

On 08/29/2014 11:17 AM, John Garbutt wrote: > After moving to use ZNC, I find IRC works much better for me now, but > I am still learning really. There! this sentence has two very important points worth highlighting: 1- when people say IRC they mean IRC + a hack to overcome its limitation 2- IRC+

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

Thanks Daniel for taking the time to write such deep message. Obviously you have thought about this issue for a long time and your opinion comes from deep personal understanding. I'm adding tags for neutron and cinder, as I know they're having similar conversations. I don't have a strong opinion o

Re: [openstack-dev] [Manila]

Hi Jyoti This is the wrong email list: we use openstack-dev only to discuss future development of OpenStack project. Use the General mailing list or the one for Operators (check http://lists.openstack.org). Alternatively search for answers (and if you don't find any, ask questions) on https:/

[openstack-dev] DefCore Community Meetings 9/10 & 9/11 AGENDA (Lighthouse.7)

The DefCore project is moving forward and needs more and more eyes on it. The next meetings are on Sept 9 and 10, with the same agenda to facilitate global access. I'm sharing the details below. All members of OpenStack ecosystem should follow this process closely as it is going to define what an

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

On 09/05/2014 07:07 PM, James Bottomley wrote: > Actually, I don't think this analysis is accurate. Some people are > simply interested in small aspects of a project. It's the "scratch your > own itch" part of open source. The thing which makes itch scratchers > not lone wolfs is the desire to g

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

On 09/09/2014 06:55 AM, James Bottomley wrote: > CLAs are a well known and documented barrier to casual contributions I'm not convinced about this statement, at all. And since I think it's secondary to what we're discussing, I'll leave it as is and go on. > I've done both ... I do prefer the patc

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

On 09/05/2014 12:36 PM, Tim Bell wrote: > How can the average deployer know whether a stackforge is > > a. An early prototype which has completed (such as some of the > early LBaaS packages) > > b. A project which has lost its initial steam and further > investment is not foreseen > >

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

On 09/10/2014 02:27 AM, Sylvain Bauza wrote: > Well, both proposals can be done : we can create subteams and the > Subteam-Approval Gerrit label right know before Kilo, and we could split > the virt repos by later once the interfaces and prereqs are done. That's what I mean in fact: create sub tea

Re: [openstack-dev] [Zaqar] Comments on the concerns arose during the TC meeting

On 09/10/2014 12:56 PM, Monty Taylor wrote: > I reject soundly and fundamentally the idea that Open Source projects > NEED a commercial ecosystem to provide solid quality software. That's not what I said. I said that assuring the quality of code on a public repository is not necessarily something

Re: [openstack-dev] [all] OpenStack bootstrapping hour - Friday Sept 19th - 3pm EST

On 09/15/2014 03:56 PM, Sean Dague wrote: > A few of us have decided to pull together a regular (cadence to be > determined) video series taking on deep dives inside of OpenStack, > looking at code, explaining why things work that way, and fielding > questions from anyone interested. > > For lack

Re: [openstack-dev] [UX] Automatically post new threads from AskBot to the list

On 11/19/2013 08:19 AM, Julie Pichon wrote: > I've been thinking about the AskBot UX website [0] and its lack of > visibility, particularly for new community members. Indeed, it's one of the drawbacks of splitting groups: information tends not to flow very well. > I think it would be valuable to

Re: [openstack-dev] Propose "project story wiki" idea

On 11/19/2013 09:33 PM, Boris Pavlovic wrote: > The idea of this proposal is that every OpenStack project should have > "story" wiki page. It means to publish every week one short message that > contains most interesting updates for the last week, and high level road > map for future week. So readi

Re: [openstack-dev] welcoming new committers

On 10/31/2013 11:49 AM, Stefano Maffulli wrote: > Another idea that Tom suggested is to use gerrit automation to send back > to first time committers something in addition to the normal 'your patch > is waiting for review' message. The message could be something like: [...] T

Re: [openstack-dev] How to best make User Experience a priority in every project

On 12/06/2013 02:19 AM, Jaromir Coufal wrote: > We are growing. At the moment we are 4 core members and others are > coming in. But honestly, contributors are not coming to specific > projects - they go to reach UX community in a sense - OK this is awesome > effort, how can I help? What can I work

[openstack-dev] [Metrics] Communicating how to interpret community data

Hello folks I wrote a blog post today after noticing again that reporters take the data published on Activity Board and Stackalytics as true, without asking questions to the protagonists. The problem is that at the moment none of the systems we have can guarantee that the data is presenting at any

Re: [openstack-dev] Stackalytics 0.4 released! [metrics]

On 12/12/2013 07:49 AM, Ilya Shakhat wrote: > Stackalytics team is happy to announce the release of version 0.4. [...] Good job Ilya, congratulations on the release. I may not be able to join the meeting (too early for me) so I leave here some feedback for you. I like the new punchcards in the pe

Re: [openstack-dev] Diversity as a requirement for incubation

On 12/18/2013 07:01 AM, Dolph Mathews wrote: > Options 2 and 3 sound identical to me, when realistically applied. > Option 3 just makes the common sense aspect mandatory. Indeed, Option 3 gets my vote. One aspect I'd like to mention regarding diversity of contributors in any open source project is

Re: [openstack-dev] Implementing VPNaas in Openstack Grizzly release

On Mon 13 Jan 2014 11:04:01 PM PST, Ashwini Babureddy wrote: > I have added all the configurations mentioned below in the mail but > getting the same error while executing the command Please move this thread to the General mailing list or the Operators list or https://ask.openstack.org. Reserve t

[openstack-dev] Sent the first batch of invitations to Atlanta's Summit

A few minutes ago we sent the first batch of invites to people who contributed to any of the official OpenStack programs[1] from 00:00 UTC on April 4, 2014 (Grizzly release day) until present. We'll send more invites *after each milestone* from now on and until feature freeze (March 6th, according

[openstack-dev] [nova][swift] Importing Launchpad Answers in Ask OpenStack

Hello folks we're almost ready to import all questions and asnwers from LP Answers into Ask OpenStack. You can see the result of the import from Nova on the staging server http://ask-staging.openstack.org/ There are some formatting issues for the imported questions and I'm trying to evaluate how

Re: [openstack-dev] [nova][swift] Importing Launchpad Answers in Ask OpenStack

On Wed 29 Jan 2014 01:49:04 PM CET, Swapnil Kulkarni wrote: > Getting lauchpad bus in ask.openstack would really help people and > this looks really nice.(just saw some question-answers) I was not able > to search for questions though Yes, we know, search is disabled on staging. > and (answered

[openstack-dev] Speaking at PyCON US 2014 about OpenStack?

If you're going to talk about anything related to OpenStack at PyCON US/Canada this year, please let me know. We're collecting the list of talks related to the project. Cheers, stef -- Ask and answer questions on https://ask.openstack.org ___ OpenStac

Re: [openstack-dev] Speaking at PyCON US 2014 about OpenStack?

On Thu 30 Jan 2014 09:36:56 PM CET, Jarret Raim wrote: > Paul Kehrer and I are talking about the state of crypto in Python. The > talk isn't specifically about OpenStack, but we will be talking about > various OpenStack related issues including the Barbican service. Thanks Jarret, that's exactly t

[openstack-dev] Ready to import Launchpad Answers into Ask OpenStack

Hello folks, we're ready to import the answers from Launchpad into Ask OpenStack. A script will import all questions, answers, comments (and data abou user accounts) from LP into Ask, tag them as the project of origin (nova, swift, etc). You can see the results of the test runs on http://ask-stagi

Re: [openstack-dev] Ready to import Launchpad Answers into Ask OpenStack

Hi Sergey On Tue 11 Feb 2014 08:01:48 AM CET, Sergey Lukjanov wrote: > Stefano, is it possible to import savanna's answers@launchpad to ask.o.o? Yes, indeed. I apologize for not putting you explicitly in the cc list. The full list of projects we'll work on is on the bug itself: https://bugs.la

Re: [openstack-dev] Sent the first batch of invitations to Atlanta's Summit

On 02/17/2014 05:21 PM, Steve Kowalik wrote: > I found it completely non-obvious too, and had to go back and look for > the link. If the promotion code text box was always visible with the > Apply button grayed out when the text box is empty, I think that would help. Unfortunately the site is mana

Re: [openstack-dev] [Cinder] Open Source and community working together

On 03/01/2014 03:30 PM, John Griffith wrote: > I just wanted to send out a quick note on a topic that came up recently. > Unfortunately the folks that I'd like to read this most; don't > participate on the ML typically, but I'd at least like to raise some > community awareness. [...] Thanks for b

Re: [openstack-dev] [nova][swift] Importing Launchpad Answers in Ask OpenStack

s to close Answers. I'll contact the PTLs to edit the projects. Cheers, stef On 01/28/2014 04:38 PM, Stefano Maffulli wrote: > Hello folks > > we're almost ready to import all questions and asnwers from LP Answers > into Ask OpenStack. You can see the result of the import from N

Re: [openstack-dev] Proposal to move from Freenode to OFTC

-1 to the switch from me. this question from Sean is of fundamental value: On 03/03/2014 03:19 PM, Sean Dague wrote: > #1) do we believe OFTC is fundamentally better equipped to resist a > DDOS, or do we just believe they are a smaller target? The ongoing DDOS > on meetup.com the past 2 weeks is

Re: [openstack-dev] [Cinder] Open Source and community working together

On the topic of 'always improving our community', here is the announcement I promised On 03/03/2014 01:52 PM, Stefano Maffulli wrote: > [...] We'll have a first > edition of this program in Atlanta. Some more details on the wiki > https://wiki.openstack.org/wiki/OpenStac

Re: [openstack-dev] Board election

On 11/30/2014 06:44 AM, Gary Kotton wrote: > When I log into the site I am unable to nominate people. Any ideas? I > get: "*Your account credentials do not allow you to nominate candidates.**”* That means that the account you're using is not the account of an Individual Member of OpenStack Foundat

Re: [openstack-dev] [neutron] Changes to the core team

On 12/04/2014 09:24 AM, Anita Kuno wrote: > I think we move into very dangerous territory if we are equating a core > review Gerrit permission (it is just a Gerrit permission, if it is > perceived as anything other than that that is a perception we have > created ourselves) with value as an OpenSta

Re: [openstack-dev] People of OpenStack (and their IRC nicks)

On 12/09/2014 06:04 AM, Jeremy Stanley wrote: > We already have a solution for tracking the contributor->IRC > mapping--add it to your Foundation Member Profile. For example, mine > is in there already: > > http://www.openstack.org/community/members/profile/5479 I recommend updating the opens

Re: [openstack-dev] People of OpenStack (and their IRC nicks)

On 12/10/2014 02:30 AM, Matthew Gilliard wrote: > So, are we agreed that http://www.openstack.org/community/members/ is > the authoritative place for IRC lookups? In which case, I'll take the > old content out of https://wiki.openstack.org/wiki/People and leave a > message directing people where to

Re: [openstack-dev] [nova] Kilo specs review day

On 12/10/2014 01:41 PM, Michael Still wrote: > at the design summit we said that we would not approve specifications > after the kilo-1 deadline, which is 18 December. Unfortunately, we’ve > had a lot of specifications proposed this cycle (166 to my count), and > haven’t kept up with the review wor

Re: [openstack-dev] [neutron] Spec reviews this week by the neutron-drivers team

I have adapted to Neutron the specs review dashboard prepared by Joe Gordon for Nova. Check it out below. Reminder: the deadline to approve kilo specs is this coming Monday, Dec 15. https://review.openstack.org/#/dashboard/?foreach=project%3A%5Eopenstack%2Fneutron-specs+status%3Aopen+NOT+owner%3A

Re: [openstack-dev] [Neutron] Core/Vendor code decomposition

On 12/09/2014 04:11 PM, by wrote: >>>[vad] how about the documentation in this case?... bcos it needs some > place to document (a short desc and a link to vendor page) or list these > kind of out-of-tree plugins/drivers... just to make the user aware of > the availability of such plugins/driers w

Re: [openstack-dev] [OpenStack-Infra] [third-party]Time for Additional Meeting for third-party

On 12/05/2014 07:08 AM, Kurt Taylor wrote: > 1. Meeting content: Having 2 meetings per week is more than is needed at > this stage of the working group. There just isn't enough meeting content > to justify having two meetings every week. I'd like to discuss this further: the stated objectives of t

[openstack-dev] The scope of OpenStack wiki [all]

hello folks, TL;DR Many wiki pages and categories are maintained elsewhere and to avoid confusion to newcomers we need to agree on a new scope for the wiki. A suggestion below is to limit its scope to content that doesn't need/want peer-review and is not hosted elsewhere (no duplication). The wik

Re: [openstack-dev] The scope of OpenStack wiki [all]

On Thu, 2015-01-08 at 12:52 -0800, Sean Roberts wrote: > Thanks for bringing this up Stef. I have found while introducing > OpenStack fundamentals in the user groups, what seems logical to us, > the fully OpenStack immersed, is confusing to newcomers. Yeah, I'm diving more in the wiki in preparat

Re: [openstack-dev] The scope of OpenStack wiki [all]

On Fri, 2015-01-09 at 10:35 +0100, Thierry Carrez wrote: > One of the issues here is that the wiki also serves as a default > starting page for "all things not on www.openstack.org" (its main page > is a list of relevant links). So at the same time we are moving > authoritative content out of the w

[openstack-dev] openstack-dev topics now work correctly

Dear all, if you've tried the topics on this mailing list and haven't received emails, well... we had a problem on our side: the topics were not setup correctly. Luigi Toscano helped isolate the problem and point at the solution[1]. He noticed that only the "QA topic" was working and that's the o

[openstack-dev] Why all OpenStack Foundation Individual Members should vote now [all]

HOW TO VOTE: If you are an eligible voter[1], you should have received an email with the subject “OpenStack Foundation – 2015 Individual Director Election” from secret...@openstack.org. This email includes your unique voting link. If you did not receive an email, please contact secret...@openstack.

Re: [openstack-dev] [all] "All rights reserved" V.S. "Apache license"

On Sat, 2015-01-17 at 16:07 -0500, Monty Taylor wrote: > It's actually a set of words that is no longer necessary as of the year > 2000. It's not communicating anything about a granted license, which is > what the Apache License does - it's actually just asserting that the > original copyright hold

Re: [openstack-dev] OpenStack access using Java SDK

On Mon 05 May 2014 05:47:02 AM PDT, Vikas Kokare wrote: > I am looking for a standard, seamless way to access OpenStack APIs , > most likely using the Java SDKs that are summarized at > https://wiki.openstack.org/wiki/SDKs#Software_Development_Kits [...] This is the wrong list for usage questions,

Re: [openstack-dev] How-to and best practices for developing new OpenStack service

On 05/08/2014 12:16 AM, Ruslan Kiianchuk wrote: > Short tutorial for developers not familiar with OpenStack infrastructure > still would be useful. My task is to help Python developers that haven't > worked with OpenStack before start an OpenStack service development in > the shortest possible peri

[openstack-dev] Announcing Community Office Hours

Hello folks one of the requests in Atlanta was to setup carefully listening ears for developers and users alike so they can highlight roadblocks, vent frustration and hopefully also give kudos to people, suggest solutions, etc. I and Tom have added two 1 hour slots to the OpenStack Meetings calen

Re: [openstack-dev] [infra] Gerrit downtime on May 23 for project renames

On 05/23/2014 03:58 PM, James E. Blair wrote: > This is complete. The actual list of renamed projects is: [...] have any of these projects changed also their launchpad name? thanks .stef ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org

Re: [openstack-dev] Fwd: Re: [openstack-tc] use of the word certified

On 06/10/2014 10:39 AM, Jay Pipes wrote: > We've been begging for input on this > stuff at the board and dev list level for a while now. And people are all ear now and leaving comments, which is good :) I think adding a clear warning on stackalytics.com that the data from DriverLog may not be accu

Re: [openstack-dev] Fwd: Fwd: Debian people don't like bash8 as a project name (Bug#748383: ITP: bash8 -- bash script style guide checker)

On Thu 12 Jun 2014 03:53:35 PM PDT, Morgan Fainberg wrote: > I understand your concerns here, and I totally get what you’re driving > at, but in the packaging world wouldn’t this make sense to call it > "python-bash8"? Now the binary, I can agree (for reasons outlined) > should probably not be name

[openstack-dev] [metrics] How to group activity in git/gerrit repositories

Hello folks, we're working on a quarterly report of activities in all our git and gerrit repositories to understand the dynamics of contributions across different dimensions. This report will be similar to what Bitergia produced at release time. I'd like to discuss more widely the format of how t

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

On 06/13/2014 05:57 AM, Doug Hellmann wrote: > That section of the file used to be organized in to separate lists > for incubated, integrated, and "other" repositories. We changed it > when we started tracking the incubation and integration dates. So it > seems like just listing them under sahar

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

On Fri 13 Jun 2014 10:51:24 AM PDT, Stangel, Dan wrote: > You can also refer to the example of Stackalytics, who have created > their own hierarchy and groupings for metrics reporting: > https://github.com/stackforge/stackalytics/blob/master/etc/default_data.json It's a very neat grouping. It seem

Re: [openstack-dev] New Contributor Agreement is not working?

Hi Sami, sorry for this. I suspect there is something going on with gerrit which throws the inappropriate error message (more below). On 06/17/2014 12:57 AM, "Sami J. Mäkinen" wrote: > For several weeks now, I just always get an error message included below. In these cases and in general, don't

Re: [openstack-dev] [OpenStack-Infra] [3rd Party] Log retention with 3rd party testing

[trimming reply-to to OpenStack Development since I don't think that infra is the right venue to discuss this] On 06/13/2014 10:08 AM, trinath.soman...@freescale.com wrote: > I have two scenarios to deal with. > > [1] A change takes two months or more to get merged into the master > branch. > >

Re: [openstack-dev] New Contributor Agreement is not working?

On 06/17/2014 10:45 AM, "Sami J. Mäkinen" wrote: > Yay. I really just had to become a new OpenStack Foundation Member. > The error message I got is just not too informative, I could not > help thinking there is something really broken. Right, unfortunately the error message from gerrit cannot be c

Re: [openstack-dev] [metrics] How to group activity in git/gerrit repositories

On 06/16/2014 12:25 PM, Ilya Shakhat wrote: > Most of groups are created from the official programs > .yaml. Every program turns into item in the module > list (colored in violet), for example 'Nova Compute' is a group > containing 'nova', 'python-novaclient' and 'nova-specs'.

Re: [openstack-dev] Travel Support Program validation date vs. early-bird deadline

Hi Sylvain, On 03/08/2014 09:34 AM, Sylvain Bauza wrote: > As I only requested for hotel+travel support, I was supposed to use my > ATC badge for the registration, *but* it is clearly explained that the > coupon code is only valid until March 21... Thanks for bringing it up, indeed I think we can

Re: [openstack-dev] [nova] OPENSTACK SERVICE ERROR

On 03/17/2014 11:14 AM, Ben Nemec wrote: > First, please don't use all caps in your subject. Second, please do use > tags to indicate which projects your message relates to. In this case, > that appears to be nova. third (actually, zero: this is the most important part of all) Don't use the dev

Re: [openstack-dev] Constructive Conversations

Hello Kurt, all, On 03/07/2014 01:56 PM, Kurt Griffiths wrote: > There have been a variety of instances where community members have > expressed their ideas and concerns via email or at a summit, or simply > submitted a patch that perhaps challenges someone’s opinion of The Right > Way to Do It, a

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

On 03/10/2014 04:10 PM, Edgar Magana wrote: > A have a few arguments why I believe this is not 100% inclusive I think by "100% inclusive" you mean "getting the right people for the problem to solve" in the room. I would support that objective. Do you think there are some key people who would need

Re: [openstack-dev] [Nova] Updates to Juno blueprint review process

On 03/20/2014 03:50 PM, Jay Lau wrote: > It is better that we can have some diagram workflow just like > Gerrit_Workflow to > show the new process. Indeed, I think it would help. While I'm here, and for the records, I think that creating a new wor

Re: [openstack-dev] [Nova] Updates to Juno blueprint review process

On 03/22/2014 03:14 AM, Sean Dague wrote: > Honestly, I largely disagree. This is applying some process where there > clearly wasn't any before. We have a different perception evidently. I'm assuming you're exaggerating for the sake of clarity because assuming there was no process before means tha

Re: [openstack-dev] [Nova] Updates to Juno blueprint review process

On 03/24/2014 09:20 AM, Russell Bryant wrote: > Another critical point of clarification ... we are *not* moving out of > blueprints at all. We're still using them for tracking, just as before. > We are *adding* the use of gerrit for reviewing the design. That changes things, thank you for the cl

Re: [openstack-dev] [Nova] Updates to Juno blueprint review process

On 03/25/2014 01:30 AM, Russell Bryant wrote: > I really don't see why this is so bad. We're using a tool specifically > designed for reviewing things that is already working *really* well, right, for code reviews. > not just for code, but also for TC governance documents. I disagree: that's a

Re: [openstack-dev] User mailing lists for OpenStack projects

Hi Shaunak, the lists for the OpenStack project are hosted on http://lists.openstack.org. You can see the full roster on that page. If you need a special list for the users of OpenStack PHP SDK you can propose a change to the lists manifest on openstack-infra/config/modules/openstack_project/mani

[openstack-dev] Dealing with changes of plans, rejections and other annoyances

Hello folks, we've been hearing a lot about the incredible growth of the OpenStack community but we don't hear much about the incredible amount of pressure that comes with such growth. One huge problem that growth brings with is that new comers have not had time to assimilate the culture of OpenSt

Re: [openstack-dev] Dealing with changes of plans, rejections and other annoyances

On 03/27/2014 06:25 PM, Anita Kuno wrote: > Back to my point, when newcomers come into an opensource project with no > understanding of what opensource means or how to communicate in an > opensource project, that creates additional learning demand that might > not have been in evidence previously.

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 in

[openstack-dev] Reviewing spelling and grammar errors in blueprints Re: [Nova] nova-specs

On 04/16/2014 07:56 PM, Dan Smith wrote: >> Do we really want to -1 for spelling mistake in nova-specs? > > I do, yes. These documents are intended to be read by deployers and > future developers. I think it's really important that they're useful in > that regard. Guys, use your judgement with th

Re: [openstack-dev] [metrics] New version of the Activity Board

Thank you Daniel, great job. On 09/17/2014 09:03 AM, Daniel Izquierdo wrote: > * Further work > = > - Add Juno release information It's coming :) > - Allow to have projects navigation per release This is interesting > - Add Askbot data per release This is really not needed, don't spen

Re: [openstack-dev] [TripleO] Set WIP for stale patches?

On Fri 19 Sep 2014 09:25:10 AM PDT, Jeremy Stanley wrote: > Here we'll just have to agree to disagree. I think core reviewers > hiding behind an automated process so that they don't have to > confront contributors about stalled/inadequate changes is inherently > less friendly. Clearly you feel that

Re: [openstack-dev] [Nova] [All] API standards working group

On 09/24/2014 10:05 AM, Jay Pipes wrote: > Whatever it ends up being, it needs to have some teeth to it. Otherwise, > we're going to end up in the exact same place we're in now, where each > project does something slightly different. +1 I think getting started and produce some material to discuss

[openstack-dev] Of wiki and contributors docs (was Re: [Nova] [All] API standards working group)

On 09/24/2014 09:09 PM, Anne Gentle wrote: > I think the wiki is a great place to get ideas out while we look for a > cross-project specs workflow in the meantime. The wiki is a great place to store things temporarily until they mature and find a stable home :) Speaking of wiki, those of you tha

Re: [openstack-dev] [Openstack-docs] Contributing to docs without Docbook -- YES you can!

hi Nick, On 09/29/2014 02:06 PM, Nicholas Chase wrote: > Because we know that the networking documentation needs particular > attention, we're starting there. We have a Networking Guide, from which > we will ultimately pull information to improve the networking section of > the admin guide. I

Re: [openstack-dev] [api] API Workgroup git repository

Hi Chris On 10/21/2014 11:08 PM, Christopher Yeoh wrote: > The API Workgroup git repository has been setup and you can access it > here. Cool, adding it to the repos to watch. > There is some content there though not all the proposed guidelines from > the wiki page are in yet: > > https://wiki.op

Re: [openstack-dev] [all] How can we get more feedback from users?

Hi Angus, quite a noble intent, one that requires lots of attempts like this you have started. On 10/23/2014 09:32 PM, Angus Salkeld wrote: > I have felt some grumblings about usability issues with Heat > templates/client/etc.. > and wanted a way that users could come and give us feedback easily

Re: [openstack-dev] [all] How can we get more feedback from users?

On 10/23/2014 11:16 PM, Angus Salkeld wrote: > Thanks for those pointers, we very interested in feedback from > operators, but > in this case I am talking more about end users not operators (people > that actually use our API). Great! There is a working group being formed also for that. I would su

Re: [openstack-dev] [all][doc] project testing interface

On 10/24/2014 03:03 PM, Anne Gentle wrote: > The git link is the reference, and we're working on publishing those, > just have to get a URL/home sorted out. > > In the meantime, yes, you can update the wiki page. Why not delete the wiki altogether? I think stale content on the wiki is damaging us

Re: [openstack-dev] FreeBSD host support

On 10/27/2014 08:51 AM, Drew Fisher wrote: > If devstack itself (not CI, but devstack) is a hard requirement for > integration we need to probably start up a different thread on what the > best way for other OSes like FreeBSD and Solaris to work around this > issue. What should we be looking at?

Re: [openstack-dev] [Infra][all] Synchronizing local Git and Gerrit repositories

On 10/29/2014 07:02 AM, Ondrej Wisniewski wrote: > If I understand correctly, we cannot use the OpenStack community Git > servers as our central Git repository since developers cannot push to > them. And we don't want to go through Gerrit and the code review > procedure just to share a bit of code

Re: [openstack-dev] TC election by the numbers

On 11/01/2014 04:31 PM, Eoghan Glynn wrote: > So, just to round out this thread, the key questions are: > > * whether a low & declining turnout is a real problem I'd like to point out that there 580 'regular' contributors at the moment[1], these are the authors of 95% of the OpenStack code. 506

[openstack-dev] [all] A more dynamic wiki, introducing Categories

Hello folks in the past months Shari and I have implemented more chunks of the taxonomy developed for us by Katherine Cranford (a volunteer expert). Using categories in the wiki pages can help us create dynamic pages and keep information more visible, well organized and discoverable. For example,

  1   2   3   >