I think it’s difficult to talk about future features without context. So it would be helpful if we could express in a great level of detail what exactly we see people doing with River. Perhaps even build a proof-of-concept demonstration and use that to drive any changes to River.
Cheers, Greg Trasuk > On Feb 25, 2016, at 9:33 AM, Patricia Shanahan <p...@acm.org> wrote: > > Thanks for getting this started. > > I think you have a high level vision of where you see River going in the > future. It might be useful to state it here. The costs and benefits of > changes are best evaluated in that sort of context. > > On 2/25/2016 3:52 AM, Peter Firmstone wrote: >> While we're waiting for people to review River 3.0's Release >> artifacts... >> >> I've posted some of my more contraversial work on River security and >> ipv6 global discovery (internet announcement protocol) on github. >> The river community is free to cherry pick the code if it wants. I >> would have much preferred to have developed it collaboratively, >> there's room for improvement. >> >> Features: > ...
