Government Team Experiments With Paying For Small Open Source Tasks (gsa.gov)
An anonymous reader writes: The U.S. General Services Administration has a team within it called 18F. They describe themselves as an open source, digital services delivery team. In other words, they create software for use by citizens and other government agencies, and the software they produce is open source. Starting next Monday, October 26, they're trying out an interesting new experiment for procuring open source code. Like any other agency, they have a budget, and they're allowed to contract out work when it makes sense to do so. But there's a difference between big projects and small ones.
If their purchase doesn't exceed $3,500, they have the authority to just do it. Higher than $3,500, and they (not to mention the contractors) have to deal with a bunch of extra red tape. This brings us to their experiment. They're developing a system that will let developers bid on small software projects the GSA needs. It starts at the cap for "micro-purchases," $3,499, and developers can bid it down if they feel it's easier. Once a bid is selected, the developer(s) have 10 working days to send back functioning code with a specific set of acceptance criteria. 18F isn't sure how well it'll work, but it's a cool way to try and make it easier for the open source community to build things for the government.
If their purchase doesn't exceed $3,500, they have the authority to just do it. Higher than $3,500, and they (not to mention the contractors) have to deal with a bunch of extra red tape. This brings us to their experiment. They're developing a system that will let developers bid on small software projects the GSA needs. It starts at the cap for "micro-purchases," $3,499, and developers can bid it down if they feel it's easier. Once a bid is selected, the developer(s) have 10 working days to send back functioning code with a specific set of acceptance criteria. 18F isn't sure how well it'll work, but it's a cool way to try and make it easier for the open source community to build things for the government.
A basic tenant of US government-created IP, that you can see throughout Wikipedia for example, is that any work created by the government is free of copyright. All that is really missing is the packaged dissemination of the work clear of any other required IP like licensed or proprietary libraries. It shouldn't take a freedom of information act request.
A United States government work is prepared by an officer or employee of the United States government as part of that person's official duties. It is not subject to copyright in the United States and there are no copyright restrictions on reproduction, derivative works, distribution, performance, or display of the work.
This is a good reason to have federal government software developed in-house instead of outsourced to the likes of Oracle, so that it can continue to benefit American people and other branches of governments instead of it being a recurring tax by corporations on the public sector.
Do one thing and do it well, a basic tenant of Unix design. Maybe the government is following Unix philosophy.
https://en.wikipedia.org/wiki/Unix_philosophy#Do_One_Thing_and_Do_It_Well
This could be a good thing.
Open source destroys good paying developer jobs.
It destroys some jobs, and creates other jobs. But by eliminating repetitive work, it raises overall productivity. Economic progress comes from the more efficient production of goods and services, not by "keeping people busy".
No, corporations aren't going to work on these things for 43,75 USD/hour.
As you can see by the screenshots they provide, the average winning rate is 171 USD/hour, which does add up with the data from BLS.gov, since you have to account for benefits and a lot of the overhead, plus, they're looking for senior people, after all.
http://www.bls.gov/oes/current...
Case in point: KDE, Gnome, Enlightenment, Unity, Cinnamon, Mate, Xfce, LXDE...
"It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap