Hi,
There are two interesting options here:

1. Codeberg: https://codeberg.org/about
Their service is free (but they live from donations) and can host:- source code 
+ issue tracker + wiki + CI/CD (all included with Foregejo)- Weblate (not sure 
if the FreeDOS locale can be used with it, but that would be great)- Pages 
(HTML + CSS + JavaScript can be used for basic websites managed through GIT)
 2. Disroot Forgejo: https://git.disroot.org/
Also free:
- source code + issue tracker + wiki + CI/CD (all included with Foregejo)
Example project: https://git.disroot.org/trougnouf/cfait
Specifically about Codeberg, they're been active for years and they're well 
organized, so that's where I would look first. Their service can sometimes be 
spotty, but they do a good job overall and it's worth talking to them for a 
potential migration to their services.

    On Wednesday, October 7, 2026 at 05:06:10 PM GMT+2, Jerome Shidel via 
Freedos-devel <[email protected]> wrote:  
 
 While working on a different project, I just found out about some changes 
coming to GitLab which are going to be a major issue to the current workflow.

Writing objects: 100% (11/11), 3.82 KiB | 1.91 MiB/s, done.
Total 11 (delta 8), reused 0 (delta 0), pack-reused 0
remote: 
remote: ========================================================================
remote: 
remote:  Scheduled rate-limit preview window: between 15:00 and 19:00 UTC on
remote:  7 October, the new limits will be briefly active so you can see how
remote:  your workloads are affected. They are live only during this window,
remote:              and apply permanently from 19 October. [Learn
remote:      more](https://about.gitlab.com/blog/rate-limit-change-2026/).
remote: 
remote: ========================================================================
remote: 
To gitlab.com:phppace/pace.git
  9a02876..19c6a77  master -> master

Looking over the announcement, they will be instituting various caps on access 
based on your account settings. And limiting non-user general access to 60 
requests an hour. Visit the page for exact details. 

This will be a problem on two fronts. 

First, when the RBEv3 assembles a release, it clones each project (like nearly 
400) then assembles the packages from those project files. So, it will flat out 
not work next month. 

Second, fdrepo connects as a non-user as well. But, it may be okay. Because, it 
first queries the git api in order to try and determine what apps have changed. 
Then it will clone the ones which have changed, generates a package, double 
checks that the contents of the package is actually different, then updates the 
repository if needed. I do not know if API queries will count against the limit 
or not. But, there are rarely more than a few projects which report things have 
changed. Even though multiple queries are needed to check all of the packages, 
it will likely be okay in fetching everything that is new. If not, it will 
likely get the rest on a future check. However, some tweaking may be needed to 
adjust the number of project status queries issued at a single time or to 
spread out those checks over a longer time period. 

But, for the RBEv3. IDK. There are a couple possibilities. None are optimal. 

For example:

* The RBEv3 could be updated to use a local copy of FDREPO to pull and cache 
projects. (Maybe, good enough. Maybe no. Don’t really want to mess with v3 
anymore than absolutely needed. It has more or less reached end-of-life. RBEv4 
was already planned to be much more efficient regarding project cloning and 
updating.) 

* Someone could fork out money to pay for our own GitLab Server. (Very 
sub-optimal). 

* Someone could fork out some cash to move the FreeDOS project groups from Free 
Tier to a paid version. (Very sub-optimal).

So, IDK.

I do know we cannot go back to the very old method of downloading the packages 
from IBIBLIO and generating a release. That server is just far to unreliable 
anymore. 

Regardless of what we decide to do in order to resolve this new problem, it is 
highly probably that there will not be a November Interim build because of 
personal time constraints. 

:-(

Jerome

_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
  
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to