iRODS-E : Differentiation vs. Effort Lower effort with less differentiation vs. more effort and higher levels of differentiation. Packaging & Installation – Increased UX Documentation In-Place - Hardening In-Place - Refactoring Branch & Merge – Hardening / Refactoring
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Address iRODS installation issues
iRODS knowledge is scattered about the irods.org wiki & irods-chat mailing list. Providing a comprehensive set of documentation would be an important differentiator for RENCI’s iRODS-E, such as:
Work closely with the DICE developers to improve the iRODS code base within the Community Code Repository :
iRODS-E then becomes a RENCI tested & certified release of the
A iRODS-C 3.0 Branch has been created in G-Forge, Current hardening & testing efforts currently focus on this code base.
Break iRODS code along interface boundaries, re-writing significant sections while maintaining backward compatibility. Early targets would be:
Using existing Open Source libraries and other modern tools, RENCI could reproduce iRODS functionality, targeted other primary use cases, ‘Big Data’, etc.