20231228 Weekly Development Meeting

[cgbosse]

Time: 8:30 GMT+0 Canary Islands Time (9:30 in Vaduz)

Location:
https://meeting.hodl10.io/ConsistentClassroomsMergeSideways

Expected duration: 2 to 4 hours with breaks

Communicated attendants:

• CGarnham(@da2ce7) - x
• JCelano(@josecelano) - x
• CBosse(@cgbosse) - x
• MMelchor(@mario-nt) - x
• GByrne(@grmbyrn) - x
• MVanDijke(@WarmBeer) - 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.

[mario-nt]

GUI

• Update footer torrust/torrust-index-gui#401
• Show torrent fields: creation_date, created_by, encoding  torrust/torrust-index-gui#278
• Research on how to implement light/dark mode for the GUI

Index

• User authentication should be done in middleware torrust/torrust-index#39

Other

• Set up new PC

[josecelano]

Tracker

• Issue: Enable test should_fail_with_ssl_enabled_and_bad_ssl_config. Waiting for feedback.
• Issue: Tracker logs are too verbose. I finally keep the log for each request but with a different format.
• PR review: chore: update cargo deps
• PR review: Update labels.json. New contributor @ShrirangB 🚀 .

Index

• Issue: Patch for Tracker API response is not working
• Issue: Fix tracker API error token not valid.

Index GUI

• Issue: authentication error: missing authentication key param for private tracker. Waiting for feedback.

Website

• PR review: widen text on larger screens and change GmbH to SL
  

Short research

Short research about decentralized indexes and how to scrape the DHT and get torrent metadata:

• https://www.tribler.org/
• https://github.com/urbanguacamole/torrent-paradise
• https://github.com/boramalper/magnetico
• https://github.com/algoprog/rivr-search

Open Discussions

• https://github.com/torrust/torrust-tracker/discussions/545
• Change workflows and branches rules to allow merging PRs with linting errors. torrust/torrust-tracker#546
• Make tracker statistics available via prometheus torrust/torrust-tracker#135 or collect data with prometheus. It would be nice a prometheus-ghrafana container setup for the live demo.
• What is the "Light-Seeding" tracker option? torrust/torrust-tracker#548
• What is the "Cryptoport" tracker option? torrust/torrust-tracker#547
• Decentralized Index: Tribler.org torrust/torrust-index#418

[cgbosse]

Sent email by @WarmBeer

I have been sick for a couple of days already and have been very busy with the holidays, so there is not much I can contribute.

My plan for the following week is to implement DashMap for the torrent tracker in an attempt to make torrent repository reads and writes even faster. Then I will work on adding a max limit to the torrent repository.