On Wed, Aug 6, 2014 at 5:30 AM, Thierry Carrez
wrote:
> Hi everyone,
>
> At the TC meeting yesterday we discussed Rally program request and
> incubation request. We quickly dismissed the incubation request, as
> Rally appears to be able to live happily on top of OpenStack and would
> benefit from
Hi all,
I want to get more eyes on a design change being proposed for the API
Reference Listing page, http://developer.openstack.org/api-ref.html.
To see the new output, look at this screenshot:
http://aa4698cc2bf4ab7e5907-ed3df21bb39de4e57eec9a20aa0b8711.r41.cf2.rackcdn.com/Screen%20Shot%202014-0
On Tue, Aug 12, 2014 at 9:56 AM, Mark McLoughlin wrote:
> Hey
>
> (Terrible name for a policy, I know)
>
> From the version_cap saga here:
>
> https://review.openstack.org/110754
>
> I think we need a better understanding of how to approach situations
> like this.
>
> Here's my attempt at docum
__In review and merged this past week__
We're cleaning up the Architecture Design Guide continually and I got my
proof copy yesterday. The green cover is lovely as part of the set. The
interior PDF is made the master branch from today and you can get those
print copies rolling!
The landing page i
On Thu, Aug 14, 2014 at 10:13 AM, Sandy Walsh
wrote:
> On 8/14/2014 11:28 AM, Russell Bryant wrote:
> > On 08/14/2014 10:04 AM, CARVER, PAUL wrote:
> >> Daniel P. Berrange [mailto:berra...@redhat.com] wrote:
> >>
> >>> Depending on the usage needs, I think Google hangouts is a quite useful
> >>>
On Fri, Aug 15, 2014 at 2:47 PM, Adam Young wrote:
> We are putting a lot of effort into the Specs process. It seems like a
> pity to let them go to waste after the features they describe are
> implemented. Ideally, they should be part of the official documentation.
> Many are too detailed to b
ople reading release notes are not the audience for
specs. Please point to deployer docs or user docs.
>
> On Fri, Aug 15, 2014 at 2:58 PM, Anne Gentle wrote:
>
>>
>>
>>
>> On Fri, Aug 15, 2014 at 2:47 PM, Adam Young wrote:
>>
>>> We are putting a lo
On Wed, Aug 13, 2014 at 3:29 PM, Doug Hellmann
wrote:
>
> On Aug 13, 2014, at 4:08 PM, Matthew Treinish
> wrote:
>
> > On Wed, Aug 13, 2014 at 03:43:21PM -0400, Eoghan Glynn wrote:
> >>
> >>
> > Divert all cross project efforts from the following projects so we
> can
> > focus
> > ou
On Fri, Aug 15, 2014 at 3:01 PM, Joe Gordon wrote:
>
>
>
> On Thu, Aug 14, 2014 at 4:02 PM, Eoghan Glynn wrote:
>
>>
>> > > Additional cross-project resources can be ponied up by the large
>> > > contributor companies, and existing cross-project resources are not
>> > > necessarily divertable on
On Thu, Aug 21, 2014 at 2:11 AM, Sharath V wrote:
> Dear Friends, Have an doubt, please clarify me .!! When i start
> understanding openstack , There are three nodes a) controller node
> b)Compute node c) Network node
> i) as my understanding controller node contains all the components like
> n
On Fri, Aug 22, 2014 at 6:17 PM, Rochelle.RochelleGrober <
rochelle.gro...@huawei.com> wrote:
> /flame-on
> Ok, this is funny to some of us in the community. The general populace of
> this community is so against the idea of management that they will use the
> term for a despotic dictator as a po
I'm following this as well since I have the exact same problem in a
docstring patch for heat.
On Sun, Aug 24, 2014 at 9:30 AM, Mike Spreitzer wrote:
> The differences do not look to me like ones that would follow from a
> difference in hash seed.
>
> Clint Byrum wrote on 08/24/2014 05:00:21 AM
On Mon, Aug 25, 2014 at 8:36 AM, Sean Dague wrote:
> On 08/20/2014 12:37 PM, Zane Bitter wrote:
> > On 11/08/14 05:24, Thierry Carrez wrote:
> >> So the idea that being (and remaining) in the integrated release should
> >> also be judged on technical merit is a slightly different effort. It's
> >
_Operators midcycle meetup report _
I went to the Operators midcycle meetup this week. Nice work Gauvain on the
automation of the New, Changed, and Deprecated configuration options -- at
the Operators Midcycle Meetup yesterday they asked for it and lo and
behold, it was already there! Nice.
The di
On Wed, Aug 27, 2014 at 7:51 AM, Thierry Carrez
wrote:
> Hi everyone,
>
> I've been thinking about what changes we can bring to the Design Summit
> format to make it more productive. I've heard the feedback from the
> mid-cycle meetups and would like to apply some of those ideas for Paris,
> with
Look on https://wiki.openstack.org/wiki/Meetings for a link to an iCal feed
of all OpenStack meetings.
https://www.google.com/calendar/ical/bj05mroquq28jhud58esggq...@group.calendar.google.com/public/basic.ics
On Mon, Sep 1, 2014 at 8:26 PM, Kevin Benton wrote:
> Is it possible to put an iC
On Thu, Sep 4, 2014 at 12:39 PM, Tim Bell wrote:
> > -Original Message-
> > From: Thierry Carrez [mailto:thie...@openstack.org]
> > Sent: 04 September 2014 16:59
> > To: openstack-dev@lists.openstack.org
> > Subject: Re: [openstack-dev] [Zaqar] Comments on the concerns arose
> during
> >
Hi Ben,
Since manila just entered incubation, the openstack-manuals repo and common
documentation will not include it until it is integrated. During incubation
we ask you to start documentation in your own repo and identify what will
eventually move into common docs. See
https://wiki.openstack.org/
On Wed, Sep 3, 2014 at 2:07 PM, Kekane, Abhishek <
abhishek.kek...@nttdata.com> wrote:
> Hi Erno,
>
> I agree that we must document what all config parameters will be reloaded
> after SIGHUP signal is processed, that's the reason why we have added
> DocImpact tag to patch https://review.openstac
On Fri, Sep 5, 2014 at 5:27 AM, Steven Hardy wrote:
> On Fri, Sep 05, 2014 at 03:56:34PM +1000, Angus Salkeld wrote:
> >On Fri, Sep 5, 2014 at 3:29 PM, Gauvain Pocentek
> > wrote:
> >
> > Hi,
> >
> > A bit of background: I'm working on the publication of the HOT
> resources
> >
On Mon, Sep 8, 2014 at 9:04 AM, Jay Pipes wrote:
> On 09/08/2014 03:46 AM, Dmitry Mescheryakov wrote:
>
>> Hello Fuelers,
>>
>> On the previous meeting a topic was raised on how Fuel doc team should
>> work with bugs, see [1] for details. We agreed to move the discussion
>> into the mailing list.
tl;dr I'm concerned we're conflating user concerns and contributor
concerns. I'd like to see laser focus on two things that help both: 1)
Define layers in our governance and integration efforts 2) Pay down
technical debt with a focus on supporting users.
Great kick off Joe, thanks. I have been wa
Bug squash day worked well on 9/9 -- squashing and triaging bugs, bringing
the openstack-manuals backlog to about 400, with 50 in progress even now!
The openstack-api-site backlog went to about 200 with 15 in progress. We
also had some fairly new docs contributors join in -- thank you everyone
who
On Mon, Sep 15, 2014 at 11:31 AM, Zane Bitter wrote:
> On 14/09/14 11:09, Clint Byrum wrote:
>
>> Excerpts from Gauvain Pocentek's message of 2014-09-04 22:29:05 -0700:
>>
>>> Hi,
>>>
>>> A bit of background: I'm working on the publication of the HOT
>>> resources reference on docs.openstack.org.
We're less than a month from our October 16th release and I'm appreciating
the focus on the install guide. Thanks Matt Kassawara and our intrepid
reviewers!
Tomorrow we should have a release 2.1.3 of the clouddocs-maven-plugin. This
is the version we'll "freeze" upon for the upcoming Juno release.
ss-project and cross-program
> issues. To address that, the plan is to carve cross-project space into
> the next design summit, even if that means a little less topical
> sessions for everyone else.
>
> Thoughts ?
>
> --
> Thierry Carrez (ttx)
>
> ___
1. In review and merged this past week:
Wow, I see about 30 fixes backported to the Havana install guides in the
last week, great work Andreas! I appreciate the focus on the install guides
since the Summit, thank you.
2. High priority doc work:
I'm very excited to have Lana offer to do a proposal
k-dev mailing list
>> OpenStack-dev@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.opensta
On Thu, Nov 21, 2013 at 1:53 AM, Michael Still wrote:
> On Thu, Nov 21, 2013 at 7:54 AM, Anne Gentle wrote:
>
> > 5. Doc tools updates:
> >
> > David Cramer tells me he'll cut one more release of the clouddocs-tools
> > maven plugin then it'll be p
us, but at the moment, when you create a
> heat stack, you specify the tenant ID three times, once in the path, once
> in the request body, and again in the context. I'm wondering why, and if
> we can kill the first two?
>
> Clearly this is different for keystone, where the top level of request
> granularity is Domain not Project, but for all other services, every
> request is scoped to a Project is it not?
>
> Steve
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Anne Gentle
annegen...@justwriteclick.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
eriences.
Thanks,
Anne
> Does that make sense ?
>
> --
> Thierry Carrez (ttx)
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Anne Gentle
annegen...@justwriteclick.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi all,
Now that you've got a decent start, how about checking it in as a
doc/source/ document in the nova repository? Seems better than keeping it
in the wiki so that you can update with code changes.
Anne
On Wed, Nov 13, 2013 at 11:11 PM, Alex Xu wrote:
> On 2013年11月14日 07:09, Christopher Ye
On Mon, Dec 2, 2013 at 9:19 AM, Jarret Raim wrote:
> All,
>
> Barbican is the OpenStack key management service and we’d like to
> request incubation for the Icehouse release. A Rackspace sponsored team has
> been working for about 9 months now, including following the Havana release
> cycle for
Thanks to new doc patchers Shilla Saebi and Thomas Herve for their clean up
work, especially for the Identity API docs and Heat install!
Be ready for 12/20/13 Doc Bug Day! Looking forward to it.
1. In review and merged this past week:
The Install Guide is still the most worked-on document. I'd l
On Wed, Dec 11, 2013 at 5:31 PM, Anne Gentle wrote:
> Thanks to new doc patchers Shilla Saebi and Thomas Herve for their clean
> up work, especially for the Identity API docs and Heat install!
>
> Be ready for 12/20/13 Doc Bug Day! Looking forward to it.
>
> 1. In review an
ailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Anne Gentle
annegen...@justwriteclick.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
er clicking the stop button, that's an example of an extension.
> >>>>>>
> >>>>>> In OpenStack, we use extensions to extend core. Core are the
> >>>>>> essential feature(s) of the project. In Cinder for example, core is
> >>>>>
tack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Anne Gentle
annegen...@justwriteclick.com
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On Wed, Jan 8, 2014 at 8:26 AM, Noorul Islam Kamal Malmiyoda <
noo...@noorul.com> wrote:
>
> On Jan 8, 2014 6:11 PM, "Sean Dague" wrote:
> >
> > On 01/07/2014 11:27 PM, Noorul Islam Kamal Malmiyoda wrote:
> > > On Wed, Jan 8, 2014 at 9:43 AM, Georgy Okrokvertskhov
> > > wrote:
> > >> Should we r
Happy new year everyone. We're hitting the books with a vengeance in 2014.
See my 2013 roundup at
http://www.openstack.org/blog/2014/01/openstack-documentation-wrap-up-for-2013/
.
1. In review and merged this past week:
I'm pleased to announce a refresh on the API Reference listing page thanks
to
It's a known identified deficiency, and all we have is this:
http://docs.openstack.org/developer/nova/api/nova.cert.manager.html
Doc bug reopened at
https://bugs.launchpad.net/openstack-manuals/+bug/1160757
Hopefully someone on the list can identify more information sources so we
can document.
A
This week we have two chances to talk docs -- the IRC meeting for US and
Europe is every other Wednesday in #openstack-meeting-alt at 03:00 UTC.
We're also hosting a hangout on air on Wednesday, January 29, 2014 at
20:00:00 UTC. Look for a Hangouts On Air invitation on Google Plus.
1. In review a
Sorry, must send a correction: Wednesday at 14:00:00 UTC is the time for
the Wednesday Doc Team meeting on IRC in #openstack-meeting-alt this week.
(Not 03:00). Thanks Matt and Summer for asking!
Anne
On Mon, Jan 27, 2014 at 9:35 AM, Anne Gentle wrote:
> This week we have two chances to t
Hi all,
The Google Summer of Code program has been around since 2005, and as an org
OpenStack has applied a few of the past years without getting accepted due
to needing more detail in the projects and dedicated mentors.
I'd like to see if we as a project want to try again this year to put in
proj
Hi can you point out where you're seeing documentation for the first
without tenant_id?
At http://api.openstack.org/api-ref-compute-ext.html#ext-os-quota-sets only
the tenant_id is documented.
This is documented identically at
http://docs.openstack.org/api/openstack-compute/2/content/ext-os-quota
Thanks, it's confirmed and the doc team can work on it. Appreciate you
asking!
Anne
On Wed, Jan 29, 2014 at 9:44 AM, Yingjun Li wrote:
> I reported a bug here:
> https://bugs.launchpad.net/openstack-manuals/+bug/1274153
>
> On Jan 29, 2014, at 23:33, Anne Gentle wrote:
>
On Wed, Jan 29, 2014 at 2:42 PM, Jarret Raim wrote:
>
> All,
>
> Barbican, the key management service for OpenStack, requested incubation
> before the holidays. After the initial review, there were several issues
> brought up by various individuals that needed to be resolved
> pre-incubation. At t
On Thu, Jan 23, 2014 at 5:21 AM, Steven Hardy wrote:
> Hi all,
>
> I've recently been working on migrating the heat internal interfaces to use
> the keystone v3 API exclusively[1].
>
> This work has mostly been going well, but I've hit a couple of issues which
> I wanted to discuss, so we agree t
On Mon, Feb 3, 2014 at 8:33 PM, Collins, Sean <
sean_colli...@cable.comcast.com> wrote:
> Hi,
>
> Some Neutron developers have some really great slides from some of the
> summits,
> and I'd like to link them in the documentation I am building as part of a
> developer doc blueprint,
> with proper
ebruary 04, 2014 5:17 PM
To: Anne Gentle
Cc: openstack-d...@lists.openstack.org; openstack-dev@lists.openstack.org
Subject: Re: [Openstack-docs] Conventions on naming
- Original Message -
> From: "Anne Gentle"
> To: openstack-d...@lists.openstack.org
> Sent: Tuesday
(not for usage questions)"
> >>
> >> Cc: "Jonathan Bryce"
> >> Sent: Wednesday, February 5, 2014 9:17:39 AM
> >> Subject: Re: [openstack-dev] [Openstack-docs] Conventions on naming
> >>
> >> On 02/05/2014 01:09 PM, Mark McLoughl
Grab that Thursday 2:00 Central while it's still available each week!
gogogogo
There's also 1:00 Central Mondays when each meeting room is open.
Give a holla with a time you decide on and I'll update the ical.
Anne
On Fri, Feb 7, 2014 at 6:59 PM, Jesse Noller wrote:
>
> On Feb 7, 2014, at 5:5
Hi Sean,
Yes, please do improve docstrings for the client object! And I think you
found that Lorin Hochstein recently added a Python SDK chapter to the end
user guide at http://docs.openstack.org/user-guide/content/ch_sdk.html.
As for the CLI project itself, the docs team has taken all the command
On Thu, Feb 13, 2014 at 7:53 AM, Sean Dague wrote:
> On 02/13/2014 05:37 AM, Thierry Carrez wrote:
> > Sandy Walsh wrote:
> >> The informal OpenStack motto is "automate everything", so perhaps we
> should consider some form of gamification [1] to help us? Can we offer
> badges, quests and challen
On Sun, Feb 23, 2014 at 1:23 PM, Steve Baker wrote:
> On 22/02/14 06:42, Mike Spreitzer wrote:
>
> Zane Bitter wrote on 02/21/2014
> 12:23:05 PM:
>
> > Yeah, we are overloading the term 'developer' here, since that section
> > contains both information that is only useful to developers working
On Sun, Feb 23, 2014 at 2:14 PM, Steve Baker wrote:
> On 24/02/14 08:44, Anne Gentle wrote:
>
>
>
>
> On Sun, Feb 23, 2014 at 1:23 PM, Steve Baker wrote:
>
>> On 22/02/14 06:42, Mike Spreitzer wrote:
>>
>> Zane Bitter wrote on
>> 02/21/2014 12:2
Hi all,
Thanks the OpenStack Foundation for funding a spot for an intern with the
GNOME Outreach Program for Women for May-August 2014. I've updated the
OpenStack wiki page and would like to recruit mentors for this round. If
you're interested in mentoring an intern and have a good idea for a 3-mon
Hi all,
Just kicked off announcing another round for the Outreach Program for
Women, exciting! I also wanted to give a round up from the world of docs so
here goes.
1. In review and merged this past week:
We've had a good number of reviews going through as well as changes to doc
tools to improve
On Mon, Mar 3, 2014 at 8:20 AM, Joe Gordon wrote:
> On Mon, Mar 3, 2014 at 4:42 AM, Sylvain Bauza
> wrote:
> > Hi Joe,
> >
> > Thanks for your reply, I'll try to further explain.
> >
> >
> > Le 03/03/2014 05:33, Joe Gordon a écrit :
> >
> >> On Sun, Mar 2, 2014 at 11:32 AM, Dina Belova
> wrote:
On Mon, Mar 3, 2014 at 11:04 AM, Joe Gordon wrote:
> On Mon, Mar 3, 2014 at 6:27 AM, Anne Gentle wrote:
> >
> >
> > On Mon, Mar 3, 2014 at 8:20 AM, Joe Gordon
> wrote:
> >>
> >> On Mon, Mar 3, 2014 at 4:42 AM, Sylvain Bauza
> >> wrote:
>
On Tue, Mar 4, 2014 at 11:10 AM, Russell Bryant wrote:
> On 03/03/2014 12:32 PM, Russell Bryant wrote:
> > There has been quite a bit of discussion about the future of the v3 API
> > recently.
>
> :-)
>
> Since this proposal was posted, it is clear that there is not much
> support for it, much
On Wed, Nov 19, 2014 at 1:34 PM, Everett Toews
wrote:
> On Nov 19, 2014, at 4:56 AM, Christopher Yeoh wrote:
>
> > Hi,
> >
> > We have moved to alternating times each week for the API WG meeting so
> > people from other timezones can attend. Since this is an odd week
> > the meeting will be Thur
Get ready for bug triage day coming sooner than we all think, as in, soon
for those in Australia!
https://wiki.openstack.org/wiki/Documentation/BugTriageDay for all the
details. Looking forward to working with our Cross-Project Liaisons (CPLs)
for docs, put your name on
https://wiki.openstack.org/w
Hi all,
Yesterday we held an all-day doc bug triage day, triaging bugs in both
openstack-manuals and openstack-api-site on Launchpad. And some even walked
around in related projects with a docs tag. Stretching our legs.
Here are some positive results:
27 triaged for openstack-api-site (3 have som
Hi Gary and Anita,
We do have a bug tracker for www.openstack.org at:
https://bugs.launchpad.net/openstack-org
Log a bug there to make sure the web devs at the Foundation get it.
Thanks,
Anne
On Sun, Nov 30, 2014 at 8:44 AM, Gary Kotton wrote:
> Hi,
> When I log into the site I am unable to n
On Tue, Dec 2, 2014 at 2:59 PM, Alan Pevec wrote:
> > Will the bugs created by this end up in the openstack-manuals project
> (which I don't think is the right place for them in this case) or has it
> been set up to create them somewhere else (or not at all) when the commits
> are against the sta
On Tue, Dec 2, 2014 at 3:44 PM, Steve Gordon wrote:
> - Original Message -
> > From: "Anne Gentle"
> > To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> >
> > On Tue, Dec
On Tue, Dec 2, 2014 at 5:10 PM, Alan Pevec wrote:
> >> In this case we're referring to how we handle DocImpact for specific
> >> branches of a project (say stable/juno of Nova, for example). I don't
> think
> >> we'd want to change the DocImpact handling for the entire project to go
> >> somewher
t;
>> >> The hypervisor drivers are documented on the wiki, sometimes they're
>> >> in-tree, sometimes they're not, but the state of testing is documented
>> on
>> >> the wiki. I think we could take this approach for network and st
On Mon, Dec 8, 2014 at 1:06 PM, Adam Young wrote:
> Isn't this what the API repos are for? Should EG the Keystone schemes be
> served from
>
> https://github.com/openstack/identity-api/
>
>
>
The -api repos will go away once we have the merges completed for
replacing with the -specs repo info.
On Tue, Dec 16, 2014 at 4:05 AM, Neil Jerram
wrote:
>
> Stefano Maffulli writes:
>
> > 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-t
I don't gush much, but when I do, it's end-of-year reflection gushing. We
have some of the most interesting docs in the world.
I'm proud of what we've accomplished as a community, as reviewers, as
coaches, as tool makers, and as writers.
To encourage and motivate nearly 200 separate contributors
On Sun, Dec 28, 2014 at 7:26 PM, liuxinguo wrote:
> We have opened a bug for document of huawei storage driver, and have
> posted the document at https://review.openstack.org/#/c/143926/.
>
> Now I have two things not very clear:
>
> 1. When will be this document merged into Kilo? At the end of
On Tue, Jan 6, 2015 at 10:03 AM, Steven Kaufer wrote:
> This is a follow up thread to [1]
>
> In order to have consistency across clients, I am proposing that the
> client side sorting has the following syntax: --sort [:]
>
> Where the --sort parameter is comma-separated and is used to specify on
On Tue, Jan 6, 2015 at 8:05 PM, Everett Toews
wrote:
> On Jan 6, 2015, at 12:46 PM, Kevin L. Mitchell <
> kevin.mitch...@rackspace.com> wrote:
>
> > On Tue, 2015-01-06 at 12:19 -0600, Anne Gentle wrote:
> >> I'm all for consistency. Sounds like a great cas
Welcome to 2015, all. Here's the latest in the docs world.
Web design for landing page is nearly done. Needs testing, so please take a
look at the output [0] in your favorite browser and let us know any issues
on the review patch itself. [1]
Web design plan [2] is to convert the End User Guide ne
Hi Stef, thanks for writing this up. One aspect this proposal doesn't
address is the ungoverned content for projects that are either in
stackforge, pre-stackforge, incubating, or have no intention of any
governance but want to use the openstack wiki. What can we do if one of
those groups raises the
Oh hi list!
Feel free to discuss the "a project just getting started" content that ends
up on the wiki -- where would that go?
Anne
On Thu, Jan 8, 2015 at 9:51 PM, Anne Gentle wrote:
> Hi Stef, thanks for writing this up. One aspect this proposal doesn't
> address is t
On Mon, Jan 12, 2015 at 1:20 PM, Chris Dent wrote:
>
> After some discussion with Sean Dague and a few others it became
> clear that it would be a good idea to introduce a new tool I've been
> working on to the list to get a sense of its usefulness generally,
> work towards getting it into global
The best guidance we have is here:
https://wiki.openstack.org/wiki/Documentation/Copyright
On Sat, Jan 17, 2015 at 2:27 AM, ZhiQiang Fan wrote:
> Hi, developers
>
> I have observed that some source code files in our projects have been
> announced as "Copyright xxx, All rights reserved", and the
t;
>
> ______
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-
nStack development environment
-- Considerations for using DevStack
-- Considerations for using system packages
-- Understanding the architecture and components
-- Building the documentation
-- Running unit tests
-- When to use fakes
-- Internal API references
-- REST API references
-- Debugging locally
-- Debugging within continuous int
d.structural_subscriber=&field.tag=&field.tags_combinator=ANY&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.
On Fri, Apr 25, 2014 at 11:01 AM, Jay Pipes wrote:
> On Fri, 2014-04-25 at 13:41 +, Akihiro Motoki wrote:
> > Hi,
> >
> > I have a same question from Mark. Why is "flavor" not desired?
> > My first vote is "flavor" first, and then "type".
>
> Some reasons:
>
> First, flavor, in English, can a
Hi all,
I've pushed the doc track to:
http://junodesignsummit.sched.org/overview/type/documentation#.U15Y4uZdU0w
The two cross-project tracks related to docs are on Tuesday:
Tues 12:05 Cross-project documentation
Tues Lunch: Let's talk docs
Tues 2:00 Easier documentation for all project developer
unity
further.
Thanks,
Anne
> Thank you,
>
> Shaunak
>
> On Apr 21, 2014, at 11:40 AM, Anne Gentle
> wrote:
>
> > Great questions, Shaunak. Yep I've been thinking about this for a while
> but not sure I have complete conclusions. More below.
> >
> &
You could log a bug against openstack-manuals and tag it with doc-builds.
That's where we track other doc tooling bugs.
It would be great to get that renamed, since it's a wadlrestapi converter.
On Sat, May 3, 2014 at 5:48 PM, Jeremy Stanley wrote:
> As of TODAY's pip 1.5.5 release, which vend
On Sat, May 3, 2014 at 7:44 PM, Jeremy Stanley wrote:
> On 2014-05-03 18:41:05 -0500 (-0500), Anne Gentle wrote:
> > You could log a bug against openstack-manuals and tag it with
> > doc-builds. That's where we track other doc tooling bugs.
>
> Thanks Anne! https://
On Tue, May 6, 2014 at 7:02 AM, Thierry Carrez wrote:
> Dean Troyer wrote:
> > I want to open the discussion of an OpenStack Client Tools program
> > proposal to a wider audience. It would initially consist of
> > OpenStackClient and eventually add the existing SDK projects as they are
> > ready
Hi all,
Anne here - your friendly documentarian!
As the docs PTL, it’s my job to gather input about and make doc tool and
process decisions. This note is the first step: Your responses to this note
give me input to share at the Summit where, hopefully, we will form a
consensus about process and
On Wed, May 7, 2014 at 1:43 PM, Roger Luethi wrote:
> On Wed, 07 May 2014 09:16:48 -0700, Anne Gentle wrote:
> > Why not? The responses to my recent survey about doc contributions
> indicate
> > that the top barriers to docs’ contributions are:
> >
> > - Tools:
om
> >
> > Le 2014-05-15 17:34, Gauvain Pocentek a écrit :
> >> Hello,
> >>
> >> This mail probably mainly concerns the doc team, but I guess that the
> >> heat team wants to know what's going on.
> >>
> >> We've shortly discusse
On Fri, May 16, 2014 at 9:47 PM, CARVER, PAUL wrote:
>
> When looking at a change in Gerrit that includes an rst file, is there
> any easy way to view the rendered view rather than merely the markup view?
> The side by side diff is great, but I'd really like a clickable link to the
> rendered vi
A great question came out of a docs session today and I wanted to post this
hint/tip here, and also ask a question.
Gerrit has documentation that describes how to use regular expressions to
search for specific reviews. See
https://review.openstack.org/Documentation/user-search.html
One that I've
On Tue, May 20, 2014 at 6:42 PM, Steve Baker wrote:
> On 21/05/14 02:31, Doug Hellmann wrote:
>
> On Fri, May 16, 2014 at 2:10 PM, Gauvain
> Pocentek
> wrote:
>
> Le 2014-05-16 17:13, Anne Gentle a écrit :
>
>
> On Thu, May 15, 2014 at 10:34 AM, Gauvain
>
On Fri, May 23, 2014 at 6:19 AM, Steven Hardy wrote:
> On Fri, May 23, 2014 at 12:38:40PM +0200, Andreas Jaeger wrote:
> > On 05/23/2014 12:13 PM, Steven Hardy wrote:
> > > [...]
> > > I'll hold my hand up as one developer who tried to contribute but ran
> away
> > > screaming due to all the XML-
On Fri, May 23, 2014 at 7:47 AM, Kyle Mestery wrote:
> On Fri, May 23, 2014 at 5:27 AM, James E. Blair
> wrote:
> > Hi,
> >
> > With apologies to the specs repos we just created, the more I think
> > about this, the more I think that the right answer is that we should
> > stick with codenames for
On Fri, May 23, 2014 at 8:42 AM, Steven Hardy wrote:
> On Fri, May 23, 2014 at 08:09:06AM -0500, Anne Gentle wrote:
> > On Fri, May 23, 2014 at 6:19 AM, Steven Hardy wrote:
> >
> > > On Fri, May 23, 2014 at 12:38:40PM +0200, Andreas Jaeger wrote:
> > > >
Here's the latest news in docland. Thanks for all the great input at the
Summit and excellent follow up conversations on the mailing lists.
1. In review and merged recently:
Conversion of the High Availability Guide to DocBook to ease maintenance.
It's so interesting that the conversation about th
Hi all,
I'm back and mellow after my week at the beach. Here's what's going on in
the world of docs.
We had our doc team meeting this morning. The 2nd and 4th Wed. are Europe
and North America times, the 1st and 3rd Wed. are for Australia and Pacific
area time zones. Find the meeting logs here:
ht
1 - 100 of 407 matches
Mail list logo
