Follow up post by Jarek Jarcec Cecho
thank you very much for starting the discussion about contrib module. Flume is a very pluggable project where user have opportunity to plug in variety of different components (sink, source, channel, interceptor, ...). I believe that having a place where users can easily exchange their own plugins would be extremely useful and would help with further adoption of the project. Having a contrib module seems as one way how to accomplish this, another way would be perhaps to have a special wiki page (which we already do have ).
I do see benefits of repository based contrib module in having the ability to track the authorship of the changes and their history as the time passed. As I do see the contrib space more as a user driven, so I would see the bar of including a new component very low. It should be very easy for one user to submit component that works in his particular environment and let other user to tweak it for yet another purpose. With the bar keeping low we can't expect that the components will always work with current flume version nor that they will be backward compatible. Having said that I don't think that such contrib module should be official part of a Flume release. We can do our best to make a contrib release as a part of our usual release process and offer it as a separate download. I would not consider broken or removed components in the contrib as blocker for flume release though.
I'm happy to hear others opinions!