how is codeberg? i am thinking about moving pkgconf to codeberg.

@ariadne I am finding it nice. The interface is usable and is like github before it got all cluttered. Critically, the administrators are easy to reach (for example via Matrix), easy to communicate with and reasonable. If you have CI/"github actions" tho idk how compatible they are with that (I think they don't do this inhouse, at least).

@mcc @ariadne the problem is that they doomscroll mastodon sometimes and tap on the post mentioning codeberg so it's presumably harder for people to talk smack 😅

but in all seriousness, it doesn't have 99.9999% uptime (unfortunately) and goes down sometimes. we are a bit messy and that is visible to the outside but are working on it. it is run by a small group of volunteers (so we might struggle during emergencies), some of my efforts involve growing that group.

@n0toose @mcc can i help this with money somehow?

@mcc @ariadne we (i) are also bad at selling things. but idk setting reasonable expectations makes people less angry at us (some find it refreshing) and i don't make money by making the user count go up. (i sometimes advocate for self-hosting or taking steps to decrease reliance on the forge itself, e.g. self-hosting some things or using another project's services, because it also helps denormalize single points of failure)

I'm not sure what I'm yapping about right now :D

@ariadne i noticed you use github actions. codeberg runs forgejo, which has a similar ci system, but it might have some differences. i am not sure whether codeberg has windows runners so it would be good to check. also my experience with forgejo ci is that the container image itself must have nodejs in it (xref: https://r.lily-is.land/tusooa/tusooa.pg.kazv.moe/actions/runs/7/jobs/1 ). this might be different from github actions, as i see your ci config does not specify an image with nodejs preinstalled.

@tusooa i defer to @DG0YT on all windows matters at this point 😂

@ariadne @DG0YT if you are ok with beginning all your ci jobs with installing nodejs via package manager (not "setup-node" action, because it requires you to have nodejs: https://r.lily-is.land/tusooa/tusooa.pg.kazv.moe/actions/runs/8/jobs/1 ), you "should" be fine. (i find it pretty ridiculous to do so, so i'm writing my own ci...)

@tusooa @DG0YT i do not believe any component of pkgconf (including CI) has any dependency on node.js

@ariadne that's exactly the point i'm making -- if you use forgejo actions, your container image must have nodejs before you can run most actions (e.g. checking out source code), which would not be reasonable if your project itself does not depend on it.

@tusooa i mean, that's fine, i can build a nightly CI image with apko 😂

@tusooa @ariadne Codeberg CI does not use Forgejo Actions, it uses Woodpecker CI. I think Codeberg CI actually predates Forgejo Actions existing.

@noisytoot @ariadne it does use forgejo actions https://codeberg.org/forgejo/forgejo/actions/runs/77163/jobs/0

@tusooa @ariadne You can use Forgejo Actions with Codeberg but you must self-host the runners (source: https://docs.codeberg.org/ci/actions/). Codeberg hosts Woodpecker CI (see, for example, https://ci.codeberg.org/repos/13361/pipeline/43).

@ariadne

No way that it is worse than Github.

@ariadne Soild meh

.I evaluated it about a year agp. ended up going with srht for accessibility

But i'd use it if it weren't for my requirements.

It's got no frills but it gets the job done

@piusbird i do not wish to use e-mail

@ariadne@treehouse.systems

what about #FossilSCM?
https://fossil-scm.org/home/doc/trunk/www/index.wiki

It's the easiest forge to self-host but if you don't have an online server or a small vps, a cheap web hosting with #cgi support (the ones that often comes for free when you but a domain name) is enough!

@giacomo i do not wish to self-host at this time

@ariadne @giacomo Don't you selfhost gitea on treehouse infrastructure?

@fun @giacomo i would like to stop using it for pkgconf

@ariadne @giacomo Has it become hard to maintain, or ? (if you don't mind)

@fun @giacomo yes, basically. CI for example is entirely broken due to hardware problems.

@ariadne @giacomo I've heard Codeberg worked nice for many then.