Committer Promotion Request for Documentation Project

INSTRUCTIONS

Instruction for adding a new committer to a repo:

  • MAKE A COPY OF THIS TEMPLATE AND MOVE IT UNDER YOUR OWN PROJECT PAGE HIERARCHY.

  • EDIT THE PAGE ACCORDINGLY, PROVIDING THE LINKS AND INFORMATION REQUESTED.

  • SEND AN EMAIL TO THE ONAP INFRASTRUCTURE COORDINATOR (@Gildas Lanilis Gmail) CONTAINING A LINK TO THIS COMPLETED PAGE WITH THE SUBJECT: COMMITTER PROMOTION REQUEST FOR [YOUR-PROJECT-TAG]

  • THE ONAP INFRASTRUCTURE COORDINATOR REVIEWS THE COMPLETENESS AND ACCURACY OF THE EVIDENCES, AND UPDATE THE Resources and Repositories (Deprecated) INFORMATION.

  • THE ONAP INFRASTRUCTURE COORDINATOR FOLLOWS UP WITH LINUX FOUNDATION FOR EXECUTION.



Contributor's Name: 

@Eric Debeau

Contributor's LFID:  eric.debeau

Link(s) demonstrating the Contributor's established history of meritocratic contributions to the project: 

Gerrit Owner code submission

Gerrit Reviewed by

JIRA Reporter

JIRA Assignee

Wiki Activities

List of current Committers (as documented here: Resources and Repositories (Deprecated) )

Committers





Active Last 6 months?

Recommendation



Rich Bennett

rb2745@att.com

Yes

Keep



Nicholas Hu

jh245g@att.com

Yes

Keep



Timo Perala

timo.perala@nokia.com

Yes

Keep



Greg Glover

gg2147@att.com

Yes

Keep



Kevin Scaggs

ks0567@att.com

No

Remove



Steven Wright

sw3588@att.com

Yes

Keep



James Yang

james.yangliu@huawei.com

Yes

Keep



Shasha Guo

guoshasha@chinamobile.com

No

Remove



Ying Li

liyingyjy@chinamobile.com

No

Remove



Lili Kong

konglili@chinamobile.com

No

Remove



Link documenting the existing Committers voting in favor of promoting the Contributor:  
Examples include project team meeting minutes, archived mailing list threads or email threads uploaded as an attachment to the wiki

Eric has provided both critical thought leadership in the Beijing release to improve ONAP documentation in general, as well as a lot of "in the trenches" work to clean up existing errors, warnings, etc. Specifically he has:

  1. Driven vision on End to End Installation Guides. Has been pushing best ways to present E2E views for both OOM and Use Case perspectives

  2. Provided input on API Documentation & Versioning strategy

  3. Provided critical support on Doc Tool Chain improvements

  4. Provided ongoing technical expertise on managing all the doc repos; Eric will be another important "go to" resource in addition to key committers like like Rich Bennett



Repositories the new Committer should be granted permissions to: 

  1. DOC

  2. DOCTOOLS