Development of Fedora kexec-tools migrating to github.com/rhkdump/kdump-utils

[Coiby Xu]

Hi All,

From now on, you are expected to send your patches by creating a pull
request against https://github.com/rhkdump/kdump-utils instead of to this
mailing list. And if you want to receive patches or discussions, you can
welcome to click the "Watch" button on the GitHub project homepage.

As some of you have noticed, we are splitting Fedora kexec-tools into
three packages kdump-utils, kexec-tools and makedumpfile [1] and we were
asked to establish an upstream repo for kdump-utils. Since this mailing
list has been mostly used for developments of kdump-utils, the name of
the mailing list (kexec) no loner makes sense.

More importantly, we'd like to take this opportunity to switch to a git
forge based workflow in order to have the following benefits,

1. Automate testing and releasing i.e. continuous integration (CI) and
    continuous delivery (CD). 
    - We are going to enable unit tests and integration tests so whenever
      you create a PR or make some changes to that PR, they will be
      triggered automatically. In this way, we can prevent/catch problems
      early by testing as early and as often as possible. This will also
      make your development experience more enjoyable as fast feedback is
      provided by the results of the automated tests.
    - We also plan to automate releasing the Fedora packages.

2. Make it easier to collocate with other contributors as many projects
    related to our project including those which we depend on or which
    depend on our project have already used GitHub.

3. Make it easy to track patches. In the past, we occasionally lost
    track of some patches sent to the mailing list. With the help of
    GitHub, this issue can be prevented.

FAQ
###

1. What about https://src.fedoraproject.org/rpms/kexec-tools.git?
    This repo and future rpms/kdump-utils.git will be merely for work
    related to packaging.

2. How can I view the patches locally maybe for code review?
    There are two ways. The first is to fetch pull/ID/head,
    ```
    git fetch origin pull/ID/head:BRANCH_NAME
    git switch BRANCH_NAME
    ```
    Or you download the patches and apply them manually,
    ```
    wget https://github.com/rhkdump/kdump-utils/pull/ID.patch
    git am ID.patch
    ```

3. What if I want to add an in-line comment on the commit message?
    Unfortunately, GitHub code review currently misses this feature [3].
    We think this is an important feature and have left a comment [3].
    And you are also welcome to leave an comment on [3] to let GitHub
    hear your voice.

[1] https://src.fedoraproject.org/rpms/kexec-tools/pull-request/17
[2] https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/re...
[3] https://github.com/orgs/community/discussions/56449