Re:The People’s Code
by SmellTheGlove on Thursday August 11, 2016 @09:27AM
(#12268005)
Putting the code out there for other agencies to use is great, but getting them to actually use it will be another battle. Reuse is tantamount to taking away someone's budget, and therefore, status. The occurrence of two different groups implementing very similar things entirely separately happens more often than you'd think. And I'm not convinced they want to talk or work together, because bureaucrat/military officer X doesn't want to lose budget/people.
[ Parent
| on HN ]
Re:The People’s Code
by evonfriedland on Thursday August 11, 2016 @10:37AM
(#12268545)
Of possible interest, I used the GitHub API a few months back to see what was actually happening with the code government agencies were committing to GitHub (reuse, contribution patterns, licensing, etc). I ended up writing up some of my observations in a post [1] and 18F blog [2].
[1]: https://emanuelfeld.github.io/blog/2016/04/27/government-git...
[2]: https://18f.gsa.gov/2016/06/16/emanuel-feld-talks-about-his-...
Re:The People’s Code
by SmellTheGlove on Thursday August 11, 2016 @11:48AM
(#12269200)
Really good work, thank you for sharing. Probably worthy of a Show HN post. I wonder how this will track over time.
Even if every bureaucrat and official says, "my group is a snowflake and needs a bespoke system", opportunities will arise to change a project from completely out of scope to "possible if we leverage this open system". That's the hook that consistently pushed open source into business IT.