From Annvix

Developer's Reference: Resource Policy

This document provides the Annvix policies regarding development machines and services, as well as the conduct developers are expected to adhere to while working on the Annvix project.

This document is based on the Debian Machine Usage Policy.

When referring to "resources" in this document, all access granted to Annvix developers including, but not limited to, computer systems, CVS access, etc. is meant.

The basic premise of access to and utilization of Annvix resources is:

• Do not by any wilful, deliberate, reckless, or unlawful act interfere with the work of another developer or jeopardize the integrity of data networks, computing equipment, system programs, or other stored information.
• Do not use Annvix resources for private financial gain or for commercial purposes, including consultancy or any other work outside the scope of official duties or functions for the time being, without specific authorization to do so.
• Do not use Annvix resources for unlawful activities including, but not limited to, software piracy.

The rules in the policies are binding and inviolate; your signed application indicates your acceptance of these policies.

General Statements

1. Access to Annvix resources is a privilege, not a right or commercial service, and we reserve the right to revoke this privilege at any time, without prior notice or explanation.
2. There is no guarantee of service. Although we will do out best to ensure that everything functions properly, no guarantees can be given.
3. There can be no expectation of privacy on Annvix resources. System administrators have access required to do their job and that may require the modification of user files if necessary. If you want or need something to remain private, do not keep it on Annvix resources.

Policies

At the moment, there are no publically available developer machines. This may change in the future as more resources are made available, however at the moment developers will be required to do packaging and testing on their own systems prior to committing to the repositories. With this in mind, many of the following policies are irrelevant, however as developer machines to become available (i.e. for alternate architectures), these policies will be in effect.

Shell access: All connections to any Annvix resources must be done via ssh or scp. Telnet, FTP, rsh, etc. are not and will not be available. All connections must also be done via ssh keys; password-based logins are not permitted.

Disk usage: Developers are expected to watch their disk usage. Do not keep unnecessary files around that take up a lot of space as this may prevent other developers from getting their work done. If you receive notification that your home directory is getting too large, clean it up immediately or an administrator may do it for you.

Processes: Do not run any long-running processes without the permission of an administrator. Running servers of any sort, including but not limited to IRC bots, without the prior permission of an administrator is expressly forbidden. Likewise, avoid running any processes that are CPU or memory expensive.

Mail/News: Reading/writing email and/or usenet is not permissible on Annvix resources. Annvix provides POP3S access to retrieve email or you can ask an administrator to forward mail for your email alias to an alternate email address.

Penalties

Enforcement of rules and policies is a fact of life. We believe in being fair to developers, however there is no room for negotiation of any rules and policies indicated here or in the Annvix applicant's agreement. This also means that any issues that conflict with said rules and policies need to be dealt with in a similar manner across the board.

On a first offense, the developer will be placed on suspension and will have any access to Annvix resources suspended for a period of time determined by the core team to coincide with the severity of the offense. On a second offense, the core team may elect to permanently revoke any and all access to the project. The developer can certainly appeal any decisions by the core team, but the core team has the final say.

Please note that these rules are not in place to make life miserable, but rather to ensure that all developers will work smoothly together to ensure the project has a healthy future and that developers have healthy working relationships. Without some form of structure, the project would be nothing but chaos which would hamper development efforts.

• This page was last modified 18:11, 10 February 2007.
• About Annvix
• Disclaimers