Lyo 2.3.0 roadmap

This a placeholder document. Make sure to put the bug links to the relevant items.

Inbox

This is a list of tasks that have not yet been incorporated into the rest of the document:

  1. Mavenizing lyo.tools (to enable P2 site builds as part of the Gerrit build).
  2. Obsolete OAuth library needs to be replaced (not supported any more, potentially unsafe). In the best case, it would be replaced with google-oauth-java-client or signpost.
  3. Making OAuth-enabled Lyo client as well as the JazzRootServicesHelper webapp oriented: they should allow for instance destruction and reinstantiation while the user is approving the access token (currently they throw an exception and expect a repeated method invocation of the method on a same class instance after the access token has been approved).
  4. Deploy to Maven central (some help from the Eclipse webmaster and GPG signing of the artifacts will be required: https://wiki.eclipse.org/Hudson/Maven)
  5. Migrate to Jena 3.
  6. Updating Lyo RIO (Reference Implementation for OSLC) for OSLC 3. To become an OASIS Standard, OSLC Core 3.0 needs three "statements of use" or implementations. Lyo could be one or more of these.
  7. Reorganise Lyo repositories (started with lyo.rio on GH, lyo-store extracted from lyo.tools as well as tools fully moved from lyo.core).
  8. Extend Lyo to support OSLC Configuration Management 1.0 specification - this would allow Lyo to support development of clients and servers that support configuration management.
  9. Development of OSLC clients and servers in other environments such as JavaScript/Node, .Net, MacOS/Swift, etc. See OSLC4JS for example at http://oslc.github.io/developing-oslc-applications/oslc-open-source-node-projects.html
  10. Replace Wink with Jersey – Andrew has a prototype working without Lyo Client and without the dynamic ShapesService getting registered properly. The prototype shows the migration from Jax-RS 1.1 to 2.0 as well as from Wink to Jersey. Dropwizard may be considered as an enhancement for the Jersey migration to make it closer to “production-ready”.
  1. We should consider creating a demo toolchain deployment for Kubernetes. Andrew has personal interest for that in his PhD project. Maybe Lyo can get some credits to run its demo on https://www.ibm.com/cloud-computing/bluemix/containers 
  1. Merge the tests in the core into the same project (migrate external JUnit 3 tests to combined JUnit 4/5; JUnit 5 will be GA this autumn):
  1.     * org.eclipse.lyo.client.java  has very limited automated tests. Additional manual testing can be done using the sample code
  2.     * org.eclipse.lyo.core.query has some unit tests, but they don’t appear to be comprehensive
  3.     * org.eclipse.lyo.trs has no unit tests
  4.     * org.eclipse.lyo.oslc4j.core has some tests, but they appear to be tests for specific issues, not a comprehensive test suite
  5.     * org.eclipse.lyo.oslc4j.provider.jena has a lot of tests
  6.     * org.eclipse.lyo.oslc4j.provider.json4j has  some tests
  7.     * org.eclipse.lyo.core.utils  has tests fro reading RDF/XML and Turtle
  8.     * org.eclipse.lyo.oslc4j.wink has no unit tests
  1. Generate an interactive Lyo client for each adaptor instead of the pale browsing UI.
  1. Interest from the Jad and Leonid sides for that
  1. Improve the docs
  1. Comments from Jim
  1. Regarding documentation, https://wiki.eclipse.org/Lyo, is the place http://git.eclipse.org/c/www.eclipse.org/lyo.git/is deployed. The problem with the eclipse wiki is the navigation sidebar is taken up by eclipse, Lyo doesn't seem to contribute to the sidebar. So there's no convenient TOC to help navigate the Lyo content.
  2. GitHub wikies do allow creation of a custom sidebar. It might also be helpful to partition the documentation by the refactored repositories so that closely related information is in the same place.
  1. Andrew suggests to try MkDocs to replace both the website and the Wiki https://github.com/berezovskyi/lyo-docs
  1. Split the lyo repositories with the examples into multiple separate repositories and move them to Lyo Github (under EPL and with all the IP checks intact).
  1. I would love Jim and Jad to do this work mainly, in order to practice with the Eclipse Webmaster communication as well as Git/Github practice. The stress here is that we move the repos in one step and leave all dependency version updates and clean-up for later.
  2. Jim’s points:
  1. Review refactoring proposal with eclipse/Lyo community and update as needed
  1. TODO solicit feedback on this roadmap
  1. 2. Review target environments and resolve any issues
  2.         1. Continue using eclipse.org for OSLC4J SDK
  1. I agree, until you feel comfortable moving between Github and Gerrit, Jim & Jad.
  1.         2. Use OSLC GitHub organization for samples and reference implementations
  2.         3. Use OSLC GitHub Wiki and optionally GitHub Pages for documentation, organized by repository
  1. I suggest to keep the docs/ folder with markdown in the projects but use MkDocs for the site & docs.
  1.         4. Use OSLC GitHub issues for change management
  1. A bit problematic for now, let’s use this Google Doc as a way to transition away from plain Bugzilla.
  1. 3. Get approval from the eclipse.org Technology PMC to perform the refactoring and repository migration
  1. No need for that as long as we keep the same level of IP check (Type B full legal check).
  1. 4. Create the GitHub repositories according to the adopted refactoring plan
  1. TODO Jim/Jad (Jim or me can +1 for the Eclipse Webmaster).
  1. 5. Clone the eclipse.org Git repositories that are to be migrated to GitHub - history is retained at eclipse.org
  1. We can just ask  Eclipse Webmaster to move them, no need to keep them on Eclipse - they remain under the same level of protection on Eclipse org on GH.
  1. 6. Build and test each repository’s components in order to reach a known, stable state
  1. HAHA, good luck with that. This is not that easy to perform cross-repo build & test.
  1. 7. Migrate eclipse/Lyo documentation to GitHub and GitHub Pages.
  1. Actually, I like the idea of moving the repo to Github but not


Backlog for 2.3.0

New contributions (NEW):

  1. (Andrew/Frederic) New Twitter Bootstrap based templates in the generated adaptors
  2. (Jad) External class libraries in the generated toolchain
  3. (Yash) Shape validation library based on SHACL definitions
  4. (Daniel) Shape validation extension for the Lyo toolchain designer
  5. (Jad/Frederic/Jim) Link preview in the generated adaptors
  6. (Andrew/Jad) Maven build config for the Lyo Toolchain Designer
  7. (Andrew/Omar/Eclipse IP) TRS provider
  8. (Andrew/Thomas/Eclipse IP) TRS consumer

Reorganisation & refactoring (REF):

  1. (Andrew & everyone else) A new combined site & wiki on MkDocs.
  2. (Jim & Jad?) Split  the sample code & examples into multiple repositories on Github
  3. (Jim?) Move the client/server code back into core for simpler process?

Bug fixes (BUG):

  1. Foo
  2. Bar

New Twitter Bootstrap based templates in the generated adaptors

Responsible: Andrew

Status:

New Twitter bootstrap based template allow to easily structure information in the adaptor and allow using Bootstrap component library, esp. JS controls.

We need to slightly adjust the code in order to use jQuery version as declared in CQ (wrong JS file uploaded) as well as await the CQ decision on the original patch from Frederic.

External class libraries in the generated toolchain

Responsible: Jad

Status:

Allows to generate Java classes for the domain spec resources into a separate folder/package for the whole toolchain. This allows writing libraries for those resources that can be reused across the toolchain.

 Shape validation library based on SHACL definitions

Responsible: Andrew, Jad/Jim

Status:

Shape validation extension for the Lyo toolchain designer

Responsible: Jad