Table of Contents

Review of new tracker items

  • SPARQL issues from Ben O'Steen: FCREPO-478,479,480
    • Moved to open state
    • Q: Does Mulgara support these to begin with?
    • A: Yes (Chris checked with Paul later in the day & updated issues accordingly in JIRA)
  • Consistent Exception Handling: FCREPO-488
    • Moved to open state
  • Rework Fedora FAQs: FCREPO-483
    • Moved to open state
  • XACML hasModel patch from Thomas Wana
    • Moved to open state
  • Fold API-A Lite into the REST API
    • Moved to open state
    • Q: Need similar issue for API-M lite?
    • A: No, REST API already generates PIDs and doesn't need upload
    • Q: Deprecated API-M lite?
    • A: Not until we have soap with attachments
  • GSearch: Broken relative includes (w/patch) from Renaud Waldura

3.2

We released Friday afternoon, updated most remaining docs over the weekend, and announced Monday.

Docs:

  • Bill: It points out on this page that the diagrams haven't been updated. Does anyone happen to have these pictures in an editable format?
    (Nobody has this...needs to be recreated) ACTION: Create Issue
  • Bill: This page and all child pages still have under construction notices, but most haven't been changed since last year. Several of the child pages are in pretty obvious need of updating.  ACTION: Create Issue
  • Bill: What's the current status of backend security?  (tick) https://fedora-commons.org/jira/browse/FCREPO-114
  • Bill: Anyone feel like checking this onefor accuracy?  ACTION: Create Issue
  • Chris: On second thought, removed "current version" header text
  • Bill: Title above tree navigation still says "Fedora 3", Dan should know how to fix this.  ACTION: Ask Dan

Misc:

  • Client Jars as part of release (fedora-client-3.2.jar, fedora-messaging-client-3.2.jar)? (Bill)
    For fedora-client-3.2.jar, we'll wait 'till old admin gui is removed, fedora-messaging has dependencies.  When we move to maven, this will be easier to do for future releases.
  • 2.x Announcement (Chris) - ACTION: Send to list

Mailing List Guidelines

Adopt ASF tips?  Or Jakarta Guidelines?

 AWS Community Guidelines
 http://developer.amazonwebservices.com/connect/guidelines.jsp
 Ubuntu Code of Conduct
 http://www.ubuntu.com/community/conduct

Agreed to use a copy of existing guidelines.  Jakarta looks good to Bill and Chris so far, but team will look deeper.

(general discussion of off-topic posting, crossposting, etc)

Kai suggested the use of a web forum for question/answer type discussions.

We talked about the general use of the mailing lists and came up with a proposal:

  • Get rid of existing fedora-commons-users and fedora-commons-developers lists
  • Replace them with
    • A support forum (with "best answer" type feedback)
    • An announcement list (releases, conferences, jobs, etc)
    • A fcrepo-dev list (just for fcrepo committer/contributor discussion)

OR'09

Chris doing a Tech Overview of Fedora alongside Brad for DSpace on Weds, 10:30-11:30, room 236
Title: Technology Overview - New Releases and Roadmaps for DSpace and FedoraAbstract: In this session, the technical leaders of DSpace and Fedora will provide technical overviews of both platforms, including new software releases and roadmaps.  The unveiling of DSpace 2.0 is a significant milestone in the DSpace community.  Brad will discuss the new modular architecture and provide highlights of the 2.0 software release.  Fedora developers have been focusing on a range of new features motivated by improved storage abstraction, lightweight web-orientation, and interoperability.  Chris will provide an overview of these new directions and discuss key features in the new Fedora 3.2 release.  After their software updates, Brad and Chris will present the DSpace and Fedora roadmaps and discuss future synergistic opportunities across the two platforms.

Team brainstormed what we can do at Fedora Developer Open House session

When: Weds, 11:30am-12:15pm
Where: Rooms 330,331, Georgia Tech Global Learning Center

  • Format: Panel or "circle of chairs" depending on size
  • Possible Topics:
    • What's new in 3.2
    • Vision: What we'd like the dev community to look like
      • Want: active community around plugin development
      • Want: empowered community: if something needs doing, can jump in and do it.
      • Want: diverse community w/r/t areas of expertise and dev environments
    • Roadmap:
      • committer priorities: maven for builds, osgi/springdm for pluggability. we think this will make contribs easier (experiences?)
      • priorities of other developers in the community?
    • New Process to Participate:
      • What exists
      • What to change
    • Workflow?  Minimal capability - what would be useful?
    • Fed"or"ation?
  • Icebreakers:
    • Who's built from source?
    • Who's made local changes?  Tried to contribute?
  • Goal:
    • Individuals more inclined to contribute

Misc Other Stuff

  • Chris went through part 1 of this tutorial on OSGi.  Grokking it: lots of similarities between Fedora's current "Module" approach.
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels