Re: Proposal to release extension in PECL
| From: | Philip Olson | Date: | Tue, 13 Feb 2007 08:34:09 +0000 |
| Subject: | Re: Proposal to release extension in PECL | ||
| References: | 1 | Groups: | php.pecl.dev |
| Request: | Send a blank email to pecl-dev+get-4501@lists.php.net to get a copy of this message | ||
Hello,
With this proposal there must be a discussion about ref.imagick too. Some facts about ref.imagick:
1. It's still in Beta (since 2002-12-03)
2. Last release was 2004-06-28
3. It was added to the PHP Manual on 2007-01-31 (only skeletons)
I don't know this topic well except to mention that as is, this proposal would mean two extensions existing about the same subject. What's the protocol on this? One is clearly old and unmaintained while the proposed is new, more extensive, and obviously active. I don't believe BC is a major concern here, but maybe it is.
Secondly, before an extension with 400 (Wow!!!) functions is documented, some serious thinking will be required about how to organize the documentation for such a beast into the PHP Manual. Not a major hurdle but a worry nevertheless... a worry requiring a solution. The thought of viewing a sidebar with over 400 functions is, well, scary :)
Regards,
Philip
On Feb 12, 2007, at 12:07 PM, Mikko Koppanen wrote:
Hi! Im creating object oriented extension around ImageMagick C API (Magickwand). The extension is currently named simply magickwand but I assume I can't use that name because it conflicts the extension created by ImageMagick Studio LLC. The extension doesn't bundle ImageMagick. All code created by me will be released under PHP license and ImageMagick license can be seen here http://imagemagick.org/script/license.php. We have a small team ( four persons ) creating the documentation. There is a lot to document since the extension itself implements over 400 methods in four classes. The extension itself is almost done but I will release the first version when it complies with the PHP Coding Standards<http://cvs.php.net/co.php/php-src/CODING_STANDARDS>and when the documentation is finished. I would like to hear suggestions for name. (Currently I'm thinking to simply name it "Gick") --Mikko Koppanen