On Tue, May 7, 2013 at 4:15 AM, Markus S= tenberg <markus.stenberg@iki.fi> wrote:

Dave Taht <dave.taht <at> gmail.com> writes:
> I note that in order to speed up the cycle and development time
> involving routing advancements, the openwrt team has broken out most > of the routing protocols in openwrt into a separate repository which > can spin faster:
>
> https://github.com/openwrt-routing/packages
>
> Perhaps this could be a home for the enhancements to bird/etc that the=
> cisco homenet group has been doing?

Possibly. I'm not sure how keen they are to have 'big' ch= anges,
though, and looking at
h= ttps://github.com/fingon/hnet-openwrt-feed Cisco homenet
implementation requires currently 4 new Lua modules (1 of them
forked version of original with better IPv6 support), forked
versions of dnsmasq/odhcp6c (for prefix class option support),
and BIRD (for external LSA support).

Unless you wi= sh to maintain these modifications forever, it is helpful to seek consensus= with the mainline developers of these tools to push your patches in a mutu= ally acceptible form. I would suspect that dnsmasq and odhcp6c devs would b= e amiable to a discussion at the very least.

=A0

As it's not very self-contained, I'm not sure how well it would
work there, and as we currently _only_ work with AA base, it
might have issues with people using trunk..

Perfec= t! You can continue have your stable release and also establish a repo(s) f= or moving them into the ongoing development processes for head of trunk, so= that these standards can be more widely adopted. Or not, depending on cons= ensus with the devs....

=A0Please post your patches to the relevant mailing lists. This is the = open source process. It's pretty similar to the ietf process of seeking= consensus except that it's incremental and the code needs to compile a= t every stage.

You end up with a lot of eyeballs on the code and more feedback from an= increasingly large userbase.

I'm very happy (and relieved) to s= ay that as of 3 weeks back everything important from=20 CeroWrt has finally been pushed into openwrt, and if I were to wipe out on = the autobahn tomorrow, it really wouldn't matter all that much. (to the= project!)

We'll (cerowrt folk) will take a look at this repo to= o to see what can get folded back into Cero, for now, but a better path is = to the core devs of the individual packages. "Feed the upstream".=

Does anyone know where the hipnet stuff lives?

Cheers,

-Markus

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet