Versions Compared

Key

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

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

...

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

OR'09

Team brainstormed what we can do at Fedora Dev Open House session.

  • 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

-asdf

Misc Other Stuff