3 ms·

It's unfortunate that they are handing these out to the press at a time when developers still cannot get a device.

fabrice_d 14y ago
We only have a limited number of devices, and won't sell any ourselves. For sure we would be happier if geeksphones were available for all to use...
- MatthewPhillips 14y ago
  I know fabrice, this isn't your fault, but I consider it a PR mistake to give these to the press when developers cannot pay for them. Sends the message that press is more important than developers (which may be true, but not the message you want). If this had been a blog post from Twitter about how they integrated Web Activities into their mobile web app, that would have been really awesome.
  - fabrice_d 14y ago
    You mean, something like http://blog.twitter.com/2013/02/twitter-for-firefox-os.html http://blog.twitter.com/2013/02/twitter-for-firefox-os.html ?
  - bsimpson 14y ago
    Having Firefox OS hardware isn't that important at this stage - it's just an Android fork that runs on a handful of commercially-available Android devices. It would be great if Mozilla had a buildbot like Cyanogen's that posted images on a publicly-accessible FTP server for the 8 or so devices they support. I'd be willing to try Firefox OS on my Galaxy Nexus, and probably even write apps for it. But, I don't really want to download GBs of toolchain and Gonk source to compile my own image to be able to do these things.
    - fabrice_d 14y ago
      We can't distribute builds for most of these devices for legal reasons.
      - anoncow 14y ago
        If you can, can you point out the legal reasons?
        fabrice_d 14y ago
        We can't redistribute binary blobs (gpu drivers for instance) that you need when building the images to flash phones. They are exceptions though, like the nexus S.
        anoncow 14y ago
        So can we expect images for nexus 4?
      - bsimpson 14y ago
        Would making the Nexus line Tier One devices change this? Or perhaps a utility that backs up your local drivers, flashes the open binaries, then pushes the encumbered ones back to the device?

We only have a limited number of devices, and won't sell any ourselves. For sure we would be happier if geeksphones were available for all to use...

MatthewPhillips 14y ago
I know fabrice, this isn't your fault, but I consider it a PR mistake to give these to the press when developers cannot pay for them. Sends the message that press is more important than developers (which may be true, but not the message you want). If this had been a blog post from Twitter about how they integrated Web Activities into their mobile web app, that would have been really awesome.
- fabrice_d 14y ago
  You mean, something like http://blog.twitter.com/2013/02/twitter-for-firefox-os.html http://blog.twitter.com/2013/02/twitter-for-firefox-os.html ?
- bsimpson 14y ago
  Having Firefox OS hardware isn't that important at this stage - it's just an Android fork that runs on a handful of commercially-available Android devices. It would be great if Mozilla had a buildbot like Cyanogen's that posted images on a publicly-accessible FTP server for the 8 or so devices they support. I'd be willing to try Firefox OS on my Galaxy Nexus, and probably even write apps for it. But, I don't really want to download GBs of toolchain and Gonk source to compile my own image to be able to do these things.
  - fabrice_d 14y ago
    We can't distribute builds for most of these devices for legal reasons.
    - anoncow 14y ago
      If you can, can you point out the legal reasons?
      - fabrice_d 14y ago
        We can't redistribute binary blobs (gpu drivers for instance) that you need when building the images to flash phones. They are exceptions though, like the nexus S.
        anoncow 14y ago
        So can we expect images for nexus 4?
    - bsimpson 14y ago
      Would making the Nexus line Tier One devices change this? Or perhaps a utility that backs up your local drivers, flashes the open binaries, then pushes the encumbered ones back to the device?