Table of Contents

Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

  • Time: 11:00am Eastern Daylight Time US (UTC-4)
  • ReadyTalk:
    • U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
    • International toll free:
      • http://www.readytalk.com/intl
      • Use the above link and input 2257295 and the country you are calling from to get your  country's toll-free dial-in number
      • Once on the call, enter participant code 2257295
  • IRC:

Attendees

Agenda

  • Fedora 3.7 Test Plan
  • Open
    • Code key signing
    • Fedora4 RoadMap review?
    • Install fest?
    • Acceptance testing?
    • Input to coming face-to-face steering meeting?
    • Other?
      • Can we document additional Fedora4 practices?
        • project descriptions in POMs (sufficient for dependency work)
        • pull request procedure
        • package level javadoc?
        • template project w/minimal POM dependencies for integration tests
    • RDF streaming inside the fcrepo4 kernel

Previous Actions

Minutes

  1. Fedora 3.7.0 status update - Ben
    1. Windows testing completed
    2. signings are next
      1. what is the minimal set of signers? ( see Fedora Contributors )
      2. clarifying the documentation ( link )
      3. renewing the web of trust might be a good idea going forward
    3. action items:  Andrew will sign Ben's key; Adam will check driver's licenses; Ben will email others today 
  2. Documenting additional Fedora4 features - Greg
    1. features
      1. project descriptions in POMs (sufficient for dependency work)
      2. package level javadoc
      3. pull request procedure
      4. template project with minimal POM dependencies for integration tests
    2. There could be value in creating maven architypes for integration tests and JAX-RS modules
    3. action item:  Andrew will turn list into tickets
  3. Where are the javadocs put now? - Adam 
    1. current status
      1. on fcrepo.org or github page?   maven site can be published to github
      1. Ben said see http://docs.fcrepo.org/
      2. Adam suggested adding sonar stuff 
      3. Greg asked if github is a better place organizationally
    2. action item:  add more stuff to docs site going forward
  4. the breaking out conversation - Adam and Andrew
    1. issues
      1. modules in separate repos 
      2. approach of building the kitchen sink v. adding a special module - Greg
      3. configuration is another topic - Adam
      4. using instead git sub modules to construct own install - Adam
    2. goal:  making it easy to build but keeping it clean
    3. examples:  e.g.  RSS, JMS, webhooks
    4. action item:   clean up github account & create more structure
  5. last week's modeshape 4.0 planning session report - Andrew
    1. Chris and Andrew attended virtually
    2. modularizing items out
  6. wiring things back together again - Andrew
    1. background
      1. Adam will create a wiki page on runtime wiring - Spring or OSGI, or other?
      2. and then there is maven
    2. two different solutions: at runtime or build dependency - strengths and weakness of approaches discussed
  7. Fedora steering group face to face meeting next week in DC (Andrew attending) 
    1. items to bring to the attending of the group: 
      1. how do we make attract developers from the larger Fedora community? 
      2. the roles for non-Java experts, e.g. HTML designing; UI design; prettifying 
      3. roles for smaller commitments of time
        1. help with migration from 3 to 4
        2. volunteers for playing with Fedora4
        3. document FAQs ahead of questions being asked - Greg
        4. repository manager eccentric group hackathon - 
        5. acceptance testing with University of New South Wales call - Andrew
        6. work on documenting and elevating findings
      4. working on broadening the audience 

Actions
#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels