===============================================
#ansible-community: Ansible Contributors Summit
===============================================


Meeting started by gundalow at 10:57:51 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/ansible-community/2020-07-06/ansible_contributors_summit.2020-07-06-10.57.log.html
.



Meeting summary
---------------
* Agenda
  https://etherpad.opendev.org/p/virtual-ansible-contributor-summit-july-2020
  (gundalow, 10:58:53)
* Etherpad
  https://etherpad.opendev.org/p/virtual-ansible-contributor-summit-july-2020
  (cybette, 11:08:24)
* Etherpad
  https://etherpad.opendev.org/p/virtual-ansible-contributor-summit-july-2020
  (felixfontein, 11:08:53)
  * Now doing Introductions: Who are you (real name & IRC/GitHub). What
    are you hoping to get from today  (gundalow, 11:10:24)
  * Ansible Code of Conduct
    https://docs.ansible.com/ansible/latest/community/code_of_conduct.html
    (gundalow, 11:10:49)
  * LINK:
    https://drive.google.com/drive/folders/1NDIQlx9olAYSTBfzwquhrFK9bKqP0YSG
    (gregdek, 11:18:23)
  * ACTION: cybette actual Angry Spuds https://www.anonymouspotato.com/
    (gundalow, 11:31:08)

* Recap of what we are doing and why  (gundalow, 11:32:45)
  * Some info on Collections
    https://github.com/ansible-collections/overview/blob/master/README.rst
    (gundalow, 11:39:04)

* ansible-base  (gundalow, 11:44:14)
  * jimi|ansible is now give an overview of `ansible-base`  (gundalow,
    11:44:31)
  * `pip install ansible` will continue to give you a working Ansible
    setup (Core Engine plus modules). `ansible` depends on the new
    `ansible-base` package  (gundalow, 11:45:14)
  * use-cases and criteria for modules being kept in `ansible-base`
    https://github.com/ansible-collections/overview/blob/master/README.rst#q-what-exactly-is-ansible-base-for-and-what-does-it-contain
    (gundalow, 11:46:58)

* new `ansible` package  (gundalow, 11:59:53)
  * You can test this today `pip uninstall ansible  --user && pip
    install ansible==2.10.0a2 --user`  (gundalow, 12:02:10)
  * ACTION: gundalow claim `builtin`
    https://github.com/ansible/galaxy/issues/2432  (gundalow, 12:02:37)
  * we are really interested in if this new package "just works" for
    you.  (gundalow, 12:06:34)

* Collections in Ansible  (gundalow, 12:14:02)
  * Collections in the Ansible 2.10 package:
    https://github.com/ansible-community/ansible-build-data/blob/main/2.10/acd.in
    (gundalow, 12:14:07)
  * IDEA: from geerlingguy -- blog post on ansible 2.10 is coming,
    here's what we're testing and how you can install / help / etc.
    (rbergeron, 12:14:09)
  * Community collections: https://github.com/ansible-collections/
    (gundalow, 12:14:31)
  * Community Collections on Galaxy https://galaxy.ansible.com/community
    (gundalow, 12:15:18)
  * LINK:
    https://github.com/ansible-community/ansible-build-data/blob/main/2.10/acd.in
    (gundalow, 12:39:46)
  * Fedora proven packager policy for reference:
    https://docs.fedoraproject.org/en-US/fesco/Provenpackager_policy/
    (gregdek, 12:47:17)
  * reminder that there is no ACD, only Ansible :)  (gregdek, 12:47:26)

* Community Stats  (gundalow, 13:02:04)
  * Now over to gwmngilfen who's giving some details of how we use data
    and statistics to make informed decisions on Community health
    (gundalow, 13:02:49)
  * You can see the growth (in terms of unique contributors) to the
    collection repos at
    https://stats.eng.ansible.com/apps/collections/contributors/
    (gundalow, 13:13:47)

* Meetups  (gundalow, 13:45:13)
  * cybette (who looks after Ansible Meetups, events and outreach) gives
    an update on meetups  (gundalow, 13:45:44)
  * LINK: https://en.wikipedia.org/wiki/Chaos_Communication_Congress ?
    (gwmngilfen, 13:55:03)
  * LINK:
    https://etherpad.opendev.org/p/virtual-ansible-contributor-summit-july-2020
    (rbergeron, 14:22:07)

* Unconference Planning  (rbergeron, 14:22:38)
  * LINK:
    https://etherpad.opendev.org/p/virtual-ansible-contributor-summit-july-2020
    (rbergeron, 14:23:01)
  * scroll down to Unconference section  (rbergeron, 14:23:14)
  * gregdek elaborated on "how this works"  (rbergeron, 14:23:32)
  * gregdek pitched session on "the bullhorn"  (rbergeron, 14:23:48)
  * carol pitches "virtual conferences" -- even though we can't meet in
    person, we should keep things going so we can stay connected, and
    what can we do virtually to make that happen?  (rbergeron, 14:25:15)
  * multiple volunteers for Testing!  (rbergeron, 14:27:46)
  * Gundalow pitches "how to keep community collections moving"
    (rbergeron, 14:28:21)
  * ACTION: gundalow to fix Bot so links aren't to master  (gundalow,
    14:32:25)
  * rbergeron possibly leading session on improving the proposal process
    assuming it is later in the day  (rbergeron, 14:37:47)
  * alicia pitching D&I session  (rbergeron, 14:37:59)
  * alicia pitching docs in the new world; what do people want, what
    strategies should we be adopting, what help do community members
    need, all topics around documentation  (rbergeron, 14:39:11)
  * robyn gave up on typing all the pitches  (rbergeron, 14:51:12)

* Community Collections contributor workflow  (gundalow, 15:12:52)
  * kubernetes experinces: 5-6 people driving it  (abadger1999,
    15:16:04)
  * kubernetes experiences:  focused on kubernetes so testing is easier
    (abadger1999, 15:16:29)
  * vision: geerlinguy would like to see large collections like
    community.general break up in the  future  (abadger1999, 15:17:30)
  * community.kubernetes testing (Sanity, Integration, Molecule)
    https://github.com/ansible-collections/community.kubernetes/blob/master/.github/workflows/ci.yml
    (gundalow, 15:17:38)
  * gwmngilfen offering his expertise to help collect and anaylze data
    about contributions, bugs, and general health  (abadger1999,
    15:19:05)
  * ACTION: gwmngilfen to look into activity heatmaps  (gwmngilfen,
    15:20:06)
  * ACTION: investigate if we can get Molecule code coverage into
    codecov.io  (gundalow, 15:20:32)
  * Example Code coverage
    https://codecov.io/gh/ansible-collections/community.zabbix/tree/master/ansible_collections/community/zabbix/plugins
    (gundalow, 15:21:30)
  * These issues and PRs will be closed with a note to say "Move to the
    `collection:XXX` repo"
    https://github.com/ansible/ansible/labels/needs_collection_redirect
    (gundalow, 15:22:35)
  * geerlinguy excited to see the separation of core and collections
    when the collection-related issues in ansible/ansible are closed
    (abadger1999, 15:22:59)
  * each issue and PR will be closed with a message to look at the PR
    labels to decide where to move to.  (abadger1999, 15:24:01)
  * a script exists to move prs but not issues.  (abadger1999, 15:24:19)
  * ACTION: cybette to create docs hackathon session for 10am UTC Tue
    (Issues and PR move)  (gundalow, 15:27:23)
  * about 8 networking collection.  All managed by the same team
    (abadger1999, 15:28:54)
  * networking team talks to each other every day  (abadger1999,
    15:29:13)
  * networking team testing: Has a large matrix of devices and python
    versions.  Easier to manage than when it was in ansible/ansible
    (abadger1999, 15:30:45)
  * Example of Grafana's CI running against a matrix of Grafana_version,
    Python_version, ansible_version:
    https://github.com/ansible-collections/community.zabbix/blob/master/.github/workflows/plugins.yml#L57-L114
    (gundalow, 15:32:35)
  * LINK:
    https://github.com/ansible-collections/ansible.netcommon/pull/75
    Example of tests running on PRs in network collections  (Qalthos,
    15:33:12)
  * networking team is closing and redirecting issues manually.
    (abadger1999, 15:34:29)
  * taking a set of issues tagged with collection_redirect every week
    and closing in the ansible/ansible repo and reopening in the network
    collection repos.  (abadger1999, 15:35:09)
  * Network Team are manually closing & redirecting issues and PRs. The
    team is working through this list
    https://github.com/ansible/ansible/issues?q=is%3Aopen+label%3Aneeds_collection_redirect++label%3Anetworking
    (gundalow, 15:35:10)
  * networking team handles the issue moving in a one hour meeting every
    week.  (abadger1999, 15:36:00)
  * at 10amET tomorrow's doc hackathon will work on the wording of this
    PR close statement to generalize for closing/moving the big batch of
    stuff still on ansible/ansible -
    https://github.com/ansible/ansible/issues/70374  (samccann,
    15:39:29)
  * Example of human closing and redirecting new issues & PR
    https://github.com/ansible/ansible/issues/70374#issuecomment-651362731
    (gundalow, 15:41:57)
  * for a large colection like community.general... Can we do something
    like: PR gets opened.  No one looks at it for (a week).  Ask if the
    PR submitter would like to become a new maintainer.  (abadger1999,
    15:43:17)
  * ACTION: For issue/pr relocation need to make it clear that "If this
    *is* still relevant, please recreate in the new place  (gundalow,
    15:47:58)

* Diversity and Inclusion  (gundalow, 15:50:12)
  * experience for first-time contributors is important in bringing in
    diverse contributors  (acozine, 15:56:18)
  * D&I slidedeck from mozilla -
    https://docs.google.com/presentation/d/13UxBGj2lI66SLjl6sp4NE3DH2ndT0k5QM0pPyyzZXuY/edit#slide=id.g3240500814_4_74
    (samccann, 15:57:46)
  * Older Mozilla research
    https://docs.google.com/presentation/d/1hsJLv1ieSqtXBzd5YZusY-mB8e1VJzaeOmh8Q4VeMio/edit#slide=id.g43d857af8_0177
    (gundalow, 15:58:02)
  * Mozilla: Contributors who received code reviews within 48 hours on
    their first bug have an exceptionally high rate of returning and
    contributing.  (gundalow, 15:58:14)
  * Mozilla: Contributors who wait longer than 7 days for code review on
    their first bug have virtually zero percent likelihood of returning.
    (gundalow, 15:58:30)
  * : Showing a contributor the next bug they can work on dramatically
    improves the odds of contributing.  (gundalow, 15:58:40)
  * https://opensourcesurvey.org/2017/#insights  (jillr, 15:59:23)
  * for PR review I personally like
    https://sage.thesharps.us/2014/09/01/the-gentle-art-of-patch-review/
    (gundalow, 16:03:40)
  * if you think people aren't using the best (welcoming) language in
    Ansible (IRC, GitHub, etc, etc) please feel free to ping me directly
    and I'll happily educate  (gundalow, 16:05:27)
  * #ansible-diversity exists now, all are welcome  (gundalow, 16:05:44)
  * ACTION: gwmngilfen produce some stats on first-time contributors, cc
    gregdek, gundalow  (gwmngilfen, 16:11:48)
  * consider incorporating review guidelines like
    https://docs.openstack.org/project-team-guide/review-the-openstack-way.html
    (acozine, 16:12:27)
  * ACTION: gwmngilfen stratify contributors along more than
    first/not-first contributor status  (gwmngilfen, 16:14:13)
  * ACTION: acozine to expand
    https://docs.ansible.com/ansible/latest/community/how_can_I_help.html#review-and-submit-pull-requests
    (acozine, 16:15:37)
  * ACTION: jillr to create GitHub issue for D&I  (gundalow, 16:26:40)
  * ACTION: jillr to add D&I into next issue of The Bullhorn  (gundalow,
    16:27:01)
  * https://github.com/ansible/community/wiki/Diversity  (jillr,
    16:29:32)

* Documentation in the new world order  (gundalow, 16:30:48)
  * ACTION: gundalow to speak to gregdek about throwing more $$$ at
    Shippable  (gundalow, 16:33:36)
  * LINK:
    https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html#
    (acozine, 16:40:42)
  * LINK:
    https://docs.ansible.com/ansible/devel/community/contributing_maintained_collections.html#contributing-maintained-collections
    (acozine, 16:40:55)
  * LINK:
    https://docs.ansible.com/ansible/devel/user_guide/collections_using.html
    (acozine, 16:41:04)
  * example of how the generated collections docs look -
    https://toshio.fedorapeople.org/ansible/docsite/collections/
    (samccann, 16:50:31)
  * Docs working group https://github.com/ansible/community/wiki/Docs
    (cybette, 16:52:54)
  * https://github.com/ansible-community/antsibull is where the docs
    pipeline lives  (acozine, 16:57:00)
  * LINK: https://puppet.com/docs/puppet/latest/puppet_index.html
    (baptistemm, 17:03:42)
  * LINK: https://docs.ansible.com/ansible/devel/index.html   (samccann,
    17:03:49)
  * Link for Bullhorn Outline issue #6:
    https://docs.google.com/document/d/1CS8Y6CpBriwyNfL5nwnQ03pQ6bJiAtLJnyqaINnE4x8/edit
    (gregdek, 17:05:01)

* The Bullhorn: The Ansible Community newsletter  (gundalow, 17:06:34)
  * Docs Working Group info:
    https://github.com/ansible/community/wiki/Docs  (acozine, 17:07:07)
  * gregdek is now talking about the Ansible Bullhorn  (gundalow,
    17:11:27)
  * ACTION: cybette to subscribe ansible-devel to The Bullhorn
    (cybette, 17:13:43)
  * We want more content on Ansible Working Groups  (gundalow, 17:16:54)
  * ACTION: gregdek add "New Collections" list community.proxysql,
    community.digitalocean  (gundalow, 17:17:39)
  * ACTION: gregdek will move outline of Bullhorn #6 to
    ansible/community repo issue (and post that link in the next
    Bullhorn!)  (gregdek, 17:22:52)
  * IDEA: where to promote The Bullhorn? Templated slide decks for
    virtual meetups; reddit; twitter (@ansible + individuals); linkedin;
    etc.  (rbergeron, 17:25:41)
  * ACTION: gregdek Slide template for Virtual Meetups  (gundalow,
    17:26:50)
  * LINK: https://twitter.com/AnsiBull/status/654991717725138944
    (rbergeron, 17:26:59)
  * ACTION: rbergeron to ask Jim to promote The Bullhorn  (gundalow,
    17:28:36)
  * Where do people discuss Ansible
    https://github.com/ansible/community/issues/525  (gundalow,
    17:29:14)
  * List of Ansible notification modules
    https://docs.ansible.com/ansible/2.9/modules/list_of_notification_modules.html
    (gundalow, 17:30:50)
  * ACTION: gregdek to see if there are AWX, ansible-lint, Molecule
    updates to include in Bullhorn  (gundalow, 17:36:21)

* Testing Ansible content  (gundalow, 17:50:36)
  * CI where `community.kubernetes` use Molecule
    https://github.com/ansible-collections/community.kubernetes/blob/master/.github/workflows/ci.yml#L67-L99
    (gundalow, 17:52:58)
  * LINK:
    https://docs.ansible.com/ansible/latest/dev_guide/testing_running_locally.html#testing-running-locally
    doesn't say anything about what it's for, how to use it, etc.
    (geerlingguy, 17:57:02)
  * ACTION: Google `ansible-test documentation` needs improving
    (gundalow, 17:57:18)
  * ACTION: We need some "Getting started with ansible-test"  docs in
    https://docs.ansible.com/ansible/latest/dev_guide/testing.html
    (gundalow, 17:58:14)
  * molecule or more complex CI is good for big items like k8 where you
    have to set up some complexity to test it.  (samccann, 17:58:51)
  * ACTION: Need to document where `ansible-test integration` vs
    `molecule` (Requiring external infra) is needed  (gundalow,
    17:58:56)
  * network collections using zuul  (samccann, 17:59:00)
  * but ansible-test is the baseline that has to pass in general to be
    sure 'all the things' like docs etc work  (samccann, 17:59:23)
  * ACTION: need to document that ansible-test is for modules & plugins.
    not for Roles  (gundalow, 17:59:54)
  * molecule also has strong roles support.  (samccann, 17:59:54)
  * ACTION: Maybe write a table of tool vs things they can test.
    (gundalow, 18:00:28)
  * ACTION: - consider adding some tidbits re molecule/test inside the
    collection template in github itself  (samccann, 18:02:29)
  * ACTION: docs: GitHub Actions are good for testing against multiple
    versions of application (API) under test (Grafana, Zabbix).
    Shippable is good where you want to test against multiple Operating
    systems  (gundalow, 18:03:01)
  * some info from geerlingguy on molecule vs ansible-test -
    https://www.jeffgeerling.com/blog/2019/how-add-integration-tests-ansible-collection-molecule
    and
    https://www.jeffgeerling.com/blog/2019/how-add-integration-tests-ansible-collection-ansible-test
    (samccann, 18:04:11)
  * ACTION: Can Molecule generate codecoverage to feed into codecov.io
    (gundalow, 18:04:40)
  * github Actions - from the user perspective, is easy to use/pickup.
    K8 collection is using it.  (samccann, 18:07:44)
  * podman also using github actions  (samccann, 18:08:08)
  * ansible-test, molecule, ansible-lint are tests, zuul, travis,
    shippable are CIs to run those tests  (samccann, 18:14:36)
  * What to run: ansible-test, ansible-lint, molecule, etc  (gundalow,
    18:15:06)
  * scheduling: GitHub Actions, Travis, Zuul, Shippable, etc  (gundalow,
    18:15:31)
  * - how 'popular' are each scheduling tool in opensource may influence
    contributors (aka I know XXX and ansible uses XXX so I can more
    easily contribute)  (samccann, 18:17:09)
  * zuul is good at cross-project testing (aka a change in nxos
    collection doesn't break the ios collection etc)  (samccann,
    18:18:30)
  * Unit tests are often best for `plugins/module_utils` when you want
    to test specific  functions.  Integration tests are often best for
    `plugins/modules` when you want to validate the interaction of a
    module on the system  (samccann, 18:22:27)
  * community.internal_test_tools - a collection for containing tools
    useful for testing collections  (samccann, 18:24:29)
  * ACTION: document `community.internal_test_tools` (what/why) from
    "Developing collections" and "/dev_guide/"  (gundalow, 18:25:22)
  * collection_template repo, which is what we fork when making new
    collection repos
    https://github.com/ansible-collections/collection_template. PR#4 in
    there update the GitHub Action  (gundalow, 18:27:05)
  * unittest with AnsibleModule framework :
    https://github.com/ansible/ansible/blob/devel/test/units/module_utils/conftest.py
    and example using it
    https://github.com/ansible/ansible/blob/devel/test/units/module_utils/basic/test_exit_json.py
    (samccann, 18:29:13)

* Plans for Ansible Galaxy and it's relationship to Automation Hub
  (gundalow, 18:30:47)
  * LINK: https://github.com/ansible/galaxy_ng/issues/58   (geerlingguy,
    18:31:03)
  * LINK: https://github.com/ansible/galaxy/issues/2253   (geerlingguy,
    18:33:02)
  * LINK:
    https://docs.ansible.com/ansible/devel/dev_guide/migrating_roles.html#migrating-roles
    (samccann, 18:37:43)

* Ending up  (gundalow, 18:53:58)
  * THANK YOU EVERYBODY  (gundalow, 18:59:15)
  * Tue & Wednesday is Hackathon in #ansible-community  (gundalow,
    18:59:28)
  * Documentation Hackathon in #ansible-docs 14:00 UTC  (gundalow,
    18:59:58)
  * We will have a hackathon on writing some content for The Bullhorn
    (gundalow, 19:00:14)
  * next two days is also "Open Office Hours", so feel free to ask any
    other questions, or more technical PR review stuff  (gundalow,
    19:01:47)
  * ACTION: Write summary of Contributor Summit in Bullhorn draft
    (gundalow, 19:03:29)

Meeting ended at 19:03:42 UTC.




Action Items
------------
* cybette actual Angry Spuds https://www.anonymouspotato.com/
* gundalow claim `builtin` https://github.com/ansible/galaxy/issues/2432
* gundalow to fix Bot so links aren't to master
* gwmngilfen to look into activity heatmaps
* investigate if we can get Molecule code coverage into codecov.io
* cybette to create docs hackathon session for 10am UTC Tue (Issues and
  PR move)
* For issue/pr relocation need to make it clear that "If this *is* still
  relevant, please recreate in the new place
* gwmngilfen produce some stats on first-time contributors, cc gregdek,
  gundalow
* gwmngilfen stratify contributors along more than first/not-first
  contributor status
* acozine to expand
  https://docs.ansible.com/ansible/latest/community/how_can_I_help.html#review-and-submit-pull-requests
* jillr to create GitHub issue for D&I
* jillr to add D&I into next issue of The Bullhorn
* gundalow to speak to gregdek about throwing more $$$ at Shippable
* cybette to subscribe ansible-devel to The Bullhorn
* gregdek add "New Collections" list community.proxysql,
  community.digitalocean
* gregdek will move outline of Bullhorn #6 to ansible/community repo
  issue (and post that link in the next Bullhorn!)
* gregdek Slide template for Virtual Meetups
* rbergeron to ask Jim to promote The Bullhorn
* gregdek to see if there are AWX, ansible-lint, Molecule updates to
  include in Bullhorn
* Google `ansible-test documentation` needs improving
* We need some "Getting started with ansible-test"  docs in
  https://docs.ansible.com/ansible/latest/dev_guide/testing.html
* Need to document where `ansible-test integration` vs `molecule`
  (Requiring external infra) is needed
* need to document that ansible-test is for modules & plugins. not for
  Roles
* Maybe write a table of tool vs things they can test.
* - consider adding some tidbits re molecule/test inside the collection
  template in github itself
* docs: GitHub Actions are good for testing against multiple versions of
  application (API) under test (Grafana, Zabbix). Shippable is good
  where you want to test against multiple Operating systems
* Can Molecule generate codecoverage to feed into codecov.io
* document `community.internal_test_tools` (what/why) from "Developing
  collections" and "/dev_guide/"
* Write summary of Contributor Summit in Bullhorn draft




Action Items, by person
-----------------------
* acozine
  * acozine to expand
    https://docs.ansible.com/ansible/latest/community/how_can_I_help.html#review-and-submit-pull-requests
* cybette
  * cybette actual Angry Spuds https://www.anonymouspotato.com/
  * cybette to create docs hackathon session for 10am UTC Tue (Issues
    and PR move)
  * cybette to subscribe ansible-devel to The Bullhorn
* gregdek
  * gwmngilfen produce some stats on first-time contributors, cc
    gregdek, gundalow
  * gundalow to speak to gregdek about throwing more $$$ at Shippable
  * gregdek add "New Collections" list community.proxysql,
    community.digitalocean
  * gregdek will move outline of Bullhorn #6 to ansible/community repo
    issue (and post that link in the next Bullhorn!)
  * gregdek Slide template for Virtual Meetups
  * gregdek to see if there are AWX, ansible-lint, Molecule updates to
    include in Bullhorn
* gundalow
  * gundalow claim `builtin`
    https://github.com/ansible/galaxy/issues/2432
  * gundalow to fix Bot so links aren't to master
  * gwmngilfen produce some stats on first-time contributors, cc
    gregdek, gundalow
  * gundalow to speak to gregdek about throwing more $$$ at Shippable
* gwmngilfen
  * gwmngilfen to look into activity heatmaps
  * gwmngilfen produce some stats on first-time contributors, cc
    gregdek, gundalow
  * gwmngilfen stratify contributors along more than first/not-first
    contributor status
* jillr
  * jillr to create GitHub issue for D&I
  * jillr to add D&I into next issue of The Bullhorn
* rbergeron
  * rbergeron to ask Jim to promote The Bullhorn
* **UNASSIGNED**
  * investigate if we can get Molecule code coverage into codecov.io
  * For issue/pr relocation need to make it clear that "If this *is*
    still relevant, please recreate in the new place
  * Google `ansible-test documentation` needs improving
  * We need some "Getting started with ansible-test"  docs in
    https://docs.ansible.com/ansible/latest/dev_guide/testing.html
  * Need to document where `ansible-test integration` vs `molecule`
    (Requiring external infra) is needed
  * need to document that ansible-test is for modules & plugins. not for
    Roles
  * Maybe write a table of tool vs things they can test.
  * - consider adding some tidbits re molecule/test inside the
    collection template in github itself
  * docs: GitHub Actions are good for testing against multiple versions
    of application (API) under test (Grafana, Zabbix). Shippable is good
    where you want to test against multiple Operating systems
  * Can Molecule generate codecoverage to feed into codecov.io
  * document `community.internal_test_tools` (what/why) from "Developing
    collections" and "/dev_guide/"
  * Write summary of Contributor Summit in Bullhorn draft




People Present (lines said)
---------------------------
* gundalow (175)
* felixfontein (136)
* geerlingguy (113)
* samccann (66)
* misc (59)
* baptistemm (59)
* abadger1999 (57)
* gwmngilfen (56)
* rbergeron (48)
* sshnaidm|mtg (47)
* acozine (38)
* gregdek (36)
* sshnaidm|ruck (35)
* resmo (29)
* zodbot (25)
* cybette (23)
* jimi|ansible (19)
* bcoca (16)
* berkhan (13)
* shaps (12)
* anshulbehl (12)
* jillr (12)
* andersson007_ (12)
* persysted (10)
* maxamillion (7)
* rosowiecki (5)
* madonius (4)
* Im0_ (4)
* Pilou (4)
* shertel (3)
* adev (3)
* TKersten (3)
* cyberpear (2)
* Qalthos (1)
* sivel (1)
* dmsimard (1)
* zbr (1)
* pabelanger (0)
* tcraxs (0)
* phips (0)




Generated by `MeetBot`_ 0.1.4

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