Skip to content

Document how we approach productionisation projects #58

@adamltyson

Description

@adamltyson

As discussed in the planning meeting, we should document our approach to internal productionisation projects.

These projects are important because:

  • In theory we can have a large impact with relatively little work (applying our existing infrastructure is quick)
  • Build relationships within SWC/GCNU
  • Improves SWC outputs
  • They're interesting

However, these projects have disadvantages:

  • Can be poorly scoped from the beginning, and this can creep
  • Collaboration with researchers can be difficult (differing skills, priorities, available time etc)
  • Hard to know when they're "done"
  • Often take more time than planned

It would be useful to write a document (web page/blog post etc) to:

  • Show off our success stories
  • Give researchers an idea of what we could do to help with their s/w
  • Set expectations of time commitments, level of assistance etc

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions