20240215 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:

• CGarnham(@da2ce7) - x
• JCelano(@josecelano) -
• CBosse(@cgbosse) - x
• MMelchor(@mario-nt) - x
• GByrne(@grmbyrn) - x
• MVanDijke(@WarmBeer) - 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]

Hi @nautilus-cyberneering/core This week I will be off from Tuesday to Friday. This is what I've done since the last meeting.

Torrust Tracker

Issues:

• Error building with rustc 1.78.0-nightly: unknown feature stdsimd torrust/torrust-tracker#691

Open new issues:

• Extract Tracker API Client packages torrust/torrust-tracker#689

Torrust Index

Issues:

• Review missing timeouts torrust/torrust-index#467
  • Tracker API client: add timeout to requests torrust/torrust-index#473
  • Index API client: add timeout to requests torrust/torrust-index#472
  • Add timeout to the http_health_check binary torrust/torrust-index#433
• Overhaul logging torrust/torrust-index#468
• Improve documentaion for the seeder command torrust/torrust-index#466
• Installation error on Debian 12 (bookworm): error: failed to run custom build command for openssl-sys v0.9.99 torrust/torrust-index#463
• API license link should be relative torrust/torrust-index#457
• Remove secrets from API config endpoint? torrust/torrust-index#424
• Allow to overwrite the auth secret_key = "MaxVerstappenWC2021" with env var torrust/torrust-index#412

Pending feedback:

Please @nautilus-cyberneering/core review my latest comment in the issue:

torrust/torrust-index#469 (comment)

That's something I would like to work on next week.

Torrust Index GUI

Open new issues:

• Allow users to reset their passwords torrust/torrust-index-gui#469
• Allow users to change their passwords torrust/torrust-index-gui#468

[mario-nt]

GUI

• Update footer torrust/torrust-index-gui#401

• GUI license page
• Research on formatting text in vue components

Index

• User ID extractor for handlers that require an user id torrust/torrust-index#445

• fix: [#445] refactor handlers with new user id extractor torrust/torrust-index#486

• Optional user ID extractor for handlers that require an optional user id torrust/torrust-index#446

• Finished extractor and refactoring handlers
• Worked on fixing merge with errors

Discussions

• Import tracker statistics in batches torrust/torrust-index#428

Training/Research

• Text formatting in vue components

[mickvandijke]

I did nothing this week.