Difference between revisions of "Developer Retreat 2014"

Revision as of 06:36, 23 July 2014

Planning for the 2014 Developer Retreat

About participation

• All developers (Ryan, Dan, Daisie, Nathan) will be participating throughout the meeting.
• It is assumed that Todd and Bill will also participate throughout the entire meeting, except for their grant administration meeting on Monday afternoon.
• Martin will participate as time allows, most likely in the morning sessions.
• Other participants are noted in the relevant sections.
• Start time is 9am both days; will run to 5-5:30pm.
• Possible group dinner on Monday night.

Monday Morning

9:00am Introductions, Brief review of Development Roadmap and Strategic Plan

9:15am General team issues:

• Extra participants: Hilmar, Jamie, Erin, Elizabeth, Jane?
• General team communication:
  • Should we encourage the entire team to use slack?
  • Should we allow/invite external developers to use slack?
• Improving communication with staff who "own" features/bugs (Erin)
• Making it easier for non-developers to edit the website (Elizabeth)
• Social media coverage (Jamie)
  • Review policies for announcements and communication with end-users.
  • Are there niches we're not hitting? (Google Plus?)

10:30am break

10:45am Support for curation (Elizabeth)

• Extra participants: Erin, Elizabeth, Jane?
• Detailed planning for curation scaling
• Review plans for workflow/communication as work moves to Drexel
• Communication between developers and curators
  • Brainstorm to identify common use cases for communication
  • What communication mechanism is best for each use case?
  • How to best handle urgent items?
  • How to notify curators of feature deployment schedule?
  • Should curators use slack?

Monday afternoon

1pm Submission system issues (Elizabeth)

• Extra participants: Erin, Elizabeth, Jamie
• Review the submission system interface -- overall workflow and usability
  • This could potentially be a substantial agenda item where we walk through the system screen by screen
• Requirements gathering for redesign review workflow (Daisie)

2:45pm break

3pm Support for near-term development projects:

• Preparing for DSpace 4.0 upgrade. Analyze test coverage and determine tests that need to be in place for a smooth upgrade. (Dan)
• (if needed) Further review/planning for ORCID work. (Ryan/Todd)
• Discuss potential UI designs for integrating DataONE search into Dryad search interface. (Nathan)

Tuesday Morning

9am Development planning for next year (Ryan)

• Support for general scalability
  • Effects of greater usage/downloads
  • Effects of greater submissions
  • Effects of greater journal integrations
• Fleshing out details for development activities in year 1 & 2 of the strategic plan.
• Timeline and resources required for all development activities on the strategic plan.
• Re-organizing the Development Roadmap to align with the Strategic Plan

'10:30am Break (Todd/Bill have scheduled a call)

Tuesday Afternoon

1pm Future of the Dryad software platform:

• Extra participants: Jim Tuttle?, Hilary Davis?
• Review/brainstorm long-term requirements for a development platform.
• Review available technology platforms.

2:45pm break

3pm Leftover issues, opportunistic issues, wrapup

Extra topics

These topics were suggested, and may be addressed as time permits. However, they can be addressed in other meetings.

• Reporting
  • Review reports that are currently sent. For each report:
    • does the report meet our needs?
    • who is responsible for creating it? is there a backup person?
    • can we automate the report?
• Document management plans -- wiki, Google docs, Dropbox
• Project management tools / methods (Trello, FogBugz, etc.)
  • Gather requirements
  • Note that a full change may need to wait until we hire an executive director.