Deploying to gh-pages from @ feff90d 🚀

Author: gaborcsardi

dev/CODE_OF_CONDUCT.html

@@ -0,0 +1,132 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in
+our community a harassment-free experience for everyone, regardless of
+age, body size, visible or invisible disability, ethnicity, sex
+characteristics, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance,
+race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open,
+welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our
+  mistakes, and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political
+  attacks
+- Public or private harassment
+- Publishing others’ private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our
+standards of acceptable behavior and will take appropriate and fair
+corrective action in response to any behavior that they deem
+inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other
+contributions that are not aligned to this Code of Conduct, and will
+communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also
+applies when an individual is officially representing the community in
+public spaces. Examples of representing our community include using an
+official e-mail address, posting via an official social media account,
+or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may
+be reported to the community leaders responsible for enforcement at
+<codeofconduct@posit.co>. All complaints will be reviewed and
+investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security
+of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in
+determining the consequences for any action they deem in violation of
+this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior
+deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders,
+providing clarity around the nature of the violation and an explanation
+of why the behavior was inappropriate. A public apology may be
+requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, for a specified period of
+time. This includes avoiding interactions in community spaces as well as
+external channels like social media. Violating these terms may lead to a
+temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards,
+including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No
+public or private interaction with the people involved, including
+unsolicited interaction with those enforcing the Code of Conduct, is
+allowed during this period. Violating these terms may lead to a
+permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of
+individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction
+within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor
+Covenant](https://www.contributor-covenant.org), version 2.1, available
+at
+<https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by \[Mozilla’s code of conduct
+enforcement ladder\]\[<https://github.com/mozilla/inclusion>\].
+
+For answers to common questions about this code of conduct, see the FAQ
+at <https://www.contributor-covenant.org/faq>. Translations are
+available at <https://www.contributor-covenant.org/translations>.

dev/CODE_OF_CONDUCT.md

@@ -0,0 +1,56 @@
+# Contributing to pkgcache
+
+This outlines how to propose a change to pkgcache. For more detailed
+info about contributing to this, and other tidyverse packages, please
+see the [**development contributing
+guide**](https://rstd.io/tidy-contrib).
+
+### Fixing typos
+
+Small typos or grammatical errors in documentation may be edited
+directly using the GitHub web interface, so long as the changes are made
+in the *source* file.
+
+- YES: you edit a roxygen comment in a `.R` file below `R/`.
+- NO: you edit an `.Rd` file below `man/`.
+
+### Prerequisites
+
+Before you make a substantial pull request, you should always file an
+issue and make sure someone from the team agrees that it’s a problem. If
+you’ve found a bug, create an associated issue and illustrate the bug
+with a minimal [reprex](https://www.tidyverse.org/help/#reprex).
+
+### Pull request process
+
+- We recommend that you create a Git branch for each pull request
+  (PR).  
+- Look at the Travis and AppVeyor build status before and after making
+  changes. The `README` should contain badges for any continuous
+  integration services used by the package.  
+- New code should follow the tidyverse [style
+  guide](http://style.tidyverse.org). You can use the
+  [styler](https://CRAN.R-project.org/package=styler) package to apply
+  these styles, but please don’t restyle code that has nothing to do
+  with your PR.  
+- We use [roxygen2](https://cran.r-project.org/package=roxygen2), with
+  [Markdown
+  syntax](https://roxygen2.r-lib.org/articles/rd-formatting.html), for
+  documentation.  
+- We use [testthat](https://cran.r-project.org/package=testthat).
+  Contributions with test cases included are easier to accept.  
+- For user-facing changes, add a bullet to the top of `NEWS.md` below
+  the current development version header describing the changes made
+  followed by your GitHub username, and links to relevant
+  issue(s)/PR(s).
+
+### Code of Conduct
+
+Please note that the pkgcache project is released with a [Contributor
+Code of
+Conduct](https://r-lib.github.io/pkgcache/dev/CODE_OF_CONDUCT.md). By
+contributing to this project you agree to abide by its terms.
+
+### See tidyverse [development contributing guide](https://rstd.io/tidy-contrib)
+
+for further details.

dev/CONTRIBUTING.html

@@ -0,0 +1,4 @@
+# License
+
+    YEAR: 2025
+    COPYRIGHT HOLDER: pkgcache authors

dev/CONTRIBUTING.md

@@ -0,0 +1,22 @@
+# MIT License
+
+Copyright (c) 2025 pkgcache authors
+
+Permission is hereby granted, free of charge, to any person obtaining a
+copy of this software and associated documentation files (the
+“Software”), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

dev/LICENSE-text.html

@@ -0,0 +1,13 @@
+# Articles
+
+### All vignettes
+
+- [pkgcache
+  internals](https://r-lib.github.io/pkgcache/dev/articles/internals.md):
+
+  For pkgcache developers.
+
+- [pkgcache and Posit Package Manager on
+  Linux](https://r-lib.github.io/pkgcache/dev/articles/ppm.md):
+
+  Using pkgcache with the Posit Package Manager on Linux.