Is it enough to put your software on Github to be its copyright holder?

Question

Law in IT

Let's say you wrote some of your super-drupal or 1c-bitrix in C ++ or Java, and you want to put it on github. At the same time, you want your software not to be modified so that someone cuts loot from it, it should always be free for everyone - no matter how it is modified. Also, your github account should remain the only distribution source for this software. If someone copies the project to himself and it will be better for you to promote it, he will pass off the product as his own, and no one will know the real author. Such situations are also to be avoided. Actually, the question is how to properly publish your open-source project, and do you need to conduct some paper legislative affairs for this, or is it enough to upload everything to github indicating the type of license?

Answer 1

Initially, only the author has rights and github has nothing to do with it. Yes, it can theoretically serve as an aid to proving rights, but in our country the "Register of computer programs" is much better suited for this.
Well, and all these are your conditions "... for everyone for free, and let no one leave offended" feel free to write in your license. In the meantime, look for her violators, save money for a lawyer :)

Answer 2

IANAL. TINLA.
> Is it enough to put your software on Github to be its copyright holder?
In order to be a copyright holder, it is enough to simply write a work. And not be bound by an agreement under which you explicitly or implicitly assign exclusive copyright to someone else. Examples of such contracts: labor in relation to works created in the performance of official duties; author's order in relation to the subject of the order.
> it should always be free for everyone
> post your open-source project
> open-source
What is the meaning of these ten non-Russian letters if you really intend to create a non-free / proprietary / proprietary program?