Re: [RFC VOTE] Unbundle ext/interbase

  105277
April 15, 2019 09:50 Martin.Koeditz@it-syn.de (=?utf-8?B?S8O2ZGl0eiwgTWFydGlu?=)
Hello everybody,

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 following points:
1. How will I be deposited as a maintainer?
2. Who has commit rights for changes?
3. How are changes in the documentation checked in? Here are my changes have not been committed for years.
4. 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.

Regards,
Martin
  105278
April 15, 2019 10:08 nikita.ppv@gmail.com (Nikita Popov)
On Mon, Apr 15, 2019 at 11:51 AM Köditz, Martin Koeditz@it-syn..de>
wrote:

> Hello everybody, > > 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 following > points: > 1. How will I be deposited as a maintainer? > 2. Who has commit rights for changes?
> 3. How are changes in the documentation checked in? Here are my changes > have not been committed for years. > 4. 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. >
Hello Martin, 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. Regards, Nikita
  105287
April 15, 2019 13:19 pierre.php@gmail.com (Pierre Joye)
Hi Martin,

On Mon, Apr 15, 2019, 5:08 PM Nikita Popov ppv@gmail.com> wrote:

> On Mon, Apr 15, 2019 at 11:51 AM Köditz, Martin Koeditz@it-syn.de> > wrote: > > > Hello everybody, > > > > 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 > following > > points: > > 1. How will I be deposited as a maintainer? > > > 2. Who has commit rights for changes? > > 3. How are changes in the documentation checked in? Here are my changes > > have not been committed for years. > > 4. 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. > > > > Hello Martin, > > 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.
You can also use github and upload releases in pecl.php.net. best, Pierre
  105286
April 15, 2019 13:16 Danack@basereality.com (Dan Ackroyd)
Hi Martin,

On Mon, 15 Apr 2019 at 10:50, Köditz, Martin Koeditz@it-syn.de> wrote:
> I agreed to continue developing the Firebird driver as a maintainer.
As mentioned previously, possibly the first thing you should do is to make clear if you're maintaining it as something that is compatible with Firebird, or whether you are continuing the compatibility with InterBase. The two pieces of software have different capabilities[*]. You seem to be interested in maintaining it for Firebird, but the extension is currently called 'InterBase'. Having the supported DB change silently is quite a surprising thing to happen. Nikita Popov wrote:
> as well as the new PECL > repository for the extension once the move is completed.
Will that include mirroring to a github repository? Martin, either way I would recommend setting up a github repo to use in your workflow somewhere, as it is much easier for people to collaborate over (and can have things like TravisCI integration) more easily that PHP's git account can. And a Github repo is probably a better place to discuss plans for future support than PHP's bug tracker. cheers Dan Ack [*] https://ib-aid.com/en/articles/differences-between-firebird-and-interbase/