Team Development

Outline

• Introduce yourselves
• Sprint planning - pick and order tickets
• Assign stories
• Get your test suite running
• Push your repo
• Pick a team name
• [OPTIONAL] Rename your repo
• Make a branch
• [OPTIONAL] Write a test
• Write some code
• Make a PR, have someone review your code
• Repeat

Team Development Backlog

• Change the banner image
• Add my team's logo
• Change the application name
• Add git-sha footer https://curationexperts.github.io/playbook/every_project/git_sha.html
• Configure background jobs using sidekiq
• Add another metadata field
• Add date slider
• Add a badge presenter for items deposited in the last 2 hours (i.e. show a badge that says "new")
• Add a controlled vocab for __________
• Add cloud upload ( browse everything )
• Set up an PDF work type ( recipe )
• Configure a pan & zoom viewer (IIIF / Universal Viewer)
• Set up an Audio work type
• Set up an ETD work type (see Mahonia, Laevigata, Alexandria models)
• Add a simple CSV importer
• Enable full text indexing
• Add a cinematographer field - http://id.loc.gov/vocabulary/relators/cng.html
• Add a new facet (browse) field
• Customize which fields are searched
• Customize notification messages
• Configure two-step mediated deposit
• Configure Hydra Role management to support admins
• Use config/role_map.yml to set up an administrator
• Add a Blurb Writer field - http://id.loc.gov/vocabulary/relators/blw.html
• Add deployment scripting ( main website | DCE recipe )
• Set up Travis-CI for your test suite
• Add a Travis badge to the readme
• Add an additional Resource Type on the deposit form
• Require users to provide a License when depositing a new item
• Add some sample content to the repo (no code required!)
• Update the README
• Exclude file name matches from search results

What Makes a good ticket

• A short descriptive title that the whole team can understand:
  • This? https://github.com/samvera/hyrax/issues/3292
  • Or This? https://github.com/samvera/hyrax/issues/3287
• A clear description of the issue being addressed (bugs & tech debt) or the benefit the ticket provides
• The specific conditions under which the work is considered done:
  • This? https://github.com/UCLALibrary/amalgamated-samvera/issues/45
  • Or This? https://github.com/curationexperts/camper/issues/17