[User-committee] Non ATC contribution recognition

Shamail itzshamail at gmail.com
Mon Mar 28 15:48:01 UTC 2016


Hi Tim,

The Non-ATC WG was/is being formed per the last User Committee meeting.  I was about to send an email today to announce it and ask for volunteers.  

I do agree that the topic that is outlined below and the objective of the Non-ATC recognition WG is the same.  Our plan was to have community members discuss the roles/ activities that are eligible, what to measure the activity, and how to measure it through a community WG effort.

Thanks,
Shamail 

> On Mar 28, 2016, at 10:04 AM, Tim Bell <Tim.Bell at cern.ch> wrote:
> 
> 
> I notice in the draft agenda for the OpenStack foundation board meeting [1] next week there is an item regarding the non ATC contributions due at 10:20.
> 
> The criteria being proposed are as follows but this would seem to be pre-empting the discussions due in the non-ATC recognition working group [2].
> 
> Has there been any discussion with the user committee or this working group on these proposals ?
> 
> [1] https://wiki.openstack.org/wiki/Governance/Foundation/29Mar2016BoardMeeting
> [2] https://wiki.openstack.org/wiki/NonATCRecognition
> 
> Tim
> —————
> 
> 
> (10:20) Proposal to increase awareness of and reward other community contributors - Allison, Paul
> *Summary*
> In light of the many individuals who are contributing their time and effort to build a vibrant OpenStack community, we are asking for the OpenStack Foundation Board’s support to increase awareness of and reward other community contributors in the same way we reward technical contributors. We want to appropriately identify community leaders who advance the objectives of the OpenStack Community and reinforce the vibrant community that continues to evolve through the amazing efforts around the world from all the great leaders, technical or not. These community leaders should be invited to have a free pass to the Summit and be designated as an active community contributor (“ACC”) similar to an active technical contributor (“ATC”).
> *Criteria*
> 
> Must be a registered member of the OpenStack community as a “Foundation Member”
> Must specify their level of community involvement under “other” on OpenStack profile page [1]
> Must have performed at least one of the following activities:
> Organized at least 3 OpenStack community meetups within the last cycle (as documented and validated by Meetup.com)
> Organized at least 3 OpenStack community events or 1 mid-cycle event for the latest release (as validated by Meetup.com or public event data)
> Organized at least 1 significant community event at the Summit (e.g. core reviewer event, community party, etc.)
> Actively participated in at least 10 meetings for OpenStack non-coding working groups (validated by agenda roll calls on the Etherpads)
> Submitted at least 10 defects within the last cycle (as documented in Stackalytics data)
> Authored OpenStack knowledge sharing/training materials/special documentation outside the OpenStack Documentation project (ACC status is not granted for contributions that would already merit ATC status)
> As an alternative option, people could nominate themselves, write a short description as to why they are a community contributor, and get a few people from the community they are serving or a Board member to validate their contributions
> 
> *Endnotes:*
> [1] To facilitate this, the OpenStack Foundation should change the User Profile page to include ways other than “projects” that people can use to document their contributions. Right now, the profile pages are only focused on code contributors but could even provide a few more community-oriented check boxes in that section
> 
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160328/4681335a/attachment-0001.html>


More information about the User-committee mailing list