Live data from Hacker News

Expanding Fuchsia's open source model

opensource.googleblog.com

71–80 of 334 posts

Re: Expanding Fuchsia's open source model

#71
post #23

Earlier quoted context omitted.

> Looks like you still cannot contribute without granting copyright ownership to Google That is not accurate. Fuchsia uses the standard Google CLA: "You do not surrender ownership of your contribution, and you do not give up any of your rights to use your contribution elsewhere." https://cla.developers.google.com/about

There's a big difference between licensing code to the world under the terms of Apache 2.0, and licensing code to Google under whatever terms they feel like now or at any time in the future.

Is there? Apache 2.0 includes clauses for patent indemnification and allowing sub-licensing derived work.

Re: Expanding Fuchsia's open source model

#72
post #27
post #4

I've heard Fuchsia referred to as a "principal engineer retention project" at Google. I'd be curious to know if others have heard the same.

As a principal software engineer that works on Fuchsia, I can assure you that the project does not exist solely to retain me. :)

Adam, how much were you involved in drafting this manifest?

Re: Expanding Fuchsia's open source model

#74
post #27

Earlier quoted context omitted.

As a principal software engineer that works on Fuchsia, I can assure you that the project does not exist solely to retain me. :)

Congrats on the promo! It didn't quite retain me either, but I was a lowly staff software engineer. I am returning to Google though (back to the Google Fonts team), and it's entirely possible we'll get a chance to work together again.

I look forward to it!

Re: Expanding Fuchsia's open source model

#75
Google and Opensource a joke of century.

Chrome -> Make chromium opensource but add spyware that phones home on every second and with new manifest v3 make sure extensions like ublock origin don't work

Andriod -> Make tip of iceberg opensource but force every vendor to use Service and lock down whole ecosystem around it. And make sure there is no way to block ads on youtube for andriod.

Fuchsia -> Initial Stage make people think they are open they are helping community for first 5-10 years. After that implant spyware etc.

Same strategy different form === Modern Polymorphism by Modern Liars.

Re: Expanding Fuchsia's open source model

#76
post #72
post #27

Earlier quoted context omitted.

As a principal software engineer that works on Fuchsia, I can assure you that the project does not exist solely to retain me. :)

Adam, how much were you involved in drafting this manifest?

I'm sorry, but I'm not sure what you mean by "this manifest." The blog post linked above was written by Wayne Piekarski, who is a Developer Advocate for Fuchsia. My role in the project is as a software engineer.

Re: Expanding Fuchsia's open source model

#77

Earlier quoted context omitted.

Linux itself has never been a GNU project and has never required copyright assignment. It is the combination of features (retain ownership and GPL) together that has enabled collaboration in Linux.

Are you saying that collaboration on Gnu Compiler Collection, binutils, bash, bison, CLISP, coreutils, etc, has been inhibited by the requirement for copyright assignment to the FSF?

The FSF is not Google. Their organizational goals are different enough that the repercussions of copyright assignment are different in each of those cases.

Basically I trust the FSF to stand by the spirit of open source. I don't trust that out of Google.

Re: Expanding Fuchsia's open source model

#78

So maybe open source, [mostly] closed ecosystem? Add a bunch of Spyware from Google and get every app maker to add a dependency to Google services and they are golden for the collection of data on all your "smart" things Sorry/not sorry for the cynicism; I feel it is warranted given what "open source" means on Android. Google talking like they have noble open source ambitions means nothing. They have a lot of amends…

Thank you for writing this so that I don't have to. :)

This would probably be a good time to mention https://github.com/zephyrproject-rtos/zephyr.

Re: Expanding Fuchsia's open source model

#79

So maybe open source, [mostly] closed ecosystem? Add a bunch of Spyware from Google and get every app maker to add a dependency to Google services and they are golden for the collection of data on all your "smart" things Sorry/not sorry for the cynicism; I feel it is warranted given what "open source" means on Android. Google talking like they have noble open source ambitions means nothing. They have a lot of amends…

yeah the base open sources Android is barely usable. Even simple things like getting a local notification at the right time are not a given. If they do the same with Fuschia, they'd better make it closed sources then.

Sorry, not familiar with Android core. For your example, how would it work without proprietary technologies? AFAIK, Android uses GCM for notifications. Adding integrations for it don't seem to make much sense in core open source Android as that will make you tied to Google's ecosystem.

Re: Expanding Fuchsia's open source model

#80
post #4

I've heard Fuchsia referred to as a "principal engineer retention project" at Google. I'd be curious to know if others have heard the same.

For all on this thread involved, thank you!

Since I was got into programming in middle school, I was obsessed with OS design (yeah, reading the source code for L4 in high school). As I went further in my education, I felt the landscape was pretty stagnate at this point and went into other areas (initially driver development and now developer tooling).

While I've not had a chance to jump over to Fuschia to participate, it warms my heart to see the development going on.

Post reply on HN