I have some code for a feed that emits Camel messages for your
LinkedIn network updates. It would be pretty easy to extend that to
Twitter, Foursquare, Yahoo, and etc. (whoever uses OAuth). It has a
dependency on Scribe which uses the MIT license -- I believe that's
fine, right?
Anyway, right now it extends the Feed* stuff from the camel-atom
module, and behaves pretty similarly to the Atom component. But I
don't think we'd want to put all this into the camel-atom module --
that would seem pretty misleading.
I'm wondering if it's worth splitting the base Feed* stuff off into
another module, or renaming camel-atom to camel-feeds and putting my
code in there, or just creating a brand new module that happens to
have a dependency on camel-atom.
Thoughts?
Thanks,
Aaron
