Data Presentation (Greg Sutcliffe )(gundalow, 13:09:26)
gwmngilfen is giving a presentation on using
data to understand community structure and aid governance(gundalow,
13:11:00)
Ideas on how to use this data, ie what
questions we should ask?(gundalow,
13:15:01)
ACTION: gundalow to
give gwmngilfen updated list of committers(gundalow,
13:15:27)
we will be pulling web stats from
docs.ansible.com to add to the stats on module usage(gundalow,
13:20:49)
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)
the merge time stats allows you to pick any two
labels to compare(gundalow,
13:22:44)
We also have some stats on
http://ansible.meetup.com(gundalow,
13:25:39)
galaxy will be the way for users to get "a la
carte" content if they so choose(gregdek,
13:45:18)
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)
chouseknecht is discussing galaxy(gregdek,
13:57:41)
geerlingguy is asking questions about ui of
galaxy(gregdek,
13:59:14)
searchabilityt of collections will be
key(gregdek,
13:59:52)
ACTION: gwmngilfen
should have basic stats for collections in galaxy(gregdek,
14:00:27)
ACTION: gregdek to
think about stats on growth of collections and usage rate(gundalow,
14:00:48)
maybe 10-30 people don't know what ansible-test
is(gundalow,
14:01:32)
`ansible-test` is what does all the work when
you push a PR to ansible/ansible(gundalow,
14:02:40)
proposal: new collection format for community
collections: one repo, many collections(gregdek,
14:32:41)
proposal: net new plugins will go into the new
community collection(gregdek,
14:33:24)
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)
For now the Ansible Community Collections will
live under github.com/ansible/(gundalow,
14:35:03)
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)
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)
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)
question in the room: will there an option to
say "this collection is for x versions only"?(gregdek,
14:49:35)
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)
These are all proposals, we need your feedback
to help work out what's the right way to move forward(gundalow,
14:52:16)
about dozzen Terraform users in the room(gundalow,
14:55:20)
Only ~dozen people in the room knew what a
collection looks like on disk (ie directory structure)(gundalow,
15:00:35)
there were some people in the room that are now
more concerned that before(gundalow,
15:06:58)
geerlingguy asks A lot of discussion is about
Python and Collections. What about Roles? When are Roles getting new
features?(gundalow,
15:09:03)
~2 two dozen people are excited for
Collections(gundalow,
15:17:17)
Requiring documentation for modules has been
key to ensuring Ansible's success(gundalow,
15:20:03)
ACTION: gundalow for
future Contributor Summits ensure we have a decent webcam/video
camera showing the room(gundalow,
15:24:42)