Hi Adam 2016-08-15 23:34 GMT+02:00 Adam Baratz <adam.bar...@gmail.com>: > As one of those two people, it would help to have an official maintainer for > this extension. The path for "something's broken" or "something should be > different" to "committed fix" has been pretty murky.
First of all, great job on the recent pdo_dblib activity, its great to see someone is actively interested in keeping this alive. > I'm interested in putting my name forward for this. It would help to know > more about what's expected. In particular, when PRs poke at broader design > questions with the extension, what's the maintainer's role? One example: > https://github.com/php/php-src/pull/2017 As for expectations, I think its generally expected that the maintainer oversees bugs, and future development of the extension. An example could be that a security issue is present in the extension and having someone that understands the code able to review, fix and work on it is good, instead of (like Stas mentioned), having someone look into the code without fully understanding it, and potentially breaking something else (kinda like what happened to ext/exif). As a maintainer, you are pretty much the one that oversees the extension, making sure its in working condition (to continue being in the core), having tests passes, bug reports and PRs. Ofcourse other core developers may from time to time touch the extension to fix something, and in that case make sure to double check that there is no obvious regressions (we all do make mistakes!). >From seeing your past commitment to pdo_dblib, I'm a +1 keeping this extension with you as a maintainer, and I'm sure Anatol (cced) who seems to also be active in some of the PRs say yes to that too. -- regards, Kalle Sommer Nielsen ka...@php.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
