Page History
...
- 1.6 Discussion
- Did we branch too soon – no activity in Trunk besides 1.7 (Stuart)
- No decision on what we wanted in 1.7? (Mark D)
- 1.6 is "put to bed"
- We didn't test the Handle Server – now seems fixed with demo.dspace.org
- Too much of a bottleneck for Jeff Trimble on Documentation. The model is right, and we'd like to expand.
- We should be more proactive to find people like Jeff.
- Demo.dspace.org is 'great' – need to develop more test practices.
- Is there a way to encourage testathon interaction (need more feedback?). First one was great – been a bit downhill since then. Do repo managers feel it is "too hard". Rebranding? What's the positive "reward" – how to you incentivize them? (It works well when people are excited about it). A top ten testers – or a drawing based on number of bugs? Talk to Val – does Global Outreach have ideas on incentives???
- Automated testing from GSoC
- Integration testing
- Performance testing is a need (small / medium / large reference datasets – how to build these / IP issues?)
- Did we branch too soon – no activity in Trunk besides 1.7 (Stuart)
- Documentation 1.6
- Confluence docs
- Snapshot versions a problem for Fedora side?
- Exports to HTML and PDF
- "Hard Stop" to move just to Confluence based Docs (move back to SVN)
- How do we make sure all patches have documentation before commits?
- Move original wiki page off to docs area
- Handle Server plugin – difficult to do migrations (have to sync up handle IP change with migration) – blind assumption that it's always running on same server as DSpace (Richard Rodgers)
- Should be replaced with a Service call (HTTP REST?) – any processing/slowdown here, likely not?
- Related to REST GSoC project?
- Graham has rewritten code entirely – one handle service that responds for all prefixes
- Decoupling is necessary – all in agreement
- CNRI Handle Server 7.0
- Anything we need to know about on our end
- Decoupling for a future hosting service (DuraSpace hosting it for small sites?)
Overview
Content Tools