6 ms·

Most organizations with nuclear weapons most certainly do pay bounties. Generally for foreign intelligence, but I believe it applies. https://www.forbes.com/si

Most organizations with nuclear weapons most certainly do pay bounties. Generally for foreign intelligence, but I believe it applies. https://www.forbes.com/sites/adamandrzejewski/2021/11/18/fbi-and-other-agencies-paid-informants-548-million-in-recent-years-with-many-committing-authorized-crimes/ https://www.forbes.com/sites/adamandrzejewski/2021/11/18/fbi...

petertodd 5y ago
I think in this case that comment was just a funny way of saying both "this is actually for the well known USA nuclear weapons program, which everyone knows uses Crays" as well as "I couldn't get anyone to approve a bounty"
- boulos 5y ago
  As was the joking response about not discussing IEEE implementations due to their ops sec :).
  - gowld 5y ago
    Oh, I didn't understand what that was getting at, beyond the generael idea of trolling the misbehaving requester, but which I thought cored devs don't do in their own bug tracker. > Hi Bill, per our operational security procedure we can't talk about ieee_arithmetic, especially when we dont get paid.
- pydry 5y ago
  Still about 100x more alarming than funny.
hughrr 5y ago
I worked for a large defence contractor and getting approval for anyone to pay for that would have been more difficult than actually learning how to fix it myself and fixing it myself. At which point I would never be allowed to contribute the fix back to the original project due to the no code export policy and airgapped network. I could of course have done a clean room patch at home based on my retained knowledge but quite frankly I probably couldn’t be assed with it by the time I’d got home and eaten dinner due to the depression of working in such a horrible place. That’s the reality of working for such folk.
- dhosek 5y ago
  I'm so glad that I never did that work when it was a possibility.
- dathinab 5y ago
  I wonder if they couldn't "just" put up a misc. software support money pool with a reasonable but in the huge picture small amount of money they can "low complexity" spend on such things?
  - hughrr 5y ago
    Considering it took three tiers of management and three facilities department members to replace a coffee machine that had an actual service contract in place already, I think something of that administrative complexity would have been beyond them. Either that or like most SMEs I’ve worked for they’re actually only using the stuff because it’s “free” by their corrupted definition of “free” which is basically it didn’t have to go through a PO process.
    - deleted 5y ago
      [deleted]
- bluGill 5y ago
  I got around that one place by just writing up a bug report and a it seems like line x of file... this wasn't government and so they wouldn't have cared anyway so i just avoided figuring out the paperwork to contribute.
- lmeyerov 5y ago
  Sort of, in a depressing way: - It's pretty doable to get someone's hours for this, especially within the contractor or one of their DC buddies: there's already a customer and a contractor, and presumably, some sort of purchase vehicle & contract. The words "senior", "support", and "fee" are probably in there in multiple places. - By (backwards) design, it is much harder for a truly expert OSS dev not in the contractor circle, and even harder, an OSS product org offering maintenance contracts for events like this - The middle ground becomes sales/lobby-heavy orgs like IBM/RedHat, which introduces another multi-layer technical & political world of pain. I haven't worked with Cray (discussed in the thread), so no comment there. But as seen, we're seeing a chain of well-funded stakeholders being fine with not supporting for a prolonged period, which is cultural red flags.

petertodd 5y ago

I think in this case that comment was just a funny way of saying both "this is actually for the well known USA nuclear weapons program, which everyone knows uses Crays" as well as "I couldn't get anyone to approve a bounty"

boulos 5y ago
As was the joking response about not discussing IEEE implementations due to their ops sec :).
- gowld 5y ago
  Oh, I didn't understand what that was getting at, beyond the generael idea of trolling the misbehaving requester, but which I thought cored devs don't do in their own bug tracker. > Hi Bill, per our operational security procedure we can't talk about ieee_arithmetic, especially when we dont get paid.
pydry 5y ago
Still about 100x more alarming than funny.

hughrr 5y ago

I worked for a large defence contractor and getting approval for anyone to pay for that would have been more difficult than actually learning how to fix it myself and fixing it myself. At which point I would never be allowed to contribute the fix back to the original project due to the no code export policy and airgapped network. I could of course have done a clean room patch at home based on my retained knowledge but quite frankly I probably couldn’t be assed with it by the time I’d got home and eaten dinner due to the depression of working in such a horrible place. That’s the reality of working for such folk.

dhosek 5y ago
I'm so glad that I never did that work when it was a possibility.
dathinab 5y ago
I wonder if they couldn't "just" put up a misc. software support money pool with a reasonable but in the huge picture small amount of money they can "low complexity" spend on such things?
- hughrr 5y ago
  Considering it took three tiers of management and three facilities department members to replace a coffee machine that had an actual service contract in place already, I think something of that administrative complexity would have been beyond them. Either that or like most SMEs I’ve worked for they’re actually only using the stuff because it’s “free” by their corrupted definition of “free” which is basically it didn’t have to go through a PO process.
  - deleted 5y ago
    [deleted]
bluGill 5y ago
I got around that one place by just writing up a bug report and a it seems like line x of file... this wasn't government and so they wouldn't have cared anyway so i just avoided figuring out the paperwork to contribute.
lmeyerov 5y ago
Sort of, in a depressing way: - It's pretty doable to get someone's hours for this, especially within the contractor or one of their DC buddies: there's already a customer and a contractor, and presumably, some sort of purchase vehicle & contract. The words "senior", "support", and "fee" are probably in there in multiple places. - By (backwards) design, it is much harder for a truly expert OSS dev not in the contractor circle, and even harder, an OSS product org offering maintenance contracts for events like this - The middle ground becomes sales/lobby-heavy orgs like IBM/RedHat, which introduces another multi-layer technical & political world of pain. I haven't worked with Cray (discussed in the thread), so no comment there. But as seen, we're seeing a chain of well-funded stakeholders being fine with not supporting for a prolonged period, which is cultural red flags.