As a senior dev, when pairing with junious I get a more skilled team. Then I can continue to give new teams the skill and we all grow as people and companies.
On commercial vessels, the colors have to follow the Solars standards. To make sure there are no misunderstandings in the charts. Many, software for no-comersical ships have much more fancy displays in random colors. Including 3d views of your route with sonar overlays. Satellite maps, but the clarity of the standard colors, or colors close to them as used by are much clearer in my view. For an overview of what Navionics, Garmin's chart brand, gives (https://www.navionics.com/fin/charts/features/garmin).
All commercial plotters have autorouting. There is automatic wind routing for sailing in OpenCPN (as a plugin). I'm not sure that adding it to a phone with carplay is a viable option. If you have a display to show it on, it's probably a display for a plotter with all the functionality, including map updates over the internet.
Thou for entertainment it's an other side, that would be useful.
It's an international standard so all professionals that read the maps never have to guess what the colors mean. In commercial vessels, you need to follow the Solas standards. This also means that you need certified hardware and software for the chart plotters.
There is no mandatory government registration of non-profits in Sweden. You can get a like a tradename protection by registering like a company name. Suppose you would like to start a non-profit or any other organization. You need a yearly meeting to take the signed protocol to your local bank if you need an account.
If you like to have an organizationalnumber, you need to apply to the tax authority. If you do business activity and like a local name protection you need to apply to bolagsverket. Depending on the size of the app these steps might be helpful. I don't think our local chapter of FSF, has done any of the registrations just as an example. They run local conferences and other simular works.
If you try that you totally broken the DevOps idea, but now the whole world of ops and IT did that ages ago as anything that is configured in code, e.g. yaml, is devops.
The article suggests using a higher level abstraction with better tools suited for the developers than the low level tools as docker, Kubernetes etc. You can make this into a separate internal product and still keep the devops idea. But as soon you break out any of the core responsibilities for the product from the team. If that's business, security, stability or quality you are moving away from devops. Sure devops isn't the solution to all problems. But why call it devops when one doesn't like the basic devops idea.
They for sure intended to make an API, but also intended it only to be used between the two contractors involved in the application development. There was a requirement in the RFQ for the backend to have a well documented API. Almost all of the RFQ was about making an API.
In this case the indended user e.g. the parrent is using the API to get the data they are supposed to get. Thou using a different webb-app than the intended one from the city. I have a hard time seeing how the parent by accessing the same data they are supposed to get are doing any crime. The police investigation came to the same comclusion, and the internal investigation at stockholm city also came to this comclusion. That the police cited stockholms internal investigations i think is a nice little detail here.
Thou if the app would have given the parents access to data they ware not supposed to get over the API they situations might been an other. Now it's just the same information but persented in a user-friendlier way.
Agile and Scrum isn't the same thing. Even if Scrum in someways are agile. The "original" agile process, or the first videspread variant XP didn't mention any dailies. Scrum as such is much a way to adopt XP into a large cooperate environment.
