Team Journal
Evolución y gestión de la configuración
Grupo 1
2024/25
This document records the minutes of key meetings for the serranito-hub project. It outlines the objectives, topics discussed, and conclusions from each meeting to ensure transparency and team alignment.
This team has been colaboration into 2 teams, serranito-hub-1 and serranito-hub-2.
| serranito-hub-1 members |
|---|
| Calero López, Marina |
| De los Santos Barrera, Elena |
| Galván Cancio, Daniel (coordinator) |
| Herencia Solís, Lucas Manuel |
| Robles Russo, Eduardo |
| Solís Padilla, Isaac |
| serranito-hub-2 members |
|---|
| García Carballo, Juan |
| García Escudero, Ángel (coordinator) |
| García Rivero, Andrés Francisco |
| Muñoz Rodríguez, Jorge |
| Pérez Santiago, Alejandro |
| Statistics |
|---|
| Total meetings: 6 |
| Total face-to-face meetings: 3 |
| Total virtual meetings: 3 |
| Total time spent in face-to-face meetings: 2h 32min |
| Total time spent in virtual meetings: 2h 42min |
- October 20, 2024 - 4:00 PM
- Mode: Discord
- Marina Calero López
- Elena de los Santos Barrera
- Daniel Galván Cancio
- Lucas Manuel Herencia Solís
- Eduardo Robles Russo
- Isaac Solís Padilla
- Juan García Carballo
- Ángel García Escudero
- Andrés Francisco García Rivero
- Jorge Muñoz Rodríguez
- Alejandro Pérez Santiago
The purpose of this meeting was to:
- Initiate the project and define initial objectives.
- Establish foundations for effective collaboration between teams.
- Identify Work Items (WIs) for participants and analyze their complexity to support task planning.
-
Project Kick-off Definition:
Defined initial steps to launch the project, including strategies, methodologies, and resource allocation. -
Review of Work Policies:
Introduced and reviewed the proposed work policies for branch management, commits, pull requests, and issue tracking to ensure uniform team operations. -
Communication Strategies:
Discussed the use of Discord, Google Drive, and other communication tools to streamline collaboration. -
Task & Initial Objective Definition:
Identified priority tasks as a starting point to clarify team goals and path toward milestones. -
Distribution of Work Items (WIs):
Aligned individual preferences and strengths with tasks to ensure that work is allocated according to each team member's expertise and comfort level.
The following tools were approved for effective communication and documentation:
- Google Drive: A central repository for documentation, deliverables, and meeting minutes.
- Discord: The main communication tool for meetings and regular updates.
- WhatsApp: For quick communications and resolving inquiries.
| Agreement | Description |
|---|---|
| 2024-01-01 | Initial priorities were established |
| 2024-01-02 | Short-term objectives were clearly defined |
| 2024-01-03 | Work Items (WIs) were assigned, and communication strategies were planned to ensure efficient teamwork as the project progresses |
- October 23, 2024 - 19:00 PM
- Mode: In-person
- Marina Calero López
- Elena de los Santos Barrera
- Daniel Galván Cancio
- Lucas Manuel Herencia Solís
- Eduardo Robles Russo
- Isaac Solís Padilla
- Juan García Carballo
- Ángel García Escudero
- Andrés Francisco García Rivero
- Jorge Muñoz Rodríguez
- Alejandro Pérez Santiago
The purpose of this meeting was to analyze the results of Milestone 1 and plan the next steps to ensure continued progress in the project.
-
Positive Feedback:
The tutor provided positive feedback on the completed milestone, and the Work Items (WIs) were formally approved. -
Work Item Clarification:
Specific details for each WI were discussed to ensure all team members have a clear understanding of their responsibilities, especially regarding integration tasks. This will promote alignment and comprehension across the team. -
Next Steps Planning:
Defined actionable steps and timelines for the next phase, ensuring effective coordination among all members.
| Agreement | Description |
|---|---|
| 2024-02-01 | Clarified the details and approach for each WI to ensure smooth integration and team understanding. |
| 2024-02-02 | Scheduled and defined next steps for the upcoming project phase, building on the positive feedback received. |
- October 27, 2024 - 1:00 PM
- Mode: In-person
- Marina Calero López
- Elena de los Santos Barrera
- Daniel Galván Cancio
- Lucas Manuel Herencia Solís
- Eduardo Robles Russo
- Isaac Solís Padilla
- Juan García Carballo
- Ángel García Escudero
- Andrés Francisco García Rivero
- Jorge Muñoz Rodríguez
- Alejandro Pérez Santiago
The purpose of this meeting was to analyze the results from the code review session conducted by potaje-hub-1, identify corrective actions, and ensure continued progress toward milestones.
-
System Evaluation & Testing Results:
Analyzed the findings from the source management system review and identified key areas that need attention. -
Defining Corrective Actions:
Discussed strategies to address system issues and concerns raised during the code review. -
Prioritization of Deliverables:
Adjusted priorities to ensure steady progress toward critical milestones and deliverables.
| Agreement | Description |
|---|---|
| 2024-03-01 | Corrective strategies were established to address the identified system issues |
| 2024-03-02 | Priorities were adjusted to maintain steady progress toward key milestones |
- November 1, 2024 - 11:00 AM
- Mode: Discord
- Marina Calero López
- Elena de los Santos Barrera
- Eduardo Robles Russo
- Isaac Solís Padilla
- Ángel García Escudero
- Andrés Francisco García Rivero
-
Validate Branch Policy:
The branch policy remains as written in the corresponding section of the Work Policies document. -
Validate Issue Naming Convention:
The issue naming convention remains as written in the corresponding section of the Work Policies document.-
Issue Naming Format:
type-WI <WI_name>-feature <functionality> close #XX
Include "Close" in the commit messages to close a branch upon request.
-
Issue Naming Format:
-
Validate Merge Policy:
Adopt the Ship / Show / Ask merge strategy model. -
Validate Incident Management:
- Review how an issue is created using a template: Template Link.
- Add a template for regular issues:
Keep the default template. Ensure proper completion of assignments, labels, etc.
-
Fix the Work Policies Document:
Review and correct the Work Policies document as needed. -
Reminder: Update Dependencies Script:
Run the following commands:git pull source venv/bin/activate ./update_dependencies.sh -
Assign the Implementation of Fakenodo:
Assign 1-2 people to handle this task. Create an API that provides empty positive responses to calls from uvlhub.
-
Conduct Survey for Fakenodo Assignment: Gather input and make assignments.
| Agreement | Description |
|---|---|
| 2024-04-01 | Branch policy was validated and confirmed to remain as outlined in the Work Policies document. |
| 2024-04-02 | Issue naming conventions and merge policies (Ship / Show / Ask) were validated and agreed upon. |
| 2024-04-03 | Incident management procedures were reviewed, including the adoption of a standardized issue template. |
| 2024-04-04 | Updates to the Work Policies document were discussed and approved. |
| 2024-04-05 | Reminders were issued about the proper use of update_dependencies.sh for dependency management. |
| 2024-04-06 | Fakenodo implementation was assigned, including the creation of an API for uvlhub. |
| 2024-04-07 | A survey was conducted to finalize assignments for the Fakenodo implementation task. |
- November 13, 2024 - 12:10 PM
- Mode: In-person
- Marina Calero López
- Elena de los Santos Barrera
- Daniel Galván Cancio
- Lucas Manuel Herencia Solís
- Eduardo Robles Russo
- Isaac Solís Padilla
- Juan García Carballo
- Ángel García Escudero
- Andrés Francisco García Rivero
- Jorge Muñoz Rodríguez
- Alejandro Pérez Santiago
The purpose of this meeting was to address the feedback received from the tutor after milestone 2, discuss the points raised, and align on the necessary actions to correct and improve the project.
-
Review of Feedback from Tutor:
After completing milestone 2, the team met in person to go over the tutor’s feedback point by point. The feedback included several key aspects that required attention. -
Restriction on Project Modifications:
The tutor reminded us that once the registration form for milestone is completed, no modifications can be made to the project. This point was emphasized to ensure all future work aligns with the established scope. -
Test Data in the Deployment Environment:
It was pointed out that we need to upload test data into the deployment environment. This will allow us to verify that the system functions as expected and ensure the proper integration of all components in the live environment. -
Issue Template for Work Items (WI):
The tutor clarified that Work Items are included when talking about issue management. We were asked to create a specific template for issues related to WIs. While we previously had a "Bug Report" template, we agreed to create a new template that fits the tutor’s request for WI-related issues.
| Agreement | Description |
|---|---|
| 2024-05-01 | The team met in person to review feedback from the tutor after milestone 2. Corrective actions were discussed and agreed upon. |
| 2024-05-02 | It was confirmed that no project modifications can be made after milestone 1 registration. |
| 2024-05-03 | Test data will be added to the deployment environment for proper system validation. |
| 2024-05-04 | A new template for Work Item (WI) issues will be created as per the tutor’s feedback, in addition to the existing Bug Report template. |
- December 15, 2024 - 4:20 PM
- Mode: Discord
- Marina Calero López
- Elena de los Santos Barrera
- Daniel Galván Cancio
- Lucas Manuel Herencia Solís
- Eduardo Robles Russo
- Isaac Solís Padilla
- Juan García Carballo
- Ángel García Escudero
- Andrés Francisco García Rivero
- Jorge Muñoz Rodríguez
- Alejandro Pérez Santiago
The purpose of this meeting was to check that everything is working correctly and to hand over the project.
-
Start of the meeting. With the attendance of all members of both working teams, serranito-hub-1 and serranito-hub-2, the project closure meeting begins.
-
Validate that the deployed version of docker works: One of the team members' work item depends on installing some npm dependencies. Docker has been tested on another team member's computer to see that it works so it can be deployed definitively.
-
Each member says the number of hours and tests they have done: This is done to make it easier to fill out the information table found in the project description section of the repository wiki.
-
Dockerfile configuration. For the proper functioning of the application, it is necessary to integrate the npm dependencies as well as:
- Update of the Dockerfile files to integrate the new required dependencies.
- Resolution of conflicts caused by the creation of the file.
| Agreement | Description |
|---|---|
| 2024-06-01 | Serranito-hub-1 team has decided to complete all M3 requirements today |
| 2024-06-02 | Serranito-hub-2 team has decided to complete all M3 requirements throughout Monday |
| 2024-06-03 | The team has decided not to make any further code changes starting Tuesday |
| 2024-06-04 | The team has decided to deploy the latet version by Sunday night |
| 2024-06-05 | The team has decided to have everything finalized by Tuesday, June 17th, at the latest |