Attendees

General

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

01/22

 

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

  • Osman
    • Yesterday:
      • Working on comments regarding PR for Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Today:
      • Working/testing the re-opened ticket, have pushed some updates to address the comments & will push more
    • Blockers: none
  • Andrew
    • Yesterday:
      • Reviewed/Re-opened  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Provided feedback on and closed  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Reviewed and merged:
        • Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Load tested bulk ingest with: plain, RDF, and blanknode resources - results pending
    • Today:
      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Finalize OR2015 proposals
      • Draft FAQ wiki page: How to Model a Book
    • No blockers
  • Yinlin
    • Yesterday:
      • Create pull-request on  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Today:
      • Continue working on Unable to locate Jira server for this macro. It may be due to Application Link configuration.  based on Andrew’s comments. 
    • Blockers: Sent in email. Please check when you have time.

01/27

  • Yinlin
    • Yesterday: 

      • My current change can show the child binary node’s DC info, however still need to append node information. 

    • Today: 

      • Figure out how to append node in allProperties and add integration test.

  • Andrew
    • Yesterday:
      • Reviewed and merged: Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      • Completed: Unable to locate Jira server for this macro. It may be due to Application Link configuration. , Indexing wiki docs

      • Drafted FAQ wiki page: How to Model a Book

    • Today:

      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      • Finalize OR2015 proposals

    • No blockers

  • Osman
    • Yesterday:
      • I have updated the PR for yesterday’s work, and closed the ticket I was working on for review. 
    • Today:
      • If I have any other updates in the meantime, I’ll update JIRA. Otherwise, I’ll be offline and most likely to be back on the grid on Wednesday.

01/28

  • Yinlin
    • Yesterday:
    • Today:
      • Write unit test and integrate test for  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Reduce some major issues in Unable to locate Jira server for this macro. It may be due to Application Link configuration. .
    • No blockers
  • Andrew
    • Yesterday:
      • Reviewed and sent back:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Reviewed and merged:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Reviewed and merged:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Reviewed and merged:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Reviewed and merged:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Finalized OR2015 LDP proposal
    • Today:
      • Finalize OR2015 TWG proposal
      • Announce Java 8 requirement starting in April
      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Work: Unable to locate Jira server for this macro. It may be due to Application Link configuration. , wiki docs
    • No blockers
  • Osman
    • Yesterday:
      • off.
    • Today:
      • currently working on responding to Unable to locate Jira server for this macro. It may be due to Application Link configuration.  take 2 review comments.
    • Blockers: none

01/29

  • Andrew
    • Yesterday:
      • Finalized OR2015 TWG proposal
      • Submitted OR2015 Fedora committers workshop proposal
      • Announced Java 8 requirement starting in April
      • Reviewed and merged:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Today:
      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Review and merge:  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      • Work: Unable to locate Jira server for this macro. It may be due to Application Link configuration. , wiki docs
    • No blockers
  • Yinlin
    • Yesterday:
    • Today:
      • Will submit new PR for Unable to locate Jira server for this macro. It may be due to Application Link configuration.  with unit test.
    • No blockers
  • Osman
    • Yesterday:
      • re-did  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Today:
      • doing  Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    • Blockers: None.