Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

Guys, What I see here is power struggle. We all have seen this type of things many times before, especially with strong opinion. Here are my 2 cents: (1) TSC shouldn't interfere with the internal management of a project. It will be a bad precedent for TSC to intervene a project's internal

[opnfv-tech-discuss] availability project meeting

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 15.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD END:VTIMEZONE BEGIN:VEVENT

Re: [opnfv-tech-discuss] [test-wg] Notes from OPNFV Plugfest meeting - "Testing group Euphrates collaborative work"

I have a question that we didn’t have a chance to loop back while we were in the plugfest. Did the discussion on test API’s extension on login with credentials reached a conclusion that can be implemented in time for CVP? Jose, Serena, can you give an update? Thanks. Wenjing From:

[opnfv-tech-discuss] [infra] [release] Upgrading Jenkins after Danube 2.0 Release

Hello, A recent CVE was published for Jenkins[1] necessitating an upgrade from 2.32.1 to 2.46.2. Given the 2.0 release is coming up shortly, I'd like to propose holding off on the upgrade until just after 2.0 is out. Assuming there are no delays to the release (there don't appear to be), that

Re: [opnfv-tech-discuss] [release][danube] more detailed scheduling for Danube 2.0

REMINDER.. You should be completing your testing on Tuesday (tomorrow). David On Thu, Apr 27, 2017 at 3:06 AM, David McBride wrote: > Team, > > I took an action during the TSC call this week to provide more detailed > scheduling for the Danube 2.0 release on

Re: [opnfv-tech-discuss] [release][euphrates] MS1 Intent to Participate / Release Planning - TOMORROW (Tues, May 2)

For some reason the link didn't work: CI Resource Requirements On Mon, May 1, 2017 at 2:35 PM, David McBride wrote: > I neglected one item for release planning (new for

Re: [opnfv-tech-discuss] [release][euphrates] MS1 Intent to Participate / Release Planning - TOMORROW (Tues, May 2)

I neglected one item for release planning (new for Euphrates): - Create and publish a release plan - Fill out the summary - Add your scenarios to the scenario status page

Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

I agree that getting TSC guidance in the way forward is the right next step. Tapio, Ray, Can we add in the agenda tomorrow on TSC for this topic? The committers have been discussing how to restructure the dovetail project to broaden talent pool and represent diverse community interests, but do

Re: [opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

Hi, In light of Chris's resignation and request, I would like to propose that we bring our plans to evolve the project to the TSC sooner, rather than later, and get TSC guidance on a number of key questions related to Dovetail, which is not like other projects because of its relationship to the

[opnfv-tech-discuss] [dovetail] Standing down as a committer on DoveTail

Hi Hongbo, I will be standing down as a committer on the Dovetail project. When I established the project it was intended to reflect as fairly as possible a common set of voices from all member companies that had a stake in our project. I feel that the balance in the project is not ideal

[opnfv-tech-discuss] [release][euphrates] MS1 Intent to Participate / Release Planning - TOMORROW (Tues, May 2)

Team, Euphrates MS1 is Tuesday, May 2 (5 p.m. Pacific). Please confirm that your project is on the intent-to-participate list. If your project is not listed and you are planning to participate,

[opnfv-tech-discuss] Updated Invitation: Parser Asia-Euro Meeting @ Weekly from 4:30am to 5:30am on Monday from Mon Jun 6, 2016 to Mon May 1 (EDT) (opnfv-tech-discuss@lists.opnfv.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:Asia/Shanghai X-LIC-LOCATION:Asia/Shanghai BEGIN:STANDARD TZOFFSETFROM:+0800 TZOFFSETTO:+0800 TZNAME:CST DTSTART:19700101T00 END:STANDARD END:VTIMEZONE