Two Bitcoin users agree to open a "bi-directional payment channel" locking say .5 BTC each into a cooperative channel. They then create Bitcoin transactions that don't get committed to main change to alter shares. As long as they keep agreeing mutually on new state (Alice .4 Bob .6 eg) no need to broadcast to chain. If either party wants to close channel they just broadcast most recent agreement to chain. If one party tries to cheat and broadcast out of date transaction to chain other party gets all the coin.
That's the ripple connection. Then they plan to have third party servers find paths between these bilateral payment channels to execute a payment across multiple hops using Hashed Timelock Contracts.
This is what this controversial Segregated Witness soft-fork drama in Bitcoin community is all about. They're solution to transaction problem is to put a Ripple network on top of the whole thing.
And from reading articles the developers are running into same hub/path liquidity issues that anyone who has studied ripple is familiar with.
It's supposedly slated to go live this year.