20240801 Weekly Development Meeting

[josecelano]

• Time: 9:30 in Canary Islands (WET (UTC+0)).
• Time: 10:30 in Vaduz (CET (UTC+1)).

Location:
https://meeting.blockfinance-eco.li/NautilusCyberneeringWeeklyDevMeeting

Expected duration: 2 to 4 hours with breaks

Communicated attendants:

• Cameron Garnham(@da2ce7) -
• Jose Celano(@josecelano) - x
• Constantin Bosse(@cgbosse) - x
• Mario Melchor(@mario-nt) -
• Graeme Byrne(@grmbyrn) - x

---

Agenda:

1. Everyone will take their turn and:

• Go over his notes added as comments for the meeting which will have been added in advance to give an update of all the work done during the previous week indicating.
  • The issues worked on
  • The progress made on them
  • Other things done
• Inform of any faced challenges and request help if necessary to work on specific issues.
• Highlight the encountered difficulties, especially if there is a risk of them causing delays or affecting end product's quality.
• Communicate what will be the next week's tasks.
• List any new topics for further discussion in an additional Technical meeting that he noted for future discussion in comments to this discussion either before the meeting or after his turn so that they get considered.

During the meeting every team member will take their turns and follow this sequence.
The topics for further discussion will be noted in advance by each the team member and to the meetings agenda.

2. At the end of the meeting if there any new technical topics to be discussed further it will be decided to
   set another meeting date for the discussion of these or to hold the meeting hereafter.

Also the persons to be part of the meeting will be decided on so that the others will be free to continue their own work.

[josecelano]

Torrust Tracker

Issues:

• Overhaul tracker keys torrust/torrust-tracker#773
  • Overhaul tracker keys: upload pre-generated keys torrust/torrust-tracker#974
  • Bug: tracker keys can contain any char not only alphanumeric chars torrust/torrust-tracker#976
  • Overhaul tracker keys: allow permanent keys torrust/torrust-tracker#979 (pending to merge)

Next:

• Overhaul tracker keys: option to disable auth key expiration torrust/torrust-tracker#978

[josecelano]

Hi @da2ce7, in the meeting I forgot to mention an important topic. In the tracker, we didn't have any database migration tool. DB schema is hardcoded. I needed to make a change to the schema to allow NULL in valid_until field in the keys table, in order to allow permanent keys. For the time being, I have added manual migrations using the same format we use in the index. We will need to add automatic migrations. Is that something we should add before the next major release?

PR: torrust/torrust-tracker#983