Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:43165 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70877 invoked from network); 24 Feb 2009 06:40:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Feb 2009 06:40:32 -0000 Authentication-Results: pb1.pair.com smtp.mail=kaigai@ak.jp.nec.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=kaigai@ak.jp.nec.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ak.jp.nec.com designates 202.32.8.206 as permitted sender) X-PHP-List-Original-Sender: kaigai@ak.jp.nec.com X-Host-Fingerprint: 202.32.8.206 TYO202.gate.nec.co.jp Solaris 8 (1) Received: from [202.32.8.206] ([202.32.8.206:49742] helo=tyo202.gate.nec.co.jp) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/D5-29217-55693A94 for ; Tue, 24 Feb 2009 01:40:31 -0500 Received: from mailgate3.nec.co.jp ([10.7.69.193]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id n1O6dm4F020990; Tue, 24 Feb 2009 15:39:48 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id n1O6dlI23844; Tue, 24 Feb 2009 15:39:47 +0900 (JST) Received: from mailsv.linux.bs1.fc.nec.co.jp (mailsv.linux.bs1.fc.nec.co.jp [10.34.125.2]) by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id n1O6dl9D027039; Tue, 24 Feb 2009 15:39:47 +0900 (JST) Received: from [10.19.71.82] (unknown [10.19.71.82]) by mailsv.linux.bs1.fc.nec.co.jp (Postfix) with ESMTP id 47D6CE4824D; Tue, 24 Feb 2009 15:39:47 +0900 (JST) Message-ID: <49A39633.1050202@ak.jp.nec.com> Date: Tue, 24 Feb 2009 15:39:47 +0900 User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Marcus Boerger CC: internals@lists.php.net References: <49A38166.7080003@ak.jp.nec.com> <5410446686.20090224064417@marcus-boerger.de> In-Reply-To: <5410446686.20090224064417@marcus-boerger.de> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] How to contribute a new extension? From: kaigai@ak.jp.nec.com (KaiGai Kohei) Marcus Boerger wrote: > Hello KaiGai, > > Tuesday, February 24, 2009, 6:11:02 AM, you wrote: > >> Hi, > >> I'm one of the developers in the SELinux. >> I have an extension of PHP to provide interfaces to communicate >> with SELinux, and would like to propose them to the official PHP. > >> Now I'm looking for informations about steps to propose a new >> extension. Could someone point to me? >> I could not find introductions to submit patches. :( > >> The following pages show specifications and implementations that >> I would like to propose: >> http://code.google.com/p/sepgsql/wiki/Memo_PHP_SELinux >> http://code.google.com/p/sepgsql/source/browse/misc/php-selinux/ > >> But I'm not clear for what should I do in the next. >> - What is the correct list to submit a patch? >> - What base version of PHP should I make a patch toward? >> - What facilities are necessary except for the code? >> (I guess documentation and testcases are required.) >> - Who can admit the patch inclusion? > >> Sorry, I'm not good at development cycle in this community... > > Nice. Now to get your work into PHP you need to propose it to > PELC (PHP Extension Community Library). To do so follow here: > http://pecl.php.net/account-request.php Marcus, Thanks for your information. I'll get a start from announcement of SELinux extensions on the pecl-dev list. I guess the module name of "selinux" will be acceptable for people. > Normally those extensions are developed with the their source > in th epecl repository, thus you need a CVS account. Also note > that we have restrictions on the possible licenses. I've not determined the license of the extension, so we can choose the most preferable one (PHP license 3.0). Thanks, -- OSS Platform Development Division, NEC KaiGai Kohei