settingsLogin | Registersettings

[Openstack-operators] Documentation Sprint

0 votes

One take away from the OpenStack operators meetup in philly this week was
the need to refresh some of the operator guides, the security guide, and
potentially put together a packaging ( deployment ) guide. I am not part
of the OpenStack documentation team, but I know they could use some help
from our side. So if we have the heads we need to get this done, I'll
reach out to them and figure out what they want us to do in terms of the
task standard and condition for documentation updates.

I figure what we want to do is get a few volunteers for each. Pick a day,
and get on a hangout, skype, webex what have you and pound out some updates
/ drafts. Alternatively we can meet somewhere geographically and spend a
day or two focused on this.

It is my opinion that the summit will be too jam packed with work for us to
spend time working on documentation. I am in NYC and can host a
documentation sprint here. Or we can figure out some other place. Though,
honestly we can probably do this on webex.

So this email is basically a call to arms. We need some folks to be
willing to sign up to help fix / update some documentation. Are you
willing?

If so email respond or respond direct to me. I'll get a list of volunteers
going. We can go from there. Or someone else can totally run this instead
of me if they feel they can do a better job ( they probably can =P ).

-Matt


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
asked Mar 11, 2015 in openstack-operators by matt (5,480 points)   1 2 3
retagged Apr 14, 2015 by admin

7 Responses

0 votes

On 3/11/15 11:09 AM, matt wrote:

So this email is basically a call to arms. We need some folks to be
willing to sign up to help fix / update some documentation. Are you
willing?

Put me down as willing. I've done doc sprints before.

--
-jlk


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 11, 2015 by jlk_at_bluebox.net (2,760 points)   2 3
0 votes

Dear All,

I'm willing to sign up with you.

Regards,

Asmaa

On Wed, Mar 11, 2015 at 6:59 PM, Jesse Keating jlk@bluebox.net wrote:

On 3/11/15 11:09 AM, matt wrote:

So this email is basically a call to arms. We need some folks to be
willing to sign up to help fix / update some documentation. Are you
willing?

Put me down as willing. I've done doc sprints before.

--
-jlk


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

--
--
Thanks,

Asmaa


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 12, 2015 by Asmaa_Ibrahim (220 points)   1
0 votes

On 03/11/2015 04:09 PM, matt wrote:
One take away from the OpenStack operators meetup in philly this week
was the need to refresh some of the operator guides, the security guide,
and potentially put together a packaging ( deployment ) guide. I am not
part of the OpenStack documentation team, but I know they could use some
help from our side. So if we have the heads we need to get this done,
I'll reach out to them and figure out what they want us to do in terms
of the task standard and condition for documentation updates.

What do you mean with packaging / deployment guide? Could you point me
to any discussion or etherpad?

For Operator's guide, Security Guide and HA Guide, contribution is
indeed very welcome.

I suggest to discuss this on the openstack-docs mailing list where all
the documentation folks are, so let me CC the list.

I figure what we want to do is get a few volunteers for each. Pick a
day, and get on a hangout, skype, webex what have you and pound out some
updates / drafts. Alternatively we can meet somewhere geographically
and spend a day or two focused on this.

It is my opinion that the summit will be too jam packed with work for us
to spend time working on documentation. I am in NYC and can host a
documentation sprint here. Or we can figure out some other place.
Though, honestly we can probably do this on webex.

So this email is basically a call to arms. We need some folks to be
willing to sign up to help fix / update some documentation. Are you
willing?

If so email respond or respond direct to me. I'll get a list of
volunteers going. We can go from there. Or someone else can totally
run this instead of me if they feel they can do a better job ( they
probably can =P ).

Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton, HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 12, 2015 by Andreas_Jaeger (17,140 points)   2 3 4
0 votes

packaging / deployment guide extends from this etherpad discussion:
https://etherpad.openstack.org/p/PHL-ops-packaging

-matt

On Thu, Mar 12, 2015 at 3:37 AM, Andreas Jaeger aj@suse.com wrote:

On 03/11/2015 04:09 PM, matt wrote:

One take away from the OpenStack operators meetup in philly this week
was the need to refresh some of the operator guides, the security guide,
and potentially put together a packaging ( deployment ) guide. I am not
part of the OpenStack documentation team, but I know they could use some
help from our side. So if we have the heads we need to get this done,
I'll reach out to them and figure out what they want us to do in terms
of the task standard and condition for documentation updates.

What do you mean with packaging / deployment guide? Could you point me
to any discussion or etherpad?

For Operator's guide, Security Guide and HA Guide, contribution is
indeed very welcome.

I suggest to discuss this on the openstack-docs mailing list where all
the documentation folks are, so let me CC the list.

I figure what we want to do is get a few volunteers for each. Pick a
day, and get on a hangout, skype, webex what have you and pound out some
updates / drafts. Alternatively we can meet somewhere geographically
and spend a day or two focused on this.

It is my opinion that the summit will be too jam packed with work for us
to spend time working on documentation. I am in NYC and can host a
documentation sprint here. Or we can figure out some other place.
Though, honestly we can probably do this on webex.

So this email is basically a call to arms. We need some folks to be
willing to sign up to help fix / update some documentation. Are you
willing?

If so email respond or respond direct to me. I'll get a list of
volunteers going. We can go from there. Or someone else can totally
run this instead of me if they feel they can do a better job ( they
probably can =P ).

Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton, HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 12, 2015 by matt (5,480 points)   1 2 3
0 votes

I'm in.

On Thu, Mar 12, 2015 at 3:38 PM, matt matt@nycresistor.com wrote:

packaging / deployment guide extends from this etherpad discussion:
https://etherpad.openstack.org/p/PHL-ops-packaging

-matt

On Thu, Mar 12, 2015 at 3:37 AM, Andreas Jaeger aj@suse.com wrote:

On 03/11/2015 04:09 PM, matt wrote:

One take away from the OpenStack operators meetup in philly this week
was the need to refresh some of the operator guides, the security guide,
and potentially put together a packaging ( deployment ) guide. I am not
part of the OpenStack documentation team, but I know they could use some
help from our side. So if we have the heads we need to get this done,
I'll reach out to them and figure out what they want us to do in terms
of the task standard and condition for documentation updates.

What do you mean with packaging / deployment guide? Could you point me
to any discussion or etherpad?

For Operator's guide, Security Guide and HA Guide, contribution is
indeed very welcome.

I suggest to discuss this on the openstack-docs mailing list where all
the documentation folks are, so let me CC the list.

I figure what we want to do is get a few volunteers for each. Pick a
day, and get on a hangout, skype, webex what have you and pound out some
updates / drafts. Alternatively we can meet somewhere geographically
and spend a day or two focused on this.

It is my opinion that the summit will be too jam packed with work for us
to spend time working on documentation. I am in NYC and can host a
documentation sprint here. Or we can figure out some other place.
Though, honestly we can probably do this on webex.

So this email is basically a call to arms. We need some folks to be
willing to sign up to help fix / update some documentation. Are you
willing?

If so email respond or respond direct to me. I'll get a list of
volunteers going. We can go from there. Or someone else can totally
run this instead of me if they feel they can do a better job ( they
probably can =P ).

Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton, HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 12, 2015 by David_Medberry (8,000 points)   1 4 5
0 votes

On 12/03/15 00:59, Jesse Keating wrote:
On 3/11/15 11:09 AM, matt wrote:

So this email is basically a call to arms. We need some folks to be
willing to sign up to help fix / update some documentation. Are you
willing?

Put me down as willing. I've done doc sprints before.

Count me in.


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 13, 2015 by Tom_Fifield (13,880 points)   2 3 5
0 votes

On 11 Mar 2015 (11:09), matt wrote:

(...)

So this email is basically a call to arms. We need some folks to be
willing to sign up to help fix / update some documentation. Are you
willing?

If so email respond or respond direct to me. I'll get a list of volunteers
going. We can go from there. Or someone else can totally run this instead
of me if they feel they can do a better job ( they probably can =P ).

Depending on the dates-timeframe I could be able to contribute.

Regards,
--
Álvaro López García aloga@ifca.unican.es
Instituto de Física de Cantabria http://alvarolopez.github.io
Ed. Juan Jordá, Campus UC tel: (+34) 942 200 969
Avda. de los Castros s/n
39005 Santander (SPAIN)


OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
responded Mar 13, 2015 by Álvaro_López_García (380 points)   1
...