Merge pull request #155 from OpenVoxProject/text_changes

Change Puppet -> OpenVox and Bolt -> OpenBolt

Author: bastelfreak

.github/rulesets.yaml

@@ -19,6 +19,6 @@ rulesets:
 
           !feature
 
-          * **Added a new feature** ([#1000](https://github.com/puppetlabs/bolt/issues/1000))
+          * **Added a new feature** ([#1000](https://github.com/OpenVoxProject/openbolt/issues/1000))
 
             A brief summary of the new feature.

CODE_OF_CONDUCT.md

@@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at conduct@puppet.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at openvox@voxpupuli.org. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 

CONTRIBUTING.md

@@ -1,61 +1,55 @@
 # Contributing
 
-## Bolt Community Slack Channel
+## OpenBolt Community Slack Channel
 
-Join the `#bolt` channel in the [Puppet community
-Slack](https://slack.puppet.com/) where Bolt developers and community members
-who use and contribute to Bolt discuss the tool. Another channel of interest is
-`#office-hours`, where once a week a Bolt developer leads a Q&A session about
-using Bolt.
+Join the `#sig-openbolt` channel in the [Vox Pupuli community
+Slack](https://voxpupuli.slack.com/) where OpenBolt developers and community members
+who use and contribute to OpenBolt discuss the tool.
 
 ## Issues
 
 Please submit new issues on the GitHub issue tracker:
-https://github.com/puppetlabs/bolt/issues
+https://github.com/OpenVoxProject/openbolt/issues
 
 Choose the appropriate template depending on the kind of issue you're filing:
 feature request, bug report, or docs change.
 
 ## Types of Improvements
 
-The Bolt ecosystem is extensible via Puppet modules such as those hosted on the
-[Forge](https://forge.puppet.com/). Many improvements to the Bolt ecosystem
+The OpenBolt ecosystem is extensible via Puppet modules such as those hosted on the
+[Forge](https://forge.puppet.com/). Many improvements to the OpenBolt ecosystem
 can be added there as new modules, including [Bolt
 tasks](https://puppet.com/docs/bolt/latest/writing_tasks.html), [Bolt
 plans](https://puppet.com/docs/bolt/latest/writing_yaml_plans.html), [inventory
 plugins](https://puppet.com/docs/bolt/latest/writing_plugins.html),
 and [Puppet functions](https://puppet.com/docs/puppet/latest/writing_custom_functions.html). Please
-consider if your use case can be solved with one of these tools before modifying Bolt itself.
+consider if your use case can be solved with one of these tools before modifying OpenBolt itself.
 
-There are certain types of improvements that we believe make sense in Bolt
+There are certain types of improvements that we believe make sense in OpenBolt
 itself:
 
 * New Transports. The transports API is a work-in-progress, but is something we
   aim to stabilize. Currently, transports can't be extended via modules, although
   in the future they likely will be.
-* Core functionality we believe makes Bolt a better tool, such as the
+* Core functionality we believe makes OpenBolt a better tool, such as the
   `aggregate` and `canary` plans included in `modules`.
 * New core functions
-    * New functions that use Bolt internals such as the Executor,
+    * New functions that use OpenBolt internals such as the Executor,
       Applicator, or Inventory should live in bolt-modules/boltlib.
-    * Other directories under bolt-modules are used to categorize Bolt's
+    * Other directories under bolt-modules are used to categorize OpenBolt's
       standard library functions.
 * New ways of interacting with plan progress and output, such as prompts to
   continue or output processors.
 
 ## Pull Requests
 
-Pull requests are welcome on GitHub: https://github.com/puppetlabs/bolt
-
-As with other open-source projects managed by Puppet, you must digitally sign
-the Contributor License Agreement before we can accept your pull request:
-https://cla.puppet.com
+Pull requests are welcome on GitHub: https://github.com/OpenVoxProject/openbolt
 
 **If this is your first time submitting a PR**:
-1. Fork the Bolt project (button in the top-right, next to 'star' and 'watch')
-1. Clone your fork of Bolt
-1. Add the puppetlabs repo as an upstream - `git remote add upstream
-   git@github.com:puppetlabs/bolt`
+1. Fork the OpenBolt project (button in the top-right, next to 'star' and 'watch')
+1. Clone your fork of OpenBolt
+1. Add the OpenVoxProject repo as an upstream - `git remote add upstream
+   git@github.com:openvoxproject/openbolt`
 1. Make a new branch off of main - `git checkout -b mybranchname`
 1. Commit your changes and add a useful commit message, including what
    specifically you changed and why - `git commit`
@@ -75,7 +69,7 @@ https://cla.puppet.com
       ```
 1. Push your changes to your branch on your fork - `git push origin
    mybranchname`
-1. Open a PR against main at https://github.com/puppetlabs/bolt
+1. Open a PR against main at https://github.com/OpenVoxProject/openbolt
 1. Ensure tests pass
 
 **If it's not your first PR:**
@@ -87,45 +81,45 @@ https://cla.puppet.com
    specifically you changed and why - `git commit`
 1. Push your changes to your branch on your fork - `git push origin
    mybranchname`
-1. Open a PR against main at https://github.com/puppetlabs/bolt
+1. Open a PR against main at https://github.com/OpenVoxProject/openbolt
 
-Once you've opened a PR the Bolt team will automatically be notified. We're a small team, but we do
+Once you've opened a PR the Vox Pupuli OpenBolt team will automatically be notified. We're a small team, but we do
 our best to review PRs in a timely manner.
 
-## Installing Bolt
+## Installing OpenBolt
 
-If you are interested in trying Bolt out or using it in production, we recommend
+If you are interested in trying OpenBolt out or using it in production, we recommend
 installing from a system package detailed in [Installing
 Bolt](https://puppet.com/docs/bolt/latest/bolt_installing.html). The following
 installation instructions are focused on developers who wish to contribute to
-Bolt.
+OpenBolt.
 
-Depending on your development workflow, you can install Bolt one of three ways:
+Depending on your development workflow, you can install OpenBolt one of three ways:
 
 * From [RubyGems](https://rubygems.org)
 * From your Gemfile with Bundler
 * From source
 
-Bolt vendors a version of Puppet that supports executing tasks and plans, so you
-do not need to install Puppet. If you happen to already have Puppet installed,
+OpenBolt vendors a version of OpenVox that supports executing tasks and plans, so you
+do not need to install OpenVox or Puppet. If you happen to already have OpenVox or Puppet installed,
 then the vendored version takes precedence and does not conflict with the
 already installed version.
 
 ### RubyGems install
 
 To install from [RubyGems](https://rubygems.org), run:
 
-    gem install bolt
+    gem install openbolt
 
 ### Bundler install
 
 To use [Bundler](https://bundler.io), add this to your Gemfile:
 
-    gem 'bolt'
+    gem 'openbolt'
 
-### Run Bolt from source
+### Run OpenBolt from source
 
-To run Bolt from source:
+To run OpenBolt from source:
 
     bundle install --path .bundle --without test
     bundle exec bolt ...

Gemfile

@@ -34,7 +34,7 @@ if File.exist? local_gemfile
   eval_gemfile local_gemfile
 end
 
-# https://github.com/OpenVoxProject/puppet/issues/90
+# https://github.com/OpenVoxProject/openvox/issues/90
 gem 'syslog', '~> 0.3' if RUBY_VERSION >= '3.4'
 
 gem 'puppet_metadata', '~> 5.3'

acceptance/README.md

@@ -23,16 +23,16 @@
 
 ## Description
 
-This acceptance suite allows you to test bolt using the following methods:
+This acceptance suite allows you to test OpenBolt using the following methods:
 
-* gem: Install bolt via gem from a gemsource defined as an environment
+* gem: Install OpenBolt via gem from a gemsource defined as an environment
  variable (defaults to https://gems.rubygems.org).
-* git: Install bolt via the git repo from a branch or SHA defined as
+* git: Install OpenBolt via the git repo from a branch or SHA defined as
  environment variables (defaults to #main/HEAD).
-* package: Install bolt via the puppet repos 
+* package: Install OpenBolt via the openvox repos 
 
 The tests assume the following [Beaker
-roles](https://github.com/puppetlabs/beaker/blob/master/docs/concepts/roles_what_are_they.md) be assigned to your SUT nodes:
+roles](https://github.com/voxpupuli/beaker/blob/master/docs/concepts/roles_what_are_they.md) be assigned to your SUT nodes:
 * `bolt`: This role defines the node that will act as the `bolt`
  controller node. There should be only one `bolt` node defined in a
  given Beaker hosts file.
@@ -42,7 +42,7 @@ roles](https://github.com/puppetlabs/beaker/blob/master/docs/concepts/roles_what
  connection protocol. Any number of nodes can be defined with this role.
 
 You might also need to specify nodes for
-[beaker-hostgenerator](https://github.com/puppetlabs/beaker-hostgenerator) to
+[beaker-hostgenerator](https://github.com/voxpupuli/beaker-hostgenerator) to
 use to test bolt on. You can see all of the available
 operatingsystem-architecture nodes by running
 ```
@@ -78,16 +78,16 @@ Setup will update passwords on targets to match this value after connecting via
 **BOLT_CONTOLLER** (Default `centos7-64bolt`): Operating system and
 architecture to be used for the node running `bolt`. This value should be one
 of the OS-architecture strings used by
-[beaker-hostgenerator](https://github.com/puppetlabs/beaker-hostgenerator)
+[beaker-hostgenerator](https://github.com/voxpupuli/beaker-hostgenerator)
 (i.e.`windows10ent-64`). See the [beaker-hostgenerator
-usage](https://github.com/puppetlabs/beaker-hostgenerator#usage) for more
+usage](https://github.com/voxpupuli/beaker-hostgenerator#usage) for more
 information about formatting, and see the [examples](#examples) below for
 examples. 
 
 **BOLT_NODES** (Default `ubuntu1604-64,osx1012-64,windows10ent-64`):
 Operating system and architecture to be used for the nodes targeted by the
 bolt tests. This value should be expressed in the notation used by
-[beaker-hostgenerator](https://github.com/puppetlabs/beaker-hostgenerator#usage).
+[beaker-hostgenerator](https://github.com/voxpupuli/beaker-hostgenerator#usage).
 Multiples should be hyphen separated. See [examples](#examples) below for
 examples.
 
@@ -192,14 +192,14 @@ bundle exec rake test:gem
 
 #### Git
 
-Example to test latest git commit to main on https://github.com/puppetlabs/bolt
+Example to test latest git commit to main on https://github.com/OpenVoxProject/openbolt
 ```
 SSH_PASSWORD='S3@ret3' \
 WINRM_PASSWORD='S3@ret3' \
 bundle exec rake test:git
 ```
 
-Example to test specific SHA on https://github.com/puppetlabs/bolt
+Example to test specific SHA on https://github.com/OpenVoxProject/openbolt
 ```
 GIT_SHA=309e197  \
 SSH_PASSWORD='S3@ret3' \

acceptance/lib/acceptance/bolt_setup_helper.rb

@@ -31,7 +31,7 @@ def git_server
     end
 
     def git_fork
-      ENV['GIT_FORK'] || 'puppetlabs/bolt'
+      ENV['GIT_FORK'] || 'OpenVoxProject/openbolt'
     end
 
     def git_branch