Updated 'gh-pages' from docs/ folder

Author: HenrikBengtsson

404.html

@@ -0,0 +1,3 @@
+Content not found. Please use links in the navbar.
+
+# Page not found (404)

404.md

@@ -0,0 +1,26 @@
+# Contributing to the ‘future.tests’ package
+
+This Git repository uses the [Git
+Flow](https://nvie.com/posts/a-successful-git-branching-model/)
+branching model (the
+[`git flow`](https://github.com/petervanderdoes/gitflow-avh) extension
+is useful for this). The
+[`develop`](https://github.com/futureverse/future.tests/tree/develop)
+branch contains the latest contributions and other code that will appear
+in the next release, and the
+[`master`](https://github.com/futureverse/future.tests) branch contains
+the code of the latest release, which is exactly what is currently on
+[CRAN](https://cran.r-project.org/package=future.tests).
+
+Contributing to this package is easy. Just send a [pull
+request](https://help.github.com/articles/using-pull-requests/). When
+you send your PR, make sure `develop` is the destination branch on the
+[future.tests repository](https://github.com/futureverse/future.tests).
+Your PR should pass `R CMD check --as-cran`, which will also be checked
+by [GitHub
+Actions](https://github.com/futureverse/future.tests/actions?query=workflow%3AR-CMD-check)
+and when the PR is submitted.
+
+We abide to the [Code of
+Conduct](https://www.contributor-covenant.org/version/2/0/code_of_conduct/)
+of Contributor Covenant.

CONTRIBUTING.html

@@ -0,0 +1,55 @@
+# NA
+
+The **[future](https://future.futureverse.org)** package defines the
+Future API which consists of a small number of functions for writing
+[R](https://www.r-project.org) code that can be evaluated either
+sequential or in parallel based a single setting without having to
+change anything in the code. Parallelization can be done via one of many
+backends, e.g. via built-in multicore, multisession and cluster backends
+(based on the **parallel** package) or via third-party backends such as
+**[future.batchtools](https://future.batchtools.futureverse.org)**,
+**[future.callr](https://future.callr.futureverse.org)** and
+**[future.mirai](https://future.mirai.futureverse.org)**. The design
+motto of the Future API is:
+
+> Write once, run anywhere
+
+In order for such code to work regardless of which future backend the
+end-user choose, it is critical that the backend fully complies with the
+[Future API Backend
+Specification](https://future.futureverse.org/articles/future-6-future-api-backend-specification.html).
+A future backend with a 100% compliance rate guarantees that the code
+will work equally well there as in sequential mode.
+
+This R package -
+**[future.tests](https://future.tests.futureverse.org)** - provides a
+test suite for validation that a future backend complies with the Future
+API.
+
+![](articles/imgs/screencast.gif)
+
+## Validate a Future Backend
+
+All future backends implementing the Future API should validate that
+they conform to the Future API. This can be done using the
+**[future.tests](https://future.tests.futureverse.org)** package, which
+provides two API for running the tests. The tests can be performed
+either from within R or from outside of R from the command line making
+it easy to include them package tests and in Continuous Integration (CI)
+pipelines.
+
+### From Within R
+
+``` r
+> results <- future.tests::check(plan = "multisession")
+> exit_code <- attr(results, "exit_code")
+> if (exit_code != 0) stop("One or more tests failed")
+```
+
+### From Outside R
+
+``` sh
+$ Rscript -e future.tests::check --test-plan="multisession"
+$ exit_code=$?
+$ [[ exit_code -eq 0 ]] || { >&2 echo "One or more tests failed"; exit 1; }
+```