jeeswg wrote:If you want to overhaul the fundamentals of expressions and operators, in my view, you should outline the proposals in full, in one place. The before and after details. And at least some cost-benefit analysis details/considerations regarding updating old scripts.
Nobody has to do that, or pass anything by anyone, or seek permission of anyone, much less you. They only have to abide by the license, and the GPL well, good luck demanding cost-benefit analysis or trying to put red tape on it. If the one receiving the pull request doesn't like, doesn't want to merge anything, then it doesn't get merged. Opposite? then it gets merged.
- I don't know how many people even know that AutoHotkey is on GitHub. (I didn't know this for many years. I was hardly aware of GitHub for many years.)
How is that anyone's problem? If you want to get involved, even if it's just tracking changes and that's it, it doesn't take much effort if you actually spend a little bit of time reading where to and how to.
If you can't find the source, it's because you don't want to find it, or don't want to get involved.
- Everything is 'backdoor' on GitHub anyway, it's so hard to find anything.
Yes, that's why github, bitbucket, sourceforge, gitlab any other VCS is barren and not used at all, because it's "backdoor". You have to be really out of touch with reality to consider version control "backdoor". Everyone just uses notepad and acronis true image, apparently.
You clearly don't to want do anything at all.
- What other places should we be aware of? Is GitHub officially mentioned on the AHK forums, or in the documentation? Even when you know they exist on GitHub, these random discussions can be hard to find, cf. a proper thread on the AHK forums. (And how well are the GitHub discussions indexed on Google/Bing etc.)
Home page states where the source is located if you read past the hero image. There's a link in the downloads page, that drops right into it, pretty hard to miss unless you are blind and dont have text to speech/braile. Nobody has to publish or request permission if they want to upload the source to a github alternative and work there. You don't want to read, you don't want to find anything. You don't like when people reply harshly, but jesus christ man come on, get out of your comfort zone every once in a while and be a little more proactive and independent.
In documentation, v2 docs, straight through: https://lexikos.github.io/v2/docs/AutoHotkey.htm
. Press on the pencil on v1. By then, you would have been exposed to the documentation in the home page, and in the downloads page.
The source is far from hidden, if you are still that dense and can't find the source, READ THE LICENSE FILE. What's GPL? search what's GPL, source nowhere and you downloaded a binary file from the dev's site? ask the developer to abide by the license and give you the link or the files. P-r-o-a-c-t-i-v-i-t-y.
It is no one's problem that you didn't know that, it is nobody's problem you don't want to go to github to discuss anything, or see anything or track anything or see how things are done, learn from it to replicate. Anyone who makes changes has 0 reason, 0 responsibility, 0 mandate to come here and post anything about any of the changes or pull requests they want to make. Ultimately, lexikos merges into his repo what he wants to merge, does what he wants to do, does it when he wants to do it, like anyone else would on these kinds of projects. Autohotkey_l is lexiko's autohotkey. Helgef has his own repo, nnnik has his own repo, along with the countless other forks that may or may not be active. You can see their changes, what they are trying to do, what they have done. I think you still haven't realized that AutoHotkey literally has no totalitarian owner, only a branch sponsored/backed by this website. Look at autohotkey_h, he could just as simply prop up his own forum separate from here as long as he abides by the GPL, does hotkeyit feel like its worth his time doing so? probably not.
If I want to make a pull request for Helgef, I will make the pull request to him and discuss with him, I don't have to discuss this with anyone else, anyone is free to jump in if they want if is a public repo. If he feels like it should be discussed with the public, he can either talk with whomever he wants to talk to or ask me to do it, then I can either make it public, or shrug it off and go on my merry way. If lexikos likes changes, sees they fit his wish for autohotkey and his schedule, then he merges. Denied/closed requests are not showstoppers to the person making them, they will continue to work in the fork of whomever made the pull public.