OpenStack DefCore Process Draft Posted for Review [major milestone]
OpenStack DefCore Committee is looking for community feedback about the
proposed DefCore Process. March has been a month for OpenStack DefCore
milestones. At the March Board meeting, the first official DefCore
Guideline (called
On Tue, 2015-03-24 at 19:01 +, Rochelle Grober wrote:
So, how do we get timely first core review of patches in areas of the
world where Core presence in IRC is slim to none?
I think that most core reviewers use bouncers, so notifying them in the
channel would probably raise a notification
On Mon, 2015-03-23 at 11:43 -0700, Mike Perez wrote:
We've been talking about CI's for a year. We started talking about CI
deadlines
in August. If you post a driver for Kilo, it was communicated that you're
required to have a CI by the end of Kilo [1][2][3][4][5][6][7][8]. This
should've
On Mon, 2015-03-23 at 16:23 -0400, Anita Kuno wrote:
Some folks just will not respect other people's time. To pretend
otherwise is a huge dis-service to folks trying their hardest to
support those worthy of the support.
This may be true in general but I have yet to be convinced that this is
Feature freeze + Kilo-3 development milestone available
We just hit Feature Freeze, so please do not approve changes that add
features or new configuration options unless those have been granted a
feature freeze exception. This is also String Freeze, so you should
avoid changing translatable
Five years in: Charting the OpenStack galaxy
The Starship Enterprise had a five year mission, to explore strange new
worlds, among other things, and as we approach the five year mark in
our own mission, it's fun to think about the worlds we've seen and
contemplate where to go next. Did anyone
hello folks,
We would like to provide a greater degree of freedom to individuals who
contribute on behalf of corporations who signed the Corporate CLA. By
allowing corporate managers to maintain list of their authorized
contributors we may be able to remove the need for every individual to
sign
On Tue, 2015-03-10 at 15:23 -0700, James E. Blair wrote:
The holy grail of this system would be the suitable for production
deployment tag, but no one has figured out how to define it yet.
Are crazy ideas welcome in this phase?
I start with 2 below:
Preface: an idea circulates about visually
On Wed, 2015-03-11 at 17:59 -0500, Ed Leafe wrote:
The longer we try to be both sides of this process, the longer we will
continue to have these back-and-forths about stability vs. innovation.
If I understand correctly your model, it works only for users/operators
who decide to rely on a vendor
Hi David,
On Sat, 2015-03-07 at 02:22 +, Chen, Wei D wrote:
I thought the feature should be approved as long as the SPEC[1] is
merged, but it seems I am wrong from the beginning[2], both of
them (SPEC merged and BP approval[4][5]) is necessary and mandatory
for getting some effective
OpenStack User Groups get a new home
It’s easy to stay in touch with OpenStack birds-of-a-feather wherever
you are, from India to Italy, with the new OpenStack User Groups portal.
Even with events all over the globe, it's super simple to stay current —
join a group, and you’ll be notified of new
On Tue, 2015-03-03 at 17:42 +0200, Eduard Matei wrote:
Is there a way to specify the Juno version to be installed using
devstack.
Let's please reserve this list for discussions about the *future* of
OpenStack development, not questions about using its tools.
Please, everybody, help us stay
On Tue, 2015-03-03 at 17:10 +0200, Duncan Thomas wrote:
I feel the need to abandon changes that seem abandoned
I think there is an agreement that there should be a way to have a clean
view of changesets that are being actively worked on, changes where the
owner is responding to comments, working
On Mon, 2015-03-02 at 13:35 -0800, Clay Gerrard wrote:
I think Tom's suggested help us help you is a great pre-abandon
warning. In swift as often as not the last message ended with
something like you can catch me on freenode in #openstack-swift if
you have any questions
Good, this thread
On Mon, 2015-03-02 at 12:00 -0700, Doug Wiegley wrote:
Why do you feel the need to keep them? Do your regularly look at
older patches? Do you know anyone that does?
I don't think that's the point. The point is to try improving
contributor's life by providing them one last useful comment
On Thu, 2015-02-26 at 16:44 -0800, James E. Blair wrote:
It is good to recognize the impact of this, however, I would suggest
that if having open changes that are not actively being worked is a
problem for statistics,
I don't think it's a problem for the statistics per se. The reports are
only
I'm not expressing myself cleary enough. I don't advocate for the
removal of anything because I like pretty charts. I'm changing the
subject to be even more clear.
On Fri, 2015-02-27 at 13:26 -0800, James E. Blair wrote:
I am asking you to please independently remove changes that you don't
On Thu, 2015-02-26 at 15:58 -0600, Kevin L. Mitchell wrote:
One thing that comes to mind is that there are a lot of reviews that
appear to have been abandoned; I just cleared several from the
novaclient review queue (or commented on them to see if they were still
alive). I also know of a few
On Thu, 2015-02-26 at 14:18 -0600, Anne Gentle wrote:
Do the features listed in the Release Notes each have appropriate
documentation? So far we just link to the specifications for nova, for
example. [1] So to me, it could be a focus on the specification
acceptance means less time/energy for
On Wed, 2015-02-25 at 21:15 +, Ian Cordasco wrote:
I read it the same was as Doug. I don’t think Jeremy was trying to
imply your reviews would move through more quickly if you reviewed
other people’s work. Just that, as with most open source projects,
there’s always at least 2 distinct
On Wed, 2015-02-25 at 14:54 -0500, Doug Hellmann wrote:
1. Should we have a unified developer guide for the project?
Yes. Absolutely. Yes.
2. Where should it live and how should we manage it?
I think the natural destination for it would be the URL
http://docs.openstack.org/developer (which
OpenStack Technical Committee Update: Project Reform Progress
Over the last few months, the Technical Committee has been discussing
plans to dissolve the binary concept of the integrated release and adapt
our projects structure to the future needs of collaborative development
in the OpenStack
Hello folks
we have a bunch of upcoming initiatives to help out new contributors to
OpenStack and we need mentors willing to help newcomers go from zero to
(at least) one merged patch.
OpenStack has always been a welcoming community despite being complex to
navigate for new contributors. If you
Changing the subject since Flavio's call for openness was broader than
just private IRC channels.
On Tue, 2015-02-17 at 10:37 +, Daniel P. Berrange wrote:
If cases of bad community behaviour, such as use of passwd protected
IRC channels, are always primarily dealt with via further private
On Mon, 2015-02-16 at 09:44 +, Daniel P. Berrange wrote:
Why did we change the rules on summit passes in this way ?
Because there is always a balance to strike between open participation
and effective conversations, while the balance point keeps changing.
In Paris we've noticed a fairly
On Sat, 2015-02-14 at 21:11 -0500, Nick Chase wrote:
Does anybody know if a) ATC emails have started to go out yet, and b)
when proposal voting will start?
Voting started:
http://www.openstack.org/vote-vancouver
Hurry, voting closes at 5pm CT on Monday, February 23.
Continue to visit
On Sun, 2015-02-15 at 14:34 +, Jeremy Stanley wrote:
Also a reminder, you need to be the owner of a change in Gerrit
which merged on or after October 16, 2014 (or have an unexpired
entry in the extra-atcs file within the governance repo) to be in
the list of people who automatically get
OpenStack crowns “Liberty” its next release name
OpenStack’s next release will be called Liberty. While you might be
thinking of the word liberty in terms of “freedom” (as in free beer or
other things), the name comes from a village in the Canadian province of
Saskatchewan.
Introducing PoshStack,
On Thu, 2015-02-12 at 16:01 +, Amrith Kumar wrote:
How is a private IRC channel any different from a culture of private
discussions? Having a chat over lunch, in the hallway, on the
telephone, etc.,
I will articulate again why I think that a group of leaders of OpenStack
*should not*
On Thu, 2015-02-12 at 10:37 +0100, Thierry Carrez wrote:
Right. You can't prevent occasional private discussions and pings, and
you shouldn't. It's when you encourage and officialize them (by for
example creating a channel for them) that things start to go bad.
Yes, that's very bad. Private
On Thu, 2015-02-12 at 10:35 +, Kuvaja, Erno wrote:
I'm not attacking against having summits, I think the face to face
time is incredibly valuable for all kind of things. My point was to
bring up general flaw of the flow between all inclusive decision
making vs. decided in summit session.
On Wed, 2015-02-11 at 09:32 -0500, Sean Dague wrote:
Definitely true, to each his/her own. I still consider it unfortunate.
I've also heard core developers state that they stopped reading the
mailing list months ago. Which I also find unfortunate.
That's terrible: do you know why they don't
On Wed, 2015-02-11 at 10:55 +0100, Flavio Percoco wrote:
This email is dedicated to the openness of our community/project.
It's good to have a reminder every now and then. Thank you Flavio for
caring enough to notice bad patterns and for raising a flag.
## Keep discussions open
I don't
On Tue, 2015-02-10 at 15:20 +, Kevin Bringard (kevinbri) wrote:
I've been talking with a few people about this very thing lately, and
I think much of it is caused by what appears to be our actively
discouraging people from working on it. Most notably, ATC is only
being given to folks
On Mon, 2015-02-09 at 13:32 +0400, Anton Zemlyanov wrote:
2) There is no such a thing as OpenStack ID. Should we use Launchpad?
Facebook login? Twitter?
Actually, there is: https://openstackid.org :) It supports OpenID and
OAuth, the code is on
OpenStack L naming poll
We'd like your help again in selecting the right name for the
development cycle and release coming after Kilo. Our next summit will
happen in Vancouver, BC (Canada) in May. L candidate names were
proposed, selected and checked for various issues... leaving 4
candidates on
** Project changed: openstack-community = horizon
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1417314
Title:
IE9 cuts out some CSS rules
Status in OpenStack
On Fri, 2015-01-30 at 23:05 +, Everett Toews wrote:
To converge the OpenStack APIs to a consistent and pragmatic RESTful
design by creating guidelines that the projects should follow. The
intent is not to create backwards incompatible changes in existing
APIs, but to have new APIs and
February 9th is the deadline to submit a talk for the May 2015 Vancouver
Summit
Would you like to speak at the May 2015 OpenStack Summit in Vancouver?
Then hurry up and submit a talk! February 9 is the final day that
speaking submissions will be accepted.
February 9th is the deadline to submit a talk for the May 2015 Vancouver
Summit
Would you like to speak at the May 2015 OpenStack Summit in Vancouver?
Then hurry up and submit a talk! February 9 is the final day that
speaking submissions will be accepted.
On Wed, 2015-01-28 at 09:27 -0600, John Griffith wrote:
You are exactly correct Thierry, being a track chair a few times in
the process has been something like:
* PIck a cut off based on votes
* Review remaining submissions as a panel
I followed a different process when I've been
On Thu, 2015-01-29 at 16:01 -0800, Michael Still wrote:
However, we got here because no one is maintaining the code in Nova
for the EC2 API. This is despite repeated calls over the last 18
months (at least).
I'd love to get to the root cause before we jump to look for solutions.
The story we
The Whys and Hows of the Oslo Namespace Change
During the Kilo cycle the Oslo team has been busy deprecating the oslo.
namespace in all of our projects. The first question this probably
raises for most people is: why? Ben Nemec has the answer in his blog
post and also explains how the Common
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 holder
2015 Election Results
Thank you to everyone who voted in this year's election. We reached
quorum and passed the three bylaws amendments. We also reached quorum in
electing eight Individual Directors to the 2015 OpenStack Board of
Directors.
And the winner is
Individual Directors
* Tim
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
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
On Tue, 2015-01-13 at 18:28 +, Csaba Henk wrote:
What we are puzzled on is the license. This is something we have to
figure out before we think of setting up the project. In general it's
understood that Apache License (v2) is preferred. Question:
is that a strict requirement on Stackforge
[one important paragraph was left out. I apologize for the double post.]
First App Tutorial for OpenStack
OpenStack needs something like the tutorial Writing your first Django
app. We're looking for volunteers to flesh out ideas on what this
tutorial would look like for OpenStack and how it would
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
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 wiki
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
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
Last newsletter of 2014, see you again in 2015!
University of Hawaii College of Education harnesses OpenStack to support
faculty research via a secure private cloud
OpenStack powers a Holodeck at University of Hawaii at Manoa... Read the
full story on Mirantis blog.
The TOSCA
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 which
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 the
** No longer affects: openstack-community
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1402632
Title:
issue with glance python client in Icehouse
To manage notifications about this bug go to:
** No longer affects: openstack-community
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1402632
Title:
issue with glance python client in Icehouse
Status in OpenStack Image Registry
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.
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
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
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
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 OpenStack
On 12/04/2014 01:59 AM, Andreas Jaeger wrote:
If there's now wait to do this, we should just add a short redirect text
and then make the page immutable so that nobody starts editing again.
I don't think this is the best approach. At some point, the pages on docs.o.o
will be changed and will be
On 12/02/2014 12:56 AM, Venu Murthy wrote:
Great Initiative Mark,
In the beginning of my openstack journey, being able to ssh/connect to
the VMs/Instances was the greatest challenge. After having spent several
months to debug such issues, I've posted one of the solutions here.
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
I have a non-functioning machine basically... my productivity is
impaired by this issue. Any workaround?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1315510
Title:
EDS
I have a non-functioning machine basically... my productivity is
impaired by this issue. Any workaround?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1315510
Title:
EDS (Evolution) contacts
On 11/14/2014 09:11 PM, Jeremy Stanley wrote:
Categories emerge automatically as you tag pages into them. No
separate category creation step is required.
True although incomplete. Categories are just pages, like almost
anything in mediawiki, so if you add text [[Category: New_Category]] in
a
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
On 11/14/2014 02:50 PM, Thierry Carrez wrote:
In this precise example, I feel like the dynamic page is much less
usable than the static page, due to the deep hierarchy.
Got it. The current taxonomy is trying to map precisely the hierarchy of
Program-Projects-Teams therefore it keeps the Nova
On 11/06/2014 01:27 PM, Andreas Jaeger wrote:
Stefano, Loic, infra-team,
Just noticed that there's upstream training content that overlaps with
the infra-manual:
http://git.openstack.org/cgit/openstack/training-guides/tree/doc/upstream-training
http://docs.openstack.org/infra/manual/
I
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
Hi Jean-Daniel,
it seems (from the little investigation I've done) that you've provided
two different email addresses for your profile on
http://openstack.org/profile/ (I see one at geekarea there) and on
gerrit (your ovh one). Use the same as primary email address and you
should be able to
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
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? A
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
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
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
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:
OpenStack Juno is here! http://www.openstack.org/software/juno/
OpenStack Juno, the tenth release of the open source software for
building public, private, and hybrid clouds has 342 new features to
support software development, big data analysis and application
infrastructure at scale. The
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
Network Function Virtualization -- The Opportunity for OpenStack
and Open Source
http://blogs.gnome.org/markmc/2014/10/02/network-function-virtualization-the-opportunity-for-openstack-and-open-source/
This week's launch of OPNFV
On 09/30/2014 08:03 AM, Kuo Hugo wrote:
Could you please post the log of related requests in Swift's log ???
please, don't cross-post and don't use the Development list for usage
questions. OpenStack-Dev is for the developers of OpenStack to discuss
development issues and roadmap.
It is
Hi Saloni
On 09/30/2014 09:12 AM, Saloni Baweja wrote:
I am an aspirant for OPW and did find projects like Wikimedia,
Evergreen interesting and have bit more inclination towards OpenStack.
But I have no idea about cloud storage, their working etc and am just
a beginner. It would be great if I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 09/29/2014 08:11 AM, Lars Kellogg-Stedman wrote:
I am wondering what sort of tools we have at our disposal to help
combat this problem. Based on what I've seen recently, we could
reduce the nature of this problem by:
Flagging the post and
mostly gathered comments from
people between San Francisco and Silicon Valley and I’d like to expand
the research. Fill in this brief survey
https://docs.google.com/forms/d/15vX9pGlvBVftq4YlD6vE0rOMKq9e3U25Qh_9gJ6Ky_4/viewform
or contact Stefano Maffulli directly via email (replying to this message
mostly gathered comments from
people between San Francisco and Silicon Valley and I’d like to expand
the research. Fill in this brief survey
https://docs.google.com/forms/d/15vX9pGlvBVftq4YlD6vE0rOMKq9e3U25Qh_9gJ6Ky_4/viewform
or contact Stefano Maffulli directly via email (replying to this message
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 that
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
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
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 spend
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 of a
** Project changed: openstack-community = nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1368259
Title:
unable to delete volume after attach with mount point fails
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
c.
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 team
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
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 patch
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 go the
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
101 - 200 of 760 matches
Mail list logo
