20241121 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) - x
• 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]

Roadmap

I wrote my thoughts about the roadmap for next year.

We need to define the roadmap; some users are waiting for/asking for certain features. It would also be useful for contributors to know where the project is heading.

Torrust Tracker

Issue:

• Error: unknown unstable option: profile running coverage report workflow torrust/torrust-tracker#1075 (fixed the coverage report)

PR review:

• udp: symmetric encrypted cookie torrust/torrust-tracker#1091

New issues:

• Ban socket addresses not sending a valid connection ID torrust/torrust-tracker#1096

Torrust Index

Issues:

• Error: unknown unstable option: profile running coverage report workflow torrust/torrust-index#770 (fixed the coverage report)

PR review:

• feat: create a new plugin for qBittorrent torrust/torrust-index#773

New issue:

• Torrents exporter torrust/torrust-index#768

Torrust Index GUI

Commented on issues:

• Hyperlinks Do Not Work torrust/torrust-index-gui#644

Torrust Website

PR reviews:

• remove vertical scroll bar torrust/torrust-website#116

Torrust Demo

I tried to find out why the UDP tracker had many connection ID errors in logs.

Issues:

• Can't connect to the UDP tracker torrust/torrust-demo#16
• Error connection id could not be verified torrust/torrust-demo#14

It seems to be a bad client. It's not using the connection ID in the announce request received in the connect request.

Torrust Bencode2Json

Issues:

• Add a workflow to generate a code coverage report on codecov torrust/bencode2json#8

New issues:

• Docs: add state diagrams torrust/bencode2json#11
• Find a better name for BencodeParser type torrust/bencode2json#12

I also met with the new contributor to answer her questions about the project.

@da2ce7, it would be nice to have your feedback on renaming the main type in the library.

New repos

Torrust Bencode Online

I have created a new repo: https://github.com/torrust/torrust-bencode-online to implement our browser bencode to JSON converter.

Torrust Installer

Also, a repo to work on a future Torrust installer.

torrust/torrust-installer#1

Both repos also contain the proposal.

Time spent on Torrust: 17h