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

Create technote describing new metrics system

    XMLWordPrintable

Details

    Description

      jsick has written up our sketch of a plan for the new metrics system. This needs to be turned into a technote to facilitate collaborative doc writing. Said technote will eventually become the guiding document for new developers writing new metrics and specifications.

      Attachments

        Issue Links

          Activity

            Technote imminent.

            Parejkoj John Parejko added a comment - Technote imminent.
            Parejkoj John Parejko added a comment -

            How do we want to handle review of this? We've got something in place, and it's not "complete", but it's enough to start writing an API against (as we've done). Should we ask for a third party to read it over for clarity?

            Parejkoj John Parejko added a comment - How do we want to handle review of this? We've got something in place, and it's not "complete", but it's enough to start writing an API against (as we've done). Should we ask for a third party to read it over for clarity?

            My opinion is that there isn't much value in a review. It's a working document that describes the system we're building and helps us coordinate between each other. And we're continuously improving it. As some point we could put it out for review when the framework has stabilized.

            jsick Jonathan Sick added a comment - My opinion is that there isn't much value in a review. It's a working document that describes the system we're building and helps us coordinate between each other. And we're continuously improving it. As some point we could put it out for review when the framework has stabilized.

            That works for me. Should we merge and close it now, and add tickets for other future changes as they come up? (e.g., defining provenance, checking industry standards for "service level agreement" names, which this is very similar to)

            Parejkoj John Parejko added a comment - That works for me. Should we merge and close it now, and add tickets for other future changes as they come up? (e.g., defining provenance, checking industry standards for "service level agreement" names, which this is very similar to)
            Parejkoj John Parejko added a comment -

            We've got coherent enough text to start building an API based on this design. Names and API details are likely to evolve, but this is a good start.

            Parejkoj John Parejko added a comment - We've got coherent enough text to start building an API based on this design. Names and API details are likely to evolve, but this is a good start.

            People

              Parejkoj John Parejko
              Parejkoj John Parejko
              Angelo Fausti, Frossie Economou, John Parejko, Jonathan Sick, Michael Wood-Vasey, Simon Krughoff (Inactive), Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.