We want as much content as possible to be freely available to the public. To this end, we do not wish for any content to be behind a login wall unless there is a compelling reason to do so (e.g. for security reasons, or practical reasons).

Example 1: Logging in may be required in the future for users to submit and edit scores to the scoreboard – both for security (users should only have access to their own scores) and practical reasons (we need to associate a person with score reports)

Example 2: Downloading level sets may be subject to a CAPTCHA for security reasons, however there is no need to require a login to download what would otherwise be publicly accessible.

In granting content managers the ability to host personal Chips-related projects at BitBusters.club, we also wish to offer as much autonomy over that content as possible. Unless it comes to our attention that the hosted content goes against the principles outlined in this document, we have no intention or interest in micromanaging privately managed projects.

We invite and are actively interested in collaboration from the community where feasible, provided the collaboration is in the spirit of the principles outlined in this document.

We wish to maintain a professional site in terms of appearance and content. This project should not be used to host content which could reasonably be expected to cause offense or controversy. When in doubt, err on the side of caution and remember the focus on Chip's Challenge content.

The same security standard must be upheld across the server. The server operators reserve the right to directly intervene where hosted content introduces any form of security threat to the server. Content managers must make reasonable effort to follow modern security best practices and must not allow others to connect to the server with their credentials.

Security threats include any actions, intentional or unintentional, which introduce unnecessary security risks to the server or its users. This could include unauthorized changes to the server configuration (e.g. opening firewall ports, circumventing server security mechanisms, granting overly permissive file permissions, etc.), use of insecure protocols (e.g. unsecure FTP, HTTP, etc.), use of unvetted third-party code/software and more.

"Less is more" is our guiding principle when granting access to new content managers or collaborators. The more access granted; the more security risk introduced. The server operators will evaluate the access needs for each content manager or collaborator on a case by case basis and offer access which balances usability with security risk.

In granting access, we wish to balance the principle of collaboration with the principles of security and stability. We don't want community members to feel excluded from being able to contribute to this project, but also recognize there is a realistic limit to how many people can and should have access to the project server for security reasons.

From both a technical and operational perspective, stability is critical to the ongoing success of this project. At the technical level, we wish to maintain the best server uptime possible and limit the impact of software updates and server upgrades on end users. The server owner will take responsibility for taking regular database and full server backups, balancing frequency with cost considerations. Content managers must not host content which has a negative effect on the BitBusters.club website's search engine rankings.

At the operational level, it is important everyone involved with the project remain focused on the principles outlined in this document and not become embroiled in drama. Personal disputes and differences must be put aside when working on this project. Prospective content managers and server operators must have a proven track record of team work and keeping a level head in collaborative projects.