NCICB would like to solicit contributions from external development teams! Put on your programming hat and help us build next generation tools that will be used by the bioinformatics community to develop n-tiered architecture that use controlled vocabularies and registered metadata. See the caCORE SDK Project Page to learn more about the caCORE SDK.
The expectations for a "unit" of contribution are described in the Unit of Contribution Section in more detail but essentially can be an extension to the code generation module, semantic connector module, service layer changes, a functional enhancement or a documentation enhancement
We will consider proposals for any kind of contribution. However, here is a list of contributions we consider most important for our upcoming release:
- Support additional versions of XMI for data loading and code generation
- Support Mac based UML tool
- Enhancements to semantic connector for UML loading
- UI for the caCORE SDK
- Enhancements to the Search paradigm.
Watch this space !! In this section we will update what projects and open source contributions have been approved for development in the late Fall release.
First, Take a look at the Wish List posted on this page. Also understand thoroughly the Unit of Contribution descriptions to get a feel for the type of project you would like to work on and your preferred level of participation. Then contact the caCORE SDK team to discuss your interest and proposed scope.
Once development is agreed upon, we will work with you to develop a project plan and integration schedule. During development you will be asked to participate in caCORE Status Meetings and caCORE design meetings. Design Meetings are informal team meetings in which we discuss and review design plans, code, client deliverables, etc. These meetings will occur regularly as needed throughout the process.
Contact can be made regarding potential contributions at NCICBOpenDevelopment@mail.nih.gov to begin the process. Be sure to include "caCORE SDK" in the subject line. We look forward to hearing from you.
A unit of contribution can be as small as a bug fix or be a new feature or whole new tool. Contributors will be asked to describe the requirements their proposal is intended to meet via a use case format. A proposed unit of contribution will be evaluated based on contributor skills and fit within each of following areas:
- The Model Driven Architecture (MDA) is expected to be understood and utilized by contributors
- caCORE release cycles would be followed incorporating appropriate phases of design, development, testing and deployment
- Demonstrated skills in appropriate programming languages
- Understanding of existing applications and functionality and role of SDK within caCORE.
- Improve the Java JET technology used for code generation of domain objects.
- Enhance the Hibernate object relational mapping files to allow automated mapping to multiple data sources.
- Enhancement to Semantic Connector for UML Model Concept validation.
- UI for caCORE SDK
- New search or search paradigm
- Generation of XML serialized data objects.
- Enhanced tool to deploy data services in JBoss
- Ability to deploy individual models in the application server
- Bug fixes
- Extension to an existing tool (i.e., take existing functionality and add additional capabilities to it)
- Enhanced testing
- Performance improvements (for example, improve the caching mechanism used in Hibernate)
- New or enhancements to Users Guides or Technical Documentation
|