On 2018-08-27 11:06:42 -0400 (-0400), Doug Hellmann wrote:
[...]
> I do not see the flag that says the CLA is required in the configuration
> for the repository:
>
> http://git.openstack.org/cgit/openstack-infra/project-config/tree/gerrit/acls/openstack/operations-guide.config
You can also tell b
Excerpts from Kunzmann, Gerald's message of 2018-08-27 12:37:28 +:
> Hi everyone,
>
> I think this is a great step to pull together all Ops related discussions
> into
> one common repo and SIG.
>
> I noticed that there was a proposal in the Vancouver discussion [1] to create
> the repo wit
: Jonathan Proulx
Cc: OpenStack Operators
Subject: Re: [Openstack-operators] Ops Community Documentation - first anchor
point
On Tue, Aug 21, 2018 at 03:14:48PM -0400, Jonathan Proulx wrote:
> Hi All...
>
> I'm still a little confused by the state of this :)
>
> I know
On Tue, Aug 21, 2018 at 02:27:44PM -0500, Sean McGinnis wrote:
:On Tue, Aug 21, 2018 at 03:14:48PM -0400, Jonathan Proulx wrote:
:Hey Jon,
:
:Pretty much everything is in place now. There is one outstanding patch to
:officially add things under the SIG governance here:
:
:https://review.openstack.o
Excerpts from Jonathan Proulx's message of 2018-08-21 15:14:48 -0400:
> Hi All...
>
> I'm still a little confused by the state of this :)
>
> I know I made some promises then got distracted the looks like Sean
> stepped up and got things a bit further, but where is it now? Do we
> have an active
On Tue, Aug 21, 2018 at 03:14:48PM -0400, Jonathan Proulx wrote:
> Hi All...
>
> I'm still a little confused by the state of this :)
>
> I know I made some promises then got distracted the looks like Sean
> stepped up and got things a bit further, but where is it now? Do we
> have an active repo
Hi All...
I'm still a little confused by the state of this :)
I know I made some promises then got distracted the looks like Sean
stepped up and got things a bit further, but where is it now? Do we
have an active repo?
It would be nice to have the repo in place before OPs meetup.
-Jon
On Tue,
> > Plan
> >
> > So to recap above, I would propose the following actions be taken:
> >
> > 1. Create sig-operators as a group to manage operator efforts at least
> > related
> >to what needs to be done in repos.
> > 2. Create an openstack/operations-guide repo to be the new home of the
Sean put together some really great things here and I do think the SiG
might be the way to go as far as ownership for the repos and the plan looks
pretty complete. I've offered to do the Git and Gerrit Lunch and Learn at
the OPS mmetup if needed to help get folks set up and going.
Amy (spotz)
On
On Tue, 26 Jun 2018 12:36:52 -0500
Sean McGinnis wrote:
> >
> > Plan
> >
> > So to recap above, I would propose the following actions be taken:
> >
> > 1. Create sig-operators as a group to manage operator efforts at least
> > related
> >to what needs to be done in repos.
> > 2. Creat
>
> Plan
>
> So to recap above, I would propose the following actions be taken:
>
> 1. Create sig-operators as a group to manage operator efforts at least related
>to what needs to be done in repos.
> 2. Create an openstack/operations-guide repo to be the new home of the
>operations
This sounds great. As I understand it Sean can set up a skeleton for us to
work on ops docs (and maybe other things later) with a minimum of
initiation energy. Count me in.
Chris
On Tue, Jun 26, 2018 at 12:42 PM Sean McGinnis
wrote:
> Reviving this thread with a fresh start. See below for the o
Reviving this thread with a fresh start. See below for the original.
To recap, the ops community is willing to take over some of the operator
documentation that is no longer available due to the loss of documentation team
resources. From discussions, there needs to be some official governance over
Excerpts from Petr Kovar's message of 2018-05-28 16:03:41 +0200:
> On Thu, 24 May 2018 07:19:29 -0700
> "Jonathan D. Proulx" wrote:
>
> > My intention based on current understandign would be to create a git
> > repo called "osops-docs" as this fits current naming an thin initial
> > document we i
On Thu, 24 May 2018 07:19:29 -0700
"Jonathan D. Proulx" wrote:
> My intention based on current understandign would be to create a git
> repo called "osops-docs" as this fits current naming an thin initial
> document we intend to put there and the others we may adopt from
> docs-team.
So, just to
On May 25, 2018 5:30:40 AM PDT, Doug Hellmann wrote:
>Excerpts from Jonathan D. Proulx's message of 2018-05-24 07:19:29
>-0700:
>>
>> My intention based on current understandign would be to create a git
>> repo called "osops-docs" as this fits current naming an thin initial
>> document we inten
Excerpts from Jonathan D. Proulx's message of 2018-05-24 07:19:29 -0700:
>
> My intention based on current understandign would be to create a git
> repo called "osops-docs" as this fits current naming an thin initial
> document we intend to put there and the others we may adopt from
> docs-team.
On Thu, May 24, 2018 at 01:26:07PM -0700, Melvin Hillsman wrote:
: I think a great model we have in general as a community is if people
: show up to do the work, it is not something crazy, get out of their
: way; at least that is how I think of it. I apologize if there is any
: perception o
I think a great model we have in general as a community is if people show
up to do the work, it is not something crazy, get out of their way; at
least that is how I think of it. I apologize if there is any perception
opposed to my previous statement by me bringing up the other repos. I tried
to be
On Thu, May 24, 2018 at 07:07:10AM -0700, Doug Hellmann wrote:
:I know you wanted to avoid lots of governance overhead, so I want
:to just mention that establishing a SIG is meant to be a painless
:and light-weight way to declare that a group of interested people
:exists so that others can find th
My intention based on current understandign would be to create a git
repo called "osops-docs" as this fits current naming an thin initial
document we intend to put there and the others we may adopt from
docs-team.
My understanding being they don't to have this type of
documentention due to much r
Excerpts from Doug Hellmann's message of 2018-05-23 22:58:40 -0700:
> Excerpts from Melvin Hillsman's message of 2018-05-23 22:26:02 -0700:
> > Great to see this moving. I have some questions/concerns based on your
> > statement Doug about docs.openstack.org publishing and do not want to
> > detour
Sure definitely, that's why I said I was not trying to detour the
conversation, but rather asking for feedback. Definitely agree things
should continue to plow forward and Chris has been doing an excellent job
here and I think it is awesome that he is continuing to push this.
On Wed, May 23, 2018
Excerpts from Melvin Hillsman's message of 2018-05-23 22:26:02 -0700:
> Great to see this moving. I have some questions/concerns based on your
> statement Doug about docs.openstack.org publishing and do not want to
> detour the conversation but ask for feedback. Currently there are a number
I'm ju
Also, apologies, if consolidation or reorganizing all these is reasonable,
what do you think that would look like; i.e.
osops
> tools
>> contrib
>> generic
>> monitoring
>> logging
> docs
> example-configs
On Wed, May 23, 2018 at 10:26 PM, Melvin Hillsman
wrote:
> Great to see this moving. I h
Great to see this moving. I have some questions/concerns based on your
statement Doug about docs.openstack.org publishing and do not want to
detour the conversation but ask for feedback. Currently there are a number
of repositories under osops-
https://github.com/openstack-infra/project-config/blo
Hi Chris,
thanks for summarize our session today in Vancouver. As I18n PTL and one
of the Docs Core I put Petr in Cc. He is currently Docs PTL, but
unfortunatelly not on-site.
I couldn't also not get the full history of the story and that's also
not the idea to starting finger pointing. As usu
You will want to follow the steps of the "project creators' guide"
[1]. Not all of them apply, because this is a docs repo and not a
code project repo. Let me know if you have questions about which
pieces do or do not apply as you go along, and we can work on
improving that document as well.
The
I hadn’t got that far in my thoughts. If you’re able to give that a go, then
that would be great!
Chris
Sent from my iPhone
> On May 23, 2018, at 6:46 PM, Jonathan D. Proulx wrote:
>
>
> Thanks for kicking this off Chris.
>
> Were you going to create that new repository? If not I can take
Thanks for kicking this off Chris.
Were you going to create that new repository? If not I can take on
the tasks of learning how and making it happen.
-Jon
On Wed, May 23, 2018 at 06:38:32PM -0700, Chris Morgan wrote:
: Hello Everyone,
: In the Ops Community documentation working session to
Hello Everyone,
In the Ops Community documentation working session today in Vancouver, we
made some really good progress (etherpad here:
https://etherpad.openstack.org/p/YVR-Ops-Community-Docs but not all of the
good stuff is yet written down).
In short, we're going to course correct on maintaini
31 matches
Mail list logo
