Live data from Hacker News

US government commits to publish publicly financed software under FOSS licenses

k7r.eu

41–50 of 110 posts

Re: US government commits to publish publicly financed software under FOSS licenses

#41
post #30

Earlier quoted context omitted.

Yes, that's correct, being able to download the code, hash it, and then compare it to the hash displayed real-time would be a first step towards enabling this.

the software can easily be modified to display the hash you are expecting

To start, something is better than nothing. Long-term remote inbound two part authitacation combine with like measures for hardware via meta-programming would make bypassing this very, very hard for the average hacker.

Re: US government commits to publish publicly financed software under FOSS licenses

#42
post #31

Earlier quoted context omitted.

It pushes the incentives around as well, though. Unless there's some sort of marginal cost for each line of code they choose to keep proprietary, they'll inevitably do "the least work necessary" when they realize that some project is going to have components fitting these clauses, by by boxing up the entire effort under one of these clauses. Ideally, with some sort of force opposing propriety, the incentive would be…

LOC-based metric tied to money... What could go wrong?

An overabundance of semicolons per line? A complete abandonment of python?

Re: US government commits to publish publicly financed software under FOSS licenses

#43

It seems like they've cut a wide swath for (probably) exempting the most interesting of the software that could have been developed in the open. > Applicable exceptions are as follows: > The release of the item is restricted by another statute or regulation, such as the Export Administration Regulations, the International Traffic in Arms Regulation, or the laws and regulations governing classified information; > The…

Sure it's wide, but it also seems pretty reasonable to me

[deleted]

Re: US government commits to publish publicly financed software under FOSS licenses

#44

It seems like they've cut a wide swath for (probably) exempting the most interesting of the software that could have been developed in the open. > Applicable exceptions are as follows: > The release of the item is restricted by another statute or regulation, such as the Export Administration Regulations, the International Traffic in Arms Regulation, or the laws and regulations governing classified information; > The…

This doesn't include anything developed at DARPA, right?

Re: US government commits to publish publicly financed software under FOSS licenses

#45

It seems like they've cut a wide swath for (probably) exempting the most interesting of the software that could have been developed in the open. > Applicable exceptions are as follows: > The release of the item is restricted by another statute or regulation, such as the Export Administration Regulations, the International Traffic in Arms Regulation, or the laws and regulations governing classified information; > The…

Of course there are many exemptions. Did you expect them to release the F-22 source code or NSA PRISM architecture?

Re: US government commits to publish publicly financed software under FOSS licenses

#46
post #22

It seems like they've cut a wide swath for (probably) exempting the most interesting of the software that could have been developed in the open. > Applicable exceptions are as follows: > The release of the item is restricted by another statute or regulation, such as the Export Administration Regulations, the International Traffic in Arms Regulation, or the laws and regulations governing classified information; > The…

This probably excludes pretty much everything except probably the most boring things - public information websites, etc. Anything within the DoD, for instance, will at minimum be tagged "for official use only", which already exempts it from FOIA requests, so I don't see this really opening much up at all.

DoD work can, in at least some cases, be open-sourced. We had some work with DARPA where open-sourcing was actually mandated in our contract (at our request), and that code was, for a while at least, in active use in the field. Although I guess research is a little different.

Whether or not it's feasible is entirely dependent on the project, though. Something that's ITAR/EAR (or classified) is never going to be open-sourced.

Re: US government commits to publish publicly financed software under FOSS licenses

#48

I hope this includes voting software.

There is an effort happening in San Francisco right now to do just this. See here, for example, for a recent March 24, 2016 hearing on the topic:

https://sfgov.legistar.com/LegislationDetail.aspx?ID=2567089...

"Hearing on San Francisco's efforts to fund, design, and implement an open source voting system, including budget costs and projected roll-out schedule; and requesting the Department of Elections and the Elections Commission to report."

It's currently up for consideration in the budget.

SF resident Brian Behlendorf recently endorsed (along with EFF, Code for San Francisco, California Common Cause, local GitHub CEO Chris Wanstrath, etc), and we're looking for more high-profile supporters to help influence the Mayor's budget decision:

https://twitter.com/cjerdonek/status/716448812181512192

Re: US government commits to publish publicly financed software under FOSS licenses

#49

Why is this limited to software? Why not also publish publicly financed: * legal agreements * HR contracts * management presentations, best practices, and training material * marketing presentations and training material * creative output such as artwork and music so that the rest of the world can use them for free..

> creative output such as artwork and music

If I'm not mistaken, all intellectual property published by the US government is public domain by law. I may be wrong or you may be referring to something else.

Re: US government commits to publish publicly financed software under FOSS licenses

#50
post #44

It seems like they've cut a wide swath for (probably) exempting the most interesting of the software that could have been developed in the open. > Applicable exceptions are as follows: > The release of the item is restricted by another statute or regulation, such as the Export Administration Regulations, the International Traffic in Arms Regulation, or the laws and regulations governing classified information; > The…

This doesn't include anything developed at DARPA, right?

Lots of DARPA sponsored projects have open source releases.
Post reply on HN