I have a few personal projects on Gitlab. Mostly I use them because my employer uses the self-hosted version. Their products are propriatery and probably need

I have a few personal projects on Gitlab. Mostly I use them because my employer uses the self-hosted version. Their products are propriatery and probably need to be stored internally for compliance reasons. I thought the self-hosted product was their USP-- believed it enough to buy a few hundred bucks of GTLB shares (-40% :sigh:) The most successful of my projects has a potential audience of a few hundred users-- custom firmware for specific obscure hardware. The others, the likely user base is likely one. I suspect that's what a lot of hobbyist projects are going to be-- an itch scratched for a single user and/or a very small community, perhaps cast into the void with the thought "someone else might find some value in it" or "this helps as a portfolio for future job interviews-- lets me showcase technologies I don't work on 40 hours a week" The thing is, this means that there's a fair chance you're going to reach endgame. You don't need any more features because your itch is scratched. There will be no new commits, but it's nice to have the archive for when someone actually needs the code. So activity is an awful proxy for value here.