[PECL-DEV] PECL GitHub Repo Access?

--000000000000c26fe3062f24295a
Content-Type: text/plain; charset="UTF-8"

Hello PECL Team,

Recently I was granted lead maintainer status over the previously
unmaintained operator package. Its GitHub repo is at
https://github.com/php/pecl-php-operator I have a PR to update the repo
with the changes that I have just published to PECL. However, I do not have
permissions on GitHub. I can see this going one of three possible ways.

1. I keep my repo (https://github.com/jb-lopez/pecl-php-operator) and
update PECL so that it points to my repo instead of the former repo. This
is the simplest solution. I don't like this idea though, moving the repo
from the PHP namespace to my personal account. It feels wrong.
2. I'm added as a member to the PHP GitHub org _but_ only with access to
the pecl-php-operator repo, and only with maintainer access. This is the
easiest for me, but I can see why the PHP group would not want to do this.
3. Every time I publish a new release on PECL I have to ping someone on the
PHP GitHub team to approve my PR and merge it for me. This sounds like the
most troublesome idea for all involved.

Perhaps there is another solution that I have not thought of yet. I'm sure
that the PHP team has encountered this before with the migration to GitHub.
I doubt this is an unsolved issue.

Thank you,
Joshua Lopez

--000000000000c26fe3062f24295a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello PECL Team,</div><div><br></div><div>Recently I =
was granted lead maintainer status over the previously unmaintained operato=
r package. Its GitHub repo is at <a href=3D"https://github.com/php/pecl-php=
-operator">https://github.com/php/pecl-php-operator</a> I have a PR to upda=
te the repo with the changes that I have just published to PECL. However, I=
 do not have permissions on GitHub. I can see this going one of three possi=
ble ways.</div><div><br></div><div>1. I keep my repo (<a href=3D"https://gi=
thub.com/jb-lopez/pecl-php-operator">https://github.com/jb-lopez/pecl-php-o=
perator</a>) and update PECL so that it points to my repo instead of the fo=
rmer repo. This is the simplest solution. I don&#39;t like this idea though=
, moving the repo from the PHP namespace to my personal=C2=A0account. It fe=
els wrong.</div><div>2. I&#39;m added as a member to the PHP GitHub org _bu=
t_ only with access to the pecl-php-operator repo, and only with maintainer=
 access. This is the easiest for me, but I can see why the PHP group would =
not want to do this.<br></div><div>3. Every time I publish a new release on=
 PECL I have to ping someone on the PHP GitHub team to approve my PR and me=
rge it for me. This sounds like the most troublesome idea for all involved.=
</div><div><br></div><div>Perhaps there is another solution that I have not=
 thought of yet. I&#39;m sure that the PHP team has encountered this before=
 with the migration to GitHub. I doubt this is an unsolved issue.</div><div=
><br></div><div>Thank you,</div><div>Joshua Lopez<br></div></div>

--000000000000c26fe3062f24295a--