Attendees

• Andrew Woods
• David Wilcox 
• Osman Din
• Yinlin Chen

General

• Indicates who took minutes -
• Call-in: Google-hangout at:
  
  • https://plus.google.com/hangouts/_/event/c1glu6soq43r1rr6ou17qtobug8

Meetings

01/16

Sprint planning

01/19

Holiday

01/20

• Andrew
  • Yesterday:
    • Investigated Unable to locate Jira server for this macro. It may be due to Application Link configuration. , F4 creates a new thread (that does not die) with each new transaction.
    • Fedora 3 to 4 Upgration pilot planning
  • Today:
    • Investigating: https://github.com/fcrepo4/fcrepo4/issues/687, Dirty error message
    • Investigate: Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Production Transaction Manager
    • No blockers
• Osman
  • Yesterday: Off.
  • Today:
    • Created PR for  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Plan to look @  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Blockers: None.
• Yinlin
  • Yesterday: Off.
  • Today:
    • Work on Unable to locate Jira server for this macro. It may be due to Application Link configuration. .
      • Reproduce the bug.
      • Identify the code location.
      • Understand the code and start implement.

01/21

• Andrew
  • Yesterday:
    • Completed https://github.com/fcrepo4/fcrepo4/issues/687, Better error response on ill-formatted requests headers (merged)
    • Completed Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Added JBoss Transaction Manager (pending review)
  • Today:
    • Review Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Camel configuration
    • Clean out GitHub issues/PRs
    • Revisit Unable to locate Jira server for this macro. It may be due to Application Link configuration.  Transactions created permanent threads
  • No blockers
• Yinlin
  • Yesterday:
    • Download the latest branch from the github and perform import / export and verify that the Header Location is already the input URL. 
    • Ask Andrew about it and the ticket is solved. 
    • Code location: https://github.com/fcrepo4/fcrepo4/blob/0e4f3a344f95a6233cac0e5e0949fa403f5c4146/fcrepo-http-api/src/main/java/org/fcrepo/http/api/FedoraImport.java
  • Today:
    • Start working on  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Reproduce the bug.
      • Identify the code location.
      • Understand the code, think about solution and then implement.
  • No blockers

01/22

• Fedora Tech Call

• Yinlin
  • Yesterday:
    • Worked on  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Reproduced the bug and confirmed that the nonRdfSource didn’t show the DC information.
      • The nonRdfSource need to add fcr:metadata in the end in order to see the DC information.
      • The code location is https://github.com/fcrepo4/fcrepo4/blob/5c889d110960432167167aa098fb5529ef14fe18/fcrepo-kernel-impl/src/main/java/org/fcrepo/kernel/impl/rdf/impl/PropertiesRdfContext.java
  • Today:
    • Find out how to get nonRdfSourceDescription properties and include that in the PropertiesRdfContext.java.
    • I have a meeting start from 10am, will join Fedora Tech meeting after that meeting.
    • I will work on it this afternoon.
  • No blockers
• Andrew
  • Yesterday:
    • Reviewed Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Camel configuration
    • Cleaned out GitHub issues, and some PRs, more PRs to go
    • Revistied Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Transactions created permanent threads, which appears to have been resolved by  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Re-drafted F4/JVM policy
  • Today:
    • Continue cleaning out old GitHub PRs
      • Review Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Make configuration parameters consistent
      • Verify Modeshape functionality: Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Authorization tooling
      • Verify Modeshape functionality: Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Version labels
  • No blockers
• Osman
  • Yesterday:
    • Investigated Unable to locate Jira server for this macro. It may be due to Application Link configuration. , submitted PR. Details in JIRA ticket.
    • Redid PR for  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  • Today:
    • Will look again at Unable to locate Jira server for this macro. It may be due to Application Link configuration.  to see if any comments, and switch for the time being to Unable to locate Jira server for this macro. It may be due to Application Link configuration. .
  • Blockers: None.

01/23

• Osman
  • Yesterday:
    • Investigated Unable to locate Jira server for this macro. It may be due to Application Link configuration.  further after submitting PR. Awaiting comments or feedback on JIRA on the issue.
  • Today:
    • Working to resolve Unable to locate Jira server for this macro. It may be due to Application Link configuration. .
  • Blockers: None.
• Andrew
  • Yesterday:
    • Sent out Fedora's JVM policy, https://wiki.duraspace.org/display/FF/Policy+-+Supported+JVM
    • Reviewed/Merged  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Reviewed/Sent-back Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Make configuration parameters consistent
    • Verified and closed Modeshape functionality: Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Authorization tooling
    • Verified and closed Modeshape functionality: Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Version labels
    • Tested: Massive blanknode IT: Unable to locate Jira server for this macro. It may be due to Application Link configuration. , there is a bug in the test itself that invalidates the results
  • Today:
    • Wrap up review and merge of:
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Provide feedback on  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Review  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Continue cleaning out old GitHub PRs
  • No blockers
• Yinlin
• • Yesterday:
    • Worked on Unable to locate Jira server for this macro. It may be due to Application Link configuration. .
      • According to the Tomcat log. It looks like when it got the childs from the node, if the child is a binary then it only get FedoraBinary and fetch the jcr:content. However, if we attach fcr:metadata in the request URL, it fetch both NonRdfSourceDescription and FedoraBinary. Any suggestion on this?
  • Today:
    • Continue working on Unable to locate Jira server for this macro. It may be due to Application Link configuration. , target to fix it soon.

01/26

01/27

01/28

01/29

• Fedora Tech Call

• Sprint Wrap-up