Tidy up agreement.md

Author: stevepiercy

coredev/agreement.md

@@ -1,13 +1,15 @@
 ---
 myst:
   html_meta:
-    "description": ""
-    "property=og:description": ""
-    "property=og:title": ""
-    "keywords": ""
+    "description": "Contributing to Plone"
+    "property=og:description": "Contributing to Plone"
+    "property=og:title": "Contributing to Plone"
+    "keywords": "Contributing, Plone"
 ---
 
-# Contributing to Plone core
+(contributing-to-plone-label)=
+
+# Contributing to Plone
 
 There are many people and companies who rely on Plone on a day-to-day basis, so we must enforce some level of code quality control.
 
@@ -17,55 +19,46 @@ Sending in a contributors agreement does not guarantee your commit access to the
 
 We ask that before requesting core access you familiarize yourself a little with the community since they will help you get ramped up:
 
-- Ask and (especially) answer questions on [the Plone forum](https://community.plone.org/) and in {doc}`Plone chat <culture>` with a focus on getting to know the active developers a bit.
+-   Ask and (especially) answer questions on [the Plone forum](https://community.plone.org/) and in {doc}`Plone chat <culture>` with a focus on getting to know the active developers a bit.
 
-- Attend a [conference](https://plone.org/events/conferences) / [symposium](http://plone.org/events/regional) or participate in a [sprint](https://plone.org/events/sprints).
+-   Attend a [conference](https://plone.org/news-and-events/events/plone-conferences), [symposium](https://plone.org/news-and-events/events/regional), or participate in a [sprint](https://plone.org/news-and-events/events/sprints).
 
-  There are plenty of opportunities to meet the community and start contributing through various coding sessions,
-  either in person or on the web.
+    There are plenty of opportunities to meet the community and start contributing through various coding sessions, either in person or on the web.
 
-  You may even be able to get immediate core access at a conference if you are flexing your mad coding skills and the right people are attending.
+    You may even be able to get immediate core access at a conference if you are flexing your mad coding skills and the right people are attending.
 
-- Get your feet wet by contributing to the [collective](https://collective.github.io/).
-  Don't worry about getting it perfect or asking for help;
-  this way you get to know us and we improve our code together as a community.
+-   Get your feet wet by contributing to the [collective](https://collective.github.io/).
+    Don't worry about getting it perfect or asking for help.
+    This way you get to know us and we improve our code together as a community.
 
-- **Patches:** Historically we encouraged people to submit patches to the ticket collector.
-  These tickets are usually ignored forever.
-  Technically,
-  in order for us to accept your patch you must sign the contributors agreement.
-  If you want to contribute fixes,
-  please just sign the agreement and go through the standard GitHub pull request process described below until you feel comfortable to bypass review.
-  If the ticket is trivial,
-  or you're fixing documentation,
-  you do not need to sign a contributor's agreement.
+-   **Patches:** Historically we encouraged people to submit patches to the ticket collector.
+    These tickets are usually ignored forever.
+    Technically, for us to accept your patch, you must sign the contributors agreement.
+    If you want to contribute fixes, please just sign the agreement and go through the standard GitHub pull request process described below until you feel comfortable to bypass review.
+    If the ticket is trivial, you do not need to sign a contributor's agreement.
 
 Once you have familiarized yourself with the community and you are excited to contribute to the core:
 
-- Sign the contributor agreement at <https://plone.org/foundation/contributors-agreement/agreement.pdf>,
-  then either snail mail it to the address provided or scan and email it to <mailto:[email protected]>.
-  This offers both copyright protection and ensures that the Plone Foundation is able to exercise some control over the codebase,
-  ensuring it is not appropriated for someone's unethical purposes.
-  For questions about why the agreement is required,
-  please see {doc}`Contributor’s Agreement for Plone Explained <contributors_agreement_explained>`.
+-   Sign the contributor agreement at <https://plone.org/foundation/contributors-agreement/agreement.pdf>, then either send by postal mail to the address provided, or scan and email it to <[email protected]>.
+    This offers both copyright protection and ensures that the Plone Foundation is able to exercise some control over the codebase, ensuring it is not appropriated for someone's unethical purposes.
+    For questions about why the agreement is required, please see [About the Plone Contributor Agreement
+](https://plone.org/foundation/contributors-agreement).
 
-If you aren't sure where to start or just want more direction, feel free to get in the forum or in chat,
-and ask for help.
-While there is no official mentoring process, there are plenty of people willing to act in that role and
-guide you through the steps of getting involved in the community.
-A common way to start contributing is to participate in a [Plone sprint](ttps://plone.org/events/sprints).
+If you aren't sure where to start or just want more direction, feel free to get in the forum or in chat, and ask for help.
+While there is no official mentoring process, there are plenty of people willing to act in that role and guide you through the steps of getting involved in the community.
+A common way to start contributing is to participate in a [Plone sprint](https://plone.org/news-and-events/events/sprints).
 
 **Welcome to the Plone community!**
 
+
 ## Dealing with pull requests on GitHub
 
 Before we can merge a pull request, we have to check that the author has signed the contributor's agreement.
 
-If they're listed in <https://github.com/plone?tab=members>, the author has signed so we can go ahead and merge.
+If they're listed in <https://github.com/orgs/plone/teams/developers/members>, the author has signed so we can go ahead and merge.
 
 If they aren't listed there, there's still a chance they have signed the contributor's agreement.
 
-If they have signed before the move to GitHub, you can ask <mailto:[email protected]> to check.
+If they have signed before the move to GitHub, you can ask <[email protected]> to check.
 
-Pull requests without contributor's agreement can only be merged in trivial cases,
-and only by the release manager.
+Pull requests without contributor's agreement can only be merged in trivial cases, and only by the release manager.