Re: [openstack-dev] [tc] assigning new liaisons to projects

[Doug Hellmann]

Trinh Nguyen  writes:

> Thank Doug for coordinating this,
>
> Is there any way for us to update the health of the Searchlight project to
> reflect the current state? Right now the status is not good to attract new
> contributors.

When the new liaisons are assigned, please talk to them about the
current status.

Doug

>
> Bests,
>
> On Fri, Oct 12, 2018 at 6:50 AM Doug Hellmann  wrote:
>
>> Doug Hellmann  writes:
>>
>> > TC members,
>> >
>> > Since we are starting a new term, and have several new members, we need
>> > to decide how we want to rotate the liaisons attached to each our
>> > project teams, SIGs, and working groups [1].
>> >
>> > Last term we went through a period of volunteer sign-up and then I
>> > randomly assigned folks to slots to fill out the roster evenly. During
>> > the retrospective we talked a bit about how to ensure we had an
>> > objective perspective for each team by not having PTLs sign up for their
>> > own teams, but I don't think we settled on that as a hard rule.
>> >
>> > I think the easiest and fairest (to new members) way to manage the list
>> > will be to wipe it and follow the same process we did last time. If you
>> > agree, I will update the page this week and we can start collecting
>> > volunteers over the next week or so.
>> >
>> > Doug
>> >
>> > [1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
>> >
>> >
>> __
>> > 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
>>
>> I have cleared out the old assignments. Please go over and edit the wiki
>> page to add yourself to the teams you want to volunteer for. Remember
>> that each member needs to sign up for exactly 10 teams. If you don't
>> volunteer for 10, we'll use the script to make random assignments for
>> the remaining slots.
>>
>> 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
>>
>
>
> -- 
> *Trinh Nguyen*
> *www.edlab.xyz *
> __
> 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] [tc] assigning new liaisons to projects

[Trinh Nguyen]

Thank Doug for coordinating this,

Is there any way for us to update the health of the Searchlight project to
reflect the current state? Right now the status is not good to attract new
contributors.

Bests,

On Fri, Oct 12, 2018 at 6:50 AM Doug Hellmann  wrote:

> Doug Hellmann  writes:
>
> > TC members,
> >
> > Since we are starting a new term, and have several new members, we need
> > to decide how we want to rotate the liaisons attached to each our
> > project teams, SIGs, and working groups [1].
> >
> > Last term we went through a period of volunteer sign-up and then I
> > randomly assigned folks to slots to fill out the roster evenly. During
> > the retrospective we talked a bit about how to ensure we had an
> > objective perspective for each team by not having PTLs sign up for their
> > own teams, but I don't think we settled on that as a hard rule.
> >
> > I think the easiest and fairest (to new members) way to manage the list
> > will be to wipe it and follow the same process we did last time. If you
> > agree, I will update the page this week and we can start collecting
> > volunteers over the next week or so.
> >
> > Doug
> >
> > [1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
> >
> >
> __
> > 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
>
> I have cleared out the old assignments. Please go over and edit the wiki
> page to add yourself to the teams you want to volunteer for. Remember
> that each member needs to sign up for exactly 10 teams. If you don't
> volunteer for 10, we'll use the script to make random assignments for
> the remaining slots.
>
> 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
>


-- 
*Trinh Nguyen*
*www.edlab.xyz *
__
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] [tc] assigning new liaisons to projects

[Doug Hellmann]

Doug Hellmann  writes:

> TC members,
>
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
>
> Last term we went through a period of volunteer sign-up and then I
> randomly assigned folks to slots to fill out the roster evenly. During
> the retrospective we talked a bit about how to ensure we had an
> objective perspective for each team by not having PTLs sign up for their
> own teams, but I don't think we settled on that as a hard rule.
>
> I think the easiest and fairest (to new members) way to manage the list
> will be to wipe it and follow the same process we did last time. If you
> agree, I will update the page this week and we can start collecting
> volunteers over the next week or so.
>
> Doug
>
> [1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
>
> __
> 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

I have cleared out the old assignments. Please go over and edit the wiki
page to add yourself to the teams you want to volunteer for. Remember
that each member needs to sign up for exactly 10 teams. If you don't
volunteer for 10, we'll use the script to make random assignments for
the remaining slots.

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] [tc] assigning new liaisons to projects

[Jean-Philippe Evrard]

On Mon, 2018-10-08 at 10:27 -0400, Doug Hellmann wrote:
> TC members,
> 
> Since we are starting a new term, and have several new members, we
> need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
> 
> Last term we went through a period of volunteer sign-up and then I
> randomly assigned folks to slots to fill out the roster evenly.
> During
> the retrospective we talked a bit about how to ensure we had an
> objective perspective for each team by not having PTLs sign up for
> their
> own teams, but I don't think we settled on that as a hard rule.
> 
> I think the easiest and fairest (to new members) way to manage the
> list
> will be to wipe it and follow the same process we did last time. If
> you
> agree, I will update the page this week and we can start collecting
> volunteers over the next week or so.
> 
> Doug
> 
> [1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
> 
> _
> _
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
> cribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

+1


__
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] [tc] assigning new liaisons to projects

[Davanum Srinivas]

On Mon, Oct 8, 2018 at 11:57 PM Ghanshyam Mann 
wrote:

>
>
>
>   On Mon, 08 Oct 2018 23:27:06 +0900 Doug Hellmann <
> d...@doughellmann.com> wrote 
>  > TC members,
>  >
>  > Since we are starting a new term, and have several new members, we need
>  > to decide how we want to rotate the liaisons attached to each our
>  > project teams, SIGs, and working groups [1].
>  >
>  > Last term we went through a period of volunteer sign-up and then I
>  > randomly assigned folks to slots to fill out the roster evenly. During
>  > the retrospective we talked a bit about how to ensure we had an
>  > objective perspective for each team by not having PTLs sign up for their
>  > own teams, but I don't think we settled on that as a hard rule.
>  >
>  > I think the easiest and fairest (to new members) way to manage the list
>  > will be to wipe it and follow the same process we did last time. If you
>  > agree, I will update the page this week and we can start collecting
>  > volunteers over the next week or so.
>
> +1, sounds good to me.
>
> -gmann
>

+1 from me as well.



>  >
>  > Doug
>  >
>  > [1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
>  >
>  >
> __
>  > 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
>


-- 
Davanum Srinivas :: https://twitter.com/dims
__
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] [tc] assigning new liaisons to projects

[Ghanshyam Mann]

  On Mon, 08 Oct 2018 23:27:06 +0900 Doug Hellmann  
wrote  
 > TC members,
 > 
 > Since we are starting a new term, and have several new members, we need
 > to decide how we want to rotate the liaisons attached to each our
 > project teams, SIGs, and working groups [1].
 > 
 > Last term we went through a period of volunteer sign-up and then I
 > randomly assigned folks to slots to fill out the roster evenly. During
 > the retrospective we talked a bit about how to ensure we had an
 > objective perspective for each team by not having PTLs sign up for their
 > own teams, but I don't think we settled on that as a hard rule.
 > 
 > I think the easiest and fairest (to new members) way to manage the list
 > will be to wipe it and follow the same process we did last time. If you
 > agree, I will update the page this week and we can start collecting
 > volunteers over the next week or so.

+1, sounds good to me.

-gmann

 > 
 > Doug
 > 
 > [1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
 > 
 > __
 > 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] [tc] assigning new liaisons to projects

[Julia Kreger]

On Mon, Oct 8, 2018 at 8:27 AM Doug Hellmann  wrote:

> TC members,
>
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
>
> Last term we went through a period of volunteer sign-up and then I
> randomly assigned folks to slots to fill out the roster evenly. During
> the retrospective we talked a bit about how to ensure we had an
> objective perspective for each team by not having PTLs sign up for their
> own teams, but I don't think we settled on that as a hard rule.
>
> I think the easiest and fairest (to new members) way to manage the list
> will be to wipe it and follow the same process we did last time. If you
> agree, I will update the page this week and we can start collecting
> volunteers over the next week or so.
>
> Doug
>
> [1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
>
>
>
+1, Sounds good. I would just ask that if a TC is member has any
expectation on another member to post  a status update, that they
explicitly reach out and convey that expectation so we minimize confusion.
__
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] [tc] assigning new liaisons to projects

[Sean McGinnis]

On Mon, Oct 08, 2018 at 10:27:06AM -0400, Doug Hellmann wrote:
> TC members,
> 
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
> 
> Last term we went through a period of volunteer sign-up and then I
> randomly assigned folks to slots to fill out the roster evenly. During
> the retrospective we talked a bit about how to ensure we had an
> objective perspective for each team by not having PTLs sign up for their
> own teams, but I don't think we settled on that as a hard rule.
> 
> I think the easiest and fairest (to new members) way to manage the list
> will be to wipe it and follow the same process we did last time. If you
> agree, I will update the page this week and we can start collecting
> volunteers over the next week or so.
> 
> Doug
> 

Seems fair and a good approach to me.

Sean

__
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] [tc] assigning new liaisons to projects

[Lance Bragstad]

On Mon, Oct 8, 2018 at 9:27 AM Doug Hellmann  wrote:

> TC members,
>
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
>
> Last term we went through a period of volunteer sign-up and then I
> randomly assigned folks to slots to fill out the roster evenly. During
> the retrospective we talked a bit about how to ensure we had an
> objective perspective for each team by not having PTLs sign up for their
> own teams, but I don't think we settled on that as a hard rule.
>
> I think the easiest and fairest (to new members) way to manage the list
> will be to wipe it and follow the same process we did last time. If you
> agree, I will update the page this week and we can start collecting
> volunteers over the next week or so.
>

+1

>From the perspective of someone new, it'll be nice to go through all the
motions.


>
> Doug
>
> [1] https://wiki.openstack.org/wiki/OpenStack_health_tracker
>
> __
> 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

[openstack-dev] [tc] assigning new liaisons to projects

[Doug Hellmann]

TC members,

Since we are starting a new term, and have several new members, we need
to decide how we want to rotate the liaisons attached to each our
project teams, SIGs, and working groups [1].

Last term we went through a period of volunteer sign-up and then I
randomly assigned folks to slots to fill out the roster evenly. During
the retrospective we talked a bit about how to ensure we had an
objective perspective for each team by not having PTLs sign up for their
own teams, but I don't think we settled on that as a hard rule.

I think the easiest and fairest (to new members) way to manage the list
will be to wipe it and follow the same process we did last time. If you
agree, I will update the page this week and we can start collecting
volunteers over the next week or so.

Doug

[1] https://wiki.openstack.org/wiki/OpenStack_health_tracker

__
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