Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

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 information.

  • The ONAP Infrastructure Coordinator follows up with Linux Foundation for execution.



Contributor's Name: Steve Smokowski

Contributor's LFID:  ss835w@att.com

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


Steve was a member of the architecture team who designed and implemented the AT&T Service Orchestrator seed code.


In 2015 he joined the A&AI project and supervised a major restructuring of the implementation


Since 2017 he has been back, serving as a technical team leader for Service Orchestrator inside AT&T as well as in the ONAP community.  In this role, he has been responsible for the oversight of all Service Orchestrator features contributed by AT&T.


Steve also made important feature code contributions in the Beijing and Casablanca releases, particularly in the areas of refactoring and optimization, including: building blocks (Beijing), java delegates and client libraries (Beijing), and application containerization (Casablanca).


He has broad knowledge of the ONAP infrastructure and of software development best practices.


Steve would be a great asset to SO as a committer.  Currently, AT&T has only one committer since John Choma's retirement.


Below are Steve's contributions :

Steve Smokowski:


Merged Commits: 

https://gerrit.onap.org/r/#/q/owner:ss835w%2540att.com+status:merged+project:so


Reviewed Commits:

https://gerrit.onap.org/r/#/q/project:so+status:merged+reviewer:%22Steve+Smokowski+%253Css835w%2540att.com%253E%22


Jira handled:

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

 



Contributor's Name: subhash

Contributor's LFIDsubhash

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


Subhash has been contributing to ONAP SO since Beijing release and have made some significant contributions towards the VoLTE and CCVPN usecases.

He is also active member of ONAP and committer in ONAP CLI project.

Apart form ONAP Subhash has also worked in ODL and openstack projects and have significant hands-on experience in developing telecos applications.

He would definitely be a good asset to the SO project based on his skill set and past experiences.

Contributions:

Merged Commits:

https://gerrit.onap.org/r/#/q/owner:%22subhash+kumar+singh+%253Csubhash.kumar.singh%2540huawei.com%253E%22+project:so+status:merged


Reviewed Commits:

https://gerrit.onap.org/r/#/q/project:so+status:merged+reviewer:%22subhash+kumar+singh+%253Csubhash.kumar.singh%2540huawei.com%253E%22


Jira Handled

type key summary assignee reporter priority status resolution created updated due
Loading...
Refresh




Contributor's Name: Lukasz Muszkieta

Contributor's LFIDlukasz.muszkieta@nokia.com

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

I have a pleasure to nominate myself as ONAP SO committer. I am a Java Developer in the Nokia team that deals with SO. I have been working in SO since one year, so I got quite enough experience with SO to be a reviewer. 
Currently in Nokia team we have a situation that nobody has committer right, so it makes review process longer that it should be, because discussions related to comments are asynchronous. If we have committer inside the team, any review comments can be discussed on the place, so the commitment process is faster.

During review I pay attention to clean code and optimisation and I never try to persuade committer to use my code style. I always write comments to make them clean for committer, to avoid unnecessary discussion. 

Contributions:

Merged Commits:

https://gerrit.onap.org/r/#/q/owner:lukasz.muszkieta%2540nokia.com+status:merged+project:so

Reviewed Commits:

https://gerrit.onap.org/r/#/q/project:so+status:merged+reviewer:%22Lukasz+Muszkieta+%253Clukasz.muszkieta%2540nokia.com%253E%22

JIRA Handled:

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh


Civs Poll has been rolled out to the current active committers:

https://civs.cs.cornell.edu/cgi-bin/vote.pl?id=E_73e2a2a8f6134ec2&key=cb6bdb8e4128bfd1

Results would be published once the voting is completed.


Repositories the new Committer should be granted permissions to:
 

https://gerrit.onap.org/r/#/admin/projects/?filter=so

  • No labels