The real deal y0
Eu fairphone 4 user here. Obviously i have none of these issues as phone/network locking isnt a thing here. And im running lineageos and not fully degoogled ( which im ok with ).
But the party trick is very real haha.
I plan to use this phone for at least 8 years as my previous phone, a one plus x, i used for 8 years.
Must be a benelux thing? Same thing here
I know, hence why i said youre not wrong but the example was wrong :p
Also, its more complex than that. Some teams can, some cant. And if they can it all depends on what project or context. The business world isnt that cut and dry hehe
Not saying youre wrong, but you took the wrong project as an example hehe.
Visual code is not open source. Its core is, but visual code isnt.
The difference is what visual code ships with, on top of its core.
Its like saying chrome == chromium ( it isnt ).
Visual code comes with a lot of features, addins and other stuff that isnt in the core.
.net debugger for example, is not found in vscodium ( build of the vscode core ). And there is more stuff i cant think of now but have come across.
Source: been using vscodium for a few months instead of vscode
Fair, and ill edit my post accordingly!
There are teams that are allowed, and within those companies are teams that are directly related to foss projects because those companies are in the foundation or supports of the foundation. However, thats doesnt mean every (product) team in the company is allowed to or that they can do or change whatever they like. Its a complex mess
Thats just dual booting. That wont work with the law if the contract says anything created using company hardware is theirs.
And yes, some companies need to give you a green light to work on projects in your free time, because they might have a team doing similar things somewhere, it might compete in something they would like to do in the future or like you said, might use company know how which is a huge nono.
Its bs imo, but those clauses and rules are found in some employment agreements.
Remember, always read your employment agreements!
Yes, but not all devs within microsoft are allowed to work on non-ms foss projects. I assume wsl devs are allowed to send stuff to linux but visual studio devs probably are not.
And not every team is allowed to do that.
Also, youre telling somebody who has worked with big companies not allowing it in their employer contract that he is lying? Riiiight…
A lot of google devs also are not allowed to do any linux work outside of work without explicit permissions because of all the internal docs, teams and other work being done on linux from within google. Development rights is an absolute mess, legally.
I usually dont care and do what is right, despite what my emploter contract says, but i have gotten in trouble for it
I agree they should have sent a patch to the grub source, but keep in mind big software companies like microsoft, Verizon, … do not normally allow their product teams to send a patch or PR to open source projects. This is because in their contract it states that all code written on and during company times is owned by the company. This means that it is impossible for them to make a patch or PR because it would conflict with the projects licence and fact its open source.
This changes when the team explicitly works on the foss product/project like the ms wsl team or the team working on linux supporting azure hardware, but that is an exception. I do not believe the microsoft kernel/bootloader team is allowed to send patches to grub.
Its a terrible thing, and it shouldnt be, but thats the fact of the world atm.
Except he is. He lives in portland now afaik
In the usb world its “host” and “device”, not “master” and “slave”.
But yes you are right
Reporting the bug without fixing it is not repairing the software :p
This is a topic about manufactoring, thats a different thing as its more based on processes and blueprints
Depending on the angle, yes. If its for repairs, then yes. If its for product (manufactoring) improvements, then no. Im a software developer that often collaborates with other teams of open source software. I report, and sometimes fix, bugs so it improves the overal product for everyone. I wouldnt put that under right to repair, as it has nothing to do with repairing it yourself and more with improving a product for everyone by tackling a problem with the product at the source.
Imo open source doesnt explicitly mean “you can build it yourself”
What it does stand for is that incase of issues it can be looked at and resolved. Be it finding the broken component, or looking at the designs and reporting the fault. Both of which improve the thing that is open sourced.
As an example : the framework laptop. Its partly open source, so in case of issues i could bring it to a repairshop which then can easily look at the designs, and figure the fault.
Or what i did with my home server sbc : get the schematics, figure out a manufactoring fault ( cracked solder on pci lane ), fix it and report it to the manufacturer ( which then investigated if it was a one off or if a solder type change was needed ).
Exactly the reason why i replaced the one plus x ( which was running a lineageos android 11 build fine ) with the fairphone 4 :D