December 3, 2020 • Written by David
A list of work packages we've fully wrapped up this month. Expand any to find out more about its conclusion.
Completely overhaul the Portmaster user interface to simplify all aspects of it. Easily block connections from the Monitor, easily block all connection of an app, etc...
We are super happy that this big milestone got reached! The redesigned UI really unravels all of the Portmaster's features which previously were hidden. We still define our software as alpha, so expect bugs - but the Portmaster has become so much more usable. Switching between trust modes, overwriting global settings in specific apps, blocking from the monitor - it is all possible now.Check out the Feature Tour on Twitter
Reintroduce the "Prompt Mode" which asks for your input whether or not to allow a connection. Naturally, make it possible to lock in a decision for the future.
Together with the new UI we also re-introduced connection prompting. Instead of allowing or blocking by default, you can make the Portmaster ask per connection. This feature is meant for low volume apps - as browsers and other apps with lots of connections will not work smoothly due to caching.Download the Portmaster
Apply for follow-up fundings from Netidee & FFG to ensure our financial stability and increase our run-way.
We are excited to announce that both the FFG and the Netidee granted further funding and loans for the year to come! Big shout-out to Raphael and Tabitha, who continuously work on these crucial tasks to keep our journey going while the devs can focus on what they do best: developing privacy software. As always, we are open about our numbers:Look at all our fundings and influences
With over 200+ tasks in the Backlog it has become infeasible to prioritize effectively. As an example: choosing from 20 urgent tasks is rather absurd. Restructure our project management so everyone can work efficiently.
Our project management tool got to a point where it became really hard to chose what to work on. Which task should you work on next when there are 20 tasks marked as URGENT? And even after chosing one, the task description was often very vague, needing lots of talk and co-ordination before being able to start. It became clear that the mountains of work lying ahead of us needed some serious restructuring.
The first part was to define responsibilities. If our Backlog should only contain the next couple of tasks for every person, who gets to call which tasks those should be? So far we often just let everybody decide with their gut, but this is counterproductive to streamlining progress and features as a team. That is why Raphael has now taken upon the role of Product Owner (another hat for you mate 🎩). Additionally, a clear process was defined so tasks are properly specified before moving into the 'Backlog'
The natural step afterwards was to move all tasks into the new workflow. Most of our old 'Backlog' tasks have now been moved to the 'Idea Phase', while the 'Backlog' remains short and clearly defined. Now everyone can easily pick up a next task after finishing up another one.
Overall, this was unexpected work, but seeing how it has improved all of our work lives it was definitely worth it.
Also on this note, a big shoutout to OpenProject! They are our self-hosted choice for project management and are FOSS too.Check Out OpenProject
Expand any work package to find out more about its progress, obstacles and sub-achievements.
After v0.1, focus on stabilizing the typical issues that arise with early software. Fix bugs, improve performance & stability. Detect failures in the network and react accordingly. Deliver to more and more pre-orders as the network matures.
As is natural, things happen and can take longer than expected as was the case with the UI Redesign. We are happy that is out of the door so Daniel can now dive into progressing the SPN again. Expect progress updates in the next update blog.
You can see our high level concepts & you can inspect our code. But nothing in between. Fill that gap by providing proper documentation of the Portmaster. What does each component do? With what other components does it interact? Where is its code located?
This big task got blocked by two things: For one, David invested a lot into the Project Managment Cleanup (see above), and second, David needed some technical guidance from Daniel, who himself was working neck deep on the Portmaster Redesign. Both of these projects are done now, so we can tackle this task again. But it probably won't come out before next year. As always, we'll keep you in the loop every month!
Enable you to pay for the SPN with cryptocurrencies such as Bitcoin, Ethereum and Monero
As this feature adds plenty of code onto our codebase, David suggested to make some bigger restructures in the first Review. Alex worked on these refactors in the last month and so this feature is now ready for Review Round II, where we will take a look at all the details.
Spice up the podcast with proper structure. Create an introduction and outro with underlined music and improve the overall storytelling.
If you ever listened to our podcast, you'll notice that every episode is a bit different. Sometimes there is a proper intro/outro, sometimes there is not. Tabi and David got together to brainstorm how to streamline our podcast episodes. After multiple sessions, the texts and concepts are done. We even have a new name ;)
Obviously, we also wanted to add some music to spice things up. For us as a company this is a bit more tricky than for hobbyists, since getting licences for music is harder. We contacted a very talented artist with which we are nearing an agreement. Stay tuned, the next episode will be in the 'new season'.Explore Our Podcast