Plagiarism of homework assignments could also be a problem.  However SJ raises a good point that making almost everything world-readable by default is a good idea.  In a typical classroom setting, there is always other students' work up all over the walls for everybody to see and learn from.  Especially content bundles that have been downloaded from the Web should be public by default, to encourage mirroring and because anyone could go get the bundle themselves, but peer learning could be encouraged if much of what the kids create is also public.  The UI would just have to make it very clear that there is a way to make stuff private. Luke <div>On 8/23/07, Jon Phillips <<a href="mailto:jon@rejon.org">jon@rejon.org</a>> wrote:<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Fri, 2007-08-24 at 01:06 -0400, Samuel Klein wrote: > From the ongoing discussion on sharing data across activities: > > | Why not make this the default state of sharable files that ship with > | an activity, and encourage activities to explicitly store sharable > | files in an appropriate directory?  I'm not clear on why we want to > | make it difficult for activities to flag their contents as > | world-readable.  Is there a counter-use case? > > More fundamentally: > Why do we believe there should be privately-owned data on XOs? > > Many parts of the system become simpler when anyone can read anything > by default. > > SJ and Michael Regardless, there is a patch sitting here at CC (just finished) for adding CC license functionality to OLPC...gotta get that in tomorrow...that's right, CC license support and some basic support for sharing ready to go in the journal, but usable across the system. I think however that the system should allow for privacy. Can you imagine some kid using this for their own personal notes about growing up, etc? Man, how akward for that to be world-readable...or how about a crush or something? This thing should support what all the grownups get... :) Anyway, the CC license functionality hopefully helps along this path...hound us with emails to get this in tomorrow :) Scott, anything to add? Jon -- Jon Phillips San Francisco, CA USA PH 510.499.0894 <a href="mailto:jon@rejon.org">jon@rejon.org</a> <a href="http://www.rejon.org">http://www.rejon.org</a> MSN, AIM, Yahoo Chat: kidproto Jabber Chat: <a href="mailto:rejon@gristle.org"> rejon@gristle.org</a> IRC: <a href="mailto:rejon@irc.freenode.net">rejon@irc.freenode.net</a> _______________________________________________ Sugar mailing list <a href="mailto:Sugar@lists.laptop.org">Sugar@lists.laptop.org </a> <a href="http://lists.laptop.org/listinfo/sugar">http://lists.laptop.org/listinfo/sugar</a> </blockquote></div>