This task is fully on me at present. The Board formed a small work group to create a "Rationale" document explaining in more detail the reference to singularity and cohesivness in the TSC Policy document. From the last meeting of this small group, I took the action item to create a first draft of that Rationale document. I am trying to have that done and reviewed by the small group prior to the next Board meeting the first week of September so that it can be reviewed/approved at that time.
Best, Phil. On Thu, Aug 18, 2016 at 10:30 AM, Colin Dixon <[email protected]> wrote: > I think the last place this left was waiting for a response from the > board. Phil, I think that's supposed to come back at the beginning of > September per bullet 6 here: > https://meetings.opendaylight.org/opendaylight-meeting/2016/ > tsc/opendaylight-meeting-tsc.2016-08-04-17.00.html > > --Colin > > > On Tue, Jun 28, 2016 at 5:15 PM, Robert Varga <[email protected]> wrote: > >> On 06/23/2016 06:57 PM, Edward Warnicke wrote: >> > Further, in my mind, if you are a core project you should be able to >> > tolerate competition... if you cannot, you are either *not* core, or you >> > are in some way failing to serve the community. It is *only* when a >> > core project is failing to serve the community that competition is >> > threatening, and that is *precisely* when it is needed. >> >> I agree with this point. This problem will get worse as projects with >> broad scope become core. I do not think we would be where we are if the >> controller, as originally proposed, were a core project. >> >> Bye, >> Robert >> >> > > _______________________________________________ > TSC mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/tsc > > -- Phil Robb Sr. Director Of Technical Operations OpenDaylight Project (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
