=============================================
#ansible-community: Ansible Community Meeting
=============================================


Meeting started by felixfontein at 19:00:53 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/ansible-community/2021-01-13/ansible_community_meeting.2021-01-13-19.00.log.html
.



Meeting summary
---------------
* Agenda https://github.com/ansible/community/issues/539  (felixfontein,
  19:00:53)

* Updates  (felixfontein, 19:00:57)
  *
    https://github.com/ansible/community/issues/539#issuecomment-758845140
    (felixfontein, 19:04:30)
  * reviewing new collections for Ansible 3.0.0 has begun!
    (felixfontein, 19:05:15)

* Collection dependency: avoid unnecessarily strict requirements to
  avoid dependency hell for Ansible building?  (felixfontein, 19:10:49)
  * we have to think how deprecation of collections will work (example:
    community.kubernetes -> kubernetes.core rename)  (felixfontein,
    19:22:13)
  * postpone dependency discussion until someone has a concrete
    suggestion  (felixfontein, 19:22:28)
  * LINK:
    https://github.com/ansible-collections/community.kubernetes/projects/2
    (jillr, 19:25:02)

* Should DOCUMENTATION, EXAMPLES, RETURN be required? (dmsimard)
  (felixfontein, 19:25:18)
  * ACTION: dmsimard to propose a PR for clarifying requirements for
    DOCUMENTATION/EXAMPLES/RETURN so we can vote on it next meeting
    (dmsimard, 19:41:43)

* Should CoC be present in the repository, or is a link to the CoC
  enough? (tadeboro)  (felixfontein, 19:43:09)
  * LINK:
    https://github.com/ansible-collections/collection_template/blob/main/CODE_OF_CONDUCT.md
    (felixfontein, 19:46:56)
  * AGREED: We require at least one of: link in README.md, file
    CODE_OF_CONDUCT.md (can have link or content of CoC)  (felixfontein,
    19:55:50)

* Differentiating between MUST change (blocker) to SHOULD change (nice
  to have, not a blocker) when providing feedback to applicants
  (dmsimard)  (felixfontein, 19:56:56)
  * LINK:
    https://github.com/ansible-collections/ansible-inclusion/discussions/4#discussioncomment-270408
    is how I started.  (tadeboro, 20:01:39)
  * AGREED: Comments must say whether they need to be addressed, or are
    optional.  (felixfontein, 20:24:39)

* Clarify "sanity tests must pass" - specifying `--python` on
  `ansible-test sanity` call can be problematic  (felixfontein,
  20:24:58)
  * AGREED: Add "Collections must run an equivalent of `ansible-test
    sanity --docker`. If they do not use `--docker`, they must make sure
    that all tests run, in particular the compile and import tests
    (which should run for all Python versions). Collections can choose
    to skip certain Python versions that they explicitly do not support;
    this needs to be documented in README.md and in every
    (felixfontein, 20:44:15)

* open floor  (felixfontein, 20:46:21)
  * anyone want to help design the next Contributor summit t-shirt,
    please ping cybette  (cybette, 20:47:44)

Meeting ended at 20:50:35 UTC.




Action Items
------------
* dmsimard to propose a PR for clarifying requirements for
  DOCUMENTATION/EXAMPLES/RETURN so we can vote on it next meeting




Action Items, by person
-----------------------
* dmsimard
  * dmsimard to propose a PR for clarifying requirements for
    DOCUMENTATION/EXAMPLES/RETURN so we can vote on it next meeting
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* felixfontein (168)
* abadger1999 (51)
* dmsimard (40)
* tadeboro (34)
* gundalow (27)
* samccann (27)
* jillr (24)
* acozine (23)
* cybette (18)
* zodbot (13)
* mattclay (11)
* ikhan (6)
* dericcrago (3)




Generated by `MeetBot`_ 0.1.4

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