Page History

...

• Topics which are still on the "back burner" (which need someone to lead a "Special Topic" meeting around them)
  • Do we want to schedule a meeting to go over proposed Modularization / Refactoring work in near future?
    • Restructure Trunk Projects
    • Refactoring the DSpace Domain Model
    • Others listed under Development Proposals
  • Discuss improving how DSpace handles Metadata (From past meetings discussions, this seems popular). Several ideas mentioned recently:
    • Updating to current DCMI standards: DS-805
    • Creating a new "dspace" internal usage schema (for administrative, or non-DC metadata)? Formalize the "dc" schema to be strictly valid QDC/DC?
    • Metadata on all DSpace objects (not just Items)
  • Discuss forming a "Documentation Management Team"? Or reworking our procedures for managing/reviewing/approving Docs on the Wiki.
    • UPDATE: Jeff Trimble will lead a discussion on this in April or May. Still working on date.
  • More discussion of Proposed RoadMap to 2.0
    • In meantime, feel free to forward thoughts on to Tim or everyone (via dspace-devel or dspace-commit).
  • Followup on some Async Discussions (both from last week and from recent email threads):
    • Tim & Mark D had a discussion about potentially reorganizing the SVN "Modules" area into more specific "groupings", to make it more clear which modules/projects are "supported" and which may be experimental, etc. Would like to consider possibly reorganizing into these general 'groupings':
      1. "Sandbox" - all modules which are still experimental (or very outdated?) should likely move to existing SVN Sandbox area
      2. "Core Modules" (may need a better name) - These are fully supported modules which actually are released as part of out-of-the-box DSpace.
      3. "Extension Modules" (may need a better name) - These are modules which should be considered "more stable" than those in Sandbox. But, they are not released as part of out-of-the-box DSpace (rather they can be installed separately as "addons" or "extensions" to DSpace).
    • The idea would be that "Sandbox" and "Extensions" areas are open to any/all developers to take part in development. But that the "Core" area is likely managed more like current SVN TRUNK (where you need to be a "Committer" or "Highly Trusted Developer" to commit code there).

Meeting Notes

• Documentation Mgmt Discussion
  • Developers decided that we need to have an "In Development" space for Documentation
    • Now created at DSDOCDEV
  • General release plan for Documentation:
    1. Docs which are unreleased will be written in DSDOCDEV space.
       • Review of documentation should also likely happen in DSDOCDEV space.
    2. During Release Process, we will copy docs from DSDOCDEV to DSDOC (official documentation) space. We will also generate PDF and/or HTML.
    3. Immediately after Release, DSDOCDEV is again for the next "unreleased" documentation (in preparation for following release)
       • DSDOC is always officially released documentation.
  • Developers also noted that we need to be better about creating our own Documentation. We also need to ensure that we are completing Documentation at least two weeks before Release (to ensure enough time for editing/reviewing of docs).

Meeting Transcript

• Full IRC Transcript is available at - http://irclogs.duraspace.org/index.php?date=2011-06-0122