=============================================================================================
#ansible-meeting: AnsibleFest Contributors Summit: Community Collections & Community Workflow
=============================================================================================


Meeting started by gundalow at 17:01:49 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/ansible-meeting/2019-09-23/ansiblefest_contributors_summit:_community_collections_&_community_workflow.2019-09-23-17.01.log.html
.



Meeting summary
---------------
* LINK:
  https://docs.ansible.com/ansible/devel/user_guide/collections_using.html#using-collections-in-a-playbook
  (samccann, 17:19:27)
* LINK:
  https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html
  (gundalow, 17:19:51)
* LINK:
  https://docs.ansible.com/ansible/devel/user_guide/collections_using.html
  (gundalow, 17:19:58)
* Need to prioritize user experience over developer experience
  (gundalow, 17:27:16)
* Only Core Team from this room have played with Collections  (gundalow,
  17:30:53)
* there are 20 people in the room  (gundalow, 17:31:09)
* core + ~5 people have looked at some of docs/webinar/blog  (gundalow,
  17:31:25)
* what's the smallest step that allows us to move in the right
  direction. IE can we just move some modules into a collection, the
  move others in later Ansible Release  (gundalow, 17:37:01)
* Some modules have "interesting" cross dependencies. IE VMware modules
  use module_utils/networking  (gundalow, 17:38:27)
* - PR backlog  (samccann, 17:45:39)
  * Core Team can "only" get through 10 old issues/PRs  (gundalow,
    17:48:26)
  * PR review days in IRC - can get through around 50 in a long day.
    (samccann, 17:49:21)
  * ACTION: gundalow Speak to GitHub to see if we can get view count for
    Issues/PRs  (gundalow, 17:51:53)
  * Do we need to get better at saying "no" to incoming feature requests
    (gundalow, 17:56:02)
  * Closing is about expectation management  (gundalow, 17:57:14)
  * a closed issues is just as easy to find as an open issue. AND makes
    the open issues easier to find  (gundalow, 17:57:48)
  * LINK: http://dash.tannerjc.net/graph Query: repo ansible/ansible
    Tick backlog  (ptoal, 18:22:55)
  * LINK:
    https://tannerjc.net/wiki/index.php?title=Ansible_Developer_Filament
    (jtanner, 18:32:11)

Meeting ended at 18:33:41 UTC.




Action Items
------------
* gundalow Speak to GitHub to see if we can get view count for
  Issues/PRs




Action Items, by person
-----------------------
* gundalow
  * gundalow Speak to GitHub to see if we can get view count for
    Issues/PRs
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* bcoca (77)
* abadger1999 (59)
* geerlingguy (52)
* felixfontein (36)
* gundalow (31)
* samccann (30)
* cyberpear (27)
* fabianvf (13)
* rharolde (7)
* zodbot (6)
* sivel (4)
* ptoal (4)
* clarkb (3)
* misc (3)
* acozine (2)
* jtanner (2)
* braindeaddev (1)
* mnaser (1)
* gregdek (1)
* FragmentedPacket (1)
* sdoran (0)
* dmsimard (0)
* jborean93 (0)
* jimi|ansible (0)
* mattclay (0)
* jillr (0)
* nitzmahone (0)
* ganeshrn (0)
* alikins (0)
* akasurde (0)
* madonius (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot