#ansible-meeting: AnsibleFest Contributors Summit: Morning Session

Meeting started by gundalow at 13:02:19 UTC (full logs).

Meeting summary

  1. Intro (gundalow, 13:03:09)
    1. https://bluejeans.com/7480904391 (gregdek, 13:06:16)
    2. https://etherpad.openstack.org/p/ansible-summit-atlanta-2019 (dmsimard, 13:06:39)
    3. https://etherpad.openstack.org/p/ansible-summit-atlanta-2019-general-session (gregdek, 13:06:43)

  2. Data Presentation (Greg Sutcliffe ) (gundalow, 13:09:26)
    1. gwmngilfen is giving a presentation on using data to understand community structure and aid governance (gundalow, 13:11:00)
    2. Ideas on how to use this data, ie what questions we should ask? (gundalow, 13:15:01)
    3. ACTION: gundalow to give gwmngilfen updated list of committers (gundalow, 13:15:27)
    4. we will be pulling web stats from docs.ansible.com to add to the stats on module usage (gundalow, 13:20:49)
    5. We have stats to show the 80% merge time for various labels. The stats confirm that label/P1 and label/P2 get merged faster than others. Likewise label/bugs get merged faster than label/feature (or label/new_module) (gundalow, 13:22:06)
    6. the merge time stats allows you to pick any two labels to compare (gundalow, 13:22:44)
    7. We also have some stats on http://ansible.meetup.com (gundalow, 13:25:39)
    8. http://stats.eng.ansible.com/apps/ (gregdek, 13:29:15)

  3. Roadmap with Dylan Silva (gregdek, 13:33:31)
    1. thaumos / Dylan contributed to 0.12 in June 2012 and has been making trouble fo us ever since (gregdek, 13:34:24)
    2. ACTION: gregdek to clean his keyboard (gregdek, 13:35:00)
    3. ACTION: jtanner to clean his keyboard (gregdek, 13:36:39)
    4. no preso on screen for this session (gregdek, 13:37:50)

  4. Open Questions / Q+A about collections (gregdek, 13:39:08)
  5. Open Questions / Q+A about Core roadmap / collections (gregdek, 13:39:21)
    1. question: what will go into ansible core and what will stay in collections? (gregdek, 13:39:41)
    2. answer: all "content" will go into some kind of collection (gregdek, 13:40:07)
    3. https://github.com/ansible-collections (bcoca, 13:44:41)
    4. galaxy will be the way for users to get "a la carte" content if they so choose (gregdek, 13:45:18)
    5. initially, current idea for community collections will likely be in a single repo and multiple collections, will discuss later in dedicated collections session (gregdek, 13:46:05)
    6. chouseknecht is discussing galaxy (gregdek, 13:57:41)
    7. geerlingguy is asking questions about ui of galaxy (gregdek, 13:59:14)
    8. searchabilityt of collections will be key (gregdek, 13:59:52)
    9. ACTION: gwmngilfen should have basic stats for collections in galaxy (gregdek, 14:00:27)
    10. ACTION: gregdek to think about stats on growth of collections and usage rate (gundalow, 14:00:48)
    11. maybe 10-30 people don't know what ansible-test is (gundalow, 14:01:32)
    12. `ansible-test` is what does all the work when you push a PR to ansible/ansible (gundalow, 14:02:40)
    13. https://github.com/ansible/ansible/tree/devel/test ? (dmsimard, 14:03:16)
    14. ansible-test is in the github.com/ansible/ansible (ie main) repo (gundalow, 14:03:26)
    15. https://docs.ansible.com/ansible/devel/user_guide/collections_using.html (bcoca, 14:09:56)
    16. https://docs.ansible.com/ansible/devel/user_guide/collections_using.html (bcoca, 14:10:17)
    17. https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html (bcoca, 14:10:25)

  6. Collections (gundalow, 14:30:13)
    1. https://etherpad.openstack.org/p/ansible-summit-atlanta-2019-general-session line 69 (gundalow, 14:30:38)
    2. proposal: new collection format for community collections: one repo, many collections (gregdek, 14:32:41)
    3. proposal: net new plugins will go into the new community collection (gregdek, 14:33:24)
    4. one of the initial structures for Community Collections will be ~21 collections, matching the top level directories from https://github.com/ansible/ansible/blob/devel/lib/ansible/modules (ie cloud_community, clustering_community, crypto_community, ...) (gundalow, 14:34:00)
    5. For now the Ansible Community Collections will live under github.com/ansible/ (gundalow, 14:35:03)
    6. The repository where a Collection lives could be anywhere, no requirement to be under GitHub. Ansible will continue to develop on GitHub (gundalow, 14:38:23)
    7. module_utils will be forked. (gregdek, 14:43:30)
    8. we're going to have to make sure that upstream and downstream are in sync, and that is on us to keep pace. (gregdek, 14:43:54)
    9. we will not necessarily fork mod_utils, but we must have the ability to do so, and if we do, maintaining upstream/downstream relationship will be critical (gregdek, 14:46:26)
    10. FYI #ansible-docs https://github.com/ansible/community/wiki/Docs (gundalow, 14:47:20)
    11. question in the room: will there an option to say "this collection is for x versions only"? (gregdek, 14:49:35)
    12. answer: yes, creators can say "this collection version only works for these versions of ansible" -- tooling will eventually restrict, but does not work that way today (gregdek, 14:50:25)
    13. These are all proposals, we need your feedback to help work out what's the right way to move forward (gundalow, 14:52:16)
    14. about dozzen Terraform users in the room (gundalow, 14:55:20)
    15. Only ~dozen people in the room knew what a collection looks like on disk (ie directory structure) (gundalow, 15:00:35)
    16. there were some people in the room that are now more concerned that before (gundalow, 15:06:58)
    17. geerlingguy asks A lot of discussion is about Python and Collections. What about Roles? When are Roles getting new features? (gundalow, 15:09:03)
    18. ~2 two dozen people are excited for Collections (gundalow, 15:17:17)
    19. Requiring documentation for modules has been key to ensuring Ansible's success (gundalow, 15:20:03)
    20. ACTION: gundalow for future Contributor Summits ensure we have a decent webcam/video camera showing the room (gundalow, 15:24:42)
    21. thaumos "licensing sucks" (geerlingguy, 15:35:22)


Meeting ended at 16:45:46 UTC (full logs).

Action items

  1. gundalow to give gwmngilfen updated list of committers
  2. gregdek to clean his keyboard
  3. jtanner to clean his keyboard
  4. gwmngilfen should have basic stats for collections in galaxy
  5. gregdek to think about stats on growth of collections and usage rate
  6. gundalow for future Contributor Summits ensure we have a decent webcam/video camera showing the room


Action items, by person

  1. gregdek
    1. gregdek to clean his keyboard
    2. gregdek to think about stats on growth of collections and usage rate
  2. gundalow
    1. gundalow to give gwmngilfen updated list of committers
    2. gundalow for future Contributor Summits ensure we have a decent webcam/video camera showing the room
  3. gwmngilfen
    1. gundalow to give gwmngilfen updated list of committers
    2. gwmngilfen should have basic stats for collections in galaxy
  4. jtanner
    1. jtanner to clean his keyboard


People present (lines said)

  1. gregdek (103)
  2. bcoca (81)
  3. gundalow (75)
  4. felixfontein (62)
  5. abadger1999 (57)
  6. jtanner (46)
  7. geerlingguy (45)
  8. mnaser (35)
  9. jimi|ansible (30)
  10. cyberpear (30)
  11. robertdebock (26)
  12. dmsimard (19)
  13. resmo (18)
  14. dmellado (17)
  15. fungi (17)
  16. pabelanger (15)
  17. misc (14)
  18. shaps (12)
  19. zodbot (10)
  20. jborean93 (8)
  21. jillr (8)
  22. alikins (6)
  23. gwmngilfen (5)
  24. maxamillion (4)
  25. BobBoldin (3)
  26. akasurde (2)
  27. chouseknecht (2)
  28. jhawkesworth (2)
  29. webknjaz (2)
  30. ptoal2 (1)
  31. samccann (1)
  32. ptoal (1)
  33. sdoran (1)
  34. smolz (1)
  35. decentral1se (0)
  36. Qalthos (0)
  37. mattclay (0)
  38. andersson007_ (0)
  39. nitzmahone (0)
  40. ganeshrn (0)
  41. sivel (0)
  42. acozine (0)
  43. thaumos (0)


Generated by MeetBot 0.1.4.