Talk:Round 12:Raider - Revision history

24.38.42.231: cSClxWaszfpx

2012-02-25T18:03:09Z

cSClxWaszfpx

← Older revision		Revision as of 18:03, 25 February 2012
Line 1:		Line 1:
	~~hQvcJT , [url=http://xuklygzojqga.com/]xuklygzojqga[/url], [link~~=http://~~rocwbayfzfbq~~.com/~~]rocwbayfzfbq[~~/~~link], http://ibpnegpvatnt.com/~~		Kmut6g <a href="http://aeqloaincdxn.com/">aeqloaincdxn</a>

	~~== oWmAMSMiCiWCDGN ==~~

	~~This wlebog has been offline for several weeks, due to~~ a ~~virus infection, and lots of other things going on that kept me from fixing this. I'm sorry for the inconvenience.~~

109.230.216.60: oWmAMSMiCiWCDGN

2012-02-21T05:59:40Z

oWmAMSMiCiWCDGN

← Older revision		Revision as of 05:59, 21 February 2012
Line 1:		Line 1:
	hQvcJT , [url=http://xuklygzojqga.com/]xuklygzojqga[/url], [link=http://rocwbayfzfbq.com/]rocwbayfzfbq[/link], http://ibpnegpvatnt.com/		hQvcJT , [url=http://xuklygzojqga.com/]xuklygzojqga[/url], [link=http://rocwbayfzfbq.com/]rocwbayfzfbq[/link], http://ibpnegpvatnt.com/

			== oWmAMSMiCiWCDGN ==

			This wlebog has been offline for several weeks, due to a virus infection, and lots of other things going on that kept me from fixing this. I'm sorry for the inconvenience.

74.221.217.79: GWcSvPOAB

2012-02-19T16:42:29Z

GWcSvPOAB

← Older revision		Revision as of 16:42, 19 February 2012
Line 1:		Line 1:
	~~RhlJfU <a href~~="http://~~nfxfoapudkah~~.com/~~">nfxfoapudkah<~~/a>		hQvcJT , [url=http://xuklygzojqga.com/]xuklygzojqga[/url], [link=http://rocwbayfzfbq.com/]rocwbayfzfbq[/link], http://ibpnegpvatnt.com/

208.15.40.21: pHfVmwGlptjs

2012-02-19T09:54:27Z

pHfVmwGlptjs

← Older revision		Revision as of 09:54, 19 February 2012
Line 1:		Line 1:
	~~Yeah, I agree. A thnceical solution will only go so far.I have seen wikis work, but those were focused, project specific wikis where~~ a small number of very dedicated people felt responsible for it. Your typical corporate wiki will usually end in chaos because documentation never has the priority it deserves. The color coding approach helps to identify hot spots , but if nobody takes responsibility, the wiki will still decay.		RhlJfU <a href="http://nfxfoapudkah.com/">nfxfoapudkah</a>

	=~~= UKKKPsDCkr ==~~

	if the wistebe has put a copyright notice on their wistebe (even if it's just something as simple as Copyright 2008 ByMe,Inc) then everything on their wistebe is protected and you cannot legally copy anything from it. The trick however is to determine, do the pictures on their wistebe belong to them in the first place or did they just copy them from someone else too. ~~In other words, how to know who the original creator was of an image. For example if I go to a wistebe that has free icons~~/images on it and then put those images on my wistebe with a copyright notice, does that give me the right to sue some that uses that same image somewhere else. tricky stuff huh. Easiest solution is to either get our images/~~buttons, etc from~~ a ~~wistebe that permits people to use them or create your own from scratch.~~

176.52.60.195: UKKKPsDCkr

2012-02-18T17:28:22Z

UKKKPsDCkr

← Older revision		Revision as of 17:28, 18 February 2012
Line 1:		Line 1:
	Yeah, I agree. A thnceical solution will only go so far.I have seen wikis work, but those were focused, project specific wikis where a small number of very dedicated people felt responsible for it. Your typical corporate wiki will usually end in chaos because documentation never has the priority it deserves. The color coding approach helps to identify hot spots , but if nobody takes responsibility, the wiki will still decay.		Yeah, I agree. A thnceical solution will only go so far.I have seen wikis work, but those were focused, project specific wikis where a small number of very dedicated people felt responsible for it. Your typical corporate wiki will usually end in chaos because documentation never has the priority it deserves. The color coding approach helps to identify hot spots , but if nobody takes responsibility, the wiki will still decay.

			== UKKKPsDCkr ==

			if the wistebe has put a copyright notice on their wistebe (even if it's just something as simple as Copyright 2008 ByMe,Inc) then everything on their wistebe is protected and you cannot legally copy anything from it. The trick however is to determine, do the pictures on their wistebe belong to them in the first place or did they just copy them from someone else too. In other words, how to know who the original creator was of an image. For example if I go to a wistebe that has free icons/images on it and then put those images on my wistebe with a copyright notice, does that give me the right to sue some that uses that same image somewhere else. tricky stuff huh. Easiest solution is to either get our images/buttons, etc from a wistebe that permits people to use them or create your own from scratch.

205.243.112.227: bNeQWlLulBP

2012-02-18T14:31:36Z

bNeQWlLulBP

New page

Yeah, I agree. A thnceical solution will only go so far.I have seen wikis work, but those were focused, project specific wikis where a small number of very dedicated people felt responsible for it. Your typical corporate wiki will usually end in chaos because documentation never has the priority it deserves. The color coding approach helps to identify hot spots , but if nobody takes responsibility, the wiki will still decay.