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 another metadata field
• Add a date slider
• Add LDAP authentication (big - follow a recipe)
• Add a badge presenter for items deposited in the last 2 hours (i.e. show a badge that says "Exciting New Stuff!")
• Add a controlled vocab for item condition: broken, abused, poor, fair, good, excellent, unused
• Set up a Oral History work type
• Enable full text indexing
• Add a cinematographer field - http://id.loc.gov/vocabulary/relators/cng.html
• Add a new facet (browse) field - e.g. condition
• Customize which fields are searched
• Update the create_superadmin task to accept an optional display name
• Add a Blurb Writer field - http://id.loc.gov/vocabulary/relators/blw.html
• Add an additional Resource Type to the resource type vocabulary
• Require users to provide a License when depositing a new item
• Add some sample content to the repo (no code required!)

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/curationexperts/laevigata/issues/1192
  • Or This? https://github.com/curationexperts/camper/issues/17