Replace Pagure links with new repo at Codeberg

src/Contribute.rst

@@ -21,7 +21,7 @@ Security Bugs and Flaws
 Tracking
 ^^^^^^^^
 
--  We use `Pagure <https://pagure.io/freeipa/issues>`__ for the upstream
+-  We use `Codeberg <https://codeberg.org/freeipa/freeipa>`__ for the upstream
    development, so all RFEs or bug reports should go primarily there.
 -  Bugs against released Fedora versions can be logged using the
    following `Bugzilla
@@ -76,8 +76,8 @@ free to ask!
 How To Start
 ~~~~~~~~~~~~
 
-The FreeIPA project uses the `Pagure ticketing
-system <https://pagure.io/freeipa/>`__ to keep track of work being done.
+The FreeIPA project uses the `Codeberg ticketing
+system <https://codeberg.org/freeipa/freeipa>`__ to keep track of work being done.
 If you want to contribute check out if there are interesting tickets in
 the pipeline (or file your own).
 

src/Downloads.rst

@@ -46,9 +46,9 @@ Sources
 ~~~~~~~
 
 If you want to `build <https://www.freeipa.org/page/Build>`__ FreeIPA
-yourself, you can check the sources stored on the project Pagure:
+yourself, you can check the sources stored on the project Codeberg:
 
--  `Latest Released Sources <https://releases.pagure.org/freeipa/>`__
+-  `Latest Released Sources <https://codeberg.org/freeipa/freeipa/releases>`__
 -  `Steps on verifying the
    release <https://www.freeipa.org/page/Verify_Release_Signature>`__
 

src/index.rst

@@ -34,9 +34,9 @@ Main features
    (Fedora), `389 Directory
    Server <http://directory.fedoraproject.org/>`__, `MIT
    Kerberos <http://k5wiki.kerberos.org/wiki/Main_Page>`__, NTP,
-   `DNS <https://pagure.io/bind-dyndb-ldap>`__, `Dogtag certificate
+   `DNS <https://codeberg.org/freeipa/bind-dyndb-ldap>`__, `Dogtag certificate
    system <http://pki.fedoraproject.org>`__,
-   `SSSD <https://pagure.io/SSSD/sssd>`__ and others.
+   `SSSD <https://sssd.io/>`__ and others.
 -  Built on top of well known Open Source components and standard
    protocols
 -  Strong focus on ease of management and automation of installation and

src/page/Build.rst

@@ -44,7 +44,7 @@ In order to get more familiar with git submodule concepts, you can read
 You can clone the FreeIPA repository and its submodules using the following
 command:
 
-``$ git clone --recurse-submodules https://pagure.io/freeipa.git``
+``$ git clone --recurse-submodules https://codeberg.org/freeipa/freeipa.git``
 
 Next, we will install all packages needed to build FreeIPA as they do
 not have to be installed on your system. You can install them easily by

src/page/Contribute/Code.rst

@@ -4,7 +4,7 @@ Code
 This article should serve both as a reference article for already
 seasoned FreeIPA developers, but also as a guide for new people who
 would like to contribute. You can fix an open bug described in chosen
-`Pagure ticket <https://pagure.io/freeipa/issues>`__ or implement a
+`Codeberg ticket <https://codeberg.org/freeipa/freeipa>`__ or implement a
 whole new feature! The steps below should help get you started.
 
 If you need to learn more about FreeIPA itself, visit the `main
@@ -27,8 +27,8 @@ Find something to start with
 
 If you want to start with something (relatively) easy please take a look
 at `list of "easyfix"
-tickets <https://pagure.io/freeipa/issues?status=Open&tags=easyfix>`__
-in our Pagure. It is always better to start with something simple :-)
+tickets <https://codeberg.org/freeipa/freeipa>`__
+in our Codeberg. It is always better to start with something simple :-)
 
 Do not hesitate to `contact us <Contribute#Communication>`__ with any
 question or idea!
@@ -84,12 +84,12 @@ in git. Retrieve it and its submodules with:
 
 ::
 
-    git clone --recurse-submodules https://pagure.io/freeipa.git
+    git clone --recurse-submodules https://codeberg.org/freeipa/freeipa.git
 
 The code can also be browsed online
-`here <https://pagure.io/freeipa/commits>`__
+`here <https://codeberg.org/freeipa/freeipa>`__
 
-Note: to avoid pushing by mistake to pagure.io, you can replace the (push) url
+Note: to avoid pushing by mistake to Codeberg, you can replace the (push) url
 with the following command:
 
 ::
@@ -136,15 +136,15 @@ Then, you just need to run:
 
 
 
-Update Pagure ticket
+Update Codeberg ticket
 ----------------------------------------------------------------------------------------------
 
-We use Pagure for work coordination. Please be so kind and assign the
+We use Codeberg for work coordination. Please be so kind and assign the
 ticket you are working on to yourself. It is just a few clicks and it
 prevents people from working on the same thing at the same time without
 knowing about each other.
 
--  `Find a ticket <https://pagure.io/freeipa/issues>`__ related to your
+-  `Find a ticket <https://codeberg.org/freeipa/freeipa>`__ related to your
    work.
 
    -  Maybe the ticket does not exist. If you consider the code change
@@ -155,10 +155,7 @@ knowing about each other.
       different approaches etc.
 
 -  In the particular ticket, assign the ticket to yourself by clicking
-   on the "Take" button (note: you must be logged in
-   `pagure.io <https://pagure.io/login/?next=https://pagure.io/freeipa/>`__,
-   see `Login to pagure or create your
-   account <https://docs.pagure.org/pagure/usage/first_steps.html#login-to-pagure-or-create-your-account>`__)
+   on the "Assign to me" option.
 
 
 
@@ -265,9 +262,9 @@ present in the source tree (.git-commit-template):
 
   Explanation
 
-  Fixes: https://pagure.io/freeipa/issue/XXXX
+  Fixes: https://codeberg.org/freeipa/freeipa/issues//XXXX
   or
-  Related: https://pagure.io/freeipa/issue/XXXX
+  Related: https://codeberg.org/freeipa/freeipa/issues/XXXX
   Signed-off-by: Full Name <email@yourmail.com>
 
 
@@ -286,7 +283,7 @@ present in the source tree (.git-commit-template):
    way, but does not resolve it/them.
 -  *Signed-off-by:* contains your email, will be credited in the Contributors and Release Notes
 
-When a pull request is created, please update Pagure ticket with link to
+When a pull request is created, please update Codeberg ticket with link to
 the pull request (in the ticket, click on "Edit Metadata" and update the
 field "on_review" with the link to your PR, for instance
 https://github.com/freeipa/freeipa/pull/1234).
@@ -355,7 +352,7 @@ to keep track of the process.
 When the reviewer pass a feedback, patch should be then updated to clear
 all concerns and thus be ready to be merged. See `Pull request on
 Github <https://www.freeipa.org/page/Pull_request_on_Github>`__ for advice how to update a pull
-request. No changes in Pagure are needed when a reviewer rejects the
+request. No changes in Codeberg are needed when a reviewer rejects the
 patch or submitter sends a new version of the patch.
 
 

src/page/Contribute/Repository.rst

@@ -14,8 +14,7 @@ FreeIPA project has 1 active repository:
 -  **Main code repository**: FreeIPA project code and tests
 
    -  Link:
-      ```https://pagure.io/freeipa.git`` <https://pagure.io/freeipa.git>`__
-   -  `Code browser <https://pagure.io/freeipa/commits/master>`__
+      ```https://codeberg.org/freeipa/freeipa.git`` <https://codeberg.org/freeipa/freeipa.git>`__
    -  `Contribution howto <Contribute/Code>`__
 
 
@@ -33,7 +32,7 @@ Write access
 ============
 
 Write access is allowed only to a limited list of upstream core
-developers (`member list <https://pagure.io/group/freeipa>`__) who are
+developers (`member list <https://codeberg.org/org/freeipa/members>`__) who are
 contributing to the project success, keep the code base clean and
 functional. The list is kept short to make sure that all committers know
 what should be pushed, when, to which branch(es) and with appropriate

src/page/Contribute/Tests.rst

@@ -141,14 +141,14 @@ Committing (doesn’t apply for the temp commit)
 #. Follow the commit message guidelines listed in `Commit message
    requirements <Contribute/Code#Commit_message_requirements>`__
 #. Signoff and sign your commit
-#. All commits must include Pagure link
+#. All commits must include Codeberg ticket link
 #. Include separate temp commit (see below)
 
 ::
 
     (lowercase) ipatests : short summary within 80 chars (no dot)
     This is the particular reason for a change and or addition of a new test. Be as specific as possible. Use imperative language (fix bug, not fixed bug nor fixes bug) and present time.
-    Fixes (or Related): Pagure ticket link
+    Fixes (or Related): Codeberg ticket link
     Signed off by: (use –signoff and -S when committing)
 
 Note: “Fixes” is used when providing a fix for the raised issue.

src/page/Pull_request_on_Github.rst

@@ -10,7 +10,7 @@ repository (cloned from fedorahosted)
 
 ::
 
-    $ git clone --recurse-submodules https://pagure.io/freeipa.git
+    $ git clone --recurse-submodules https://codeberg.org/freeipa/freeipa.git
     $ cd freeipa/
     $ git remote add myfork git@github.com:/freeipa.git
 
@@ -61,4 +61,4 @@ enough, but it is also possible to develop Modern WebUI separately using:
 The other processes are similar.
 
 Do note, that all of the development for Modern WebUI is done on
-`GitHub <https://github.com/freeipa/freeipa-webui>`__, not on Pagure.
+`GitHub <https://github.com/freeipa/freeipa-webui>`__, not on Codeberg.

src/page/Release.md

@@ -207,7 +207,7 @@ Building the sources
 If doing a pre release pull a fresh tree to do the builds into a separate directory:
 
 ```
-$ git clone --recurse-submodules [https://pagure.io/freeipa.git](https://pagure.io/freeipa.git) freeipa-x-y-z
+$ git clone --recurse-submodules [https://codeberg.org/freeipa/freeipa.git](https://codeberg.org/freeipa/freeipa.git) freeipa-x-y-z
 $ cd freeipa-x-y-z
 ```
 
@@ -263,7 +263,7 @@ $ gpg2 --default-key <IPA MASTER KEYID> --armor --detach-sign freeipa-x.y.z.tar.
 $ gpg2 --verify freeipa-x.y.z.tar.gz.asc
 ```
 
-Upload tarball and signature to pagure.io: [https://pagure.io/freeipa/releases](https://pagure.io/freeipa/releases)
+Upload tarball and signature to Codeberg: [https://codeberg.org/freeipa/freeipa/releases](https://codeberg.org/freeipa/freeipa/releases)
 
 If you signing key is not in the [Verify Release Signature](/web/20221001164305/https://freeipa.org/page/Verify_Release_Signature "Verify Release Signature") guide, append it to the list and gpg verify command.
 
@@ -383,13 +383,3 @@ When doing a major release, consider following extra steps:
 *   [Roadmap](/web/20221001164305/https://freeipa.org/page/Roadmap "Roadmap") - consider updating information about planned or new releases
 *   [Documentation](/web/20221001164305/https://freeipa.org/page/Documentation "Documentation") - update links and version numbers
 *   [Build](/web/20221001164305/https://freeipa.org/page/Build "Build") - update COPR repositories if new ones are introduced or old abandoned
-
-Tickets administravia
----------------------
-
-FixMe: is this being done for 4.9.x?
-
-*   [Create a milestone](https://fedorahosted.org/freeipa/milestone?action=new) for next FreeIPA version in form FreeIPA x.y.z.
-*   Create a new milestone in [Pagure project settings](https://pagure.io/freeipa/settings) (if doesn't exist).
-*   Move all [opened tickets](https://pagure.io/freeipa/roadmap?status=Open&milestone=FreeIPA+4.5.1&all_stones=True&no_stones=) from the released version milestone to the new milestone. (Following script can be used, use [move-milestone.py --help](https://raw.githubusercontent.com/freeipa/freeipa-tools/master/release/move-milestone.py) to see usage)
-*   Close the old milestone in the [Roadmap](https://fedorahosted.org/freeipa/roadmap).