Initial commit of converted rst to MyST and inserted MyST empty html_meta headers

Author: stevepiercy

coredev/agreement.md

@@ -0,0 +1,71 @@
+---
+myst:
+  html_meta:
+    "description": ""
+    "property=og:description": ""
+    "property=og:title": ""
+    "keywords": ""
+---
+
+# Contributing to Plone core
+
+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.
+
+Plone's source code is hosted in git repositories at  <https://github.com/plone>, but only members of the developer team have commit rights.
+
+Sending in a contributors agreement does not guarantee your commit access to the repositories, but once you send it in we will always have it on file for when you are ready to contribute.
+
+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.
+
+- Attend a [conference](https://plone.org/events/conferences) / [symposium](http://plone.org/events/regional) or participate in a [sprint](https://plone.org/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.
+
+  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.
+
+- **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.
+
+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>`.
+
+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).
+
+**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 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.
+
+Pull requests without contributor's agreement can only be merged in trivial cases,
+and only by the release manager.

coredev/agreement.rst

@@ -0,0 +1,70 @@
+.. -*- coding: utf-8 -*-
+
+==========================
+Contributing to Plone Core
+==========================
+
+There are many people and companies who rely on Plone on a day-to-day basis so we have to enforce some level of code quality control.
+
+Plone's source code is hosted in git repositories at  https://github.com/plone, but only members of the developer team have commit rights.
+
+Sending in a contributors agreement does not guarantee your commit access to the repositories,
+but once you send it in we will always have it on file for when you are ready to contribute.
+
+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.
+
+* Attend a `conference <https://plone.org/events/conferences>`_ / `symposium <http://plone.org/events/regional>`_ or participate in a `sprint <https://plone.org/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.
+
+  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.
+
+* **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.
+
+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 [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>`.
+
+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>`_.
+
+
+**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 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 [email protected] to check.
+
+Pull requests without contributor's agreement can only be merged in trivial cases,
+and only by the release manager.

coredev/continous-integration.md

@@ -0,0 +1,120 @@
+---
+myst:
+  html_meta:
+    "description": ""
+    "property=og:description": ""
+    "property=og:title": ""
+    "keywords": ""
+---
+
+% -*- coding: utf-8 -*-
+
+# Essential Continuous Integration Practices
+
+The CI system at [jenkins.plone.org](http://jenkins.plone.org) is a shared resource for Plone core developers
+to notify them of regressions in Plone core code.
+
+Build breakages are a normal and expected part of the development process.
+Our aim is to find errors and eliminate them as quickly as possible, without expecting perfection and zero errors.
+Though, there are some essential rules that needs to be followed in order to achieve a stable build.
+
+## 1) Don’t Check In on a Broken Build
+
+Do not make things more complicated for the developer who is responsible for breaking the build.
+
+If the build breaks, the developer has to identify the cause of the breakage as soon as possible and should fix it.
+
+If we adopt this strategy, we will always be in the best position to find out what caused the breakage and fix it immediately.
+
+If one of the developers has made a check-in and broken the build as a result, we have the best chance of fixing
+the build if we have a clear look at the problem.
+
+Checking in further changes and triggering new builds will just lead to more problems.
+
+If the build is broken over a longer period of time (more than a couple of hours)
+you should either notify the developer who is responsible for the breakage, fix the problem yourself,
+or just revert the commit in order to be able to continue to work.
+
+:::{note}
+There is one exception to this rule.
+Sometimes there are changes or tests that depend on changes in other packages.
+If this is the case,
+there is no way around breaking a single build for a certain period of time.
+In this case run the all tests locally with all the changes and commit them within a time frame of 10 minutes.
+:::
+
+## 2) Always Run All Commit Tests Locally before Committing
+
+Following this practice ensures the build stays green and other developers can continue to work without breaking the first rule.
+
+There might be changes that have been checked in before your last update from the version control that might
+lead to a build failure in Jenkins in combination with your changes.
+
+Therefore it is essential that you check out ({command}`git pull`) and run the tests again before you push your changes to GitHub.
+
+Furthermore, a common source of errors on check-in is to forget to add some files to the repository.
+
+If you follow this rule and your local build passes, you can be sure that this is because someone else checked in in the meantime,
+or because you forgot to add a new class or configuration file that you have been working on into the version control system.
+
+## 3) Wait for Commit Tests to Pass before Moving On
+
+Always monitor the build’s progress and fix the problem right away if it fails.
+
+You have a far better chance of fixing the build, if you just introduced a regression than later.
+Also another developer might have committed in the meantime (by breaking rule 1)
+making things more complicated for your.
+
+## 4) Never Go Home on a Broken Build
+
+Taking into account the first rule of CI ("Don't check in on a broken build"), breaking the build essentially
+stops all other developers from working on it.
+
+Therefore going home on a broken build (or even on a build that has not finished yet) is **not** acceptable.
+It will prevent all the other developers to stop working on the build or fixing the errors that you introduced.
+
+## 5) Always Be Prepared to Revert to the Previous Revision
+
+In order for the other developers to be able to work on the build, you should always be prepared to revert
+to the previous (passing) revision.
+
+## 6) Time-Box Fixing before Reverting
+
+When the build breaks on check-in, try to fix it for ten minutes.
+If, after ten minutes, you aren’t finished with the solution, revert to the previous version from your version control system.
+This way you will allow other developers to continue to work.
+
+## 7) Don’t Comment Out Failing Tests
+
+Once you begin to enforce the previous rule, the result is often that developers start commenting out
+failing tests in order to get the build passing again as quick as possible.
+
+While this impulse is understandable, it is **wrong**.
+
+The tests have been passing for a while and then start to fail.
+This means that we either caused a regression, made assumptions that are no longer valid,
+or the application has changed the functionality being tested for a valid reason.
+
+You should always either fix the code (if a regression has been found), modify the test
+(if one of the assumptions has changed), or delete it (if the functionality under test no longer exists).
+
+## 8) Take Responsibility for All Breakages That Result from Your Changes
+
+If you commit a change and all the tests you wrote pass, but others break, the build is still broken.
+This also applies to tests that fail in `buildout.coredev` and don't belong directly to the package you worked on.
+
+This means that you have introduced a regression bug into the application.
+
+It is **your responsibility** — because you made the change — to fix all tests that are not passing as a result of your changes.
+
+There are some tests in Plone that fail randomly, we are always working on fixing those.
+If you think you hit such a test, try to fix it (better) or re-run the Jenkins job to see if it passes again.
+
+In any case the developer who made the commit is responsible to make it pass.
+
+## Further Reading
+
+Those rules were taken from the excellent book "Continuous Delivery" by Jez Humble and David Farley (Addison Wesley),
+and have been adopted and rewritten for the Plone community.
+
+If you want to learn more about Continuous Integration and Continuous Delivery, I'd recommend that you buy this book.

coredev/continous-integration.rst

@@ -0,0 +1,130 @@
+.. -*- coding: utf-8 -*-
+
+==========================================
+Essential Continuous Integration Practices
+==========================================
+
+The CI system at `jenkins.plone.org <http://jenkins.plone.org>`_ is a shared resource for Plone core developers
+to notify them of regressions in Plone core code.
+
+Build breakages are a normal and expected part of the development process.
+Our aim is to find errors and eliminate them as quickly as possible, without expecting perfection and zero errors.
+Though, there are some essential rules that needs to be followed in order to achieve a stable build.
+
+1) Don’t Check In on a Broken Build
+===================================
+
+Do not make things more complicated for the developer who is responsible for breaking the build.
+
+If the build breaks, the developer has to identify the cause of the breakage as soon as possible and should fix it.
+
+If we adopt this strategy, we will always be in the best position to find out what caused the breakage and fix it immediately.
+
+If one of the developers has made a check-in and broken the build as a result, we have the best chance of fixing
+the build if we have a clear look at the problem.
+
+Checking in further changes and triggering new builds will just lead to more problems.
+
+If the build is broken over a longer period of time (more than a couple of hours)
+you should either notify the developer who is responsible for the breakage, fix the problem yourself,
+or just revert the commit in order to be able to continue to work.
+
+.. note::
+
+    There is one exception to this rule.
+    Sometimes there are changes or tests that depend on changes in other packages.
+    If this is the case,
+    there is no way around breaking a single build for a certain period of time.
+    In this case run the all tests locally with all the changes and commit them within a time frame of 10 minutes.
+
+
+2) Always Run All Commit Tests Locally before Committing
+========================================================
+
+Following this practice ensures the build stays green and other developers can continue to work without breaking the first rule.
+
+There might be changes that have been checked in before your last update from the version control that might
+lead to a build failure in Jenkins in combination with your changes.
+
+Therefore it is essential that you check out (:command:`git pull`) and run the tests again before you push your changes to GitHub.
+
+Furthermore, a common source of errors on check-in is to forget to add some files to the repository.
+
+If you follow this rule and your local build passes, you can be sure that this is because someone else checked in in the meantime,
+or because you forgot to add a new class or configuration file that you have been working on into the version control system.
+
+
+3) Wait for Commit Tests to Pass before Moving On
+=================================================
+
+Always monitor the build’s progress and fix the problem right away if it fails.
+
+You have a far better chance of fixing the build, if you just introduced a regression than later.
+Also another developer might have committed in the meantime (by breaking rule 1)
+making things more complicated for your.
+
+
+4) Never Go Home on a Broken Build
+==================================
+
+Taking into account the first rule of CI ("Don't check in on a broken build"), breaking the build essentially
+stops all other developers from working on it.
+
+Therefore going home on a broken build (or even on a build that has not finished yet) is **not** acceptable.
+It will prevent all the other developers to stop working on the build or fixing the errors that you introduced.
+
+
+5) Always Be Prepared to Revert to the Previous Revision
+========================================================
+
+In order for the other developers to be able to work on the build, you should always be prepared to revert
+to the previous (passing) revision.
+
+
+6) Time-Box Fixing before Reverting
+===================================
+
+When the build breaks on check-in, try to fix it for ten minutes.
+If, after ten minutes, you aren’t finished with the solution, revert to the previous version from your version control system.
+This way you will allow other developers to continue to work.
+
+
+7) Don’t Comment Out Failing Tests
+==================================
+
+Once you begin to enforce the previous rule, the result is often that developers start commenting out
+failing tests in order to get the build passing again as quick as possible.
+
+While this impulse is understandable, it is **wrong**.
+
+The tests have been passing for a while and then start to fail.
+This means that we either caused a regression, made assumptions that are no longer valid,
+or the application has changed the functionality being tested for a valid reason.
+
+You should always either fix the code (if a regression has been found), modify the test
+(if one of the assumptions has changed), or delete it (if the functionality under test no longer exists).
+
+
+8) Take Responsibility for All Breakages That Result from Your Changes
+======================================================================
+
+If you commit a change and all the tests you wrote pass, but others break, the build is still broken.
+This also applies to tests that fail in ``buildout.coredev`` and don't belong directly to the package you worked on.
+
+This means that you have introduced a regression bug into the application.
+
+It is **your responsibility** — because you made the change — to fix all tests that are not passing as a result of your changes.
+
+There are some tests in Plone that fail randomly, we are always working on fixing those.
+If you think you hit such a test, try to fix it (better) or re-run the Jenkins job to see if it passes again.
+
+In any case the developer who made the commit is responsible to make it pass.
+
+
+Further Reading
+===============
+
+Those rules were taken from the excellent book "Continuous Delivery" by Jez Humble and David Farley (Addison Wesley),
+and have been adopted and rewritten for the Plone community.
+
+If you want to learn more about Continuous Integration and Continuous Delivery, I'd recommend that you buy this book.