introducing OOOR - OpenObject On Rails: driving/requesting your OpenERP became a child play

One year ago, much for the fun, I started a small open source project [OOOR - OpenObject on Rails](http://github.com/rvalyi/ooor): the idea was to explore Ruby metaprogramming techniques to remotely access the whole API of OpenERP using the standard OpenERP webservices just like the genuine [Rails ActiveResource API](http://api.rubyonrails.org/classes/ActiveResource/Base.html). The thing is that OOOR is more and more being used for awesome stuff today, so I think it was the right time to finally present it to the general public...
Read full article

Scaling OpenERP's community to the world

Things have been moving really fast for OpenERP and Tiny during those last 2 years. A lot of indicators (Google Insight, Launchpad inscription rates, partner list…) show OpenERP matured from a confidential francophone ERP to the global leader of open source ERP’s. As you may have noticed this hasn’t been without a clash. Especially, Tiny has been recently totally overwhelmed by the huge demand and community activity, unable to interact with the community anymore. This bottleneck around Tiny leaded to frustrations in the forums. This is time for action, and I believe this is finally happening.

The ambition is to remove the bottleneck around Tiny by decentralizing some processes to the global community instead. With an exponentially growing community it would just have been too bad not being able to benefit from all that growing tireless grey matter working 24 hours a day, 7 days a week, 365 days a year. A key for the expertise decentralization is to set up expert teams that would act as intermediary hubs between Tiny and the community and thus alleviate Tiny from most interactions, speeding up decisions processes and putting more grey matter in the process. It is thus expected both to polish the 5.0.x releases more effectively and make the most from the community excellence for the coming 5.2 release for Q1 2010.

Those expert teams include several infrastructure teams to manage the community communication itself, bug and development planning, the openobject framework and ergonomics. There will also be a localization expert team to help all national localization teams to network more efficiently about common issues. Finally, there are also domain expert team for accounting, manufacturing and service business fields.

Read full article