20250505 Weekly Development Meeting

[josecelano]

NOTE: This week's meeting will be on Monday, as there was no meeting last week (https://github.com/orgs/nautilus-cyberneering/discussions/145).

• 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) - x
• Jose Celano (@josecelano) - x
• Constantin Bosse (@cgbosse) - 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]

Things I want to discuss in the meeting (cc @da2ce7):

• Overhaul stats torrust/torrust-tracker#1327
  • Overhaul stats: Add the PeerClient and version as labels to metrics torrust/torrust-tracker#1456 (comment)
  • Overhaul stats: Increase IPv4 stats for IPv6 IPs with the prefix ::ffff: torrust/torrust-tracker#1375 (comment)
  • Overhaul stats: Handle lagging in event listeners channels torrust/torrust-tracker#1449
  • Adding events to tracker-core and torrent-repository
    • Overhaul stats: Add extendable-labeled metrics to the tracker-core package torrust/torrust-tracker#1437 (comment)
    • Overhaul stats: Emit events from the torrent-repository package and collect metrics torrust/torrust-tracker#1358 (comment)

[josecelano]

I also found this interesting conversation: arvidn/libtorrent#5860 (comment)