Open Source Rookies of the Year
From the webpage:
The fifth annual Black Duck Open Source Rookies of the Year program recognizes the top new open source projects initiated in 2012. This year’s Open Source Rookies honorees span JavaScript frameworks, cloud, mobile, and messaging projects that address needs in the enterprise, government, gaming and consumer applications, among others, and reflect important trends in the open source community.
The 2012 Winners:
- Ansible – configuration management, deployment, and ad-hoc task execution. (Ohloh entry)
- Chaplin js – an architecture for JavaScript applications using the Backbone.js library. (Ohloh entry)
- GPUImage – an iOS library for adding GPU-accelerated filters for video and images. (Ohloh entry)
- Hammer.js – JavaScript library for multi-touch gestures in the mobile web. (Ohloh entry)
- Inasafe – produces natural hazard impact scenarios for planning, preparedness and response. (Ohloh entry)
- Sidekiq – provides simple, efficient message processing for Ruby. (Ohloh entry)
- Syte – packaged personal site with social app integrations like Twitter, GitHub and more. (Ohloh entry)
- Twitter Bower – a package manager for the web that also manages dependencies. (Ohloh entry)
- TypeScript – a language for application-scale JavaScript development. (Ohloh entry)
- Yahoo! Mojito – JavaScript MVC framework for mobile and Web apps running on client and server. (Ohloh entry)
Honorable Mention: DCPUToolChain – an assembler, compiler, emulator and IDE for DCPU-16 virtual CPU (Ohloh entry).
What lessons do you draw from these awards about possible topic map projects for the coming year?
Projects that would interest developers that is. 😉
For example, Inasafe is described as:
InaSAFE provides a simple but rigorous way to combine data from scientists, local governments and communities to provide insights into the likely impacts of future disaster events. The software is focused on examining, in detail, the impacts that a single hazard would have on specific sectors, for example, the location of primary schools and estimated number of students affected by a possible tsunami like in Maumere, for instance, when it happened during the school hours.
Which is fine so long as I am seated in a reinforced concrete bunker with redundant power supplies.
On the other hand, if I am using a mobile device to access the same data source during a tornado watch, shouldn’t I get the nearest safe location?
Reduced or even eliminated navigation with minimal data could be returned from a topic map based on geo-location and active weather alerts.
I am sure there are others.
Comments/suggestions?