#ansible-meeting: ansible public core meeting

Meeting summary

1. A common practice I have seen in modules is that the input parameters are put in the result output dictionary (abadger1999, 19:14:23)
   1. ACTION: dag to PR a guideline to say "do not place params into the module's return value" (abadger1999, 19:17:14)
   
   
2. From time to time new parameters are proposed with the unit as part of the parameter name, (abadger1999, 19:17:19)
   1. https://github.com/ansible/ansible/issues/20160#issuecomment-272053518 (abadger1999, 19:19:43)
   2. https://golang.org/pkg/time/#ParseDuration (sivel, 19:27:08)
   3. AGREED: no 'unit' postfix on options (bcoca, 19:29:15)
   4. ACTION: implement duration and datetime types for argspec (bcoca, 19:29:31)
   5. ACTION: add duration/datetime argtypes to 2.5 roadmap (nitzmahone, 19:30:00)
   6. ACTION: migrate existing 'unit suffixed' options to aliases and make 'unitless' the main focus (bcoca, 19:30:03)
   
   
3. required_by (bcoca, 19:31:29)
   1. https://github.com/ansible/ansible/pull/28662 (dag1, 19:31:37)
   2. ACTION: tabled till 2.5 (bcoca, 19:54:27)
   
   
4. open floor (bcoca, 19:54:46)

Action items

1. dag to PR a guideline to say "do not place params into the module's return value"
2. implement duration and datetime types for argspec
3. add duration/datetime argtypes to 2.5 roadmap
4. migrate existing 'unit suffixed' options to aliases and make 'unitless' the main focus
5. tabled till 2.5

Action items, by person

1. dag
   1. dag to PR a guideline to say "do not place params into the module's return value"
2. UNASSIGNED
   1. implement duration and datetime types for argspec
   2. add duration/datetime argtypes to 2.5 roadmap
   3. migrate existing 'unit suffixed' options to aliases and make 'unitless' the main focus
   4. tabled till 2.5

People present (lines said)

1. bcoca (61)
2. dag1 (60)
3. sivel (38)
4. nitzmahone (28)
5. abadger1999 (25)
6. jtanner (21)
7. mikedlr (14)
8. zodbot (10)
9. rohitkum (2)
10. dag (0)