I can't even imagine what Richard Stallman thinks about this.
I would have loved to be a part of the conversation. While I'm sure there are at least 100s or 1,000 of open source projects that would be classified as critical, by any set of requirements, I'm really curious how the real silent killer, transitive dependencies, would be handled.
Modern development is all about grabbing someone else's package, that has grabbed these other folks packages... and as one would expect , there is a recursive nightmare of dependencies, 100s or more, per package.
I'm not one of the folks that believes government can't do anything right. However, I fear the open source community would be quite split over support an FOSS application that the government is openly connected with.
a public-private partnership to identify a list of critical open source projects
Which should create:
formal requirements or standards for maintaining the security of that critical code.
I want to see the governement barging in on any random project, dictating to the maintainers how they're going to run the thing .
Even governemental funding might have too many strings attached. Our governement is providing subsidies to small local charity's. Turns out they wanted a paper trail with detailled activities for each meeting, and signatures from a lot of people. Auditors ran amock, requiring even more paper. The volunteers complained about the morass of paperwork, so the gov helped them 'professionalise'. After a year of professionalizing, it turns out they lost so much volunteers that a lot of local chapters were giving up.
4 comments
[ 4.5 ms ] story [ 20.5 ms ] threadI would have loved to be a part of the conversation. While I'm sure there are at least 100s or 1,000 of open source projects that would be classified as critical, by any set of requirements, I'm really curious how the real silent killer, transitive dependencies, would be handled.
Modern development is all about grabbing someone else's package, that has grabbed these other folks packages... and as one would expect , there is a recursive nightmare of dependencies, 100s or more, per package.
I'm not one of the folks that believes government can't do anything right. However, I fear the open source community would be quite split over support an FOSS application that the government is openly connected with.
Even governemental funding might have too many strings attached. Our governement is providing subsidies to small local charity's. Turns out they wanted a paper trail with detailled activities for each meeting, and signatures from a lot of people. Auditors ran amock, requiring even more paper. The volunteers complained about the morass of paperwork, so the gov helped them 'professionalise'. After a year of professionalizing, it turns out they lost so much volunteers that a lot of local chapters were giving up.