Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/12/15 02:53, Anne Gentle wrote:
> On Fri, Dec 11, 2015 at 10:27 AM, Andreas Jaeger <aj at suse.com> wrote:
> 
>> On 12/11/2015 05:04 PM, Anne Gentle wrote:
>>
>>>
>>>
>>> On Fri, Dec 11, 2015 at 12:13 AM, Andreas Jaeger <aj at suse.com
>>> <mailto:aj at suse.com>> wrote:
>>>
>>>     On 12/10/2015 10:16 PM, Lana Brindley wrote:
>>>
>>>         -----BEGIN PGP SIGNED MESSAGE-----
>>>         Hash: SHA256
>>>
>>>         I think that will require a bug, if someone wants to take that on.
>>>
>>>
>>>     A bug to implement a cross-project spec?
>>>
>>>     I don't think that's necessary,
>>>
>>>
>>> We'll need some way to scope what it means for docs. Perhaps the spec
>>> itself could serve for tracking and scope purposes. I don't know another
>>> way to assign and track the docs tasks other than bugs or blueprints.
>>>
>>>
>> Perhaps my understanding of cross-project specs is wrong. Should we -1 the
>> cross project spec and ask to add sections for documentation?
>>
>> Or is it expected that for cross-project specs each projects tracks them
>> on their own?
> 
> 
> I'm reviewing the spec now and will request they add the doc details as
> needed.
> 
> Yes, docs needs can be in the cross-project spec. We also need a docs
> liaison to the cross project group who tracks theses and inserts docs needs
> when appropriate. [1] And it's nearly always appropriate. Did we already
> identify someone?
> 

No, we haven't. Any volunteers?

L

- -- 
Lana Brindley
Technical Writer
Rackspace Cloud Builders Australia
http://lanabrindley.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCAAGBQJWbf7ZAAoJELppzVb4+KUy5n4H/jvqLpHlD+jycnKkPdVdS9/c
ArkjkLRLVnHBMUBkXaP4GAFzqwIdY56DPm2YFTn3gQFkmp0rDpX+sbZeZ/RQldLl
gsSQiyzDH3lFUwsMdegNFnll9r1U97aj2rNpz2D7Nr7HrI8HRl70+Ws1iugx+yd1
TbBeXqOKdi20vYevau1nPrrSqhDodytHE4U5O/u4NZHVSr5iHOY2sL3oV8bE/TeO
rq6gLGiAokojpch1dhxXrzQtZGgz3olo6+7ioW3ASkrFDK6te6C+H39u3oNzJdwr
4eo+Vi3LUSG0ZrOsF2v7GWYPJSjuj77fm5nwjO3/FexTt07RKGZd0vS2xeZ7cnA=
=y5ww
-----END PGP SIGNATURE-----