...
- Longshou
- Finished 'Update GET fcr:sparql to return a SPARQL service description'
- Also finished 'Update repository root RDF serialization to use the standard SPARQL predicate to point at the fcr:sparql service'
- Nearly finished 'Document fcr:sparql "query via url-encoded"'
- Looking for new tickets to work on
- Esme
- 'SPARQL Update fails with PathNotFoundException when node path contains spaces'
- https://www.pivotaltracker.com/story/show/72296804
- Integration tests shows it fails
- Working on this now
- Finding the right place in the ID translation to make sure it gets escaped/unescaped
- 'Get baseURL for JMS events from JAX-RS instead of requiring it be configured separately'
- https://www.pivotaltracker.com/story/show/72351918
- Events are sending the URL, indexer isn’t using it yet
- 'Throw informative exception on invalid Federation'
- https://www.pivotaltracker.com/story/show/73575994
- We’re doing everything we can
- Need to dig into ModeShape to see if there is a bug to file
- Good responses/feedback form ModeShape (within a couple hours)
- Mohamed
- Finished 'Fedora Repository HTTP API Module fails to build without 'clean' due to integration test failure'
- Working on 'Unique IDs in BasicRolesWriterIT and AbstractBasicRolesIT'
- May have some time left over to pick up another ticket
- Hardware resources should be available today to test cluster
- Finished 'Fedora Repository HTTP API Module fails to build without 'clean' due to integration test failure'
- 'SPARQL Update fails with PathNotFoundException when node path contains spaces'
7/17
...
- Found the daily standups useful for getting info from other people
- The RDF type duplicates ticket was very helpful for getting familiar with the code, since it involved several layers of the code.
- Testing tickets didn't help in that way, but were very useful for getting into the testing framework.
...
- Our standups sometimes drag on, and we get into the weeds talking about issues
- Would be much better to identify who can help someone with a problem and let the standup move on.
- Not such a problem for a small number of developers, but would be a bigger problem with more developers on a sprint.
- We sometimes have a lot of active tickets, with one developer working several tickets.
- This sometimes happens when you start a new ticket and get a finished ticket reopened, or for inter-related tickets.
- But it makes it riskier that multiple tickets will be left open at the end of the sprint, and prevents other developers from being able to grab tickets.
- So it's good to keep an eye on this and try to get tickets finished.
...