What was the reasoning not to absorb liblldp into the openflow project? Because lldp isn't part of openflow? That makes sense and I don't think we will find a project as this really is it's own protocol.
For the sake of finding a good place to park it, though, ofp is a good project since ofp uses the lib and genius and netvirt use ofp. If not, what was the consensus on if we could reduce the process requirements for making this it's own project? Could we just make the project and let it automatically get pass on the milestones? Make it such that we only have the startup costs to migrate it to a project, get it building and leave it on auto-pilot. On Thu, Jul 13, 2017 at 2:25 PM, Sam Hague <sha...@redhat.com> wrote: > > > On Thu, Jul 13, 2017 at 1:09 PM, Robert Varga <n...@hq.sk> wrote: > >> Hello everyone, >> >> controller is hosting liblldp.jar, but it is not part of >> controller-published features nor is it actively maintained. >> >> As part of cleaning up the controller project, we would like to have >> this library removed from the controller and maintained somewhere else. >> >> Since the following projects are referencing it in their pom.xmls: >> ofp, gbp, atrium, netvirt, nemo, nic, genius >> >> and the following projects are spelling it out in their features: >> genius, netvirt, ofp >> > genius and netvirt pull from ofp (as well as the other projects) so would > it make most sense to put in in ofp? Or if only genius and netvirt use it > then genius would make more sense since netvirt pulls from genius. > > Or as a separate project, is there any lightweight process for a project - > like add the new project for liblldp and then let netvirt or genius cover > it in their project status? > >> >> I think it would be appropriate to either have it split off from the >> controller into its own project, or it needs to be absorbed into one of >> the projects actually using it. >> >> Are there any volunteers willing to take ownership of it? >> >> Thanks, >> Robert >> >> >> _______________________________________________ >> openflowplugin-dev mailing list >> openflowplugin-dev@lists.opendaylight.org >> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev >> >> >
_______________________________________________ openflowplugin-dev mailing list openflowplugin-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
