-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting minutes
The minutes for the meetings held during development will be posted here.
- Héctor Triguero del Río
- Fernando Cachon Alonso
- Daniel Fernández Cabrero
- Umut Dolangac
- Diego Martínez Chamorro
Does not apply.
During this meeting, we agreed to review the application requirements and conduct different research throughout the week. The goal is to have a clearer understanding of the project by the next meeting, so we can start decision-making.
The following tasks were defined during the meeting. Each task includes detailed information such as objectives and sub-tasks, these are accessible through the linked issues:
Important
All except the last have been scheduled to be done before next week.
- Study the requirements of the application
- Create the GitHub Project
- Research about DBMS alternatives
- Research about candidate technologies
- Look into other projects from past years
- Research about WikiData
- Research about LLMs
- Research about PR strategies
- Héctor Triguero del Río
- Fernando Cachon Alonso
- Daniel Fernández Cabrero
- Umut Dolangac
- Diego Martínez Chamorro
We reviewed the work done for the following tasks and we obtained several conclusions.
- Study the requirements of the application: The requirements were discussed and several doubts that have to be asked to the teacher arised, for example the amount of hints or the generation of questions.
- Create the GitHub Project: The project was created successfully.
- Research about DBMS alternatives: We discussed relational and non-relational databases but we concluded we should analyze last year projects to take a decission.
- Research about candidate technologies: After considering pros and cons of different technologies, several where chosen (see Summary).
- Research about WikiData: Last year projects must be analyzed and another API must be researched.
- Research about LLMs: Gemini and Empathy AI were discussed and a demo of Gemini was executed and analyzed, analyze past projects can provide a better perspective.
We closed the following tasks:
We decided to continue working in these tasks:
- Research about DBMS alternatives
- Research about WikiData
- Research about PR strategies
- Look into other projects from past years
During this meeting, we reviewed the work done by each member and we took several decisions:
- Use React as frontend technology.
- Use Node.js as backend technology.
- Use Docker as DevOps technology.
Also, we assigned to each member the different projects from last year to analyze in order to take decisions about DBMSs or the WikiData API, understandig how the project can be done.
The following task was defined during the meeting:
Important
It has been scheduled to be done before next week.
- Héctor Triguero del Río
- Fernando Cachon Alonso
- Daniel Fernández Cabrero
- Umut Dolangac
- Diego Martínez Chamorro
We reviewed the work done for the following tasks and we obtained several conclusions.
- Study the past years projects: The last years proyects were discussed and compared together, in order to discuss its documentations and plan to refine them. The project es_3b was taken as model for its well designed UI, performance and architecture, as it was similar to the ones that we decided as well.
We closed the following tasks:
We decided to continue working in these tasks: *
During this meeting, we reviewed the work done by each member and we took several decisions:
- The selected projects from past years was [WIQ_ES3B] as a reference and code source for at least the UI.
- The documentation sections where divided among the team members
- We asked the client about the constraints related with the questions generation and the LLM
- One team member was instructed in the deployment of the application.
The following task was defined during the meeting:
Important
It has been scheduled to be done before next week. (Documentation v1)
- Héctor Triguero del Río
- Fernando Cachon Alonso
- Daniel Fernández Cabrero
- Umut Dolangac
- Diego Martínez Chamorro
We reviewed the work done for the following tasks and we obtained several conclusions.
- Write documentation: Here we also take into account the sub-issues. The documentation was evaluated by the professor, as a result we ended up writing some corrections to be done, but overall it was good.
- Research about WikiData: After further analysis of the API, we decide on using the endpoint: https://query.wikidata.org/sparql
- Research about PR strategies: We decided to follow the commit/branching/PR startegy described in the issue using the extension https://www.conventionalcommits.org/en/v1.0.0/
- First deliverable self-reports: After discussion with the professor, we were asked to improve our self-reports, trying to be more concrete on what were our contributions.
We closed the following tasks:
- Write documentation and its sub-issues
- Research about WikiData
- Research about PR strategies
We decided to continue working in these tasks:
- First deliverable self-reports reopened for applying the changes individually in each sub-issue.
During this meeting, we agreed to distribute the work for the first prototype. The idea is to work on individual feature branches that will be merged to a new prototype branch, from where it will be finally merged with master. Additionally, we wrote down all the possible fixes for our documentation that needs to be done.
The following tasks were defined during the meeting. Each task includes detailed information such as objectives and sub-tasks, these are accessible through the linked issues:
Important
The fixes to the self-report should be done before next week, the documentation and prototype can be done up to the second deliverable.
- Héctor Triguero del Río
- Fernando Cachon Alonso
- Daniel Fernández Cabrero
- Umut Dolangac
- Diego Martínez Chamorro
We reviewed the work done for the following tasks:
-
We are still missing some fixes but the team mostly completed the fixes to the documentation successfully.
During this meeting, we reviewed the fixes for the documentation, further detailed the work distribution and clarified some implementation aspects and design decisions.
The following tasks were defined during the meeting. Each task includes detailed information such as objectives and sub-tasks, these are accessible through the linked issues:
Important
The implementation for the first prototype should be started for next week.
- Subissues inside First Prototype Development