Re: Need help with GitHub Issues migration

On Monday, February 24th, 2025 at 7:01 PM, Yury V. Zaytsev via mc-devel <mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org> wrote:

> > On 24. Feb 2025, at 16:56, David Niklas via mc-devel mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org wrote:
> > 
> > On Mon, 24 Feb 2025 08:18:50 +0100
> > "Yury V. Zaytsev" [email protected] wrote:
> > 
> > > > On 24. Feb 2025, at 01:20, David Niklas via mc-devel
> > > > mc-devel-+hD5IHI5XseWCegYutOAJTiNl0CLU6MPYPYVAmT7z5s@public.gmane.org wrote:
> > > > 
> > > > I know it's probably a bit late for this, but maybe you should
> > > > consider that tying yourself/project to github isn't the best idea in
> > > > the world.
> > > 
> > > So what is the best idea in the world?
> > 
> > If only I knew!
> > 
> > There's gitlab and sourceforge, amoung others, I'm sure. For bug reports
> > some projects use bugzilla. The linux kernel still does bug reports and
> > fixes through the ML.
> > 
> > What's insufficient about the current system?
> 
> 
> I tried to explain this and what I think about other options I have considered so far in the opening email.
> 
> > I'm more worried about what becomes of the code bases and devs than
> > perturbed for any other reason.
> 
> 
> As for the code base, I maintain an active mirror at repo.or.cz:
> 
> https://repo.or.cz/midnight-commander.git

:) Hello again

FYI, there's also https://git.disroot.org/explore/repos that runs on https://forgejo.org/.

I'm just an outsider, so forgive me for crashing this thread, but GitHub has some pros:

- 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.
- You save your time and mental effort not having to maintain a self-hosted website. Considering that you're doing this project in your free time, this point is doubly important.
- GitHub CLI (`gh`) enables terminal users to open issues in the terminal (https://cli.github.com/manual/gh_issue_create). Why is this important? Firstly, terminal users are both your userbase and potential contributors. If you promote new issue submission by recommending the use of GitHub CLI in your README, you encourage more terminal users to clone your repo and explore the use of the terminal to handle one more task (open an issue).

If you mirror both the source code repo and docs repo on another Git host, it's hard to imagine ways in which GitHub could endanger the continuity of your package.
FYI, it's also possible to export all GitHub issues, e.g., https://github.com/git-bug/git-bug?tab=readme-ov-file#bridges and take them with you too if need be.

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