Goodbye GitHub ... ?

[mer]

So what exactly are we talking about here? Self hosting code/revision management has been around for a very long time, heck back to rcs and cvs and earlier.

What "github" and others get you is the ability to share your stuff with others, allow them to contribute and yes potentially "steal".

It all goes back to what the OP desires: if it's making private work available to the public, you kind of have 2 options:
Self host and make publicly available which opens you to all the downfalls
Use an existing publicly available resource under whatever EULA they provide

 

[bakul]

What do you think of? How do you handle it on your end? Thanks.

My only advice is to not tie yourself to any specific hosting platform & always keep a local copy of anything you care about (& have space for).

 

[DanielBowman]

Not having your free code stolen by a few billionaires must be a nightmare.

I believe he is not coding recipe for his own version of Coca Cola.

 

[rbranco]

monwarez I understand what you mean, but let’s not get into a political debate, what you’re saying could apply to anything, and it doesn’t change the fact that Codeberg lacks a clear stance on AI, using vague terms like "heavy use."

I’m just looking for a remote repository to store some code in and gain a bit of visibility

You can self-host if you have the resources, but Gitea is better. Codeberg forked Gitea and chose the worst license for Forgejo.

 

[Cthulhux]

git, fossil, hg, whatever is basically the same for a one-person-project

Git and Mercurial are optimised for being used in Bazaar projects, but most people actually have a Cathedral.

 

[Cthulhux]

I believe he is not coding recipe for his own version of Coca Cola.

That’s not the point of software licensing now, is it? A license should be valid even if nobody but two people on Earth will ever use the software.

 

[JohnK]

ai:
I buy the boat.
I buy the fishing pole.
I buy the license.
I get up at 5:00am.
I drive the boat to the supermarket.
I eat the fish someone else caught.

Git and Mercurial are optimised for being used in Bazaar projects, but most people actually have a Cathedral.

Agreed, but let's not place unnecessary importance on something not fundamentally important (most solo dev's wouldn't care one iota between the differences between B v C). "Push", "Pull", "Undo"... -i.e., "make a backup of my genius, magic thing".

I’m just looking for a remote repository to store some code in and gain a bit of visibility

You can self-host if you have the resources, but Gitea is better. Codeberg forked Gitea and chose the worst license for Forgejo.

Again, you are confusing the situation. It doesnt take anything more than git-tiny to self host. Visiablity is another thing entirely. You can self host, invite others to partake witout ever publicly sharing just code code. Create code, create blog, publicize email. You can self host on the smallest / slowest machine you own.

 

[rbranco]

Again, you are confusing the situation. It doesnt take anything more than git-tiny to self host. Visiablity is another thing entirely. You can self host, invite others to partake witout ever publicly sharing just code code. Create code, create blog, publicize email. You can self host on the smallest / slowest machine you own.

A git forge is for more than just sharing. Sigh. It allows for tracking issues, CI integration, etc.

 

[JohnK]

A git forge is for more than just sharing. Sigh. It allows for tracking issues, CI integration, etc.

Oh yes I forgot, developers could not track *any* issues before github via things like text files or TODOs. What's wrong with githooks or entr(1) or...?

entr(1)

EDIT:
Look, I made something:

// TODO: Task/Issue &date @assigned ^priority %tag #hash

 

[drhowarddrfine]

I spent time learning Git, it does what I need it to do, and I don't see any reason to switch to something else.

One of the guys at my company decided we should learn git. So he spent time doing so. After losing some of his work for the third time, that was the end of that. He went back to Mercurial.
Everyone can have a story but that's mine.

 

[hruodr]

git, fossil, hg, whatever is basically the same for a one-person-project so, what does that have to do with anything (they are all decentralized VCS--the "interface" is a minor)? there is also, knowing git will allow you to switch to got.

Almost all scm have similar commands. Of course, small differences may become trap.

Git and Mercurial are optimised for being used in Bazaar projects, but most people actually have a Cathedral.

fossil for cathedral, and a person working alone will very probably follow the cathedral model.

Oh yes I forgot, developers could not track *any* issues before github via things like text files or TODOs. What's wrong with githooks or entr(1) or...?
entr(1)

for CVS there is:

CVSTrac Legacy Code: Browser Verification

It is from the same author of fossil, later, its functionality was included in fossil.

You can self-host if you have the resources, but Gitea is better. Codeberg forked Gitea and chose the worst license for Forgejo.

It is very easy to run many fossil instances, for different projects, as cgi.

I like to have a server, then is a form of backup. I have the local and the remote copy of the repo.

One can get for free a server for running CGI. Or one can use:

https://chiselapp.com/

The problem is, they have not the same publicity as github & co.

 

[T-Aoki]

You can always selfhost gitea, forejo or other options. The main reason to be on one of the shared sites is either for visibility or to share, and you can always send the private repo to a public one.

I generally just use git on my local filesystem, but I'll likely switch to gitea in a jail if I start coding regularly on my laptop.

MY understanding for shared, public repos running Forgejo, Codeberg, GitLab or GitHub are needed for forks that can handle pull requests each other, and having "issues" (bug tracker) functionalities.
Especially, pull request can't be made from local, private repo that cannot be accessed from Internet. How anyone pull commits from the repo?
Only public repos facing and accepting connection from Internet can, except in orgnaization (including SOHO) internal networks by the members.

 

[JohnK]

MY understanding for shared, public repos running Forgejo, Codeberg, GitLab or GitHub are needed for forks that can handle pull requests each other, and having "issues" (bug tracker) functionalities.
Especially, pull request can't be made from local, private repo that cannot be accessed from Internet. How anyone pull commits from the repo?
Only public repos facing and accepting connection from Internet can, except in orgnaization (including SOHO) internal networks by the members.

A fork is nothing other than another copy of the repo (hence: "decentralized").

Basics:
If you have ssh(1) access, you *can* allow others access as well so you can both push/pull to `main`. The GUI (forge) does not offer you anything new.

With git cli, you do pull requests the same as git gui (forge).

       % git fetch origin pull/<ID>/head:<BRANCHNAME>

    where <ID> is the pull request id and <BRANCHNAME> is the name of the
    new branch that you want to create. Once you have created the branch,
    then simply
        % git checkout $BRANCHNAME

 

[T-Aoki]

A fork is nothing other than another copy of the repo (hence: "decentralized").

Thanks!
I was not sure whether fork is a simple copy (with recording and exposing "who forked what, when") or specially expanded branches (to reduce capacities without help of dedupe features in underlying filesystems).

But anyway, "facing Internet and always accepting connection from Internet" would be the key to handle pull requests, regardless how forks are implemented.

 

[rbranco]

Oh yes I forgot, developers could not track *any* issues before github via things like text files or TODOs. What's wrong with githooks or entr(1) or...?

This is human slop or what? A TODO file is not a system that lets other users file issues.

 

[T-Aoki]

This is human slop or what? A TODO file is not a system that lets other users file issues.

Human slops. And AI slops, too.
Both are NOT perfect.
So the intermediate and (relatively safe not to be sued somewhere) effective way would be:

1. Let AI / LLM to find bugs.
2. The operator (or the person's natural human co-workers) write fixes to clarify natural human copyright holder.
3. Let AI / LLM to review the fix.
4. And once AI / LLM says OK, review by natural human again (as the authorized and responsible person).
5. Then, submit the fix once the responsible natural human finds it OK and no one others already proposed fixes.

 

[rbranco]

Human slops. And AI slops, too.
Both are NOT perfect.
So the intermediate and (relatively safe not to be sued somewhere) effective way would be:

1. Let AI / LLM to find bugs.
2. The operator (or the person's natural human co-workers) write fixes to clarify natural human copyright holder.
3. Let AI / LLM to review the fix.
4. And once AI / LLM says OK, review by natural human again (as the authorized and responsible person).
5. Then, submit the fix once the responsible natural human finds it OK and no one others already proposed fixes.

And I mostly agree. Nobody but vibecoders let AI have all the fun.

Submitting code not reviewed by AI is rude.

 

[rmomota]

Why would you do that when you can have git over ssh?

a NAS storage accessible by ssh? sure
With 3 SSDs in a RAIDZ1 for git repos data redundancy would be a good alternative for Github.

 

[cracauer@]

ai is stupid.

why even use a GUI (like gitlab or gitea or...)? You're already using the shell to interact with your VCS. My git server is headless (you should do that too).

git, fossil, hg, whatever is basically the same for a one-person-project so, what does that have to do with anything (they are all decentralized VCS--the "interface" is a minor)? there is also, knowing git will allow you to switch to got.

Keep in mind that there are GUI programs to examine a checked out tree. I used gitk quite a bit.

Not everything has to be web based.

 

[DanielBowman]

That’s not the point of software licensing now, is it? A license should be valid even if nobody but two people on Earth will ever use the software.

If someone copies your GPLv2 licensed code, closes it and sells it, you will never know.

 

[DanielBowman]

One of the guys at my company decided we should learn git. So he spent time doing so. After losing some of his work for the third time, that was the end of that. He went back to Mercurial.
Everyone can have a story but that's mine.

LOL.
I have similar stories with vmware snapshots, which are much easier to grasp and not done that often...but far more catasthropic.
Some people just can't grasp it.
I absolutely loved it, when some genius treated snapshots as backups, while delta files just bloating and bloating.

 

[JohnK]

This is human slop or what? A TODO file is not a system that lets other users file issues.

Human slops. And

Yes, the concept of a task/TODO file and/or inline TODOs is slop. No one ever uses them. Same with git hooks. Do not ever do/use either.

I wonder how GitHub keep's track of issues? It must be witchcraft!

Keep in mind that there are GUI programs to examine a checked out tree. I used gitk quite a bit.

There is absolutly nothing wrong with using a gui of any kind (even if it's web based). My response was to the general slopper tone of the thread (which is becoming more and more prelavent) lately.

 

[MG]

I don’t think that Git is the best choice for most people in the first place, so I avoid it’s whole ecosystem. No “AI” anywhere.

It really sucks that p2p networks are phased out by the copyrights mafia. That was actually the best solution for a public software project. These commercial centralized providers are a joke. They exploit everything that has potential for profit. Open source or not, I won't give anything to Microsoft anyway. That's just ridiculous. For what exactly? A file hosting service? They may take effort to get it and publicate it themselves...