|author||infinote <email@example.com>||2018-12-12 19:12:13 +0000|
|committer||infinote <firstname.lastname@example.org>||2018-12-12 19:12:13 +0000|
Automated Commit of /meeting-templates/fedora-commops-meeting-next
1 files changed, 14 insertions, 20 deletions
diff --git a/meeting-templates/fedora-commops-meeting-next b/meeting-templates/fedora-commops-meeting-next
index a9f3a8b..c0653a2 100644
@@ -1,4 +1,4 @@
-#startmeeting Fedora CommOps (2018-12-12)
+#startmeeting Fedora CommOps (2018-12-19)
#chair <given to approved members of FAS group at meeting>
@@ -26,7 +26,7 @@ If this is your first time at a CommOps meeting, feel free to introduce yourself
-#info === Fedora Elections in progress - voting closes Thu, Dec. 20 ===
+#info === Fedora Elections in progress - voting closes TOMORROW: Thu, Dec. 20 ===
#info Find candidate interviews on the Community Blog or linked from the voting app. Be sure to get your votes in before the polls close on Thursday, Dec. 20th.
@@ -34,9 +34,9 @@ If this is your first time at a CommOps meeting, feel free to introduce yourself
#info mattdm shares a vision of the future, as discussed last week at the Fedora Council hackfest. The Council is looking for feedback on the proposal.
-#info === "FPgM report: 2018-49" ===
-#info You didn't even have to guess – bcotton has the inside scoop of Fedora development in this week's report. Note the major Red Hat Bugzilla upgrade and the cassandra package maintainers looking for help.
+#info === "" ===
#info === "" ===
@@ -49,23 +49,17 @@ If this is your first time at a CommOps meeting, feel free to introduce yourself
#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 === [INCOMPLETE] "jwf Draft set of user testing scenarios for contributing to docs, create new tickets for each test scenario. Due: before 2019." ===
-#action 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
-#info Note: Another action item to request Design Team feedback is part of the required follow-up for this to be complete. It is now included in this action item.
-#info === [COMPLETE] "jwf Start new Discourse thread about the Dilemma of the Conflicting Meetings" ===
-#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. (this is on the agenda for tickets — we will revisit soon!)
+#info ===  "" ===
-#info === [INCOMPLETE] "bpabon Create a flowchart based on meeting discussion (around conventions / expectations for filing a CommOps ticket), review at next meeting" ===
-#action 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
+#info ===  "" ===
-#info === [PARTIALLY COMPLETE] "jwf Post Discourse summary / do ticket updates from meeting this week" ===
-#info Summary is up, but not all tickets have updates. Some of the things we discussed need new tickets, as per an earlier action item.
+#info ===  "" ===
#info ===  "" ===