# VCS Account Request: ayesh - Thread: https://externals.io/message/125676 - Original archive: https://news-web.php.net/php.internals/125676 - Started by Ayesh Karunaratne on 2024-09-25T18:54:15+00:00 - Messages: 10 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #125676 — Ayesh Karunaratne — 2024-09-25T18:54:15+00:00 URL: https://externals.io/message/125676#125676 Hello Internals, My name is Ayesh Karunaratne, with GitHub username @Ayesh. In one of my recent PRs, Christoph (@cmb) made a friendly mention that it might be time for a php.net and commit karma to php-src (https://github.com/php/php-src/pull/13675#issuecomment-2373846727). I'm excitedly requesting one now :) I started to contribute to php-src mostly with typo fixes, changes in the UPGRADING file, GitHub Actions, followed by changes and new features in mbstring, Curl, and pcre extensions. I run a PHP-related website at https://php.watch, where most of my posts include the latest changes in the upcoming PHP version. This has me pulling up the latest php-src commits, running my own tests on them, and documenting those changes. In addition to code contributions, I'm one of the volunteers in the PHP Foundation on our PHP Core Roundup post series, and participate in the internals mailing list where I might be able to add some value. For PHP 8.5, I'm also one of the co-authors of the `get_declared_enums` RFC. I look forward to working on future RFCs, especially focusing on Mbstring/unicode, Curl and pcre extensions. I realize some of the changes I mentioned above don't require a php.net account, and wiki.php.net is separate from Git access. However, I hope it paints a slightly detailed picture that I have been working with php-src for a while and that I'm familiar with it. Even with a php.net account, I understand that following the PR and review process is important. However, I might be able to help with minor upkeep tasks such as quick fixes in CI, Readme, UPGRADING, etc files, as well as potential contributions and PR approvals/merges in doc-en and even php-src once I learn from core developers. Thank you for your time. --- ## #125677 — Christoph M. Becker — 2024-09-25T19:17:58+00:00 URL: https://externals.io/message/125676#125677 · In reply to: #125676 > My name is Ayesh Karunaratne, with GitHub username @Ayesh. > > In one of my recent PRs, Christoph (@cmb) made a friendly mention that > it might be time for a php.net and commit karma to php-src > (https://github.com/php/php-src/pull/13675#issuecomment-2373846727). > I'm excitedly requesting one now :) > > I started to contribute to php-src mostly with typo fixes, changes in > the UPGRADING file, GitHub Actions, followed by changes and new > features in mbstring, Curl, and pcre extensions. > > I run a PHP-related website at https://php.watch, where most of my > posts include the latest changes in the upcoming PHP version. This has > me pulling up the latest php-src commits, running my own tests on > them, and documenting those changes. > > In addition to code contributions, I'm one of the volunteers in the > PHP Foundation on our PHP Core Roundup post series, and participate in > the internals mailing list where I might be able to add some value. > > For PHP 8.5, I'm also one of the co-authors of the > `get_declared_enums` RFC. I look forward to working on future RFCs, > especially focusing on Mbstring/unicode, Curl and pcre extensions. > > I realize some of the changes I mentioned above don't require a > php.net account, and wiki.php.net is separate from Git access. > However, I hope it paints a slightly detailed picture that I have been > working with php-src for a while and that I'm familiar with it. > > Even with a php.net account, I understand that following the PR and > review process is important. However, I might be able to help with > minor upkeep tasks such as quick fixes in CI, Readme, UPGRADING, etc > files, as well as potential contributions and PR approvals/merges in > doc-en and even php-src once I learn from core developers. Hi Ayesh, I don't see a reason why we shouldn't grant you a php.net account. However, did you already fill-out and send the form on ? There is apparently no account request filed on people.php.net. Christoph --- ## #125678 — Jim Winstead — 2024-09-25T19:23:11+00:00 URL: https://externals.io/message/125676#125678 · In reply to: #125677 > > > > […] > > > Hi Ayesh, > > I don't see a reason why we shouldn't grant you a php.net account. > > However, did you already fill-out and send the form on > ? There is apparently no account > request filed on people.php.net. I already approved the account. The confirmation messages that get sent to internals were being bounced because the sender (group@php.net) was not subscribed to the list. That's been fixed, so future notifications of approved accounts should make it through. Jim --- ## #125679 — Ayesh Karunaratne — 2024-09-25T19:26:31+00:00 URL: https://externals.io/message/125676#125679 · In reply to: #125677 > Hi Ayesh, > > I don't see a reason why we shouldn't grant you a php.net account. > > However, did you already fill-out and send the form on > ? There is apparently no account > request filed on people.php.net. > > Christoph > > I see Jim also responded about the sender not being in the list. That was indeed the case; I filled the form with one email address, but I was subscribed to the internals using a different email address (so I can easily filter them). I see the account is already approved. Thank you so much! --- ## #125680 — Ayesh Karunaratne — 2024-09-25T19:28:04+00:00 URL: https://externals.io/message/125676#125680 · In reply to: #125678 > I already approved the account. The confirmation messages that get sent to internals were being bounced because the sender (group@php.net) was not subscribed to the list. That's been fixed, so future notifications of approved accounts should make it through. > Thank you so much Jim, I received the account creation confirmation email. You are also right that the internals email bounced because the email address I used in the form is different to the email address I was subscribed to in the internals list. --- ## #125681 — Christoph M. Becker — 2024-09-25T20:02:36+00:00 URL: https://externals.io/message/125676#125681 · In reply to: #125678 > > > > […] > > I already approved the account. The confirmation messages that get sent to internals were being bounced because the sender (group@php.net) was not subscribed to the list. That's been fixed, so future notifications of approved accounts should make it through. Thank you for the approval, the explanation and the fix! Christoph --- ## #125682 — tim@bastelstu.be — 2024-09-26T11:45:14+00:00 URL: https://externals.io/message/125676#125682 · In reply to: #125679 Hi Am 2024-09-25 21:26, schrieb Ayesh Karunaratne: > I see the account is already approved. Unless you did not yet accept the invitation to the GitHub organization, it appears that you were not invited there yet. If that is the case, someone should send the invite. Best regards Tim Düsterhus --- ## #125683 — Ilija Tovilo — 2024-09-26T11:52:40+00:00 URL: https://externals.io/message/125676#125683 · In reply to: #125682 > > Am 2024-09-25 21:26, schrieb Ayesh Karunaratne: > > […] > > Unless you did not yet accept the invitation to the GitHub organization, > it appears that you were not invited there yet. If that is the case, > someone should send the invite. Thanks for the hint, I sent Ayesh an invite to the php-src team. Ilija --- ## #125684 — Ayesh Karunaratne — 2024-09-26T12:00:55+00:00 URL: https://externals.io/message/125676#125684 · In reply to: #125683 > Thanks for the hint, I sent Ayesh an invite to the php-src team. > > Ilija I just received it and accepted the GitHub invite. Thank you so much for having me 💟 Ayesh. --- ## #125685 — Christoph M. Becker — 2024-09-26T12:07:32+00:00 URL: https://externals.io/message/125676#125685 · In reply to: #125682 > Am 2024-09-25 21:26, schrieb Ayesh Karunaratne: > > […] > > Unless you did not yet accept the invitation to the GitHub organization, > it appears that you were not invited there yet. If that is the case, > someone should send the invite. Apparently, an invite had already been sent. Christoph