Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 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

...

  • 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?

...

  • 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)
    Sandy:

OR'09

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

When: Weds, 11:30am-12:15pm

Where: Rooms 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.