Slashdot Mirror


Massachusetts Builds Open-Source Public Repository

An anonymous reader writes "Massachusetts on Wednesday took the wraps off a new software repository designed to let government agencies make more efficient use of open-source software. The repository will be managed by the Government Open Code Collaborative, a newly formed group of seven states and four municipalities that will contribute and download open-source software and proprietary software designed by government agencies for their use."

135 comments

  1. Massachusetts Information Technology Division by DeadSea · · Score: 4, Informative
    This makes me proud to live in Massachusetts. I can't find the repositor that the article is talking about, but it appears to come out of the Massachusetts Government Information Technology Division headed by Peter J. Quinn, CIO. He seems be putting quite a bit of support behind moving the Mass. Government to open source.

    The ITD website has some really kewl stuff on it like a legal toolkit for using Open Source software. Press releases on the sit seem to indicate that Republican Governer Mitt Romney is behind the move to open source. He'll be getting my vote when he runs for re-election.

    1. Re:Massachusetts Information Technology Division by jamshid42 · · Score: 3, Funny

      Glad to see that Massachusetts can produce something other than drunk senators...

      --
      /. - Proof that Sturgeon's Law is true...
    2. Re:Massachusetts Information Technology Division by Anonymous Coward · · Score: 1, Informative

      Same here, I'd love to see open code being used more here.

      I'd love to see something open source being used at my school, but I think it's too late for that. Everyone's locked into Windows 2000, and every classroom has a SmartBoard, which I don't believe has Linux drivers.

      The only Linux powered computer is the content filtering system, which everyone has grown to hate since it blocks game sites. :-)

      Oh well, in the Government is a start, hopefully, this will succeed and continue on to desktops in public schools.

    3. Re:Massachusetts Information Technology Division by Nakito · · Score: 4, Interesting

      I wonder to what extent this is a byproduct of the number of major universities in the Boston area (MIT, Harvard, Boston University, Boston College, Northeastern, Tufts, Brandeis, UMass, etc.). Or to look at it the other way around, I wonder if this would be less likely to occur in a state in which the population is not saturated with tech-savvy college graduates. To make this happen, would you need a critical mass of people in the state population who give a damn -- a "seed" population? If so, how many other places have the right conditions? On the other hand, could it be done by just a small core of motivated people in the right government agency?

    4. Re:Massachusetts Information Technology Division by jamshid42 · · Score: 2, Informative

      NC State seems to have it working.

      Here are the installation directions for the driver.

      --
      /. - Proof that Sturgeon's Law is true...
    5. Re:Massachusetts Information Technology Division by edbarrett · · Score: 1

      From the "Brief Intro" link on that page:

      The Information Technology Division gratefully acknowledges the assistance of Alba Bozo, HLS '04

      Only Bozos know anything about OS licenses... :)

    6. Re:Massachusetts Information Technology Division by Orgazmus · · Score: 2, Funny

      I`ll *hick* second that!

      --
      The system had the verbosity of HTML combined with all the readability of compiled assembly viewed as bitmap images
    7. Re:Massachusetts Information Technology Division by S.O.B. · · Score: 1

      We could even start a geek relocation program for areas that don't have enough geek influence in their area. Slowly infiltrating at the municipal level until we control all the key economic and industrial centers. Then quietly moving up the levels of government until we control the world! Mwa ha ha ha!

      Geeks of the world unite!!!! Throw off the pocket protectors of your oppressors and rise up!.

      ...Sorry. I got a bit carried away.

      --
      Some of what I say is fact, some is conjecture, the rest I'm just blowing out my ass...you guess.
    8. Re:Massachusetts Information Technology Division by Trigun · · Score: 2, Funny

      *hic* is Massachusetts, *hick* is Arkansas. And if you were wondering, *Phhhbbbt* is DC.

    9. Re:Massachusetts Information Technology Division by Atzanteol · · Score: 1

      I'll er, have you know, ah, that our ah drunk senators are better than anybody elses drunk senators.

      I didn't come in here wearing any pants, and I'm, er, not leaving with any pants...

      --
      "Ignorance more frequently begets confidence than does knowledge"

      - Charles Darwin
    10. Re:Massachusetts Information Technology Division by linicks · · Score: 2, Funny

      This is wicked awesome news :-)

      --

      I got nothing...
    11. Re:Massachusetts Information Technology Division by Anonymous Coward · · Score: 0

      Glad to see that you will be voting for the asshole who tried to get the state medical schools, as well as the Art schools, and Maritime academy axed from the state budget.

    12. Re:Massachusetts Information Technology Division by John+F-ing+Kerry · · Score: 1

      I am not a drunk! I am ornery, a lecher (I love marrying rich btw), anti-war (except when a Democrat fights them), two-faced lying, and all around boring. But I am not a drunk! You must be thinking of my good friend Ted Kennedy.

      --
      By the way, did I mention I served in Vietnam.
    13. Re:Massachusetts Information Technology Division by kinzillah · · Score: 1

      That might be intended as a joke, but nix the conquering the world part and I think its a good idea.
      Or at least something like a Geek PAC.

      --
      Douglas P. Price
    14. Re:Massachusetts Information Technology Division by pendergast · · Score: 1

      I set up this server and will be finalizing the install at URI next week. If anyone is interested in the setup doc, I will post it on the site or you can email me at tpendergast at sec dot state dot ri dot us.

    15. Re:Massachusetts Information Technology Division by f0rtytw0 · · Score: 1

      correction
      I er ah will have you know that ah our drunk senatahs are er bettah then anybody elses drunk senatahs

      --
      this is the most important sig ever! In your face 446154!
    16. Re:Massachusetts Information Technology Division by Fear+the+Clam · · Score: 1

      Knobshiner Bock is from Texas.

    17. Re:Massachusetts Information Technology Division by S.O.B. · · Score: 1

      It was intended as a joke. I don't think relocating tech-savvy people to influence local politics is either practical or desirable. I think a better approach is to educate the general public so that they better understand the issues and what's at stake.

      The SCO case is a perfect example. I've mentioned the SCO case to a few friends who aren't in the "industry" and they didn't know who SCO was, that they were suing IBM for $5B and they only had a vague idea of what Linux was. With that level of knowledge there is no hope that they could understand what's at stake if SCO were to prove any part of their case.

      Of course I did my part and educated them so now whenever I talk to them they ask how the case is going.

      FYI, one of my friends was even an IBM employee.

      --
      Some of what I say is fact, some is conjecture, the rest I'm just blowing out my ass...you guess.
    18. Re:Massachusetts Information Technology Division by sglines · · Score: 1

      Yah this is great news for everyone unless you read the fine print. The hardware colo has been outsourced to The University of Rhode Island and all system administrator has been outsourced to India.

    19. Re:Massachusetts Information Technology Division by SoopahMan · · Score: 1

      It's worth noting that, although Romney's push for Open Source is admirable, there are places it's been taken much too far - particularly, there are existing, perfectly-working systems that he and the CIO are tearing up in the name of Open Source. Big waste of cash.

      As an MA resident, don't get me wrong - I like Romney (a Republican) even though I'm a Democrat. He's done a good job in most ways. But I think most Slashdot readers, Open Source junkies or no, would cry murder if they saw the quality code being thrown out by Romney on for example, Mass.gov
  2. Is that the same initiative as... by tcopeland · · Score: 4, Interesting

    ...this? It sounds like the same thing.

    Sounds like a perfect opportunity for another GForge installation... one more for the list!

    1. Re:Is that the same initiative as... by zerOnIne · · Score: 1

      i actually brought this up with them this past week at the conference for OpenSource in Government, where they initially announced the GOCC thing. the developer's been talking with tim, it seems, and they're trying to figure out of GF is really a good fit for them, especially with the security restrictions they want to have in there. maybe this will be a good push for that old RBAC patch i submitted to get dusted off and fixed? :)

      --
      09
    2. Re:Is that the same initiative as... by tcopeland · · Score: 1

      > they're trying to figure out of
      > GF is really a good fit for them

      Cool. Maybe I'll email them with some current government usages of GForge... can't hurt.

      > that old RBAC patch i submitted

      Actually, Tim and Guillame were chatting about that on IRC just yesterday, I think...

  3. Open Source and Goverment? by stecoop · · Score: 0

    Do you really want the government involved in Open Source? It seems there are plenty of standards (GPL etc). I prefer separation of Source and State.

    1. Re:Open Source and Goverment? by filekutter · · Score: 1

      That is something to ponder, along with what restrictions and/or panels and boards will they implement to oversee development paths.

      --
      I call computer-illiteracy job security
    2. Re:Open Source and Goverment? by Amiga+Lover · · Score: 0, Troll

      Same here. I'd like to know what checks & balances there are in place to ensure there are no government 'back doors' into software.

      Is this the first step towards a governmental attempt to control F/OSS software? Will we soon only be able to get our software from government approved repositories?

      I don't like the smell of it

    3. Re:Open Source and Goverment? by biglig2 · · Score: 1, Redundant

      The check and balance that there are no back doors in F/OSS software is that you can read the source and look for them.

      --
      ~~~~~ BigLig2? You mean there's another one of me?
    4. Re:Open Source and Goverment? by ThogScully · · Score: 5, Insightful

      It sounds like you're joking, but just in case...

      If you're worried about the government infecting open source projects with hidden code or something, then don't. It's open - that's the point. At the very worst, it would be on par with the proprietary software in use now. Hidden code would be seen.

      Are you concerned that the government will screw up open source with bad management? So don't use software that is run by bad managers - simple solution. It's not like you don't have choices. If someone doesn't like the direction a government entity is taking a project, it will fork - not unlike the way things are now.

      I just hope you don't get modded insightful as this sounds like one of those comments that gets insightful when it's anything but.
      -N

      --
      I've nothing to say here...
    5. Re:Open Source and Goverment? by pfleming · · Score: 1

      As I read it this is mostly for *other* agencies. The ability of a government agency to reuse code developed by another agency, to share development costs, finished code, etc. has to be the main goal of this project. They aren't trying to rewrite the rules of FOSS, they are coming up with a license that allows them to share code between agencies while preventing commercial exploitation of that code. This is a great move on the part of the participating agencies but I doubt any regular FOSS coder will be using any of this software.

  4. Nice Zealotry by USAPatriot · · Score: 1, Interesting
    from the seeing-the-light dept.

    More proof that open-source is a religion here. No evidence of whether this repository will be any good or contain anything of value, just that's its OSS, hip hip hooray.

    I've seen the light on sourceforge, and it ain't pretty.

    --

    Slashdot Moderation: From positive to terrible in 2 "insightful" posts.

    1. Re:Nice Zealotry by J.+Jacques · · Score: 2, Interesting

      As I understand it, the point is to make OSS more easily available to government agencies which should in theory save the state a sizeable chunk of money that might otherwise be spent on other software. The thinking is that OSS = cheaper = a good thing.

      --
      http://www.questionablecontent.net
    2. Re:Nice Zealotry by irving47 · · Score: 1

      from the seeing-the-light dept.
      Either that, or he watched Stargate SG-1 last week and wants a Repository of the Ancients downloaded into his brain. (And who can blame him?!)
      It uses lots of flashy, colored, pretty light.

      --
      I had a sucky sig.
    3. Re:Nice Zealotry by Anonymous Coward · · Score: 0

      > More proof that open-source is a religion here.

      No, just proof that one perception of this story is that governmental organizations aren't afraid of using `free` software if its more efficient.

      > Proud To Be An American.

      Proud to be anti-American imperialism.
      http://cryptome.org/mil-dead-iqw.htm

    4. Re:Nice Zealotry by Anonymous Coward · · Score: 1, Insightful

      I'm not an open source advocate, but I don't see how this could be a *bad* thing.

      I mean...it could be mostly worthless, but the idea, at least, is sound.

      At the very least, if another department needs software, they already have a catalog of what other departments are using.

      As for SourceForge...true, lots of unfinished and probably worthless stuff there. But I've gone there plenty of times and gotten exactly what I needed.

    5. Re:Nice Zealotry by roomisigloomis · · Score: 3, Insightful

      That's a rather inane comment. People here are really just interested in one thing, when you get right down to it: being able to make software work the way they want it to behave. It seems that Massachusetts' CIO is also interested in seeing this happen. What is wrong or zealous about being happy to see a state government doing its part to use open source software and possibly lower costs and improve productivity in the process? If you don't like it, don't participate. There's no reason to troll or rain on everyone's parade.

      --
      "We are accountable for not only what we do, but also that which we don't do." -- Moliere
    6. Re:Nice Zealotry by stratjakt · · Score: 1

      And how much taxpayer money will get pissed away maintaining this OSS repository?

      --
      I don't need no instructions to know how to rock!!!!
    7. Re:Nice Zealotry by goldspider · · Score: 2, Insightful
      "The thinking is that OSS = cheaper = a good thing."

      Before you call it a "good thing" did you ever stop and consider whether that statement is accurate?

      Just because it's open source, it doesn't automatically make it more useful, or imply sufficient support, or even meet the specific needs of the government.

      Hell, using OSS doesn't even mean that it is in fact cheaper! I work at a government institution and we have worked with free software. Sure, the software itself didn't cost us anything, but getting support for the piece of crap cost us (literally) millions.

      The grandparent poster is RIGHT ON! Only blind zealotry can explain the knee-jerk "OSS IS ALWAYS GOOD!" reaction to these stories.

      --
      "Ask not what your country can do for you." --John F. Kennedy
    8. Re:Nice Zealotry by homebrewmike · · Score: 5, Insightful

      Well, as I see it, the government is directly involved with developing software. Well, since we are the government WE are paying for the development of software, and yet WE don't get access ot that source

      Here's an example. The state of MN just wrote some software to help track the amount of salt that it uses during the winter time, allowing them to better track and order salt in a timely manner.

      Who paid for that? Well, me, and a bunch of other Minnesotans. Well, don't cha think that Wisconsin, our happy go-lucky-badger-fearing state would LOVE to have the code? Sure WI could buy that package from MN, but I'll bet that Wisconsin will just go ahead, and reinvent that wheel. Government works like a business (but with a bit more transparancy) and most businesses are heavily involed with the NOT INVENTED HERE SYNDROME.

      So WI and MN tax payers are paying twice what they need to. So, why not share the code? Chances are that WI will have projects that MN would want. Is it going to cut jobs? Probably not - it's just going to make things more efficent. Developers will still need to adapt the packages to the current environment.

      We're paying to have this software developed - we might as well get a copy of it!

    9. Re:Nice Zealotry by J.+Jacques · · Score: 2, Interesting

      Did you notice that I qualified my statements with "in theory" and "the thinking is"? Of course OSS is not going to be cheaper in EVERY SINGLE SITUATION. In this case, however, a number of people who have clearly done quite a bit of research into it have decided that OSS could be cheaper in this particular situation. They think it worthwhile to establish a means of distributing it more easily among government agencies.

      --
      http://www.questionablecontent.net
    10. Re:Nice Zealotry by Anonymous Coward · · Score: 0

      I would love to see a financial breakdown of exactly how support cost you 'millions'. Imho, I think perhaps you just made that up off the top of your head .

      There is a wonderful invention called the internet, a veritable marvel of modern technology whereby you can get information for free from all over the world.
      Try it, its all the rage don't you know.

    11. Re:Nice Zealotry by An+Onerous+Coward · · Score: 1

      The hardware/software setup doesn't sound very complicated. Administration will be the biggie, as always. But in the bigger picture, how much it costs to maintain isn't relevant; the hope is that the dollar figure will be dwarfed by the savings that come from better software, reduced licensing fees, reduced development costs, and more efficient government services.

      The trouble is, it's easy to quantify the costs of running the repository, and much harder to quantify the savings that it produces.

      --

      You want the truthiness? You can't handle the truthiness!

    12. Re:Nice Zealotry by Anonymous Coward · · Score: 0

      About the same amount of money you piss away of your employers composing innane comments to slashdot.

      And oh yeah, btw. FAG!

    13. Re:Nice Zealotry by Anonymous Coward · · Score: 0

      I'm sure it'll take off at least 5 minutes from the Iraq operations budget. Won't somebody please think of the soldiers!!

    14. Re:Nice Zealotry by ClosedSource · · Score: 1

      "Well, since we are the government WE are paying for the development of software, and yet WE don't get access ot that source"

      There are many goods and services that the government buys without receiving any IP, what's so special about software? To be consistent, shouldn't we demand the design specs to the office equipment, vehicles, recipes, etc that the government buys. Perhaps we should also be able to obtain personal information about anyone that works for the government, since we are paying their salary. Where does it all end?

    15. Re:Nice Zealotry by Anonymous Coward · · Score: 0

      Why do you need access to the source to use the program?

    16. Re:Nice Zealotry by Dr.+Smeegee · · Score: 1

      Just curious: What were the pieces of free software that y'all had so much trouble with? It'd be nice to know, and perhaps the maintainers could be made aware of the difficulties and fix it in future releases. Granted, it won't help you now, but surely you'd like to help the next bunch who look at it...

    17. Re:Nice Zealotry by Short+Circuit · · Score: 1

      It's easy to quantify the savings. You include or exclude uncertainties depending on who's paying you for the study.

    18. Re:Nice Zealotry by spectecjr · · Score: 1

      We're paying to have this software developed - we might as well get a copy of it! ... which is why it should be released under the Public Domain, and not under any Open Source license.

      That, after all, is one of the legal requirements that the government is held to - and for good reason.

      --
      Coming soon - pyrogyra
    19. Re:Nice Zealotry by DukeyToo · · Score: 1

      One reason that existing software developed by the government will not be made open-source, is security. While a program to calculate salt usage is probably not a security risk, what about the software used to run a government web site, or to manage social security benefits?

      Programmers are lazy, and (IMO) security-by-obscurity is the most common type in use today in closed-source apps. If the code becomes open, then the security is invalidated, and sensitive data becomes at risk of being exposed. It costs money to ensure that security is incorporated correctly into applications, and government has not historically been willing to spend money in that area.

      I agree with you, government software should be open - I just don't think it'll happen, and if it does then it will be a disaster from a security standpoint.

      --
      Most writers regard truth as their most valuable possession, and therefore are most economical in its use - Mark Twain
    20. Re:Nice Zealotry by Bull999999 · · Score: 1

      If you RTFA, you would've noticed that:

      " The repository will consist of a MySQL database, Z Object Publishing Environment application server, Apache Web server, OpenLDAP authentication service for storing membership data, and Debian Linux"

      At least the software they are using for the repository aren't considered pieces of crap. As for the support, any decent sys admin shouldn't have trouble learning new O/S and software. If the sys admin sucks, then there plenty good out of work sys admins out there.

      --
      1f u c4n r34d th1s u r34lly n33d t0 g37 l41d
    21. Re:Nice Zealotry by Bull999999 · · Score: 1

      More like not RTFA is a religion here.

      " "We want to create a central place where the public sector can go and see what other projects are being developed,"

      This project looks more like the government opening up their projects for the public viewing, not the anti-MS, must use open-source project.

      --
      1f u c4n r34d th1s u r34lly n33d t0 g37 l41d
    22. Re:Nice Zealotry by Wybaar · · Score: 1

      True, a piece of software being open source does not necessarily imply that it's the best tool for the job. However, I imagine that if a piece of software doesn't meet some government agency's needs, they'll modify it so it does or ask someone else to modify it. Then they can put it back in the repository for the next government agency to use. If the states involved in this effort play their cards right, and try to make sure that the code they produce is reusable and generally good quality, the development and support costs can be amortized over each state and a decent amount of time. Will the price to get one piece of software in the repository working in one specific situation for a short period of time be less than the price of purchasing a non-open source alternate? Not necessarily. Will the price to get a piece of software that is generally application to many situations (with minor adjustment) and will be used for a decent period of time be less than the cost of licensing that non-open source alternate for each situation for that length of time? Perhaps. Time will tell, but if nothing else this is a good opportunity for open source to show what it's made of.

      --
      Y|
    23. Re:Nice Zealotry by Darby · · Score: 1

      Just curious: What were the pieces of free software that y'all had so much trouble with?

      I've had a lot of trouble finding a FTP over SSL Linux client that uses client certificates.

      Any suggestions?

    24. Re:Nice Zealotry by Minna+Kirai · · Score: 1

      Programmers are lazy, and (IMO) security-by-obscurity is the most common type in use today in closed-source apps.

      No. Wrong. Backwards. Bizarro. That's all lies.

      Nobody uses security-through-obscurity in software. Especially in government military/espionage matters! The NSA simply isn't moronic enough to let that happen.

    25. Re:Nice Zealotry by midol · · Score: 1
      I don't know the current state of affairs in the US, I live in Canada.

      Years ago I found that it was the policy of the US government that if software was developed with public funding it had to be made available to the public. Agencies were able to charge a nominal fee to cover the cost of distribution, mag tapes at that time.

      I requested a listing of available software and was told that as a non-resident my access was restricted. Moreover the policy was under review and I would be kept informed if access was opened up.

      Well, imagine my surprise when, after an interval of six months, I got a great whacking 132 column high speed line printer listing of some tens of thousands of software titles I could have!

      Among the offerings was a complete telemetry and launch control system for large satellite vehicles and a custom real time operating system for an IBM mainframe. At the time this was mind-boggling stuff. I did not actually have occasion to use any launch control software, but it was a giddy idea. Does anyone know the current state of affairs in this regard?

  5. Other states by hey · · Score: 3, Insightful

    I wonder if other states could use it.
    If so it would make it easier for them to
    move to open source.

    1. Re:Other states by mrscott · · Score: 3, Informative

      If you contact one of the members of the GOCC, they can likely get any government entity into the project that is willing to work with open source. It's actually a really cool initiative and will hopefully drive consistent open source applications in government.

  6. We have to tailor your arguments for your audience by Saeed+al-Sahaf · · Score: 4, Insightful

    The is great. I suppose this might be a little "off topic" but I think it is due in no small part to the growing public awareness that has come about because of the SCO case. We are starting to see a much more critical eye from the press and public officials to FUD put out by anti-OOS pundits. This is in no small part to the fact that more than ever, the OSS position is more organized and sounds a lot less like a bunch of hippies frothing at the mouth against "big business". We (many of us) have known for a long time the benefits to society and by way of those that work in the Public Sector, bodies that are here to benefit society, the ideas behind OSS, but in the past these ideas have not been articulated in a way that is understandable to the non-geek, non-IT centered thought patterns. A good PowerPoint wouldn't hurt (joke). You have to tailor your arguments for your audience.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  7. Conflicts with open values? by Anonymous Coward · · Score: 3, Interesting

    "Government agencies looking to use the repository must sign a contract with the collaborative. This grants an agency a license to any open-source and proprietary software it finds in the repository and prohibits that software from being used to make a profit."

    Im not suggesting this idea is a _bad_thing_, it looks like a worthy endeavour, but doesn't this restriction go against the underlying GPL. ??

    1. Re:Conflicts with open values? by stratjakt · · Score: 2, Insightful

      Ohmigoodness they aren't practicing the gospel according to RMS!

      This isn't linux or the HURD. This is stuff developed with taxpayer dollars. All the bits and bobs written for various agencies stuck in one pile. Under MA law, taxpayer dollars can not be used for corporate R&D.

      This isn't incompatible with the GPL, the GPL is incompatible with this. Doesn't stop them from using linux, but it does prevent them from contributing to it.

      --
      I don't need no instructions to know how to rock!!!!
    2. Re:Conflicts with open values? by Anonymous Coward · · Score: 0

      "This isn't incompatible with the GPL, the GPL is incompatible with this." :)

      I didn't realise compatability was a non commutative function. So perhaps it's not that my actions are incompatible with the Law, but that the Law is incompatibe with my actions. I will remember that defence the next time I'm up before the bar. Not.

    3. Re:Conflicts with open values? by 110010001000 · · Score: 1

      What underlying GPL? Not all the software in the repository is GPLd. There is proprietary software and non-GPL software in there as well.

    4. Re:Conflicts with open values? by slavefishy · · Score: 1

      My thoughts precisely. Surely that violates section 4 of the GPL, and I quote: "You may not... sublicense... except as expressly provided under this License", which would therefore invoke section 5, preventing them distributing it.

      Are they getting permission from the authors to sublicense the software under their own scheme? That's the only way I can see them getting around it.

    5. Re:Conflicts with open values? by Ugmo · · Score: 2, Informative

      IANAL

      Elsewhere in the article it explains that whenever states wanted to reuse each others software they needed to meet with lawyers and come up with a contract. This "collaborative" is like an ongoing contract/project. Instead of meeting after meeting you sign one contract and all future software in the collaborative comes under those terms.

      That being understood, the collaborative is not public. It is a private agreement among state governments. The software used by the collaborative is not public. You must sign a contract to see and use the software. The collaborative is not distributing the software. It is like a coporation that uses GPL software and modifies it for internal use. They are not distributing it to the public and they are not selling it so they do not have to make their changes public or provide source. They are complying with the GPL.

      I think it would be better for them and for the Open Source community if they just worked via Source Forge or Savannah, thereby getting the benefits of more developers and at the same time contributing back software to the community. It seems for legal reasons that they cannot.

      Possibly there can be a compromise. Right now there is a one way valve. The collaborative can take in Open Source code and make changes, but does not give back. Maybe they can not be completely open with their code continuously but they can, on a regular basis, provide patches back to the projects they use as part of their projects. If done often enough it would be little different from have a completely open project.

      The only problem would be if someone in government invents a completely new project from scratch. In that case, maybe they could convince a contractor to create a external Open Source version under the GPL and donate the code to that to be run as a seperate project in paralell to the original. (Think Apache vs NCSA)

  8. Not open source by Anonymous Coward · · Score: 5, Insightful

    Government agencies looking to use the repository must sign a contract with the collaborative. This grants an agency a license to any open-source and proprietary software it finds in the repository and prohibits that software from being used to make a profit. This is a crucial component, since Massachusetts law prohibits commercial entities from making money off products developed by the commonwealth using taxpayer money.

    The key words in the above are "prohibits that software from being used to make a profit". This means that any software they develop will either have to be done from scratch or from a very permissive license such as BSD, which allows the modification of the license of the code.

    Furthermore, this license does not fall under The Open Source Definition or The Free Software Definition for this same reason.

  9. If only they'd named it by Anonymous Coward · · Score: 0

    Government Resources Open Code Collaborative, we'd have known their hearts were really in it.

  10. Incentive issues by agslashdot · · Score: 3, Interesting
    Government managing something, anything, almost always results in inefficiency and bereaucracy. I'd hate the state government managing OSS or anything else. Let them build roads & such...

    Would there have been a Linux if the Government of Finland stepped in, instead of Linus & his bunch of highly caffeinated sharpshooters ?

    I don't have a problem with government embracing OSS that is privately built using legions of programmers, because the programmers then have the incentive - fame ( in the OSS community), fortune ( ok, takes much longer to go IPO these days), hopefully both. But government managing OSS, where's the incentive ?

    1. Re:Incentive issues by autocracy · · Score: 1

      Come on... they'll have to internally manage anything that they use to some extent. What agency that writes their own code doesn't have some way to manage it? Why does making it sharable with other agencies make it different?

      --
      SIG: HUP
    2. Re:Incentive issues by jks · · Score: 3, Informative
      Would there have been a Linux if the Government of Finland stepped in

      In fact, the Government of Finland, via the University of Helsinki, funded the beginnings of Linux by keeping Linus employed and not bothering him. Of course, nowadays the university is, shall we say, much more proactive about IPR issues, so it won't probably happen again.

  11. You mean like this? by Anonymous Coward · · Score: 2, Informative
  12. Dont worry it is going to happen by codepunk · · Score: 1

    As your school budget get's cut more and more and the money dries up to even afford school rate licenses you will become linux users.

    --


    Got Code?
    1. Re:Dont worry it is going to happen by smittyoneeach · · Score: 1

      I dunno. That recent story about MS passing out software at no cost to the DOD may have been the tiniest shot across the bow.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    2. Re:Dont worry it is going to happen by Anonymous Coward · · Score: 0

      when they realize how much its going to cost to retrain teachers and everyone else how to use linux instead of windows, i think they will get the fuck over paying for software you fuckign linux zealot tools!

    3. Re:Dont worry it is going to happen by TWX · · Score: 1

      Yeah, but what are the odds that proper accounting of the license materials will occur? Remember, you have to keep the booklet with the weird printed certificate thing, or else have the sticker on the side of the case in order to remain in compliance.

      Saying that you received it in the mail means nothing. Technically, receiving it in the mail means nothing, because you could have sold it or given it away, which would mean that you don't have the license anymore anyway.

      The beauty of software released under the GPL is that end users really cannot pirate it, no matter how hard they try.

      --
      Do not look into laser with remaining eye.
  13. fermi does this too.. by Xzzy · · Score: 4, Informative

    Granted much of the software isn't as user-oriented, but that's not the point. The point is it is another government institution that has put real effort into making free software available to the public.

    http://fermitools.fnal.gov/

    This is just one example I personally know of. Is this common at all? I'm too lazy to sift through every *.gov domain hunting for a software page. ;)

    1. Re:fermi does this too.. by tcopeland · · Score: 1

      There's the COUGAAR agent framework and its supporting projects - it's funded by the feds.

      There's also this NOAA project site.

    2. Re:fermi does this too.. by Anonymous Coward · · Score: 0

      "TRANSPORT is a computer program used to design charged particle beam transport systems."

      Cool. No need to write the code needed to build my death ray. The government already did it for me.

    3. Re:fermi does this too.. by Anonymous Coward · · Score: 0

      shut the hell up, page widener.

  14. Exactly my point by agslashdot · · Score: 4, Interesting
    Look at the hurdles I'd face if I want to sign up -

    Must sign a contract

    Must use only stuff already in the repository

    Can't ever make money - prohibited by diktat - so what's my incentive ?

    Furthermore, how do you enforce these things ? If the repository is public, I could very easily take bits & pieces & repackage it as proprietary software & sell it, thus making money off products developed by the commonwealth using taxpayer money. If the repository is not public, then how is it open source ?

    Seems overly complicated. Why doesn't the government of MA simply provide monetary incentives for programmers to contribute to existing repositories like sourceforge ? You could get things moving so much faster that way...or am I missing something here ?

    1. Re:Exactly my point by Anonymous Coward · · Score: 0

      My guess is that the governments can individually then redistribute the software to their constituents under an open source license. So it isn't that bad. But the fact remains that this relicensing of the software, if it was originally under most open or free licenses, would be illegal.

      I agree that enforcement would also be a problem. Especially, if the above is true, then the government would be able to pick up its own software again under the open source license and avoid the non-profit restriction.

    2. Re:Exactly my point by circusnews · · Score: 1

      The point you are missing is that Mass laws in question are not going to change any time soon. Right or wrong (and I think its very wrong...), its the reality that we must live with, at least for now.

      The people doing this are not in a position to change the law to allow comenwealth employees to contribute to GPL (and many other F/OSS licenced) projects, but they want the benifits of it, and they want to have a nice way of documenting the need to change this in the future.

      While I have not seen this system in action, I suspect that for now, projects that are used by various govenments can be downloaded from the project. Citations of who else is using it, discussions about it (etc.) are going to be avalible in one place. For software that is released under a lic. that they approve, contributions can be made to the project directly through this site.

      In the future, they could point to things like OOo and say "We have these 50 patches that we can't contribute back to the community at large due to this law, but these would make the world work better", and use that to push for change in the law. It can be a long, and slow process, but its a process that seems to be underway.

  15. Re:We have to tailor your arguments for your audie by Anonymous Coward · · Score: 0

    Not to be cynical, but I really don't think there is much public awareness due to SCO. Even my geek friends haven't heard of SCO, although they're not hardcore computer geeks.

  16. Mostly good by Mjlner · · Score: 5, Interesting
    Any government that invests money in any sort of software development should make sure that the money goes back to tax payers. Just as with anything else, the government (in theory, at least) invests money in stuff that is for the peoples benefit. Eg. defence fundings are spent in order to defend the people.

    Free / Open source software is an effective way of making sure that the people benefits from the development. It's the ultimate public service. A penny spent on FOSS is a penny earned in future projects and software for the masses, while a penny spent on proprietary software is merely a penny spent.

    --
    Lemon curry???
  17. Here in MA by superpulpsicle · · Score: 3, Funny

    Ok if there is one thing about the state of MA. Every project with the word "government" begins with a budget and end with an infinite budget.

    Just look at Big Dig, that thing is never going to finish. It's a political blackhole for sucking up $$$.

    1. Re:Here in MA by IO+ERROR · · Score: 1
      Just look at Big Dig, that thing is never going to finish. It's a political blackhole for sucking up $$$.

      Er, the Big Dig is very nearly complete and open to traffic now.

      --
      How am I supposed to fit a pithy, relevant quote into 120 characters?
  18. Re:Speaking of public repositories... by Joseph+Vigneau · · Score: 1

    Anyone else feel a little nervous that the usenet archives are in the hands of a private company, which could potentially fold or go under -instead of being made freely available in a federally funded repository?

    Anyone has had the opportunity to archive USENET. But, only one company saw the value in this and invested in it, and Google bought them. They simply harvested all of those messages over the past 15-20 years. Don't like it? Create your own archive. Good luck finding a server that has a spool for the last 15+ years of USENET, though...

  19. How is it more easily available? by bluprint · · Score: 1

    Maybe I'm just not understanding something, but if it applies to existing OSS projects, they are already on the internet for everyone to get/use (sounds pretty easy to me). If it's for new projects, why not just use something again already available publicly for creating/managing projects?

    --
    A modern day witchhunt.
  20. The way I see it... by innerweb · · Score: 3, Interesting

    .. one of the huge problems for software developers is that so much of the money in software development goes to people who have relatively little if anything to do with software development. OSS will actually (IMHO) do more to correct this than any other business model.

    The step the state is taking will actually allow more money to be targeted at solutions and less money to be given to people who understood how to legally "appropriate" others ideas. Lets face it, with the IP world going the way it is going, if the government does not step in actively to fight the Copyright Law the fed has created, it will become fiscally dangerous to write and release code.

    If the governing bodies develop their own code base by paying internal people to write what they need, sharing and building upon the efforts of other similar bodies, not only will they evolve better standards (happens easier when you share code development), but we will wind up with more "fill in your state here" based coders. I am sure that outsourcing will happen with much of the development eventually, but they will still need internal brain trust to make it all work, and the code will be available for others to build upon. So, instead of paying forever for marginally valuable software, they pay once for targeted solutions that can be expanded, replaced or enhanced as they see fit. Then they only pay to enhance or fix what they have. Since the code base is shared by other government programmers (or actually is OSS), they gain the benefits of OSS at least to a limited degree. In the end, it will be less expensive, a better use of tax dollars and more productive at the user end.

    Maybe the states can use the savings to improve the education system. How many other professions can you attend school for 12 years of you life and only expect to make 50k to 60k per year? Heck, my wife worked at a cosmetics counter selling Cli**que and made more money than a teacher with less than a few years experience.

    InnerWeb

    --
    Freud might say that Intelligent Design is religion's ID.
  21. Ooooohh, you just wait... by inode_buddha · · Score: 0, Troll

    BillG's gonna be pissed now!

    --
    C|N>K
  22. Zope is on the list by srichter · · Score: 1

    As a MA resident and one of the developers of the upcoming Zope 3 release, I was very positively surprised to see Zope (Z Object Publishing Environment) on the list of supported projects. I know that Zope has been used by the government for a long time, but that it is being embraced in this way is even better!

    Go MA and Peter Quinn!

    --
    -- Stephan Richter
    1. Re:Zope is on the list by AlastairBurt · · Score: 1

      The way I understood it they are using Zope to implement the repository itself. In this they are more or less following in the footsteps of the Brazilian government:

      http://www.softwarelivre.gov.br/


      -- Alastair

      http://www.for-the-people.org/

  23. Are you serious? by Anonymous Coward · · Score: 1, Insightful

    It is finished. The tunnels are open.

    1. Re:Are you serious? by amabbi · · Score: 1
      It is finished. The tunnels are open.

      No, it's not. The tunnels might be open, but they're not complete, and won't be for at least a year. Currently they're open to the elements (tunnels couldn't be completely enclosed until the elevated artery was demolished) and the southbound tunnel near Dewey Square only has 2 lanes instead of the 3-4 lanes it was designed for. It's scheduled to be finished in 12-18 months or so, I think, which only makes ita decade or so behind schedule.

    2. Re:Are you serious? by Anonymous Coward · · Score: 0

      What kind of a fucking idiot are you? Your obviously one of those peoples republic of cambridge cock smoking limosine liberal fucktards who doesn't have to drive to the end of storrow drive to get on the interchange to the tobin bridge...you too busy taking it up the ass from your fellow kennedy worshipers.

  24. Been there, done that. by agslashdot · · Score: 4, Interesting
    Whoever modded the grandparent a troll simply doesn't get it.

    See, the last outfit I worked for, a private brokerage company, had 15,000+ employees scattered across a dozen cities. They wanted to do the SAME EXACT thing - "build and manage an OSS software repository". Same spiel - "We are using OSS all over the place, but each department has its own variant & version, so lets get together & pool our resources, build an internal repository of OSS & then manage it ourselves".

    Guess what ? After a few months & a few hundred thousand dollars, the thing simply fell apart. The "department to build & manage OSS repository" was disbanded & people moved on.

    Why ? Because folks in insurance wanted functionality that folks in mortgage didn't want that compliance wanted that legal didn't want that sysadmins wanted that webmasters didn't want that Perl hackers wanted that Java developers didn't want that....you get my point.

    Different versions and variants exist because different people want different things. Trying to come up with a common software repository is just a pipedream.

    Now, all the above happened in a PRIVATE company, where there are things like profit margins & paychecks - real incentive to make things happen. Imagine a government trying to "build and manage an OSS repository", with umpteen departments, terrific bereaucracy, and absolutely no commercial incentive. The mind boggles...

    1. Re:Been there, done that. by autocracy · · Score: 1

      I think the big distinction was that the sofware these states wanted to manage would be code that was written by them specifically for governmental purposes... as opposed to something like a standardized version of Apache.

      --
      SIG: HUP
  25. Anyone read as *M$* build Opensource repository by toesate · · Score: 0, Troll

    I thought the sun has set on the wrong side suddenly.

    --
    Hey, that's my password you are typing
    1. Re:Anyone read as *M$* build Opensource repository by Anonymous Coward · · Score: 0

      Ummm, how the hell do you confuse "Microsoft" with "Massachusetts?"

  26. Oh, good. by musingmelpomene · · Score: 1
    For a minute there, I thought they'd made an open-source suppository.

    That would be bad in innumerable ways.

  27. Re:We have to tailor your arguments for your audie by Saeed+al-Sahaf · · Score: 1

    But I do think that IT managers, both public and private (as well as press) are now starting to see the issues. I'm not sure that the general public, even psudo-geeks and computer literate ones, even need to care much about it, other than communication to public officials that how our tax dollars are spent is important.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  28. I gotta admit, I'm impressed by digrieze · · Score: 0, Troll

    I was wondering WHAT could take the place of "THE BIG DIG", now I know.

    This is a stroke of genious, fully worthy of a legacy for Teddy K. and J.F.Kerry. Just imagine, a government agency authorized to spend the governments money to store and maintain active datacenters for publically available program code they rip off the internet. Just imagine the Terrabytes waiting to be archived in some dismal data warehouse that will need a continually increasing budget. Best yet, the only people that will be aware of it will be a few legislators that actually read the budget and notice a single line item for "data storage".

    If the air force had figured this out area 51 would still be a total secret and the budget would be high enough by now to have their OWN space station.

    and no, I'm NOT cynical.

    --
    It doesn't matter what you wrap your emotions around, Reality is a brick wall specifically designed to scramble eggs
  29. MITD-It's "Hammered" Time. by Anonymous Coward · · Score: 0

    There's also the "economic crunch" that states are suffering. I believe Massachusetts is one of the harder hit states.

  30. Re:Speaking of public repositories... by Anonymous Coward · · Score: 0

    And when they're gone, the archive is gone. There are no servers w/ archives going 20 years back, and you know it....

    When google goes the way of pets.com, a vital piece of internet history will go with them. If you're comfortable with that, fine. But your comfort doesn't mean that would not be a negative development for the world at large.

  31. Re:Speaking of public repositories... by hyperstation · · Score: 1

    fire up your fav editor, and write a web spider to suck all of googles archives out.

    then start archiving from the present feeds....

  32. Future of Freedom by bstadil · · Score: 2, Interesting
    I just finished Fareed Zakaria's book Future of Freedom and he makes a point why it is that Programs never dies.

    The reason is the Cost / Benefit of the two groups involved.

    The benefactors of the program stands to gain a huge amount per member and as such is very motivated to Lobby and exercise Democratic rights for keeping the program.

    The group paying (General Public) is large and the impact on each member is VERY small so they have little incentive to stop it through democtatic pressure. Result: No program ever dies.

    The book is highly recommended.

    Synopsis:

    Democracy is not inherently good, Zakaria (From Wealth to Power) tells us in his thought-provoking and timely second book. It works in some situations and not others, and needs strong limits to function properly. The editor of Newsweek International and former managing editor of Foreign Affairs takes us on a tour of democracy's deficiencies, beginning with the reminder that in 1933 Germans elected the Nazis. While most Western governments are both democratic and liberal-i.e., characterized by the rule of law, a separation of powers, and the protection of basic rights-the two don't necessarily go hand in hand. Zakaria praises countries like Singapore, Chile and Mexico for liberalizing their economies first and then their political systems, and compares them to other Third World countries "that proclaimed themselves democracies immediately after their independence, while they were poor and unstable, [but] became dictatorships within a decade." But Zakaria contends that something has also gone wrong with democracy in America, which has descended into "a simple-minded populism that values popularity and openness." The solution, Zakaria says, is more appointed bodies, like the World Trade Organization and the U.S. Supreme Court, which are effective precisely because they are insulated from political pressures. Zakaria provides a much-needed intellectual framework for many current foreign policy dilemmas, arguing that the United States should support a liberalizing dictator like Pakistan's Pervez Musharraf, be wary of an elected "thug" like Venezuela's Hugo Chavez and take care to remake Afghanistan and Iraq into societies that are not merely democratic but free.

    --
    Help fight continental drift.
  33. Re:Ninnle tops the list! by Anonymous Coward · · Score: 0

    Ninnle IS Linux! It happens to be the distro that Linus himself has on his personal system.

  34. Many others by Anonymous Coward · · Score: 0
    Many government and university labs release there software to the community. In fact, many are legally required to release there sofware into the public domain. Here are just a couple examples off the top of my head:

    Argonne National Laboratory maintains a MPI (Message Passing Interface) implementation for parallel computing called MPICH

    The National Center for Biotechnology Information(NCBI), run by the NIH, develops a suite of utilities and libraries for developing bioinformatics applications called the NCBI Toolkit

  35. Ignorance + Age = Stupidity by LaCosaNostradamus · · Score: 3, Interesting

    For many OSS proponents, it's not religious zeal. It's JOY ... joy over finally having a critical alternative to closed-source AND proprietary systems.

    The world is attempting to wake up from the Microsoft Age -- the Nightmare, the Dark Ages of Information -- which have been filled with secrecy, hidden potholes and vast mistrust. DRM is coming like a chariot being whipped by Microsoft and media corporations, and it frankly hates you, the common man. It's coming to turn your computer into a television set (and if I have to explain to you what's so horrible about TV, then you're intellectually lost).

    Some OSS repository in one state government is not hurting you at all. I'm sure Mass. has plenty of Microsoft, Oracle, etc. licences floating around. Now they have more choices. More alternatives. And this kind of thing is quite beneficial; after all, your government should be able to make data without having it held for ransom by a proprietary and closed provider.

    I'm warning you now. If you reside in willful ignorance long enough, you become STUPID. Is that what you really wanted in your life?

    --
    [You have a stable society when some nut guns down a schoolyard and the law doesn't change.]
  36. The meaning of 'open source' by gidds · · Score: 1
    While I agree with most of your points, I must take issue with:

    If the repository is not public, then how is it open source?

    Open source does not necessarily mean that everyone has access to the source. It means that everyone who has access to the binary also has access to the source.

    That's a very different proposition, but it's enough to ensure code freedom. (For common values of 'freedom', anyway.) That's how companies can legally modify open-sourced software for their internal use without releasing it. For that matter, that's how I'm able to modify open-sourced software for my private use without releasing it!

    --

    Ceterum censeo subscriptionem esse delendam.

    1. Re:The meaning of 'open source' by Minna+Kirai · · Score: 1

      It means that everyone who has access to the binary also has access to the source.

      That's a little different from the definition of Free Software, which requires that everyone with access to the binary also has access and rights to the source.

  37. They've got more than one by stoolpigeon · · Score: 1

    but the Navy space station is even nicer. Oh, did I type that out loud?

    --
    It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
    1. Re:They've got more than one by digrieze · · Score: 1

      Yeah, but they had to have that to support the massive energy transmission arrays they built up in the arctic.

      --
      It doesn't matter what you wrap your emotions around, Reality is a brick wall specifically designed to scramble eggs
  38. Nice Zealotry-Will bomb for code. by Anonymous Coward · · Score: 0

    Well I payed to have tactical nukes built. Were's the tactical nuke I'm owed?

  39. Word Left Out... by MonkeyGone2Heaven · · Score: 1


    The repository will be managed by the Government Open Code Collaborative


    Given government's love of acronyms I can't believe that nobody though of Government Reusable Open Code Collaborative; aka, GROCC.

  40. Not GPL compatible by 0x0d0a · · Score: 2, Informative

    The license being used by the repository is explicitly not GPL-compatible. It prohibits any commercial use of the code. This is a primary reason for setting up the repository, as commonwealth-produced software cannot (under the current system) be used by entities to make money, according to the article.

  41. Seems like what we have... by xmda · · Score: 1

    ...here in the Nordic countries:

    http://www.nordicos.org/

    Me like.

  42. CUPS... by TWX · · Score: 1

    mainly just Common Unix Printing System...

    Though the wardriving software for Linux wasn't as easy to use as the wardriving software for OSX, last time I looked at both.

    That's about it so far...

    --
    Do not look into laser with remaining eye.
  43. I'm scared... by mi · · Score: 1

    The best way to kill an idea is to let a government do it.

    Especially the government of the People's Republic of Massachusetts. Even with the best of intentions they will screw up.

    --
    In Soviet Washington the swamp drains you.