Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Jay S Bryant]

On 3/14/2018 10:57 AM, Doug Hellmann wrote:

Excerpts from Jay S Bryant's message of 2018-03-14 10:38:37 -0500:

On 3/14/2018 10:04 AM, Petr Kovar wrote:

On Tue, 13 Mar 2018 18:57:24 -0500
Jay S Bryant  wrote:


Amy,

The top level page for projects is referenced under documentation from
here:  https://docs.openstack.org/queens/projects.html

So, I think we have that one covered for people who are just looking for
the top level documentation.

Yes, we have that covered. Just to clarify this a bit further, we also have
project lists like https://docs.openstack.org/queens/install/,
https://docs.openstack.org/queens/admin/ and
https://docs.openstack.org/queens/configuration/, what's missing is
https://docs.openstack.org/queens/contributor/.

Cheers,
pk


Petr,

Do we need a contributor link per-release?  I thought in past
discussions that the contributor info should always go to latest and
that was why this is slightly different.

Jay

We can have a per-series page that lists all projects and links to their
"latest" contributor doc page.


Agreed.  That would make the most sense.


Doug

__
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-dev



__
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-dev

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Petr Kovar]

On Wed, 14 Mar 2018 10:38:37 -0500
Jay S Bryant  wrote:

> 
> 
> On 3/14/2018 10:04 AM, Petr Kovar wrote:
> > On Tue, 13 Mar 2018 18:57:24 -0500
> > Jay S Bryant  wrote:
> >
> >> Amy,
> >>
> >> The top level page for projects is referenced under documentation from
> >> here:  https://docs.openstack.org/queens/projects.html
> >>
> >> So, I think we have that one covered for people who are just looking for
> >> the top level documentation.
> > Yes, we have that covered. Just to clarify this a bit further, we also have
> > project lists like https://docs.openstack.org/queens/install/,
> > https://docs.openstack.org/queens/admin/ and
> > https://docs.openstack.org/queens/configuration/, what's missing is
> > https://docs.openstack.org/queens/contributor/.
> >
> > Cheers,
> > pk
> >
> Petr,
> 
> Do we need a contributor link per-release?  I thought in past 
> discussions that the contributor info should always go to latest and 
> that was why this is slightly different.

Right, that's a good point! I guess we should really just have
https://docs.openstack.org/latest/contributor/ then, perhaps
https://docs.openstack.org/contributor/ would be even better (with a
redirect). This means we need to treat templates for contributor project
docs as a special case and just point to /latest/contributor from all
release-specific docs.o.o landing pages.

Cheers,
pk


> >> On 3/13/2018 3:02 PM, Amy Marrich wrote:
> >>> I think if we're going to have that go to the development contributors
> >>> section (which makes sense) maybe we should also have ways of getting
> >>> to the deployment and admin docs as well?
> >>>
> >>> Amy (spotz)
> >>>
> >>> On Tue, Mar 13, 2018 at 2:55 PM, Jay S Bryant  >>> > wrote:
> >>>
> >>>
> >>>
> >>>  On 3/13/2018 1:38 PM, Petr Kovar wrote:
> >>>
> >>>  On Thu, 8 Mar 2018 12:54:06 -0600
> >>>  Jay S Bryant  >>>  > wrote:
> >>>
> >>>  Good overview.  Thank you!
> >>>
> >>>  One additional goal I want to mention on the list, for
> >>>  awareness, is the
> >>>  fact that we would like to eventually get some consistency
> >>>  to the pages
> >>>  that the 'Contributor Guide' lands on for each of the
> >>>  projects.  Needs
> >>>  to be a page that is friendly to new contributors, makes
> >>>  it easy to
> >>>  learn about the project and is not overwhelming.
> >>>
> >>>  What exactly that looks like isn't defined yet but I have
> >>>  talked to
> >>>  Manila about this.  They were interested in working
> >>>  together on this.
> >>>  Cinder and Manila will work together to get something
> >>>  consistent put
> >>>  together and then we can work on spreading that to other
> >>>  projects once
> >>>  we have agreement from the SIG that the approach is 
> >>> agreeable.
> >>>
> >>>  This is a good cross-project goal, I think. We discussed a
> >>>  similar approach
> >>>  in the docs room wrt providing templates to project teams that
> >>>  they can
> >>>  use to design their landing pages for admin, user,
> >>>  configuration docs; that
> >>>  would also include the main index page for project docs.
> >>>
> >>>  As for the project-specific contributor guides,
> >>>  https://docs.openstack.org/doc-contrib-guide/project-guides.html
> >>>  
> >>> 
> >>>  specifies
> >>>  that any contributor content should go to
> >>>  doc/source/contributor/. This will
> >>>  allow us to use templates to generate lists of links,
> >>>  similarly to what
> >>>  we do for other content areas.
> >>>
> >>>  Cheers,
> >>>  pk
> >>>
> >>>
> >>>  
> >>> __
> >>>  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-dev
> >>>  
> >>> 
> >>>
> >>>  Petr,
> >>>
> >>>  Good point.  I was trying to think of how to make a better landing
> >>>  page for new contributors and you may have hit on the answer.
> >>>  RIght now when you click through from  here:
> >>>  https://www.openstack.org/community
> >>>   You land at the top level
> 

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Doug Hellmann]

Excerpts from Jay S Bryant's message of 2018-03-14 10:38:37 -0500:
> 
> On 3/14/2018 10:04 AM, Petr Kovar wrote:
> > On Tue, 13 Mar 2018 18:57:24 -0500
> > Jay S Bryant  wrote:
> >
> >> Amy,
> >>
> >> The top level page for projects is referenced under documentation from
> >> here:  https://docs.openstack.org/queens/projects.html
> >>
> >> So, I think we have that one covered for people who are just looking for
> >> the top level documentation.
> > Yes, we have that covered. Just to clarify this a bit further, we also have
> > project lists like https://docs.openstack.org/queens/install/,
> > https://docs.openstack.org/queens/admin/ and
> > https://docs.openstack.org/queens/configuration/, what's missing is
> > https://docs.openstack.org/queens/contributor/.
> >
> > Cheers,
> > pk
> >
> Petr,
> 
> Do we need a contributor link per-release?  I thought in past 
> discussions that the contributor info should always go to latest and 
> that was why this is slightly different.
> 
> Jay

We can have a per-series page that lists all projects and links to their
"latest" contributor doc page.

Doug

__
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-dev

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Jay S Bryant]

On 3/14/2018 10:04 AM, Petr Kovar wrote:

On Tue, 13 Mar 2018 18:57:24 -0500
Jay S Bryant  wrote:


Amy,

The top level page for projects is referenced under documentation from
here:  https://docs.openstack.org/queens/projects.html

So, I think we have that one covered for people who are just looking for
the top level documentation.

Yes, we have that covered. Just to clarify this a bit further, we also have
project lists like https://docs.openstack.org/queens/install/,
https://docs.openstack.org/queens/admin/ and
https://docs.openstack.org/queens/configuration/, what's missing is
https://docs.openstack.org/queens/contributor/.

Cheers,
pk


Petr,

Do we need a contributor link per-release?  I thought in past 
discussions that the contributor info should always go to latest and 
that was why this is slightly different.


Jay



On 3/13/2018 3:02 PM, Amy Marrich wrote:

I think if we're going to have that go to the development contributors
section (which makes sense) maybe we should also have ways of getting
to the deployment and admin docs as well?

Amy (spotz)

On Tue, Mar 13, 2018 at 2:55 PM, Jay S Bryant > wrote:



 On 3/13/2018 1:38 PM, Petr Kovar wrote:

 On Thu, 8 Mar 2018 12:54:06 -0600
 Jay S Bryant > wrote:

 Good overview.  Thank you!

 One additional goal I want to mention on the list, for
 awareness, is the
 fact that we would like to eventually get some consistency
 to the pages
 that the 'Contributor Guide' lands on for each of the
 projects.  Needs
 to be a page that is friendly to new contributors, makes
 it easy to
 learn about the project and is not overwhelming.

 What exactly that looks like isn't defined yet but I have
 talked to
 Manila about this.  They were interested in working
 together on this.
 Cinder and Manila will work together to get something
 consistent put
 together and then we can work on spreading that to other
 projects once
 we have agreement from the SIG that the approach is agreeable.

 This is a good cross-project goal, I think. We discussed a
 similar approach
 in the docs room wrt providing templates to project teams that
 they can
 use to design their landing pages for admin, user,
 configuration docs; that
 would also include the main index page for project docs.

 As for the project-specific contributor guides,
 https://docs.openstack.org/doc-contrib-guide/project-guides.html
 
 specifies
 that any contributor content should go to
 doc/source/contributor/. This will
 allow us to use templates to generate lists of links,
 similarly to what
 we do for other content areas.

 Cheers,
 pk


 
__
 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-dev
 

 Petr,

 Good point.  I was trying to think of how to make a better landing
 page for new contributors and you may have hit on the answer.
 RIght now when you click through from  here:
 https://www.openstack.org/community
  You land at the top level
 Cinder documentation page which is incredibly overwhelming for a
 new person: https://docs.openstack.org/cinder/latest/
 

 If the new contributor page instead lands here:
 https://docs.openstack.org/cinder/latest/contributor/index.html
 
 It would give me a page to craft for new users looking for
 information to get started.

 Thoughts on this approach?

 Kendall and Mike ... Does the above approach make sense?

 Jay



 __
 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-dev
 

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Petr Kovar]

On Tue, 13 Mar 2018 18:57:24 -0500
Jay S Bryant  wrote:

> Amy,
> 
> The top level page for projects is referenced under documentation from 
> here:  https://docs.openstack.org/queens/projects.html
> 
> So, I think we have that one covered for people who are just looking for 
> the top level documentation.

Yes, we have that covered. Just to clarify this a bit further, we also have
project lists like https://docs.openstack.org/queens/install/,
https://docs.openstack.org/queens/admin/ and
https://docs.openstack.org/queens/configuration/, what's missing is
https://docs.openstack.org/queens/contributor/.

Cheers,
pk



> On 3/13/2018 3:02 PM, Amy Marrich wrote:
> > I think if we're going to have that go to the development contributors 
> > section (which makes sense) maybe we should also have ways of getting 
> > to the deployment and admin docs as well?
> >
> > Amy (spotz)
> >
> > On Tue, Mar 13, 2018 at 2:55 PM, Jay S Bryant  > > wrote:
> >
> >
> >
> > On 3/13/2018 1:38 PM, Petr Kovar wrote:
> >
> > On Thu, 8 Mar 2018 12:54:06 -0600
> > Jay S Bryant  > > wrote:
> >
> > Good overview.  Thank you!
> >
> > One additional goal I want to mention on the list, for
> > awareness, is the
> > fact that we would like to eventually get some consistency
> > to the pages
> > that the 'Contributor Guide' lands on for each of the
> > projects.  Needs
> > to be a page that is friendly to new contributors, makes
> > it easy to
> > learn about the project and is not overwhelming.
> >
> > What exactly that looks like isn't defined yet but I have
> > talked to
> > Manila about this.  They were interested in working
> > together on this.
> > Cinder and Manila will work together to get something
> > consistent put
> > together and then we can work on spreading that to other
> > projects once
> > we have agreement from the SIG that the approach is agreeable.
> >
> > This is a good cross-project goal, I think. We discussed a
> > similar approach
> > in the docs room wrt providing templates to project teams that
> > they can
> > use to design their landing pages for admin, user,
> > configuration docs; that
> > would also include the main index page for project docs.
> >
> > As for the project-specific contributor guides,
> > https://docs.openstack.org/doc-contrib-guide/project-guides.html
> > 
> > specifies
> > that any contributor content should go to
> > doc/source/contributor/. This will
> > allow us to use templates to generate lists of links,
> > similarly to what
> > we do for other content areas.
> >
> > Cheers,
> > pk
> >
> >
> > 
> > __
> > 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-dev
> > 
> >
> > Petr,
> >
> > Good point.  I was trying to think of how to make a better landing
> > page for new contributors and you may have hit on the answer. 
> > RIght now when you click through from  here:
> > https://www.openstack.org/community
> >  You land at the top level
> > Cinder documentation page which is incredibly overwhelming for a
> > new person: https://docs.openstack.org/cinder/latest/
> > 
> >
> > If the new contributor page instead lands here:
> > https://docs.openstack.org/cinder/latest/contributor/index.html
> > 
> > It would give me a page to craft for new users looking for
> > information to get started.
> >
> > Thoughts on this approach?
> >
> > Kendall and Mike ... Does the above approach make sense?
> >
> > Jay
> >
> >
> >
> > 
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > 
> > 

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Jay S Bryant]

Amy,

The top level page for projects is referenced under documentation from 
here:  https://docs.openstack.org/queens/projects.html


So, I think we have that one covered for people who are just looking for 
the top level documentation.


Jay


On 3/13/2018 3:02 PM, Amy Marrich wrote:
I think if we're going to have that go to the development contributors 
section (which makes sense) maybe we should also have ways of getting 
to the deployment and admin docs as well?


Amy (spotz)

On Tue, Mar 13, 2018 at 2:55 PM, Jay S Bryant > wrote:




On 3/13/2018 1:38 PM, Petr Kovar wrote:

On Thu, 8 Mar 2018 12:54:06 -0600
Jay S Bryant > wrote:

Good overview.  Thank you!

One additional goal I want to mention on the list, for
awareness, is the
fact that we would like to eventually get some consistency
to the pages
that the 'Contributor Guide' lands on for each of the
projects.  Needs
to be a page that is friendly to new contributors, makes
it easy to
learn about the project and is not overwhelming.

What exactly that looks like isn't defined yet but I have
talked to
Manila about this.  They were interested in working
together on this.
Cinder and Manila will work together to get something
consistent put
together and then we can work on spreading that to other
projects once
we have agreement from the SIG that the approach is agreeable.

This is a good cross-project goal, I think. We discussed a
similar approach
in the docs room wrt providing templates to project teams that
they can
use to design their landing pages for admin, user,
configuration docs; that
would also include the main index page for project docs.

As for the project-specific contributor guides,
https://docs.openstack.org/doc-contrib-guide/project-guides.html

specifies
that any contributor content should go to
doc/source/contributor/. This will
allow us to use templates to generate lists of links,
similarly to what
we do for other content areas.

Cheers,
pk



__
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-dev


Petr,

Good point.  I was trying to think of how to make a better landing
page for new contributors and you may have hit on the answer. 
RIght now when you click through from  here:
https://www.openstack.org/community
 You land at the top level
Cinder documentation page which is incredibly overwhelming for a
new person: https://docs.openstack.org/cinder/latest/


If the new contributor page instead lands here:
https://docs.openstack.org/cinder/latest/contributor/index.html

It would give me a page to craft for new users looking for
information to get started.

Thoughts on this approach?

Kendall and Mike ... Does the above approach make sense?

Jay



__
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-dev





__
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-dev

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Amy Marrich]

I think if we're going to have that go to the development contributors
section (which makes sense) maybe we should also have ways of getting to
the deployment and admin docs as well?

Amy (spotz)

On Tue, Mar 13, 2018 at 2:55 PM, Jay S Bryant  wrote:

>
>
> On 3/13/2018 1:38 PM, Petr Kovar wrote:
>
>> On Thu, 8 Mar 2018 12:54:06 -0600
>> Jay S Bryant  wrote:
>>
>> Good overview.  Thank you!
>>>
>>> One additional goal I want to mention on the list, for awareness, is the
>>> fact that we would like to eventually get some consistency to the pages
>>> that the 'Contributor Guide' lands on for each of the projects.  Needs
>>> to be a page that is friendly to new contributors, makes it easy to
>>> learn about the project and is not overwhelming.
>>>
>>> What exactly that looks like isn't defined yet but I have talked to
>>> Manila about this.  They were interested in working together on this.
>>> Cinder and Manila will work together to get something consistent put
>>> together and then we can work on spreading that to other projects once
>>> we have agreement from the SIG that the approach is agreeable.
>>>
>> This is a good cross-project goal, I think. We discussed a similar
>> approach
>> in the docs room wrt providing templates to project teams that they can
>> use to design their landing pages for admin, user, configuration docs;
>> that
>> would also include the main index page for project docs.
>>
>> As for the project-specific contributor guides,
>> https://docs.openstack.org/doc-contrib-guide/project-guides.html
>> specifies
>> that any contributor content should go to doc/source/contributor/. This
>> will
>> allow us to use templates to generate lists of links, similarly to what
>> we do for other content areas.
>>
>> Cheers,
>> pk
>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
> Petr,
>
> Good point.  I was trying to think of how to make a better landing page
> for new contributors and you may have hit on the answer.  RIght now when
> you click through from  here: https://www.openstack.org/community  You
> land at the top level Cinder documentation page which is incredibly
> overwhelming for a new person:  https://docs.openstack.org/cinder/latest/
>
> If the new contributor page instead lands here:
> https://docs.openstack.org/cinder/latest/contributor/index.html It would
> give me a page to craft for new users looking for information to get
> started.
>
> Thoughts on this approach?
>
> Kendall and Mike ... Does the above approach make sense?
>
> Jay
>
>
>
> __
> 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-dev
>
__
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-dev

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Jay S Bryant]

On 3/13/2018 1:38 PM, Petr Kovar wrote:

On Thu, 8 Mar 2018 12:54:06 -0600
Jay S Bryant  wrote:


Good overview.  Thank you!

One additional goal I want to mention on the list, for awareness, is the
fact that we would like to eventually get some consistency to the pages
that the 'Contributor Guide' lands on for each of the projects.  Needs
to be a page that is friendly to new contributors, makes it easy to
learn about the project and is not overwhelming.

What exactly that looks like isn't defined yet but I have talked to
Manila about this.  They were interested in working together on this.
Cinder and Manila will work together to get something consistent put
together and then we can work on spreading that to other projects once
we have agreement from the SIG that the approach is agreeable.

This is a good cross-project goal, I think. We discussed a similar approach
in the docs room wrt providing templates to project teams that they can
use to design their landing pages for admin, user, configuration docs; that
would also include the main index page for project docs.

As for the project-specific contributor guides,
https://docs.openstack.org/doc-contrib-guide/project-guides.html specifies
that any contributor content should go to doc/source/contributor/. This will
allow us to use templates to generate lists of links, similarly to what
we do for other content areas.

Cheers,
pk


__
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-dev

Petr,

Good point.  I was trying to think of how to make a better landing page 
for new contributors and you may have hit on the answer.  RIght now when 
you click through from  here: https://www.openstack.org/community  You 
land at the top level Cinder documentation page which is incredibly 
overwhelming for a new person:  https://docs.openstack.org/cinder/latest/


If the new contributor page instead lands here: 
https://docs.openstack.org/cinder/latest/contributor/index.html It would 
give me a page to craft for new users looking for information to get 
started.


Thoughts on this approach?

Kendall and Mike ... Does the above approach make sense?

Jay


__
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-dev

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Petr Kovar]

On Thu, 8 Mar 2018 12:54:06 -0600
Jay S Bryant  wrote:

> Good overview.  Thank you!
> 
> One additional goal I want to mention on the list, for awareness, is the 
> fact that we would like to eventually get some consistency to the pages 
> that the 'Contributor Guide' lands on for each of the projects.  Needs 
> to be a page that is friendly to new contributors, makes it easy to 
> learn about the project and is not overwhelming.
> 
> What exactly that looks like isn't defined yet but I have talked to 
> Manila about this.  They were interested in working together on this.  
> Cinder and Manila will work together to get something consistent put 
> together and then we can work on spreading that to other projects once 
> we have agreement from the SIG that the approach is agreeable.

This is a good cross-project goal, I think. We discussed a similar approach
in the docs room wrt providing templates to project teams that they can
use to design their landing pages for admin, user, configuration docs; that
would also include the main index page for project docs.

As for the project-specific contributor guides,
https://docs.openstack.org/doc-contrib-guide/project-guides.html specifies
that any contributor content should go to doc/source/contributor/. This will
allow us to use templates to generate lists of links, similarly to what
we do for other content areas.

Cheers,
pk


__
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-dev

Re: [openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Jay S Bryant]

Good overview.  Thank you!

One additional goal I want to mention on the list, for awareness, is the 
fact that we would like to eventually get some consistency to the pages 
that the 'Contributor Guide' lands on for each of the projects.  Needs 
to be a page that is friendly to new contributors, makes it easy to 
learn about the project and is not overwhelming.


What exactly that looks like isn't defined yet but I have talked to 
Manila about this.  They were interested in working together on this.  
Cinder and Manila will work together to get something consistent put 
together and then we can work on spreading that to other projects once 
we have agreement from the SIG that the approach is agreeable.


Jay

(jungleboyj)



On 3/5/2018 2:00 PM, Kendall Nelson wrote:

Hello Everyone :)

It was wonderful to see and talk with so many of you last week! For 
those that couldn't attend our whole day of chats or those that 
couldn't attend at all, I thought I would put forth a summary of our 
discussions which were mostly noted in the etherpad[1]


#Contributor Guide#

- Walkthrough: We walked through every section of what exists and came 
up with a variety of improvements on what is there. Most of these 
items have been added to our StoryBoard project[2]. This came up again 
Tuesday in docs sessions and I have added those items to StoryBoard as 
well.


- Google Analytics: It was discussed we should do something about 
getting the contributor portal[3] to appear higher in Google searches 
about onboarding. Not sure what all this entails. NEEDS AN OWNER IF 
ANYONE WANTS TO VOLUNTEER.


#Mission Statement#

We updated our mission statement[4]! It now states:

To provide a place for new contributors to come for information and 
advice. This group will also analyze and document successful 
contribution models while seeking out and providing information to new 
members of the community.


#Weekly Meeting#

We discussed beginning a weekly meeting- optimized for APAC/Europe and 
settled on 800 UTC in #openstack-meeting on Wednesdays. Proposed 
here[5]. For now I added a section to our wiki for agenda 
organization[6]. The two main items we want to cover on a weekly basis 
are new contributor patches in gerrit and if anything has come up on 
ask.openstack.org  about contributors so 
those will be standing agenda items.


#Forum Session#

We discussed proposing some forum sessions in order to get more 
involvement from operators. Currently, our activities focus on 
development activities and we would like to diversify. When this SIG 
was first proposed we wanted to have two chairs- one to represent 
developers and one to represent operators. We will propose a session 
or two when the call for forum proposals go out (should be today).


#IRC Channels#
We want to get rid of #openstack-101 and begin using #openstack-dev 
instead. The 101 channel isn't watched closely enough anymore and it 
makes more sense to move onboarding activities (like in OpenStack 
Upstream Institute) to a channel where there are people that can 
answer questions rather than asking those to move to a new channel. 
For those concerned about noise, OUI is run the weekend before the 
summit when most people are traveling to the Summit anyway.


#Ongoing Onboarding Efforts#

- GSOC: Unfortunately we didn't get accepted this year. We will try 
again next year.


- Outreachy: Applications for the next round of interns are due March 
22nd, 2018 [7]. Decisions will be made by April and then internships 
run May to August.


- WoO Mentoring: The format of mentoring is changing from 1x1 to 
cohorts focused on a single goal. If you are interested in helping 
out, please contact me! I NEED HELP :)


- Contributor guide: Please see the above section.

- OpenStack Upstream Institute: It will be run, as usual, the weekend 
before the Summit in Vancouver. Depending on how much progress is made 
on the contributor guide, we will make use of it as opposed to slides 
like previous renditions. There have also been a number of OpenStack 
Days requesting we run it there as well. More details of those to come.


#Project Liaisons#

The list is filling out nicely, but we still need more coverage. If 
you know someone from a project not listed that might be willing to 
help, please reach out to them and get them added to our list [8].


I thiink that is just about everything. Hopefully I at least 
covered everything important :)


Thanks Everyone!

- Kendall Nelson (diablo_rojo)

[1] PTG Etherpad https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG
[2] StoryBoard Tracker https://storyboard.openstack.org/#!/project/913 


[3] Contributor Portal https://www.openstack.org/community/
[4] Mission Statement Update https://review.openstack.org/#/c/548054/
[5] Meeting Slot Proposal https://review.openstack.org/#/c/549849/
[6] Meeting Agenda 

[openstack-dev] [First Contact][SIG] [PTG] Summary of Discussions

[Kendall Nelson]

Hello Everyone :)

It was wonderful to see and talk with so many of you last week! For those
that couldn't attend our whole day of chats or those that couldn't attend
at all, I thought I would put forth a summary of our discussions which were
mostly noted in the etherpad[1]

#Contributor Guide#

- Walkthrough: We walked through every section of what exists and came up
with a variety of improvements on what is there. Most of these items have
been added to our StoryBoard project[2]. This came up again Tuesday in docs
sessions and I have added those items to StoryBoard as well.

- Google Analytics: It was discussed we should do something about getting
the contributor portal[3] to appear higher in Google searches about
onboarding. Not sure what all this entails. NEEDS AN OWNER IF ANYONE WANTS
TO VOLUNTEER.

#Mission Statement#

We updated our mission statement[4]! It now states:

To provide a place for new contributors to come for information and advice.
This group will also analyze and document successful contribution models
while seeking out and providing information to new members of the community.

#Weekly Meeting#

We discussed beginning a weekly meeting- optimized for APAC/Europe and
settled on 800 UTC in #openstack-meeting on Wednesdays. Proposed here[5].
For now I added a section to our wiki for agenda organization[6]. The two
main items we want to cover on a weekly basis are new contributor patches
in gerrit and if anything has come up on ask.openstack.org about
contributors so those will be standing agenda items.

#Forum Session#

We discussed proposing some forum sessions in order to get more involvement
from operators. Currently, our activities focus on development activities
and we would like to diversify. When this SIG was first proposed we wanted
to have two chairs- one to represent developers and one to represent
operators. We will propose a session or two when the call for forum
proposals go out (should be today).

#IRC Channels#
We want to get rid of #openstack-101 and begin using #openstack-dev
instead. The 101 channel isn't watched closely enough anymore and it makes
more sense to move onboarding activities (like in OpenStack Upstream
Institute) to a channel where there are people that can answer questions
rather than asking those to move to a new channel. For those concerned
about noise, OUI is run the weekend before the summit when most people are
traveling to the Summit anyway.

#Ongoing Onboarding Efforts#

- GSOC: Unfortunately we didn't get accepted this year. We will try again
next year.

- Outreachy: Applications for the next round of interns are due March 22nd,
2018 [7]. Decisions will be made by April and then internships run May to
August.

- WoO Mentoring: The format of mentoring is changing from 1x1 to cohorts
focused on a single goal. If you are interested in helping out, please
contact me! I NEED HELP :)

- Contributor guide: Please see the above section.

- OpenStack Upstream Institute: It will be run, as usual, the weekend
before the Summit in Vancouver. Depending on how much progress is made on
the contributor guide, we will make use of it as opposed to slides like
previous renditions. There have also been a number of OpenStack Days
requesting we run it there as well. More details of those to come.

#Project Liaisons#

The list is filling out nicely, but we still need more coverage. If you
know someone from a project not listed that might be willing to help,
please reach out to them and get them added to our list [8].

I thiink that is just about everything. Hopefully I at least covered
everything important :)

Thanks Everyone!

- Kendall Nelson (diablo_rojo)

[1] PTG Etherpad https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG
[2] StoryBoard Tracker https://storyboard.openstack.org/#!/project/913
[3] Contributor Portal https://www.openstack.org/community/
[4] Mission Statement Update https://review.openstack.org/#/c/548054/
[5] Meeting Slot Proposal https://review.openstack.org/#/c/549849/
[6] Meeting Agenda
https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda
[7] Outreachy https://www.outreachy.org/apply/
[8] Project Liaisons
https://wiki.openstack.org/wiki/First_Contact_SIG#Project_Liaisons
__
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-dev