[repo] Update ownership and links to point here

moodlehq · Jan 24, 2025 · 3da83d0 · 3da83d0
1 parent c45730a
commit 3da83d0
Show file tree

Hide file tree

Showing 5 changed files with 49 additions and 52 deletions.
diff --git a/.github/settings.yml b/.github/settings.yml
@@ -1,7 +1,7 @@
 repository:
   name: CFPropertyList
   description: PHP Implementation of Apple's PList (binary and xml)
-  homepage: http://teclib.github.io/CFPropertyList/
+  homepage: http://moodlehq.github.io/CFPropertyList/
   topics: apple, plist
   private: false
   has_issues: true
@@ -43,4 +43,4 @@ labels:
   - name: help wanted
     color: 33aa3f
   - name: good first issue
-    color: 7057ff
+    color: 7057ff
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -32,12 +32,6 @@ Project maintainers have the right and responsibility to remove, edit, or reject
 
 This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
 
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. 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.
-
 ## Attribution
 
 This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -1,12 +1,10 @@
-# How to contribute to Teclib' CFPropertyList
+# How to contribute to Moodle HQ's CFPropertyList
 
 Welcome to our ever-growing community :octocat:!
 
-Teclib’ is an open source software editor that offers a vast range of fully integrated open source technology packages, to better respond to business needs.
-
 We are more than happy to accept external contributions to the project in the form of feedback, translations, bug reports, and even better, pull requests.
 
-We present you here the guidelines to start contributing in any of the Teclib' projects.
+We present you here the guidelines to start contributing to this project.
 
 # <a name="top"></a>Table of contents
 
@@ -37,7 +35,7 @@ We present you here the guidelines to start contributing in any of the Teclib' p
                 - 4.2.3.2.1 [Header: Writing a `type`](#4.2.3.2.1)
                 - 4.2.3.2.2 [Header: Writing the `(optional scope)`](#4.2.3.2.2 )
                 - 4.2.3.2.3 [Header: Writing a `description`](#4.2.3.2.3)
-                - 4.2.3.2.4 [Header Lenght](#4.2.3.2.4)
+                - 4.2.3.2.4 [Header Length](#4.2.3.2.4)
                 - 4.2.3.2.5 [Writing the `optional body`](#4.2.3.2.5)
                 - 4.2.3.2.6 [Writing the `optional footer`](#4.2.3.2.6)
             - 4.2.3.3 [Commit Examples](#4.2.3.3)
@@ -55,33 +53,30 @@ We present you here the guidelines to start contributing in any of the Teclib' p
 # <a name="1"></a> 1. See what's going on! [:top:](#top)
 
 ## <a name="1.1"></a> 1.1 Issue Dashboard
-If you want to know all the issues we're dealing with right now, take a look at our [Issue Dashboard](https://github.com/TECLIB/CFPropertyList/issues) and look for areas in which you can help.
+If you want to know all the issues we're dealing with right now, take a look at our [Issue Dashboard](https://github.com/moodlehq/CFPropertyList/issues) and look for areas in which you can help.
 
 
 ## <a name="1.2"></a> 1.2 Pull Request Dashboard
-If you want to give us a hand solving issues then great, take a look at our [Pull Request Dashboard](https://github.com/TECLIB/CFPropertyList/pulls) and check for an open or closed PR. We don’t want to duplicate efforts.
+If you want to give us a hand solving issues then great, take a look at our [Pull Request Dashboard](https://github.com/moodlehq/CFPropertyList/pulls) and check for an open or closed PR. We don’t want to duplicate efforts.
 
 # <a name="2"></a> 2. Assistance [:top:](#top)
 
 ## <a name="2.1"></a> 2.1 Contact us
-You can contact us through any of our channels, check our [Contact section](http://www.teclib-edition.com/en/contact-us/)
-
-## <a name="2.2"></a> 2.2 Customers Assistance
-Use our official [support channel](https://support.teclib.com/).
+You can contact us through any of our channels, check our [Contact section](https://moodledev.io/general/channels)
 
 # <a name="3"></a> 3. Feature Requests [:top:](#top)
 
 ## <a name="3.1"></a> 3.1 Requirement for a Feature Request
-If you like to _implement_ a new feature please [submit an Issue](https://github.com/TECLIB/CFPropertyList/issues/new) with a proposal, so we can be sure it's relevant.
+If you like to _implement_ a new feature please [submit an Issue](https://github.com/moodlehq/CFPropertyList/issues/new) with a proposal, so we can be sure it's relevant.
 
 ### <a name="3.1.1"></a> 3.1.1 Major Feature Request
-For a major new feature request, [open an Issue](https://github.com/TECLIB/CFPropertyList/issues/new) and outline your proposal so it can be discussed.
+For a major new feature request, [open an Issue](https://github.com/moodlehq/CFPropertyList/issues/new) and outline your proposal so it can be discussed.
 
 ### <a name="3.1.2"></a> 3.1.2 Minor Feature Request
-For a minor new feature request, you can craft it and directly [submit it as a Pull Request](https://github.com/TECLIB/CFPropertyList/pulls), we'll take care of it.
+For a minor new feature request, you can craft it and directly [submit it as a Pull Request](https://github.com/moodlehq/CFPropertyList/pulls), we'll take care of it.
 
 ## <a name="3.2"></a> 3.2 Request a New Feature
-You can request a new feature by [submitting an Issue](https://github.com/TECLIB/CFPropertyList/issues/new)
+You can request a new feature by [submitting an Issue](https://github.com/moodlehq/CFPropertyList/issues/new)
 
 # <a name="4"></a> 4. Submitting [:top:](#top)
 
@@ -92,10 +87,10 @@ A good Issue/Bug report shouldn't leave others needing to chase you up for more
 A bug is a _demonstrable problem_ that is caused by the code in the repository. Good bug reports are extremely helpful, here are steps to follow to build a good one:
 
 ### <a name="4.1.1"></a> 4.1.1 Check for Past Issues or Bugs
-Before submitting the issue please check the [Issue Tracker](https://github.com/TECLIB/CFPropertyList/issues/), maybe the issue/bug was already reported by another contributor. By doing this you help us maximize the effort spent on solving problems and the addition of new features.
+Before submitting the issue please check the [Issue Tracker](https://github.com/moodlehq/CFPropertyList/issues/), maybe the issue/bug was already reported by another contributor. By doing this you help us maximize the effort spent on solving problems and the addition of new features.
 
 ### <a name="4.1.2"></a> 4.1.2 Try to Reproduce It!
-Try to reproduce this issue/bug using the latest `develop` branch in the repository [Check it here](https://github.com/TECLIB/CFPropertyList/branches).
+Try to reproduce this issue/bug using the latest `develop` branch in the repository [Check it here](https://github.com/moodlehq/CFPropertyList/branches).
 
 ### <a name="4.1.3"></a> 4.1.3 Isolate the Problem
 Ideally, create a reduced test case. We prefer bug reports with small, portable test cases.
@@ -108,7 +103,7 @@ We require the following information:
 * :boom: **Expected Results:** What did you expect to happen?
 
 ### <a name="4.1.5"></a> 4.1.5 Submit an Issue. :rocket:
-Having all data at hand, file the new issue by filling out our [Issue form](https://github.com/TECLIB/CFPropertyList/issues/new).
+Having all data at hand, file the new issue by filling out our [Issue form](https://github.com/moodlehq/CFPropertyList/issues/new).
 
 **&mdash; That's it! :tada:**
 
@@ -196,7 +191,7 @@ A description must immediately follow the **`type(optional scope):`** The descri
 >feat(parser)::point_right:add ability to parse arrays:point_left:
 ---
 
-### <a name="4.2.3.2.4"></a> 4.2.3.2.4 Header Lenght
+### <a name="4.2.3.2.4"></a> 4.2.3.2.4 Header Length
 The **header** cannot be longer than 100 characters. This allows the message to be easier to read on GitHub as well as in various git tools.
 
 ### <a name="4.2.3.2.5"></a> 4.2.3.2.5 Writing the `optional body`
@@ -253,7 +248,7 @@ After working on your changes you need to Push it (upload) your **newly created
 
 Pull requests or PR are **proposed changes** to a repository submitted by a user and accepted or rejected by a repository's collaborators.
 
-After all the work being pushed to the newly created branch, In GitHub, send a pull request to our [repository.](https://github.com/TECLIB/CFPropertyList/pulls)
+After all the work being pushed to the newly created branch, In GitHub, send a pull request to our [repository.](https://github.com/moodlehq/CFPropertyList/pulls)
 
 ### <a name="4.2.5.1"></a> 4.2.5.1 How to Write a Title for a Pull Request
 Pull Request should be named in reference to the main fix or feature you provide; minor information can be added to the description. Please be specific and don't use generic terms.
@@ -281,9 +276,9 @@ Pull Request should be named in reference to the main fix or feature you provide
 
 ### <a name="4.2.5.2"></a> 4.2.5.2 Before Send a Pull Request
 
-**1 - Pull Request Description:** Write a description about the changes, we provide a [template](https://github.com/TECLIB/CFPropertyList/community) for Pull Request descriptions. When you're creating a Pull Request it'll be shown automatically. Just fill it out and you're done.
+**1 - Pull Request Description:** Write a description about the changes, we provide a [template](https://github.com/moodlehq/CFPropertyList/community) for Pull Request descriptions. When you're creating a Pull Request it'll be shown automatically. Just fill it out and you're done.
 
-**2 - Choose the right label**: Look at the [list of available labels.](https://github.com/TECLIB/CFPropertyList/issues/labels)
+**2 - Choose the right label**: Look at the [list of available labels.](https://github.com/moodlehq/CFPropertyList/issues/labels)
 
 **3 - Smash that button!** Press that _Create Pull Request_ button and you're done.
 
@@ -377,4 +372,4 @@ To ensure consistency throughout the source code, keep these rules in mind as yo
 * All features or bug fixes must be tested by one or more specs (unit-tests).
 * All methods must be documented.
 
-# Good luck! :tada:
+# Good luck! :tada:
diff --git a/README.md b/README.md
@@ -1,16 +1,9 @@
 # CFPropertyList
 
-![Teclib' Banner](https://user-images.githubusercontent.com/29282308/31669540-abed67a8-b355-11e7-98e2-0ad190f37088.png)
-
 [![License MIT](https://img.shields.io/badge/License-MIT-blue.svg)](./LICENSE.md)
-[![Follow twitter](https://img.shields.io/badge/Twitter-Teclib%27-940CA5.svg)](https://twitter.com/teclib)
 [![Project Status: Active](http://www.repostatus.org/badges/latest/active.svg)](http://www.repostatus.org/#active)
 [![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)
 
-Teclib’ is an open source software editor that offers a vast range of fully integrated open source technology packages, to better respond to business needs.
-
-Visit our Website [Teclib'](http://www.teclib-edition.com/en/).
-
 ## Table of Contents
 
 * [Synopsis](#synopsis)
@@ -34,33 +27,39 @@ Although you might want to deliver data to your iPhone application, you might wa
 
 |**Release channel**|Beta Channel|
 |:---:|:---:|
-|![unit tests](https://github.com/TECLIB/CFPropertyList/actions/workflows/run_tests.yml/badge.svg?branch=master)|![unit tests](https://github.com/TECLIB/CFPropertyList/actions/workflows/run_tests.yml/badge.svg?branch=develop)|
+|![unit tests](https://github.com/moodlehq/CFPropertyList/actions/workflows/run_tests.yml/badge.svg?branch=master)|![unit tests](https://github.com/moodlehq/CFPropertyList/actions/workflows/run_tests.yml/badge.svg?branch=develop)|
 
 ## Installation
 
-See or [How to install article](https://teclib.github.io/CFPropertyList/howtos/installation).
+See or [How to install article](https://moodlehq.github.io/CFPropertyList/howtos/installation).
 
 ## Documentation
 
-We maintain a detailed documentation of the project on the Website, check the Development [Development](https://teclib.github.io/CFPropertyList/) and [How-tos](https://teclib.github.io/CFPropertyList/howtos) sections.
+We maintain a detailed documentation of the project on the Website, check the Development [Development](https://moodlehq.github.io/CFPropertyList/) and [How-tos](https://moodlehq.github.io/CFPropertyList/howtos) sections.
 
 ## Versioning
 
 In order to provide transparency on our release cycle and to maintain backward compatibility, Flyve MDM is maintained under [the Semantic Versioning guidelines](http://semver.org/). We are committed to following and complying with the rules, the best we can.
 
-See [the tags section of our GitHub project](https://github.com/TECLIB/CFPropertyList/tags) for changelogs for each release version. Release announcement posts on [the official Teclib' blog](http://www.teclib-edition.com/en/communities/blog-posts/) contain summaries of the most noteworthy changes made in each release.
+See [the tags section of our GitHub project](https://github.com/moodlehq/CFPropertyList/tags) for changelogs for each release version.
 
 ## Contact
 
-You can contact us through any of our channels, check our [Contact section](http://www.teclib-edition.com/en/contact-us/)
+You can contact us through any of our channels, check our [Support channels](https://moodledev.io/general/channels)
 
 ## Contribute
 
 Want to file a bug, contribute some code, or improve documentation? Excellent! Read up on our
-guidelines for [contributing](./CONTRIBUTING.md) and then check out one of our issues in the [Issues Dashboard](https://github.com/TECLIB/CFPropertyList/issues).
+guidelines for [contributing](./CONTRIBUTING.md) and then check out one of our issues in the [Issues Dashboard](https://github.com/moodlehq/CFPropertyList/issues).
 
 ## Copying
 
 * **Code**: you can redistribute it and/or modify
     it under the terms of the MIT License ([MIT](https://opensource.org/licenses/MIT)).
-* **Documentation**: released under Attribution 4.0 International ([CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)).
+* **Documentation**: released under Attribution 4.0 International ([CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)).
+
+## History
+
+This repository was previously maintained by [Teclib](https://github.com/TECLIB/CFPropertyList/) but was archived. We thanks Teclib for their years of work work maintaining this project
+
+Please note that several attempts were made to contact Teclib regarding a transfer of ownership but our contact went unanswered.
diff --git a/composer.json b/composer.json
@@ -1,16 +1,26 @@
 {
-    "name": "rodneyrehm/plist",
+    "name": "moodlehq/cfpropertylist",
     "description": "Library for reading and writing Apple's CFPropertyList (plist) files in XML as well as binary format.",
     "keywords": ["Core Foundation", "CFPropertyList", "plist", "apple", "xml", "binary"],
     "type": "library",
-    "homepage": "https://github.com/TECLIB/CFPropertyList",
+    "homepage": "https://github.com/moodlehq/CFPropertyList",
     "license": "MIT",
     "require": {
         "php": "^7.4 || ^8.0",
         "ext-dom": "*",
         "ext-libxml": "*"
     },
     "authors": [
+        {
+            "name": "Andrew Lyons",
+            "email": "[email protected]",
+            "role": "developer"
+        },
+        {
+            "name": "Andrew Gosali",
+            "email": "[email protected]",
+            "role": "developer"
+        },
         {
             "name": "Christian Kruse",
             "email": "[email protected]",
@@ -28,11 +38,10 @@
       }
  ],
     "support": {
-        "issues": "https://github.com/TECLIB/CFPropertyList/issues",
-        "source": "https://github.com/TECLIB/CFPropertyList",
-        "email": "[email protected]",
-        "docs": "http://teclib.github.io/CFPropertyList/howtos/",
-        "rss": "https://teclib.github.io/CFPropertyList/feed.xml"
+        "issues": "https://github.com/moodlehq/CFPropertyList/issues",
+        "source": "https://github.com/moodlehq/CFPropertyList",
+        "docs": "http://moodlehq.github.io/CFPropertyList/howtos/",
+        "rss": "https://moodlehq.github.io/CFPropertyList/feed.xml"
     },
     "autoload": {
         "psr-4": {