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)
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)
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