[dev-servo] What would it take to make Servo a replacement for ChromeOS?
blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px
#715FFA solid !important; padding-left:1ex !important; background-color:white
!important; } So yes, there’s Redox as an alt-os in Rust and it’s quite early
for to start thinking this way, but perhaps not. A Servo based OS would have
many benefits. A browser engine based OS is where we should’ve been in 1994 if
we had more CS people aware of the true nature and goals of the (I)nternet as
imagined in the 60s and 70s.
With WebAssembly and competing technologies at its core, ServoOS can come
closer to a decentralized and scalable platform for all to share, use and
express on.
Again, from a technical perspective, what would this take to extend Servo to a
full OS?
Thanks
Sent from Yahoo Mail for iPhone
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] What would it take to make Servo a replacement for ChromeOS?
On 18/06/2017 22:04, Jose Marinez via dev-servo wrote: So yes, there’s Redox as an alt-os in Rust and it’s quite early for to start thinking this way, but perhaps not. A Servo based OS would have many benefits. A browser engine based OS is where we should’ve been in 1994 if we had more CS people aware of the true nature and goals of the (I)nternet as imagined in the 60s and 70s. With WebAssembly and competing technologies at its core, ServoOS can come closer to a decentralized and scalable platform for all to share, use and express on. Again, from a technical perspective, what would this take to extend Servo to a full OS? Thanks Hi, You may have heard of Firefox OS, also known as Boot to Gecko (B2G). It’s a lot like an hypothetical ServoOS in its core idea: “The Web is the platform.” Its components are split into three layers: * Gonk is roughly half of Android: the kernel, device drivers, the low-level rendering pipeline, etc. But not the Java VM, for example. * Gecko, Firefox’s rendering engine. In the case of Firefox OS, running directly on top of Gonk without the rest of a traditional operating system. * Gaia, the user interface (home screen, status bar, base apps) written in JavaScript/HTML/CSS and running on top of Gecko. All apps/websites also run on Gecko. Back in Servo land, a couple years ago we had an experiment called Boot to Servo (B2S): make Servo run on top of Gonk, with the goal of eventually being able to run Gaia and make Servo an alternative engine for Firefox OS. We got a prototype working on real hardware: https://blog.servo.org/2015/02/10/twis-23/#screenshots Last year, we removed the Gonk port from the Servo tree after Mozilla effectively abandoned Firefox OS. More background: https://medium.com/@bfrancis/the-story-of-firefox-os-cb5bf796e8fb -- Simon Sapin ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] What would it take to make Servo a replacement for ChromeOS?
blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px
#715FFA solid !important; padding-left:1ex !important; background-color:white
!important; } Thanks Simon for the info. Any idea where the code for Gonk is at
the moment? GitHub somewhere?
I might be interés in reviving this initiative.
Thanks,Jose
Sent from Yahoo Mail for iPhone
On Monday, June 19, 2017, 10:11 AM, Simon Sapin wrote:
On 18/06/2017 22:04, Jose Marinez via dev-servo wrote:
> So yes, there’s Redox as an alt-os in Rust and it’s quite early for
> to start thinking this way, but perhaps not. A Servo based OS would
> have many benefits. A browser engine based OS is where we should’ve
> been in 1994 if we had more CS people aware of the true nature and
> goals of the (I)nternet as imagined in the 60s and 70s.
>
> With WebAssembly and competing technologies at its core, ServoOS
> can come closer to a decentralized and scalable platform for all to
> share, use and express on.
>
> Again, from a technical perspective, what would this take to extend
> Servo to a full OS?
>
> Thanks
Hi,
You may have heard of Firefox OS, also known as Boot to Gecko (B2G).
It’s a lot like an hypothetical ServoOS in its core idea: “The Web is
the platform.”
Its components are split into three layers:
* Gonk is roughly half of Android: the kernel, device drivers, the
low-level rendering pipeline, etc. But not the Java VM, for example.
* Gecko, Firefox’s rendering engine. In the case of Firefox OS, running
directly on top of Gonk without the rest of a traditional operating system.
* Gaia, the user interface (home screen, status bar, base apps) written
in JavaScript/HTML/CSS and running on top of Gecko. All apps/websites
also run on Gecko.
Back in Servo land, a couple years ago we had an experiment called Boot
to Servo (B2S): make Servo run on top of Gonk, with the goal of
eventually being able to run Gaia and make Servo an alternative engine
for Firefox OS.
We got a prototype working on real hardware:
https://blog.servo.org/2015/02/10/twis-23/#screenshots
Last year, we removed the Gonk port from the Servo tree after Mozilla
effectively abandoned Firefox OS.
More background:
https://medium.com/@bfrancis/the-story-of-firefox-os-cb5bf796e8fb
--
Simon Sapin
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] What would it take to make Servo a replacement for ChromeOS?
You can look at what was removed in
https://github.com/servo/servo/pull/11474
I (still) think this is an interesting idea, and now doable out of the
main Servo tree. That could work well with the "services" model
envisioned in the B2G OS community
(https://discourse.mozilla-community.org/c/b2g-os-participation) that
almost no one had time to work on yet! The main issue to get something
really usable will likely be the current lack of support of many web
apis by Servo.
Fabrice
On 06/19/2017 08:48 AM, Jose Marinez via dev-servo wrote:
blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px
#715FFA solid !important; padding-left:1ex !important; background-color:white
!important; } Thanks Simon for the info. Any idea where the code for Gonk is at
the moment? GitHub somewhere?
I might be interés in reviving this initiative.
Thanks,Jose
Sent from Yahoo Mail for iPhone
On Monday, June 19, 2017, 10:11 AM, Simon Sapin wrote:
On 18/06/2017 22:04, Jose Marinez via dev-servo wrote:
So yes, there’s Redox as an alt-os in Rust and it’s quite early for
to start thinking this way, but perhaps not. A Servo based OS would
have many benefits. A browser engine based OS is where we should’ve
been in 1994 if we had more CS people aware of the true nature and
goals of the (I)nternet as imagined in the 60s and 70s.
With WebAssembly and competing technologies at its core, ServoOS
can come closer to a decentralized and scalable platform for all to
share, use and express on.
Again, from a technical perspective, what would this take to extend
Servo to a full OS?
Thanks
Hi,
You may have heard of Firefox OS, also known as Boot to Gecko (B2G).
It’s a lot like an hypothetical ServoOS in its core idea: “The Web is
the platform.”
Its components are split into three layers:
* Gonk is roughly half of Android: the kernel, device drivers, the
low-level rendering pipeline, etc. But not the Java VM, for example.
* Gecko, Firefox’s rendering engine. In the case of Firefox OS, running
directly on top of Gonk without the rest of a traditional operating system.
* Gaia, the user interface (home screen, status bar, base apps) written
in JavaScript/HTML/CSS and running on top of Gecko. All apps/websites
also run on Gecko.
Back in Servo land, a couple years ago we had an experiment called Boot
to Servo (B2S): make Servo run on top of Gonk, with the goal of
eventually being able to run Gaia and make Servo an alternative engine
for Firefox OS.
We got a prototype working on real hardware:
https://blog.servo.org/2015/02/10/twis-23/#screenshots
Last year, we removed the Gonk port from the Servo tree after Mozilla
effectively abandoned Firefox OS.
More background:
https://medium.com/@bfrancis/the-story-of-firefox-os-cb5bf796e8fb
___
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo
[dev-servo] Mozilla central backout support arriving to Servo later this week
tldr: If you see some PRs from the moz-servo-sync GitHub user with a priority of "treeclosed," it's because those must be landed into Servo ASAP to support Firefox backouts. Due to some amazing work from gps, we already have support for taking code changes that occur in Servo on Github and automatically pushing them to the Firefox Mercurial servers. Now that stylo will soon be building by default, we will need to go the other way, too - pushing changes made in Firefox back to Servo. The key first scenario here is supporting "backouts" from Firefox. Backouts are basically undo commits that revert a change that the test-after-checkin system has determined to be faulty. This manual process, performed by administrators known as sheriffs, needs to be instant and atomic across the repos. The solution that we've implemented is: 1) The backout / undo commit is landed in Firefox. 2) A PR is created on the Servo side, authored by the moz-servo-sync user, with a priority that closes the Servo tree until the PR lands. This is important due to the fact that we sync changes from Servo instantly and automatically to Firefox, and do not want to have two versions of history [1]. 3) The PR is tested by homu and ultimately landed. If the undo commit from the sheriffs does not actually compile or otherwise pass Servo tests, we should push *additional commits* on top of the undo commit that fix up the PR until it lands. The original commit authored by moz-servo-sync should not be altered. This process should only be hit in the event that there is a backout on the Firefox side of things that also touches Servo code. Hopefully, such backouts are extremely rare events, and should be even more rare once we support a basic in-Firefox build & test for the geckolib code by homu. We are planning to test this support via some dummy backouts (e.g., edits to Readme.md) later this week, at a time when the queue is quiet. Thanks for your patience as we roll this out and sort out any initial kinks in the system! - Lars [1] There is a race condition here, where homu lands a commit to Servo master but the vcs-sync has not propagated it to Firefox as the sheriff performs the backout. We believe this window is only a few seconds and hope not to hit it, but have some plans in place for how to manually fix up this situation if it occurs, which will be separately documented. ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
Re: [dev-servo] [stylo-team] Mozilla central backout support arriving to Servo later this week
Thank for everyone's efforts here. There never seems to be a perfect solution in technology, but I am happy we've found a solution that satisfies most of the constraints and were able to deploy it in time. For anyone that didn't already see it, glob wrote about the design here: https://blog.glob.com.au/2017/05/08/servo-vcs-sync/ jack. On Mon, Jun 19, 2017 at 1:48 PM, Lars Bergstrom wrote: > tldr: If you see some PRs from the moz-servo-sync GitHub user with a > priority of "treeclosed," it's because those must be landed into Servo ASAP > to support Firefox backouts. > > Due to some amazing work from gps, we already have support for taking code > changes that occur in Servo on Github and automatically pushing them to the > Firefox Mercurial servers. Now that stylo will soon be building by default, > we will need to go the other way, too - pushing changes made in Firefox back > to Servo. > > The key first scenario here is supporting "backouts" from Firefox. Backouts > are basically undo commits that revert a change that the test-after-checkin > system has determined to be faulty. This manual process, performed by > administrators known as sheriffs, needs to be instant and atomic across the > repos. The solution that we've implemented is: > 1) The backout / undo commit is landed in Firefox. > 2) A PR is created on the Servo side, authored by the moz-servo-sync user, > with a priority that closes the Servo tree until the PR lands. This is > important due to the fact that we sync changes from Servo instantly and > automatically to Firefox, and do not want to have two versions of history > [1]. > 3) The PR is tested by homu and ultimately landed. If the undo commit from > the sheriffs does not actually compile or otherwise pass Servo tests, we > should push *additional commits* on top of the undo commit that fix up the > PR until it lands. The original commit authored by moz-servo-sync should not > be altered. > > This process should only be hit in the event that there is a backout on the > Firefox side of things that also touches Servo code. Hopefully, such > backouts are extremely rare events, and should be even more rare once we > support a basic in-Firefox build & test for the geckolib code by homu. > > We are planning to test this support via some dummy backouts (e.g., edits to > Readme.md) later this week, at a time when the queue is quiet. > > Thanks for your patience as we roll this out and sort out any initial kinks > in the system! > - Lars > > [1] There is a race condition here, where homu lands a commit to Servo > master but the vcs-sync has not propagated it to Firefox as the sheriff > performs the backout. We believe this window is only a few seconds and hope > not to hit it, but have some plans in place for how to manually fix up this > situation if it occurs, which will be separately documented. > > -- > You received this message because you are subscribed to the Google Groups > "stylo-team" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to stylo-team+unsubscr...@mozilla.com. > To post to this group, send email to stylo-t...@mozilla.com. > To view this discussion on the web visit > https://groups.google.com/a/mozilla.com/d/msgid/stylo-team/CABO6m45F1ud_vFbR59WzG1Gf48-CFYRiHQvT1ij1MGQwPzMLJQ%40mail.gmail.com. ___ dev-servo mailing list dev-servo@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-servo
