Difference between revisions of "Lyo/ProjectPlans"

From Eclipsepedia

< Lyo
Jump to: navigation, search
Line 1: Line 1:
= Introduction =  
+
= Introduction =
  
This page contains the project plans for the Eclipse Lyo project. The first part of the plan describes the various components of Lyo and the currently planned enhancements to functionality. This plan is subject to changes based on community participation and the importance of proposed functionality to the community - we encourage anyone interested to participate. The planning process will be as open as possible and this plan will be updated as it changes.   Please provide feedback on the lyo-dev@eclipse.org mailing list.
+
This page contains the project plans for the Eclipse Lyo project. The first part of the plan describes the various components of Lyo and the currently planned enhancements to functionality. This plan is subject to changes based on community participation and the importance of proposed functionality to the community - we encourage anyone interested to participate. The planning process will be as open as possible and this plan will be updated as it changes. Please provide feedback on the lyo-dev@eclipse.org mailing list.  
  
= Lyo Components =  
+
= Lyo Components =
== OSLC Java SDKs ==
+
* Documentation
+
* Constant strings for OSLC namespaces and providers
+
* POJO model for OSLC resources
+
* RDF parser and serializer
+
* JSON parser and serializer
+
* OSLC query parser
+
* HTTP client library
+
* Basic, Form, Oauth support
+
* Client query builder (contributors needed)
+
  
== Test suite for OSLC ==
+
== OSLC Java SDKs  ==
The test suite for OSLC is currently available on the Lyo project.  See [[Lyo/LyoTestSuite|the Lyo test suite page]] for details.  Currently planned enhancements are
+
* Add reporting capabilities
+
* Improve Change Management MUST and SHOULD requirement coverage (contributors needed)
+
* Improve Requirements and Change Management MUST coverage (contributors needed)
+
* Improved query tests (contributors needed)
+
* Improved Oauth tests
+
* Tests driven by resource shape documents (contributors needed)
+
  
== Reference implementations for OSLC (RIOs) ==
+
*Documentation
Reference implementations are currently available for the Change, Requirements and Architecture Management specifications.  See [[Lyo/LyoRio|the Lyo reference implementation page]] for details.  Currently planned enhancements are:
+
*Constant strings for OSLC namespaces and providers
* Support for the Quality Management domain (contributors needed)
+
*POJO model for OSLC resources
* Adoption of the OSLC Java SDK
+
*RDF parser and serializer
* Refactoring to allow for pluggable RDF and application server technologies (contributors needed)
+
*JSON parser and serializer
* Improve reference implementation web UI (contributors needed)
+
*OSLC query parser
 +
*HTTP client library
 +
*Basic, Form, Oauth support
 +
*Client query builder (contributors needed)
  
 +
== Test suite for OSLC  ==
  
== Additional Proposed SDKs ==
+
The test suite for OSLC is currently available on the Lyo project. See [[Lyo/LyoTestSuite|the Lyo test suite page]] for details. Currently planned enhancements are
Contributors are needed and welcome for all of the following:
+
 
* .NET (C# or other)
+
*Add reporting capabilities
* Perl
+
*Improve Change Management MUST and SHOULD requirement coverage ('''contributors needed''')
* Python
+
*Improve Requirements and Change Management MUST coverage ('''contributors needed''')
* PHP  
+
*Improved query tests ('''contributors needed''')
* JavaScript
+
*Improved Oauth tests
 +
*Tests driven by resource shape documents ('''contributors needed''')
 +
 
 +
== Reference implementations for OSLC (RIOs)  ==
 +
 
 +
Reference implementations are currently available for the Change, Requirements and Architecture Management specifications. See the&nbsp;[[Lyo/LyoRIO|Lyo reference implementation]] page for details. Currently planned enhancements are:
 +
 
 +
*Support for the Quality Management domain ('''contributors needed''')
 +
*Adoption of the OSLC Java SDK
 +
*Refactoring to allow for pluggable RDF and application server technologies ('''contributors needed''')
 +
*Improve reference implementation web UI ('''contributors needed''')
 +
 
 +
<br>
 +
 
 +
== Additional Proposed SDKs ==
 +
 
 +
Contributors are needed and welcome for all of the following:  
 +
 
 +
*.NET (C# or other)  
 +
*Perl  
 +
*Python  
 +
*PHP  
 +
*JavaScript
 +
 
 +
= Milestones  =
 +
 
 +
Currently planned milestones are:
 +
 
 +
*M1 (Q4 2011) - theme is test suite enhancements
  
= Milestones =
 
Currently planned milestones are:
 
* M1 (Q4 2011) - theme is test suite enhancements
 
 
   * Reporting
 
   * Reporting
  * Improved CM MUST and SHOULD requirement coverage
+
  * Improved CM MUST and SHOULD requirement coverage
  * Improved QM and RM MUST coverage
+
  * Improved QM and RM MUST coverage
  * Soliciting contributions for other domains
+
  * Soliciting contributions for other domains
* M2 (Q1 2011) - theme is initial Java SDK and refactored reference implementations
+
 
 +
*M2 (Q1 2011) - theme is initial Java SDK and refactored reference implementations
 +
 
 
   * Initial Java provider and client SDK
 
   * Initial Java provider and client SDK
  * Example reference implementations based on the SDK
+
  * Example reference implementations based on the SDK
  * Additional test suite enhancements to support apps written with the SDK
+
  * Additional test suite enhancements to support apps written with the SDK
* M3/Beta (Q2 2011) - theme is feature completeness
+
 
 +
*M3/Beta (Q2 2011) - theme is feature completeness
 +
 
 
   * Full Java provider and client SDKs
 
   * Full Java provider and client SDKs
  * Reference implementation completely refactored to take advantage of SDK  
+
  * Reference implementation completely refactored to take advantage of SDK  
  * Reference implementation can use pluggable RDF/application server providers
+
  * Reference implementation can use pluggable RDF/application server providers
  * Documentation
+
  * Documentation
* Release candidates and 1.0 (Q3 2011) - theme is stabilization and shutdown
+
 
 +
*Release candidates and 1.0 (Q3 2011) - theme is stabilization and shutdown
 +
 
 
   * Stretch items based on community participation
 
   * Stretch items based on community participation
      * non-Java language SDKs
+
    * non-Java language SDKs
      * Additional reference implementation and test suite enhancements
+
    * Additional reference implementation and test suite enhancements
  * Release shutdown work
+
  * Release shutdown work

Revision as of 17:15, 31 October 2011

Contents

Introduction

This page contains the project plans for the Eclipse Lyo project. The first part of the plan describes the various components of Lyo and the currently planned enhancements to functionality. This plan is subject to changes based on community participation and the importance of proposed functionality to the community - we encourage anyone interested to participate. The planning process will be as open as possible and this plan will be updated as it changes. Please provide feedback on the lyo-dev@eclipse.org mailing list.

Lyo Components

OSLC Java SDKs

  • Documentation
  • Constant strings for OSLC namespaces and providers
  • POJO model for OSLC resources
  • RDF parser and serializer
  • JSON parser and serializer
  • OSLC query parser
  • HTTP client library
  • Basic, Form, Oauth support
  • Client query builder (contributors needed)

Test suite for OSLC

The test suite for OSLC is currently available on the Lyo project. See the Lyo test suite page for details. Currently planned enhancements are

  • Add reporting capabilities
  • Improve Change Management MUST and SHOULD requirement coverage (contributors needed)
  • Improve Requirements and Change Management MUST coverage (contributors needed)
  • Improved query tests (contributors needed)
  • Improved Oauth tests
  • Tests driven by resource shape documents (contributors needed)

Reference implementations for OSLC (RIOs)

Reference implementations are currently available for the Change, Requirements and Architecture Management specifications. See the Lyo reference implementation page for details. Currently planned enhancements are:

  • Support for the Quality Management domain (contributors needed)
  • Adoption of the OSLC Java SDK
  • Refactoring to allow for pluggable RDF and application server technologies (contributors needed)
  • Improve reference implementation web UI (contributors needed)


Additional Proposed SDKs

Contributors are needed and welcome for all of the following:

  • .NET (C# or other)
  • Perl
  • Python
  • PHP
  • JavaScript

Milestones

Currently planned milestones are:

  • M1 (Q4 2011) - theme is test suite enhancements
  * Reporting
 * Improved CM MUST and SHOULD requirement coverage
 * Improved QM and RM MUST coverage
 * Soliciting contributions for other domains
  • M2 (Q1 2011) - theme is initial Java SDK and refactored reference implementations
  * Initial Java provider and client SDK
 * Example reference implementations based on the SDK
 * Additional test suite enhancements to support apps written with the SDK
  • M3/Beta (Q2 2011) - theme is feature completeness
  * Full Java provider and client SDKs
 * Reference implementation completely refactored to take advantage of SDK 
 * Reference implementation can use pluggable RDF/application server providers
 * Documentation
  • Release candidates and 1.0 (Q3 2011) - theme is stabilization and shutdown
  * Stretch items based on community participation
    * non-Java language SDKs
    * Additional reference implementation and test suite enhancements
 * Release shutdown work