Vlad Bastina commited on
Commit
08d44f9
·
1 Parent(s): e4691e6

default report

Browse files
Files changed (1) hide show
  1. app.py +28 -15
app.py CHANGED
@@ -6,6 +6,7 @@ from moviepy import VideoFileClip
6
  import json
7
  from pathlib import Path
8
  import tempfile
 
9
 
10
  def extract_audio(video_path, audio_path):
11
  video = VideoFileClip(video_path)
@@ -95,25 +96,37 @@ If you would like to test without your own meeting video, we can showcase its ca
95
  st.write(response)
96
 
97
  elif video_option == "Use default video":
98
- # Path for default video
99
- video_path = "meeting.mp4"
100
- audio_path = "temp_audio.wav"
101
- extract_audio(video_path, audio_path)
102
 
103
- with st.spinner("Fetching transcript from meeting..."):
104
- meeting_transcript = get_transcription()
105
 
106
- with st.spinner("Uploading video..."):
107
- video_file = client.upload_video(video_path)
108
 
109
- with st.spinner("Processing video..."):
110
- client.wait_for_processing()
 
111
 
112
- with st.spinner("Generating response.."):
113
- response = client.summarize_video(meeting_transcript)
114
 
115
- st.subheader("📜 Report of the meeting:")
116
- st.write(response)
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
117
 
118
 
119
  import streamlit.components.v1 as components
@@ -137,4 +150,4 @@ components.html(
137
  setInterval(sendHeightWhenReady, 1000);
138
  </script>
139
  """,height=0
140
- )
 
6
  import json
7
  from pathlib import Path
8
  import tempfile
9
+ import time
10
 
11
  def extract_audio(video_path, audio_path):
12
  video = VideoFileClip(video_path)
 
96
  st.write(response)
97
 
98
  elif video_option == "Use default video":
99
+ with st.spinner("Loading default video..."):
100
+ time.sleep(2) # Simulate a 2-second delay
 
 
101
 
102
+ st.markdown('''## Engineering Key Review Meeting Report - February 18th, 2021
 
103
 
104
+ ### 1. Attendance & Attention Analysis
 
105
 
106
+ - Attendees included: Eric Johnson (host), Christopher, Lily, Craig, Said, Gary, Max, Megan, Paul, and others.
107
+ - Engagement levels appeared generally high based on active participation and responses to questions. Some discussion topics elicited more engagement than others (e.g., the discussion around MR rate metrics sparked significant back and forth).
108
+ - Eric Johnson shifted to a question-asking role, as he stated as one of his goals for the meeting.
109
 
110
+ ### 2. Meeting Outline
 
111
 
112
+ - **Meeting Breakup Proposal**: A proposal to break up the existing meeting into separate meetings for each department, rotating Security and UX every other month, was discussed and tentatively approved, with plans to monitor its effectiveness.
113
+ - **MR Rate Metrics**: The team discussed the definitions and relevance of the overall and wider MR (Merge Request) rates and the problems, ultimately deciding to focus on the percentage of total MRs coming from the community over time instead.
114
+ - **Postgres Replication Lag**: The team discussed the ongoing issues with postgres replication lag and assigned responsibility, highlighting the need for dedicated resources, performance tuning, and workload improvements.
115
+ - **Defect Tracking and SLOs**: The team discussed the progress of defect tracking and SLO (Service Level Objective) achievement and potential issues with the current measurement approach, focusing on open bugs, especially as it relates to the age of those bugs.
116
+ - **Key Meeting Metrics Review**: The team reviewed the overall key meeting metrics, highlighting the smallest decline in Q4, but also the need to address underlying measurement problems.
117
+ Narrow MR Rate: The team reviewed the narrow MR rate, attributing the below-target performance to vacation days and other events.
118
+
119
+ ### 3. Sentiment Analysis
120
+
121
+ - The overall emotional tone was generally neutral to positive, with a collaborative and problem-solving atmosphere.
122
+ - There were moments of mild frustration surrounding the clarity and usefulness of existing metrics, particularly the MR rate metrics.
123
+ - Enthusiasm was evident when discussing potential solutions and improvements, such as focusing on the percentage of total MRs coming from the community.
124
+ - Agreement was reached on several key actions, such as trying the new meeting rotation and refining the bug tracking metrics.
125
+
126
+ ### 4. Final Summary
127
+
128
+ The Engineering Key Review on February 18th, 2021, was a productive session focused on refining metrics, addressing performance bottlenecks, and improving team structure. The team engaged in open discussions, identified key areas for improvement, and agreed upon actionable steps to drive progress. The overall tone was collaborative, with a focus on data-driven decision-making and continuous improvement.''')
129
+
130
 
131
 
132
  import streamlit.components.v1 as components
 
150
  setInterval(sendHeightWhenReady, 1000);
151
  </script>
152
  """,height=0
153
+ )