Hello folks,
On 11/15/2016 02:43 AM, matt Jarvis wrote:
> I'd like to propose that, in line with the new process for creation of
> working groups, we set up some initial IRC meetings for all interested
> parties.
I'll be glad to read summaries and participate to conversations on the
mailing
On 02/05/2016 07:17 PM, Doug Hellmann wrote:
> So, is Poppy "open core"?
I think it's a simple answer: no, Poppy is not open core.
Poppy is not open core... Is Linux Open Core because you have to buy a
processor and ram to run it?
Or is Firefox open core because I have to buy service from a
On 01/19/2016 02:28 PM, Mike Perez wrote:
> Do you mean the Dev Digest? It was originally in the newsletter, and then
> people at the summit approached me about making it more visible, so it's now
> a separate thing and emailed to the dev and operators list weekly.
>
>
On 01/12/2016 06:13 AM, Amrith Kumar wrote:
[...]
> I did not exhaustively verify this but
[...]
A fair question to ask then is, why are you proposing these patches?
> I created a quick poll to tally results
oh no, not another survey! :) Sometimes I feel that survey-itis[1] is a
consequence of
On 12/01/2015 06:38 PM, Spencer Krum wrote:
> There is a thread beginning here:
> http://lists.openstack.org/pipermail/openstack-dev/2015-October/076962.html
> which covers what to expect from the new software.
Nice! This is awesome: the new review panel lets you edit files on the
web interface.
On 08/03/2015 09:22 AM, Ju Lim wrote:
Any chance that the Ops meetup will have some ability for folks to
teleconference in?
Given that the conference will be at a hotel, experience tells me that
we'll be lucky if there is enough bandwidth for all participants. OTOH,
Tom has surprised us before,
On 07/29/2015 09:27 AM, Maish Saidel-Keesing wrote:
Some of my thoughts on the Voting process.
Excellent conversation starter, Maish. One piece that attracted my
attention on your post is:
Community and How to Contribute. Way down there in at the bottom.
Is that because people already
On 07/15/2015 11:25 AM, Joshua Harlow wrote:
So I've been following the TC work on tags, and have been slightly
confused by the whole work, so I am wondering if I can get a
'explainlikeimfive' (borrowing from reddit terminology) edition of it.
I'll try :)
You need to think of tags as the
Five things every contributor should know about the OpenStack docs
project
http://superuser.openstack.org/articles/five-things-every-contributor-should-know-about-the-openstack-docs-project
New docs contributors may be afraid of moving too fast and breaking
things - but don’t
Containers and OpenStack: here's what you need to know
http://superuser.openstack.org/articles/containers-and-openstack-here-s-what-you-need-to-know
Interview with Adrian Otto, a principal architect at Rackspace, is the
project technical lead (PTL) for Magnum, an API service
On 06/02/2015 07:54 AM, Jay Pipes wrote:
Please, no. We should not have ops tags that are different than other
tags for no good reason.
Let me put it another way:
I think there is a good reason for Operators to look for information
about a project that is more descriptive than the current
OpenStack users share how their deployments stack up
http://superuser.openstack.org/articles/openstack-users-share-how-their-deployments-stack-up
Some of OpenStack’s founding projects -- including Nova, Keystone,
Glance, Horizon and Cinder -- continue to be the most popular. That
First of all a reminder to everybody doing code reviews:
Avoid sarcasm and jokes
Those travel poorly across TCP/IP and don't translate well in different
languages. Just don't use them.
If you get a negative vote or comments you don't like/understand ask for
more explanations. Offer a place and
On 05/13/2015 11:48 AM, Mike Perez wrote:
The Cinder team has met today [1] to begin discussions on the deadline
for new volume drivers in the Liberty release.
The proposed deadline for volume drivers to be merged by is June 19th 2015
[...]
Great to read this, thanks Mike.
On a wider note,
Thanks Joe for bringing this up. I have always tried to find topics
worth being covered in the weekly newsletter. I assemble that newsletter
thinking of developers and operators as the main targets, I'd like both
audiences to have one place to look at weekly and skim rapidly to see if
they missed
Kilo Logo
Superuser Awards final faceoff: your vote counts
Four great finalists, but only one can win: it’s a close call as the
voting deadline approaches for this edition of the Superuser Awards.
Snapshot of the OpenStack community behind Kilo
The OpenStack community that helped create the
On Thu, 2015-04-30 at 12:26 +0200, Flavio Percoco wrote:
I've seen the number of threads to discuss Ops topics increase in
openstack-dev and the influence of Ops - even just points of views
inherited from the feedback we've got - on reviews has gotten better
as well.
Fantastic, that has
On Wed, 2015-04-29 at 12:59 +0300, Maish Saidel-Keesing wrote:
Again my apologies for the incorrect format - since I am still not
receiving the messages from this thread.
let me know if you want me to investigate this further.
Doug - evidently this is not working as it should. As Chris said
On Wed, 2015-04-29 at 18:28 +0300, Maish Saidel-Keesing wrote:
How about the fact that the definition of an ATC was changed [1] for a
free Summit pass? [2]
This was not a decision of the TC, it was a decision of the Foundation
staff. The definition of ATC has *not* changed, that's embedded in
On Mon, 2015-04-27 at 17:00 -0400, Doug Hellmann wrote:
I would have to go back and check, but I'm pretty sure the posts were
highlighted in Stef's community newsletter email.
They were, in fact. But I know as a fact that even if people many love
the newsletter, I have the impression that few
On Tue, 2015-04-28 at 16:30 +0100, Chris Dent wrote:
What's important to avoid is the blog postings being only reporting of
conclusions. They also need to be invitations to participate in the
discussions. Yes, the mailing list, gerrit and meeting logs have some
of the ongoing discussions but
Why you should attend an OpenStack Summit
OpenStack Summits don’t miss a beat - with a schedule full of diverse
breakout sessions, captivating speakers, off-the-wall evening events and
the occasional surprise, it’s the twice-yearly event you simply cannot
miss. What would you add to the list of 10
On Fri, 2015-04-24 at 15:02 +, Amrith Kumar wrote:
I would support changes to both reviewstats and stackalytics to do the
following.
1. recognizes and gives credit to '0' comments
2. identifies recheck, reverify and similar directives to the CI
system and flag them appropriately,
On Thu, 2015-04-23 at 15:00 +0200, Salvo Rapisarda wrote:
I have a problem with auth google n ask.openstack.org
When I try to login the page redirect to
https://support.google.com/accounts/answer/6206245?p=openidrd=1
Hi Salvo
I apologize for the issue. We've had a couple of delays while
OpenStack DefCore Community Review – TWO Sessions April 21 (agenda)
During the DefCore process, we’ve had regular community check points to
review and discuss the latest materials from the committee. With the
latest work on the official process and flurry of Guidelines, we’ve got
a lot of concrete
Making your list and checking it twice for the OpenStack Vancouver
Summit
Emily Hugenbruch shared her pre-summit checklists: great tips there.
OVN and OpenStack Integration Development Update
The Open vSwitch project announced the OVN effort back in January and
Russell Bryant started to look
Making your list and checking it twice for the OpenStack Vancouver
Summit
Emily Hugenbruch shared her pre-summit checklists: great tips there.
OVN and OpenStack Integration Development Update
The Open vSwitch project announced the OVN effort back in January and
Russell Bryant started to look
[REMINDER]
the service Ask OpenStack on https://ask.openstack.org will be down for
maintenance on Monday, April 6 from 9am PDT for around 3-4 hours.
The downtime is needed to move the service on new infrastructure,
powered by OpenStack and puppet script. Once we move to the new server
we'll have
Game changer: inside Adobe’s new Marketing Cloud architecture
The Adobe Marketing Cloud powers software-as-a-service marketing for
outfits such as the Los Angeles Kings, eBags and Verizon Wireless. When
the IT infrastructure team in Adobe’s Digital Marketing group realized
it was time for an
Game changer: inside Adobe’s new Marketing Cloud architecture
The Adobe Marketing Cloud powers software-as-a-service marketing for
outfits such as the Los Angeles Kings, eBags and Verizon Wireless. When
the IT infrastructure team in Adobe’s Digital Marketing group realized
it was time for an
Hello folks
the service Ask OpenStack on https://ask.openstack.org will be down for
maintenance on Monday, April 6 from 9am PDT for around 3-4 hours.
The downtime is needed to move the service on new infrastructure,
powered by OpenStack and puppet script. Once we move to the new server
we'll
On Sat, 2015-03-28 at 19:58 +0530, Ganesh R wrote:
I am a newbie to OpenStack, very interested in contributing to
OpenStack development.
Welcome.
Jeremy provided some useful suggestions. Just last week I added to how
to contribute page the links to mentors page:
Folks,
If you have received your discount code to OpenStack summit Vancouver,
stop whatever you're doing and
register *now*
Admission prices go up to $900 tomorrow and you'll have to pay the
difference. *There will be absolutely no exceptions*.
If you're in doubt if you
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
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
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
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
1 - 100 of 315 matches
Mail list logo
