On Wed, May 11, 2022 at 08:24:30AM -0400, Dusty Mabe wrote:
On 5/11/22 07:34, Coiby Xu wrote:
> Hi Dusty,
>
> On Tue, May 03, 2022 at 10:36:17AM -0400, Dusty Mabe wrote:
>> Hi all,
>>
>> I'm looking at possibly creating a patch for kexec-tools. Sending patches to
the mailing
>> list is something I don't do very often and will probably make mistakes.
I'm spoiled by
>> the git forge "pull request" workflow. Is this community considering
moving to any git
>> forge that will allow PRs from casual users/contributors?
>
> Yes, currently we are considering moving to gitlab mainly to
> automatically trigger three kinds of tests which include static code
> analysis, unit tests and integration tests when there is a PR. If you
> need to send patches before I finish setting up the Gitlab CI, you can
> send a PR via
https://src.fedoraproject.org/rpms/kexec-tools.
>
That's great news. I'll look for it on GitLab when it's moved there.
If I open a PR to
https://src.fedoraproject.org/rpms/kexec-tools is
that effectively upstream such that the change won't get lost in the
future?
Yes, the change won't get lost. Although the Community Platform
Engineering (CPE) team announced "opting for GitLab for our dist git"
[1] last year, it seems they are not ready according to the listed repos
under
https://gitlab.com/fedora. So I'll still sync changes to
https://src.fedoraproject.org/rpms/kexec-tools to release packages even
after moving to gitlab.
[1]
https://communityblog.fedoraproject.org/making-a-git-forge-decision/
Dusty
--
Best regards,
Coiby