20260219 Weekly Development Meeting

[josecelano]

• Time:

  • 09:30 in Canary Islands (WET / UTC+0)
  • 10:30 in Vaduz (CET / UTC+1)

• Location:
  https://meeting.blockfinance-eco.li/nautiluscyberneeringweeklydevmeeting

• Expected Duration: 2 to 4 hours, including breaks

• Confirmed Attendees:

  • Cameron Garnham (@da2ce7)
  • Constantin Bosse (@cgbosse)
  • Jose Celano (@josecelano)

---

Agenda

1. Weekly Updates (Each participant will take a turn)

Each team member should come prepared with comments added in advance to this discussion. During their turn, they will:

• Review their notes/comments and provide a summary of:
  • Issues worked on
  • Progress made
  • Other relevant tasks completed
• Share any challenges faced and request assistance if needed
• Highlight any difficulties that may risk delays or affect the final product's quality
• Outline their planned tasks for the upcoming week
• Mention any new technical topics they've noted for potential future discussion (to be added as comments in this thread)

🔁 This format ensures everyone follows a structured sequence during the meeting.

2. Technical Discussion Planning

After all updates:

• Any proposed technical topics will be reviewed
• A decision will be made on whether to:
  • Schedule a follow-up technical meeting, or
  • Continue with the discussion immediately, time permitting
• The attendees for the follow-up meeting will be determined, allowing others to resume their work as needed

[josecelano]

Torrust Website

New blog post: https://torrust.com/blog/vortex-rust-bittorrent-client-review

Torrust Tracker Deployer

Bugs:

• Bug: render command ignores --working-dir global argument torrust/torrust-tracker-deployer#365

CI:

• ci: add cargo fetch step to measure download vs build time torrust/torrust-tracker-deployer#343
• fix: [#342] resolve Docker BuildKit 'image already exists' error in CI torrust/torrust-tracker-deployer#344 (bug: race condition tagging docker images used in tests)
• ci: add code statistics workflow with tokei torrust/torrust-tracker-deployer#346 (see example)

Refactoring:

• test: add comprehensive unit tests for endpoint_builder module torrust/torrust-tracker-deployer#347
• refactor: improve TrackerContext type safety with structured database configs torrust/torrust-tracker-deployer#350
• refactor: separate view data from views in presentation layer torrust/torrust-tracker-deployer#354

Roadmap:

• Add levels of verbosity
  • feat: Add verbosity levels to provision command (-v, -vv, -vvv) torrust/torrust-tracker-deployer#361 (docs)
  • Add verbosity levels to configure command torrust/torrust-tracker-deployer#363 (docs)
  • Add verbosity levels to release command torrust/torrust-tracker-deployer#367 (docs)
• Improve AI agent experience
  • Provide Configuration Examples and Questionnaire for AI Agent Guidance torrust/torrust-tracker-deployer#339
• Add JSON output format support (see this to know why I have included this again in the roadmap. Initially, I wanted to include it in future releases.
  • Add JSON Output to create Command torrust/torrust-tracker-deployer#349
  • Add JSON output to provision command torrust/torrust-tracker-deployer#352
  • Add JSON output to show command torrust/torrust-tracker-deployer#355
  • Add JSON output to run command torrust/torrust-tracker-deployer#357
  • Add JSON Output to List Command torrust/torrust-tracker-deployer#359

AI:

I've added many skills. They seem to work, but are not very reliable in Copilot. I've had many cases where a needed skill isn't triggered. I do not know whether the hooks are only before user prompts (I don't think so) or are triggered internally every time the agent prompts the LLM models. However, since this is a standard, I would expect all agents to improve this.

I do not like duplicate information in the project documentation, but it seems better to ensure the guide is included in the context (at least the header), so the skill can be reused everywhere. Some skills are intended to be used with the whole repo cloned, but others can be used by agents in other contexts.