From f5240fce9614251a49c13770898481d03ee63efd Mon Sep 17 00:00:00 2001
From: Andri Joos <andri@joos.io>
Date: Thu, 13 Jun 2024 21:16:22 +0200
Subject: [PATCH] fix meeting notes
---
.../meeting-notes.tex | 30 +++++++++----------
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/src/03_project-documentation/meeting-notes.tex b/src/03_project-documentation/meeting-notes.tex
index 77e93d0..368fbd9 100644
--- a/src/03_project-documentation/meeting-notes.tex
+++ b/src/03_project-documentation/meeting-notes.tex
@@ -1,9 +1,9 @@
\chapter{Meeting Notes}
\section{09.02.2024 11:30}
\begin{itemize}
- \item Project is about implementing a chatbot on the SmartEating site
- \item SmartEating is an existing project
- \item Existing team can help with questions regarding the SmartEating application
+ \item Project is about implementing a chatbot in the Smart Eating platform
+ \item Smart Eating is an existing project
+ \item Existing team can help with questions regarding the Smart Eating application
\item Diffrent approaches
\begin{itemize}
\item GTPAgent
@@ -42,14 +42,14 @@
\begin{itemize}
\item Requirements are good so far
\item Long term plan looks good
- \item Unit tests are really recommended, if some user stories need to be dropped, we can do this in an agile was: if there is not enough time to fulfill all, we will drop some
+ \item Unit tests are really recommended, if some user stories need to be dropped, we can do this in an agile way: if there is not enough time to fulfill all, we will drop some
\item Meeting on the 18th march is cancelled due not much progress, as I am in Zivilschutz the week before
\end{itemize}
\section{Sprint 01 Review 06.02.2024 13:30}
\begin{itemize}
\item Progress is according to plan
- \item Long term plan maybe needs some adjustments after the next sprint due to Zivilschutz
+ \item Long term plan may needs some adjustments after the next sprint due to Zivilschutz
\end{itemize}
\subsection{Retrospective}
@@ -97,7 +97,8 @@
\begin{itemize}
\item Webapp backend already has a test project with MSTest
\item No tests available yet for Python/React
- \item React could be also tested
+ \item React could be also tested, but is not implemented yet.
+ Also, this is not needed.
\end{itemize}
\end{itemize}
@@ -216,7 +217,7 @@
\item Git Quality
\begin{itemize}
- \item In the Smarteating project, there are two leftover branches
+ \item In the Smart Eating project, there are two leftover branches
\begin{itemize}
\item For one, a MR is still to be merged, but no further work needed there (I can't merge branches into master because of permissions)
\item The second one is for the chatbot backend, which I didn't manage to finish.
@@ -236,7 +237,7 @@
\end{itemize}
\item Currently working in the webapp backend to connect to chat service
- \item Meeting this week with Abinas to discuss how to connect to llm's
+ \item Meeting this week with Abinas to discuss how to connect to LLMs
\end{itemize}
\section{In-house LLMs 10.04.2024 10:30}
@@ -279,10 +280,9 @@
\item The communication between webapp frontent, webapp backend, as well as the implementation of the OpenAI assistant and chat service is done in \href{https://git.joos.io/ost/ba/project/-/issues/8}{one ticket}.
\item This issue will be closed, as the main focus of this task, the implementation of the OpenAI assistant, is already done
\item A new task will be created to address the communication between the components.
- \item A new user story will be created to address the communication between the components.
\end{itemize}
- \item Long term plan needs an adjustment, to take the previously mentioned issue into account
+ \item Long term plan needs an adjustment to take the previously mentioned issue into account
\end{itemize}
\subsection{Retrospective}
@@ -303,7 +303,7 @@
\item Risk Reevaluation
\begin{itemize}
\item OpenAI model training takes too much time $\rightarrow$ L: 1, C: 1, the OpenAI assistant is good enough with finetuning the instructions, no specifically trained model needed
- \item Lack of experience in the in-house models API $\rightarrow$ C: 1, there is someone working in the SmartEating project, that can help me in case any clarification is needed
+ \item Lack of experience in the in-house models API $\rightarrow$ C: 1, there is someone working in the Smart Eating project, that can help me in case any clarification is needed
\end{itemize}
\item Code Quality
@@ -366,9 +366,9 @@
\item Reasoning why mixtral assistant is implemented with haystack and not langchain or implement in langchain
\item Next tasks:
\begin{itemize}
- \item voice chat
- \item current date \& date per recipe in recipe evaluation to prioritize today's recipes
- \item user information, if there is time to do that
+ \item Voice chat
+ \item Current date \& date per recipe in recipe evaluation to prioritize today's recipes
+ \item User information, if there is time to do that
\end{itemize}
\end{itemize}
@@ -466,6 +466,6 @@
\item Git Quality
\begin{itemize}
\item No leftover branches
- \item One MR is open, which will be reviewed by people in the SmartEating project
+ \item One MR is open, which will be reviewed by people in the Smart Eating project
\end{itemize}
\end{itemize}
--
GitLab