Prepare move into org

[Xenira]

As david is no longer active here the repo should be moved into an org.

That way we can give more granular permissions to maintainers and benefit from some org only github features.

Some points we need to do:

• Update README.md to point users to the new repository.
• Update guide to redirect users to the new guide url.
• Set up custom github pages url
• Check if we have absolute urls in our code and update them (maybe after move?).
• Feature freeze and finish last release from this repo.
• Configure org. ext-php-rs is taken. Registered extphprs for now. If someone has a better idea suggestions are welcome.

If david has time to properly move it, that would be preferred. If not we need to manually migrate issues/MRs and ask him to archive once we are done.

Edit: Might not be needed exactly. Reading up on what happens with proper transfer on github docs.

[kakserpom]

I have no doubts it would be a good move (pun intended).

[Xenira]

just registered ext-php.rs as domain. Can migrate docs there to have a constant url after the move.

[Xenira]

• Update README.md to point users to the new repository.
• Update guide to redirect users to the new guide url.

From github docs:

If the transferred repository contains a GitHub Pages site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect GitHub Pages associated with the repository.

So readme does not need to be updated and github pages impact can be lessened with the custom domain. Sent david a mail, so he can set that up.

[kakserpom]

https://php.rs/ is for sale for $1.2k

[Xenira]

Just did a test move into the org and it redirects cleanly.

https://github.com/Xenira/ext-php-rs-template

[Xenira]

https://php.rs/ is for sale for $1.2k

Might have bought it... Not for that price, but still not the wisest investment 😅

[MillerVictor]

I'm glad to see that this project has been revived. Is this a very interesting project? However, at present, the project is not ready to be put into production?

[Xenira]

I'm glad to see that this project has been revived. Is this a very interesting project?

Thanks :)

However, at present, the project is not ready to be put into production?

Depends. Some features are more stable than others. That being said we are not v1.0.0 yet and there will be breaking changes. While we try to keep them as minimal as possible (hope v0.14 was an exception) we will break things as needed. There will be migration guides though.

I have a small extension in production use and its working fine so far.

[kakserpom]

@MillerVictor I am actively working on a number of extensions and they all are going straight into a huge production.

[ptondereau]

About the production problem, I have a very old issue that still occurs: some memory leak when zend bailout.

Full story on Discord: https://discord.com/channels/115233111977099271/829877152048349266/995334037277249606