Hi An, apologies for late answer. As per [1] and [2] the project openflowjava will be absorbed by project openflowplugin during Nitrogen release. Based on that openflowjava project intends to drop

+1 Congratulations, we've got 3 out of 4. Hereby I pronounce openflowjava project to be destined for archive state. -- Michal Rehák Software developer Pantheon Technologies s.r.o. Mlynské Nivy

Hi Michal, I agree. +1 for me. Michal Polkorab 2017-06-29 9:59 GMT+02:00 Jozef Bacigál <jozef.bacigal@...>:

+1 Jozef Od: Michal Rehák <michal.rehak@...> Odoslané: štvrtok, 29. júna 2017 9:54:48 Komu: openflowjava-dev@... Predmet: [openflowjava-dev] Committers vote for archiving openflowjava project

Hi openflowjava committers, based on intend of openflowplugin project to adopt codebase of openflowjava [1] - which I agree with - let me start voting formoving openflowjava project into archive

Hi all, unfortunately the deadline for answer regarding Nitrogen participation is in 2 days. Based on openflowplugin communication and weather page [3] I presume that the decision to adopt codebase

Thanks Andy! Hopefully Sam can also make it.

Abhijit, Yes I can join this coming week. -Andy- -- Andrew J Grimberg Lead, IT Release Engineering The Linux Foundation

I talked with Jozef and Tomas right now - and we think it will be good to discuss this in the Monday OpenFlow Plugin meeting this process (steps provided by Andy, the process followed by Sam/NetVirt

OpenflowJava/Plugin devs, I believe openflowjava would still be adding patch to enable in integration/distribution as part of Karaf4 migration, before this merge? I didn't see any patch yet so wanted

I would guess so. It also means we need to figure out something like a Termination Review process or something... Any ideas? Regards, Robert

As an aside, I'm assuming this means openflowjava will not participate in nitrogen. Is that right? --Colin

Perfect :) Ed

Agree with you Ed about having a vote in OpenFlow Java committer community - and in general the TSC role if we plan to archive. Had planned on that based on how we have decided to proceed (based on

So looks like we don't need a TSC approval for this merge. Only committers needs to agree on it. Though it's good to have an official vote from openflowjava committer about this merger. So i think

Just for a my clarity, merging these two project won't require TSC approval and permission from the openflowjava project PTL/Committer? I think we have the latter, but not the first if requires. --

Hi Michal, these conflicts can be resolved by using git subtree instead of git merge, as subtree can "merge" repository/branch into subdirectory. I prepared this OpenFlowJava merge in 3 patches,

Yes please open a helpdesk ticket for this. I see 2 routes we can go from there: 1) Ask LF to do it 2) LF gives committers temporary push permissions and they can do it themselves I think 1) might

Abhijit, This strikes me as good news overall. It might be a good idea to get a vote from the OpenflowJava Committers, particularly as they will need to vote to archive the openflowjava

Hi all, merging ofjava with ofplugin yields some conflicts: Conflicts: .gitignore .gitreview artifacts/pom.xml parent/pom.xml pom.xml .git* and