Just to clarify our stance: We're happy to accept large free/libre software projects migrating to Codeberg. This can even happen in a hurry. And we're ready to help with the migration as good as possible.
But to reiterate: Hosting proprietary content on Codeberg is not allowed. And: Causing excessive traffic to mostly proprietary content is even less allowed.
My estimate would be that github can sustain a lot more bandwidth than codeberg ever will, but correct me if I am wrong. No offense, but M$ has the $-sign in the name.
So hosting an "excessive bandwidth" repository probably just means the excessive bandwidth M$ managers had in their inbox due to friends and lobbyists complaining about said repository?
@girlintech If a user does not choose to distribute their source code / project with a license anywhere on the Internet, it is "proprietary" (or what we would refer to as "source-available"). It's similar to photos or art shared online: Just because it's out there, that doesn't mean you can (re)use that material however you want.
With that being said, we do not force someone to use a license through our ToS, but you'd be breaking our rules, somewhat. ~n
@girlintech We allow small repositories to keep notes etc. under specific conditions.
We're a nonprofit, primarily sustained through volunteer efforts and donations meant to fund a platform that helps people "give something back" to the world. It wouldn't be productive if we forced people to also use another platform for those small things, however. ~n
@girlintech I'm not responsible for handling these situations, but, from what I've gathered, it'd involve a warning, a popup with a reminder (if you use lots of space), or a personal ask to fix this (sent using your email address). Accidents happen and people can forget things sometimes.
This isn't a rule applying to all situations, however. But please don't panic. 😀 ~n
@ProfessorCode @girlintech Again, it wouldn't be productive if we forced you to host everything BUT your very small config files on GitHub. We're fine with it if you don't want to show these anywhere apart from... eh, perhaps the confessional booth. 😀
"[Private repositories] are also allowed for really small & personal stuff like your journal, config files, ideas or notes, but explicitly not as a personal cloud or media storage." See codeberg.org/Codeberg/org/src/…. ~n
@girlintech Releasing "compiled" artifacts without the code is typically not considered free software, same as how compiled binaries are typically not considered free software.
Encrypting your code before sharing would probably fall into the very same category. ~f @ProfessorCode
(i ask because i had (in my mind) an open license but forget to upload it "officially" for month, so it's to know how you andle this kind of thing when you come across those project (maybe a warning ?)
Anselm Schüler
Als Antwort auf Codeberg.org • • •Codeberg.org
Als Antwort auf Codeberg.org • • •Just to clarify our stance: We're happy to accept large free/libre software projects migrating to Codeberg. This can even happen in a hurry. And we're ready to help with the migration as good as possible.
But to reiterate: Hosting proprietary content on Codeberg is not allowed.
And: Causing excessive traffic to mostly proprietary content is even less allowed.
Thanks.
Harald
Als Antwort auf Codeberg.org • • •My estimate would be that github can sustain a lot more bandwidth than codeberg ever will, but correct me if I am wrong. No offense, but M$ has the $-sign in the name.
So hosting an "excessive bandwidth" repository probably just means the excessive bandwidth M$ managers had in their inbox due to friends and lobbyists complaining about said repository?
Codeberg.org
Unbekannter Ursprungsbeitrag • • •@girlintech If a user does not choose to distribute their source code / project with a license anywhere on the Internet, it is "proprietary" (or what we would refer to as "source-available"). It's similar to photos or art shared online: Just because it's out there, that doesn't mean you can (re)use that material however you want.
With that being said, we do not force someone to use a license through our ToS, but you'd be breaking our rules, somewhat. ~n
Codeberg.org
Als Antwort auf Codeberg.org • • •@girlintech We allow small repositories to keep notes etc. under specific conditions.
We're a nonprofit, primarily sustained through volunteer efforts and donations meant to fund a platform that helps people "give something back" to the world. It wouldn't be productive if we forced people to also use another platform for those small things, however. ~n
Professor Code
Als Antwort auf Codeberg.org • • •Codeberg.org
Unbekannter Ursprungsbeitrag • • •@girlintech I'm not responsible for handling these situations, but, from what I've gathered, it'd involve a warning, a popup with a reminder (if you use lots of space), or a personal ask to fix this (sent using your email address). Accidents happen and people can forget things sometimes.
This isn't a rule applying to all situations, however. But please don't panic. 😀 ~n
EDIT: A further clarification from ~f: social.anoxinon.de/@Codeberg/1…
Codeberg.org
2024-10-16 18:29:25
Codeberg.org
Als Antwort auf Professor Code • • •@ProfessorCode @girlintech Again, it wouldn't be productive if we forced you to host everything BUT your very small config files on GitHub. We're fine with it if you don't want to show these anywhere apart from... eh, perhaps the confessional booth. 😀
"[Private repositories] are also allowed for really small & personal stuff like your journal, config files, ideas or notes, but explicitly not as a personal cloud or media storage." See codeberg.org/Codeberg/org/src/…. ~n
org/TermsOfUse.md at main
Codeberg.orgCodeberg.org
Unbekannter Ursprungsbeitrag • • •Codeberg.org
Unbekannter Ursprungsbeitrag • • •@girlintech
Releasing "compiled" artifacts without the code is typically not considered free software, same as how compiled binaries are typically not considered free software.
Encrypting your code before sharing would probably fall into the very same category. ~f
@ProfessorCode
Aleksandra Lesya
Als Antwort auf Codeberg.org • • •Aleksandra Lesya
Als Antwort auf Professor Code • • •@ProfessorCode you encrypt it and and push it into a copyleft license, the code is free but without the key they cannot use it.
Only my deranged mind can find this kind of solution xD
Codeberg.org
Unbekannter Ursprungsbeitrag • • •@girlintech Hi! We must admit that we occasionally just nuke things, but we do not really care about small repos and little traffic at all.
Our mentality is "If you didn't think a few seconds before pushing x to Codeberg, we won't spend a minute writing you an email, too".
Things like large encrypted personal file backups, media storage, hosting pirated content for the world etc etc.
Codeberg.org
Unbekannter Ursprungsbeitrag • • •@girlintech
It is not impossible, but difficult with our non-profit status. And not what we actually want.
There are some upcoming commercial Forgejo hostings, at least one or two are already available.
But those people that cause the most headache for us won't pay money for the service anyway. ~f
@ProfessorCode
Rob Cresswell
Als Antwort auf Codeberg.org • • •Codeberg.org
Als Antwort auf Rob Cresswell • • •Strypey
Als Antwort auf Codeberg.org • • •> For those wondering why Codeberg is slow right now
Is this why CodeBerg is completely offline right now? Or is that to do with the outcome of your train trip ...