AUCRecognition

AUC (Active User Contributor) Recognition Working Group
Status: Disbanded (as of December 6th, 2016)

User Committee Members: Edgar Magana, Jon Proulx, Shilla Saebi Working Group Organizers: Shamail Tahir (irc: shamail), Maish Saidel-Keesing (irc: maishsk)

Scope
This working group was created to assist the User Committee (UC) define its constituency in a manner similar to how the Technical Committee (TC) has defined the designation of Active Technical Contributors (ATC)/Active Project Contributors (APC) for participants eligible to participate in the electoral process for Project Team Leads (PTL) and Technical Committee members. The User Committee formally started conversations to recognize contributions inside the OpenStack community that are out of scope for the ATC designation. The scope for this new designation is currently being refined but the intent is to recognize OpenStack community contributors (such as operators) that are not committing code to an OpenStack TC sanctioned project. OpenStack community contributions such as code contributions to repositories under User Committee governance (e.g. OSOps, ops-tags, etc.), active participation in any User Committee working group (e.g. API-WG, Enterprise-WG, Product-WG, etc.), moderating sessions at OpenStack Ops-meetups, organizing OpenStack user group meet-ups across the world, and many other forms of contributions are currently being considered for inclusion in the formal definition of the User Committee constituency. Please see the email from Edgar Magana (User Committee member) and logs from the March 14th, 2016 User Committee IRC meeting for more information.

Duration
Please note that this working group was formed in March 2016 as a "working team" to achieve the specific goal of helping define the formal definition for "User Committee constituency" (e.g. identify people who would be eligible for the designation selected by the User Committee similar to what ATC is for the Technical Committee). Once this working team has met its objective, it will be disbanded. This is a high-priority need and therefore we anticipate making progress against our objective within weeks to months (at the most).

Meeting Information
There are no future meetings.

Approach

 * Members met regularly using an OpenStack meeting channel on IRC
 * We provided periodic updates to the User Committee (at least once a month) of our progress
 * The working group sent an email to the OpenStack user committee and operators mailing lists as milestones were achieved to solicit feedback from the affected OpenStack community members
 * The team provided a final read-out to the User Committee once our objective has been completed. The User Committee will relay the outcome and next steps to the broader OpenStack Community.