GitLab.com vs Codeberg.org lazarus / 8-Other ---------------------------------------------------------------------- Fred vS · 2022-09-04 16:58 Hello. There is a project that I follow for age, that has his deb debian official package and with code hosted on Gitlab. https://www.surina.net/soundtouch/download.html Suddenly, without any warning, GitLab just blocked soundtouch account. Here the note of maintainer: Quote2021-10-14 OP: For some reason that currently is unknown to us, gitlab.com blocked soundtouch account without any prior notice, hence soundtouch repository moved to codeberg.org, hopefully a more stable and friendly home for an opensource project. Here his new CodeBerg project: https://codeberg.org/soundtouch/soundtouch I hope that GitLab will not do the same for fpc/Lazarus (or some projects that I care). ---------------------------------------------------------------------- Thaddy · 2022-09-04 17:04 There was a good reason for that, Fred. Just not public yet. Simply don't use it for now. (Well, if you really payed attention and did some research you know why my reaction is that way....) I strongly discourage the use of codeberg, obviously. ---------------------------------------------------------------------- Fred vS · 2022-09-04 17:08 Quote from: Thaddy on September 04, 2022, 07:04:15 pm Just not public yet. Simply don't use it for now. Hello Thaddy. Not sure to understand, should I renounce to use that library just because GitLab blocked the account, without any notice? Is GitLab the promised GodLab? ---------------------------------------------------------------------- Thaddy · 2022-09-04 17:11 Quote from: Fred vS on September 04, 2022, 07:08:53 pmQuote from: Thaddy on September 04, 2022, 07:04:15 pm Just not public yet. Simply don't use it for now. Hello Thaddy. Not sure to understand, should I renounce to use that library just because GitLab blocked the account, without any notice? Is GitLab the promised GodLab? No, you should pay attention from where it is coming from. You are perfectly capabele to detect that yourself. See my avatar, the world is more complex than you think! The gitlab account is blocked for good reasons. And no notice is a good thing. Not all is what is seems. This may be legit, but the maintainer is under surveillance. Kind like a fly trap. You can ask why it is blocked, btw. Probably similar answer. ---------------------------------------------------------------------- Awkward · 2022-09-04 17:18 Quote from: Fred vS on September 04, 2022, 07:08:53 pmQuote from: Thaddy on September 04, 2022, 07:04:15 pm Just not public yet. Simply don't use it for now. Hello Thaddy. Not sure to understand, should I renounce to use that library just because GitLab blocked the account, without any notice? Is GitLab the promised GodLab? Gitlab don't like yor placement? Well, you always can move to another repo site, isn't it? And they moved, not deleted, right? So, best practice can be to make many copies on different repo sites ---------------------------------------------------------------------- Fred vS · 2022-09-04 17:19 Quote from: Thaddy on September 04, 2022, 07:11:54 pmThe gitlab account is blocked for good reasons. Hum, maybe but why not give any infos or warning to the owner/maintainer? ( Or you encourage me to, like must be always done in that new age, do my own exploration and find the reason if there is one and give the result to Olli the maintainer). (Anyway, imho, gitlab should give a message to the maintainer but ok, respect does not have any sense now) ---------------------------------------------------------------------- Thaddy · 2022-09-04 17:20 Quote from: Awkward on September 04, 2022, 07:18:23 pmGitlab don't like yor placement? Well, you always can move to another repo site, isn't it? And they moved, not deleted, right? So, best practice can be to make many copies on different repo sites Gitlab does only do so without notice is something is really wrong. Moving things make things worse. ---------------------------------------------------------------------- Thaddy · 2022-09-04 17:21 Quote from: Fred vS on September 04, 2022, 07:19:53 pmQuote from: Thaddy on September 04, 2022, 07:11:54 pmThe gitlab account is blocked for good reasons. Hum, maybe but why not give any infos or warning to the owner/maintainer? ( Or you encourage me to, like must be always done in that new age, do my own exploration and find the reason if there is one and give the result to Olli the maintainer). (Anyway, imho, gitlab should give a message to the maintainer but ok, respect does not have any sense now) I know for a fact that the maintainer has got the message.... ---------------------------------------------------------------------- Fred vS · 2022-09-04 17:29 Quote from: Thaddy on September 04, 2022, 07:21:37 pmQuote from: Fred vS on September 04, 2022, 07:19:53 pmQuote from: Thaddy on September 04, 2022, 07:11:54 pmThe gitlab account is blocked for good reasons. Hum, maybe but why not give any infos or warning to the owner/maintainer? ( Or you encourage me to, like must be always done in that new age, do my own exploration and find the reason if there is one and give the result to Olli the maintainer). (Anyway, imho, gitlab should give a message to the maintainer but ok, respect does not have any sense now) I know for a fact that the maintainer has got the message.... Hum, I wouldn't dare to insist on that, Olli Parviainen, the maintainer said that he dont receive anything, better not upset him. ---------------------------------------------------------------------- Fred vS · 2022-09-04 17:35 @Thaddy. OK, I will investigate, annoying  (I am the King for that) GitLab team, asking why this site is blocked: https://gitlab.com/soundtouch/soundtouch [EDIT] https://forum.gitlab.com/t/gitlab-blocked-account/74570 ---------------------------------------------------------------------- Fred vS · 2022-09-04 19:24 For the fun and only if it works out-of-the-box, I did try to create migration to CodeBerg of one of my project from GitHub and GitLab. I have to admit that it was incredibly easy, just a account to create, then click on New Migration and choose a GitLab, GitHub or many other servers. https://codeberg.org/fredvs/uos Not doing pub but that Codeberg has server on Europe (Germany)... ---------------------------------------------------------------------- Martin_fr · 2022-09-04 23:11 This is all more than vague... First of all, the account does not seem to be blocked right now? All we have is a statement of that person (of whom we know little to nothing?) On the gitlab page the author wrote: QuoteThis move is because gitlab.com once suddenly blocked our account and another time made the repository private without any prior notice,"ONCE" => as in "one time in the past". (One  times is still one time to much, but...) And they had issues before (moved to private). Other than the statement, there is no proof. The user may have done so himself by accident, or given to much access to a contributor, or have been hacked..... I don't say any of this was the case, but I for once have no objective information about what really happened. (And any extremely vague hint by someone else, alluding of that person self- claimed non-proven inside knowledge... well that does not help either) Another easy explanation could be, he logged in from another browser => then you get an email, if that was you, or if you need to change your password. It contains a link, to be clicked only if it wasn't you. Maybe that got mistaken? Or maybe there once was a fault/bug/mistake at/by GitLab? Happens to the best. But if so, it doesn't look like it's something that is out of control. It's not like everytime you read about gitlab it ends in a warning.... All I can say is - he got access again, because he posted that statement. - the repo is still there, accessible to everyone All the rest seems speculation (as are all of my above possibilities) So overall, I don't think that having a project at gitlab is a risk of loosing access. Speculating again they (as a big entity) a probably in a much better position to protect my data for me against loss by hardware fault, hacker attack, even my own fault. A better position than I would be in if I hosted myself, or than a smaller entity might be. And as for trust, in the grand picture there is no reason not to. Also git is distributed. We always have a copy. Only the issues and merge requests, we don't have outside of gitlab. ---------------------------------------------------------------------- dbannon · 2022-09-04 23:59 Yes, never attribute to malice that which is adequately explained by incompetence. Davo ---------------------------------------------------------------------- Fred vS · 2022-09-05 09:54 Quote from: Martin_fr on September 05, 2022, 01:11:36 amFirst of all, the account does not seem to be blocked right now? All we have is a statement of that person (of whom we know little to nothing?) On the gitlab page the author wrote: QuoteThis move is because gitlab.com once suddenly blocked our account and another time made the repository private without any prior notice,"ONCE" => as in "one time in the past". (One  times is still one time to much, but...) And they had issues before (moved to private). Hum, indeed I have seen that too. But I trust Olli, if he said that he got problems, it is true. And what I like with CodeBerg is that it seems to not be part of a giant group, like GitHub and GitLab, and that the main servers are in EU-Germany. Fre;D ---------------------------------------------------------------------- Fred vS · 2022-09-05 16:44 Quote from: Thaddy on September 04, 2022, 07:04:15 pmI strongly discourage the use of codeberg, obviously. @Thaddy: Could you give, please, the obvious reason why? ---------------------------------------------------------------------- af0815 · 2022-09-05 17:39 @Thaddy: Could you give, please, the obvious reason why? The theme is interesting. Why ?! The project is holded by society (Verein e V.) which is accepted by german tax office as a non-profit organization. ---------------------------------------------------------------------- Olli · 2022-09-05 18:14 Quote from: Martin_fr on September 05, 2022, 01:11:36 amThis is all more than vague... First of all, the account does not seem to be blocked right now? All we have is a statement of that person (of whom we know little to nothing?) ... Other than the statement, there is no proof. The user may have done so himself by accident, or given to much access to a contributor, or have been hacked..... I don't say any of this was the case, but I for once have no objective information about what really happened. (And any extremely vague hint by someone else, alluding of that person self- claimed non-proven inside knowledge... well that does not help either) Another easy explanation could be, he logged in from another browser => then you get an email, if that was you, or if you need to change your password. It contains a link, to be clicked only if it wasn't you. Maybe that got mistaken? Hi everyone! My name is Olli. I joined in as here seems to be some discussion about my project ("soundtouch") and also my character. So, I wrote an account about this git-blocked-event that resulted into the Soundtouch project moving to Codeberg service here, as reply to thread that Fred opened: https://forum.gitlab.com/t/gitlab-blocked- account/74570/7?u=ollip So why moved to codeberg in particular: 1. It seems that Codelab has policy that they can block projects, no warnings given, no explanations provided afterwards. If you make a google search "site:gitlab.com account blocked" you'll find that quite many other projects have had the same experience. I don't give advice but personally I didn't like the unnecessary mess caused to maintainers & users by a git repository just suddenly disappearing for a week, so I moved soundtouch project elsewhere. The old gitlab account is still there because some projects may still depend on it. 2. I asked other Soundtouch users for alternative git hosts, and got several recommendations to use Codeberg, so that's where I then went to. --- Then about this "that person of whom we know little to nothing" piece  : - to cover this gap: I am 46 years old, male as assumed gender, live in Helsinki Finland, have two kids at pre/teen age, am obviously fond of computers as the household seems to have 11 PCs when I previously counted although kids may have carried couple more in, am working among software for living, currently among weather systems in particular. This site seems to be about Pascal, and Pascal was the 3rd programming language I knew after commodore64-basic and -assembly, and the first programming language that earned salary to myself in 1996. Delphi was wonderful, and was far-far ahead in ease of use compared to the concurrently fashionable react+npm UI development toolchains are today. What else. Pepsi and Coke taste equally well. Am also fond of riding mountain bikes + motor bikes + kayaking. So hi to everyone. ---------------------------------------------------------------------- MarkMLl · 2022-09-05 18:34 Welcome to the forum Olli. I'm only a bystander in this discussion but I'd suggest that (a) corporates- including (the owners of) Sourceforge, GitHub and GitLab- don't necessarily take criticism of their policies or behaviour in good grace and (b) as somebody has already said I think that anybody who selects a hosting service without careful consideration of the jurisdiction in which it resides is being naive. Leaving aside my personal distaste for Git and my dislike of being railroaded into using it, the FPC and Lazarus projects have previously had problems where SourceForge refused to service connections from countries on the USA's shitlist. Since the projects have a comparatively small number of users in the USA and its satellites, I think it would be fair to argue that tying them to a hosting service subject to USA law and potentially dismissive of anybody else's position is unfortunate. MarkMLl ---------------------------------------------------------------------- Fred vS · 2022-09-05 18:44 Hello and welcome Olli. You forgot to mention the fpc Pascal header of your fantastic library ( used by many great apps, like Audacity). https://codeberg.org/soundtouch/soundtouch/src/branch/master/source/So undTouchDLL/SoundTouchDLL.pas (By the way, the code could be updated to be Unix compatible, like this one: https://github.com/fredvs/uos/blob/main/src/uos_soundtouch.pas) Fre;D ---------------------------------------------------------------------- Martin_fr · 2022-09-05 23:04 QuoteThen about this "that person of whom we know little to nothing" piece It's ok, without a full CV.... Given that you care enough to respond, is the kind of tell-tale needed here. It is unfortunate that you never got to know what it was. After all now you don't know if it is something that codeberg would have to legally apply to. (ok, if so you would find out if they react faster). They are in Europe and have to follow European law. If they believe, or are made to believe (even if by false claims) that your repo violates the law, then they must act. At least I believe that is the rule. I.e. they offer you there servers, and they aren't hold accountable for what you do, until such time as they learn about it. Code: Pascal  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i  If you make a google search "site:gitlab.com account blocked"Most of the results seem to be help pages by gitlab. I followed some of the others. - One ignored a mail that told him he had to act to avoid this... - One had code that violated some rules (not sure copyrighted or similar / quite a long story, didn't read to the end / he got replies though) The google result I got, don't seem out of the ordinary to me... After all, one would expect some people getting into such issues. Gitlab must follow the law.... And may have some rules on top. Also maybe they do track suspicious behaviour patterns, to identify spammers, hackers and the like. That would be for the protection of all, and even if there was the occasional false positive, a benefit for all. We ban spammers from the forum. Some before they even post any spam. Once in a blue moon we kick the wrong person out. When we get feedback about it, we apologize. I do agree though that in your case communications have gone badly wrong. ---------------------------------------------------------------------- Fred vS · 2022-09-05 23:38 Maybe it is a problem with the servers that they prefer not to admit. GitLab has 30 million members and each one can have many projects. Is it not "lot of" for the servers to manage all that? (GitHub has 83 million members!) PS:  The numbers of members come from Google : github how many members and gitlab how many members ---------------------------------------------------------------------- Martin_fr · 2022-09-05 23:59 From Codeberg QuoteContent that is deemed illegal in Germany (e.g. by violating copyright or privacy laws) will be taken offline and may lead to immediate account suspension.QuoteForks, migrations and testing repos are considered as inactive when they don't contain unique contributions and are inactive for more than a month. They shouldn't be kept for a prolonged amount of time, and thus might be removed after notifying maintainers and providing a 90 days period to ask for preservation. Quote Abandoned user accounts or organizations with no (or extremely few) all-time contributions may be deleted after being unused for 365 days. A warning via email is sent 1 month in advance. The "must be active" is likely not an issue for most. But we have still some private testing repos, that may get less frequent updates. And a backup of the git, immediately after the svn conversion. That just sits around with no changes. ---------------------------------------------------------------------- Fred vS · 2022-09-06 00:18 Quote from: Martin_fr on September 06, 2022, 01:59:26 amFrom Codeberg QuoteForks, migrations and testing repos are considered as inactive when they don't contain unique contributions and are inactive for more than a month. They shouldn't be kept for a prolonged amount of time, and thus might be removed after notifying maintainers and providing a 90 days period to ask for preservation. The "must be active" is likely not an issue for most. Hum, indeed, one month is a few short but if they give notification regularly until 90 days after first notif, well, ok. So, to resume, maybe Codeberg for active projects who dont want to depend of USA laws and agree with EU-Germany laws. Maybe not for mirror or backup. ---------------------------------------------------------------------- Martin_fr · 2022-09-06 01:02 There are other considerations. Codeberg is a "Eingetragener Verein" = registered society? They have 200 members in that society.  I don't know if they have any paid stuff to perform duties or support. They have 32.000 Users, that may want/need support. And then there are practical issues. We had to decide between GitHub and GitLab. IIRC some considerations was their userbase. Had we chosen GitHub more Lazarus users may have had an account there already. But Gitlab had the better offer for open source projects, in terms of features. (I don't have the list at hand). Comparing a huge platform like Gitlab to CodeBerg... GitLab offers us a huge amount of free CI minutes. Could codeberg do that? Given that CodeBerg is very concerned about not wasting storage, where as again GitLab doesn't need to care about some dead repo sitting on their server. GitLab likely has some resistance against DDOS, where does Codeberg stand? (Given that google recently successfully defended one of their clients against a DDOS with 46million requests per second https://www.heise.de/news/Rekord-DDoS-auf-Layer-7-Google-wehrt- ab-7235554.html ) Don't get me wrong, I am all for small independent suppliers. But no one shoe fits all. Also we have git mirrors on GitHub and Sourceforge. So we wouldn't be inaccessible. Every developer has a copy of the git repo, it could me moved to a new host in no time. Users would only need to change the remote url, no new download, git would pick up where it was. The only issue would be getting and moving all the bug reports. ---------------------------------------------------------------------- Fred vS · 2022-09-06 01:02 Quote from: Martin_fr on September 06, 2022, 01:59:26 amAnd a backup of the git, immediately after the svn conversion. Of couuurse not now!  By the way, after less than 2 minutes (I promise) the migration from fpc-gitlab to fpc-codeberg was done. With the gitlab-issues. Tip: For migration choose "Git" (not "GitLab" because it does not accept the "." in /freepascal.org/) No tuning done yet. To update the site, just do regularly in the fpc git-directory: Code: Bash  [Select][+][-]window.onload = function(){var x1 = document.getElementById("main_content_section"); if (x1) { var x = document.getElementsByClassName("geshi");for (var i = 0; i > git push --mirror https://codeberg.org/freepascal-org/fpc/source https://codeberg.org/fredvs/freepascal ---------------------------------------------------------------------- Fred vS · 2022-09-06 01:14 Quote from: Martin_fr on September 06, 2022, 03:02:36 amThere are other considerations. ::: The only issue would be getting and moving all the bug reports. That is not a big issue, there are converters for this or, like Codeberg propose, link the issues with GilLab issues (see in the fpc migration in previous post). ---------------------------------------------------------------------- Martin_fr · 2022-09-06 02:12 Quote from: Fred vS on September 06, 2022, 03:14:38 amQuote from: Martin_fr on September 06, 2022, 03:02:36 amThere are other considerations. ::: The only issue would be getting and moving all the bug reports. That is not a big issue, there are converters for this or, like Codeberg propose, link the issues with GilLab issues (see in the fpc migration in previous post). "The only issue would be getting and moving all the bug reports." This was meant in the context of GitLab unexpectedly and permanently locking us out, so that we would not be able to access anything. ---------------------------------------------------------------------- Fred vS · 2022-09-06 02:30 Quote from: Martin_fr on September 06, 2022, 04:12:56 amQuote from: Fred vS on September 06, 2022, 03:14:38 amQuote from: Martin_fr on September 06, 2022, 03:02:36 amThere are other considerations. ::: The only issue would be getting and moving all the bug reports. That is not a big issue, there are converters for this or, like Codeberg propose, link the issues with GilLab issues (see in the fpc migration in previous post). "The only issue would be getting and moving all the bug reports." This was meant in the context of GitLab unexpectedly and permanently locking us out, so that we would not be able to access anything. Imho, the best would be to have a independent "issue-site" hosted in one of your server (if fpc has one). (By the way, where is hosted Lazarus forum?) I did not check yet if GitLab gives the possibility to use a external issues-site like Codeberg does. . ---------------------------------------------------------------------- PascalDragon · 2022-09-06 05:49 Quote from: MarkMLl on September 05, 2022, 08:34:07 pmWelcome to the forum Olli. I'm only a bystander in this discussion but I'd suggest that (a) corporates- including (the owners of) Sourceforge, GitHub and GitLab- don't necessarily take criticism of their policies or behaviour in good grace and (b) as somebody has already said I think that anybody who selects a hosting service without careful consideration of the jurisdiction in which it resides is being naive. Leaving aside my personal distaste for Git and my dislike of being railroaded into using it, the FPC and Lazarus projects have previously had problems where SourceForge refused to service connections from countries on the USA's shitlist. Since the projects have a comparatively small number of users in the USA and its satellites, I think it would be fair to argue that tying them to a hosting service subject to USA law and potentially dismissive of anybody else's position is unfortunate. This is after all the main reason why we went with GitLab instead of GitHub: if push comes to shove and either our own projects or users of our project are cut of then we can set up a GitLab instance ourself and just move things over. Quote from: Fred vS on September 06, 2022, 04:30:32 amQuote from: Martin_fr on September 06, 2022, 04:12:56 amQuote from: Fred vS on September 06, 2022, 03:14:38 amQuote from: Martin_fr on September 06, 2022, 03:02:36 amThere are other considerations. ::: The only issue would be getting and moving all the bug reports. That is not a big issue, there are converters for this or, like Codeberg propose, link the issues with GilLab issues (see in the fpc migration in previous post). "The only issue would be getting and moving all the bug reports." This was meant in the context of GitLab unexpectedly and permanently locking us out, so that we would not be able to access anything. Imho, the best would be to have a independent "issue-site" hosted in one of your server (if fpc has one). (By the way, where is hosted Lazarus forum?) FPC has its own servers which is where the mailing lists and the main website are hosted. I think the Lazarus forum and the wiki are hosted on a different server provided by the Lazarus team. And then there's the FTP server. All are located in Europe. ---------------------------------------------------------------------- af0815 · 2022-09-06 06:58 I think "GitLab vs Codeberg.org" is not a discussion for the fpc/lazarus project. The settlement for this projects were done. But my question is, why should Codeberg avoided as Thaddy wrote. For me is a git hoster in Europe a good thing and i have no problem with the german law. I know it a little more than the US. law. I think i can give them a chance with my small projects. ---------------------------------------------------------------------- marcov · 2022-09-06 07:13 Quote from: PascalDragon on September 06, 2022, 07:49:52 amFPC has its own servers which is where the mailing lists and the main website are hosted. I think the Lazarus forum and the wiki are hosted on a different server provided by the Lazarus team. And then there's the FTP server. All are located in Europe. FTP and Lazarus server are the same (Scenergy) ---------------------------------------------------------------------- MarkMLl · 2022-09-06 07:38 Quote from: Martin_fr on September 06, 2022, 01:04:06 amIf they believe, or are made to believe (even if by false claims) that your repo violates the law, then they must act. At least I believe that is the rule. I.e. they offer you there servers, and they aren't hold accountable for what you do, until such time as they learn about it. But they have to satisfy themselves that the person demanding the action is legally empowered to do so. In principle, that means a warrant signed off by a court. Two cases that illustrate when things have gone wrong. First, a number of years ago Rackspace UK (I think) gave a server to the FBI because it contained photographs they wanted which had been taken in Switzerland. There was, quite correctly, a massive row since no British or European legal process was involved. Having worked for a couple of multinationals, I have some sympathy for the people on the ground who suddenly got an unwelcome directive from on high... but even so. Second, a number of years ago the UK blocked access to Wikipedia since some semi-independent body had decided that the "Virgin Killer" page was offensive. Again, there was an outcry. Together, these highlight that (a) process must be followed in the appropriate (or at least dominant) jurisdiction and (b) the broader community must ensure by constant vigilance that anybody who is empowered to interfere is well-informed as well as being well- intentioned. The bottom line is that any project or entity needs mirrors in multiple jurisdictions, together with safeguards against one mirror subverting the remainder (which I suspect is rather a tall order) or declare itself the one true root. MarkMLl ---------------------------------------------------------------------- PascalDragon · 2022-09-06 11:57 Quote from: MarkMLl on September 06, 2022, 09:38:39 amQuote from: Martin_fr on September 06, 2022, 01:04:06 amIf they believe, or are made to believe (even if by false claims) that your repo violates the law, then they must act. At least I believe that is the rule. I.e. they offer you there servers, and they aren't hold accountable for what you do, until such time as they learn about it. But they have to satisfy themselves that the person demanding the action is legally empowered to do so. In principle, that means a warrant signed off by a court. But even if there are warrants it can be that the claims are incorrect (see the RIAA takedown request of youtube-dl two years ago) and then you'll have unexpected downtime of services. And then there's the story where SourceForge had/has to block users from certain foreign countries due to US policies... ---------------------------------------------------------------------- MarkMLl · 2022-09-06 12:27 Quote from: PascalDragon on September 06, 2022, 01:57:33 pmBut even if there are warrants it can be that the claims are incorrect (see the RIAA takedown request of youtube-dl two years ago) and then you'll have unexpected downtime of services. Yes, but at least by then there's a papertrail of what's happened and in principle that can be followed all the way to the local legislature in order to get a badly-drafted law clarified (including tightening up QUANGO supervision etc.). It's unfortunate the extent to which that enriches the legal profession, but that should be a reminder to all of us that we should be actively scrutinising the legislative process. QuoteAnd then there's the story where SourceForge had/has to block users from certain foreign countries due to US policies... Yes, I already mentioned that that has in the past affected FPC/Lazarus. But the bottom line in both cases is that since we are predominantly a European project, we stand absolutely zero chance of sorting out a foulup caused originally by the American (or Chinese, Russian etc.) government MarkMLl ---------------------------------------------------------------------- Fred vS · 2022-09-06 14:30 Quote from: PascalDragon on September 06, 2022, 01:57:33 pmAnd 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 ---------------------------------------------------------------------- MarkMLl · 2022-09-06 15:03 Quote from: Fred vS on September 06, 2022, 04:30:32 pmAbsolutely scandalous ( or ridiculous ) but GitLab does the same: https://gitlab.com/gitlab-org/gitlab/-/issues/260406 Nothing at all scandalous: neither more nor less than you'd expect if they're domiciled in the USA. Far more scandalous is Apple- undeniably an American company, whatever its "flag of convenience"- refusing (or pleading inability) to provide information to the FBI etc. after being ordered to. MarkMLl ---------------------------------------------------------------------- Fred vS · 2022-09-06 15:22 Quote from: MarkMLl on September 06, 2022, 05:03:52 pmQuote from: Fred vS on September 06, 2022, 04:30:32 pmAbsolutely scandalous ( or ridiculous ) but GitLab does the same: https://gitlab.com/gitlab- org/gitlab/-/issues/260406 Nothing at all scandalous: neither more nor less than you'd expect if they're domiciled in the USA. OK, then ridiculous. I was talking about a law that prohibits some people from viewing a site of open-source-projects-that-comply-with-US-laws. Not about the company that follows the laws. Quote from: MarkMLl on September 06, 2022, 05:03:52 pmFar more scandalous is Apple- undeniably an American company, whatever its "flag of convenience"- refusing (or pleading inability) to provide information to the FBI etc. after being ordered to. I agree with you for the principle, you are a US company, follow the US laws or close your company in US and go in a other country. ---------------------------------------------------------------------- Fred vS · 2022-09-06 18:38 About a independent issues tracker: There are lot of that can import the csv from GitLab-issues-export-csv https://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems But yes, needs some work and passion (or obligation) to do it. And also lot of time to choose the best independent issues tracker. ---------------------------------------------------------------------- PascalDragon · 2022-09-07 07:58 Quote from: Fred vS on September 06, 2022, 08:38:14 pmAbout a independent issues tracker: I don't know how this discussion came up, but we currently do not plan to move away from GitLab, so any discussion about independent issues trackers is useless. ---------------------------------------------------------------------- Fred vS · 2022-09-07 10:03 Quote from: PascalDragon on September 07, 2022, 09:58:41 amQuote from: Fred vS on September 06, 2022, 08:38:14 pmAbout a independent issues tracker: I don't know how this discussion came up, but we currently do not plan to move away from GitLab, so any discussion about independent issues trackers is useless. 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. ---------------------------------------------------------------------- Martin_fr · 2022-09-07 11:17 Quote from: Fred vS on September 07, 2022, 12:03:11 pmOf 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) ---------------------------------------------------------------------- PascalDragon · 2022-09-07 11:27 Quote from: Fred vS on September 07, 2022, 12:03:11 pmQuote from: PascalDragon on September 07, 2022, 09:58:41 amQuote from: Fred vS on September 06, 2022, 08:38:14 pmAbout a independent issues tracker: I don't know how this discussion came up, but we currently do not plan to move away from GitLab, so any discussion about independent issues trackers is useless. 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. We don't want an independent tracker anymore. ---------------------------------------------------------------------- Fred vS · 2022-09-07 11:32 Quote from: PascalDragon on September 07, 2022, 01:27:07 pmQuote from: Fred vS on September 07, 2022, 12:03:11 pmQuote from: PascalDragon on September 07, 2022, 09:58:41 amQuote from: Fred vS on September 06, 2022, 08:38:14 pmAbout a independent issues tracker: I don't know how this discussion came up, but we currently do not plan to move away from GitLab, so any discussion about independent issues trackers is useless. 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. We don't want an independent tracker anymore. OK,ok, sorry for the noise. (But don't cry if the gas is cut off). ---------------------------------------------------------------------- PascalDragon · 2022-09-07 11:42 Quote from: Fred vS on September 07, 2022, 01:32:38 pm(But don't cry if the gas is cut off). That's why we went with GitLab in the first place: we can simply run our own instance then. (Also my flat is heated with oil, thank you very much) ---------------------------------------------------------------------- Fred vS · 2022-09-07 11:56 Quote from: PascalDragon on September 07, 2022, 01:42:40 pm(Also my flat is heated with oil, thank you very much) With recycled oil and with powerful filter in the chimney I hope. ---------------------------------------------------------------------- Fred vS · 2022-09-07 12:40 Quote from: Martin_fr on September 07, 2022, 01:17:05 pmQuote from: Fred vS on September 07, 2022, 12:03:11 pmOf 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 · 2022-09-08 08:45 Quote from: Fred vS on September 07, 2022, 01:56:17 pmWith 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 · 2022-09-09 09:51 Quote from: PascalDragon on September 07, 2022, 01:27:07 pmWe don't want an independent tracker anymore. Well, it was not unanimous :-) ---------------------------------------------------------------------- Bi0T1N · 2022-09-09 12:51 Quote from: Fred vS on September 06, 2022, 04:30:32 pmQuote from: PascalDragon on September 06, 2022, 01:57:33 pmAnd 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. Quote from: Fred vS on September 07, 2022, 02:40:50 pmOK, 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 · 2022-09-09 14:37 Quote from: Martin_fr on September 07, 2022, 01:17:05 pm... 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 · 2022-09-09 15:03 Quote from: Bi0T1N on September 09, 2022, 02:51:15 pmAs 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 · 2022-09-09 17:45 Quote from: Fred vS on September 06, 2022, 04:30:32 pmAbsolutely 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. Quote from: Fred vS on September 09, 2022, 04:37:32 pmBy 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.