20240711 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) - x
• 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:

• Config overhaul: remove secrets when final config is printed to console torrust/torrust-tracker#948
• Config overhaul: lowercase for DatabaseDriver torrust/torrust-tracker#950
• Denial of Service attack factor torrust/torrust-tracker#324

I've reopened issue #324, and I've confirmed that even with the new hyper version (1.4.0), the problem is still there; there is no default timeout to close the connection.

I've created a relase plan together with @cgbosse.

Torrust Index

Issues:

• Configuration overhaul: make mail-related configuration clearer torrust/torrust-index#654
• Update dependencies
• Review security advisory (pending feedback from @da2ce7)

Comments on issues:

• Include non standards field in the info dictionary for popular BitTorrent clients? torrust/torrust-index#567

I've created a relase plan together with @cgbosse.

Torrust Index GUI

I've created a relase plan together with @cgbosse.

Torrust Demo

• Update demo following changes in configuration files.

Torrust Website

• Meeting with @grmbyrn to start working on the new website.

Torrust Rebranding

Review proposals received from the designer for the new logo.

Learning

Starting reading a new Rust book: Rust in Action.

Eng. Manager

One-on-ones with @grmbyrn and @mario-nt

[mario-nt]

Index

• #615: Authorization for public handlers torrust/torrust-index#662

Reviews

Training/Research

• Are you using Object-Oriented Programming? | Vaughn Vernon lecture

Other

• One on One with Constantin and Jose

New issues

[grmbyrn]

Torrust website

• Research best ways to structure v2 of website
• Read through SvelteKit docs
• One on one with Jose to discuss the best way forward with v2
• Examine Figma and decide how to proceed with implementing it in v2
• Begin implementation of v2

Learning

• Revise Python

[mario-nt]

Index

• #615: Authorization for public handlers torrust/torrust-index#662

Training/Research

• Are you using Object-Oriented Programming? | Vaughn Vernon lecture

Other

• One on One with Constantin and Jose