Programming

17446 readers

114 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

Open source Git repo owners with open licenses, how do you know your code is being used by a big corpo? (sh.itjust.works)

submitted 5 months ago* (last edited 4 months ago) by alphacyberranger@sh.itjust.works to c/programming@programming.dev

19 comments fedilink hide all child comments

How do people find out or know whether your repo which is having MIT or apache or AGPL license is being used by a corpo and profiting from it and not making the code open source or paying license fees?

you are viewing a single comment's thread
view the rest of the comments

[–] refalo@programming.dev 3 points 4 months ago (1 children)

keeping a list of changes in the source code

Source?

[–] Perhyte@lemmy.world 4 points 4 months ago

I may have slightly misremembered the license text (subsection 4c):

You must cause any modified files to carry prominent notices stating that You changed the files;

So I guess technically you only need to indicate that you have changed the files, not what you've changed in them. I suppose that's less burdensome because it only needs to be done once per file at most.