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] [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/07/2014 01:41 PM, Eoghan Glynn wrote: > My point was simply that we don't have direct control over the > contributors' activities This is not correct and I've seen it repeated too often to let it go uncorrected: we (the OpenStack project as a whole) have a lot of control over contributors to

Re: [openstack-dev] [Octavia] Weekly meetings resuming + agenda

On Thu 07 Aug 2014 12:12:26 PM PDT, Brandon Logan wrote: > It's just my own preference. Others like webex/hangouts because it can > be easier to talk about topics than in IRC, but with this many people > and the latency delays, it can become quite cumbersome. Plus, it makes > it easier for meetin

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

On 08/07/2014 01:49 AM, Thierry Carrez wrote: > As an ex factory IT manager, I feel compelled to comment on that :) Multidisciplinary training rules! As an architect with field experience building roads, sidewalks, roofs, city planning (and training in lean manufacturing and services) I think I ca

Re: [openstack-dev] How to improve the specs review process

On 08/06/2014 04:54 PM, Kevin Benton wrote: > I'm curious, how would having Nova reviewers look at this have helped? In general, we should try to involve users in all spec reviews. With Nova being a (heavy) user of Neutron, I think, in general, having Nova people involved would help. In general.

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

On 08/06/2014 04:57 PM, Aaron Rosen wrote: > Gah, clearly hitting some kind of gmail bug as i replied to the right > thread all 3 times i believe. gmail is the new Outlook ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.op

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

On Wed 06 Aug 2014 02:10:23 PM PDT, Michael Still wrote: > - we rate limit the total number of blueprints under code review at > any one time to a fixed number of "slots". I secretly prefer the term > "runway", so I am going to use that for the rest of this email. A > suggested initial number of r

Re: [openstack-dev] How to improve the specs review process (was Re: [Neutron] Group Based Policy and the way forward)

On Wed 06 Aug 2014 01:21:26 PM PDT, Eugene Nikanorov wrote: > So I don't think it's fair to blame reviewers here. Just want to be super clear: there is no 'blaming' here. This is a request to regroup and look at why we are having this conversation about GBP now, this late in cycle, and about such

[openstack-dev] How to improve the specs review process (was Re: [Neutron] Group Based Policy and the way forward)

On 08/06/2014 11:19 AM, Edgar Magana wrote: > That is the beauty of the open source projects, there is always a smartest > reviewer catching out the facts that you don¹t. And yet, the specification clearly talks about 'endpoints' and nobody caught it where it supposed to be caught so I fear that s

Re: [openstack-dev] [neutron] [not-only-neutron] How to Contribute upstream in OpenStack Neutron

On 07/31/2014 11:24 AM, Stefano Maffulli wrote: > Given the amount of google juice that Ask OpeNStack gets, I'd suggest to > ask those questions there and work on answers on that site. It's really > effective at making information like this available. We can tag the > questi

Re: [openstack-dev] Step by step OpenStack Icehouse Installation Guide

On 08/03/2014 03:49 AM, chayma ghribi wrote: > I want to share with you our OpenStack Icehouse Installation Guide for > Ubuntu 14.04. [...] Thanks for the effort. Would you please consider working with the existing Documentation team to add/improve current manuals? Also, please use this list only

Re: [openstack-dev] [neutron] [not-only-neutron] How to Contribute upstream in OpenStack Neutron

On 07/28/2014 01:51 AM, Thierry Carrez wrote: > This is a great set of questions. When we have answers, we should > consolidate them into a "contributors expectations" wiki page (in the > same vein as the ML Etiquette one[1] or the Reviewers expectations one[2]) Given the amount of google juice th

Re: [openstack-dev] Mentor program?

On 07/23/2014 11:02 AM, Anne Gentle wrote: > I'll let Stefano answer further, but yes, we've discussed a centralized > mentoring program for a year or so. I'm not sure we have enough mentors > available, there are certainly plenty of people seeking and needing > mentoring. So he can elaborate more

Re: [openstack-dev] [neutron] [not-only-neutron] How to Contribute upstream in OpenStack Neutron

On Fri 25 Jul 2014 01:25:16 AM PDT, Luke Gorrie wrote: > I have one idea for low-hanging fruit to put new contributors more at > ease: to explain a little about both when and why the "Merge" button > is finally pressed on a change. Indeed, communication is key. I'm not sure how you envision to im

[openstack-dev] [nova][neutron] Splitting Content of Blueprint

moving the thread to the more appropriate openstack-dev mailing list, since this conversation is about the 'future'. Get familiar with the topics of the mailing lists: https://wiki.openstack.org/wiki/MailingLists#Future_Development On Fri 25 Jul 2014 06:29:52 AM PDT, Andreas Scheuring wrote: > Hi

[openstack-dev] [Off Topic] Women Who Code, San Francisco, looking for mentors

In the lead up to the next round of the GNOME Outreach Program for Women (application deadline 10/22/2014), the group is hosting a series of meetups around getting involved in free and open source software development. Given OpenStack's committment to Outreach Program for Women, we're looking for

Re: [openstack-dev] [Neutron] Specs approved for Juno-3 and exceptions

On 07/23/2014 06:22 AM, Kyle Mestery wrote: > Thanks for sending this out Salvatore. We are way oversubscribed, > and at this point, I'm in agreement on not letting any new > exceptions which do not fall under the above guidelines. Given how > much is already packed in there, this makes the most se

[openstack-dev] Resources to fix MS Outlook (was Re: [Nova] [Gantt] Scheduler split status (updated))

On 07/15/2014 09:02 AM, Dugger, Donald D wrote: > Unfortunately, much as I agree with your sentiment (Death to MS > Outlook) my IT overlords have pretty much forced me into using it. It's been a while since I had to deal with really awful software but since the is a common problem, shall we coll

Re: [openstack-dev] [Sahara] Master-instance: Service hadoop-* not running

On Mon 14 Jul 2014 09:14:38 AM PDT, Dat Tran wrote: > I install openstack icehouse, then install sahara. I create cluster, > it worked! > But [...] This is the wrong list to report problems while using openstack. use openstack-dev only to discuss the future of OpenStack, even if you area a devel

Re: [openstack-dev] [OpenStack-Dev] Commit messages and lawyer speak

On 07/07/2014 11:30 PM, Monty Taylor wrote: > Also, CLA's are pointless. Let's be clear: this is your personal opinion, not that of the OpenStack project nor of the OpenStack Foundation. >From OpenStack project's perspective, CLAs are not pointless, they're mandated by bylaws and by years of prac

[openstack-dev] Emails sent to publicly archived mailing lists are *NOT* confidential Re: [third-party-ci][neutron] What is "Success" exactly?

> The contents of this message and any attachments to it are > confidential and may be legally privileged. If you have received this > message in error you should delete it from your system immediately > and advise the sender. > > To any recipient of this message within HP, unless otherwise stated

Re: [openstack-dev] [neutron] Specs repo

On 07/03/2014 03:34 PM, Sumit Naiksatam wrote: > Is this still the right repo for this: > https://github.com/openstack/neutron-specs No. The right repo is: http://git.openstack.org/cgit/openstack/neutron-specs/ github is used only as copy for convenience and things may break there. /stef -- A

Re: [openstack-dev] [Octavia] PTL and core team members

On 06/22/2014 11:38 AM, Brandon Logan wrote: > I'm thinking we are going to need more than 2 on the core team at first > but it is hard to tell exactly how many people will be contributing code > at first. I know we've got a lot of interested parties and the > possibility that some 10+ people are

[openstack-dev] [metrics] Re: [nova][all] Tracking bug and patch statuses

Looks like something we can add to Activity reports, if you think it's useful. At the moment there are fairly simple charts for bugs but querying the database to find stale bugs and their reviews shouldn't be too hard. If I understand correctly, you're querying LP to get the bugs in status: ('New

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] 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] [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?

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] [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] [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

[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] 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

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] [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

[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] 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

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,

[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] [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

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.

[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] 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

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] [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/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/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] [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] 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] [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] 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] [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] 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] [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] [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] 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] 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

[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] 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] 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] [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] [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

[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

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

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] 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

[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] 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

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] 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] [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

[openstack-dev] OFF TOPIC Re: IP Spoofing Security Issue in Gateway VM

On Mon 18 Nov 2013 04:06:34 PM PST, Aradhana Adhikari wrote: > Hi Neutron/VPNaaS Team, > > I am trying to configure VPN with latest Havana releaseand I have > some concerns regarding gateway VM set-up. While configuring a VPN [...] This discussion is OFF TOPIC on this list. This list for the de

Re: [openstack-dev] Using AD for keystone authentication only

On Mon 18 Nov 2013 11:41:41 AM PST, Avi L wrote: > Our AD server does not allow anonymous browse so I am sure that when [...] This discussion is OFF TOPIC on this list. This list for the developers of OpenStack to discuss development issues and roadmap. It is focused on the next release of Open

Re: [openstack-dev] Split of the openstack-dev list (summary so far)

On 11/15/2013 02:06 AM, Thierry Carrez wrote: > Arguments in favor of splitting openstack-dev / stackforge-dev > * People can easily filter out all non-openstack discussions > * Traffic would drop by about 25% I'm not so convinced about this figure, as others pointed out. > * Removes confusion as

[openstack-dev] filtering traffic on the mailing list (was Re: Split of the openstack-dev list)

On 11/14/2013 11:52 AM, Joe Gordon wrote: > This may be a silly question, but what is the best way to filter out > stackforge and related projects? Should I make a local filter and > whitelist all integrated projects? Not a silly question at all, quite the opposite. One way to filter traffic is to

Re: [openstack-dev] Split of the openstack-dev list

On 11/14/2013 11:46 AM, Clint Byrum wrote: > Now, choose which city will grow faster and produce more innovation. This is not about welcoming newcomers. It's about teaching newcomers the tools, habits, culture of an established community that keeps growing. If questions about usage need to be ask

Re: [openstack-dev] Split of the openstack-dev list

On 11/14/2013 09:03 AM, David Ripton wrote: > I don't think it's worth the bother. openstack-dev would still receive > most of the traffic. Once you add back the traffic from people > cross-posting, posting to the wrong list, yelling at people > cross-posting or posting to the wrong list, etc. I'

Re: [openstack-dev] Proposal to recognize indirect contributions to our code base

On 11/13/2013 04:34 PM, Colin McNamara wrote: > Not to be contrarian, but 92% of the commits in Havana came from > non-individual contributions. The majority of those came from big name > companies (IBM, RedHat, etc). ow, that's harsh. Despite what US Supreme Court Judges may think, Companies are

Re: [openstack-dev] Proposal to recognize indirect contributions to our code base

On 11/12/2013 01:58 AM, Thierry Carrez wrote: > This proposal raises several questions. > > (1) Is it a good idea to allow giving credit to patch sponsors > > On one hand, this encourages customers of OpenStack service companies to > fund sending back bugfixes and features upstream. Does it? I'm

Re: [openstack-dev] [summit] Youtube stream from Design Summit?

On Fri 01 Nov 2013 12:40:44 PM PDT, Jaromir Coufal wrote: > Since I have quite good experience with using these hangouts on air, I > wanted to propose it as a general way how to get our sessions more > accessible. Lot of people are asking how they can get more involved > and I received very positiv

Re: [openstack-dev] [summit] Youtube stream from Design Summit?

On 11/01/2013 05:33 AM, Jaromir Coufal wrote: > I was wondering, since there is a lot of people who cannot attend Design > Sessions, if we can help them to be present at least in some way. We tried in the past to setup systems to enable remote participation in a generic way (give a URL per each se

Re: [openstack-dev] Re : welcoming new committers

On 10/31/2013 03:45 PM, Romain Hardouin wrote: > Adding a message for new comers is a good idea. > I am a new Horizon contributor, some of my fixes have been merged > (thanks to Upstream University :-) Indeed :) Can you share with us briefly what you found interesting in the sessions of Upstream U

[openstack-dev] welcoming new committers (was Re: When is it okay for submitters to say 'I don't want to add tests' ?)

On 10/31/2013 07:05 AM, Kyle Mestery (kmestery) wrote: [...] > If we want to grow the committer base and help people to become > better reviewers, taking the time to show them the ropes is part of > the game. hijacking the thread using Kyle's comment as an excuse. It's not an 'if' but a 'since':

Re: [openstack-dev] [Solum] Solum transitioned to openstack-dev

On 10/30/2013 03:44 PM, Adrian Otto wrote: > So, that's working. My concern is that the topic is listed as > "OpenStack Solum" and should be listed as "Solum" because this > project is not incubated, and should not use the OpenStack brand. Indeed, it was a copy-paste mistake on my side. Fixed now

Re: [openstack-dev] [Solum] Solum transitioned to openstack-dev

On 10/30/2013 12:08 PM, Adrian Otto wrote: > The Solum team has agreed[1] to use openstack-dev, and has closed its > project-specific mailing list. Welcome. There is now also a topic on the Dev list: people can subscribe to receive only messages tagged [Solum] or [solum] in the subject. Cheers,

Re: [openstack-dev] [Nova] Blueprint review process

On Wed 30 Oct 2013 03:29:32 AM PDT, Thierry Carrez wrote: > (1) Rating blueprints "low priority" doesn't mean they won't make it. It > means we have no idea if they will make it. Maybe the proposer doesn't > have a proven track record of hitting promised deadlines, maybe we don't > have core review

Re: [openstack-dev] [Nova] Blueprint review process

On 10/28/2013 10:28 AM, Russell Bryant wrote: > 2) Setting clearer expectations. Since we have so many blueprints for > Nova, I feel it's very important to accurately set expectations for how > the priority of different projects compare. In the last cycle, > priorities were mainly subjectively se

[openstack-dev] Looking for an MC for Ligthing Talks in Hong Kong

Hello folks as it's now an established tradition of OpenStack Summits, we'll have 30 minutes every day in Hong Kong for people to present their projects in 5 minutes or less. The projects can be about anything, really, from building furniture to 3D printing to cloudy stuff. People that want to ta

Re: [openstack-dev] [Nova] Blueprint review process

On 10/23/2013 08:33 AM, Russell Bryant wrote: > At the last Nova meeting we started talking about some updates to the > Nova blueprint process for the Icehouse cycle. I had hoped we could > talk about and finalize this in a Nova design summit session on "Nova > Project Structure and Process" [1],

Re: [openstack-dev] Announcing Project Solum

On 10/23/2013 12:03 PM, Adrian Otto wrote: > Along with eBay, RedHat, Ubuntu/Canonical, dotCloud/Docker, Cloudsoft, > and Cumulogic, we at Rackspace are happy to announce we have started > project Solum as an OpenStack Related open source project. Solum is a > community-driven initiative currently

Re: [openstack-dev] Error while executing 'git review'

On 10/22/2013 06:04 AM, S Sridhar wrote: > But getting following error while posting for review. > > sridhar@ubuntu:~/repo/neutron$ git review > remote: Resolving deltas: 100% (4/4) > remote: Processing changes: refs: 1, done > To ssh://saggezz...@review.openstack.org:29418/openstack/neutron.g

Re: [openstack-dev] Call for a clear COPYRIGHT-HOLDERS file in all OpenStack projects (and [trove] python-troveclient_0.1.4-1_amd64.changes REJECTED)

On 10/20/2013 06:00 AM, Jeremy Stanley wrote: > I know the Foundation's got work underway to improve the affiliate > map from the member database, so it might be possible to have some > sort of automated job which proposes changes to a copyright holders > list in each project by running a query wit

Re: [openstack-dev] [Metrics] Improving the data about contributor/affiliation/time

On 10/18/2013 05:33 AM, Sean Dague wrote: > I'm not sure it is well understoond that all members have to join the > foundation. We don't make that a requirement on someone slinging a > patch. I believe we do make it a requirement: you can't sign the CLA if you are not also a member of the Foundat

[openstack-dev] [Metrics] Improving the data about contributor/affiliation/time

hello folks first of all: congratulations to all developers, testers, users, translators, tech writers for the new release: Havana is out of the gate with impressive numbers. Speaking of numbers, a lot of you have noticed mistakes in the reported numbers, from misspelling of names to missing/wron

Re: [openstack-dev] [Metrics] Working on affiliations details: Activity Board

Thank you Daniel. On 10/15/2013 11:07 AM, Daniel Izquierdo wrote: > ps: not sure if it's a good idea to resend this to the general list > without the topic [metrics] nah, I don't think it's needed. > http://activity.openstack.org/dash/browser/data/affs/openstack-community-affs.csv This is usefu

[openstack-dev] Join the online meeting for moderators of Ask OpenStack

We are holding an online meeting for all the people that use Ask OpenStack. On Thursday Sept. 5 from 6PM to 7PM Pacific Time on IRC freenode.net #openstack-community The main intention is to share best practices and in the long term improve the objective of Ask OpenStack: to provide the bes

Re: [openstack-dev] [savanna] use openstack-dev mailing list

Hi Sergey On 07/24/2013 01:49 AM, Sergey Lukjanov wrote: > We decided to use openstack-dev@lists.openstack.org mailing list > instead of savanna-...@lists.launchpad.net for all savanna-related > communication. I have created a mailman topic for Savanna too, so people interested only in receiving

Re: [openstack-dev] [Murano] The mailing list address is changed

I have created a mailman topic for Murano too, so people interested only in receiving messages with "[Murano]" in the subject line can subscribe to the topic only. How to use Mailman topics: http://www.gnu.org/software/mailman/mailman-member/node31.html http://lists.openstack.org/cgi-bin/mailma

Re: [openstack-dev] [Stackalytics] 0.1 release [metrics]

On 07/23/2013 07:25 AM, Roman Prykhodchenko wrote: > I still think counting lines of code is evil because it might encourage > some developers to write longer code just for statistics. Data becomes evil when you decide to use them for evil purposes :) I don't think that lines of code is a bad metr

[openstack-dev] Discussing Amazon API compatibility [Nova][Swift]

Hello I have seen lots of discussions on blogs and twitter heating up around Amazon API compatibility and OpenStack. This seems like a recurring topic, often raised by pundits and recently joined by members of the community. I think it's time to bring the discussions inside our community to our es

<    1   2   3   >