...
- Indicates who took minutes -
- Call-in: Google-hangout at:
Goals
- Get Giulia on-board
- Acceptance testing
- User documentation
- Revitalize "metrics"
- Bring unit tests over 70%
Minutes
Goals Discussion
- This is Giulia's first Fedora code sprint, so one of the main goals is to get her up to speed on the project and the development processes
- Acceptance testing should focus on features that support UC Berkeley use cases
- There is a lot of user documentation, so Giulia will focus on the docs related to other issues in the sprint
- We have seen an renewed interest in Metrics recently, so now is a good time to revisit it in the Fedora 4 context
- Unit test coverage has been dropping lately, so we need to bring it back above 70% (at a minimum)
Tickets Discussion
- Establish developer environment
- https://www.pivotaltracker.com/story/show/77114002
- IRC, mailing list, etc.
- Giulia will use a Windows environment, mostly to test that Windows is fully supported
- If she runs into too many problems she may switch to Mac or Linux
- 'Remove redundant jms-indexer:reindex() method'
- https://www.pivotaltracker.com/story/show/76839922
- Simple initial task to walk through the process
- 'Acceptance test: locking'
- 'Unit test: metrics.ReporterFactory'
- https://www.pivotaltracker.com/story/show/77113576
- Improve unit test coverage
- Get familiar with metrics capability
- Acceptance test: large files
- https://www.pivotaltracker.com/story/show/77112490
- UC Berkeley is interested in federation, so Giulia will investigate this task in that context
- Metrics: demonstrate functionality
- Review user documentation for gaps
- https://www.pivotaltracker.com/story/show/76247526
- Focused on features in other tickets in this sprint
- Metrics: user documentation
- Acceptance test: triplestore
- Acceptance test: Federation over many files
- David to create ticket