To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
-[ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-[ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-[ ] [Set up project integrations](https://gitlab.common-lisp.net/clo/terms-and-privacy-docs/-/settings/integrations)
## Collaborate with your team
-[ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-[ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-[ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
Use the built-in continuous integration in GitLab.
-[ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-[ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-[ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-[ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-[ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
## License
For open source projects, say how it is licensed.
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
This will contain the Privacy Statement and Terms of Service for the
# Privacy Policy for GitLab Hosted by the Common Lisp Foundation
**Effective Date:** 2024-12-08
## 1. Who We Are
The Common Lisp Foundation (“we,” “our,” “us”) operates this GitLab
instance, hosted at `future.common-lisp.net`. We are a non-profit
organization incorporated in the Netherlands, dedicated to supporting
and promoting the use of Common Lisp.
## 2. What Information We Collect
We collect the following types of personal information from users who
register for and use our GitLab instance:
-**Email Address**: Used for GitLab-related communication, such as account management, notifications, and system updates.
-**User Account Information**: Includes username, password (stored in encrypted form), and other optional profile data provided by users.
-**Activity Logs**: Information about actions performed on this GitLab instance for auditing and security purposes.
## 3. How We Use Your Information
We collect and use your information solely to:
- Enable you to use this GitLab instance and its features.
- Communicate with you regarding account management, security updates, and GitLab-related notifications.
- Maintain the security and functionality of this GitLab instance.
## 4. How We Protect Your Information
We implement appropriate technical and organizational measures to ensure the security of your personal information, including:
- Encryption of passwords and sensitive data.
- Secure access protocols.
- Regular system updates and monitoring.
## 5. Sharing of Information
We do not sell, rent, or share your personal information with third parties, except as required by law or to fulfill our GitLab-related obligations. Specifically:
- We may share information with service providers to ensure the secure operation of this GitLab instance.
- We may disclose information if required by law or to protect the rights and safety of our users and the Common Lisp Foundation.
## 6. Data Retention
We retain your personal information for as long as your account is active or as needed to provide GitLab-related services. If you close your account, we will delete your data in accordance with applicable laws and our data retention policies.
## 7. Your Rights
As a user, you have the following rights under the General Data
Protection Regulation (GDPR) and similar regulations worldwide:
-**Access**: You can request access to the personal data we hold about you.
-**Rectification**: You can request corrections to inaccurate or incomplete data.
-**Erasure**: You can request deletion of your data, subject to legal obligations.
-**Restriction**: You can request that we limit processing of your data.
-**Portability**: You can request a copy of your data in a commonly used format.
-**Objection**: You can object to data processing in certain circumstances.
To exercise these rights, please contact us at [clo-devel@common-lisp.net].
## 8. Cookies and Tracking
This GitLab instance uses cookies to enhance your experience and
maintain session security. By using this service, you consent to our
use of cookies.
## 9. Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will
be posted on this page with a revised effective date. Your continued
use of this GitLab instance after changes are made constitutes your
acceptance of the updated Privacy Policy.
## 10. Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us:
- **Activity Logs**: Information about actions performed on this GitLab instance for auditing and security purposes.
## 3. How We Use Your Information
We collect and use your information solely to:
- Enable you to use this GitLab instance and its features.
- Communicate with you regarding account management, security updates, and GitLab-related notifications.
- Maintain the security and functionality of this GitLab instance.
## 4. How We Protect Your Information
We implement appropriate technical and organizational measures to ensure the security of your personal information, including:
- Encryption of passwords and sensitive data.
- Secure access protocols.
- Regular system updates and monitoring.
## 5. Sharing of Information
We do not sell, rent, or share your personal information with third parties, except as required by law or to fulfill our GitLab-related obligations. Specifically:
- We may share information with service providers to ensure the secure operation of this GitLab instance.
- We may disclose information if required by law or to protect the rights and safety of our users and the Common Lisp Foundation.
## 6. Data Retention
We retain your personal information for as long as your account is active or as needed to provide GitLab-related services. If you close your account, we will delete your data in accordance with applicable laws and our data retention policies.
## 7. Your Rights
As a user, you have the following rights under the General Data Protection Regulation (GDPR):
- **Access**: You can request access to the personal data we hold about you.
- **Rectification**: You can request corrections to inaccurate or incomplete data.
- **Erasure**: You can request deletion of your data, subject to legal obligations.
- **Restriction**: You can request that we limit processing of your data.
- **Portability**: You can request a copy of your data in a commonly used format.
- **Objection**: You can object to data processing in certain circumstances.
To exercise these rights, please contact us at [Insert Contact Email].
## 8. Cookies and Tracking
This GitLab instance uses cookies to enhance your experience and maintain session security. By using this service, you consent to our use of cookies. For more details, please refer to GitLab’s [Cookie Policy](https://docs.gitlab.com/ee/user/profile/preferences.html#cookies).
## 9. Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will be posted on this page with a revised effective date. Your continued use of this GitLab instance after changes are made constitutes your acceptance of the updated Privacy Policy.
## 10. Contact Us
If you have any questions or concerns about this Privacy Policy, please contact us:
- **Email**: [Insert Contact Email]
- **Mail**: Common Lisp Foundation, [Insert Address], Netherlands
y provide additional free or paid services, including but not limited to:
- Private repository hosting.
- Continuous Integration (CI) runner resources.
- Container registry services.
The availability and terms for these additional services are subject to change and will be communicated to affected users.
## 4. Eligibility
To use this service, you must:
- Register for an account and provide accurate information.
- Use the service only for projects directly related to Common Lisp.
We reserve the right to review and, at our discretion, deny or terminate accounts or projects that do not align with the purpose of this platform.
## 5. User Responsibilities
By using this service, you agree to:
- **Abide by applicable laws** and not use this service for illegal purposes.
- **Respect the rights of others**, including intellectual property rights.
- **Maintain security of your account**, including using two-factor authentication (2FA) as required.
- **Avoid abusive usage**, such as excessive resource consumption or actions that disrupt the service.
## 6. Limitation of Liability
The Common Lisp Foundation provides this service "as is" without any warranties or guarantees. We are not liable for:
- Any data loss or service interruptions.
- Indirect, incidental, or consequential damages arising from the use or inability to use this service.
Users are encouraged to maintain their own backups of important data.
## 7. Termination of Service
We reserve the right to suspend or terminate accounts or projects for:
- Violation of these Terms of Service.
- Activities that harm the stability or security of this GitLab instance.
- Non-payment of fees for any agreed-upon paid services.
## 8. Privacy
Your use of this service is also governed by our [Privacy Policy](./privacy.md), which explains how we collect, use, and protect your personal data.
## 9. Modifications to These Terms
We may update these Terms of Service from time to time. Any changes will be posted on this page with a revised effective date. Continued use of the service after changes constitutes acceptance of the updated terms.
## 10. Contact Us
If you have questions about these Terms of Service or need support, please contact us:
- **Email**: [Insert Contact Email]
- **Mail**: Common Lisp Foundation, [Insert Address], Netherlands