In reply to @telegram_293342249:tchncs.de
A script that magically repairs every problem in arch.

In reply to @gokuldas:matrix.org
Arch is a high maintenance system, requiring a lot of care from the user. It pays off significantly in other ways though - and those are the benefits users stay on for. Arch wiki has an entire wiki page dedicated to system maintenance that all arch users must know and follow regularly and religiously, to keep their system clean and operational.

In reply to @telegram_345769011:tchncs.de
I have a small open source queue management website that I build and put it on GitHub under GPL3. Someone reached out to me asking if they can use it.

Just keeping the GPL3 LICENSE as a file in the root folder and telling him to use it as they want, should do?

I am not a license expert

There are a few conditions for derivative works of GPL code. Most important are the following:

1. The license and copyright should be preserved. The license file can be in the root directory, sub directory or a link to the online copy. Copyright is very important, because it's the copyright owner who asserts the license. The lines written by the copyright owner will remain their IP, even when it is part of a derivative project.

2. The derivative work should be on similar terms. That is, distribution of derivative work should also be accompanied by source (if the user desires).

In reply to @telegram_345769011:tchncs.de
Do I have to go through some legal stuff to register the copyright?

In reply to @telegram_345769011:tchncs.de
I am lazy, don’t think this is important enough to do that. Is that fine?

In reply to @gokuldas:matrix.org
Do what?

In reply to @telegram_345769011:tchncs.de
Register a copyright

In reply to @telegram_345769011:tchncs.de
Curious to know, how do I prove that I am the author? Because code was pushed from my GitHub account?

In reply to @telegram_345769011:tchncs.de
Ok. Just asked for understanding. Thanks

In reply to @telegram_293342249:tchncs.de
What exactly is "signing". How does that work for sourcecode

'Signing' means an action that proves that you are the owner of certain data or document. Digital signing (or eSign) is done using cryptographic signing software, like Gnupg, minisign or X.509 PKI.

If you have a gpg keypair (which is your identity), you can sign a document using command gpg --sign document_name

The same can be done for git commits. When you sign your git commits, it's a proof that the commits and its contents came from you. This can be done with command git commit --gpg-sign.
I have set up my git to automatically sign every commit even without the --gpg-sign flag.

Madhav V⸙ꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋꠋ (Telegram): If you really want to know how digital signing works, here is a somewhat simplistic and slightly inaccurate explanation.

The first step in signing is to take the 'cryptographic hash' of the plain-text data. The hash is small piece of data that is derived from the plain-text data and is unique. No other plaintext data gives the same hash (in theory). Also the hash can't be reversed (the plain-text data cannot be extracted from the hash).

The next step is to encrypt the hash using your 'private key'. Your private key is your secret, but your 'public key' is with everyone. Whatever is encrypted with the private key can be decrypted using the public key. The encrypted hash is called the signature.

So, if a signature can be decrypted with your public key, it means that you made the signature (because only you have the private key). And if the decrypted hash matches the plain-text data, then it's proof that you had the plain-text data with you.