-
Notifications
You must be signed in to change notification settings - Fork 74
Product Roadmap
Issues are all listed in github issues.
We discuss open issues and future plans at regular google+ hangouts. Issues are picked and placed into milestones. We are using tagging that can be used to view the milestone in huboard.com. This is to keep the core team coordinated, and to let interested people know what to expect downstream for lens. That said, contributions and pull requests are welcome at any time that deal with any open issues. The core team is using the following tagging scheme:
0 - Backlog an issue in a milestone, but not ready to be worked on yet.
1 - Ready can be worked on.
2 - Working is working within a branch
3 - Done tested, reviewed and merged into master
- Sparate eLife Lens and document definition.
- Refactor codebase to make it more modular and configurable
Mainly tracked with these tickets:
The focus of the current stream of work is to create a tool that is far easier for others to contribute to. To that end we will refactor the code to allow for a more maintainable, modular and flexible codebase for the core viewer, and to separate the view and document model by introducing an explicit definition of the lens article (https://github.com/elifesciences/lens-article).
In addition we want article pages to be crawlable by google, and we want to tidy up how refract obtains images for eLife documents, and make that parsing scheme sane.
Finally, we want to make getting started with Lens against your own content much much easier.
When we complete this round of work we should have:
-
a cleaner codebase, that is more attractive for other developers
-
a clean separate extensible document model that self-describes itself
-
a really easy way to get started
-
Current Milestone: https://github.com/elifesciences/lens/issues?milestone=1&state=open
- make lens support editing of the underlying XML files
- Integrating other OA content (first will be PLoS)
- Private notes, so users can stick notes on their paper which are stored locally
- Mobile optimizations
- Evaluating options for offline reading