Re: Need help with GitHub Issues migration

Max via mc-devel <mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org> Tue, 25 Feb 2025 10:07:56 +0000
Newsgroups gmane.comp.gnome.apps.mc.devel
Message-ID <zzC2ztM39bv6mB0ym9jl2VWRqvOaMZjbi7kS_VHXS-h8RSg7qvwcB6SmTctSp-p7veEnmjx2FpEtJG40Fq89KS9sdXFYcRmbk7YmNQAkD_0=@protonmail.ch>
On Tuesday, February 25th, 2025 at 8:08 AM, Yury V. Zaytsev <[email protected]> wrote:

> > On 24. Feb 2025, at 22:21, Max mleonov-g/[email protected] wrote:
> >
> > - Visibility to developers as potential contributors (community = people). It takes less time for a GitHub user to contribute on GitHub. IOW, GitHub has more potential contributors who have less dedication and less availability.
>
>
> I'm more worried about an influx of GitHub contributors with small, untested patches to scratch their own itch, but breaking everything for almost everyone else, and of course without any tests and/or documentation. Then you ask for changes and tests, and the usual drama about evil bureaucratic maintainers ensues. At least this is the kind of pull request we have been getting. But maybe I'm being too negative.

You bet. I suggest posting clear upfront rules for potential contributors about what kind of contributions are requested and defining a milestone plan so that they play by your rules.
https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/about-milestones

-- 
mc-devel mailing list
mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org
https://lists.midnight-commander.org/mailman/listinfo/mc-devel