I will do so, however, the Oledrion module is really outdated, it is worth to change it, when I create a base with tdmcreate 1.91?
It's really up to you, what you find more useful. However, sometimes it's better to fix/improve an existing module, instead creating a new one.
My personal preference would be to merge the best features from some existing modules and create one that is better than any of them individually, and provide users of these modules with a migration path to that one.
Publisher is the best example. We had News, xNews, AMS, SmartSections, but all of them could be migrated to Publisher. I prefer to work on and improve Publisher, and encourage all users to migrate to Publisher, because then we have less modules to maintain
We need to focus on more reuse between modules. The best example of reuse is what Mage did with the "ModuleAdmin", because now all modules can share it and we have a nice consistency between modules.
It's possible that we cannot adjust Oledrion to be a "Restaurant" module. But think how cool it would be, if we could transform Oledrion into a generic "eCommerce engine", and by adding a specialized plugins like a "Hotel", "Restaurant", or "Bookshop", being able to provide our users with such solutions. It would be much faster to develop such plugins and easier to maintain them, than having tons of different modules developed from scratch.
I hope, XMF and Bitcero's Common Utilities will help us to extract more and more common features that could be shared and reused between module....