From 531327c52b737e5a1285e4b2a5e8e92082221b1d Mon Sep 17 00:00:00 2001 From: Jens Vagelpohl Date: Sat, 28 Sep 2024 08:46:24 +0200 Subject: [PATCH] - integrate changes drom d-maurer --- docs/hacking.rst | 15 +++++++++++---- setup.py | 2 +- 2 files changed, 12 insertions(+), 5 deletions(-) diff --git a/docs/hacking.rst b/docs/hacking.rst index e3e38d7..9c51f97 100644 --- a/docs/hacking.rst +++ b/docs/hacking.rst @@ -177,9 +177,16 @@ Sharing Your Changes or bug fixes, although it is possible that you may have tested your new code by updating existing tests. -If have made a change you would like to share, the best route is to fork -the Githb repository, check out your fork, make your changes on a branch -in your fork, and push it. You can then submit a pull request from your -branch: + Contributions to Plone/Zope Foundation packages require contributor status. + Please see https://www.zope.dev/developer/becoming-a-committer.html. + +If you have made changes you would like to share, the best route is to create a +branch in the GitHub repository and push changes there, which requires +`contributor status +`_. You can +also fork the GitHub repository, check out your fork, make your changes on a +branch in your fork, and then push them. A private fork makes it harder for +others and the package maintainers to work with your changes, so it is +discouraged. Either way, you can then submit a pull request from your branch: https://github.com/zopefoundation/zope.meta/pulls diff --git a/setup.py b/setup.py index 75130cd..940fea3 100644 --- a/setup.py +++ b/setup.py @@ -29,7 +29,7 @@ def read(*rnames): name='zope.meta', version='1.0.dev0', author='Zope Foundation and Contributors', - author_email='zope-dev@zope.org', + author_email='zope-dev@zope.dev', description='Helper functions for package management', long_description=( read('README.rst')