GitLab.com vs Codeberg.org

[Fred vS]

Of course you will still use GitLab for git but one of the proposition was to have a independent issues tracker so, if GitLab makes problems, you still have all the data + program for issues.

IIRC Gitlab allows to link to a separate tracker....

But, we had that. Remember Mantis? We wanted to no longer having to maintain it (one burden less).
And if the answer was, not to self host our bugtracker, then we needed to trust someone. We might as well make that someone GitLab. Then at least we benefit from the better integration (i.e. the bugtracker automatically links to issues with a mention)

OK, so, maybe do regularly a "export-issues-csv" of fpc GitLab-issues and in case of a problem appears you have a backup.
https://docs.gitlab.com/ee/user/project/issues/csv_export.html

If you do it yet, once again, sorry for the noise. 

[PascalDragon]

With recycled oil and with powerful filter in the chimney I hope. 

It's the job of my landlord to care about that, not mine.

[marcov]

We don't want an independent tracker anymore.

Well, it was not unanimous :-)

[Bi0T1N]

And then there's the story where SourceForge had/has to block users from certain foreign countries due to US policies...

Absolutely scandalous ( or ridiculous ) but GitLab does the same: https://gitlab.com/gitlab-org/gitlab/-/issues/260406

There is the Tor Project to help you avoid any censorship. Otherwise a simple VPN connection will help or a combination of both in case you're living in a country which is very restrictive and you don't want the hassle that some exit nodes are blocked by webmasters.

OK, so, maybe do regularly a "export-issues-csv" of fpc GitLab-issues and in case of a problem appears you have a backup.
https://docs.gitlab.com/ee/user/project/issues/csv_export.html

As you can see the CSV export doesn't include all information one might need from an issue. E.g. attachments of users. Better use there API to really fetch everything you need (that's what Michael used to add/convert all the issues from Mantis to Gitlab). If I recall correctly he also published his code for it but right now I could only find the package to access the API: https://gitlab.com/freepascal.org/fpc/source/-/tree/main/packages/gitlab
There are also other alternatives like python-gitlab.

Now that you have all the information you need, go ahead and write a script capable of constantly mirroring the Gitlab issues to a "safe" location. And please set up a website to collect all our private addresses in case your chosen server location might block us - so you can send us a floppy-disk or CD (hopefully not rewritable, as it could then contain a virus or so: [1], [2] )

[Fred vS]

...
Remember Mantis?

Of course (and some "hot" issue discussion  )
By the way, Mantis is still first in the top 10 of best issue tracking tools:
https://www.fosslinux.com/50578/opensource-bug-and-issue-tracking-tools-for-linux.htm

[Fred vS]

As you can see the CSV export doesn't include all information one might need from an issue. E.g. attachments of users. Better use there API to really fetch everything you need (that's what Michael used to add/convert all the issues from Mantis to Gitlab). If I recall correctly he also published his code for it but right now I could only find the package to access the API: https://gitlab.com/freepascal.org/fpc/source/-/tree/main/packages/gitlab
There are also other alternatives like python-gitlab.

Now that you have all the information you need, go ahead and write a script capable of constantly mirroring the Gitlab issues to a "safe" location. And please set up a website to collect all our private addresses in case your chosen server location might block us - so you can send us a floppy-disk or CD (hopefully not rewritable, as it could then contain a virus or so: [1], [2] )

Huh, maybe re-install Mantis on a safe place should even be faster-simpler. 

OK, ok,  I'm leaving...

[Arioch]

Absolutely scandalous ( or ridiculous ) but GitLab does the same: https://gitlab.com/gitlab-org/gitlab/-/issues/260406

Well, as long as you have servers, those servers should physically exists somewhere, and then they are subject to local laws.

There are trackers, that are hosted inside the code repository: Fossil, and there was some add-on for Git too.
Those can not be censored in any "single point of failure", repository copies can be hosted in several countries and be naturally sycnhronized.

But i suspect this kind of trackers would be not very comfortable to use.

By the way, Mantis is still first in the top 10 of best issue tracking tools:

I suspect, because it's user interface is so simplistic. And nice-looking too. For non-IT people it is important.

Feature-wise Trac would be better for low-requirements project server, but it looks just ugly, few people want to use it.
Mantis then is cute and is somewhat obvious how to use it.
I once set it in non-IT environment, where people tried to track tasks in MSWord tables and e-mail, and chat, and....
3 months later people were used it mostly without mistakes, and more importantly, they started to LIKE this way of interactions.

I occasionalyl felt confined by Mantis limits, but not often. And non-IT people struggled to learn with the very idea of formalized workflow.
A tool more complex then Mantis would just scare them away.

Mantis somehow really managed to find the soft spot of "as few features as possible, but not less".

...Then one big boss prohibited it and installed Redmine ("because my husband said it is the best tool"). 
Well, yeah, indeed quite a pack. So full of features no one knew what they are and why. And the features of Mantis-scope were hidden deep or made very uncomfortable to use. Information flow went away into Telegram in no time. And the boss enjoyed the tracker was clear, with no "dirt" and "noise", only nice pure reports "task opened"/"task closed", ideal reporting tool.