Shamail,

Please, send a reminder of the day and time when the meeting will be hosted.

Edgar

From: Shamail Tahir <itzsham...@gmail.com<mailto:itzsham...@gmail.com>>
Date: Wednesday, March 30, 2016 at 5:38 PM
To: Rochelle Grober 
<rochelle.gro...@huawei.com<mailto:rochelle.gro...@huawei.com>>
Cc: openstack-operators 
<openstack-operators@lists.openstack.org<mailto:openstack-operators@lists.openstack.org>>,
 
"user-commit...@lists.openstack.org<mailto:user-commit...@lists.openstack.org>" 
<user-commit...@lists.openstack.org<mailto:user-commit...@lists.openstack.org>>,
 "commun...@lists.openstack.org<mailto:commun...@lists.openstack.org>" 
<commun...@lists.openstack.org<mailto:commun...@lists.openstack.org>>
Subject: Re: [openstack-community] [User-committee] Announcing the Non-ATC 
Recognition Working Group

Hi Rocky,

The plan is to start the meeting next week.  I created the poll so that people 
can pick days of the week and times that will work best for them.  I apologize 
for any confusion caused by the dates, the meeting will actually start next 
week and will be scheduled for the best day/time.  I hope this helps!

Thanks,
Shamail

On Wed, Mar 30, 2016 at 8:30 PM, Rochelle Grober 
<rochelle.gro...@huawei.com<mailto:rochelle.gro...@huawei.com>> wrote:
Left a comment on the doodle.

Could you double-check the dates?  Most of the days and times listed are 
already past.

--Rocky

From: Shamail Tahir [mailto:itzsham...@gmail.com<mailto:itzsham...@gmail.com>]
Sent: Wednesday, March 30, 2016 10:36 AM
To: openstack-operators; 
commun...@lists.openstack.org<mailto:commun...@lists.openstack.org>; 
user-commit...@lists.openstack.org<mailto:user-commit...@lists.openstack.org>
Subject: Re: [User-committee] Announcing the Non-ATC Recognition Working Group

Hi everyone,

Friendly reminder:  The doodle poll[1] for the Non-ATC recognition WG meeting 
time will be closing at March 31st, 2100 UTC (tomorrow).

Please vote if you plan to join us!

[1] http://doodle.com/poll/7r5khrefyx7wysi4

Thanks,
Shamail

On Mon, Mar 28, 2016 at 3:33 PM, Shamail Tahir 
<itzsham...@gmail.com<mailto:itzsham...@gmail.com>> wrote:
Hi everyone,

We had some great discussion on the mailing lists on how to recognize operators 
and other contributors in the OpenStack community who don't qualify for ATC 
(Active Technical Contributor) status earlier this month[1].  We revisited this 
topic at the last User Committee meeting[2] and decided to start a short-term 
working group with one objective: to help define the User Committee 
constituency.  This will help us determine who should be included in the {not 
yet named} contributor program by the User Committee and how to qualify.

Maish and I volunteered to help start the conversations, document the 
decisions, and provide updates on the outcome to the User Committee.  We have 
created a wiki[3] for this new working group (which will be disbanded once we 
have reached our objective) and there is an active doodle poll[4] to determine 
the time for our weekly meeting, which will be held in an IRC channel.  The 
poll shows the start dates as this week but the please just vote for the 
day/time (not date) since we will not begin our meeting until next week (week 
of 4/4).

Please volunteer if you want to help us develop the membership definition for 
this new designation.  The user committee will have a lot more work ahead of 
them to fully build out a new charter and/or program but this activity will be 
extremely helpful as a foundational building block.

[1] http://lists.openstack.org/pipermail/community/2016-March/001422.html
[2] http://eavesdrop.openstack.org/meetings/uc/2016/uc.2016-03-14-19.00.log.html
[3] https://wiki.openstack.org/wiki/NonATCRecognition
[4] http://doodle.com/poll/7r5khrefyx7wysi4

--
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time




--
Thanks,
Shamail Tahir
t: @ShamailXD
tz: Eastern Time
_______________________________________________
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to