Forgot your password?

RIM Opens the Door for Developer Contributions to WebWorks Code

RIM Opensource

RIM made a big splash by announcing an quasi open source project with BlackBerry WebWorks. I am loving the fact that RIM finally has a Git repository though until now you could just view the source of the current WebWorks Trunk. Tim Neil let me know on the developer forums that RIM has just opened the door to code contributions to WebWorks from lone developers and companies. They have adopted a license based on the one used by the Apache Software Foundation and is very similar to what Google uses for Android.

RIM seems to still be ironing out the details but this means that if a developer finds a bug in the WebWorks framework or wants to improve it they will be able to submit their contributions. RIM mentions that you can already submit bugs and bug fix code contributions through their developer issue tracker but they still prefer to have this agreement in place.

Check out the details at this link on RIM’s GetHub WiKi if you are interested.

From one I am hearing it seems like developers would rather RIM show the source code and allow for direct contributions to upcoming versions instead of only being able to see the current trunk. Something makes me doubt that RIM will do it but who knows! I really want to comment whomever or whichever group at RIM is driving this effort. Keep up the good work.

5 total comments on this postSubmit your comment!
  1. Would love to hear from some of the devs we know read BerryReview. Is this open source effort going be anything, or is it just a geeky thing that’s never gonna mean anything really cool to end users?

  2. Every DevCon, I see RIM making a big deal about this new WebWorks (formerly Widgets) thing. And whenever they do, RIM always sounds enthusiastic while the crowd seems to not really care too much. Maybe its because everything there is actually a Java developer and not a web designer.

    In any case, what I really want to see is some more open-source efforts (possibly even RIM-sponsored ones) that benefit the core Java platform. So many BB developers seem to invent their own solutions to platform shortcomings, and *never* want to share them with anyone, lest they lose a competitive advantage. While this helps them in the short term, it hurts the whole platform in the longer term. If RIM started pushing common library code (and not just KB samples) in the context of open-source projects, it could definitely help with that.

  3. I don’t really understand what most of this means, but if its something that is beneficial to RIM and all of us end users, then I’m all for it.

  4. It is good to see, they still have a bit to go, but they are working in the right direction to draw developers.

  5. One thing that’s quite obvious from comments on these websites, and from my usual idling on FreeNode IRC (##blackberry and ##blackberry-dev) is just how little overlap there really is between developers and users on the BlackBerry platform.

    While I don’t expect most users to be developers, I really wish more developers were actually users. (Instead of just being tapped by their employer to “figure out this BlackBerry stuff”.)

BlackBerry© is a registered Trademark of BlackBerry Limited. BerryReview is in no way affiliated with BlackBerry Limited though sometimes their lawyers send us love letters...

Copyright © 2007-‘2016’ BerryReview LLC