Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Government Open Source IT

Ask Slashdot: How To Share a SharePoint Site? 151

New submitter grzzld writes "I am a systems analyst for a County in New York. Last year I made a SharePoint site that manages grants and it was well received. So much so that it won a NACo award. Since then, there have been several requests from other municipalities from around the country who would like to get this SharePoint site. The county is trying to figure out how to protect ourselves from people making money from it and having people hold us liable if it they use it and something goes awry. I am afraid that ultimately nothing will be done and the site will not be shared since at the end of the day it is much easier to not do anything and just say no. I proposed that we license it under an Open Source agreement but I am not versed enough in the differences between all of them. It is also unclear to me if I could do this since the nature of the 'program' is a SharePoint site. It seemed like CodePlex would be a good place to put this since it is Microsoft centric and it an open source initiative. I just want to contribute my work to others who may find it useful. The county just wants to make sure they can't be held liable and have somebody turn my work around and make a buck. How can I release this to the world and make sure the county's concerns are addressed?"
This discussion has been archived. No new comments can be posted.

Ask Slashdot: How To Share a SharePoint Site?

Comments Filter:
  • by abiggerhammer ( 753022 ) on Thursday April 19, 2012 @01:00PM (#39735467)
    The GPL variants and the BSD licenses all contain a disclaimer of warranty (the part that reads "THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE" or similar), which addresses the county's concerns. By releasing code under a license with such a disclaimer, you are asserting that no one can sue you if the code breaks, even if your code breaking caused them some kind of loss.
  • Do nothing. (Score:2, Insightful)

    by Anonymous Coward on Thursday April 19, 2012 @01:01PM (#39735477)

    CYA and don't share anything. If they want it badly enough, they can contract you to build something similar.

  • Making money (Score:4, Insightful)

    by man_of_mr_e ( 217855 ) on Thursday April 19, 2012 @01:10PM (#39735611)

    Why do you care if others make money off it? It's government developed so that means it was funded by taxpayer money.

    All taxpayers should have access to it, even if they want to make money from it. It should automatically be public domain.

    You can still CYA by a simple BSD style license.

  • Re:quick how-to (Score:3, Insightful)

    by Anonymous Coward on Thursday April 19, 2012 @01:10PM (#39735615)

    I loath Microsoft and closed-source software, and "walk the walk" (I use a total of 4 proprietary programs), but this comment is beyond worthless. The poster says that the site works great, and wants to share it with other groups. You are basically saying "no it doesn't." And there is no analysis as to why that might be the case. You might as well have just screamed nonsenically in anger.

  • by jpate ( 1356395 ) on Thursday April 19, 2012 @01:24PM (#39735737) Homepage
    Why does the county care if somebody else makes money on it? That's just vindictive. As long as there's nothing blocking somebody from developing useful things for free, I see no reason to forbid business uses.
  • Talk to a lawyer! (Score:4, Insightful)

    by Dynedain ( 141758 ) <slashdot2 AT anthonymclin DOT com> on Thursday April 19, 2012 @01:37PM (#39735869) Homepage

    If the county wants to share but is concerned about liability, THEY SHOULD TALK TO THEIR ON-STAFF/ IN-HOUSE/ ON-RETAINER legal counsel!

    They have them, I guarantee it. Use them. The last they want is a tech guy (who has already admitted he doesn't know the implications of the various licenses) fumbling around to figure this out.

    If they really really don't want to talk to their own legal counsel, then just prepare an instruction list that other municipalities could follow and publish that instead of trying to distribute the whole kit-and-kaboodle.

  • Re:quick how-to (Score:5, Insightful)

    by Serious Callers Only ( 1022605 ) on Thursday April 19, 2012 @05:51PM (#39739455)

    Microsoft does not make computers, or make them cheaper. That trend was started by hardware manufacturers competing with IBM with clean room implementations of the bios, and continued with netbooks etc. Nice rewrite of history.

  • by westyvw ( 653833 ) on Friday April 20, 2012 @12:33AM (#39742473)

    Every year a company comes drops down a freedom of information act for a particular piece of software in our state. They take it and go out and make money with it. Every year I argue that we should just put it out on the Internet so we can save the freedom of information act request time and money. Whats wrong with giving back the tax dollars in research to help put someone (and their employees) to work?

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...