gundalow's meeting titled "AnsibleFest Austin: Contributors Summit -
Contributor Experience" ended in #ansible-community
by notifications@fedoraproject.org
Notification time stamped 2018-10-01 21:56:44 UTC
====================================================================================
#ansible-community: AnsibleFest Austin: Contributors Summit - Contributor Experience
====================================================================================
Meeting started by gundalow at 20:12:18 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/ansible-community/2018-10-01/ansiblefes...
.
Meeting summary
---------------
* https://etherpad.openstack.org/p/ansible-community-experience
(gundalow, 20:12:29)
* https://github.com/orgs/ansible/projects/2 (gundalow, 20:19:10)
* New Contributors https://github.com/ansible/community/issues/353
(gundalow, 20:20:38)
* Identify common issues, feed those into Bot, CI etc (gundalow,
20:28:22)
* Speak to the people (gundalow, 20:28:27)
* Add the human touch - Personally great people (gundalow, 20:29:43)
* Docs team are meeting weekly to review docs PRs. They are also aiming
to give a human response and a) request feedback b) close c) fix d)
fix+merge (gundalow, 20:31:39)
* Bot is good for rapid turn around, not for the human touch (gundalow,
20:31:56)
* ACTION: gundalow to follow up with David@cisco about why merging
didn't work (gundalow, 20:33:51)
* take advantage of GitHub's notifications of CONTRIBUTOR.md linking for
new_contributors (gundalow, 20:35:05)
* Add very basic workflow (with links to other docs) into
`CONTRIBUTOR.md` so people will be notified via GitHub UI (gundalow,
20:36:32)
* AGREED: adding a changelog shouldn't block automerge (gundalow,
20:41:19)
* PRs that affect lib/ bin/ contrib/ (but not bin/ansible-test
lib/ansible/release.py) MUST have changelog fragment for stable-x.y
PRs (gundalow, 20:48:38)
* LINK:
https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v...
(felixfontein, 21:00:11)
* Agree (via dev_guide) when we need `fragments` (gundalow, 21:02:49)
* Question: How do we increase testing (gundalow, 21:04:51)
* Question: How do we increase people looking at/testing PRs (gundalow,
21:05:04)
* "Topic of the week" - How to get people together for one purpose
(gundalow, 21:09:57)
* reducing back-and-forth needs to be done (gundalow, 21:15:29)
* What other working groups do we need - Look at PRs per directory.
(gundalow, 21:16:15)
* Use GitHub issues to notify maintainers to see if they would be
interested in setting up a Working Group (gundalow, 21:19:37)
* review maintainers guide (gundalow, 21:21:17)
* The Fedora Project has/had similar problems with reviewing new
packages. There are three former Fedora Project Leaders here, at
ansiblefest that you could pick the brains of: Matt Miller, robyn,
and gregdek (abadger1999, 21:21:17)
* org level github project to make visible the Contributor Experience
action items https://github.com/orgs/ansible/projects/2 (abadger1999,
21:25:11)
* The Fedora Project has/had similar problems with reviewing new
packages. There are three former Fedora Project Leaders here, at
ansiblefest that you could pick the brains of: Matt Miller, robyn,
and gregdek (abadger1999, 21:25:47)
* org level github project to make visible the Contributor Experience
action items https://github.com/orgs/ansible/projects/2 (abadger1999,
21:25:58)
* How did "Active Community Members" find out/get involved. How can we
encuragethat (gundalow, 21:26:32)
* how do we define "active" in the above (gundalow, 21:27:58)
* Post-Contributors Blog post should also make it clear that we aren't
just talking about Python programmers - Link to acozine's talk
(gundalow, 21:29:18)
* Post-Contributors Blog post - Also detail what type of participation
we are looking for (gundalow, 21:29:54)
* Create issue" WG - todo list" 1) Docs 2) PRs without
needs_info/needs_revision 3) Needs test (gundalow, 21:35:32)
* Badges: Mozilla & Fedora - Ask Matthew Miller if they've helped or
not. What are the real rewards (recognition, merge rights, etc)
(gundalow, 21:40:14)
* Lessons learnt from Network Documentation t-shirt game - Multiple
example PRs on same file resulted in continual merge conflicts. Had a
few people that tried to "game" the system (just copy-paste). Next
time: Would timebound it from the start. Add initial limits for
responses from PR authors. More general ensure every module EXAMPLE
has a `- name: ` set (gundalow, 21:45:45)
* Look at https://openbadges.org/ and https://badges.fedoraproject.org/
(gundalow, 21:49:02)
* Badges/points for doing X each week. Number of weeks X was done.
Number of continuous weeks where X was don e (gundalow, 21:52:40)
* what are the rewards (gundalow, 21:53:38)
* LINK:
https://www.redhat.com/archives/fedora-devel-list/2004-May/msg00104.html
(abadger1999, 21:55:10)
Meeting ended at 21:56:43 UTC.
Action Items
------------
* gundalow to follow up with David@cisco about why merging didn't work
Action Items, by person
-----------------------
* gundalow
* gundalow to follow up with David@cisco about why merging didn't work
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* gundalow (46)
* felixfontein (37)
* misc (27)
* bcoca (19)
* abadger1999 (19)
* zodbot (7)
* acozine (1)
* jlk (1)
* mattclay (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
https://meetbot.fedoraproject.org/ansible-community/2018-10-01/ansiblefes...
--
You received this message due to your preference settings at
https://apps.fedoraproject.org/notifications/fmnmeetingminutes.id.fedorap...