MRI projects are now integrated for this release. Please note that the full distribution is currently

We are not using it for the TSC and TWS meetings - but it’s very possible that the projects may be using it. We can discuss it at the TSC meetings but also over the mailing lists.

Hi, Andy. I look forward to community feedback. I've also made this a topic for our next TSC meeting. Best, Casey Cain Technical Program Manager / Community Architect Linux

Greetings folks, We're working on migrating the couple of instances of meetbot we have running to new infrastructure. What I would like to know is if anyone in the community is actually still using

Hi folks, Please note this Monday, April 27, the TWS session will be about Transport PCE. The TWS session zoom details are as follows: https://wiki.lfnetworking.org/display/ODL/TWS Meeting time:

Hello, gerrit seems to be down (i.e. reports a 504), filed https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-19523 for that. Bye, Robert

Hi folks, As decided in the last TSC meeting, the ODL TSC meeting of April 23 has been cancelled to let ODL community members to participate in the online LFN April Technical Meeting sessions. For

Hello TSC members, Please vote on the project approval here: https://wiki.lfnetworking.org/x/fAgQAg The project is contemplating changing the name to be a slight variation of the original proposed

Hello TSC and all We are going to code freeze Magnesium for all Managed Projects ( cut and lock release branches ) on Monday April 27th at 10 am pst so we can release SR1 on May 4th. Please let us

Please note this session is planned for Monday 9 am Pacific Time / 9:30 pm IST / 6 pm CET.

The OpenFlow Plugin project page needs to be updated. :) Best, Casey Cain Technical Program Manager / Community Architect Linux Foundation _________________ IRC: CaseyLF WeChat: okaru6 Voice:

This is all great for those of us already receiving emails and paying attention, but if you are new to OpenDaylight and want to get the attention of say, openflowplugin (as an

Yes - actually I was in favor of that alternative. However since it had already passed with only 2 lists instead of 3 or 4, I decided to skip that particular vote :). We can talk about it in the TSC

In advance of this change, I put in the Project template on the wiki to indicate either app-dev or kernel-dev. As Projects migrate to the new wiki, if they use the template that I provided, they

Hi, Jamo. I sent out the mapping of mailing lists as part of the migration. Currently, projects that are considered "Kernel" are all forwarded to kernel-dev. All other mailing lists (not including

I do not know if it too late for this but I also think it would have been better to separate in kernel, plugins and apps.

I agree with you. It should be there somewhere central. It should be also on each project’s wiki.

Yeah, I can look up the old emails too. My question comes from the POV of a new person and how they are supposed to know where to send an email? Thanks, JamO

Jamo, In the email below are listed the projects in the kernel mailing list. The remaining projects should be in the app-dev mailing list. Abhijit ---------- Forwarded message --------- From: Casey

Casey, Where can I find the mapping of projects to which new email list I should be sending to? Like, which projects are in the kernel-dev vs app-dev lists? Also, can we edit the info on this page