20250430 Weekly Development Meeting

[josecelano]

NOTE: This week there will be no meeting because it's a bank holiday in Spain and Germany, where most of the attendants are this week.

You can write down your weekly report anyway. We will reschedule next week's meeting to Monday.

Communicated attendants:

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

[josecelano]

Torrust Tracker

Newly opened issues:

• Overhaul Secrets: consider using secrecy to handle secrets torrust/torrust-tracker#1490

Comment on issues:

• Overhaul stats: Add extendable-labeled metrics to the tracker-core package torrust/torrust-tracker#1437 (comment)

Issues:

• Fix shutdown message and improve it torrust/torrust-tracker#1477
• Overhaul stats torrust/torrust-tracker#1327
  • Overhaul Stats: Refactor event listeners initialization torrust/torrust-tracker#1444
  • Overhaul stats: Extract events package (part 1) torrust/torrust-tracker#1478
  • Overhaul stats: Extract events package (part 2) torrust/torrust-tracker#1480
  • Overhaul stats: Extract events package (part 3) torrust/torrust-tracker#1485
  • Overhaul stats: Simplify torrent-repository package before adding events torrust/torrust-tracker#1491

This week, my primary focus has again been on the stats overhaul.

1. Refactor boostrapping. Event listeners are now also controlled by the main app, and there is a new type JobManager for handling jobs.
2. Extract the duplicated events code into a new events package, before continuing to add events to more packages, which would increase the duplicity.
3. Simplify torrent-repository package before adding events. WIP but almost finished. I only have to clean the tests.

NOTE: total time spent on Torrust ~27,5h

Learning

I was also experimenting with https://www.cursor.com/, creating a new repository with notes about Rust as part of my learning process. I installed the GitHub MCP server (not yet used), and I was reviewing the rules (https://www.projectrules.ai/) to include in projects.

• https://github.com/anthropics/prompt-eng-interactive-tutorial
• https://docs.cursor.com/context/rules
• https://www.projectrules.ai/

This is the sample repository: https://github.com/josecelano/learning-rust

[josecelano]

The other thing I want to try is rustcoder: https://www.secondstate.io/articles/rustcoder/

[grmbyrn]

Torrust

• Set up and read through Torrust code

Learning

• Continued course learning Nuxt
• Continued course on improving TypeScript

Project Idea

• Create a resource for new members of the team to get up to date with the technologies we use through reading the official documentation and then answering multiple choice questions. This would encourage spaced repetition and help any new members follow a self-paced learning path to ensure comprehension and retention. The multiple choice questions would be sourced from the documentation of key technologies like SvelteKit, Rust, Nuxt, etc, focusing on core concepts and best practices to strengthen their foundational knowledge and practical skills.