Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-6648

Refresh & unify documentation on writing Tasks

    Details

      Description

      Our current documentation on writing Tasks is fragmentary: it's partially in Doxygen and partially on Confluence. It's also incomplete – or, at least, it doesn't fully and unambiguously specify all the rules, procedures and best practices which developers are expected to bear in mind (see, for example, this discussion).

      Please provide a unified reference document on task construction, explicitly specifying all requirements.

        Attachments

          Issue Links

            Activity

            Hide
            jsick Jonathan Sick added a comment - - edited

            John Swinbank This is well-known and is already being internally planned in the DM-6199 epic, though tickets have not been filled in for it. Thank you for creating the ticket for us. Feel free to add other tickets to that epic in areas you see particular need.

            cc Frossie Economou

            Show
            jsick Jonathan Sick added a comment - - edited John Swinbank This is well-known and is already being internally planned in the DM-6199 epic, though tickets have not been filled in for it. Thank you for creating the ticket for us. Feel free to add other tickets to that epic in areas you see particular need. cc Frossie Economou
            Show
            swinbank John Swinbank added a comment - See also https://community.lsst.org/t/design-principles-for-tasks/895 .

              People

              • Assignee:
                jsick Jonathan Sick
                Reporter:
                swinbank John Swinbank
                Watchers:
                John Swinbank, Jonathan Sick
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: