#openstack-meeting-4: log_wg

Meeting started by Rockyg at 20:01:20 UTC (full logs).

Meeting summary

  1. problems in moving user facing specs forward (Rockyg, 20:09:18)
    1. https://etherpad.openstack.org/p/Operator_Use_Cases (Rockyg, 20:30:02)
    2. ACTION: item: Put two prospective use cases into etherpad https://etherpad.openstack.org/p/Operator_Use_Cases (Rockyg, 20:44:16)
    3. ACTION: item: Advertise use case etherpad to ops to get them to start collaborating on it (Rockyg, 20:44:16)
    4. ACTION: item: work with other xproject wg to write up philosphy of what the user wants out of this openstack "thing" (Rockyg, 20:45:10)
    5. ACTION: item: include a use case for clarifying *why* Error codes are worthwhile implementing (Rockyg, 20:46:18)
    6. ACTION: item: suggest same for request id spec and for API wg (Rockyg, 20:47:10)
    7. What do all these groups, requests have in common? Humans want the information to use in tracking down problems! So make them human! readable (Rockyg, 20:48:24)

  2. open discussion (Rockyg, 20:50:51)
    1. http://stackoverflow.com/questions/16008670/python-how-to-hash-a-string-into-8-digits something like that (jokke_, 21:06:10)


Meeting ended at 21:12:30 UTC (full logs).

Action items

  1. item: Put two prospective use cases into etherpad https://etherpad.openstack.org/p/Operator_Use_Cases
  2. item: Advertise use case etherpad to ops to get them to start collaborating on it
  3. item: work with other xproject wg to write up philosphy of what the user wants out of this openstack "thing"
  4. item: include a use case for clarifying *why* Error codes are worthwhile implementing
  5. item: suggest same for request id spec and for API wg


Action items, by person

  1. openstack
    1. item: Put two prospective use cases into etherpad https://etherpad.openstack.org/p/Operator_Use_Cases
    2. item: work with other xproject wg to write up philosphy of what the user wants out of this openstack "thing"
  2. UNASSIGNED
    1. item: Advertise use case etherpad to ops to get them to start collaborating on it
    2. item: include a use case for clarifying *why* Error codes are worthwhile implementing
    3. item: suggest same for request id spec and for API wg


People present (lines said)

  1. Rockyg (80)
  2. jokke_ (48)
  3. bknudson (37)
  4. dhellmann (18)
  5. openstack (3)


Generated by MeetBot 0.1.4.