Team,

We successfully released VNFSDK as part of Amsterdam yesterday. Congratulations!

Instead of a meeting today, I’d like to start discussion through email on 
several topics:

·        committer promotion(s)

·        Planning for maintenance release (Amsterdam 1.0.1)

·        Planning for Beijing release

committer promotion
Several people have asked about the committer promotion process.  Essentially, 
we need to discuss promotions as a team and conduct a vote of the committers.  
Once we complete the vote, we ask the TSC to approve our decision.

3.2.2.1 Adding Committers

     *   Initial Committers for a project will be specified at project creation
     *   Committer rights for a project are earned via contribution and 
community trust. Committers for a project select and vote for new Committers 
for that project, subject to TSC approval.
     *   New Committers for a project should have a demonstrable established 
history of meritocratic contributions

I would like to open up the promotion process by soliciting criteria and 
nominations.  One source of data is bitergia, which shows code added and 
modified.
Author

Commits

Projects

Added Lines

Removed Lines

Avg. Files

Murali Mohan Murthy Potham

117

1

3,730

808,243

49.991

Harry Huang

49

1

1,265

1,346

1.245

Avinash S

35

1

10,867

700,332

120.629

Chris Donley

32

1

5,508

856

1.875

Gary Wu

11

1

6

6

0.545

GOKUL SINGARAJU

9

1

45,526

87

21.333

Jessica Wagantall

7

1

5

5

0.714

Lianhao Lu

7

1

636

55

3.857

Eric Debeau

5

1

928

939

2.4

Morgan Richomme

4

1

558

562

2













However, this does not show confluence activity or other project activities 
(such as in the vnf modeling subteam). How should we measure them to 
demonstrate “meritocratic contributions”?

Planning for maintenance release
There will be an Amsterdam maintenance release in mid-January.  While the 
criteria and process have not been published yet, I believe it’s for bug fixes 
only.  I think we’ll have a window until mid-Dec to work on highest, high, and 
medium bugs.  After mid-December, we will probably be limited to high/highest 
bugs and results of pair testing and integration testing.  We have a handful of 
medium bugs in the queue.  Aside from those, are there other things we should 
consider?

Planning for Beijing
We’ve talked about a few aspects already (image store, updating code to reflect 
the new model, etc.) .  In addition, I spoke with David Shadmi from AT&T about 
possible ways to get better alignment with SDC and VVP in Beijing.  We’d like 
to set up a joint meeting after Thanksgiving (look for something around 11/29), 
and a follow-up at the developer summit in December.   What else should we 
consider?  Please continue to circulate ideas on the wiki and via email – we’ll 
review in two weeks.

Note that next week’s meeting is also cancelled due to the Thanksgiving holiday 
in the US.

Chris

From: [email protected] 
[mailto:[email protected]] On Behalf Of Brian Hedstrom
Sent: Thursday, November 16, 2017 1:47 PM
To: onap-discuss <[email protected]>
Subject: [onap-discuss] [vnfsdk] VNF SDK Meeting tomorrow (11/17/17) is 
CANCELLED

Hi Team,
Chris would like to cancel tomorrow's meeting and hold it via email.  Look for 
an email from Chris later tonight or tomorrow.

Thanks,

--
Brian Hedstrom
Founder/CEO
OAM Technology Consulting LLC
oamtechnologyconsulting.com<http://oamtechnologyconsulting.com>
[email protected]<mailto:[email protected]>
720-470-7091
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss

Reply via email to