To update the documentation you can either use the editor at edit.php.net (useful for smaller changes and does not require permissions),
or also request direct commit access to the documentation.
I've added the changes via edit.php.net. But nothing happened since then. I think it will be a good practice to request direct access.
Von: Nikita Popov [mailto:[email protected]]
Gesendet: Montag, 15. April 2019 12:08
An: Köditz, Martin [email protected]
Cc: [email protected]
Betreff: Re: [PHP-DEV] Re: [RFC VOTE] Unbundle ext/interbase
On Mon, Apr 15, 2019 at 11:51 AM Köditz, Martin [email protected]
I want to give you the general state of the Firebird driver. At the
end of January, I agreed to continue developing the Firebird driver as
a maintainer. In this regard, I first took care of getting familiar
with the code and an important bug (# 72175).
Obviously, this information has not got through to the PHP community
for a variety of reasons. Unfortunately, the project seems to be
pulled away by the vote to remove the driver underfoot.
It would be nice if someone could agree with me on the further steps
regarding further development. I particularly need help with the
- How will I be deposited as a maintainer?
- Who has commit rights for changes?
- How are changes in the documentation checked in? Here are my
changes have not been committed for years.
- Where are the current development guidelines? I have an old book,
but it does not seem to reflect the current quality standards.
Maybe it's to late. But maybe we (the Firebird and the PHP community)
can continue on a common path.
The vote currently under way shouldn't change much for you: It mainly means that the code of the extension will be moved into a new repository and that the extension has to be installed using "pecl install interbase" instead of "./configure --with-interbase".
Unless you already have one, please request a PHP git account at https://www.php.net/git-php.php. Once it is approved you will be granted access to the ext/interbase extension in php-src, as well as the new PECL repository for the extension once the move is completed. You can then commit changes using git via git.php.net.
To update the documentation you can either use the editor at edit.php.net (useful for smaller changes and does not require permissions), or also request direct commit access to the documentation.