systhread policy

systhread's policies

As a public (yet still free) site, systhread must maintain some sort of policy regarding a few topics:

Content Redistribution
Code Redistribution
Email Privacy and Reader Contributions
Retention of Postings and Texts
Outbound Flight (you leave here)

This document covers these policies, if in doubt, contact me with questions or comments.

Content Policy Redistribution

Content is published under the creative commons license version 3. The strictest form. More information can be found here.

Code Redistribution

Are just that, snipplets. Consider them public domain. Programs all have their own licenses, otherwise they are public domain. So to further explain the policy it works like this:

Code in texts is public domain in of iteslf even if it is a complete program.
Code in the repositories is all licensed under their own terms (depending upon the project) and stand as is.

Email Privacy and Reader Contributions

No email addresses sent via or about systhread will ever be or have ever been divulged (including predecessor projects). If an email corrects an error or just points out a mistake please let me know ahead of time if it is okay to quote the sender (e.g. you) by name, hacker alias, email or any/all of the above otherwise will have to ask which delays in making the update. Like to give credit where credit is due but only if you want credit.

Retention of Postings and Texts

Retention policy here is ... weird. It kind of works off of the webmeisters feelings and sundry logs. Certainly non-article or non-texts content is simply purged after a certain time because it is no longer relevant. Some texts are also purged for the exact same reason, they are outdated and either were not going to be updated or could not be updated and hence can be found in the attic area of the site - but it is purely subjective and it has caused issues in the past. The retention policy for retention now is:

Transient news items simply go into /dev/null ; that would be site news, code release info etc. All the code stuff is in version control anyhow so if you want to see eff-ups - have at it. As for transient site news - who really cares?
Texts - when a text is deemed non-relevant the policy used to be delete it; after 2 cases of that being an issue the new policy is put in the attic.