-
-
Notifications
You must be signed in to change notification settings - Fork 28.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Link to maintained successor for PHP #2846
Conversation
I think this is a bit soon. You need to first prove that you're a good maintainer for the list. Also make sure the list passes the current guidelines and Awesome lint. |
My track record of decades in open source should speak for itself :) |
Fun fact: |
@@ -274,7 +274,7 @@ | |||
- [OCaml](https://github.com/ocaml-community/awesome-ocaml#readme) | |||
- [ColdFusion](https://github.com/seancoyne/awesome-coldfusion#readme) | |||
- [Fortran](https://github.com/rabbiabram/awesome-fortran#readme) | |||
- [PHP](https://github.com/ziadoz/awesome-php#readme) - Server-side scripting language. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
$ node --experimental-permission t.js
node:internal/modules/cjs/loader:162
const result = internalModuleStat(filename);
^
Error: Access to this API has been restricted
at stat (node:internal/modules/cjs/loader:162:18)
at Module._findPath (node:internal/modules/cjs/loader:640:16)
at resolveMainPath (node:internal/modules/run_main:15:25)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:53:24)
at node:internal/main/run_main_module:23:47 {
code: 'ERR_ACCESS_DENIED',
permission: 'FileSystemRead',
resource: '/Users/rafaelgss/repos/os/node/t.js'
}
I would usually agree with you. Any further needs to get the linting green will of course be taken as a group effort in the very near future. |
Is there a final decision on how this should be handled? |
Hi. I'm the author of the original Awesome PHP list. It seems like @dereuromark and @alexkart tried to reach out in an issue on my repo, but I only saw it today. Sorry about that. I've had a busy and stressful 2023. I would prefer bringing on new collaborators to my list over a hard fork. Will discuss further on the issue. Thanks. |
Closing then for now since the original maintainer is back and we can collaborate. |
Previous one is not maintained anymore.
So taking over as a group effort from now on.