Quote:
Originally Posted by EowynCarter
You know what would be nice : Open source.
Have the official-reads-drm version maintained by bookeen, and an open source one maintained by the community. (With a common part for menu and all, maintained by both).
Trouble being testing. I'll never put a firmware on my reader unless it's stable.
|
I doubt that this is viable because if you have an official part for DRM and an open source part for the rest, who will users get support from when something isn't working. Normally users would complain to the company they bought it from and no company would want to get flamed for problems resulting from the open source part.
It might be possible to create a certain area for open source code if you allow plugins. That way problems are somewhat containable and customer support could always request to remove all plugins to see if the problem persists. But there's only so much you can do with a plugin structure, the main interface and functions would have to be excluded for the reasons mentioned above...
Much better would be to offer a FW entirely open sourced. It wouldn't be a problem really, for customer support you could always define a certain version number as the only supported one and if users flash newer versions or different branches they're on their own there. But in this case it's not possible because reader devices currently cannot do without supporting DRM (although that will hopefully change) and DRM can never be open-sourced.