diff --git a/.github/workflows/org-metrics.yml b/.github/workflows/org-metrics.yml new file mode 100644 index 0000000..688db07 --- /dev/null +++ b/.github/workflows/org-metrics.yml @@ -0,0 +1,23 @@ +name: Metrics +on: + schedule: [{cron: "0 2 * * 3"}] + workflow_dispatch: +jobs: + github-metrics: + runs-on: ubuntu-latest + environment: + name: production + permissions: + contents: write + pull-requests: write + steps: + - uses: lowlighter/metrics@latest + with: + token: ${{ secrets.METRICS_TOKEN }} + user: puppetlabs + filename: profile/github-metrics.svg + output_action: pull-request-merge + plugin_languages: yes + plugin_followup: yes + plugin_rss: yes + plugin_rss_source: https://dev.to/feed/tag/puppet diff --git a/CODEOWNERS b/CODEOWNERS index b028270..be19b02 100644 --- a/CODEOWNERS +++ b/CODEOWNERS @@ -1 +1,4 @@ -* @puppetlabs/open-source-stewards +* @puppetlabs/open-source-stewards + +# All GitHub workflows and changes to them should be reviewed +/.github/workflows/ @puppetlabs/workflow-security-review diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index f947ee4..a1e3052 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -49,9 +49,8 @@ Notes: * People who are committing minor formatting / style infractions will get some education, rather than hammering them in the 3 strikes process. -Contact conduct@puppet.com to report abuse or appeal violations. This email list -goes to Kara Sowles (kara at puppet.com) and Katie Abbott (katie dot abbott at -puppet.com). In the case of appeals, we know that mistakes happen, and we’ll +Contact conduct@puppet.com to report abuse or appeal violations to our Community +Conduct team. In the case of appeals, we know that mistakes happen, and we’ll work with you to come up with a fair solution if there has been a misunderstanding. diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 563cccd..2f77d42 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -22,37 +22,50 @@ be added in modules. Exceptions would be things like new cross-OS providers and updates to existing core types. If you are unsure of whether your contribution should be implemented as a -module or part of Puppet Core, you may visit [#puppet-dev on slack](https://puppetcommunity.slack.com/), or ask on +module or part of Puppet Core, you may visit [#puppet-dev on slack](https://slack.puppet.com/), or ask on the [puppet-dev mailing list](https://groups.google.com/forum/#!forum/puppet-dev) for advice. ## Getting Started -* Make sure you have a [Jira account](https://tickets.puppetlabs.com). * Make sure you have a [GitHub account](https://github.com/signup/free). -* Submit a Jira ticket for your issue if one does not already exist. +* (Optional) Submit a GitHub Issue if one does not already exist. * Clearly describe the issue including steps to reproduce when it is a bug. * Make sure you fill in the earliest version that you know has the issue. - * A ticket is not necessary for [trivial changes](https://puppet.com/community/trivial-patch-exemption-policy) * Fork the repository on GitHub. ## Making Changes * Create a topic branch from where you want to base your work. - * This is usually the master branch. - * Only target release branches if you are certain your fix must be on that - branch. - * To quickly create a topic branch based on master, run `git checkout -b - fix/master/my_contribution master`. Please avoid working directly on the - `master` branch. -* Make commits of logical and atomic units. + * For new and active repositories, this is usually the `main` branch, but for + older or less active repos, the default branch may still be named `master`. + * Only target branches other than the default if you are certain your fix must + be on that branch. + * To quickly create a topic branch based on the default branch, run `git + checkout -b fix/main/my_contribution main` (or `master` for older repos). + Please avoid working directly on the default branch. +* Make commits of atomic units. + * Your commit message should clearly describe how the behavior is changing and why. + * Commit messages that say "fixes bug" or are empty will be rejected. + * If code changes cause tests to fail, then the tests should be updated in the + same commit as the code changes. + * Squash intermediate commits. + * Do not create merge commits in your pull request. Instead rebase your pull + request. For example, if your feature branch tracks `upstream/main`, then + run `git rebase $(git merge-base HEAD upstream/main) --onto upstream/main` + and force push to your remote `git push --force origin HEAD`. +* Make commits of logical units. + * Significant whitespace-only changes should be made in a single commit, not + comingled with non-whitespace changes. + * For significant changes, break down your work in separate commits to make it + easier to review. + * If your pull request contains multiple commits, then tests should pass at each + stage. To confirm, assuming your feature branch tracks `upstream/main`, then run + `git rebase -i $(git merge-base HEAD upstream/main) --exec 'bundle exec rake '` * Check for unnecessary whitespace with `git diff --check` before committing. -* Make sure your commit messages are in the proper format. If the commit - addresses an issue filed in the - [Puppet Jira project](https://tickets.puppetlabs.com/browse/PUP), start - the first line of the commit with the issue number in parentheses. +* Make sure your commit messages are in the proper format. We use the [50/72 rule](https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project) in commit messages. - ``` - (PUP-1234) Make the example in CONTRIBUTING imperative and concrete + ```text + Make the example in CONTRIBUTING imperative and concrete Without this patch applied the example commit message in the CONTRIBUTING document is not a concrete example. This is a problem because the @@ -60,72 +73,20 @@ the [puppet-dev mailing list](https://groups.google.com/forum/#!forum/puppet-dev based on a description rather than an example. This patch fixes the problem by making the example concrete and imperative. - The first line is a real-life imperative statement with a ticket number - from our issue tracker. The body describes the behavior without the patch, - why this is a problem, and how the patch fixes the problem when applied. + The first line is a real-life imperative statement. The body describes + the behavior without the patch, why this is a problem, and how the + patch fixes the problem when applied. ``` -* Make sure you have added the necessary tests for your changes. -* For details on how to run tests, please see [the quickstart guide](https://github.com/puppetlabs/puppet/blob/master/docs/quickstart.md) - -## Writing Translatable Code - -We use [gettext tooling](https://github.com/puppetlabs/gettext-setup-gem) to -extract user-facing strings and pull in translations based on the user's locale -at runtime. In order for this tooling to work, all user-facing strings must be -wrapped in the `_()` translation function, so they can be extracted into files -for the translators. - -When adding user-facing strings to your work, follow these guidelines: - -* Use full sentences. Strings built up out of concatenated bits are hard to translate. -* Use string formatting instead of interpolation. Use the hash format and give good names to the placeholder values that can be used by translators to understand the meaning of the formatted values. - For example: `_('Creating new user %{name}.') % { name: user.name }` -* Use `n_()` for pluralization. (see gettext gem docs linked above for details) - -It is the responsibility of contributors and code reviewers to ensure that all -user-facing strings are marked in new PRs before merging. -## Making Trivial Changes - -For [changes of a trivial nature](https://puppet.com/community/trivial-patch-exemption-policy), it is not always necessary to create a new -ticket in Jira. In this case, it is appropriate to start the first line of a -commit with one of `(docs)`, `(maint)`, or `(packaging)` instead of a ticket -number. - -If a Jira ticket exists for the documentation commit, you can include it -after the `(docs)` token. - -``` - (docs)(DOCUMENT-000) Add docs commit example to CONTRIBUTING - - There is no example for contributing a documentation commit - to the Puppet repository. This is a problem because the contributor - is left to assume how a commit of this nature may appear. - - The first line is a real-life imperative statement with '(docs)' in - place of what would have been the PUP project ticket number in a - non-documentation related commit. The body describes the nature of - the new documentation or comments added. -``` - -For commits that address trivial repository maintenance tasks or packaging -issues, start the first line of the commit with `(maint)` or `(packaging)`, -respectively. +* Make sure you have added the necessary tests for your changes. +* For details on how to run tests, please see [the quickstart guide](https://github.com/puppetlabs/puppet/blob/main/docs/quickstart.md) ## Submitting Changes -* Sign the [Contributor License Agreement](http://links.puppet.com/cla). * Push your changes to a topic branch in your fork of the repository. * Submit a pull request to the repository in the puppetlabs organization. -* Update your Jira ticket to mark that you have submitted code and are ready - for it to be reviewed (Status: Ready for Merge). - * Include a link to the pull request in the ticket. -* The core team looks at Pull Requests on a regular basis in a weekly triage - meeting that we hold in a public Google Hangout. The hangout is announced in - the weekly status updates that are sent to the puppet-dev list. Notes are - posted to the [Puppet Community community-triage - repo](https://github.com/puppet-community/community-triage/tree/master/core/notes) - and include a link to a YouTube recording of the hangout. + * Sign the CLA when prompted to via a PR comment. +* If a GitHub Issues exists [link to it](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) to indicate that your PR addresses this issue. * After feedback has been given we expect responses within two weeks. After two weeks we may close the pull request if it isn't showing any activity. @@ -144,10 +105,10 @@ of its discovery, the commit(s) responsible _may_ be reverted, at the discretion of the committer and Puppet maintainers. This action would be taken to help maintain passing states in our testing pipelines. -The original contributor will be notified of the revert in the Jira ticket -associated with the change. A reference to the test(s) and operating system(s) -that failed as a result of the code change will also be added to the Jira -ticket. This test(s) should be used to check future submissions of the code to +The original contributor will be notified of the revert in a comment the PR or +issue associated with the change. A reference to the test(s) and operating +system(s) that failed as a result of the code change will also be added to the +comment. This test(s) should be used to check future submissions of the code to ensure the issue has been resolved. ### Summary @@ -158,10 +119,8 @@ ensure the issue has been resolved. ## Additional Resources * [Puppet community guidelines](https://puppet.com/community/community-guidelines) -* [Bug tracker (Jira)](https://tickets.puppetlabs.com) -* [Contributor License Agreement](http://links.puppet.com/cla) +* [Contributor License Agreement](https://puppet.com/community/contributor-license-agreement) * [General GitHub documentation](https://help.github.com/) * [GitHub pull request documentation](https://help.github.com/articles/creating-a-pull-request/) -* #puppet-dev IRC channel on freenode.org ([Archive](https://botbot.me/freenode/puppet-dev/)) +* [Puppet Community Slack](https://slack.puppet.com) * [puppet-dev mailing list](https://groups.google.com/forum/#!forum/puppet-dev) -* [Community PR Triage notes](https://github.com/puppet-community/community-triage/tree/master/core/notes) diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..795087c --- /dev/null +++ b/LICENSE @@ -0,0 +1,427 @@ +Attribution-ShareAlike 4.0 International + +======================================================================= + +Creative Commons Corporation ("Creative Commons") is not a law firm and +does not provide legal services or legal advice. Distribution of +Creative Commons public licenses does not create a lawyer-client or +other relationship. Creative Commons makes its licenses and related +information available on an "as-is" basis. Creative Commons gives no +warranties regarding its licenses, any material licensed under their +terms and conditions, or any related information. Creative Commons +disclaims all liability for damages resulting from their use to the +fullest extent possible. + +Using Creative Commons Public Licenses + +Creative Commons public licenses provide a standard set of terms and +conditions that creators and other rights holders may use to share +original works of authorship and other material subject to copyright +and certain other rights specified in the public license below. The +following considerations are for informational purposes only, are not +exhaustive, and do not form part of our licenses. + + Considerations for licensors: Our public licenses are + intended for use by those authorized to give the public + permission to use material in ways otherwise restricted by + copyright and certain other rights. Our licenses are + irrevocable. Licensors should read and understand the terms + and conditions of the license they choose before applying it. + Licensors should also secure all rights necessary before + applying our licenses so that the public can reuse the + material as expected. Licensors should clearly mark any + material not subject to the license. This includes other CC- + licensed material, or material used under an exception or + limitation to copyright. More considerations for licensors: + wiki.creativecommons.org/Considerations_for_licensors + + Considerations for the public: By using one of our public + licenses, a licensor grants the public permission to use the + licensed material under specified terms and conditions. If + the licensor's permission is not necessary for any reason--for + example, because of any applicable exception or limitation to + copyright--then that use is not regulated by the license. Our + licenses grant only permissions under copyright and certain + other rights that a licensor has authority to grant. Use of + the licensed material may still be restricted for other + reasons, including because others have copyright or other + rights in the material. A licensor may make special requests, + such as asking that all changes be marked or described. + Although not required by our licenses, you are encouraged to + respect those requests where reasonable. More considerations + for the public: + wiki.creativecommons.org/Considerations_for_licensees + +======================================================================= + +Creative Commons Attribution-ShareAlike 4.0 International Public +License + +By exercising the Licensed Rights (defined below), You accept and agree +to be bound by the terms and conditions of this Creative Commons +Attribution-ShareAlike 4.0 International Public License ("Public +License"). To the extent this Public License may be interpreted as a +contract, You are granted the Licensed Rights in consideration of Your +acceptance of these terms and conditions, and the Licensor grants You +such rights in consideration of benefits the Licensor receives from +making the Licensed Material available under these terms and +conditions. + + +Section 1 -- Definitions. + + a. Adapted Material means material subject to Copyright and Similar + Rights that is derived from or based upon the Licensed Material + and in which the Licensed Material is translated, altered, + arranged, transformed, or otherwise modified in a manner requiring + permission under the Copyright and Similar Rights held by the + Licensor. For purposes of this Public License, where the Licensed + Material is a musical work, performance, or sound recording, + Adapted Material is always produced where the Licensed Material is + synched in timed relation with a moving image. + + b. Adapter's License means the license You apply to Your Copyright + and Similar Rights in Your contributions to Adapted Material in + accordance with the terms and conditions of this Public License. + + c. BY-SA Compatible License means a license listed at + creativecommons.org/compatiblelicenses, approved by Creative + Commons as essentially the equivalent of this Public License. + + d. Copyright and Similar Rights means copyright and/or similar rights + closely related to copyright including, without limitation, + performance, broadcast, sound recording, and Sui Generis Database + Rights, without regard to how the rights are labeled or + categorized. For purposes of this Public License, the rights + specified in Section 2(b)(1)-(2) are not Copyright and Similar + Rights. + + e. Effective Technological Measures means those measures that, in the + absence of proper authority, may not be circumvented under laws + fulfilling obligations under Article 11 of the WIPO Copyright + Treaty adopted on December 20, 1996, and/or similar international + agreements. + + f. Exceptions and Limitations means fair use, fair dealing, and/or + any other exception or limitation to Copyright and Similar Rights + that applies to Your use of the Licensed Material. + + g. License Elements means the license attributes listed in the name + of a Creative Commons Public License. The License Elements of this + Public License are Attribution and ShareAlike. + + h. Licensed Material means the artistic or literary work, database, + or other material to which the Licensor applied this Public + License. + + i. Licensed Rights means the rights granted to You subject to the + terms and conditions of this Public License, which are limited to + all Copyright and Similar Rights that apply to Your use of the + Licensed Material and that the Licensor has authority to license. + + j. Licensor means the individual(s) or entity(ies) granting rights + under this Public License. + + k. Share means to provide material to the public by any means or + process that requires permission under the Licensed Rights, such + as reproduction, public display, public performance, distribution, + dissemination, communication, or importation, and to make material + available to the public including in ways that members of the + public may access the material from a place and at a time + individually chosen by them. + + l. Sui Generis Database Rights means rights other than copyright + resulting from Directive 96/9/EC of the European Parliament and of + the Council of 11 March 1996 on the legal protection of databases, + as amended and/or succeeded, as well as other essentially + equivalent rights anywhere in the world. + + m. You means the individual or entity exercising the Licensed Rights + under this Public License. Your has a corresponding meaning. + + +Section 2 -- Scope. + + a. License grant. + + 1. Subject to the terms and conditions of this Public License, + the Licensor hereby grants You a worldwide, royalty-free, + non-sublicensable, non-exclusive, irrevocable license to + exercise the Licensed Rights in the Licensed Material to: + + a. reproduce and Share the Licensed Material, in whole or + in part; and + + b. produce, reproduce, and Share Adapted Material. + + 2. Exceptions and Limitations. For the avoidance of doubt, where + Exceptions and Limitations apply to Your use, this Public + License does not apply, and You do not need to comply with + its terms and conditions. + + 3. Term. The term of this Public License is specified in Section + 6(a). + + 4. Media and formats; technical modifications allowed. The + Licensor authorizes You to exercise the Licensed Rights in + all media and formats whether now known or hereafter created, + and to make technical modifications necessary to do so. The + Licensor waives and/or agrees not to assert any right or + authority to forbid You from making technical modifications + necessary to exercise the Licensed Rights, including + technical modifications necessary to circumvent Effective + Technological Measures. For purposes of this Public License, + simply making modifications authorized by this Section 2(a) + (4) never produces Adapted Material. + + 5. Downstream recipients. + + a. Offer from the Licensor -- Licensed Material. Every + recipient of the Licensed Material automatically + receives an offer from the Licensor to exercise the + Licensed Rights under the terms and conditions of this + Public License. + + b. Additional offer from the Licensor -- Adapted Material. + Every recipient of Adapted Material from You + automatically receives an offer from the Licensor to + exercise the Licensed Rights in the Adapted Material + under the conditions of the Adapter's License You apply. + + c. No downstream restrictions. You may not offer or impose + any additional or different terms or conditions on, or + apply any Effective Technological Measures to, the + Licensed Material if doing so restricts exercise of the + Licensed Rights by any recipient of the Licensed + Material. + + 6. No endorsement. Nothing in this Public License constitutes or + may be construed as permission to assert or imply that You + are, or that Your use of the Licensed Material is, connected + with, or sponsored, endorsed, or granted official status by, + the Licensor or others designated to receive attribution as + provided in Section 3(a)(1)(A)(i). + + b. Other rights. + + 1. Moral rights, such as the right of integrity, are not + licensed under this Public License, nor are publicity, + privacy, and/or other similar personality rights; however, to + the extent possible, the Licensor waives and/or agrees not to + assert any such rights held by the Licensor to the limited + extent necessary to allow You to exercise the Licensed + Rights, but not otherwise. + + 2. Patent and trademark rights are not licensed under this + Public License. + + 3. To the extent possible, the Licensor waives any right to + collect royalties from You for the exercise of the Licensed + Rights, whether directly or through a collecting society + under any voluntary or waivable statutory or compulsory + licensing scheme. In all other cases the Licensor expressly + reserves any right to collect such royalties. + + +Section 3 -- License Conditions. + +Your exercise of the Licensed Rights is expressly made subject to the +following conditions. + + a. Attribution. + + 1. If You Share the Licensed Material (including in modified + form), You must: + + a. retain the following if it is supplied by the Licensor + with the Licensed Material: + + i. identification of the creator(s) of the Licensed + Material and any others designated to receive + attribution, in any reasonable manner requested by + the Licensor (including by pseudonym if + designated); + + ii. a copyright notice; + + iii. a notice that refers to this Public License; + + iv. a notice that refers to the disclaimer of + warranties; + + v. a URI or hyperlink to the Licensed Material to the + extent reasonably practicable; + + b. indicate if You modified the Licensed Material and + retain an indication of any previous modifications; and + + c. indicate the Licensed Material is licensed under this + Public License, and include the text of, or the URI or + hyperlink to, this Public License. + + 2. You may satisfy the conditions in Section 3(a)(1) in any + reasonable manner based on the medium, means, and context in + which You Share the Licensed Material. For example, it may be + reasonable to satisfy the conditions by providing a URI or + hyperlink to a resource that includes the required + information. + + 3. If requested by the Licensor, You must remove any of the + information required by Section 3(a)(1)(A) to the extent + reasonably practicable. + + b. ShareAlike. + + In addition to the conditions in Section 3(a), if You Share + Adapted Material You produce, the following conditions also apply. + + 1. The Adapter's License You apply must be a Creative Commons + license with the same License Elements, this version or + later, or a BY-SA Compatible License. + + 2. You must include the text of, or the URI or hyperlink to, the + Adapter's License You apply. You may satisfy this condition + in any reasonable manner based on the medium, means, and + context in which You Share Adapted Material. + + 3. You may not offer or impose any additional or different terms + or conditions on, or apply any Effective Technological + Measures to, Adapted Material that restrict exercise of the + rights granted under the Adapter's License You apply. + + +Section 4 -- Sui Generis Database Rights. + +Where the Licensed Rights include Sui Generis Database Rights that +apply to Your use of the Licensed Material: + + a. for the avoidance of doubt, Section 2(a)(1) grants You the right + to extract, reuse, reproduce, and Share all or a substantial + portion of the contents of the database; + + b. if You include all or a substantial portion of the database + contents in a database in which You have Sui Generis Database + Rights, then the database in which You have Sui Generis Database + Rights (but not its individual contents) is Adapted Material, + including for purposes of Section 3(b); and + + c. You must comply with the conditions in Section 3(a) if You Share + all or a substantial portion of the contents of the database. + +For the avoidance of doubt, this Section 4 supplements and does not +replace Your obligations under this Public License where the Licensed +Rights include other Copyright and Similar Rights. + + +Section 5 -- Disclaimer of Warranties and Limitation of Liability. + + a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE + EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS + AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF + ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, + IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, + WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR + PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, + ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT + KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT + ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. + + b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE + TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, + NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, + INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, + COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR + USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN + ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR + DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR + IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + + c. The disclaimer of warranties and limitation of liability provided + above shall be interpreted in a manner that, to the extent + possible, most closely approximates an absolute disclaimer and + waiver of all liability. + + +Section 6 -- Term and Termination. + + a. This Public License applies for the term of the Copyright and + Similar Rights licensed here. However, if You fail to comply with + this Public License, then Your rights under this Public License + terminate automatically. + + b. Where Your right to use the Licensed Material has terminated under + Section 6(a), it reinstates: + + 1. automatically as of the date the violation is cured, provided + it is cured within 30 days of Your discovery of the + violation; or + + 2. upon express reinstatement by the Licensor. + + For the avoidance of doubt, this Section 6(b) does not affect any + right the Licensor may have to seek remedies for Your violations + of this Public License. + + c. For the avoidance of doubt, the Licensor may also offer the + Licensed Material under separate terms or conditions or stop + distributing the Licensed Material at any time; however, doing so + will not terminate this Public License. + + d. Sections 1, 5, 6, 7, and 8 survive termination of this Public + License. + + +Section 7 -- Other Terms and Conditions. + + a. The Licensor shall not be bound by any additional or different + terms or conditions communicated by You unless expressly agreed. + + b. Any arrangements, understandings, or agreements regarding the + Licensed Material not stated herein are separate from and + independent of the terms and conditions of this Public License. + + +Section 8 -- Interpretation. + + a. For the avoidance of doubt, this Public License does not, and + shall not be interpreted to, reduce, limit, restrict, or impose + conditions on any use of the Licensed Material that could lawfully + be made without permission under this Public License. + + b. To the extent possible, if any provision of this Public License is + deemed unenforceable, it shall be automatically reformed to the + minimum extent necessary to make it enforceable. If the provision + cannot be reformed, it shall be severed from this Public License + without affecting the enforceability of the remaining terms and + conditions. + + c. No term or condition of this Public License will be waived and no + failure to comply consented to unless expressly agreed to by the + Licensor. + + d. Nothing in this Public License constitutes or may be interpreted + as a limitation upon, or waiver of, any privileges and immunities + that apply to the Licensor or You, including from the legal + processes of any jurisdiction or authority. + + +======================================================================= + +Creative Commons is not a party to its public licenses. +Notwithstanding, Creative Commons may elect to apply one of its public +licenses to material it publishes and in those instances will be +considered the β€œLicensor.” The text of the Creative Commons public +licenses is dedicated to the public domain under the CC0 Public Domain +Dedication. Except for the limited purpose of indicating that material +is shared under a Creative Commons public license or as otherwise +permitted by the Creative Commons policies published at +creativecommons.org/policies, Creative Commons does not authorize the +use of the trademark "Creative Commons" or any other trademark or logo +of Creative Commons without its prior written consent including, +without limitation, in connection with any unauthorized modifications +to any of its public licenses or any other arrangements, +understandings, or agreements concerning use of licensed material. For +the avoidance of doubt, this paragraph does not form part of the public +licenses. + +Creative Commons may be contacted at creativecommons.org. diff --git a/profile/Community-Marquee-1792x768.png b/profile/Community-Marquee-1792x768.png new file mode 100644 index 0000000..291f4c5 Binary files /dev/null and b/profile/Community-Marquee-1792x768.png differ diff --git a/profile/README.md b/profile/README.md new file mode 100644 index 0000000..544a230 --- /dev/null +++ b/profile/README.md @@ -0,0 +1,52 @@ +## Welcome to the Puppet community πŸ‘‹ + +![Puppet folk having a grand time at Portland's annual Pride parade.](https://raw.githubusercontent.com/puppetlabs/.github/main/profile/Community-Marquee-1792x768.png) + +Metrics + +At Puppet, open source software is in our DNA. From the earliest days of Facter to the latest version of Bolt, we’ve always been firm believers in the power of open source. We have a supportive, active community of thousands of people just like you who are making Puppet better β€” and making IT a better place to work. + + +### πŸŽͺ An interconnected community + +You can get involved in the [Puppet community](https://puppet.com/community/) by connecting at events, getting or giving help in any of our many channels, sharing modules on the Forge, contributing code, docs, or any of your valuable insights--and many other ways, too! However you decide to jump in, we know you’ll learn a lot and enjoy meeting the smart, friendly people who make up the Puppet community. Maybe you'll even fall in with our good friends at [🦊 Vox Pupuli](https://voxpupuli.org)! + +- πŸ’¬ https://puppetcommunity.slack.com +- 🎫 https://tickets.puppet.com +- πŸ› οΈ https://forge.puppet.com +- 🦊 https://voxpupuli.org +- πŸŽ™ https://dev.to/puppet +- 🐘 https://fosstodon.org/@puppet +- πŸ‘©β€πŸ’» https://github.com/puppetlabs/community/discussions +- πŸ“° https://dev.to/feed/tag/puppet + +Don't forget that all participation is governed by our [Code of conduct](https://pup.pt/conduct). + +### 🎁 Contributing to the ecosystem + +Community contributions are awesome and part of the way that we make sure that our tools continue to solve your problems. We want to keep it as easy as possible to participate and make contributions. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things, of course! + +Most of our projects will use our standard [contribution guidelines](https://github.com/puppetlabs/.github/blob/main/CONTRIBUTING.md), but you should check individual repositories for a more specific guide before submitting a PR. + +### 🎟️ Reporting issues + +We have moved exclusively to GitHub Issues for reporting problems with any of our products. For open source products, you'll simply use their corresponding repositories. Some of the most common ones: + * [Puppet](https://github.com/puppetlabs/puppet) + * [Bolt](https://github.com/puppetlabs/bolt) + * [Facter](https://github.com/puppetlabs/facter) + * [PuppetDB](https://github.com/puppetlabs/puppetdb) + * [Puppet Server](https://github.com/puppetlabs/puppetserver) + * [Puppet Modules](https://github.com/search?q=topic%3Amodule+org%3Apuppetlabs+fork%3Atrue&type=Repositories) (take note of the support status) + +Some products, like Puppet Enterprise itself, are developed internally. These now have corresponding GitHub repositories that are currently only used for issue reporting. + * [Puppet Forge](https://github.com/puppetlabs/forge_issues) + * [Puppet Enterprise](https://github.com/puppetlabs/puppet-enterprise_issues) + * [CEM Modules](https://github.com/puppetlabs/cem_issues) + * [Puppet Documentation](https://github.com/puppetlabs/puppet-docs) + +### πŸ’» Wanna come work with us? + +Check out our πŸ“œ [job listings](https://www.perforce.com/careers) and see what strikes your fancy. + + + diff --git a/profile/github-metrics.svg b/profile/github-metrics.svg new file mode 100644 index 0000000..069091a --- /dev/null +++ b/profile/github-metrics.svg @@ -0,0 +1,342 @@ + + + + + + + +
+
+

+ + Puppet +

+
+
+
+ + + + Joined GitHub 15 years ago +
+
+ + + + Portland, OR +
+
+
+
+ + + + 9 members +
+
+ + + + Verified +
+
+
+
+
+
+
+

+ + + + 717 Repositories +

+
+
+
+ + + + Prefers Apache-2.0 license +
+
+ + + + 291 Releases +
+
+ + + + 2 Packages +
+
+ + + + 3.85 GB used +
+
+
+
+ + + + 0 Sponsors +
+
+ + + + 10709 Stargazers +
+
+ + + + 5993 Forkers +
+
+ + + + 2654 Watchers +
+
+
+
+
+
+
+

+ + + + Overall issues and pull requests status +

+
+
+

On Puppet's repositories

+
+
+

Issues

+ + + + + + + + + + + + + + +
+
+ + + + + 392 open +
+
+ + + + + 2261 closed +
+
+ + + + 0 drafts +
+
+ + + + 0 skipped +
+
+
+
+

Pull requests

+ + + + + + + + + + + + + + +
+
+ + + + 226 open +
+
+ + + + 19020 merged +
+
+ + + + + 0 drafts +
+
+ + + + 5362 closed +
+
+
+
+
+
+

+ + + + 13 Languages +

+
+
+

Most used languages

+ + + + + + + + + + + + + + +
+
+ + + + HTML +
+
+ + + + Ruby +
+
+ + + + Puppet +
+
+ + + + JavaScript +
+
+ + + + CSS +
+
+ + + + SCSS +
+
+ + + + Shell +
+
+ + + + PowerShell +
+
+
+
+

+ + + + DEV Community: puppet RSS feed +

+
+
+
+ + + +
+
PDK 3.6.1 patch release available!
+
13 Jan 2026
+
+
+
+ + + +
+
Puppet with Foreman - Pilot
+
11 Jan 2026
+
+
+
+ + + +
+
Puppetlabs Modules Roundup – December 2025
+
7 Jan 2026
+
+
+
+ + + +
+
End-to-End BNPL App Development Solutions: Architecture, APIs & Compliance
+
7 Jan 2026
+
+
+
+
+
+
+ Last updated 14 Jan 2026, 02:44:21 with lowlighter/metrics@3.34.0 +
+
+
+ + \ No newline at end of file