WebSVN – Moodle – Diff – /lib/plist/CONTRIBUTING.md

-# 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.
+Welcome to our ever-growing community :octocat:!
 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.
             - 4.2.3.1 [Rules to Follow](#4.2.3.1)
             - 4.2.3.2 [Commit Format](#4.2.3.2)
                 - 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)
         - 4.2.4 [Push your Changes](#4.2.4)
         - 4.2.5 [Create a Pull Request](#4.2.5)
 - 6 [Coding Rules](#6)
 # <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.
-# <a name="2"></a> 2. Assistance [:top:](#top)
 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.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"></a> 2. Assistance [:top:](#top)
-## <a name="2.2"></a> 2.2 Customers Assistance
+## <a name="2.1"></a> 2.1 Contact us
-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)
 * :warning: **Observed Results:** A brief description of the problem.
 * :mag_right: **What steps will reproduce the issue?:** If suitable, including the steps required to reproduce the bug.
 * :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).
 ---
 >**Example for `<description>`**:
 >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.5"></a> 4.2.5 Create a Pull Request
 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)
 >:point_right:Added a Table of Content for the Contributing Guideline Document.:point_left:
 ---
 ### <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.
 To ensure consistency throughout the source code, keep these rules in mind as you are working:
 * All features or bug fixes must be tested by one or more specs (unit-tests).
-* All methods must be documented.
 * All methods must be documented.

Proyectos de Subversion Moodle

(root)/lib/plist/CONTRIBUTING.md – Rev 1 → 1441