Earlier quoted context omitted.
So not 100% open source. Thanks for the info
Above a certain complexity, there is basically no 100% open-source hardware out there. Like none of the Pinephone, Librem, Framework laptops are "open-source" to the bone.
Pebble Watch software is now open source
151–160 of 236 posts
Re: Pebble Watch software is now open source
#152I'm sure its happened before, but this is the first time i finally get to see some sort of modern hardware in KiCad. Pretty cool to see all 6 layers, paste layers, and adhesive layers as well. I've always wondered how the cake was made and if big projects do/could use KiCad. Seems like a lot more work relative to those Single Layer PCBs on YouTube for things like emulators and custom PCBs. Glad I now know for sure, t…
You almost certainly could do it - obviously with some time investment. Getting multi layer PCBs made is surprisingly affordable now.
Re: Pebble Watch software is now open source
#153A little surprised there has been no mention of the app being Kotlin multiplatform. https://github.com/coredevices/mobileapp I had heard of many smaller apps using Kotlin for their iOS app, but this may be the biggest all in multiplatform app I've seen. It would be awesome if there may eventually be support for writing Pebble apps in Kotlin.
Re: Pebble Watch software is now open source
#154Earlier quoted context omitted.
From the article: >Another important note - some binary blobs and other non-free software components are used today in PebbleOS and the Pebble mobile app (ex: the heart rate sensor on PT2 , Memfault library, and others). Optional non-free web services, like Wispr-flow API speech recognizer, are also used. These non-free software components are not required - you can compile and run Pebble watch software without them.…
If they are not mandatory it's 100%. Otherwise according to your standard, Debian is not 100% free software either.
Re: Pebble Watch software is now open source
#155Earlier quoted context omitted.
Well the Pebble specific parts are. This is an unfortunate state of affairs from hardware manufacturers, they are very late to the open source game, if at all.
From the article: >Another important note - some binary blobs and other non-free software components are used today in PebbleOS and the Pebble mobile app (ex: the heart rate sensor on PT2 , Memfault library, and others). Optional non-free web services, like Wispr-flow API speech recognizer, are also used. These non-free software components are not required - you can compile and run Pebble watch software without them.…
Re: Pebble Watch software is now open source
#156Re: Pebble Watch software is now open source
#157Earlier quoted context omitted.
That is incredibly fantastic feat of engineering!
Exciting, except it runs Android Wear OS by Google instead of a deGoogled OS, and in the comments it says: "Repairability is admirable but only 3 years of security updates isn't near enough" FTA: "We’re also making sure that our new watches are more repairable than old Pebble watches. The back cover of Pebble Time 2 is screwed in. You can remove the back cover and replace the battery." So the battery of the Pebble Ti…
After Pebble went kaput, I got an Apple Watch through a work reward thing and honestly it’s been solid. I turned off a lot of notifications and mostly use it for things I really want to know, some light exercise tracking, time and weather.
Re: Pebble Watch software is now open source
#158Earlier quoted context omitted.
Above a certain complexity, there is basically no 100% open-source hardware out there. Like none of the Pinephone, Librem, Framework laptops are "open-source" to the bone.
So don't say 100%? Not hard.
So given that the word doesn't really apply to hardware, I believe they used it correctly (100% means the set of things where it makes sense to be used) and are not misleading. In fact I strongly dislike some of the "open-hardware" marketing of some previously mentioned devices, when that is obviously false and misleading.
Re: Pebble Watch software is now open source
#159Earlier quoted context omitted.
Please note our CLA explicitly include a clause to require Core Devices to distribute all contributions under an OSI-compatible FOSS license (e.g. GPLv3). So no contributions can be 'stolen'. https://ericmigi.notion.site/Core-Devices-Software-Licensing...
But OSI-compatible FOSS licenses include pushover ones like MIT, so even though you couldn't steal all of the contributions to make a proprietary fork, any other company then could.
Calling it "stealing" doesn't help.
[1] I'd usually call it a distraction, a sleigh of hand, smoke and mirrors, but we have to give Eric credit for not burying the CLA.