<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rschmid</id>
	<title>Expertiza_Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rschmid"/>
	<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Special:Contributions/Rschmid"/>
	<updated>2026-05-13T15:05:03Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2176</id>
		<title>CSC 379:Week 5, Group 4</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2176"/>
		<updated>2007-08-08T12:30:36Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Paperless Electronic Voting=&lt;br /&gt;
'''Examine the ethical issues regarding paperless electronic voting (e.g. voting machines with no voter-approved persistent paper record of the electronic ballots cast).  Include a brief overview of what paperless electronic voting is and instances where it has been used.  Draw from a variety of internet resources to explain its advantages and disadvantages (including obstacles to adoption of equipment that maintain a paper record).  Is there an ethical responsibility to create and maintain a persistent paper record of votes, if so, whose?'''&lt;br /&gt;
&lt;br /&gt;
'''The [http://courses.ncsu.edu/csc379/lec/001/lectures/wk14/index.html discussion questions] listed at the bottom of the weekly assignments page should be answered through the content you provide on this wiki page.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
===What is Paperless Electronic Voting===&lt;br /&gt;
* Paperless Electronic Voting is a completely computerized voting system. A voter places their vote by touchscreen, keyboard or some other electronic means. No paper records of the electronic ballot are kept and there is no way for the voter to verify/check their vote.&lt;br /&gt;
* Paperless Electronic Voting has been used in the following states/elections&lt;br /&gt;
** [http://www.heraldtribune.com/apps/pbcs.dll/article?AID=/20061108/NEWS/611080506 Sarasota County election of Republican Vern Buchanan]&lt;br /&gt;
&lt;br /&gt;
===Ethical Issues===&lt;br /&gt;
Without any kind of a paper trail it would be impossible to validate people votes. This brings about many ethical issues...&lt;br /&gt;
* Voters could accidentally vote for the wrong person without knowing it.&lt;br /&gt;
* Voters may not have the ability to change their vote if they accidentally vote for the wrong canidate.&lt;br /&gt;
* Programmers could write faulty code, causing inacurate ballots without anyone even knowing. This is especially risky if software testing is not implemented fully.&lt;br /&gt;
* Programmers could intentionally write malicious code which automatically votes for a specific canidate regardless of who the voter actually votes for.&lt;br /&gt;
&lt;br /&gt;
===Relevant External Links===&lt;br /&gt;
* [http://www.verifiedvotingfoundation.org/article.php?id=6461 It's Time to Outlaw Paperless Electronic Voting in the U.S.]&lt;br /&gt;
* [http://jurist.law.pitt.edu/paperchase/2006/12/federal-report-says-paperless.php Federal report says paperless electronic voting machines cannot be made secure]&lt;br /&gt;
* [http://jurist.law.pitt.edu/paperchase/2006/11/florida-lawsuit-targets-electronic.php Florida lawsuit targets electronic voting machines in close race]&lt;br /&gt;
&lt;br /&gt;
* [http://www.washingtonpost.com/wp-dyn/content/article/2006/11/30/AR2006113001637.html Security Of Electronic Voting Is Condemned]&lt;br /&gt;
* [http://www.nytimes.com/2007/07/28/us/28vote.html?ex=1343620800&amp;amp;en=985acc7423727bdf&amp;amp;ei=5124&amp;amp;partner=permalink&amp;amp;exprod=permalink New York Times - Scientists’ Tests Hack Into Electronic Voting Machines in California and Elsewhere]&lt;br /&gt;
* [http://www.sourcewatch.org/index.php?title=Help_America_Vote_Act Congresspedia - Help America Vote Act]&lt;br /&gt;
&lt;br /&gt;
===Relevant Class Website Links===&lt;br /&gt;
* [http://ethics.csc.ncsu.edu/risks/reliability/voting/receipts/new.html Articles on Paperless Electronic Voting]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2175</id>
		<title>CSC 379:Week 5, Group 4</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2175"/>
		<updated>2007-08-06T21:59:39Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Paperless Electronic Voting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Paperless Electronic Voting=&lt;br /&gt;
'''Examine the ethical issues regarding paperless electronic voting (e.g. voting machines with no voter-approved persistent paper record of the electronic ballots cast).  Include a brief overview of what paperless electronic voting is and instances where it has been used.  Draw from a variety of internet resources to explain its advantages and disadvantages (including obstacles to adoption of equipment that maintain a paper record).  Is there an ethical responsibility to create and maintain a persistent paper record of votes, if so, whose?'''&lt;br /&gt;
&lt;br /&gt;
'''The [http://courses.ncsu.edu/csc379/lec/001/lectures/wk14/index.html discussion questions] listed at the bottom of the weekly assignments page should be answered through the content you provide on this wiki page.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
===What is Paperless Electronic Voting===&lt;br /&gt;
* Paperless Electronic Voting is a completely computerized voting system. I voted places their vote by touchscreen, keyboard or some other electronic means. No paper recrods of the electronic ballot are kept and there is no way for the voter to verify/check thier vote.&lt;br /&gt;
* Paperless Electronic Voting has been used in the following states/elections&lt;br /&gt;
** [http://www.heraldtribune.com/apps/pbcs.dll/article?AID=/20061108/NEWS/611080506 Sarasota County election of Republican Vern Buchanan]&lt;br /&gt;
&lt;br /&gt;
===Ethical Issues===&lt;br /&gt;
Without any kind of a paper trail it would be impossible to validate people votes. This brings about many ethical issues...&lt;br /&gt;
* Voters could accidentally vote for the wrong person without knowing it.&lt;br /&gt;
* Voters may not have the ability to change their vote if they accidentally vote for the wrong canidate.&lt;br /&gt;
* Programmers could write faulty code, causing inacurate ballots without anyone even knowing. This is especially risky if software testing is not implemented fully.&lt;br /&gt;
* Programmers could intentionally write malicious code which automatically votes for a specific canidate regardless of who the voter actually votes for.&lt;br /&gt;
&lt;br /&gt;
===Relevant External Links===&lt;br /&gt;
* [http://www.verifiedvotingfoundation.org/article.php?id=6461 It's Time to Outlaw Paperless Electronic Voting in the U.S.]&lt;br /&gt;
* [http://jurist.law.pitt.edu/paperchase/2006/12/federal-report-says-paperless.php Federal report says paperless electronic voting machines cannot be made secure]&lt;br /&gt;
* [http://jurist.law.pitt.edu/paperchase/2006/11/florida-lawsuit-targets-electronic.php Florida lawsuit targets electronic voting machines in close race]&lt;br /&gt;
&lt;br /&gt;
* [http://www.washingtonpost.com/wp-dyn/content/article/2006/11/30/AR2006113001637.html Security Of Electronic Voting Is Condemned]&lt;br /&gt;
* [http://www.nytimes.com/2007/07/28/us/28vote.html?ex=1343620800&amp;amp;en=985acc7423727bdf&amp;amp;ei=5124&amp;amp;partner=permalink&amp;amp;exprod=permalink New York Times - Scientists’ Tests Hack Into Electronic Voting Machines in California and Elsewhere]&lt;br /&gt;
* [http://www.sourcewatch.org/index.php?title=Help_America_Vote_Act Congresspedia - Help America Vote Act]&lt;br /&gt;
&lt;br /&gt;
===Relevant Class Website Links===&lt;br /&gt;
* [http://ethics.csc.ncsu.edu/risks/reliability/voting/receipts/new.html Articles on Paperless Electronic Voting]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2174</id>
		<title>CSC 379:Week 5, Group 4</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2174"/>
		<updated>2007-08-06T21:41:19Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Paperless Electronic Voting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Paperless Electronic Voting=&lt;br /&gt;
'''Examine the ethical issues regarding paperless electronic voting (e.g. voting machines with no voter-approved persistent paper record of the electronic ballots cast).  Include a brief overview of what paperless electronic voting is and instances where it has been used.  Draw from a variety of internet resources to explain its advantages and disadvantages (including obstacles to adoption of equipment that maintain a paper record).  Is there an ethical responsibility to create and maintain a persistent paper record of votes, if so, whose?'''&lt;br /&gt;
&lt;br /&gt;
'''The [http://courses.ncsu.edu/csc379/lec/001/lectures/wk14/index.html discussion questions] listed at the bottom of the weekly assignments page should be answered through the content you provide on this wiki page.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
===What is Paperless Electronic Voting===&lt;br /&gt;
* Paperless Electronic Voting is a completely computerized voting system. I voted places their vote by touchscreen, keyboard or some other electronic means. No paper recrods of the electronic ballot are kept and there is no way for the voter to verify/check thier vote.&lt;br /&gt;
* Paperless Electronic Voting has been used in the following states/elections&lt;br /&gt;
** [http://www.heraldtribune.com/apps/pbcs.dll/article?AID=/20061108/NEWS/611080506 Sarasota County election of Republican Vern Buchanan &lt;br /&gt;
&lt;br /&gt;
===Ethical Issues===&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
===Relevant External Links===&lt;br /&gt;
* [http://www.verifiedvotingfoundation.org/article.php?id=6461 It's Time to Outlaw Paperless Electronic Voting in the U.S.]&lt;br /&gt;
* [http://jurist.law.pitt.edu/paperchase/2006/12/federal-report-says-paperless.php Federal report says paperless electronic voting machines cannot be made secure]&lt;br /&gt;
* [http://jurist.law.pitt.edu/paperchase/2006/11/florida-lawsuit-targets-electronic.php Florida lawsuit targets electronic voting machines in close race]&lt;br /&gt;
&lt;br /&gt;
* [http://www.washingtonpost.com/wp-dyn/content/article/2006/11/30/AR2006113001637.html Security Of Electronic Voting Is Condemned]&lt;br /&gt;
* [http://www.nytimes.com/2007/07/28/us/28vote.html?ex=1343620800&amp;amp;en=985acc7423727bdf&amp;amp;ei=5124&amp;amp;partner=permalink&amp;amp;exprod=permalink New York Times - Scientists’ Tests Hack Into Electronic Voting Machines in California and Elsewhere]&lt;br /&gt;
* [http://www.sourcewatch.org/index.php?title=Help_America_Vote_Act Congresspedia - Help America Vote Act]&lt;br /&gt;
&lt;br /&gt;
===Relevant Class Website Links===&lt;br /&gt;
* [http://ethics.csc.ncsu.edu/risks/reliability/voting/receipts/new.html Articles on Paperless Electronic Voting]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2173</id>
		<title>CSC 379:Week 5, Group 4</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2173"/>
		<updated>2007-08-06T20:44:20Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Paperless Electronic Voting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Paperless Electronic Voting=&lt;br /&gt;
'''Examine the ethical issues regarding paperless electronic voting (e.g. voting machines with no voter-approved persistent paper record of the electronic ballots cast).  Include a brief overview of what paperless electronic voting is and instances where it has been used.  Draw from a variety of internet resources to explain its advantages and disadvantages (including obstacles to adoption of equipment that maintain a paper record).  Is there an ethical responsibility to create and maintain a persistent paper record of votes, if so, whose?'''&lt;br /&gt;
&lt;br /&gt;
'''The [http://courses.ncsu.edu/csc379/lec/001/lectures/wk14/index.html discussion questions] listed at the bottom of the weekly assignments page should be answered through the content you provide on this wiki page.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
===What is Paperless Electronic Voting===&lt;br /&gt;
* Paperless Electronic Voting is &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Relevant External Links===&lt;br /&gt;
* [http://www.verifiedvotingfoundation.org/article.php?id=6461 It's Time to Outlaw Paperless Electronic Voting in the U.S.]&lt;br /&gt;
* [http://jurist.law.pitt.edu/paperchase/2006/12/federal-report-says-paperless.php Federal report says paperless electronic voting machines cannot be made secure]&lt;br /&gt;
* [http://jurist.law.pitt.edu/paperchase/2006/11/florida-lawsuit-targets-electronic.php &lt;br /&gt;
Florida lawsuit targets electronic voting machines in close race]&lt;br /&gt;
&lt;br /&gt;
* [http://www.washingtonpost.com/wp-dyn/content/article/2006/11/30/AR2006113001637.html Security Of Electronic Voting Is Condemned]&lt;br /&gt;
* [http://www.nytimes.com/2007/07/28/us/28vote.html?ex=1343620800&amp;amp;en=985acc7423727bdf&amp;amp;ei=5124&amp;amp;partner=permalink&amp;amp;exprod=permalink New York Times - Scientists’ Tests Hack Into Electronic Voting Machines in California and Elsewhere]&lt;br /&gt;
* [http://www.sourcewatch.org/index.php?title=Help_America_Vote_Act Congresspedia - Help America Vote Act]&lt;br /&gt;
&lt;br /&gt;
===Relevant Class Website Links===&lt;br /&gt;
* [http://ethics.csc.ncsu.edu/risks/reliability/voting/receipts/new.html Articles on Paperless Electronic Voting]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2172</id>
		<title>CSC 379:Week 5, Group 4</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_5,_Group_4&amp;diff=2172"/>
		<updated>2007-08-06T20:38:03Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Paperless Electronic Voting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Paperless Electronic Voting=&lt;br /&gt;
'''Examine the ethical issues regarding paperless electronic voting (e.g. voting machines with no voter-approved persistent paper record of the electronic ballots cast).  Include a brief overview of what paperless electronic voting is and instances where it has been used.  Draw from a variety of internet resources to explain its advantages and disadvantages (including obstacles to adoption of equipment that maintain a paper record).  Is there an ethical responsibility to create and maintain a persistent paper record of votes, if so, whose?'''&lt;br /&gt;
&lt;br /&gt;
'''The [http://courses.ncsu.edu/csc379/lec/001/lectures/wk14/index.html discussion questions] listed at the bottom of the weekly assignments page should be answered through the content you provide on this wiki page.'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
__TOC__&lt;br /&gt;
&lt;br /&gt;
===Relevant External Links===&lt;br /&gt;
* [http://www.verifiedvotingfoundation.org/article.php?id=6461 It's Time to Outlaw Paperless Electronic Voting in the U.S.]&lt;br /&gt;
* [http://jurist.law.pitt.edu/paperchase/2006/12/federal-report-says-paperless.php Federal report says paperless electronic voting machines cannot be made secure]&lt;br /&gt;
* [http://www.washingtonpost.com/wp-dyn/content/article/2006/11/30/AR2006113001637.html Security Of Electronic Voting Is Condemned]&lt;br /&gt;
* [http://www.nytimes.com/2007/07/28/us/28vote.html?ex=1343620800&amp;amp;en=985acc7423727bdf&amp;amp;ei=5124&amp;amp;partner=permalink&amp;amp;exprod=permalink New York Times - Scientists’ Tests Hack Into Electronic Voting Machines in California and Elsewhere]&lt;br /&gt;
* [http://www.sourcewatch.org/index.php?title=Help_America_Vote_Act Congresspedia - Help America Vote Act]&lt;br /&gt;
&lt;br /&gt;
===Relevant Class Website Links===&lt;br /&gt;
* [http://ethics.csc.ncsu.edu/risks/reliability/voting/receipts/new.html Articles on Paperless Electronic Voting]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_4,_Group_6&amp;diff=1980</id>
		<title>CSC 379:Week 4, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_4,_Group_6&amp;diff=1980"/>
		<updated>2007-07-30T00:31:08Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Relevant External Links: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Mapping / Google Street View=&lt;br /&gt;
Many are concerned about the invasiveness of satellite/aerospace imaging.  Governments have complained of risks related to the availability of images of sensitive military or strategic sites, sometimes requesting obfuscation or blackouts of the compromising images.  With the expansion of mapping technologies to the street level (see links below), more people have become concerned about how invasive to their privacy public photography can be. &lt;br /&gt;
&lt;br /&gt;
Amongst many lawful and beneficial uses, mapping technologies have also made it easier for planning crimes.&lt;br /&gt;
&lt;br /&gt;
'''Explore the ethical implications of mapping technologies.  Should mapping technologies comply with the laws of every country that has access their services even if they are not located there?  Are requests for censorship of public photography ethical?  When?  As mapping imagery increases in coverage and resolution over time, should there be limits set or censorship mandated to protect the public from lawful but invasive and sometimes unwanted photography?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Google Street View=&lt;br /&gt;
==Overview==&lt;br /&gt;
[http://http://maps.google.com/help/maps/streetview/ Google Street View] is a tool integrated into [http://maps.google.com Google Maps] that allows users to view routes from a street-level perspective.  This tool is only available for select locations, usually large cities such as Miami and San Francisco.  When using Street View, you are given a 360 degree view of the street from the perspective of a car on the street.  The view is generated from actual photographs taken of the streets.  There is a zoom feature incorporated into the view and people and private property are not censored by Google.  Street View was developed as a tool to aid users in finding landmarks, shops, restaurants, and other points of interest in cities that would otherwise be foreign to a tourist or other traveler.  Another touted feature is that you can take a 'virtual walk' around a Street View enabled city.  &lt;br /&gt;
&lt;br /&gt;
==Concerns==&lt;br /&gt;
There are several concerns that people have with Google Street View.  Many people function under the assumption that their everyday actions are not being watched.  Some of the Street View photographs, which are all readily accessible show people walking the streets or entering establishments.  Most of these pictures seem harmless, but there are a few that show men walking into adult-themed bookstores, or women laying out sunbathing.  Had these people known that they would be displayed to the world, they may have changed their plans for that particular day, and surely some of them would have never consented to these images being shown.  While there are some obvious benefits to Street View, if even one person is offended by the content of the images then there is reason for concern of the ethicality of the tool.  Some may argue that the pictures are taken from a public place, and would be visible to anyone who happened to be traveling through the area.  While this is compelling, one must also consider the fact that the people photographed may not have had a problem with being seen by the general public in small numbers, but would object to being seen by the millions of people that use Google.  &lt;br /&gt;
&lt;br /&gt;
There are many questions that can be raised about Street View regarding individual's privacy rights. However, none break any actual laws since all pictures are taken in public places. Does that make it ok though? Is it ethical? If you accidentally caught changing infront of the shower by Google Street View photographers should they remove the photo? Since it was obviously not their intent to take a picture of you naked it may be hard to hold them accountable. However, it would be in good ethical 'taste' to remove the pictures if so requested, eventhough it would not be required by law.&lt;br /&gt;
&lt;br /&gt;
It's not just mapping on a street level that have ethical implications. Mapping technologies on a larger scale bring up other ethical issues. While being able to view satalite imagery may make it easier for you to find a place of business, it could also aid robbers in researching their next robbery victim. It could even help terrorists plan their next attack on a major landmark without even requiring them to visit their target. Satalite imagery could have a huge impact on national security. Should access to such information be restricted? and to who's laws should they conform to? This all depends on who has ownership of the information. If a Russian satalite is sailing over the United States and takes pictures of the White House they should be allowed to do whatever they want with those images, unless of course, they obtained them by breaking some law. This obviously has great implications if such information falls into the wrong hands, but, ethically, you can't deny or restrict someone use to something that is rightfully and legally theirs. The access to such information can not ethically be restricted, but perhaps the ways the information is obtained could.&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
===Relevant External Links:===&lt;br /&gt;
* [http://www.nytimes.com/2007/06/01/technology/01private.html Google Zooms In Too Close for Some (New York Times)] &lt;br /&gt;
* [http://www.boingboing.net/2007/06/05/google_street_view_a.html Public Opinion on Google Street View (Boing Boing)]&lt;br /&gt;
* [http://jonsmith.greykitty.net/2007/07/09/google-street-view/ Google Street View at Arriving Somewhere]&lt;br /&gt;
* [http://www.govexec.com/dailyfed/0805/082405td2.htm Google satellite imaging software raises terrorism concerns]&lt;br /&gt;
* [http://www.nytimes.com/2005/12/20/technology/20image.html?ei=5090&amp;amp;en=fc8a8529ca004e0c&amp;amp;ex=1292734800&amp;amp;adxnnl=1&amp;amp;partner=rssuserland&amp;amp;emc=rss&amp;amp;adxnnlx=1185755335-XtGDEBT8QrPTINYVSlN1wg Governments Tremble at Google's Bird's-Eye View]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_4,_Group_6&amp;diff=1979</id>
		<title>CSC 379:Week 4, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_4,_Group_6&amp;diff=1979"/>
		<updated>2007-07-30T00:30:29Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Relevant External Links: */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Mapping / Google Street View=&lt;br /&gt;
Many are concerned about the invasiveness of satellite/aerospace imaging.  Governments have complained of risks related to the availability of images of sensitive military or strategic sites, sometimes requesting obfuscation or blackouts of the compromising images.  With the expansion of mapping technologies to the street level (see links below), more people have become concerned about how invasive to their privacy public photography can be. &lt;br /&gt;
&lt;br /&gt;
Amongst many lawful and beneficial uses, mapping technologies have also made it easier for planning crimes.&lt;br /&gt;
&lt;br /&gt;
'''Explore the ethical implications of mapping technologies.  Should mapping technologies comply with the laws of every country that has access their services even if they are not located there?  Are requests for censorship of public photography ethical?  When?  As mapping imagery increases in coverage and resolution over time, should there be limits set or censorship mandated to protect the public from lawful but invasive and sometimes unwanted photography?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Google Street View=&lt;br /&gt;
==Overview==&lt;br /&gt;
[http://http://maps.google.com/help/maps/streetview/ Google Street View] is a tool integrated into [http://maps.google.com Google Maps] that allows users to view routes from a street-level perspective.  This tool is only available for select locations, usually large cities such as Miami and San Francisco.  When using Street View, you are given a 360 degree view of the street from the perspective of a car on the street.  The view is generated from actual photographs taken of the streets.  There is a zoom feature incorporated into the view and people and private property are not censored by Google.  Street View was developed as a tool to aid users in finding landmarks, shops, restaurants, and other points of interest in cities that would otherwise be foreign to a tourist or other traveler.  Another touted feature is that you can take a 'virtual walk' around a Street View enabled city.  &lt;br /&gt;
&lt;br /&gt;
==Concerns==&lt;br /&gt;
There are several concerns that people have with Google Street View.  Many people function under the assumption that their everyday actions are not being watched.  Some of the Street View photographs, which are all readily accessible show people walking the streets or entering establishments.  Most of these pictures seem harmless, but there are a few that show men walking into adult-themed bookstores, or women laying out sunbathing.  Had these people known that they would be displayed to the world, they may have changed their plans for that particular day, and surely some of them would have never consented to these images being shown.  While there are some obvious benefits to Street View, if even one person is offended by the content of the images then there is reason for concern of the ethicality of the tool.  Some may argue that the pictures are taken from a public place, and would be visible to anyone who happened to be traveling through the area.  While this is compelling, one must also consider the fact that the people photographed may not have had a problem with being seen by the general public in small numbers, but would object to being seen by the millions of people that use Google.  &lt;br /&gt;
&lt;br /&gt;
There are many questions that can be raised about Street View regarding individual's privacy rights. However, none break any actual laws since all pictures are taken in public places. Does that make it ok though? Is it ethical? If you accidentally caught changing infront of the shower by Google Street View photographers should they remove the photo? Since it was obviously not their intent to take a picture of you naked it may be hard to hold them accountable. However, it would be in good ethical 'taste' to remove the pictures if so requested, eventhough it would not be required by law.&lt;br /&gt;
&lt;br /&gt;
It's not just mapping on a street level that have ethical implications. Mapping technologies on a larger scale bring up other ethical issues. While being able to view satalite imagery may make it easier for you to find a place of business, it could also aid robbers in researching their next robbery victim. It could even help terrorists plan their next attack on a major landmark without even requiring them to visit their target. Satalite imagery could have a huge impact on national security. Should access to such information be restricted? and to who's laws should they conform to? This all depends on who has ownership of the information. If a Russian satalite is sailing over the United States and takes pictures of the White House they should be allowed to do whatever they want with those images, unless of course, they obtained them by breaking some law. This obviously has great implications if such information falls into the wrong hands, but, ethically, you can't deny or restrict someone use to something that is rightfully and legally theirs. The access to such information can not ethically be restricted, but perhaps the ways the information is obtained could.&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
===Relevant External Links:===&lt;br /&gt;
* [http://www.nytimes.com/2007/06/01/technology/01private.html Google Zooms In Too Close for Some (New York Times)] &lt;br /&gt;
* [http://www.boingboing.net/2007/06/05/google_street_view_a.html Public Opinion on Google Street View (Boing Boing)]&lt;br /&gt;
* [http://jonsmith.greykitty.net/2007/07/09/google-street-view/] Google Street View at Arriving Somewhere&lt;br /&gt;
* [http://www.govexec.com/dailyfed/0805/082405td2.htm] Google satellite imaging software raises terrorism concerns&lt;br /&gt;
* [http://www.nytimes.com/2005/12/20/technology/20image.html?ei=5090&amp;amp;en=fc8a8529ca004e0c&amp;amp;ex=1292734800&amp;amp;adxnnl=1&amp;amp;partner=rssuserland&amp;amp;emc=rss&amp;amp;adxnnlx=1185755335-XtGDEBT8QrPTINYVSlN1wg] Governments Tremble at Google's Bird's-Eye View&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_4,_Group_6&amp;diff=1978</id>
		<title>CSC 379:Week 4, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_4,_Group_6&amp;diff=1978"/>
		<updated>2007-07-30T00:27:32Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Concerns */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Mapping / Google Street View=&lt;br /&gt;
Many are concerned about the invasiveness of satellite/aerospace imaging.  Governments have complained of risks related to the availability of images of sensitive military or strategic sites, sometimes requesting obfuscation or blackouts of the compromising images.  With the expansion of mapping technologies to the street level (see links below), more people have become concerned about how invasive to their privacy public photography can be. &lt;br /&gt;
&lt;br /&gt;
Amongst many lawful and beneficial uses, mapping technologies have also made it easier for planning crimes.&lt;br /&gt;
&lt;br /&gt;
'''Explore the ethical implications of mapping technologies.  Should mapping technologies comply with the laws of every country that has access their services even if they are not located there?  Are requests for censorship of public photography ethical?  When?  As mapping imagery increases in coverage and resolution over time, should there be limits set or censorship mandated to protect the public from lawful but invasive and sometimes unwanted photography?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Google Street View=&lt;br /&gt;
==Overview==&lt;br /&gt;
[http://http://maps.google.com/help/maps/streetview/ Google Street View] is a tool integrated into [http://maps.google.com Google Maps] that allows users to view routes from a street-level perspective.  This tool is only available for select locations, usually large cities such as Miami and San Francisco.  When using Street View, you are given a 360 degree view of the street from the perspective of a car on the street.  The view is generated from actual photographs taken of the streets.  There is a zoom feature incorporated into the view and people and private property are not censored by Google.  Street View was developed as a tool to aid users in finding landmarks, shops, restaurants, and other points of interest in cities that would otherwise be foreign to a tourist or other traveler.  Another touted feature is that you can take a 'virtual walk' around a Street View enabled city.  &lt;br /&gt;
&lt;br /&gt;
==Concerns==&lt;br /&gt;
There are several concerns that people have with Google Street View.  Many people function under the assumption that their everyday actions are not being watched.  Some of the Street View photographs, which are all readily accessible show people walking the streets or entering establishments.  Most of these pictures seem harmless, but there are a few that show men walking into adult-themed bookstores, or women laying out sunbathing.  Had these people known that they would be displayed to the world, they may have changed their plans for that particular day, and surely some of them would have never consented to these images being shown.  While there are some obvious benefits to Street View, if even one person is offended by the content of the images then there is reason for concern of the ethicality of the tool.  Some may argue that the pictures are taken from a public place, and would be visible to anyone who happened to be traveling through the area.  While this is compelling, one must also consider the fact that the people photographed may not have had a problem with being seen by the general public in small numbers, but would object to being seen by the millions of people that use Google.  &lt;br /&gt;
&lt;br /&gt;
There are many questions that can be raised about Street View regarding individual's privacy rights. However, none break any actual laws since all pictures are taken in public places. Does that make it ok though? Is it ethical? If you accidentally caught changing infront of the shower by Google Street View photographers should they remove the photo? Since it was obviously not their intent to take a picture of you naked it may be hard to hold them accountable. However, it would be in good ethical 'taste' to remove the pictures if so requested, eventhough it would not be required by law.&lt;br /&gt;
&lt;br /&gt;
It's not just mapping on a street level that have ethical implications. Mapping technologies on a larger scale bring up other ethical issues. While being able to view satalite imagery may make it easier for you to find a place of business, it could also aid robbers in researching their next robbery victim. It could even help terrorists plan their next attack on a major landmark without even requiring them to visit their target. Satalite imagery could have a huge impact on national security. Should access to such information be restricted? and to who's laws should they conform to? This all depends on who has ownership of the information. If a Russian satalite is sailing over the United States and takes pictures of the White House they should be allowed to do whatever they want with those images, unless of course, they obtained them by breaking some law. This obviously has great implications if such information falls into the wrong hands, but, ethically, you can't deny or restrict someone use to something that is rightfully and legally theirs. The access to such information can not ethically be restricted, but perhaps the ways the information is obtained could.&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
===Relevant External Links:===&lt;br /&gt;
* [http://www.nytimes.com/2007/06/01/technology/01private.html Google Zooms In Too Close for Some (New York Times)] &lt;br /&gt;
* [http://www.boingboing.net/2007/06/05/google_street_view_a.html Public Opinion on Google Street View (Boing Boing)]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_4,_Group_6&amp;diff=1977</id>
		<title>CSC 379:Week 4, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_4,_Group_6&amp;diff=1977"/>
		<updated>2007-07-30T00:27:02Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Concerns */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Mapping / Google Street View=&lt;br /&gt;
Many are concerned about the invasiveness of satellite/aerospace imaging.  Governments have complained of risks related to the availability of images of sensitive military or strategic sites, sometimes requesting obfuscation or blackouts of the compromising images.  With the expansion of mapping technologies to the street level (see links below), more people have become concerned about how invasive to their privacy public photography can be. &lt;br /&gt;
&lt;br /&gt;
Amongst many lawful and beneficial uses, mapping technologies have also made it easier for planning crimes.&lt;br /&gt;
&lt;br /&gt;
'''Explore the ethical implications of mapping technologies.  Should mapping technologies comply with the laws of every country that has access their services even if they are not located there?  Are requests for censorship of public photography ethical?  When?  As mapping imagery increases in coverage and resolution over time, should there be limits set or censorship mandated to protect the public from lawful but invasive and sometimes unwanted photography?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Google Street View=&lt;br /&gt;
==Overview==&lt;br /&gt;
[http://http://maps.google.com/help/maps/streetview/ Google Street View] is a tool integrated into [http://maps.google.com Google Maps] that allows users to view routes from a street-level perspective.  This tool is only available for select locations, usually large cities such as Miami and San Francisco.  When using Street View, you are given a 360 degree view of the street from the perspective of a car on the street.  The view is generated from actual photographs taken of the streets.  There is a zoom feature incorporated into the view and people and private property are not censored by Google.  Street View was developed as a tool to aid users in finding landmarks, shops, restaurants, and other points of interest in cities that would otherwise be foreign to a tourist or other traveler.  Another touted feature is that you can take a 'virtual walk' around a Street View enabled city.  &lt;br /&gt;
&lt;br /&gt;
==Concerns==&lt;br /&gt;
There are several concerns that people have with Google Street View.  Many people function under the assumption that their everyday actions are not being watched.  Some of the Street View photographs, which are all readily accessible show people walking the streets or entering establishments.  Most of these pictures seem harmless, but there are a few that show men walking into adult-themed bookstores, or women laying out sunbathing.  Had these people known that they would be displayed to the world, they may have changed their plans for that particular day, and surely some of them would have never consented to these images being shown.  While there are some obvious benefits to Street View, if even one person is offended by the content of the images then there is reason for concern of the ethicality of the tool.  Some may argue that the pictures are taken from a public place, and would be visible to anyone who happened to be traveling through the area.  While this is compelling, one must also consider the fact that the people photographed may not have had a problem with being seen by the general public in small numbers, but would object to being seen by the millions of people that use Google.  &lt;br /&gt;
There are many questions that can be raised about Street View regarding individual's privacy rights. However, none break any actual laws since all pictures are taken in public places. Does that make it ok though? Is it ethical? If you accidentally caught changing infront of the shower by Google Street View photographers should they remove the photo? Since it was obviously not their intent to take a picture of you naked it may be hard to hold them accountable. However, it would be in good ethical 'taste' to remove the pictures if so requested, eventhough it would not be required by law.&lt;br /&gt;
It's not just mapping on a street level that have ethical implications. Mapping technologies on a larger scale bring up other ethical issues. While being able to view satalite imagery may make it easier for you to find a place of business, it could also aid robbers in researching their next robbery victim. It could even help terrorists plan their next attack on a major landmark without even requiring them to visit their target. Satalite imagery could have a huge impact on national security. Should access to such information be restricted? and to who's laws should they conform to? This all depends on who has ownership of the information. If a Russian satalite is sailing over the United States and takes pictures of the White House they should be allowed to do whatever they want with those images, unless of course, they obtained them by breaking some law. This obviously has great implications if such information falls into the wrong hands, but, ethically, you can't deny or restrict someone use to something that is rightfully and legally theirs. The access to such information can not ethically be restricted, but perhaps the ways the information is obtained could.&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
===Relevant External Links:===&lt;br /&gt;
* [http://www.nytimes.com/2007/06/01/technology/01private.html Google Zooms In Too Close for Some (New York Times)] &lt;br /&gt;
* [http://www.boingboing.net/2007/06/05/google_street_view_a.html Public Opinion on Google Street View (Boing Boing)]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1730</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1730"/>
		<updated>2007-07-17T02:59:20Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Discussion Questions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as originally a way of allowing many projects to share source code under a unifying license. In simple terms, a project licensed with the GPL can be freely distributed and charged for, but any and all distribution must provide the source code to the consumer as well.  Also, according to the GPL, any work which uses code licensed by the GPL must license itself with the GPL.  It ensures that any software that was derived from open source remains available to the general public and freely distributable.&lt;br /&gt;
&lt;br /&gt;
* GPL - Version 1.0, February 1989&lt;br /&gt;
** To guarantee the freedoms to share and change free software.&lt;br /&gt;
** To make sure the software is free for all its users.&lt;br /&gt;
* GPL - Version 2.0, June 1991&lt;br /&gt;
** Further restricted rights from Version 1.0&lt;br /&gt;
** Updated to cover distribution of the program or programs as a whole.&lt;br /&gt;
** Linux kernel released under this license version&lt;br /&gt;
* GPL - Version 3.0, January 2006&lt;br /&gt;
** Further restricted rights from Version 2.0&lt;br /&gt;
** Updated to the cohort the ability to make changes to software and to compel for changes to be distributed so everyone benefits from the intellectual energy used to make changes.&lt;br /&gt;
** Main purpose, the abolition of DRM as a social practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
'''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
In general GPL software will impact certain groups, companies, or organizations differently and others in the same manner. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
! Impact On:&lt;br /&gt;
! Positive:&lt;br /&gt;
! Negative:&lt;br /&gt;
|- &lt;br /&gt;
| Personal Software Users&lt;br /&gt;
| The reduced monetary cost to acquire and use of software to achieve a personal task or action. No need to hack a commercial licensed product if a free version is available and easy to use. &lt;br /&gt;
| The learning curve and time to evaluate the software and its stability. In most cases GPL software lack proper documentation or specific key features. Although we can look at the code, we may be ignorant to the intentions of the programs and the community that created it.&lt;br /&gt;
|-&lt;br /&gt;
| Developers - Open Source&lt;br /&gt;
| To encourage evolution of software without having to re-invent the wheel. To continue and encourage the open source movement. &lt;br /&gt;
| An unwelcome change of a supporting program feature will generate chatter and distractions and delays from the ultimate goals of the developed system. A breach of commercial copyright laws by the application or supporting programs.&lt;br /&gt;
|-&lt;br /&gt;
| Developers – Commercial&lt;br /&gt;
| Developer can investigate and analyze already used and solved approaches to a problem and their core issues. Temptations caused by cost and times lines constraints may lead to illegal use of GPL code in commercial systems.&lt;br /&gt;
| Alternative free version of application is already available and free to users meaning that creating similar commercial version of the program will have to achieve higher appeal to justify its cost.&lt;br /&gt;
|-&lt;br /&gt;
| Commercial Software Companies&lt;br /&gt;
| Companies may be able to replace commercial software with open source counterparts to save money and increase profits. A good example of this is replacing their internal bug tracking system from a costly commercial one to bugzilla.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Non-profit organizations&lt;br /&gt;
| A community may be experienced and willing to provide a good solution or product to keep the operating cost down.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Government&lt;br /&gt;
| The Government may be able to replace commercial software with open source counterparts to save money. Encourage others to use GLP software. &lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Education and Research&lt;br /&gt;
| A community may be experienced and willing to provide guidance for students and researchers to analyze and learn how to solve certain types of problems or tasks.&lt;br /&gt;
| Negative impact:  The student or researcher will have to spend extra time learning and understanding a developed strategy of the program or source code is poorly written and no documentation is available for it.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
The main ethical issue with a license requiring the acceptance of the most recent version is that it forces the user to sign a contract which has not been written yet.  While the user could agree with the current version, a future version may change in such a fashion as to restrict the liberties of the user beyond what they would agree to.  This setup provides a large amount of leverage and power to the writers of the new versions of the license because they can force a huge tree of people into new agreements.  If a small, but widely used section of code was licensed under the GPL and the new version required additional profit restrictions, it would affect every project which used that code, as well as the projects which used those projects ect.  At the same time, if the license is changed in such a way that it benefits the users then that too can affect a large group.  The main ethical issue is the amount of power given to the writers of the license and how it is used.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
'''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;br /&gt;
&lt;br /&gt;
According to the patent sharing/protection agreement, Microsoft will collaborate Novell to support SuSe Linux as an alternative deployment platform to Windows. The partnership is said to make it easier for users to run both Windows and Linux-based systems and according to Microsoft CEO, Steve Ballmer, is said to &amp;quot;bridge the divide between open-source and proprietary source software&amp;quot; [http://news.com.com/Microsoft+makes+Linux+pact+with+Novell/2100-1016_3-6132119.html Microsoft make Linux pact with Novell.]&lt;br /&gt;
&lt;br /&gt;
Although the agreement is beneficial to both companies and its customers, it does raise some ethical concerns. Novell's open source software is under the GPL license which requires software to be distributed and modified freely but under the Microsoft/Novell agreement a royalty is being paid.&lt;br /&gt;
In another sense it almost seems like Microsoft has bought out Novell. Although sources say the agreement won't affect [http://news.com.com/Novell+sues+Microsoft+for+sinking+WordPerfect/2100-1012_3-5450285.html Novell's antitrust suit against Microsoft], it is somewhat hard to believe that two companies collaborating together would be suing one another. Infact, under the agreement Microsoft promised not to file patent suits against developers creating code for SuSe. Perhaps Microsoft hopes this will encourage Novell to drop their suit.&lt;br /&gt;
&lt;br /&gt;
Another ethical issues arising out of the agreement is that of loyalty, or for that matter, lack there of. The open source community has never been fond of Microsoft and Novell is build on software developed by the open source community. This has angered a large part of the open source community and [http://techp.org/petition/show/1 &amp;quot;in short, now that Novell has chosen not to hang together with the Free Software community, they've chosen not to do so with them.&amp;quot;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' Main Links '''&lt;br /&gt;
* [http://www.gnu.org gnu.org]&lt;br /&gt;
* [http://www.opensource.org opensource.org]&lt;br /&gt;
* [http://www.fsf.org/ FreeSoftwareFoundation.org]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1727</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1727"/>
		<updated>2007-07-16T16:39:27Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as originally a way of allowing many projects to share source code under a unifying license. In simple terms, a project licensed with the GPL can be freely distributed and charged for, but any and all distribution must provide the source code to the consumer as well.  Also, according to the GPL, any work which uses code licensed by the GPL must license itself with the GPL.  It ensures that any software that was derived from open source remains available to the general public and freely distributable.&lt;br /&gt;
&lt;br /&gt;
* GPL - Version 1.0, February 1989&lt;br /&gt;
** To guarantee the freedoms to share and change free software.&lt;br /&gt;
** To make sure the software is free for all its users.&lt;br /&gt;
* GPL - Version 2.0, June 1991&lt;br /&gt;
** Further restricted rights from Version 1.0&lt;br /&gt;
** Updated to cover distribution of the program or programs as a whole.&lt;br /&gt;
** Linux kernel released under this license version&lt;br /&gt;
* GPL - Version 3.0, January 2006&lt;br /&gt;
** Further restricted rights from Version 2.0&lt;br /&gt;
** Updated to the cohort the ability to make changes to software and to compel for changes to be distributed so everyone benefits from the intellectual energy used to make changes.&lt;br /&gt;
** Main purpose, the abolition of DRM as a social practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
'''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
In general GPL software will impact certain groups, companies, or organizations differently and others in the same manner. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
! Impact On:&lt;br /&gt;
! Positive:&lt;br /&gt;
! Negative:&lt;br /&gt;
|- &lt;br /&gt;
| Personal Software Users&lt;br /&gt;
| The reduced monetary cost to acquire and use of software to achieve a personal task or action. No need to hack a commercial licensed product if a free version is available and easy to use. &lt;br /&gt;
| The learning curve and time to evaluate the software and its stability. In most cases GPL software lack proper documentation or specific key features. Although we can look at the code, we may be ignorant to the intentions of the programs and the community that created it.&lt;br /&gt;
|-&lt;br /&gt;
| Developers - Open Source&lt;br /&gt;
| To encourage evolution of software without having to re-invent the wheel. To continue and encourage the open source movement. &lt;br /&gt;
| An unwelcome change of a supporting program feature will generate chatter and distractions and delays from the ultimate goals of the developed system. A breach of commercial copyright laws by the application or supporting programs.&lt;br /&gt;
|-&lt;br /&gt;
| Developers – Commercial&lt;br /&gt;
| Developer can investigate and analyze already used and solved approaches to a problem and their core issues. Temptations caused by cost and times lines constraints may lead to illegal use of GPL code in commercial systems.&lt;br /&gt;
| Alternative free version of application is already available and free to users meaning that creating similar commercial version of the program will have to achieve higher appeal to justify its cost.&lt;br /&gt;
|-&lt;br /&gt;
| Commercial Software Companies&lt;br /&gt;
| Companies may be able to replace commercial software with open source counterparts to save money and increase profits. A good example of this is replacing their internal bug tracking system from a costly commercial one to bugzilla.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Non-profit organizations&lt;br /&gt;
| A community may be experienced and willing to provide a good solution or product to keep the operating cost down.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Government&lt;br /&gt;
| The Government may be able to replace commercial software with open source counterparts to save money. Encourage others to use GLP software. &lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Education and Research&lt;br /&gt;
| A community may be experienced and willing to provide guidance for students and researchers to analyze and learn how to solve certain types of problems or tasks.&lt;br /&gt;
| Negative impact:  The student or researcher will have to spend extra time learning and understanding a developed strategy of the program or source code is poorly written and no documentation is available for it.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
The main ethical issue with a license requiring the acceptance of the most recent version is that it forces the user to sign a contract which has not been written yet.  While the user could agree with the current version, a future version may change in such a fashion as to restrict the liberties of the user beyond what they would agree to.  This setup provides a large amount of leverage and power to the writers of the new versions of the license because they can force a huge tree of people into new agreements.  If a small, but widely used section of code was licensed under the GPL and the new version required additional profit restrictions, it would affect every project which used that code, as well as the projects which used those projects ect.  At the same time, if the license is changed in such a way that it benefits the users then that too can affect a large group.  The main ethical issue is the amount of power given to the writers of the license and how it is used.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
'''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;br /&gt;
&lt;br /&gt;
According to the patent sharing/protection agreement, Microsoft will collaborate Novell to support SuSe Linux as an alternative deployment platform to Windows. The partnership is said to make it easier for users to run both Windows and Linux-based systems and according to Microsoft CEO, Steve Ballmer, is said to &amp;quot;bridge the divide between open-source and proprietary source software&amp;quot; [http://news.com.com/Microsoft+makes+Linux+pact+with+Novell/2100-1016_3-6132119.html Microsoft make Linux pact with Novell.]&lt;br /&gt;
&lt;br /&gt;
Although the agreement is beneficial to both companies and its customers, it does raise some ethical concerns. Novell's open source software is under the GPL license which requires software to be distributed and modified freely but under the Microsoft/Novell agreement a royalty is being paid.&lt;br /&gt;
In another sense it almost seems like Microsoft has bought out Novell. Although sources say the agreement won't affect [http://news.com.com/Novell+sues+Microsoft+for+sinking+WordPerfect/2100-1012_3-5450285.html Novell's antitrust suit against Microsoft], it is somewhat hard to believe that two companies collaborating together would be suing one another. Infact, under the agreement Microsoft promised not to file patent suits against developers creating code for SuSe. Perhaps Microsoft hopes this will encourage Novell to drop their suit.&lt;br /&gt;
&lt;br /&gt;
Another ethical issues arising out of the agreement is that of loyalty, or for that matter, lack there of. The open source community has never been fond of Microsoft and Novell is build on software developed by the open source community. This has angered a large part of the open source community and [http://techp.org/petition/show/1 &amp;quot;in short, now that Novell has chosen not to hang together with the Free Software community, [they've] chosen not to do so with [them].&amp;quot;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
''' Main Links '''&lt;br /&gt;
* [http://www.gnu.org gnu.org]&lt;br /&gt;
* [http://www.opensource.org opensource.org]&lt;br /&gt;
* [http://www.fsf.org/ FreeSoftwareFoundation.org]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1726</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1726"/>
		<updated>2007-07-16T16:36:00Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Discussion Questions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as originally a way of allowing many projects to share source code under a unifying license. In simple terms, a project licensed with the GPL can be freely distributed and charged for, but any and all distribution must provide the source code to the consumer as well.  Also, according to the GPL, any work which uses code licensed by the GPL must license itself with the GPL.  It ensures that any software that was derived from open source remains available to the general public and freely distributable.&lt;br /&gt;
&lt;br /&gt;
* GPL - Version 1.0, February 1989&lt;br /&gt;
** To guarantee the freedoms to share and change free software.&lt;br /&gt;
** To make sure the software is free for all its users.&lt;br /&gt;
* GPL - Version 2.0, June 1991&lt;br /&gt;
** Further restricted rights from Version 1.0&lt;br /&gt;
** Updated to cover distribution of the program or programs as a whole.&lt;br /&gt;
** Linux kernel released under this license version&lt;br /&gt;
* GPL - Version 3.0, January 2006&lt;br /&gt;
** Further restricted rights from Version 2.0&lt;br /&gt;
** Updated to the cohort the ability to make changes to software and to compel for changes to be distributed so everyone benefits from the intellectual energy used to make changes.&lt;br /&gt;
** Main purpose, the abolition of DRM as a social practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
'''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
In general GPL software will impact certain groups, companies, or organizations differently and others in the same manner. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
! Impact On:&lt;br /&gt;
! Positive:&lt;br /&gt;
! Negative:&lt;br /&gt;
|- &lt;br /&gt;
| Personal Software Users&lt;br /&gt;
| The reduced monetary cost to acquire and use of software to achieve a personal task or action. No need to hack a commercial licensed product if a free version is available and easy to use. &lt;br /&gt;
| The learning curve and time to evaluate the software and its stability. In most cases GPL software lack proper documentation or specific key features. Although we can look at the code, we may be ignorant to the intentions of the programs and the community that created it.&lt;br /&gt;
|-&lt;br /&gt;
| Developers - Open Source&lt;br /&gt;
| To encourage evolution of software without having to re-invent the wheel. To continue and encourage the open source movement. &lt;br /&gt;
| An unwelcome change of a supporting program feature will generate chatter and distractions and delays from the ultimate goals of the developed system. A breach of commercial copyright laws by the application or supporting programs.&lt;br /&gt;
|-&lt;br /&gt;
| Developers – Commercial&lt;br /&gt;
| Developer can investigate and analyze already used and solved approaches to a problem and their core issues. Temptations caused by cost and times lines constraints may lead to illegal use of GPL code in commercial systems.&lt;br /&gt;
| Alternative free version of application is already available and free to users meaning that creating similar commercial version of the program will have to achieve higher appeal to justify its cost.&lt;br /&gt;
|-&lt;br /&gt;
| Commercial Software Companies&lt;br /&gt;
| Companies may be able to replace commercial software with open source counterparts to save money and increase profits. A good example of this is replacing their internal bug tracking system from a costly commercial one to bugzilla.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Non-profit organizations&lt;br /&gt;
| A community may be experienced and willing to provide a good solution or product to keep the operating cost down.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Government&lt;br /&gt;
| The Government may be able to replace commercial software with open source counterparts to save money. Encourage others to use GLP software. &lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Education and Research&lt;br /&gt;
| A community may be experienced and willing to provide guidance for students and researchers to analyze and learn how to solve certain types of problems or tasks.&lt;br /&gt;
| Negative impact:  The student or researcher will have to spend extra time learning and understanding a developed strategy of the program or source code is poorly written and no documentation is available for it.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
The main ethical issue with a license requiring the acceptance of the most recent version is that it forces the user to sign a contract which has not been written yet.  While the user could agree with the current version, a future version may change in such a fashion as to restrict the liberties of the user beyond what they would agree to.  This setup provides a large amount of leverage and power to the writers of the new versions of the license because they can force a huge tree of people into new agreements.  If a small, but widely used section of code was licensed under the GPL and the new version required additional profit restrictions, it would affect every project which used that code, as well as the projects which used those projects ect.  At the same time, if the license is changed in such a way that it benefits the users then that too can affect a large group.  The main ethical issue is the amount of power given to the writers of the license and how it is used.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
'''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;br /&gt;
&lt;br /&gt;
According to the patent sharing/protection agreement, Microsoft will collaborate Novell to support SuSe Linux as an alternative deployment platform to Windows. The partnership is said to make it easier for users to run both Windows and Linux-based systems and according to Microsoft CEO, Steve Ballmer, is said to &amp;quot;bridge the divide between open-source and proprietary source software&amp;quot; [http://news.com.com/Microsoft+makes+Linux+pact+with+Novell/2100-1016_3-6132119.html Microsoft make Linux pact with Novell.]&lt;br /&gt;
&lt;br /&gt;
Although the agreement is beneficial to both companies and its customers, it does raise some ethical concerns. Novell's open source software is under the GPL license which requires software to be distributed and modified freely but under the Microsoft/Novell agreement a royalty is being paid.&lt;br /&gt;
In another sense it almost seems like Microsoft has bought out Novell. Although sources say the agreement won't affect [http://news.com.com/Novell+sues+Microsoft+for+sinking+WordPerfect/2100-1012_3-5450285.html Novell's antitrust suit against Microsoft], it is somewhat hard to believe that two companies collaborating together would be suing one another. Infact, under the agreement Microsoft promised not to file patent suits against developers creating code for SuSe. Perhaps Microsoft hopes this will encourage Novell to drop their suit.&lt;br /&gt;
&lt;br /&gt;
Another ethical issues arising out of the agreement is that of loyalty, or for that matter, lack there of. The open source community has never been fond of Microsoft and Novell is build on software developed by the open source community. This has angered a large part of the open source community and [http://techp.org/petition/show/1 &amp;quot;in short, now that Novell has chosen not to hang together with the Free Software community, [they've] chosen not to do so with [them].&amp;quot;]&lt;br /&gt;
&lt;br /&gt;
''' Main Links '''&lt;br /&gt;
* [http://www.gnu.org gnu.org]&lt;br /&gt;
* [http://www.opensource.org opensource.org]&lt;br /&gt;
* [http://www.fsf.org/ FreeSoftwareFoundation.org]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1725</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1725"/>
		<updated>2007-07-16T16:34:28Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Discussion Questions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as originally a way of allowing many projects to share source code under a unifying license. In simple terms, a project licensed with the GPL can be freely distributed and charged for, but any and all distribution must provide the source code to the consumer as well.  Also, according to the GPL, any work which uses code licensed by the GPL must license itself with the GPL.  It ensures that any software that was derived from open source remains available to the general public and freely distributable.&lt;br /&gt;
&lt;br /&gt;
* GPL - Version 1.0, February 1989&lt;br /&gt;
** To guarantee the freedoms to share and change free software.&lt;br /&gt;
** To make sure the software is free for all its users.&lt;br /&gt;
* GPL - Version 2.0, June 1991&lt;br /&gt;
** Further restricted rights from Version 1.0&lt;br /&gt;
** Updated to cover distribution of the program or programs as a whole.&lt;br /&gt;
** Linux kernel released under this license version&lt;br /&gt;
* GPL - Version 3.0, January 2006&lt;br /&gt;
** Further restricted rights from Version 2.0&lt;br /&gt;
** Updated to the cohort the ability to make changes to software and to compel for changes to be distributed so everyone benefits from the intellectual energy used to make changes.&lt;br /&gt;
** Main purpose, the abolition of DRM as a social practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
'''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
In general GPL software will impact certain groups, companies, or organizations differently and others in the same manner. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
! Impact On:&lt;br /&gt;
! Positive:&lt;br /&gt;
! Negative:&lt;br /&gt;
|- &lt;br /&gt;
| Personal Software Users&lt;br /&gt;
| The reduced monetary cost to acquire and use of software to achieve a personal task or action. No need to hack a commercial licensed product if a free version is available and easy to use. &lt;br /&gt;
| The learning curve and time to evaluate the software and its stability. In most cases GPL software lack proper documentation or specific key features. Although we can look at the code, we may be ignorant to the intentions of the programs and the community that created it.&lt;br /&gt;
|-&lt;br /&gt;
| Developers - Open Source&lt;br /&gt;
| To encourage evolution of software without having to re-invent the wheel. To continue and encourage the open source movement. &lt;br /&gt;
| An unwelcome change of a supporting program feature will generate chatter and distractions and delays from the ultimate goals of the developed system. A breach of commercial copyright laws by the application or supporting programs.&lt;br /&gt;
|-&lt;br /&gt;
| Developers – Commercial&lt;br /&gt;
| Developer can investigate and analyze already used and solved approaches to a problem and their core issues. Temptations caused by cost and times lines constraints may lead to illegal use of GPL code in commercial systems.&lt;br /&gt;
| Alternative free version of application is already available and free to users meaning that creating similar commercial version of the program will have to achieve higher appeal to justify its cost.&lt;br /&gt;
|-&lt;br /&gt;
| Commercial Software Companies&lt;br /&gt;
| Companies may be able to replace commercial software with open source counterparts to save money and increase profits. A good example of this is replacing their internal bug tracking system from a costly commercial one to bugzilla.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Non-profit organizations&lt;br /&gt;
| A community may be experienced and willing to provide a good solution or product to keep the operating cost down.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Government&lt;br /&gt;
| The Government may be able to replace commercial software with open source counterparts to save money. Encourage others to use GLP software. &lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Education and Research&lt;br /&gt;
| A community may be experienced and willing to provide guidance for students and researchers to analyze and learn how to solve certain types of problems or tasks.&lt;br /&gt;
| Negative impact:  The student or researcher will have to spend extra time learning and understanding a developed strategy of the program or source code is poorly written and no documentation is available for it.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
The main ethical issue with a license requiring the acceptance of the most recent version is that it forces the user to sign a contract which has not been written yet.  While the user could agree with the current version, a future version may change in such a fashion as to restrict the liberties of the user beyond what they would agree to.  This setup provides a large amount of leverage and power to the writers of the new versions of the license because they can force a huge tree of people into new agreements.  If a small, but widely used section of code was licensed under the GPL and the new version required additional profit restrictions, it would affect every project which used that code, as well as the projects which used those projects ect.  At the same time, if the license is changed in such a way that it benefits the users then that too can affect a large group.  The main ethical issue is the amount of power given to the writers of the license and how it is used.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
'''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;br /&gt;
   According to the patent sharing/protection agreement, Microsoft will collaborate Novell to support SuSe Linux as an alternative deployment platform to Windows. The partnership is said to make it easier for users to run both Windows and Linux-based systems and according to Microsoft CEO, Steve Ballmer, is said to &amp;quot;bridge the divide between open-source and proprietary source software&amp;quot; [http://news.com.com/Microsoft+makes+Linux+pact+with+Novell/2100-1016_3-6132119.html Microsoft make Linux pact with Novell.]&lt;br /&gt;
   Although the agreement is beneficial to both companies and its customers, it does raise some ethical concerns. Novell's open source software is under the GPL license which requires software to be distributed and modified freely but under the Microsoft/Novell agreement a royalty is being paid.&lt;br /&gt;
In another sense it almost seems like Microsoft has bought out Novell. Although sources say the agreement won't affect [http://news.com.com/Novell+sues+Microsoft+for+sinking+WordPerfect/2100-1012_3-5450285.html Novell's antitrust suit against Microsoft], it is somewhat hard to believe that two companies collaborating together would be suing one another. Infact, under the agreement Microsoft promised not to file patent suits against developers creating code for SuSe. Perhaps Microsoft hopes this will encourage Novell to drop their suit.&lt;br /&gt;
   Another ethical issues arising out of the agreement is that of loyalty, or for that matter, lack there of. The open source community has never been fond of Microsoft and Novell is build on software developed by the open source community. This has angered a large part of the open source community and [http://techp.org/petition/show/1 &amp;quot;in short, now that Novell has chosen not to hang together with the Free Software community, [they've] chosen not to do so with [them].&amp;quot;]&lt;br /&gt;
&lt;br /&gt;
''' Main Links '''&lt;br /&gt;
* [http://www.gnu.org gnu.org]&lt;br /&gt;
* [http://www.opensource.org opensource.org]&lt;br /&gt;
* [http://www.fsf.org/ FreeSoftwareFoundation.org]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1724</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1724"/>
		<updated>2007-07-16T16:33:18Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Discussion Questions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as originally a way of allowing many projects to share source code under a unifying license. In simple terms, a project licensed with the GPL can be freely distributed and charged for, but any and all distribution must provide the source code to the consumer as well.  Also, according to the GPL, any work which uses code licensed by the GPL must license itself with the GPL.  It ensures that any software that was derived from open source remains available to the general public and freely distributable.&lt;br /&gt;
&lt;br /&gt;
* GPL - Version 1.0, February 1989&lt;br /&gt;
** To guarantee the freedoms to share and change free software.&lt;br /&gt;
** To make sure the software is free for all its users.&lt;br /&gt;
* GPL - Version 2.0, June 1991&lt;br /&gt;
** Further restricted rights from Version 1.0&lt;br /&gt;
** Updated to cover distribution of the program or programs as a whole.&lt;br /&gt;
** Linux kernel released under this license version&lt;br /&gt;
* GPL - Version 3.0, January 2006&lt;br /&gt;
** Further restricted rights from Version 2.0&lt;br /&gt;
** Updated to the cohort the ability to make changes to software and to compel for changes to be distributed so everyone benefits from the intellectual energy used to make changes.&lt;br /&gt;
** Main purpose, the abolition of DRM as a social practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
'''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
In general GPL software will impact certain groups, companies, or organizations differently and others in the same manner. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
! Impact On:&lt;br /&gt;
! Positive:&lt;br /&gt;
! Negative:&lt;br /&gt;
|- &lt;br /&gt;
| Personal Software Users&lt;br /&gt;
| The reduced monetary cost to acquire and use of software to achieve a personal task or action. No need to hack a commercial licensed product if a free version is available and easy to use. &lt;br /&gt;
| The learning curve and time to evaluate the software and its stability. In most cases GPL software lack proper documentation or specific key features. Although we can look at the code, we may be ignorant to the intentions of the programs and the community that created it.&lt;br /&gt;
|-&lt;br /&gt;
| Developers - Open Source&lt;br /&gt;
| To encourage evolution of software without having to re-invent the wheel. To continue and encourage the open source movement. &lt;br /&gt;
| An unwelcome change of a supporting program feature will generate chatter and distractions and delays from the ultimate goals of the developed system. A breach of commercial copyright laws by the application or supporting programs.&lt;br /&gt;
|-&lt;br /&gt;
| Developers – Commercial&lt;br /&gt;
| Developer can investigate and analyze already used and solved approaches to a problem and their core issues. Temptations caused by cost and times lines constraints may lead to illegal use of GPL code in commercial systems.&lt;br /&gt;
| Alternative free version of application is already available and free to users meaning that creating similar commercial version of the program will have to achieve higher appeal to justify its cost.&lt;br /&gt;
|-&lt;br /&gt;
| Commercial Software Companies&lt;br /&gt;
| Companies may be able to replace commercial software with open source counterparts to save money and increase profits. A good example of this is replacing their internal bug tracking system from a costly commercial one to bugzilla.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Non-profit organizations&lt;br /&gt;
| A community may be experienced and willing to provide a good solution or product to keep the operating cost down.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Government&lt;br /&gt;
| The Government may be able to replace commercial software with open source counterparts to save money. Encourage others to use GLP software. &lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Education and Research&lt;br /&gt;
| A community may be experienced and willing to provide guidance for students and researchers to analyze and learn how to solve certain types of problems or tasks.&lt;br /&gt;
| Negative impact:  The student or researcher will have to spend extra time learning and understanding a developed strategy of the program or source code is poorly written and no documentation is available for it.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
The main ethical issue with a license requiring the acceptance of the most recent version is that it forces the user to sign a contract which has not been written yet.  While the user could agree with the current version, a future version may change in such a fashion as to restrict the liberties of the user beyond what they would agree to.  This setup provides a large amount of leverage and power to the writers of the new versions of the license because they can force a huge tree of people into new agreements.  If a small, but widely used section of code was licensed under the GPL and the new version required additional profit restrictions, it would affect every project which used that code, as well as the projects which used those projects ect.  At the same time, if the license is changed in such a way that it benefits the users then that too can affect a large group.  The main ethical issue is the amount of power given to the writers of the license and how it is used.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
'''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;br /&gt;
According to the patent sharing/protection agreement, Microsoft will collaborate Novell to support SuSe Linux as an alternative deployment platform to Windows. The partnership is said to make it easier for users to run both Windows and Linux-based systems and according to Microsoft CEO, Steve Ballmer, is said to &amp;quot;bridge the divide between open-source and proprietary source software&amp;quot; [http://news.com.com/Microsoft+makes+Linux+pact+with+Novell/2100-1016_3-6132119.html Microsoft make Linux pact with Novell.]&lt;br /&gt;
Although the agreement is beneficial to both companies and its customers, it does raise some ethical concerns. Novell's open source software is under the GPL license which requires software to be distributed and modified freely but under the Microsoft/Novell agreement a royalty is being paid.&lt;br /&gt;
In another sense it almost seems like Microsoft has bought out Novell. Although sources say the agreement won't affect [http://news.com.com/Novell+sues+Microsoft+for+sinking+WordPerfect/2100-1012_3-5450285.html Novell's antitrust suit against Microsoft], it is somewhat hard to believe that two companies collaborating together would be suing one another. Infact, under the agreement Microsoft promised not to file patent suits against developers creating code for SuSe. Perhaps Microsoft hopes this will encourage Novell to drop their suit.&lt;br /&gt;
Another ethical issues arising out of the agreement is that of loyalty, or for that matter, lack there of. The open source community has never been fond of Microsoft and Novell is build on software developed by the open source community. This has angered a large part of the open source community and [http://techp.org/petition/show/1 &amp;quot;in short, now that Novell has chosen not to hang together with the Free Software community, [they've] chosen not to do so with [them].&amp;quot;]&lt;br /&gt;
&lt;br /&gt;
''' Main Links '''&lt;br /&gt;
* [http://www.gnu.org gnu.org]&lt;br /&gt;
* [http://www.opensource.org opensource.org]&lt;br /&gt;
* [http://www.fsf.org/ FreeSoftwareFoundation.org]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1723</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1723"/>
		<updated>2007-07-16T16:33:00Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Discussion Questions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as originally a way of allowing many projects to share source code under a unifying license. In simple terms, a project licensed with the GPL can be freely distributed and charged for, but any and all distribution must provide the source code to the consumer as well.  Also, according to the GPL, any work which uses code licensed by the GPL must license itself with the GPL.  It ensures that any software that was derived from open source remains available to the general public and freely distributable.&lt;br /&gt;
&lt;br /&gt;
* GPL - Version 1.0, February 1989&lt;br /&gt;
** To guarantee the freedoms to share and change free software.&lt;br /&gt;
** To make sure the software is free for all its users.&lt;br /&gt;
* GPL - Version 2.0, June 1991&lt;br /&gt;
** Further restricted rights from Version 1.0&lt;br /&gt;
** Updated to cover distribution of the program or programs as a whole.&lt;br /&gt;
** Linux kernel released under this license version&lt;br /&gt;
* GPL - Version 3.0, January 2006&lt;br /&gt;
** Further restricted rights from Version 2.0&lt;br /&gt;
** Updated to the cohort the ability to make changes to software and to compel for changes to be distributed so everyone benefits from the intellectual energy used to make changes.&lt;br /&gt;
** Main purpose, the abolition of DRM as a social practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
'''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
In general GPL software will impact certain groups, companies, or organizations differently and others in the same manner. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
! Impact On:&lt;br /&gt;
! Positive:&lt;br /&gt;
! Negative:&lt;br /&gt;
|- &lt;br /&gt;
| Personal Software Users&lt;br /&gt;
| The reduced monetary cost to acquire and use of software to achieve a personal task or action. No need to hack a commercial licensed product if a free version is available and easy to use. &lt;br /&gt;
| The learning curve and time to evaluate the software and its stability. In most cases GPL software lack proper documentation or specific key features. Although we can look at the code, we may be ignorant to the intentions of the programs and the community that created it.&lt;br /&gt;
|-&lt;br /&gt;
| Developers - Open Source&lt;br /&gt;
| To encourage evolution of software without having to re-invent the wheel. To continue and encourage the open source movement. &lt;br /&gt;
| An unwelcome change of a supporting program feature will generate chatter and distractions and delays from the ultimate goals of the developed system. A breach of commercial copyright laws by the application or supporting programs.&lt;br /&gt;
|-&lt;br /&gt;
| Developers – Commercial&lt;br /&gt;
| Developer can investigate and analyze already used and solved approaches to a problem and their core issues. Temptations caused by cost and times lines constraints may lead to illegal use of GPL code in commercial systems.&lt;br /&gt;
| Alternative free version of application is already available and free to users meaning that creating similar commercial version of the program will have to achieve higher appeal to justify its cost.&lt;br /&gt;
|-&lt;br /&gt;
| Commercial Software Companies&lt;br /&gt;
| Companies may be able to replace commercial software with open source counterparts to save money and increase profits. A good example of this is replacing their internal bug tracking system from a costly commercial one to bugzilla.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Non-profit organizations&lt;br /&gt;
| A community may be experienced and willing to provide a good solution or product to keep the operating cost down.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Government&lt;br /&gt;
| The Government may be able to replace commercial software with open source counterparts to save money. Encourage others to use GLP software. &lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Education and Research&lt;br /&gt;
| A community may be experienced and willing to provide guidance for students and researchers to analyze and learn how to solve certain types of problems or tasks.&lt;br /&gt;
| Negative impact:  The student or researcher will have to spend extra time learning and understanding a developed strategy of the program or source code is poorly written and no documentation is available for it.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
The main ethical issue with a license requiring the acceptance of the most recent version is that it forces the user to sign a contract which has not been written yet.  While the user could agree with the current version, a future version may change in such a fashion as to restrict the liberties of the user beyond what they would agree to.  This setup provides a large amount of leverage and power to the writers of the new versions of the license because they can force a huge tree of people into new agreements.  If a small, but widely used section of code was licensed under the GPL and the new version required additional profit restrictions, it would affect every project which used that code, as well as the projects which used those projects ect.  At the same time, if the license is changed in such a way that it benefits the users then that too can affect a large group.  The main ethical issue is the amount of power given to the writers of the license and how it is used.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
'''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;br /&gt;
According to the patent sharing/protection agreement, Microsoft will collaborate Novell to support SuSe Linux as an alternative deployment platform to Windows. The partnership is said to make it easier for users to run both Windows and Linux-based systems and according to Microsoft CEO, Steve Ballmer, is said to &amp;quot;bridge the divide between open-source and proprietary source software&amp;quot; [http://news.com.com/Microsoft+makes+Linux+pact+with+Novell/2100-1016_3-6132119.html Microsoft make Linux pact with Novell.]&lt;br /&gt;
Although the agreement is beneficial to both companies and its customers, it does raise some ethical concerns. Novell's open source software is under the GPL license which requires software to be distributed and modified freely but under the Microsoft/Novell agreement a royalty is being paid.&lt;br /&gt;
In another sense it almost seems like Microsoft has bought out Novell. Although sources say the agreement won't affect [http://news.com.com/Novell+sues+Microsoft+for+sinking+WordPerfect/2100-1012_3-5450285.html Novell's antitrust suit against Microsoft], it is somewhat hard to believe that two companies collaborating together would be suing one another. Infact, under the agreement Microsoft promised not to file patent suits against developers creating code for SuSe. Perhaps Microsoft hopes this will encourage Novell to drop their suit.&lt;br /&gt;
Another ethical issues arising out of the agreement is that of loyalty, or for that matter, lack there of. The open source community has never been fond of Microsoft and Novell is build on software developed by the open source community. This has angered a large part of the open source community and [http://techp.org/petition/show/1]&amp;quot;in short, now that Novell has chosen not to hang together with the Free Software community, [they've] chosen not to do so with [them].&amp;quot;&lt;br /&gt;
&lt;br /&gt;
''' Main Links '''&lt;br /&gt;
* [http://www.gnu.org gnu.org]&lt;br /&gt;
* [http://www.opensource.org opensource.org]&lt;br /&gt;
* [http://www.fsf.org/ FreeSoftwareFoundation.org]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1722</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1722"/>
		<updated>2007-07-16T16:28:59Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Discussion Questions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as originally a way of allowing many projects to share source code under a unifying license. In simple terms, a project licensed with the GPL can be freely distributed and charged for, but any and all distribution must provide the source code to the consumer as well.  Also, according to the GPL, any work which uses code licensed by the GPL must license itself with the GPL.  It ensures that any software that was derived from open source remains available to the general public and freely distributable.&lt;br /&gt;
&lt;br /&gt;
* GPL - Version 1.0, February 1989&lt;br /&gt;
** To guarantee the freedoms to share and change free software.&lt;br /&gt;
** To make sure the software is free for all its users.&lt;br /&gt;
* GPL - Version 2.0, June 1991&lt;br /&gt;
** Further restricted rights from Version 1.0&lt;br /&gt;
** Updated to cover distribution of the program or programs as a whole.&lt;br /&gt;
** Linux kernel released under this license version&lt;br /&gt;
* GPL - Version 3.0, January 2006&lt;br /&gt;
** Further restricted rights from Version 2.0&lt;br /&gt;
** Updated to the cohort the ability to make changes to software and to compel for changes to be distributed so everyone benefits from the intellectual energy used to make changes.&lt;br /&gt;
** Main purpose, the abolition of DRM as a social practice.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
'''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
In general GPL software will impact certain groups, companies, or organizations differently and others in the same manner. &lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; cellspacing=&amp;quot;0&amp;quot; cellpadding=&amp;quot;5&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
! Impact On:&lt;br /&gt;
! Positive:&lt;br /&gt;
! Negative:&lt;br /&gt;
|- &lt;br /&gt;
| Personal Software Users&lt;br /&gt;
| The reduced monetary cost to acquire and use of software to achieve a personal task or action. No need to hack a commercial licensed product if a free version is available and easy to use. &lt;br /&gt;
| The learning curve and time to evaluate the software and its stability. In most cases GPL software lack proper documentation or specific key features. Although we can look at the code, we may be ignorant to the intentions of the programs and the community that created it.&lt;br /&gt;
|-&lt;br /&gt;
| Developers - Open Source&lt;br /&gt;
| To encourage evolution of software without having to re-invent the wheel. To continue and encourage the open source movement. &lt;br /&gt;
| An unwelcome change of a supporting program feature will generate chatter and distractions and delays from the ultimate goals of the developed system. A breach of commercial copyright laws by the application or supporting programs.&lt;br /&gt;
|-&lt;br /&gt;
| Developers – Commercial&lt;br /&gt;
| Developer can investigate and analyze already used and solved approaches to a problem and their core issues. Temptations caused by cost and times lines constraints may lead to illegal use of GPL code in commercial systems.&lt;br /&gt;
| Alternative free version of application is already available and free to users meaning that creating similar commercial version of the program will have to achieve higher appeal to justify its cost.&lt;br /&gt;
|-&lt;br /&gt;
| Commercial Software Companies&lt;br /&gt;
| Companies may be able to replace commercial software with open source counterparts to save money and increase profits. A good example of this is replacing their internal bug tracking system from a costly commercial one to bugzilla.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Non-profit organizations&lt;br /&gt;
| A community may be experienced and willing to provide a good solution or product to keep the operating cost down.&lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Government&lt;br /&gt;
| The Government may be able to replace commercial software with open source counterparts to save money. Encourage others to use GLP software. &lt;br /&gt;
| Replacing a commercial program may require the company to incur extra maintenance cost and need to hire an experienced administrator.&lt;br /&gt;
|-&lt;br /&gt;
| Education and Research&lt;br /&gt;
| A community may be experienced and willing to provide guidance for students and researchers to analyze and learn how to solve certain types of problems or tasks.&lt;br /&gt;
| Negative impact:  The student or researcher will have to spend extra time learning and understanding a developed strategy of the program or source code is poorly written and no documentation is available for it.&lt;br /&gt;
|-&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
The main ethical issue with a license requiring the acceptance of the most recent version is that it forces the user to sign a contract which has not been written yet.  While the user could agree with the current version, a future version may change in such a fashion as to restrict the liberties of the user beyond what they would agree to.  This setup provides a large amount of leverage and power to the writers of the new versions of the license because they can force a huge tree of people into new agreements.  If a small, but widely used section of code was licensed under the GPL and the new version required additional profit restrictions, it would affect every project which used that code, as well as the projects which used those projects ect.  At the same time, if the license is changed in such a way that it benefits the users then that too can affect a large group.  The main ethical issue is the amount of power given to the writers of the license and how it is used.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
'''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;br /&gt;
According to the patent sharing/protection agreement, Microsoft will collaborate Novell to support SuSe Linux as an alternative deployment platform to Windows. The partnership is said to make it easier for users to run both Windows and Linux-based systems and according to Microsoft CEO, Steve Ballmer, is said to &amp;quot;bridge the divide between open-source and proprietary source software&amp;quot; [http://news.com.com/Microsoft+makes+Linux+pact+with+Novell/2100-1016_3-6132119.html] Microsoft make Linux pact with Novell. &lt;br /&gt;
Although the agreement is beneficial to both companies and its customers, it does raise some ethical concerns. Novell's open source software is under the GPL license which requires software to be distributed and modified freely but under the Microsoft/Novell agreement a royalty is being paid.&lt;br /&gt;
In another sense it almost seems like Microsoft has bought out Novell. Although sources say the agreement won't affect [http://news.com.com/Novell+sues+Microsoft+for+sinking+WordPerfect/2100-1012_3-5450285.html]Novell's antitrust suit against Microsoft, it is somewhat hard to believe that two companies collaborating together would be suing one another. Infact, under the agreement Microsoft promised not to file patent suits against developers creating code for SuSe. Perhaps Microsoft hopes this will encourage Novell to drop their suit.&lt;br /&gt;
Another ethical issues arising out of the agreement is that of loyalty, or for that matter, lack there of. The open source community has never been fond of Microsoft and Novell is build on software developed by the open source community. This has angered a large part of the open source community and [http://techp.org/petition/show/1]&amp;quot;in short, now that Novell has chosen not to hang together with the Free Software community, [they've] chosen not to do so with [them].&amp;quot;&lt;br /&gt;
&lt;br /&gt;
''' Main Links '''&lt;br /&gt;
* [http://www.gnu.org gnu.org]&lt;br /&gt;
* [http://www.opensource.org opensource.org]&lt;br /&gt;
* [http://www.fsf.org/ FreeSoftwareFoundation.org]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1602</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1602"/>
		<updated>2007-07-13T00:16:27Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as originally a way of allowing many projects to share source code under a unifying license. It ensures that any software that was derived from open source remains available to the general public and freely distributable.&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
* '''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1601</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1601"/>
		<updated>2007-07-13T00:07:42Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as a way of allowing many projects to share source code under a unifying license. The GPL ensures that any software that was derived from open source remains free and guarantees freedom to share and change the software at the users will.&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
* '''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1600</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1600"/>
		<updated>2007-07-12T23:53:16Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* GNU General Public License */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as a way of allowing many projects to share source code under a unifying license. The GPL also ensures that any software that was derived from open source remains open source.&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
* '''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1599</id>
		<title>CSC 379:Week 2, Group 5</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_2,_Group_5&amp;diff=1599"/>
		<updated>2007-07-12T23:51:07Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=GNU General Public License=&lt;br /&gt;
&lt;br /&gt;
==Overview==&lt;br /&gt;
&lt;br /&gt;
The General Public License (GPL) was created in 1989 by Richard Stallman as a way of allowing many projects to share source code under a unifying license. The GPL also ensures that any open source software stays open source.&lt;br /&gt;
&lt;br /&gt;
==Discussion Questions==&lt;br /&gt;
&lt;br /&gt;
* '''What is the impact of GPL use?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''What are the ethical considerations for licenses like GPL that require their adoption if work licensed under it is incorporated into a parent work, with additional stipulations that include the acceptance of the most current version of the GPL license?'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''What ethical considerations are highlighted by the patent sharing/protection agreement between Microsoft and Novell?'''&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1432</id>
		<title>CSC 379:Week 1, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1432"/>
		<updated>2007-07-06T21:10:52Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* The Ethics of Defenses against Spam */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== The Ethics of Defenses against Spam ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''Blocking domains'''&lt;br /&gt;
** Domain Blocking allows specific users to be blocked from sending emails, based on their origin domain. To block a specific domain you would add that domain (or a rule applied to multiple domains) to a block list or 'black list'. Domains you wish to allow could also be added to a 'white list'.&lt;br /&gt;
** Pros - highly effective at blocking spam coming from specific domains. A user could very easily block a large amount of spam by adding one 'rule'; for instance, you could easily block all foreign domains [http://blogs.earthlink.net/webmail/2006/12/effective_domain_blocking.php read more about how to easily block all foreign domains]&lt;br /&gt;
** Cons - may inadvertently block legitimate addresses. Reuse of a domain by a legitmate company that was once used by a spammer would cause that company to be blocked/blacklisted. [http://www.the-cma.org/PublicUploads/224861ForgeMarketingOct03.pdf read more]&lt;br /&gt;
* '''Require users to request permission to send you an e-mail.'''&lt;br /&gt;
** Much like domain blocking users can setup black and white lists but rather then adding entire domains to the list they would add specific email addresses to the list.&lt;br /&gt;
** Pros - Guaranteed that any email you recieve is legitamte since you must approve all senders.&lt;br /&gt;
** Cons - again, this may inadvertently block some legitimate addresses. For instance, someone may request permission to send you an email from an address you do not recognize or someone may not even know they need to request permission to email you.&lt;br /&gt;
* '''Charge for e-mails sent.'''&lt;br /&gt;
** Users are charged a fee for every email sent.&lt;br /&gt;
** Pros - Eliminates the purpose of spam since it will no longer be a free form of advertising. It would become very pricey for a single spammer to send out millions of emails.&lt;br /&gt;
** Cons - Creates a problem for lower income users, especially those who may need to send out many emails and can not afford to. Non-profit organizations would also not be able to afford to send out mailings. [http://www.eschoolnews.com/news/showStoryts.cfm?ArticleID=6179 Read more about how AOL plans to help non-profit organizations.]&lt;br /&gt;
* '''Opt in for commercial e-mail.'''&lt;br /&gt;
** User must specify that they would like to receive emails from a company.&lt;br /&gt;
** Pros - Eliminate unsolicited commercial emails as long as its well enforced. Gives company a better target demographic because they know the user is interested. [http://www.americanchronicle.com/articles/viewArticle.asp?articleID=14247 read more about advantages of opt-in mailing lists.]&lt;br /&gt;
** Cons - Not practical since it would be very difficult to actually enforce. Reduce potential advertising capabilities of companies.&lt;br /&gt;
* '''Domain authentication.'''&lt;br /&gt;
** Domain authentication provides a way for the identify of a sender to be verified. This helps to prevent identity theft, fraud and spam in general. An identity is usually verified and authenticated by using some kind of a key or identification sequence.&lt;br /&gt;
** Pros - would help prevent fraudulent emails, phishing, and falsifying identity.&lt;br /&gt;
** Cons - If the authentication key gets compromised it may give a false sense of security to those who think the domain is authentic.&lt;br /&gt;
* '''Bounties'''&lt;br /&gt;
** The bounty system rewards users for information leading to the capture and conviction of spammers, usually by giving them a percentage of the revenue that the spammer had acquired.&lt;br /&gt;
** Pros - Money collected from spammers who have been caught can be used to catch other spammers. Give you a large policing force that could detect spammers better then a spam filter.&lt;br /&gt;
** Cons - People may become money hungry and turn in non-spammers simple for a reward.&lt;br /&gt;
* '''The &amp;quot;Goodmail&amp;quot; approach.''' [http://blogs.zdnet.com/BTL/?p=2737 Read more about the Goodmail Approach]&lt;br /&gt;
**Pros - Prevent smaller spamming companies unwilling to pay fees.&lt;br /&gt;
**Cons - Non-profit organization would have difficulties paying fees. Larger spamming companies could easily pay the fees and get easy access to email people. [http://www.techworld.com/security/features/index.cfm?featureid=2292 read more about issues with the Goodmail Approach]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1418</id>
		<title>CSC 379:Week 1, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1418"/>
		<updated>2007-07-06T13:17:10Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* The Ethics of Defenses against Spam */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== The Ethics of Defenses against Spam ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''Blocking domains'''&lt;br /&gt;
** Domain Blocking allows specific users to be blocked from sending emails, based on their origin domain. To block a specific domain you would add that domain (or a rule applied to multiple domains) to a block list or 'black list'. Domains you wish to allow could also be added to a 'white list'.&lt;br /&gt;
** Pros - highly effective at blocking spam coming from specific domains. A user could very easily block a large amount of spam by adding one 'rule'; for instance, you could easily block all foreign domains [http://blogs.earthlink.net/webmail/2006/12/effective_domain_blocking.php read more about how to easily block all foreign domains]&lt;br /&gt;
** Cons - may inadvertently block legitimate addresses. Reuse of a domain by a legitmate company that was once used by a spammer would cause that company to be blocked/blacklisted. [http://www.the-cma.org/PublicUploads/224861ForgeMarketingOct03.pdf read more]&lt;br /&gt;
* '''Require users to request permission to send you an e-mail.'''&lt;br /&gt;
** Much like domain blocking users can setup black and white lists but rather then adding entire domains to the list they would add specific email addresses to the list.&lt;br /&gt;
** Pros - Guaranteed that any email you recieve is legitamte since you must approve all senders.&lt;br /&gt;
** Cons - again, this may inadvertently block some legitimate addresses. For instance, someone may request permission to send you an email from an address you do not recognize or someone may not even know they need to request permission to email you.&lt;br /&gt;
* '''Charge for e-mails sent.'''&lt;br /&gt;
** Users are charged a fee for every email sent.&lt;br /&gt;
** Pros - Eliminates the purpose of spam since it will no longer be a free form of advertising. It would become very pricey for a single spammer to send out millions of emails.&lt;br /&gt;
** Cons - Creates a problem for lower income users, especially those who may need to send out many emails and can not afford to. Non-profit organizations would also not be able to afford to send out mailings. [http://www.eschoolnews.com/news/showStoryts.cfm?ArticleID=6179 Read more about how AOL plans to help non-profit organizations.]&lt;br /&gt;
* '''Opt in for commercial e-mail.'''&lt;br /&gt;
** &lt;br /&gt;
** Pros - Eliminate unsolicited commercial emails as long as its well enforced. Gives company a better target demographic. [http://www.americanchronicle.com/articles/viewArticle.asp?articleID=14247 read more about advantages of opt-in mailing lists.]&lt;br /&gt;
** Cons - Not practical since it would be very difficult to actually enforce. Reduce potential advertising cababilities of companies.&lt;br /&gt;
* '''Domain authentication.'''&lt;br /&gt;
** Pros - would help prevent fraudulent emails, phishing, and falsifying identity.&lt;br /&gt;
** Cons - If the authentication key gets compromised it may give a false sense of security to those who think the domain is authentic.&lt;br /&gt;
* '''Bounties'''&lt;br /&gt;
** Pros - Money collected from spammers who have been caught can be used to catch other spammers. Give you a large policing force that could detect spammers better then a spam filter.&lt;br /&gt;
** Cons - People may become money hungry and turn in non-spammers simple for a reward.&lt;br /&gt;
* '''The &amp;quot;Goodmail&amp;quot; approach.''' [http://blogs.zdnet.com/BTL/?p=2737 Read more about the Goodmail Approach]&lt;br /&gt;
**Pros - Prevent smaller spamming companies unwilling to pay fees.&lt;br /&gt;
**Cons - Non-profit organization would have difficulties paying fees. Larger spamming companies could easily pay the fees and get easy access to email people. [http://www.techworld.com/security/features/index.cfm?featureid=2292 read more about issues with the Goodmail Approach]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1417</id>
		<title>CSC 379:Week 1, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1417"/>
		<updated>2007-07-06T13:13:12Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* The Ethics of Defenses against Spam */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== The Ethics of Defenses against Spam ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''Blocking domains'''&lt;br /&gt;
** Domain Blocking allows specific users to be blocked from sending emails, based on their origin domain. To block a specific domain you would add that domain (or a rule applied to multiple domains) to a block list or 'black list'. Domains you wish to allow could also be added to a 'white list'.&lt;br /&gt;
** Pros - highly effective at blocking spam coming from specific domains. A user could very easily block a large amount of spam by adding one 'rule'; for instance, you could easily block all foreign domains [http://blogs.earthlink.net/webmail/2006/12/effective_domain_blocking.php read more about how to easily block all foreign domains]&lt;br /&gt;
** Cons - may inadvertently block legitimate addresses. Reuse of a domain by a legitmate company that was once used by a spammer would cause that company to be blocked/blacklisted. [http://www.the-cma.org/PublicUploads/224861ForgeMarketingOct03.pdf read more]&lt;br /&gt;
* '''Require users to request permission to send you an e-mail.'''&lt;br /&gt;
** Much like domain blocking users can setup black and white lists but rather then adding entire domains to the list they would add specific email addresses to the list.&lt;br /&gt;
** Pros - Guaranteed that any email you recieve is legitamte since you must approve all senders.&lt;br /&gt;
** Cons - again, this may inadvertently block some legitimate addresses. For instance, someone may request permission to send you an email from an address you do not recognize or someone may not even know they need to request permission to email you.&lt;br /&gt;
* '''Charge for e-mails sent.'''&lt;br /&gt;
** Users are charged a fee for every email sent.&lt;br /&gt;
** Pros - Eliminates the purpose of spam since it will no longer be a free form of advertising. It would become very pricey for a single spammer to send out millions of emails.&lt;br /&gt;
** Cons - Creates a problem for lower income users, especially those who may need to send out many emails and can not afford to. Non-profit organizations would also not be able to afford to send out mailings.&lt;br /&gt;
* '''Opt in for commercial e-mail.'''&lt;br /&gt;
** &lt;br /&gt;
** Pros - Eliminate unsolicited commercial emails as long as its well enforced. Gives company a better target demographic. [http://www.americanchronicle.com/articles/viewArticle.asp?articleID=14247 read more about advantages of opt-in mailing lists.]&lt;br /&gt;
** Cons - Not practical since it would be very difficult to actually enforce. Reduce potential advertising cababilities of companies.&lt;br /&gt;
* '''Domain authentication.'''&lt;br /&gt;
** Pros - would help prevent fraudulent emails, phishing, and falsifying identity.&lt;br /&gt;
** Cons - If the authentication key gets compromised it may give a false sense of security to those who think the domain is authentic.&lt;br /&gt;
* '''Bounties'''&lt;br /&gt;
** Pros - Money collected from spammers who have been caught can be used to catch other spammers. Give you a large policing force that could detect spammers better then a spam filter.&lt;br /&gt;
** Cons - People may become money hungry and turn in non-spammers simple for a reward.&lt;br /&gt;
* '''The &amp;quot;Goodmail&amp;quot; approach.''' [http://blogs.zdnet.com/BTL/?p=2737 Read more about the Goodmail Approach]&lt;br /&gt;
**Pros - Prevent smaller spamming companies unwilling to pay fees.&lt;br /&gt;
**Cons - Non-profit organization would have difficulties paying fees. Larger spamming companies could easily pay the fees and get easy access to email people. [http://www.techworld.com/security/features/index.cfm?featureid=2292 read more about issues with the Goodmail Approach]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1416</id>
		<title>CSC 379:Week 1, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1416"/>
		<updated>2007-07-06T13:00:45Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: /* The Ethics of Defenses against Spam */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== The Ethics of Defenses against Spam ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* '''Blocking domains'''&lt;br /&gt;
** Domain Blocking allows specific users to be blocked from sending emails, based on their origin domain. To block a specific domain you would add that domain (or a rule applied to multiple domains) to a block list or 'black list'. Domains you wish to allow could also be added to a 'white list'.&lt;br /&gt;
** Pros - highly effective at blocking spam coming from specific domains. A user could very easily block a large amount of spam by adding one 'rule'; for instance, you could easily block all foreign domains [http://blogs.earthlink.net/webmail/2006/12/effective_domain_blocking.php read more about how to easily block all foreign domains]&lt;br /&gt;
** Cons - may inadvertently block legitimate addresses. Reuse of a domain by a legitmate company that was once used by a spammer would cause that company to be blocked/blacklisted. [http://www.the-cma.org/PublicUploads/224861ForgeMarketingOct03.pdf read more]&lt;br /&gt;
* '''Require users to request permission to send you an e-mail.'''&lt;br /&gt;
** Much like domain blocking users can setup black and white lists but rather then adding entire domains to the list they would add specific email addresses to the list.&lt;br /&gt;
** Pros - Guaranteed that any email you recieve is legitamte since you must approve all senders.&lt;br /&gt;
** Cons - again, this may inadvertently block some legitimate addresses. For instance, someone may request permission to send you an email from an address you do not recognize or someone may not even know they need to request permission to email you.&lt;br /&gt;
* '''Charge for e-mails sent.'''&lt;br /&gt;
** Pros - Eliminates the purpose of spam since it will no longer be free to send mail and advertise.&lt;br /&gt;
** Cons - Creates a problem for lower income users, especially those who may need to send out many emails and can not afford to. Non-profit organizations would also not be able to afford to send out emails.&lt;br /&gt;
* '''Opt in for commercial e-mail.'''&lt;br /&gt;
**  Pros - Eliminate unsolicited commercial emails as long as its well enforced. Gives company a better target demographic. [http://www.americanchronicle.com/articles/viewArticle.asp?articleID=14247 read more about advantages of opt-in mailing lists.]&lt;br /&gt;
** Cons - Not practical since it would be very difficult to actually enforce. Reduce potential advertising cababilities of companies.&lt;br /&gt;
* '''Domain authentication.'''&lt;br /&gt;
** Pros - would help prevent fraudulent emails, phishing, and falsifying identity.&lt;br /&gt;
** Cons - If the authentication key gets compromised it may give a false sense of security to those who think the domain is authentic.&lt;br /&gt;
* '''Bounties'''&lt;br /&gt;
** Pros - Money collected from spammers who have been caught can be used to catch other spammers. Give you a large policing force that could detect spammers better then a spam filter.&lt;br /&gt;
** Cons - People may become money hungry and turn in non-spammers simple for a reward.&lt;br /&gt;
* '''The &amp;quot;Goodmail&amp;quot; approach.''' [http://blogs.zdnet.com/BTL/?p=2737 Read more about the Goodmail Approach]&lt;br /&gt;
**Pros - Prevent smaller spamming companies unwilling to pay fees.&lt;br /&gt;
**Cons - Non-profit organization would have difficulties paying fees. Larger spamming companies could easily pay the fees and get easy access to email people. [http://www.techworld.com/security/features/index.cfm?featureid=2292 read more about issues with the Goodmail Approach]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1411</id>
		<title>CSC 379:Week 1, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1411"/>
		<updated>2007-07-06T00:30:30Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== The Ethics of Defenses against Spam ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Blocking domains&lt;br /&gt;
** Pros - highly effective at blocking spam coming from specific domains.&lt;br /&gt;
** Cons - may inadvertently block legitimate addresses. Reuse of a domain by a legitmate company that was once used by a spammer would cause that company to be blocked/blacklisted. [http://www.the-cma.org/PublicUploads/224861ForgeMarketingOct03.pdf read more]&lt;br /&gt;
* Require users to request permission to send you an e-mail.&lt;br /&gt;
** Pros - Guaranteed that any email you recieve is legitamte since you must approve all senders.&lt;br /&gt;
** Cons - again, this may inadvertently block some legitimate addresses. For instance, someone may request permission to send you an email from an address you do not recognize or someone may not even know they need to request permission to email you.&lt;br /&gt;
* Charge for e-mails sent.&lt;br /&gt;
** Pros - Eliminates the purpose of spam since it will no longer be free to send mail and advertise.&lt;br /&gt;
** Cons - Creates a problem for lower income users, especially those who may need to send out many emails and can not afford to. Non-profit organizations would also not be able to afford to send out emails.&lt;br /&gt;
* Opt in for commercial e-mail.&lt;br /&gt;
**  Pros - Eliminate unsolicited commercial emails as long as its well enforced. Gives company a better target demographic. [http://www.americanchronicle.com/articles/viewArticle.asp?articleID=14247 read more about advantages of opt-in mailing lists.]&lt;br /&gt;
** Cons - Not practical since it would be very difficult to actually enforce. Reduce potential advertising cababilities of companies.&lt;br /&gt;
* Domain authentication.&lt;br /&gt;
** Pros - would help prevent fraudulent emails, phishing, and falsifying identity.&lt;br /&gt;
** Cons - If the authentication key gets compromised it may give a false sense of security to those who think the domain is authentic.&lt;br /&gt;
* Bounties&lt;br /&gt;
** Pros - Money collected from spammers who have been caught can be used to catch other spammers. Give you a large policing force that could detect spammers better then a spam filter.&lt;br /&gt;
** Cons - People may become money hungry and turn in non-spammers simple for a reward.&lt;br /&gt;
* The &amp;quot;Goodmail&amp;quot; approach. [http://blogs.zdnet.com/BTL/?p=2737 Read more about the Goodmail Approach]&lt;br /&gt;
**Pros - Prevent smaller spamming companies unwilling to pay fees.&lt;br /&gt;
**Cons - Non-profit organization would have difficulties paying fees. Larger spamming companies could easily pay the fees and get easy access to email people. [http://www.techworld.com/security/features/index.cfm?featureid=2292 read more about issues with the Goodmail Approach]&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1408</id>
		<title>CSC 379:Week 1, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1408"/>
		<updated>2007-07-06T00:21:35Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
== The Ethics of Defenses against Spam ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Blocking domains&lt;br /&gt;
** Pros - highly effective at blocking spam coming from specific domains.&lt;br /&gt;
** Cons - may inadvertently block legitimate addresses. Reuse of a domain by a legitmate company that was once used by a spammer would cause that company to be blocked/blacklisted. [http://www.the-cma.org/PublicUploads/224861ForgeMarketingOct03.pdf read more]&lt;br /&gt;
* Require users to request permission to send you an e-mail.&lt;br /&gt;
** Pros - Guaranteed that any email you recieve is legitamte since you must approve all senders.&lt;br /&gt;
** Cons - again, this may inadvertently block some legitimate addresses. For instance, someone may request permission to send you an email from an address you do not recognize or someone may not even know they need to request permission to email you.&lt;br /&gt;
* Charge for e-mails sent.&lt;br /&gt;
** Pros - Eliminates the purpose of spam since it will no longer be free to send mail and advertise.&lt;br /&gt;
** Cons - Creates a problem for lower income users, especially those who may need to send out many emails and can not afford to. Non-profit organizations would also not be able to afford to send out emails.&lt;br /&gt;
* Opt in for commercial e-mail.&lt;br /&gt;
**  Pros - Eliminate unsolicited commercial emails as long as its well enforced.&lt;br /&gt;
** Cons - Not practical since it would be very difficult to actually enforce. Reduce potential advertising cababilities of companies.&lt;br /&gt;
* Domain authentication.&lt;br /&gt;
** Pros - would help prevent fraudulent emails, phishing, and falsifying identity.&lt;br /&gt;
** Cons - If the authentication key gets compromised it may give a false sense of security to those who think the domain is authentic.&lt;br /&gt;
* Bounties&lt;br /&gt;
** Pros - Money collected from spammers who have been caught can be used to catch other spammers. Give you a large policing force that could detect spammers better then a spam filter.&lt;br /&gt;
** Cons - People may become money hungry and turn in non-spammers simple for a reward.&lt;br /&gt;
* The &amp;quot;goodmail&amp;quot; approach.&lt;br /&gt;
**Pros - Prevent smaller spamming companies unwilling to pay fees.&lt;br /&gt;
**Cons - Non-profit organization would have difficulties paying fees. Larger spamming companies could easily pay the fees and get easy access to email people.&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1406</id>
		<title>CSC 379:Week 1, Group 6</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_379:Week_1,_Group_6&amp;diff=1406"/>
		<updated>2007-07-06T00:20:32Z</updated>

		<summary type="html">&lt;p&gt;Rschmid: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Blocking domains&lt;br /&gt;
** Pros - highly effective at blocking spam coming from specific domains.&lt;br /&gt;
** Cons - may inadvertently block legitimate addresses. Reuse of a domain by a legitmate company that was once used by a spammer would cause that company to be blocked/blacklisted. [http://www.the-cma.org/PublicUploads/224861ForgeMarketingOct03.pdf read more]&lt;br /&gt;
* Require users to request permission to send you an e-mail.&lt;br /&gt;
** Pros - Guaranteed that any email you recieve is legitamte since you must approve all senders.&lt;br /&gt;
** Cons - again, this may inadvertently block some legitimate addresses. For instance, someone may request permission to send you an email from an address you do not recognize or someone may not even know they need to request permission to email you.&lt;br /&gt;
* Charge for e-mails sent.&lt;br /&gt;
** Pros - Eliminates the purpose of spam since it will no longer be free to send mail and advertise.&lt;br /&gt;
** Cons - Creates a problem for lower income users, especially those who may need to send out many emails and can not afford to. Non-profit organizations would also not be able to afford to send out emails.&lt;br /&gt;
* Opt in for commercial e-mail.&lt;br /&gt;
**  Pros - Eliminate unsolicited commercial emails as long as its well enforced.&lt;br /&gt;
** Cons - Not practical since it would be very difficult to actually enforce. Reduce potential advertising cababilities of companies.&lt;br /&gt;
* Domain authentication.&lt;br /&gt;
** Pros - would help prevent fraudulent emails, phishing, and falsifying identity.&lt;br /&gt;
** Cons - If the authentication key gets compromised it may give a false sense of security to those who think the domain is authentic.&lt;br /&gt;
* Bounties&lt;br /&gt;
** Pros - Money collected from spammers who have been caught can be used to catch other spammers. Give you a large policing force that could detect spammers better then a spam filter.&lt;br /&gt;
** Cons - People may become money hungry and turn in non-spammers simple for a reward.&lt;br /&gt;
* The &amp;quot;goodmail&amp;quot; approach.&lt;br /&gt;
**Pros - Prevent smaller spamming companies unwilling to pay fees.&lt;br /&gt;
**Cons - Non-profit organization would have difficulties paying fees. Larger spamming companies could easily pay the fees and get easy access to email people.&lt;/div&gt;</summary>
		<author><name>Rschmid</name></author>
	</entry>
</feed>