# How to contribute a new extension? - Thread: https://externals.io/message/43163 - Original archive: https://news-web.php.net/php.internals/43163 - Started by KaiGai Kohei on 2009-02-24T05:11:02+00:00 - Messages: 3 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #43163 — KaiGai Kohei — 2009-02-24T05:11:02+00:00 URL: https://externals.io/message/43163#43163 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... Thanks, -- OSS Platform Development Division, NEC KaiGai Kohei 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 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. marcus > Thanks, > -- > OSS Platform Development Division, NEC > KaiGai Kohei Best regards, Marcus --- ## #43165 — KaiGai Kohei — 2009-02-24T06:39:47+00:00 URL: https://externals.io/message/43163#43165 · In reply to: #43164 Marcus Boerger wrote: > Hello KaiGai, > > Tuesday, February 24, 2009, 6:11:02 AM, you wrote: > > > […] > > > […] > > > […] > > > […] > > > […] > > > […] > > 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