20241114 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]

Code Coverage Report

We have to change the way we create and upload the code coverage to codecov.

I have created an example: https://github.com/josecelano-test/pull_request_target

In the example, we are not using the alekitto/[email protected]. The action has not been updated to fix this issue.

Bencode2Json

Dicussion with @da2ce7: torrust/bencode2json#7

Community support

• I had a meeting (approx 2h) with two Rust developers to introduce them to Torrust. One of them wants to start contributing.

Torrust Website

• I've installed the Index+Tracker in a new VM from scratch (3.5h) and updated the blog article with minor changes.

The process is very tedious. It would be convenient to build at least a simple installer. I think this could be a common way to deploy Torrust.

I've also opened new issues:

• The search box in blog section does not work torrust/torrust-website#108
• New article: Announcing Torrust Tracker Client torrust/torrust-website#110

PR review:

• fix search error for no results torrust/torrust-website#111

Torrust Index GUI

Comment on issues:

• Hide "Sign Up link" when registration in disabled torrust/torrust-index-gui#635
• Customisable logo torrust/torrust-index-gui#637
• New Torrust brand colors theme torrust/torrust-index-gui#638

Torrust Tracker

New PR:

• Extract console clients into a new package torrust/torrust-tracker#1081

Torrust Demo

New issue:

• Can't connect to the UDP tracker torrust/torrust-demo#16

NOTE: This week, I've worked 14h approx on Torrust.

[mario-nt]

GUI

• New Torrust brand colors theme torrust/torrust-index-gui#638
• Customisable logo torrust/torrust-index-gui#637
• GUI layout needs some work torrust/torrust-index-gui#428

Training and research

• https://flexboxfroggy.com/

Other

• Research on how to close Snyk automatic PRs

[grmbyrn]

Torrust Website:

• fix search error for no results
• add melt-ui toc in (pages)
• remove vertical scroll bar

Study:

• Scrimba TypeScript Course