Notification time stamped 2020-03-31 18:54:37 UTC
=================================================
#ansible-community: Contributors Summit Hackathon
=================================================
Meeting started by gundalow at 09:02:42 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/ansible-community/2020-03-30/contributors…
.
Meeting summary
---------------
* ACTION: gundalow add `settings.yml` to all Community repos (gundalow,
09:07:33)
* ACTION: every PR in community.general with a changelog fragment will
trigger a *full* CI run. that's really annoying. (gundalow, 10:04:24)
* ACTION: revert
https://github.com/ansible-collections/community.general/pull/71 once
changelog detection has been fixed (gundalow, 10:12:41)
* Contributor Summit recordings will be uploaded to
https://www.youtube.com/channel/UCThD8eHpOt7YdJlzpQRiAvQ (cybette,
11:33:37)
* LINK:
https://github.com/ansible-collections/community.general/blob/master/tests/…
(bcoca, 19:17:59)
* LINK:
https://github.com/ansible-collections/community.general/blob/master/tests/…
<= the one we already generated i mean (bcoca, 19:20:05)
* ACTION: we need ansible-test to validate meta/routing.yml in
collections (do files exists) (gundalow, 07:37:29)
* ACTION: validate-modules deprecation plugin test needs updating for
collections to use meta/routing.yml to check if the file is
deprecated. (gundalow, 07:38:42)
* Playlist for contributor summit recordings:
https://www.youtube.com/playlist?list=PL0FmYCf7ocraJzcnE3-VwVozQ0Zt7vm7z
(cybette, 08:12:56)
* ACTION: template repo needs to include gitignore and galaxy.yml (with
galaxy tags) (gundalow, 08:18:30)
* ACTION: DOCS make it clear that (at least) Ansible managed/co-owned
(what are we calling them) collections MUST be under the same licenses
as ansible/ansible was (gundalow, 08:44:00)
* ACTION: DATA publish all appropriate R code and link to it from
relevant places (gwmngilfen, 08:53:24)
* ACTION: DATA make the config for public apps visible and open for PRs
(gwmngilfen, 10:34:30)
* ACTION: DATA take a stab at differentiating unmaintained from stable
repos, possibly via time-to-1st-comment survival or issues-to-PRs
ratio (gwmngilfen, 11:12:18)
* LINK: https://github.com/ansible/ansible/pull/66920 (see last comment)
(felixfontein, 12:37:17)
* LINK: https://github.com/ansible-collections/community.general/pull/85
<- if anyone wants to have a look/review, please be nice :) (shaps,
13:48:43)
* ACTION: DOCS Collections and 2.9: not really a priority. ansible-base
(2.10) already exists (gundalow, 13:54:11)
* ACTION: DOCS and CI test for `__init__.py` existing (or not?!??!)
under collection's `plugin/` and `tests/utils` directory structure
(gundalow, 14:19:30)
* ACTION: Collection + 2.9 testing (backlog) (gundalow, 14:26:32)
* LINK:
https://github.com/ngine-io/ansible-collection-cloudstack/runs/549147037
(resmo, 15:24:26)
* ACTION: DATA graph new collections over time on Galaxy (gwmngilfen,
15:40:45)
* ACTION: gundalow contact all collection owners to update Unit test
directories; Python imports; ignore.txt (gundalow, 17:20:56)
Meeting ended at 18:54:36 UTC.
Action Items
------------
* gundalow add `settings.yml` to all Community repos
* every PR in community.general with a changelog fragment will trigger a
*full* CI run. that's really annoying.
* revert
https://github.com/ansible-collections/community.general/pull/71 once
changelog detection has been fixed
* we need ansible-test to validate meta/routing.yml in collections (do
files exists)
* validate-modules deprecation plugin test needs updating for
collections to use meta/routing.yml to check if the file is
deprecated.
* template repo needs to include gitignore and galaxy.yml (with galaxy
tags)
* DOCS make it clear that (at least) Ansible managed/co-owned (what are
we calling them) collections MUST be under the same licenses as
ansible/ansible was
* DATA publish all appropriate R code and link to it from relevant
places
* DATA make the config for public apps visible and open for PRs
* DATA take a stab at differentiating unmaintained from stable repos,
possibly via time-to-1st-comment survival or issues-to-PRs ratio
* DOCS Collections and 2.9: not really a priority. ansible-base (2.10)
already exists
* DOCS and CI test for `__init__.py` existing (or not?!??!) under
collection's `plugin/` and `tests/utils` directory structure
* Collection + 2.9 testing (backlog)
* DATA graph new collections over time on Galaxy
* gundalow contact all collection owners to update Unit test
directories; Python imports; ignore.txt
Action Items, by person
-----------------------
* gundalow
* gundalow add `settings.yml` to all Community repos
* gundalow contact all collection owners to update Unit test
directories; Python imports; ignore.txt
* **UNASSIGNED**
* every PR in community.general with a changelog fragment will trigger
a *full* CI run. that's really annoying.
* revert
https://github.com/ansible-collections/community.general/pull/71
once changelog detection has been fixed
* we need ansible-test to validate meta/routing.yml in collections (do
files exists)
* validate-modules deprecation plugin test needs updating for
collections to use meta/routing.yml to check if the file is
deprecated.
* template repo needs to include gitignore and galaxy.yml (with galaxy
tags)
* DOCS make it clear that (at least) Ansible managed/co-owned (what
are we calling them) collections MUST be under the same licenses as
ansible/ansible was
* DATA publish all appropriate R code and link to it from relevant
places
* DATA make the config for public apps visible and open for PRs
* DATA take a stab at differentiating unmaintained from stable repos,
possibly via time-to-1st-comment survival or issues-to-PRs ratio
* DOCS Collections and 2.9: not really a priority. ansible-base (2.10)
already exists
* DOCS and CI test for `__init__.py` existing (or not?!??!) under
collection's `plugin/` and `tests/utils` directory structure
* Collection + 2.9 testing (backlog)
* DATA graph new collections over time on Galaxy
People Present (lines said)
---------------------------
* felixfontein (250)
* gundalow (138)
* shaps (59)
* bcoca (43)
* gwmngilfen (37)
* resmo (36)
* mattclay (27)
* sshnaidm (27)
* Federico87_ (26)
* jtanner (25)
* geerlingguy (20)
* andersson007_ (14)
* dmellado (10)
* misc (9)
* cybette (9)
* zodbot (8)
* zbr (8)
* belfast77 (6)
* tadeboro (5)
* agaffney (4)
* webknjaz (4)
* lillianphyoe (3)
* jhawkesworth (3)
* cyberpear (3)
* fobhep (3)
* abadger1999 (2)
* rmarcand (2)
* samccann (1)
* Pilou (1)
* phips (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBothttps://meetbot.fedoraproject.org/ansible-community/2020-03-30/contributors…
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedorapro…
Notification time stamped 2020-03-31 16:23:51 UTC
===========================================
#ansible-docs: Docs Working Group aka DaWGs
===========================================
Meeting started by acozine at 14:31:56 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/ansible-docs/2020-03-31/docs_working_grou…
.
Meeting summary
---------------
* sanity check (acozine, 14:32:31)
* contributor summit summary (acozine, 14:47:33)
* Contributor summit summary -
https://meetbot.fedoraproject.org/ansible-community/2020-03-29/ansible_cont…
(samccann, 14:47:52)
* contributor summit log -
https://meetbot.fedoraproject.org/ansible-community/2020-03-29/ansible_cont…
(samccann, 14:48:12)
* docs discussions focues on changelog/porting guide optins and how
ansible docs will be handled in the NWO (samccann, 14:51:48)
* changelogs and porting guides from Collections (acozine, 14:54:21)
* LINK:
https://github.com/ansible-collections/overview/issues/18#issuecomment-6039…
for reference (samccann, 15:34:24)
* one idea - we would have two options for collection owners - 1. use
our tool, or 2. use your own solution and provide us with a file
that looks like <proposal>
https://gist.github.com/felixfontein/d15112c7a866e8806d7e9f9ea4085cfa
(samccann, 15:42:13)
* this would require (1) core team has to get the ansible/ansible
changelog generator to output the new format. (2) the community
team would have to write code for the acd changelog generator to
consume the new format (samccann, 15:42:30)
* another idea - we mandate one tool and integrate that tool's output
with core's changelog (aka collections in ACD would not have a
choice but must use this tool) (samccann, 15:45:10)
* - third idea - we link to peoples disparate change logs (least work,
but doesn't give comprehensive view of changes, just a bunch of
links users have to follow) (samccann, 15:46:00)
* - fourth idea - people write an input => input transform + metadata
of what input fragments are needed for the next release. - similar
to first proposal, but there are individual fragments instead of a
container (samccann, 15:46:58)
* fifth idea - we handle ACD like a linux distro - changelogs would be
links. however, there would be a common release notes that
individual components could contribute things they considered major
enough to be worthy of that. (samccann, 15:48:12)
* LINK:
https://github.com/abadger/misc-work/blob/master/ansible/build_acd/acd.in
(abadger1999, 16:11:52)
* ACD as currently envisioned would have 55 collections (samccann,
16:12:38)
* AGREED: we will add the pros/cons for all the ideas here -
https://github.com/ansible-collections/overview/issues/18
(samccann, 16:18:43)
* open floor (acozine, 16:21:51)
Meeting ended at 16:23:51 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* acozine (111)
* felixfontein (87)
* samccann (83)
* abadger1999 (67)
* bcoca (34)
* gundalow (11)
* zodbot (10)
* zbr (2)
* tremble (2)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBothttps://meetbot.fedoraproject.org/ansible-docs/2020-03-31/docs_working_grou…
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedorapro…
Notification time stamped 2020-03-31 15:54:35 UTC
======================================
#fedora-meeting-3: RELENG (2020-03-31)
======================================
Meeting started by mboddu at 15:01:13 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-3/2020-03-31/releng.2020-0…
.
Meeting summary
---------------
* init process (mboddu, 15:01:13)
* #8957 Nonpackagers can review packages (mboddu, 15:04:05)
* LINK: https://pagure.io/releng/issue/8957 (mboddu, 15:04:11)
* Alternate Arch Updates (mboddu, 15:16:48)
* #8690 Can't build module with dependency on module in RHEL - From
fedora-infrastructure (mboddu, 15:37:15)
* LINK: https://pagure.io/fedora-infrastructure/issue/8690 (mboddu,
15:37:21)
* mboddu will schedule a meeting with koji folks to discuss how we can
achieve this (mboddu, 15:47:24)
* Open Floor (mboddu, 15:47:28)
* Next week Tuesday Fedora F32 Final Freeze starts (mboddu, 15:47:53)
Meeting ended at 15:54:35 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (68)
* nirik (46)
* sharkcz (24)
* zodbot (10)
* tdawson (1)
* jednorozec (0)
* pbrobinson (0)
* dustymabe (0)
* pingou (0)
* ksinny (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBothttps://meetbot.fedoraproject.org/fedora-meeting-3/2020-03-31/releng.2020-0…
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedorapro…