4 ms·
They're trying to destroy FOSS ...by hiring FOSS developers? I don't buy it. More like, log4j was an actual real big issue for government agencies because the
by kube-system 4y ago
They're trying to destroy FOSS ...by hiring FOSS developers?
I don't buy it. More like, log4j was an actual real big issue for government agencies because they use rely on tons of open source projects and haven't previously done much to make sure that that supply chain is robust. This would help to change that.
Federal contractors don't need to sell proprietary software to make money -- they make more money selling FOSS software.
- throwbigdata 4y agoMore or less of a big issue than the revolving door of Microsoft bugs?
- kube-system 4y agoDifferent types of issues with different solutions. When you have a support contract with the original developer of a piece of code, you can demand the original developer fix the code.
- dllthomas 4y agoThat same solution still works for FOSS, you just actually need to pay for it. The situation for FOSS is even better because you also have the option of paying any other person to fix the code. Hopefully that's kinda what this bill does, though?
- kube-system 4y agoIt’s “the same” in a really broad hand-wavy sort of way. It’s not the same practically speaking. FOSS usually does not have warrantees, SLAs, or developers in particular locations with particular credentials. The government has processes that they must follow for paying contractors, so “just pay them” is not something that can easily be done last minute, (and sometimes, not at all without a literal act of Congress.) Also the financial and obligatory relationship between them and the developer is much different, and must be managed differently. Really, it is very important for people doing technology projects at the government to understand the difference between calling up the developer of Windows and calling up the developer of Git. Those are two very different relationships.
- dllthomas 4y agoYou seem to be reading me as implying any use of FOSS is equivalent to having a support contract; it's not. I was claiming that having a support contract for FOSS is equivalent to having a support contract for proprietary software. If you need "support contract" level support you should probably be paying for a support contract. At least with FOSS that can be competitive for the same piece of software (although that probably also means that some of the services on offer are quite a bit worse, having not had to organizationally have passed the hurdle of "actually making the software" at any point). Finding out that you have a problem when you don't have a support contract and then looking around for someone to work on the thing is not the same thing as having a support contract, although in some cases it can be a sufficient substitute and it's certainly cheaper in the best case (like any other form of skipping insurance). Depending on context, providing the "support contract" internally is also an option.
- kube-system 4y agoI said the issues are different and you disagreed, so I detailed what I meant. It’s also not reasonable to require the government to just get 10,000 support contracts just to implement a single application. What makes the most sense is what they’re doing here: 1. come up with a strategy for managing these risks 2. Collectively work with OSS developers instead of treating every one of the governments 10 bazillion projects like it needs a separate support contract for a component that is shared
- dllthomas 4y ago> I said the issues are different and you disagreed I disagreed that things are all that different "if you have a support contract." > It’s also not reasonable to require the government to just get 10,000 support contracts just to implement a single application. I agree, but I'm not sure that's relevant? If a single support contract is sufficient for proprietary software - making them responsible for addressing (incl. possibly working around) issues in any dependency - why is that not also viable for FOSS software? I don't disagree that what they're doing here seems likely to be a good idea, I just think you were initially selling "pay for support for the software you rely on as a big organization" a little short in its general applicability; indeed, this probably be viewed as providing that service internally.
- aaubry 4y agoIt's not so simple. The developers are not necessarily available for this kind of support. For example, I maintain an FOSS library, but I already have a full time job, and I'm not interested in working more hours. Unless someone hires me to work full time on this library, there is no chance that I provide paid support. I suspect that many other maintainers are in the same situation.
- dllthomas 4y agoThat's also potentially true of proprietary software, though. Not every company will offer a support contract, so if that's what you need you need to pick other software. I agree that probably a smaller fraction of FOSS projects offer first-party support contracts, but on the other hand third-party support contracts are a lot more reasonable in the FOSS context.
- wnevets 4y ago> Federal contractors don't need to sell proprietary software to make money -- they make more money selling FOSS software. tech companies in general are making billions using FOSS.
- kube-system 4y agoOf course, which is why I think viewing this as a push for proprietary software is not a fair assessment. Increasing your company's development costs is not a way to make more profit. The point of this is that you can't treat proprietary software dependencies the same way you treat FOSS. Community FOSS projects just don't have the same development process and governance model that proprietary software does. And so, the assessment of these projects is necessarily different.
- peteforde 4y agoRespectfully, you have a too-reasonable hunch of how decisions are made at the executive level, and because of that, you're reaching an incorrect conclusion. The primary factor driving the decision making process is not cost but risk. Many fail to remember the lengths to which companies like Microsoft, Oracle, Sun and others went to create FUD around the adoption of OSS in the public sector. It involved lobbyists, marketing campaigns and a whole certifications industry. When a CIO selects a technology, they aren't just weighing its merits and price tag; they are actively looking to leave a glowing legacy while actively doing everything they can to avoid being humiliated if the technology fails. See, the CIO knows that, as far as their board of directors is concerns, it's not the software that failed but the executive. That's why enterprise support packages exist; it's an insurance policy and a promise that if something goes terribly wrong at 2am, someone is going to pick up the phone when you call. Companies with expensive tools have an obvious interest in convincing their best customers that the competition in inherently risky.
- deleted 4y ago[deleted]
- Forgeties79 4y ago
- thayne 4y ago> haven't previously done much to make sure that that supply chain is robust I'm doubtful that anything short of requiring thorough security/pen testing on everything in the dependency tree would have prevented log4shell. And if that is the goal here, who is going to pay for that? Most open source projects don't have that kind of funding.
- dllthomas 4y ago> everything in the dependency tree With reasonable prioritization, we can probably do a lot to reduce the threat long before we get near everything. > who is going to pay for that? Well, this bill does seem to involve hiring FOSS devs, maybe that's partly what they'd do?
- drc500free 4y agoSeriously, the government would rather burn $50k on the manpower that makes the decision to not pay $10k in software licenses. The beltway contracting space is about selling a lot of butts in a lot of seats, and a bit of hardware that goes boom. FOSS is AMAZING for govt contractors, they can bill $250m building something using FOSS that's available as a commercial-off-the-shelf (COTS) product. They put a lot of work into ensuring the govt requirements are rigid enough that the COTS alternative is deemed unacceptable during the AoA process.