Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  • GSoC project updates (Mark Diggory)
  • 2.0 integration work (Mark Diggory)
    • Overview of DSpace Addon Module Design and Spring
    • Discussion of Storage Services and Storage Providers as an addition to 1.7
    • Discussion on Solr Integration and Unified Search/Browse as an addition to 1.7
  • AIP Backup and Restore / DuraCloud integration project (DuraSpace & MIT & IUPUI) (Tim Donohue)
  • 1.7 planning (what's in it?)

...

3:30-4:45pm : Discussion of RoadMap for Future

  • Fedora integration proposal (Tim Donohue)
  • Longer-Term Questions:
    • Source / binary distributions (what should/shouldn't be included?)
    • Should all webapps/UIs remain out of the box? (JSPUI, XMLUI, OAI, SWORD, LNI, SOLR)
    • How do we make upgrades/installs/configuration easier?

...

The url and the location map: http://11870.com/pro/manolo-1934-bar-restauranteImage Removed

In any case, the area of Moncloa/Arguelles is full of bars.

...

  • 1.6 Discussion - Reflecting on how release went
    • Did we branch too soon – no activity in Trunk besides 1.7 (Stuart)
      • No decision on what we wanted in 1.7? May not have been fault of branching too soon. (Mark D)
    • 1.6 is now "put to bed" – likely no more 1.6.x releases (unless something major comes up)
    • Issue: We didn't test the Handle Server – issue now seems fixed, as we have a valid handle server on http://demo.dspace.orgImage Removed
    • Issue: Too much of a bottleneck for Jeff Trimble as the Documentation Guru. The model is right (to have one or more folks lead the Documentation effort), and we'd like to expand.
      • We should be more proactive to find people like Jeff. We need to enable more people to help with documentation (moving main docs to wiki should help)
    • Demo.dspace.org is 'great' – need to develop even better test practices.
      • Is there a way to encourage testathon interaction (need more feedback?). First one for 1.6.0 was great – been a bit downhill since then. Do repo managers feel it is "too hard"? Do we need 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 you found? TODO: 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? TODO: Can Repository Managers help us find data to test with? Talk to Global Outreach committee.)

...