[DOC] Contributor docs update (#2554)

* contributing docs update

* contributing docs update 2

* typos

* Update contributing.md

new section

* Update testing.md

testing update

* Update contributing.md

dont steal code

* Automatic `pre-commit` fixes

* Update contributing.md

if

---------

Co-authored-by: MatthewMiddlehurst <25731235+MatthewMiddlehurst@users.noreply.github.com>
Co-authored-by: Antoine Guillaume <antoine.guillaume45@gmail.com>

Author: MatthewMiddlehurst

.github/PULL_REQUEST_TEMPLATE.md

@@ -51,7 +51,7 @@ not applicable. To check a box, replace the space inside the square brackets wit
 -->
 
 ##### For all contributions
-- [ ] I've added myself to the [list of contributors](https://github.com/aeon-toolkit/aeon/blob/main/.all-contributorsrc). Alternatively, you can use the [@all-contributors](https://allcontributors.org/docs/en/bot/usage) bot to do this for you after the PR has been merged.
+- [ ] I've added myself to the [list of contributors](https://github.com/aeon-toolkit/aeon/blob/main/.all-contributorsrc). Alternatively, you can use the [@all-contributors](https://allcontributors.org/docs/en/bot/usage) bot to do this for you **after** the PR has been merged.
 - [ ] The PR title starts with either [ENH], [MNT], [DOC], [BUG], [REF], [DEP] or [GOV] indicating whether the PR topic is related to enhancement, maintenance, documentation, bugs, refactoring, deprecation or governance.
 
 ##### For new estimators and functions

docs/contributing.md

@@ -5,7 +5,7 @@ kinds of contributions, not just code. Improvements to docs, bug reports, and ta
 on communications or code of conduct responsibilities are all examples of valuable
 contributions beyond code which help make `aeon` a great package.
 
-Please consider whether you will be able to tackle and issue or pull request before
+Please consider whether you will be able to tackle and issue or pull request (PR) before
 assigning yourself to it. If the issue requires editing Python code, you should have
 some experience with Python and be able to run tests. If the issue tackles the
 specifics of a machine learning algorithm, some relevant knowledge of machine learning
@@ -14,9 +14,22 @@ of knowledge is required to make a meaningful contribution to certain issues.
 ChatGPT is not a replacement for this knowledge.
 
 Pull requests from unknown contributors which do not attempt to resolve the issue being
-addressed, completely disregard the pull request template, or consist of low quality AI
+addressed, completely disregard the PR template, or consist of low quality AI
 generated output may be closed without review.
 
+When implementing new algorithms, developers may require some benchmarking
+against alternative implementations or published results. This is likely to
+be the case for complex published algorithms which are not contributed by trusted
+developers or the original authors. A developer may eventually do this themselves if the
+contributor is unable to, but this is a time-consuming process and may delay the
+merging of the PR significantly. Please be aware of this when assigning
+yourself to an issue for such algorithms.
+
+When using code from another package or writing code inspired from another implementation,
+please mention this in your PR. At the very least credit must be given where
+applicable. If the package has a different license, using the code as is may not be
+acceptable. Using others code without credit will like result in your PR being closed.
+
 In the following we will give a brief overview of how to contribute to `aeon`. Making
 contributions to open-source projects takes a bit of proactivity and can be daunting at
 first, but members of the community are here to help and answer questions. If you get
@@ -36,7 +49,8 @@ list may be a good place to start.
 it. **First ensure that the issue is not already being worked on. Look if there are any
 linked PRs and search the issue number in the pull requests list.**
 To assign yourself an **Issue/Pull Request**, please post a comment in the issue
-including '@aeon-actions-bot', the username of people to assign and the word `assign`:
+including '@aeon-actions-bot', the username of people to assign and the word `assign`
+(Please note that anyone @'ed in the comment will be assigned to the issue):
 
     For example:
     ```python
@@ -58,6 +72,9 @@ be patient, as Core Developers are volunteers and may be busy with other tasks o
 outside the package. It could take a while to get a review during
 slow periods, so please do not rush to @ developers or repeatedly ask for a review.
 Consider opening the PR as a draft until it is ready for review and passing tests.
+7. Respond to reviews if applicable. If you disagree with a change, discuss with the reviewer
+Push code as required. Please avoid force-pushing code unless necessary, as this can make
+reviewing more difficult and interacts poorly with some CI elements.
 8. Once your PR is approved, it will be merged into the `aeon` repository. Thanks for
 making a contribution! Make sure you are included in the [list of contributors](contributors.md).
 
@@ -83,6 +100,17 @@ Alternatively, you can use the [@all-contributors](https://allcontributors.org/d
 bot to do this for you. If the contribution is contained in a PR, please only @ the bot
 when the PR has been merged. A list of relevant tags can be found [here](https://allcontributors.org/docs/en/emoji-key).
 
+## Joining `aeon` as a Core Developer
+
+`aeon` Core Developers have write access to the repository and the ability to vote on
+community decisions. For more details on this role, please refer to the
+[about](about.md) and [governance](governance.md) pages.
+
+If you would like to become a Core Developer, the best way is to reach out and express
+your interest. We are particularly open to dedicated contributors who have made
+high-quality contributions to the project, as well as time series researchers and
+industry professionals.
+
 ## Further Reading
 
 For further information on contributing to `aeon`, please see the following pages.

docs/developer_guide/testing.md

@@ -166,7 +166,8 @@ The `aeon` PR testing workflow runs on every PR to the main branch. By default,
 will run a constrained set of tests excluding some tests such as those which
 are noticeably expensive or prone to failure (i.e. I/O from external sources).
 The estimators run will also be split into smaller subsets to spread them over
-different Python version and operating system combinations. This is controlled by the
+different Python version and operating system combinations. This can result in failures
+in some runs (likely 3), while others pass without issue. This is controlled by the
 `PR_TESTING` flag in [`testing/testing_config.py`](https://github.com/aeon-toolkit/aeon/blob/main/aeon/testing/testing_config.py).
 
 A large portion of testing time is spent compiling `numba` functions. By default,