Page History
...
- DSpace 4.0 - Planning next steps, calls for help/support, etc.
- Empowering individuals / small teams to tackle problems & find solutions rapidly
- Came up during an IRC Mtg dicussion on 2013-04-10 (starts around [20:32])
- Want to avoid "blockages" or slowing down progress by waiting around for "widespread approval" on any proposal/idea. Instead, we want to let small groups move/develop rapidly, and trust that they will build something "good enough" (which we can later improve on if needed). These small groups would still need to communicate their work/progress back to broader developer community (to keep others in the loop / receive ongoing feedback / avoid duplicate projects), but need not wait for an "official vote" before moving forward with their work.
- Possible "quicker" workflow:
- someone raises an issue / feature idea
- several interested parties discuss it
- self-organized team presents an idea, hears objections and suggestions
- (if needed) team addresses immediate concerns and presents again
- (we hope) everybody is okay with amended proposal and work goes forward
- people talk about the work as it is progressing, and get more feedback
- finished work addresses all known issues and is voted in. If additional work is needed it may be voted in as a "beta" feature until it can be improved in future releases.
- someone raises an issue / feature idea
- DSpace 3-5 Year Vision: Discussion of output of the May meeting (in Chicago) to draft a 3-5 year high-level vision/roadmap for DSpace software. This meeting was formed out of the vision discussions that took place as part of the DuraSpace Sponsor Summit in March
- DCAT proposal to improve metadata support in DSpace (https://wiki.duraspace.org/display/DSPACE/Updating+the+Qualified+Dublin+Core+registry+in+DSpace+to+the+latest+standards+of+the+DCMI).
Sign Up to Attend!
If you're planning to attend this meeting, please add your name to the sign up sheet. This will allow us to determine a proper headcount.
...
Overview
Content Tools