|
Re: 答复: Re: 答复: Re: BIER_APP project requests for creation review
xiong.quan@...
Hi Colin, Thank you for the schedule arrangement. The meeting time is good for us. I will finish and upload the presentation slides as soon as possible before the meeting. Best Regards, Xiong 熊泉 xiongquan 软件工程师 Software Engineer
原始邮件 发件人： <colin@...>; 收件人：熊泉00091065; 抄送人： <project-proposals@...>; <an.ho@...>;宦林英10042773;喻敬海10005643;高陈强10202383; <bier-dev@...>; 日 期 ：2017年06月09日 23:53 主 题 ：Re: 答复: Re: [Project-proposals] BIER_APP project requests for creation review Understood. The next regularly scheduled TSC meeting after the two-week public review period is 6/22, which is actually the Asia-friendly TSC call time too, which is probably good. Does that time work for you? It would be this: https://www.timeanddate.com/ You can read through some advice on creation reviews here: Cheers, --Colin On Thu, Jun 8, 2017 at 9:29 PM, <xiong.quan@...> wrote:
|
||||||
|
|
||||||
|
Re: 答复: Re: BIER_APP project requests for creation review
Colin Dixon
Understood. The next regularly scheduled TSC meeting after the two-week public review period is 6/22, which is actually the Asia-friendly TSC call time too, which is probably good. Does that time work for you? It would be this: https://www.timeanddate.com/ You can read through some advice on creation reviews here: Cheers, --Colin On Thu, Jun 8, 2017 at 9:29 PM, <xiong.quan@...> wrote:
|
||||||
|
|
||||||
|
Re: P4Plugin Proposal
Colin Dixon
Understood. The next regularly scheduled TSC meeting after the two-week public review period is 6/22, which is actually the Asia-friendly TSC call time too, which is probably good. Does that time work for you? It would be this: https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=6&day=22&hour=3&min=30&sec=0&p1=771&p2=33&p3=248&p4=283&p5=263&p6=37 You can read through some advice on creation reviews here: --Colin On Thu, Jun 8, 2017 at 9:20 PM, <ding.rui@...> wrote:
|
||||||
|
|
||||||
|
Re: 答复: Re: BIER_APP project requests for creation review
xiong.quan@...
Hi Colin, Thank you for the reply! The details are as follows. ) Do you actually want to participate in Nitrogen, it will be a very fast release with API freeze (including support for Karaf 4) being 7/14 at the latest and code freeze being 8/14 at the latest? Alternately, you could wait and participate in Oxygen which is targeting at 3/7/2018 release. Xiong RE: BIER_APP project still plans to participate in Nitrogen and there is no problem with the plan time, cause we have finished the work partly and I believe we can catch up with the shedule. 2.) Does this actually need to be a a new project or does it make sense to have it as a part of the bier project. In general, I applaud the idea that the pure plugin and the applications that use that plugin should be kept separate, but we've found that often this results in tightly-linked changes between the two and it's easier (at least at first) to keep them separate. That being said, if you feel strongly about having two projects, we can have a creation review. Xiong RE: We still want to separate the BIER plugin and applications and do our best to guarantee the independence between the two projects. Best Regards, Xiong 熊泉 xiongquan 软件工程师 Software Engineer
原始邮件 发件人： ＜colin@...＞; 收件人：熊泉00091065; 抄送人： ＜project-proposals@...＞; ＜an.ho@...＞;宦林英10042773;喻敬海10005643;高陈强10202383; ＜bier-dev@...＞; 日 期 ：2017年06月08日 22:23 主 题 ：Re: [Project-proposals] BIER_APP project requests for creation review Thanks for the request. Two quick questions: 1.) Do you actually want to participate in Nitrogen, it will be a very fast release with API freeze (including support for Karaf 4) being 7/14 at the latest and code freeze being 8/14 at the latest? Alternately, you could wait and participate in Oxygen which is targeting at 3/7/2018 release. 2.) Does this actually need to be a a new project or does it make sense to have it as a part of the bier project. In general, I applaud the idea that the pure plugin and the applications that use that plugin should be kept separate, but we've found that often this results in tightly-linked changes between the two and it's easier (at least at first) to keep them separate. That being said, if you feel strongly about having two projects, we can have a creation review. Cheers, --Colin On Tue, Jun 6, 2017 at 10:19 PM, ＜xiong.quan@...＞ wrote:
|
||||||
|
|
||||||
|
Re: P4Plugin Proposal
ding.rui@...
Thank you for your reply, we have discussed the release schedule of this project, considering the deadline of Nitrogen release, we decide to participate in the Oxygen release, but we want the project to be formally approved by the TSC as soon as possible. 原始邮件 发件人： ＜colin@...＞; 收件人：丁瑞10106591; 抄送人： ＜project-proposals@...＞; 日 期 ：2017年06月08日 22:18 主 题 ：Re: [Project-proposals] P4Plugin Proposal Thank you for the proposal. Is the intent for this to participate in the (short) Nitrogen release ending on 9/7/2017. See: If so, this is going to be a pretty whirlwind tour of getting a release done. API freeze including support for Karaf 4 will be no later than 7/14 and code freeze will be no later than 8/14. The alternative is to participate in the Oxygen release, which will target a 3/7/2018 release. --Colin On Sun, Jun 4, 2017 at 9:01 PM, ＜ding.rui@...＞ wrote:
|
||||||
|
|
||||||
|
Re: BIER_APP project requests for creation review
Colin Dixon
Thanks for the request. Two quick questions: 1.) Do you actually want to participate in Nitrogen, it will be a very fast release with API freeze (including support for Karaf 4) being 7/14 at the latest and code freeze being 8/14 at the latest? Alternately, you could wait and participate in Oxygen which is targeting at 3/7/2018 release. 2.) Does this actually need to be a a new project or does it make sense to have it as a part of the bier project. In general, I applaud the idea that the pure plugin and the applications that use that plugin should be kept separate, but we've found that often this results in tightly-linked changes between the two and it's easier (at least at first) to keep them separate. That being said, if you feel strongly about having two projects, we can have a creation review. Cheers, --Colin On Tue, Jun 6, 2017 at 10:19 PM, <xiong.quan@...> wrote:
|
||||||
|
|
||||||
|
Re: [opendaylight-dev] [Reminder] Date for Project Proposals
Colin Dixon
I've given the P4 plugin proposal roughly that advice. --Colin On Mon, Jun 5, 2017 at 12:02 PM, Thanh Ha <thanh.ha@...> wrote:
|
||||||
|
|
||||||
|
Re: P4Plugin Proposal
Colin Dixon
Thank you for the proposal. Is the intent for this to participate in the (short) Nitrogen release ending on 9/7/2017. See: If so, this is going to be a pretty whirlwind tour of getting a release done. API freeze including support for Karaf 4 will be no later than 7/14 and code freeze will be no later than 8/14. The alternative is to participate in the Oxygen release, which will target a 3/7/2018 release. --Colin On Sun, Jun 4, 2017 at 9:01 PM, <ding.rui@...> wrote:
|
||||||
|
|
||||||
|
BIER_APP project requests for creation review
xiong.quan@...
Hi An Ho, BIER_APP project requests for creation review and plans to participate in Nitrogen release. Project proposal have been provided as follows and I have added the wiki link in the New Pending Creation Review list. https://wiki.opendaylight.org/view/Project_Proposals:BIER_APP Please reply to me about the review meeitng shedule and what I should prepare. Best Regards, Xiong
熊泉 xiongquan 软件工程师 Software Engineer
|
||||||
|
|
||||||
|
Re: [opendaylight-dev] [Reminder] Date for Project Proposals
Thanh Ha <thanh.ha@...>
Agreed, I think 2 months is too short a time to integration a new project into a simultaneous release, plus the Karaf 4 migration is our current focus. We should encourage proposals and if approved make it for Oxygen instead. Regards, Thanh On Fri, Jun 2, 2017 at 7:27 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
|
||||||
|
|
||||||
|
P4Plugin Proposal
ding.rui@...
Hi, everyone, I creat a new project proposal which is about P4 technology. Please review it. Thanks. https://wiki.opendaylight.org/view/Project_Proposals:P4_Plugin |
||||||
|
|
||||||
|
Re: [Reminder] Date for Project Proposals
Abhijit Kumbhare
Just my 2 cents (not an official position unless agreed/voted on by the TSC): I think we should allow & encourage project proposals to be sent - however I think it makes the most sense to not allow new projects join the Nitrogen release as it is a short two month cycle. They can of course get a project approved - get the tooling in place so that they can join in the Oxygen release. On Fri, Jun 2, 2017 at 3:28 PM, An Ho <An.Ho@...> wrote:
|
||||||
|
|
||||||
|
[Reminder] Date for Project Proposals
an.ho@huawei.com
We kindly remind prospective teams of the latest date a project proposal can be sent to the project-proposals list and still have the required two week public comment period before its project creation review. Project proposals submitted after this date will not be able to become formal projects unless granted exception, as per the tentative Nitrogen Simultaneous Release Plan.
Offset 0: 6/14/2017 Offset 1: 6/21/2017 Offset 2: 6/28/2017
Best Regards, An Ho
[1] https://wiki.opendaylight.org/view/Simultaneous_Release:Nitrogen_Release_Plan#Schedule
|
||||||
|
|
||||||
|
Re: TL1 for Opendaylight Proposal
Colin Dixon
Can you create this as a wiki page on the wiki so it's easier for people to see and review? --ColinOn Tue, Mar 14, 2017 at 11:36 PM, Ahmed Waqas <awaqas2013@...> wrote:
|
||||||
|
|
||||||
|
TL1 for Opendaylight Proposal
Ahmed Waqas <awaqas2013@...>
Respected Mam/Sir, Please find the attached proposal for Transaction language 1 protocol plugin in Opendaylight. Thanks & Regards, Ahmed Waqas Nasir. Namal College, Mianwali, Pakistan. An Associated College of Bradford University, UK |
||||||
|
|
||||||
|
Re: Creation Review Request for FPC Agent Project proposal
Bertz, Lyle T [CTO] <Lyle.T.Bertz@...>
Yes! Looking forward to it!
From: Colin Dixon [mailto:colin@...]
Sent: Thursday, February 02, 2017 8:52 AM To: Bertz, Lyle T [CTO] <Lyle.T.Bertz@...> Cc: Phil Robb <probb@...>; project-proposals@...; Vijayan, Vivek [CTO] <Vivek.2.Vijayan@...> Subject: Re: [Project-proposals] Creation Review Request for FPC Agent Project proposal
Just to confirm, you'll dial in today (in about 3 hours)? --Colin
On Mon, Jan 30, 2017 at 4:15 PM, Bertz, Lyle T [CTO] <Lyle.T.Bertz@...> wrote:
|
||||||
|
|
||||||
|
Re: Creation Review Request for FPC Agent Project proposal
Colin Dixon
Just to confirm, you'll dial in today (in about 3 hours)? --ColinOn Mon, Jan 30, 2017 at 4:15 PM, Bertz, Lyle T [CTO] <Lyle.T.Bertz@...> wrote:
|
||||||
|
|
||||||
|
Re: Creation Review Request for FPC Agent Project proposal
Bertz, Lyle T [CTO] <Lyle.T.Bertz@...>
Colin,
Lyle
From: Colin Dixon [mailto:colin@...]
Sent: Friday, January 27, 2017 9:45 AM To: Bertz, Lyle T [CTO] <Lyle.T.Bertz@...> Cc: Phil Robb <probb@...>; project-proposals@...; Vijayan, Vivek [CTO] <Vivek.2.Vijayan@...> Subject: Re: [Project-proposals] Creation Review Request for FPC Agent Project proposal
I've let this drop so far and I apologize for that. The next step is to schedule a creation review during a TSC call. There's a two-week public comment period that you've already been through, so this could be scheduled as early as next week. The TSC calls are normally at 10a pacific on Thursdays. More information is here: Would you be ready to present and answer questions or 10-20 minutes on Thursday, February 2nd sometime between 10a and 11a pacific? If a later week works better, let us know too.
Cheers, --Colin
On Tue, Jan 10, 2017 at 9:17 AM, Bertz, Lyle T [CTO] <Lyle.T.Bertz@...> wrote:
|
||||||
|
|
||||||
|
Re: Creation Review Request for FPC Agent Project proposal
Colin Dixon
I've let this drop so far and I apologize for that. The next step is to schedule a creation review during a TSC call. There's a two-week public comment period that you've already been through, so this could be scheduled as early as next week. The TSC calls are normally at 10a pacific on Thursdays. More information is here: https://wiki.opendaylight.org/view/Project_Proposals:Main#Guidelines_for_Creation_Review Would you be ready to present and answer questions or 10-20 minutes on Thursday, February 2nd sometime between 10a and 11a pacific? If a later week works better, let us know too. Cheers, --ColinOn Tue, Jan 10, 2017 at 9:17 AM, Bertz, Lyle T [CTO] <Lyle.T.Bertz@...> wrote:
|
||||||
|
|
||||||
|
Re: Creation Review Request for FPC Agent Project proposal
Bertz, Lyle T [CTO] <Lyle.T.Bertz@...>
Phil,
Thanks.
I’ll send you a tarball (if it fits in my mail system ;) ) – we are running the code through CheckMarx tool hopefully today and hopefully won’t have updates for a few weeks.
On a side note, all code is copyright 2016 as we have made no changes in 2017 but I am sure that will change shortly.
Is it ODL policy to blanket upgrade copyright (all files) to the same notice? If so, we can make the copyright change now.
Lyle
From: Phil Robb [mailto:probb@...]
Sent: Monday, January 09, 2017 6:40 PM To: Bertz, Lyle T [CTO] <Lyle.T.Bertz@...> Cc: project-proposals@...; Vijayan, Vivek [CTO] <Vivek.2.Vijayan@...> Subject: Re: [Project-proposals] Creation Review Request for FPC Agent Project proposal
Hi Lyle, that's great to hear.
Note that the proposal needs to be in existence for 2 weeks to allow public review before you request a Creation Review with the TSC.
To avoid any additional delay, you can send me a tarball of the code you expect to contribute prior to the creation review. I'll scan & review it for license information to ensure it adheres to our Inbound Code Policy [0].
Best,
Phil.
On Mon, Jan 9, 2017 at 2:52 PM, Bertz, Lyle T [CTO] <Lyle.T.Bertz@...> wrote:
-- Phil Robb Sr. Director Of Networking Solutions The Linux Foundation (O) 970-229-5949 (M) 970-420-4292 Skype: Phil.Robb |
||||||
|
|
