Page History

...

1. Request for blogging of DuraCloud activities (MattZ, others)
   1. Action: Add DuraCloud wiki space
2. Request for Fedora transparency
   1. Interest in Special Topics meetings
   2. Interest in recording audio of meetings for people to listen to later
      1. Action: June 9th for Special Topics
3. Request for details of FedoraRepository/DSpace architectural roadmap
   1. Want latest Roadmap on website/wiki (TimD discussion: "Roadmap" theme as Jira field, and auto-generate parts of roadmap from Jira?)
4. Maven2:
   1. Lots of positive responses
   2. MarkD wants Fedora POM for DSpace-on-Fedora builds
5. OSGi:
   1. DSpace considered OSGi early on, but steered away from it in part due to percieved complexity.  Currently using it's own "OSGi-like" module approach, using Spring.
   2. Sakai went back and forth on OSGi, now moving toward it.
   3. AaronZ (sakai/dspace2 committer) gave us an osgi primer
   4. DaveF pulling together resources for Eddie+AaronZ to go to osgi conference and experiment with OSGi-fying Fedora
6. FedoraFS (Rebecca Koeser@Emory's repo challenge entry):
   1. Allows use of Fedora via standard filesystem interface (video here)
   2. ChrisW talking w/Rebecca this week: re: potential "contrib" project
7. Wider developer participation:
   1. Sakai experiences:
      1. When voting on issues, people tend to choose the big, difficult items.
      2. Having a "contrib" area has been very successful
   2. Sakai suggestions:
      1. Put out a list of things to do; people will help (even if not right away)
      2. Get people helping in non-coding ways (docs, managing users)
      3. Make sure people and institutions get proper credit for their contribs
8. Desire for dev-focused get-together
9. Somebody did a Fedora Ubuntu/Debian installer (poster)
10. Fedora integration with JPEG 2000 (http://apps.sourceforge.net/mediawiki/djatoka/index.php?title=Fedora_Integration)
11. Bill Parod interested in being able to allow only certain API-A methods to be accessed by unauthenticated users

Potential actions

1. Draft release of 3.3 feature list
2. Promote feature "interest groups"
   1. These groups would ideally be self-forming
   2. May need initial help from core-developers to establish precedence
   3. Would have wiki area for design, units-of-work, status, etc...
      1. maven2 ?
      2. fedora as self-contained, deployable war ?
      3. OSGi ?
      4. Web Admin additions ?
      5. Enhanced Content Model ?
      6. Workflow ?
      7. Security redesign ?
      8. ...
3. New development infrastructure
   1. OSUOSL for hosting svn, etc...
   2. Forum
   3. Mailing lists
4. Establish "contrib" area of svn
   1. Plan towards "garage sale"
   2. Encourage community to bring customizations out of wood-work
5. Hack-a-thon
6. Include JP2 service as part of Fedora distro with demo objects available to view (similar to Mr.SID)
7. ...