Adobe has made extensive contributions to the world of EPUB software, from the free (as in beer), cross-platform Digital Editions reader to their open source contributions in epubcheck, epub-tools, and the ePub output for the DocBook-XSL project. Adobe's adoption of open source development models has benefited the community (and, I hope, Adobe) greatly, and I'd like to encourage them to adopt another open source technique for Digital Editions.
Like any piece of software, Digital Edition has bugs. As publishers sell more EPUB books, readers become more aware of the EPUB format, and Adobe partners with more hardware manufacturers, it becomes increasingly important that the Digital Editions/Reader Mobile SDK team collect, publish, and correct bug reports from the community. I've noticed a marked uptick in complaints about EPUB on Twitter, in person, and from our customers. Many of these can be traced back not to EPUB the format, but to the particular reading system being used to read EPUB. For better or worse, Adobe has the dominant reading system in Digital Editions (outside the iPhone), and it has both an opportunity and responsibility to improve reader satisfaction by resolving problems in the software.
To help facilitate that aim, I'd strongly encourage Adobe to adopt an open bug tracker for Digital Editions. Not only will an open bug tracker allow Adobe to be alerted to problems more quickly, it will also allow developers and content creators to develop workarounds for known bugs and improve the experience for readers. An open bug tracker will also help customer service departments triage customer complaints, as it becomes more clear whether a reader has come across a known issue in a specific version. Moreover, Adobe already has the infrastructure for open bug tracking at bugs.adobe.com.
I think it's also important that the Digital Editions team be transparent in their plans for the evolution of the software. A published roadmap would help readers and developers outside Adobe understand the basic goals for the future of the reading system. As Adobe's Reader Mobile SDK reaches wider and wider adoption, it'll be crucially important to understand whether Adobe intends to simplify and constrain the desktop version of Digital Editions (and the underlying rendering engine) by using a single codebase shared between both products. EPUB creators are often frustrated to learn of the constraints Adobe expects EPUB to follow on devices like the Sony Reader's 300KB "chunk" size limit and I think it's important to understand where those constraints do and do not apply.
Finally, I'd like to encourage the Digital Editions team to provide more structured release notes in EPUB format with the details of changes in every minor and major release. Ideally, these notes would include the current version at the top, but also the dates and notes on each previous version in the same document. In each version, any changes that introduce non-conformant features or enhancements should be unambiguously called out.