One of the great things about using open source code for projects is the opportunity to contribute back to the community and get a little recognition for your hard work. Just like the code though, there's a "Drupal way" for patch contribution and the goal of this article is to help you expedite your plan to contribute module patches back to the community and to limit the difficulty you will have in getting those patches accepted.

1. Pulling the latest code.

I've taken the open souce ext_calendar component (http://extensions.joomla.org/component/option,com_mtree/task,viewlink/li...) and made some significant modifications to it.  I cleaned things up fairly considerably for creating search engine friendly urls, and I ported the event administration to the back end.  My goal is to turn around and release this one to open source.  I’ll see if I can’t address some of the other user concerns and clean up the code more, but this could be/should be a nice contribution back to the open source