summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorinfinote <nobody@fedoraproject.org>2018-12-12 19:13:25 +0000
committerinfinote <nobody@fedoraproject.org>2018-12-12 19:13:25 +0000
commitf9e9e79a5450e40f19b6e003e6030438ee98b9ea (patch)
tree1cdc6a039396cb5bc29e74c74c3f8a25bc59a010
parent4729dea07087bffdde96022d01f3d70eb16e6ecb (diff)
downloadinfinote-f9e9e79a5450e40f19b6e003e6030438ee98b9ea.zip
infinote-f9e9e79a5450e40f19b6e003e6030438ee98b9ea.tar.gz
infinote-f9e9e79a5450e40f19b6e003e6030438ee98b9ea.tar.xz
Automated Commit of /meeting-templates/fedora-commops-meeting-next
-rw-r--r--meeting-templates/fedora-commops-meeting-next27
1 files changed, 26 insertions, 1 deletions
diff --git a/meeting-templates/fedora-commops-meeting-next b/meeting-templates/fedora-commops-meeting-next
index c0653a2..42e3645 100644
--- a/meeting-templates/fedora-commops-meeting-next
+++ b/meeting-templates/fedora-commops-meeting-next
@@ -46,9 +46,25 @@ If this is your first time at a CommOps meeting, feel free to introduce yourself
#topic Action items from last meeting
-#link https://discussion.fedoraproject.org/t/2018-12-04-docs-contributability-tests-and-brainstorming-on-on-boarding/778
+#link https://discussion.fedoraproject.org/t/2018-12-12-may-the-games-begin-game-ifying-the-docs-and-charting-a-path-forward-from-last-week/805
#info How This Works: We look at past #action items from the last meeting for quick follow-up. If a task is completed, we move on to the next one. If it isn't, we get an update and re-action if needed. If no status, we'll try to get a quick update and move forward.
+#info === [] "jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario, ask for Design Team feedback. Due: before 2019" ===
+#link
+#info
+
+#info === [] "bpabon Create a flowchart based on 2018-12-04 meeting discussion (around conventions / expectations for filing a CommOps ticket), ready for review by Wed, Dec. 19th" ===
+#link
+#info
+
+#info === [] "jwf File a new ticket to better document and offer up recurring "easyfix" tasks for CommOps by Wed, Dec. 19th" ===
+#link
+#info
+
+#info === [] "bt0 File a new ticket to create a "Fedora jargon" cheatsheet, to help explain different terms and phrases often used in Fedora (but not obvious to a newcomer or first-timer) by Wed, Dec. 19th" ===
+#link
+#info
+
#info === [] "" ===
#link
#info
@@ -66,6 +82,15 @@ If this is your first time at a CommOps meeting, feel free to introduce yourself
#info
+bpabon File a new ticket to better document procedure and best practices on cross-team communication and collaboration by Wed, Dec. 19th (and maybe add the flowchart from previous action there once it is ready!)
+meskarune File a new ticket for a "cheatsheet" to explain different Fedora tools, apps, and resources and how they are used, by Wed, Dec. 19th
+meskarune File a new ticket for brainstorming docs event "competition" categories and possible prizes to go with them, by Wed, Dec. 19th
+
+#info === [] "" ===
+#link
+#info
+
+
#topic Tickets
#link https://pagure.io/fedora-commops/issues?status=Open&priority=20