On Thu, 2008-09-18 at 16:57 +0200, Samuel Murray (Groenkloof) wrote: > F Wolff wrote: > > > I think each deployment should write its own policy, and we shouldn't > > pretend to be able to say anything about servers in general, because we > > can't. We could encourage administrators to include a privacy notice, in > > the same way we encourage them to put in contact details to the > > administrators. > > We can expect Pootle administrators to be experts in server > administration and similar technical issues, but we can't expect them to > know the issues surrounding privacy issues, copyright issues etc. > > Therefore I think Pootle should be distributed in such a way that Pootle > admins can focus on what they do best, and safely assume that the rest > has been taken care of. > > Few if any Pootle admins will think of writing a privacy policy, and by > the time they realise they need one, it'll be mostly too late to > implement one. If we can provide a generic privacy, it protects our > customers.
I think we should include a default one, but I'd rather see people actively take step to add their own or review the default. So I think similar to what the default setup does we simply prepend text that says: "This is the default privacy policy distributed with Pootle. Please update this to reflect the policy of your organisation, write your own or review the default and remove this text to make it your privacy policy" Or something like that. > > > As Dwayne suggested, let's make it focus on the positives. > > My proposed privacy policy statement does not contain any negatives. > Negative and positive are in the eye of the beholder, I think. The > privacy policy is not a marketing document to make the system seem > friendly, but a dry, factual statement about how private data is dealt > with on the site. > > Nor do I think one should, as Dwayne suggested, identify aspects that we > regard as unpleasant, and bury those in legalese... although I'm all for > a more legal sounding privacy policy, and I'm not against rewording. > > > Many people > > want credit for their work, and they want team communication to work. > > You're assuming a scenario in which Pootle is specifically touted to > translators as a team system and where there are so many translators > that they can't help but be aware of each other's presence. > > Samuel > -- Dwayne Bailey Associate +27 12 460 1095 (w) Translate.org.za +27 83 443 7114 (c) Recent blog posts: * The birth of the GNU generation http://www.translate.org.za/blogs/dwayne/en/content/birth-gnu-generation * Firefox users experience discrimination * RPM packages for py lib 0.9.2 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
