• 0 Posts
  • 19 Comments
Joined 4 days ago
cake
Cake day: January 21st, 2025

help-circle







  • Create a new repo locally.

    git init
    git add .
    git commit -m "Initial commit"
    

    Then to create a new remote repo, you can do this.

    git remote add origin git@git.sr.ht:~user/my-new-repo
    git push origin main
    

    You’ll get a message that says.

    remote: 
    remote:         NOTICE
    remote: 
    remote:         You have pushed to a repository which did not exist. ~user/my-new-repo
    remote:         has been created automatically. You can re-configure or delete this
    remote:         repository at the following URL:
    remote: 
    remote:         https://git.sr.ht/~user/my-new-repo/settings/info
    



  • Interesting! I didn’t realize this! https://www.gnu.org/licenses/why-assign.en.html

    only the copyright holder or someone having assignment of the copyright can enforce the license. If there are multiple authors of a copyrighted work, successful enforcement depends on having the cooperation of all authors.

    So it seems like the FSF does this in order to be able to enforce GPL. Buuut, these guys really gotta be the exception. I feel like the probability of the FSF selling out and going full corporate evil is pretty low…

    a good idea to have a CLA so that’s no conflict that the project owns the code.

    That’s exactly the problem though. The project owning the code, instead of the contributors owning the code.