me-shaon/glwtpl

"Good Luck With That" Public License

Hi There, I'm Ahmed Shamim 👋

A Full-stack Developer from 🇧🇩

glwtpl's Issues

Why not have a Badge?

I think it will be cool, like this:

Although I don't know which color or word is better.

You call.

submission to SPDX and OSI

Hi, i was thinking if you can submit this license for approval to the public list:
SPDX List

The needed procedure is just to compile this:
SPDX Validation Tool

and eventually this:
OSI Submission

What do you think about? o.O

Any Chance of Bengali Translation?

I am wondering if there would be any Bengali Translation. 😀

Suggestion: add "Preamble" before the 3rd paragraph.

To make a sort of a good introduction and like real licenses, we can place the 3rd paragraph ("The author has absolutely no clue...") under Preamble section because right now it's just a paragraph that is not associated with copying, nor rules, so it should go under another section.

Perfect license for post-hackathon code

Add a list of contributors.

Currently, we have 27 contributors and I think it is important to somehow list them about what they did and how they contributed. For example, look at the bottom of README here. A list of Authors where we can see them in their glory!

This is just childish

GPL compatibility status

Could you please clarify in the README if this license is GPL compatible or not?

Grammar issue in Turkish Translation

Hello,

In the Yazarın bu projedeki kodun ne yaptığına dair en ufak bir fikri yoktur. Ya çalışır, ya çalışmaz, üçüncü bir seçenek yoktur. sentence, the word Üçüncü should start with a lower case letter.

Create LICENSE_ja-JP

Create japanese translation for GLWTPL

Turkish translation has some issues

Hello,

In both versions of Turkish translation, there are some grammatical and semantic issues; also the translations of NSFW and non-NSFW versions are not the same.

There is some issue with this LICENSE

God knows what

"Buddha-like" Public License

"Buddha-like" Public License

The profanity was funny

The license previously included several instances of the fuck word, which have since been removed. I can see people wanting to remove it, but I liked it; might I recommend two versions of the license, one with profanity and one without?

The GLWTSPL (Good Luck With That Shit Public License)?

remove or change [fullname] field

[fullname] field in line 2 contradicts rule 0 ..."NEVER LEAVE A
TRACE TO TRACK THE AUTHOR"

Fix typo in russian version

The Russian version says УДАЧИ С ЭТОЙ ОБЩЕСТВЕННОЙ ЛИЦЕНЗИЕЙ, which means Good luck with that public license, where it means good luck with the license itself.

Change it to УДАЧИ С ЭТИМ ОБЩЕСТВЕННАЯ ЛИЦЕНЗИЯ for it to be Good luck with that public license for it to say that it's the name of the license

Indentations

License files have mixed indentations consist of tabs and spaces.

The first two paragraphs of the license should be swapped

The following two paragraphs of the license should be swapped their places (as pointed by @thecsw in #39):

The author has absolutely no clue what the code in this project does.
It might just work or not, there is no third option.

Everyone is permitted to copy, distribute, modify, merge, sell, publish,
sublicense or whatever they want with this software but at their OWN RISK.

Issue: There is no god

So not even a god knows.

Blue Screen

When I clone this repository my laptop show one strange error.

May not be compatible with git

The anti-attribution aspect of this means that commits referencing the original author may need to be modified to redact the original author.

Changing commit data means creating a new commit ID entirely which may be somewhat of a hindrance in properly tracking changes.

The GLWT license is unusable by design

The GLWT license is released under the GLWT license, which means that anyone who wishes to use the license must abide by section 0 of the license, and make it untraceable to the original author. However, anybody could look up the license and trace it back, meaning that in using the license verbatim, you'd be violating the terms of the license.

The only "workaround" as of now is to sufficiently modify the license to the point where it's unrecognisable, however this effectively defeats the purpose of using this license as opposed to another or just writing one from scratch.

Could the license be released under another license, or a clause be implemented that excludes the license from being affected by itself? Alternatively, if the license isn't supposed to be released under itself, can the correct license be added to the repo?

This license seems impossible to comply with

I have reservations about this part of the license:

"NEVER LEAVE A TRACE TO TRACK THE AUTHOR of the original product"

Given current ML techniques, it is possible to track down authors just by their coding style. Under these conditions, any users of the source code are under serious obligation to employ obfuscation techniques and scrub anything that might be deemed identifiable information. I feel like this clause should be changed to something more like "You must neither include links to where you got the code from, nor include the author's name, e-mail or other personal information, in either binary or source distributions".