Leading up to the release of Tracker 3.0, we have decided to have a team meeting every 2 weeks. This will take place online using videoconferencing software (i’m not sure which yet… any suggestions?). It’ll be at 15.00 UTC on Saturday 18th April, and the plan is to have a meeting every 2 weeks.
The core team (Carlos Garnacho and me) will be present and you’re invited too if you have something you want to discuss. Just add it to the agenda here: https://wiki.gnome.org/Projects/Tracker/Meetings/20200418 or reply to this post.
In particular we want to start porting apps and libraries to Tracker 3.0, so it’ll be great to have folks who work on content apps, Grilo, etc.
If you want to join in with a fun open source project then we can also use the time to help you get started with some work on Tracker!
We’ve tried a couple of solutions in our working group and had the most success using a self-hosted bigbluebutton instance. I’d be happy to join on Rygel’s behalf
Great! is there a way we could use this bigbluebutton instance for the meeting?
Regarding Rygel, I have a few thoughts!
Like most apps I’ve looked at, Rygel doesn’t seem to have any automated tests covering the Tracker related codepaths. Probably because there’s never been a clear way to use Tracker from tests. For 3.0 we will have a story for this, see here for an example, so maybe we can add a test and use that to test the port to 3.0?
Regarding the work required for porting Rygel to 3.0, the big change is probably that the ‘nmm:uPnPShared’ flag will no longer be stored with the filesystem metadata, it’ll be stored in a Rygel-specific Tracker database instead.
Regarding that BBB instance, unfortunately, no. That’s behind a VPN. And unfortunately my server doesn’t meet the prerequisites :-/
Regarding Rygel: Yes, we tried to cover the the core functionality with the tests (which still isn’t on par to what it was before :/) , and also back in Nokia days, as you said, the tracker testing story wasn’t that clear.
As an alternative, there is Jitsi Meet. Here is a list of reliable instances.
There are currently some issues when using Firefox but they are being worked out.
My point is let’s not use Zoom nor Chrome ! But I would be lying if I said that the current status of Jitsi + Firefox was optimal.
That being said, I have never added any issue with Firefox + the Jitsi instance from framatalk (between 2 and 5 participants during my calls). According to the bug reports, things get messy when there are a lot of participants to a call.
I could also set up a BBB room at https://meeten.statt-drosseln.de/ - It is very privacy friendly and BBB seems to work fine with Firefox. We can also just try one of each on subsequent meetings and see which one floats our boat the best
How does everyone feel about recording the meetings as videos? I’m not sure I want everything I say to be preserved for eternity… andiIf someone does want to catch up, it also seems like it’d be more work watching hours of rambling meeting videos, than reading the edited notes in the wiki.
! But I would be lying if I said that the current status of Jitsi + Firefox was optimal.