On one hand - it makes sense to push for more visibility - to test the depths of their commitment to right-to-repair.
On the other hand - being overly critical about a new entrant that is attempting to address the right-to-repair market for not getting everything perfect from the get go might send the wrong signals about the right-to-repair market to the rest of the industry.
It seems like a delicate balance might be wise. Having module level repairability for LCD panels, connectors, drivers, memory is a pretty big step relative to the other OEMs.
Perhaps the best analogy would be Raspberry Pi schematics which are also reduced [1] and IMHO, the RPi has generally been a plus for the open source hardware/software community. Similarly I could definitely see Intel having some trade secrets as you get closer the CPU.
Yep, we absolutely understand and respect Louis and community members' requests for full schematics, and we appreciate the folks who extend understanding as we work through constraints (including Louis as noted in that last video). We're continuing to make as much open as we can, and we're adding to that list as we go:
This is the challenge of trying to do good - no matter how much better you are than the default, for some subset of users you will never be good enough, and they’ll complain just as loudly about you as they do the default (far worse) option.
Unrealistic purity tests ruin all sorts of attempts to make the world a better place. We should celebrate attempts to change the status quo.
I think the difference is in the (perception of) honesty or hypocrisy. If Apple jealously guards details about their hardware and impedes repairs, it's bad but it's expected. If Framework guards details about their hardware and impedes repairs, it's in direct opposition to their claimed mission and the reason people were interested, and it feels like a betrayal. (Obviously this varies; not everyone cares about the same things or to the same degree. But I suspect that's this is where a lot of the dissent comes from.)
The problem I have is that if these requests are unrealistic, they should just say that. As far as I can tell, what they're currently doing requires more effort to vet repair shops and create an NDA than if they just dumped the schematics online.
Now, maybe there's a great reason for this. Maybe they're under NDA and can't reveal part of the schematics. Maybe releasing these schematics would make it super easy for a competitor to completely steal everything. Maybe they are going to release the full schematics and we're waiting on their engineering team and legal team to review them.
The problem here is that Framework hasn't communicated any of this. Every time they're asked they don't seem to give any reason and just dodge around with "we'd love to release the full schematics". Well, why haven't you then? Please tell us.
> Now, maybe there's a great reason for this. Maybe they're under NDA and can't reveal part of the schematics. Maybe releasing these schematics would make it super easy for a competitor to completely steal everything. Maybe they are going to release the full schematics and we're waiting on their engineering team and legal team to review them.
I guess I'd question 'fear of competitors' being a "good" reason, but I'd agree with you otherwise. Regardless of what the need for secrecy is, unless it's "we're forbidden by the state" and there's some kind of national security letter involved or "We're doing something illegal and we'd get sued if it were known to the public", why not just tell the public why they can't release the full schematics? What else would prevent someone from talking about why they couldn't talk about something? Refusing to even explain themselves just makes it all seem more suspicious.
Sometimes NDAs prevent even revealing the scope of the NDA, because knowing the scopes of things is then potentially exposing information a party doesn't want known by others. Sure, maybe Framework could just go and state those things, but they're potentially burning their relationships with key partners that might be necessary to make the product at the moment.
I'm not arguing this is a good thing, just trying to share some perspective.
One might even imagine someone would write something like this in an effort to reinforce the parents the point.
The strongest interpretation of "we'd love to release the full schematics" the subtext: but we can't / don't want to due to "reasons*, none of which are likely to satisfy everyone, so we'll try to avoid that discussion as it would help distract us all rather than getting on with our goals.
The strongest and most likely interpretation is that they simply don't own the IP, and it's based on a licensed reference design. It makes zero sense for a startup like this to have done all of it from scratch - just copy everything possible and innovate the actually interesting parts. If they don't own the design, they can't say that due to NDAs, and the best they can do is a maximally broad interpretation of "repair shop".
IMHO, the best they can do is being honest about what they can't say due to an NDA. For example, if they can't say that they don't own the design, they might say "due to an NDA we cannot say who owns the design". This goes a long way to earn trust.
>Our main manufacturing partner is Compal, who makes laptops for many other large US notebook makers.
>Apart from off the shelf modules like the SSD, RAM, WiFi, and LCD, the Framework Laptop is entirely custom to us, and we own all of the design and tooling.
If you locate Acer Swift 3 SF313-53 diagram it will be 90% same thing, just shuffled around with different mechanical design.
They might be owning the design itself, but I can easily imagine that the NDAs required to get access to specifications and design guidelines for parts like the CPU, GPU and other chipsets include a provision that no material must be released that allows others to clean-room reverse-engineer the protected material.
There are limits to contracts in the law. There would have to be some form of consideration to that contract. If you gave me a million dollars a year but I just can't use my current legal name in casual conversation, I'd take that contract. If you just wrote a contract that said "you can't use your name, you get nothing" its an unenforceable contract under US (and most of the developed world's) contract laws under the principle of consideration.
I wish "innovative, actually interesting parts" would include delivering an actually repair-friendly laptop - that is - one with full schematics; only ICs that are normally in-stock on digi-key/mouser; no soldered-down components made of melty plastic, especially not next to places that are likely to be reworked; soldermask that doesn't obscure traces; all important signals brought to accessible probe points; mechanical design/connectors/cabling allowing for easy power-on outside of chassis, etc...
Sure, QR stickers and a bunch of new/incompatible iteration of good old ExpressCard are nice to have, thank you, but that doesn't make all that big of a difference to repairability.
This sounds like a great set of constraints for an industrial controller, or a custom Cyberdeck-type portable.
I’m confident any device following these guidelines would be DOA in the larger market, though. Even _if_ you could source things like LCD assemblies that fit your criteria, the expected density (high) and labor costs (low) people have for modern electronics don’t leave a lot of room for this kind of bespoke design.
I’m extremely impressed with how far Framework got on the path to “full repairability” using off-the-shelf parts without producing something that looks like a late-90s Thinkpad.
Don’t get me wrong: I love the old IBM, Tadpole, Toshiba, et. al. designs, but I don’t think that many people outside this community would be willing to pay 2-3x as much for something 2-3x larger and heavier and several generation behind in terms of performance. (Not to mention wildly incompatible with any non-hobbyist OS.)
OTOH, what you’re describing does sound a lot like why custom, hand-wired audio amplifier builders do. They manage to make a business out of it, mainly by appealing to folks willing to spend effectively unlimited money to get that “special something”.
Not sure what you meant by "full repairability", but for component-level system board repair, framework laptop is not far at all from current-gen lenovo or macbook. That's the whole point of OP's video.
User-replaceable RAM, SSD and keyboard are all steps in the right direction, of course. But it would be quite a stretch to give product full marks on repairability based on that alone.
And no SMD mounted connectors, only hole through connectors. The problem with that is that it will preclude the use of certain kinds of cables because the whole industry has now pretty much moved to SMD where possible to shave off the last couple of percent cost.
External connectors are pretty much the only kind of component that is still routinely being used in (full or partial) through-hole form-factor.
Laptop in question does use partial through-hole connectors for all 4 USB-C ports - notice 6 shiny slots around each such port around 0:25 mark in video. Such connectors are actually harder to rework/replace, but also tougher and less likely to require repair in the first place. So overall, well-done here to framework, even if most everybody else is doing that too.
honestly with how much heat the ground plane can soak up on modern electronics, desoldering a beefy through hole ground connector is such a pain in the ass I might rather they be SMD if I have to do something with them in general.
I feel its likely the marketing verbiage w.r.t. repairability was targeting the average "prosumer level repairability" - which is probably more closer to an iFixit level of repairability (i.e. more on the torx screw and less on the solder/depop spectrum of repair) [1].
That said in response to these HN and Youtube threads - perhaps they could update it to be more specific about their definition of repairability as well as why schematics will be or can't be released.
In the future - if Intel is the issue - it might be smart to design some additional modularity and relegate the proprietary Intel stuff to some sort of system on module (like the RPi4 Compute Module) and increase the amount of open source able main board.
It seems likely that the 'module' would just cover the entire space of the board as-is if they did this with a modern intel system anyways, especially when there's also SODIMM module slots, an m.2 slot, and 4 full tb4 ports on the board.
All those high speed bus interfaces are probably tied directly into the CPU, the chipset, or both, and so are largely gonna be covered by any confidentiality agreement intel imposes on vendors of those parts.
The Pi4 CM is a much more modest device by comparison. It has no ram expansion and only a few lanes of PCIe, USB3, and some other fairly standard IO interfaces otherwise.
Realistically, the frame.work mainboard is the compute module. You plug it into the equivalent of a CM carrier board with the TB4 ports.
It's not just about the reason, but other details too. Does "we'd love to release them" mean "we just mean more time", "there's a 50/50 chance we'll be able to release them", or "we'd love to but it's a long shot". If they are going to come out, will it be in weeks, months, or years?
Them not mentioning it, despite mentioning it making their optics better, pretty much seem to point to the NDA not even letting them discuss the stuff you stated.
The watch industry used to vet repair Watch Repair shops on the guise of "Quality Assurance". They would require Watchmakers buy their expensive cleaning machines, and a bunch of other pricy tooling, and requirements; in order to procure parts. 90% of watchmakers couldn't get a parts accout, and the watch companies loved it. it meant more after sales/warranty business.
This was because they didn't want to sell parts to anyone. They wanted to do the repairs
For a few years, certain Watchmakers kept up with the demands from Rolex, and The Swatch Group.
We were just happy to be able to get parts.
About 15 years ago the watch companies just decided not to sell parts to anyone.
That whole Vertical Intregtation consumer ripoff.
I am very leary of any company that wants to vet their repair shops for anything, other than maybe medical equipment.
They will supply the schematics, but they don't want to make it easy.
It is not them though, they clearly just follow rules here that they have to obey. But I think it is a great idea to compare it with the watch market - independent repair shops there have neven seen like a bad idea, and the schematics are pretty much always open - in that the movement is just there, accessible - and the watches are copyable. Which happens a lot though - might not be the most convincing argument if that were the fear.
> (...) no matter how much better you are than the default, for some subset of users you will never be good enough (...)
What if it is really not good enough?
Should everyone just accept someone's claims that they addressed a problem when they might be actually making it worse by pretending it's solved when it isn't?
I recall the days of old when no laptop supported linux, and the impact there was when a model showed up with claims it indeed supported linux. I bought one based on those claims (don't recall the make-model, might have been an Acer) and I still recall the disappointment I felt when I discovered critical stuff like wifi did not worked at all. There were a few comments like "It boots, right?" followed by "for some subset of users you will never be good enough" when critical problems were pointed out, but the truth of the matter was that a purchase was made based on a feature that was advertised but was in fact not offered.
> and they’ll complain just as loudly about you as they do the default (far worse) option.
This is optimistic. They'll lampoon you and call you hypocrites for claiming to be helpful but not doing the zillions of things they have in mind, while giving the unfriendly incumbent a pass.
I'm not sure who they is in this context but the person who runs the channel linked in the topic and who is normally in the videos has consistently praised Framework for their efforts, including the release of these public schematics, regardless of being partially complete, and has reminded viewers how it compares to other brands that don't release anything of the kind for helping repair shops.
In a recent video they were considering buying a second Framework laptop of their own just to have it displayed in videos as essentially free advertising. If some of these characterizations are about them it seems misplaced tbh.
Same "they" as the parent-- "for some subset of users you will never be good enough, and they’ll complain just as loudly about you as they do the default (far worse) option." Not implying that it's the channel's stance.
On any criterion: ease of repair, privacy, security, good citizenship, etc: there's some subset of critics who treat the best behaved companies and individuals worse than the worst. These are the people who e.g. give Apple a much harder time on privacy than Meta.
> . We should celebrate attempts to change the status quo
yes but... no. if you go half way to do something you will not reap much of the expected benefits. in certain use cases hard thresholds are important to consider. in this case half available schematics is not good enough to do repairs even if its better than no schematics at all.
But half way to something here is demonstrably better. The computer opens with ordinary tools and the parts are modular and available! It was also stated above that this repairer did not ask for the schematics.
Similarly I could definitely see Intel having some trade secrets as you get closer the CPU.
If they're "secrets", they're probably one of the worst-kept in the industry.
You can already find plenty of other, probably leaked, schematics of laptops using the same if not very similar platform. They are all based on reference designs from Intel, after all. It's inevitable that yours will leak too, hopefully sooner rather than later.
Hence I am strongly siding with the "marketing BS" people here. Claiming to be so strongly in support of RtR, and then turning around and keeping the barely-existing artificial moat up, is practically not much better than all the other laptops that already have schematics available.
Agree - I think Intel would have a big say in what it wants released under no NDA. It's important to keep in mind - NDA's aren't always meant to prevent the average person from accessing it ever. In fact it'd be most likely primarily used to enable an Intel (or Framework) legal team to have some leverage to go for damages against the most extreme cases of abuse [1].
Also - w.r.t. to right to repair - I've always gotten from their marketing more of a right to repair at the iFixit level (swap SSD, memory, LCD panels, keyboards, etc.) versus de-popping the Intel CPU.
Hopefully Intel's lawyers realise that suing its customers who are buying its products would be a bad idea. If anything, getting Intel to open up more documentation --- like it used to have --- would increase sales and community reputation. Especially with its diminishing performance lead, and the rise of performant but even more horribly proprietary ARM SoCs, opening up seems to make even more sense. Remember that x86 and the PC architecture dominated the computing industry because it was open.
Hopefully may or may not be sufficient for them to bet the farm on.
Knowingly breaching a contract you've already invested many dollars and hours building and understanding, against the advice of your legal council, seems risky.
Additionally - while the legacy bemoth Intel is getting onboard with open source schematics (and figuring out its strategy to open source the VHDL for its 12th gen core to compete against RISC-V - perhaps now that Gelsinger who is more technical than the previous CEO - there is some hope!) -- the question is whether we'd rather see a product like Framework make inroads despite the roadblocks and build up marketshare to further the case toward right to repair.
Interesting. That said - its one thing to have a knowledge base likely targeted toward corporate IT teams with direct access to order-able parts via Lenovo value added resellers and another to put it on the landing page for a consumer facing laptop.
It'd be a huge win in fact for right to repair if Lenovo did do this in response to Framework.
Thinkpads have always been very repairable at the module level since they were still called IBM Thinkpads. You can also find schematics for them on other sites.
Sooner or later one of those repair shops is going to leak those schematics. Either intentionally or accidentally, it won't matter.
To me, it feels like Framework is creating a lot of extra work and damage to the brand, just for delaying the inevitable.
Instead of lawyers, hire engineers to support the repair shops. Wasn't the whole promise of Framework that it would be repairable?
Or maybe the laptop "that respects your right to repair", and "that respects the planet" and "that's designed to last" is just another load of marketing bs.
As a framework owner I wouldn't personally care if they never released them at all. What makes the framework repairable isn't board-level schematics, its the modularity and access (similar to a desktop). If a part in my framework breaks I'll just replace the individual part. IMO there is no brand damage here outside of some purists calling for things 99.9% of customers don't give 2 shits about.
>outside of some purists calling for things 99.9% of customers don't give 2 shits about.
I'm sure if Louis or another technician told you "I could fix your mainboard, but I don't have the schematics. Buy a whole separate board for $400 and I'll install it for you." You might be a little ticked.
1) Framework provides schematics to repair shops that ask
2) Modularity keeps the cost of individual components so low that board-level repair isn't nearly as important. What would Louis charge me? $350 at least for shipping and time according to similar quotes I've seen of his.
I was an aviation electronics technician in the Navy, and I can say from experience that it is very easy to underestimate the time and effort that can go into a component-level repair job.
I once troubleshot a faulty RF power meter down to a single transistor, and it was incredibly gratifying to see it working after replacing a sub-$1 part but if I was paid by the hour it would’ve been an unprofitable job for sure.
>2) Modularity keeps the cost of individual components so low that board-level repair is hardly worth it. What would Louis charge me? $350 for shipping and time?
I don't know where you get your numbers, and Louis isn't the only person in the world with the ability to repair this stuff; you can make up a number so that it seems anti-competitive against the idea of modularity and buying a whole new replacement module -- but let it be said that these repairs can be done fairly cheap with some research and a bit of parts gathering. Cheaper than 350 cheap, in most cases.
> but let it be said that these repairs can be done fairly cheap with some research and a bit of parts gathering. Cheaper than 350 cheap, in most cases.
I don't know about that for component level repairs. Sure you can replace a hard drive, memory, a wifi card or a fan but those can all be done already with the Framework laptop without the detailed schematics. Most people are not knowledgeable enough and even if they were they likely wouldn't feel comfortable doing component level repairs on a motherboard, especially if they have to do any soldering. There's a reason that the vast majority of places computer repair places don't do component level repairs. You need a lot of expertise to do so, and that expertise doesn't come cheap.
> There's a reason that the vast majority of places computer repair places don't do component level repairs. You need a lot of expertise to do so, and that expertise doesn't come cheap.
you also need tooling. $20 radio shack soldering iron from dad won’t do it for anything that’s worth the labor costs.
if you don’t have any of that you’ll be spending $350 to get the bare minimum to practice the job.
$350 is basically free in terms of skilled technician time to solve a problem that requires any non-trivial amount of investigation. You're devaluing the labor and thinking only in terms of the raw materials.
> You're devaluing the labor and thinking only in terms of the raw materials.
very common for folks to compare the cost of having something assembled for the first time in a low-wage country, to having it disassembled, diagnosed, repaired, and reassembled in a high-wage country.
See my above comments - I've had board level repairs done before and they aren't cheap. Best case scenario with the framework modular design, you save $50 and get back an old part that is prone to additional failures. With modularity you can buy and replace just the part you need and maybe even upgrade while you're at it.
Having both would be ideal but isn't always practical due to agreements with chip suppliers etc. Framework is a huge step in the right direction and I don't think being puristic about things is helpful for the right to repair movement.
No, not at all. The whole idea is modularity, upgradabilty and access. Most technies people know how to swap out an nvme or ram, basically any ifixit level repair. Board level repairs is a whole other ballpark and the need is reduced greatly due to a modular design.
People like that desktops are modular, you can easily replace a single part when it breaks or upgrade a part too. Framework is the equivalent for laptops.
> some purists calling for things 99.9% of customers don't give 2 shits about.
It is really arrogant to proclaim that 99.9% of consumers share your opinion and financial privilidge of not caring about repairs.
Polls consistently show that modt xustomers want repairs and repairability, for laptops >50%, and something like 30% would attempt repairs themselves.
We have a real problem with folks like yourself denying that we, people who want repair, even exist. And companies making parts impossible to get hold of.
Are you talking about soldering on the mainboard, or replacing broken parts? It's hard for me to imagine that 30% of customers want to attempt to solder new parts onto their laptop mainboard, which is what I think this discussion is about. There's more discussion upthread, but work that requires board schematics also requires exceptional tooling, expertise, and time, and is therefore also quite expensive ($250-$425 was the number quoted upthread).
> work that requires board schematics also requires exceptional tooling, expertise, and time, and is therefore also quite expensive ($250-$425 was the number quoted upthread).
Stop thinking about the West, the rest of the world exists.
Where do you think your monitor goes when you throw it away because an $1 capacitor has blown? Not into a black hole. Our broken devices get shipped to other countries as e-waste.
There cost of labour is $5 and people want to repair that device and keep it going for 40 years.
If you want ti say 'i dont care about other countries', then you will have to recycle this shit domestically and pay real money for it's disposal- and then repairing will look different economically
>Stop thinking about the West, the rest of the world exists.
Framework only sells in the west and the west (and 1st world/highly developed countries/regions outside of the west) account for pretty much all high end laptop sales - your diatribe doesn't really hold up even so though. The modularity of the framework means less ewaste than the status quo - that is a net positive.
Again, youi are missing the forest for the trees - when you sell old laptop on ebay, where does it go? When you get rid of the laptop and give it to recycling, where does it go?
It goes to a second or third world country, where they will try to repair and use it if possible.
Very few institutions in the west actually recycle anything.
And only 4 other laptops have scored as high as framework for repairability since 2010 - and only 1 other from this decade, none of which were as modular or upgradeable after the fact.
>What makes the framework repairable isn't board-level schematics, its the modularity and access.
why not both?
no one in their right mind can argue that NDAing and walling documentation aids the repair effort.
so.. in other words.. framework is repairable up until the point that it may hurt their bottom-end profits; then you're on your own.
maybe they should get into selling board-level components so that they have a financial incentive to act morally and within their projected image of 'right-to-repair' advocacy.
You're making a very bold claim that they won't do it because of money. In an earlier video, Louis Rossmann said he can't publicly say what those reasons are but that he understands them. It is not something I would expect him to say if it was purely "they want to make more money."
What would be a legitimate reason that he can't publicly say why? Certainly he would be allowed to say that Intel or some other supplier doesn't allow them to share the specs. So it must be some other reason.
> What would be a legitimate reason that he can't publicly say why?
I have no idea. Don't have a clue. However, given that I don't have any idea, I'm not going to go around making bold definitive claims like 'they do it because they want more money."
> maybe they should get into selling board-level components so that they have a financial incentive to act morally and within their projected image of 'right-to-repair' advocacy.
That might help if the component packs had a decent loyalty markup. I'm sure repair shops and DIY'ers would love to have access to guaranteed-exact-same-components. Just buying the same number from the datasheet doesn't always guarantee identical electrical characterization across different manufacturers and batches.
The primary issue Framework is facing (AIUI) is that if they release the complete board-level schematics, enterprises in Shenzhen will immediately release Framework clones (and sub-module clones) which are part-for-part compatible with the actual Framework laptops. This could undercut their business model at a very high-risk time for their company. They're incredibly capital-constrained and need to meet their pricing/sales targets just to survive (not even considering making their investors happy). Framework is a bit of a "Tech Fad" at the moment, and consumers have historically been known to be incredibly price-conscious, even sometimes demonizing the companies who did the original innovation after they can't meet or beat the clones prices or functionality (I recall this with Arduino). This would make me super wary of releasing the full schematics as well.
I would be very suprised if Rossmann Repair was unaware of the NDA. I suspect Framework are being very very magnanimous in their communications here. Rossmann Group probably omitted that context in slightly bad faith to pressure Framework a bit more. That's normal for zealots -- and it is still a symbiotic ecosystem...Rossmann Group laid so much of the foundation needed for Framework to thrive! Also some of Framework's investors (Linus of Linus Tech Tips) were directly responsible for mediating/facilitating/negotiating the current schematic NDA arrangement after listening to Rossmann's critiques as a pre-condition to investing their money, time, and reputation. It would be strange if that story had somehow slipped past Rossmann Group...
[Edit: According to others, Louis has a video where he acknowledges the current situation and empathizes with Framework about it, so clearly Rossman is aware. Other people have since mentioned that Framework may be legally unable to release the schematics because they are based on licensed designs from an ODM or chipset/component supplier. In which case, perhaps this video from Rossmann group is designed to help the public put pressure on those upstream IP stakeholders.]
I do agree with 'LeonM. Eventually the detailed schematics they provide to repair shops will leak or be stolen or whatever anyways. But I understand Frameworks concerns.
There's a need for truly open source hardware. Please support the projects at CrowdSupply[0] ... many of which do have truly open source hardware+software+schematics+PCB Layout Files. And they are nearly all very very small "cottage industry" side-gigs which desperately need the financial enthusiasm and participatory enthusiasm of early adopters in order to thrive.
Lack of schematics does not stop anyone in Shenzhen. If they want to clone your device, they will clone your device, along with its packaging and the store it's sold in.
Aren't all laptops that aren't macs easily repairable?
RAM, SSD, battery, keyboard(but in many laptops the whole top panel has to be replaced), track pad, wifi card, display(framework has the better way only over here).
I mean buying a tongfang OR a system 76 is a way better option than going for framework due to its QR codes I don't understand why.
I'm not shitting on framework this is just what I've been wanting to ask for so long
I give a shit what happens to the module I replace. Individual parts go down to the components on the board, there is a distinction between repair and replace.
I believe the manufacturer places limitations on the availability of the schematics, not Framework. Iirc Framework had to negotiate with their manufacturer in order to get them released to repair shops.
> Sooner or later one of those repair shops is going to leak those schematics. Either intentionally or accidentally, it won't matter.
While you may be right, the trade secret value of the schematics decreases by the day. If they can delay schematic leaks for months or even a year, that's still a big win. They'll be on to the next generation by then.
While it may seem futile in the end, delaying the inevitable leak and demonstrating to your partners that you made a best effort attempt to keep them confidential is actually a huge win.
> Sooner or later one of those repair shops is going to leak those schematics. Either intentionally or accidentally, it won't matter.
If one of the repair shops leak the schematics, it's probably fine for them — it means Framework isn't the one on the hook for any liabilities of the leak. Heck it wouldn't be surprising if they were (unofficially) happy about it.
In general, Framework has been extremely transparent, but they haven't given specifics about this issue. In a previous video ( https://www.youtube.com/watch?v=8cJj8PUY0DU ), Louis Rossman mentions that he asked Framework why they wouldn't release schematics and was given an answer (that he deemed valid) on the condition that he couldn't publicly say what that answer is. I imagine it's because of some sort of legal agreement, either with the ODM that designed the motherboard or one or more of their chip suppliers. I doubt it's for fear of cloning, leaked schematics for products from a variety of manufacturers (Apple, Dell, Lenovo, Samsung, etc) have been available for years and you don't see any cloning going on there.
> I imagine it's because of some sort of legal agreement, either with the ODM that designed the motherboard or one or more of their chip suppliers. I doubt it's for fear of cloning, leaked schematics for products from a variety of manufacturers (Apple, Dell, Lenovo, Samsung, etc) have been available for years and you don't see any cloning going on there.
This doesn't make sense to me. If it was because of a legal agreement I imagine they'd just publicly say that they can't "for legal reasons" and everyone would just shut up about it because, hey, it's not strictly their fault, so why give them grief about it? An easy way to snip the whole "no schematics" controversy in the bud. "Sorry, we can't release them publicly for legal reasons, but for future products we'll try to negotiate with the vendors to allow it." And they're done.
But the only thing we get is radio silence, so either they don't want to explicitly say that it's "for legal reasons" (which, again, doesn't make sense to me), or because it's due to something else.
Publishing schematics doesn't mean publishing the PCB design, which is where most of the work is. If you wanted to clone Framework you could just as easily grab the leaked schematic for any other Intel laptop, they're all functionally equivalent.
I bet Framework has a legal agreement with someone not to publish the schematic so they're sharing it with repair shops under NDA so they're not liable when it leaks.
Somebody can & will co-opt their production & magically sell it for less if they completely open source things. Cuz third world country labor n shit.
Lack of published schematics means that the Chinese cloners will not be able to copy the design in 2-3 weeks as usual. Instead it will take them at least 14-21 days.
> We also make full schematics and assembly drawings available to repair shops who get Framework products in for repair
But what about individuals who need to repair their own Framework products? If schematics and boardviews are only avaailable to repair shop businesses, that seems to completely contradict most of the copy on the framework site such as:
"Our philosophy is that by making well-considered design tradeoffs and trusting customers and repair shops with the access and information they need, we can make fantastic devices that are still easy to repair"
Louis has dozens upon dozens of videos where he fixes macbooks doing component-level repair. The schematics he uses are available and you could perform the same repairs if you have an hot air pen.
You should try it sometime, component repair is not that hard even with average tools. I stuck a phantom powered aux jack in my laptop once, finding the faulty amp transistor and replacing it took about 20 minutes, and that was without schematics.
Is it limited to "repair shops" or to anyone who's happy to sign the NDA (such as an end-customer looking to repair their own machine after spilling a drink)?
If the former, what's the criteria that determines whether one is a "repair shop"? Would Honest Achmed's Used Laptops and Certificates[1] qualify if he wanted to repair his cousin Mustafa's laptop?
The knowledge-base there doesn't give any idea of what kind of criteria you are required to meet in order to receive the schematics. It just says "repair business". How many laptops need to come into the business before any information will be provided? Why are individuals not able to qualify (maybe they can? the page doesn't make it appear to be the case). Would there be any additional requirements for signing the confidentiality agreement such as having to sell products to customers or providing PII of customers? Both of those things are things that happen under other manufacturers repair programs.
> to repair shops under a confidentiality agreement
To be honest (and as a Framework laptop owner) that's a bit disappointing, the 'to repair shops' part and I assume some sort of bar to meet for that, I suppose I understand though. The link you post says pinouts are available, which following through to Github seems to mean just for connectors. I wonder if you could share the BoM and locations perhaps, so not a full schematic, but enough for someone to replace a faulty component like for like or with an equivalent part?
Seems to me that would protect what (I presume) you want to protect, while still giving owner-tinkerer-repairers basically everything they want?
They're a company truly trying to strike a balance between defending the IP they create and what's best for their community. There's no real winning move here that doesn't open them up to Chinese framework clones on Alibaba in a month
There's no real winning move here that doesn't open them up to Chinese framework clones on Alibaba in a month
Arguably if the Chinese wanted to, they could've already beaten Framework to the market. All the major OEMs/ODMs are in China (or Taiwan, but let's not get political here...) and I'm almost willing to bet Framework just contracted this work out to one of them. Also, those OEMs/ODMs are very much capable of taking the Intel reference design schematics and fitting them into the requested shape. That's basically how things like the Thinkpad X62 happened: https://news.ycombinator.com/item?id=15274644
Are BOM & part locations really the key missing pieces that are going to enable that/make it significantly more likely?
Some could already do it, and don't need those; the rest would still be missing schematics, layouts, mechanical drawings, etc. just like a user that wants to know what the unmarked/ambiguously marked chip is in order to try to replace it.
Likely a condition of the manufacturers allowing the release of the schematics in the first place. If Framework proves itself, it will have some more weight to throw around in this area. Maybe enough to make the schematics public.
Oh please, do you have access to a microscope, a hot air station and all of the required hardware to perform component-level repairs? Do you even know how to read a schematics? (I don't mean you in person but you as in the average consumer).
This is why we can't have nice things, y'all keep making unrealistic demands that are seriously disheartening.
I think such expectations are perfectly fair for a company that advertises that they "support your right to repair" on their front page. When you claim such support, you change the expectations people have of your product. As a consumer, you pay a significant fee for the repairability of the laptop compared to laptops from other brands. If all you get in return is coloured screws and recessed USB ports then I'd be pretty annoyed too.
This company claims they'll support your right to repair but then doesn't support _certain_ types of repair unless you meet their conditions. That's no different from Google, Apple, or any other tech giants that also will happily let you repair your device if you've got the right contacts and credentials. Even John Deer has repair manuals available.
Yes, I can read schematics and I have preformed multiple component-level repairs on two of my laptops in the past. Even if I hadn't, this wouldn't discount my argument. The fact that the "average consumer" hasn't wouldn't either.
Repairability and modularity are two distinct concepts. The framework laptop is modular but it is not repairable. At least not any more repairable then my Toshiba or MSI laptops. End of story.
May I ask you why you feel more confident with sharing data only to repair shops instead of publicly? I apologize if this question sounds too invasive, it's just that I can't imagine a scenario in which a malicious actor wouldn't be able to just pay for the data from shops anyway.
You're assuming it's their choice. It's much more likely that they don't own all the IP and can't get the relevant rightsholder(s) to agree to make things public. Notice that they say "we were able to share" and mention "work[ing] through constraints" when talking about sharing more detailed schematics.
I imagine they can't say this explicitly because the terms of their business relationships are themselves confidential and they don't want to say anything that could jeopardize those relationships.
It seems this is something that you really want repair shops to be informed of even if they have never heard of your brand. Perhaps putting text to the effect of "Full schematics are available to repair shops under a confidentiality agreement. Please contact foo@bar.com" on the first page that the QR codes resolve to would greatly improve communications with repairers.
Louis describes talking to the founder about their reasons, but it was in confidence so he doesn't really say much. https://youtu.be/G2YjKYG8P58?t=50 (just watch the whole thing it's only 3m)
> it really did show me that a lot needs to change throughout the entire industry ... I respect and understand why they have the concerns that they do, they are real concerns ...
If Louis was convinced that there were valid reasons not to publish the schematics then somehow I doubt it is as simple as Chinese copycat manufacturers, but who knows.
Of course it is a bad thing. Framework is not a nonprofit. They spent blood and tears developing the designs, and needs to at least recoup the cost spent, if not make a profit.
Simple: Copyright isn't always enough to protect your IP when you are a small company. They do want allow repair-ability, they don't want to make unauthorized clones too simple.
Bigger tech companies don't have to worry to much about this (given how they operate, legal teams they have, influence they have etc.). For small companies in the bootstrapping phase it's a problem.
Also there might be legal requirements, like some small parts of the layout being based on Intel provided schemas or similar. But that last point is pure speculative and irrelevant as the first point is good enough of an reason (while your company is in the bootstrapping phase).
Are you allowed to say if it is the board manufacturer or chip/component manufacturers that require the NDA? I'm mostly curious what level of vendor the restriction is coming from to get a better idea of what needs to change for Framework (or any other company) to be able to release the full schematics without NDA.
Unfortunately all industries are slowly boiling away the old standard of shipping schematics and diagrams of products we purchase. It seems layers of bureaucracy, contracts, and misaligned incentives have made it virtually impossible to continue that tradition even if desired. I'm happy with my Framework laptop, I'm glad that you were able to publish the schematics that are available publicly, and I'm glad that you will provide full board views to repair shops that ask for them. I hope you will be able to publish complete schematics for public consumption at some point in the future, even if it's late.
If you are allowed to comment on this: Is there an official expiry date when the publishing of the schematics will no longer be an issue? If yes, when?
I think that’s completely unfair and you’re letting the perfect be the enemy of the good.
Are they perfect in meeting their mission because of this clause? Maybe not.
But are they still by far the most open and most repairable mass produced laptop on the market? They are.
Their mission is extremely ambitious, and they’re trying to drag a massive market in the right direction. Maybe cut them a tiny bit of slack on the way?
While I absolutely agree with you in general, I was a bit taken aback to find this out this morning: their marketing had worked on me, and I had assumed all of this was open, too. So, I can understand why some people are responding badly to this as well.
What's the big deal? Just upload it somewhere. Don't worry, nobody is embarrassed that the majority of it is copy-pasted reference schematics from parts vendors - that's how it is done!
No kidding. If you've studied enough other laptop schematics you'll quickly realise this. Some might be more cost-optimised ("cost down" in jargon) than others, but they aren't all totally unique and almost always based on reference schematics from Intel or AMD.
In this case, we didn't see a request for it come in.
Publicly with no agreement required, we were able to share a sub-set of the schematic focused on the internal and external connectors: https://github.com/FrameworkComputer/Mainboard/blob/main/Ele...
Louis has more context on the latter in an earlier video: https://www.youtube.com/watch?v=8cJj8PUY0DU