|author||infinote <email@example.com>||2018-12-12 17:02:45 +0000|
|committer||infinote <firstname.lastname@example.org>||2018-12-12 17:02:45 +0000|
Automated Commit of /meeting-templates/fedora-commops-meeting-next
1 files changed, 2 insertions, 2 deletions
diff --git a/meeting-templates/fedora-commops-meeting-next b/meeting-templates/fedora-commops-meeting-next
index 6ca1d2c..b7f35a0 100644
@@ -58,7 +58,7 @@ If this is your first time at a CommOps meeting, feel free to introduce yourself
#info Choosing a new time for meetings in 2019. Please review the suggested options and let us know your preference if one time works better than another for you to join.
#info === [INCOMPLETE] "jwf File new tickets to discuss / plan out ideas from 2018-12-04 meeting further" ===
-#help If some folks are willing to help with this, it would help to distribute the ticket filing. And then jwf doesn't have to re-explain the original ideas that came from others last week.
+#help If some folks are willing to help with this, it would help to distribute the ticket filing. And then jwf doesn't have to re-explain the original ideas that came from others last week. (this is on the agenda for tickets — we will revisit soon!)
#info ===  "bpabon Create a flowchart based on meeting discussion (around conventions / expectations for filing a CommOps ticket), review at next meeting" ===
@@ -79,7 +79,7 @@ If this is your first time at a CommOps meeting, feel free to introduce yourself
#topic Ticket #159: "Run a "Write the Docs" event targeting Fedora support groups"
-#info Next steps:
+#info Next steps: This ticket is too big. We had several great ideas from last week's meeting about how to divide this up. Let's try to come up with how we want to break this up and file
#topic Ticket #195: "Launch a Teleirc volunteer sysadmin group / SIG"