hi Philip,
Thanks for the clarification :)
Cheers,
2010/8/6 Philip Olson :
>
> While hosting code within the PECL SVN repository has its advantages, I don't
> think one of them should be the 'ability to have documentation at php.net'
> and instead we, the documentation team, should adhere to w
Just a PEAR-nut perspective here, because we deal with this exact issue.
2010/8/6 Philip Olson :
> Also, I think it's far worse to scatter documentation all over the Internet
> which is something PEAR is suffering from today.
We also suffer from scattered source code —
http://pear.php.net/bugs/b
While hosting code within the PECL SVN repository has its advantages, I don't
think one of them should be the 'ability to have documentation at php.net' and
instead we, the documentation team, should adhere to what's listed at
pecl.php.net.
Users mostly care about 'pecl install foo' which is w
On Thu, 2010-08-05 at 14:56 -0700, Stas Malyshev wrote:
> Hi!
>
> > Also keep in mind that PECL extensions are often updated when the API
> > in PHP changes drastically, and various people help out making sure
> > they build on newer PHP versions. We cannot do that with extensions
> > hosted outsi
Hi!
Also keep in mind that PECL extensions are often updated when the API
in PHP changes drastically, and various people help out making sure
they build on newer PHP versions. We cannot do that with extensions
hosted outside of PHP SVN.
With github it's supposed to be quite easy - fork it, mak
On Thu, Aug 5, 2010 at 6:09 PM, Hannes Magnusson
wrote:
> On Thu, Aug 5, 2010 at 15:59, Pierre Joye wrote:
>> Now, if the php-doc team considers to stop hosting documentation for
>> PECL's extension not having their repository in svn.php.net, then it
>> is a rather drastic change and I have to th
On Thu, Aug 5, 2010 at 15:59, Pierre Joye wrote:
> Now, if the php-doc team considers to stop hosting documentation for
> PECL's extension not having their repository in svn.php.net, then it
> is a rather drastic change and I have to think a bit further about the
> consequences of such changes in
On Thu, Aug 5, 2010 at 5:51 PM, Derick Rethans wrote:
> Sure, you can still make docs CC-licensed for a very closed extension
> though.
>
>> > So restricting it to PECL extensions that are installable through
>> > our pecl channel makes sense. (Because we demand certain licenses
>> > for those).
On Thu, 2010-08-05 at 15:43 +0200, Hannes Magnusson wrote:
> That is totally true - and it is awesome that you have written the
> English docs - but did you know the docs have been translated to
> French? The Japanese version is even under development..
>
> And whenever we make template changes, o
On Thu, 5 Aug 2010, Pierre Joye wrote:
> On Thu, Aug 5, 2010 at 5:24 PM, Derick Rethans wrote:
>
> > Perhaps it's time to write up a few of those guidelines? I obviously
> > have little problem with having the mongo driver docs in phpdoc, but
> > we do need to realize that we can't just have a
On Thu, Aug 5, 2010 at 5:24 PM, Derick Rethans wrote:
> Perhaps it's time to write up a few of those guidelines? I obviously
> have little problem with having the mongo driver docs in phpdoc, but
> we do need to realize that we can't just have any random PHP extension's
> docs in phpdoc. For exam
On Thu, 5 Aug 2010, Pierre Joye wrote:
> On Thu, Aug 5, 2010 at 12:37 PM, Hannes Magnusson
> wrote:
>
> >> We knew that when we accepted this extension and I have no problem
> >> with continuing to publish the mongo documentation. Or to be more
> >> clear, I see no reason to change anything in o
hi,
On Thu, Aug 5, 2010 at 3:43 PM, Hannes Magnusson
wrote:
> It is waaay to much hassle to work with things outside of our domain.
> If all the things around the extension is external, then your users
> expect to find the manual at your site anyway..
As I said already numerous times in this di
On Thu, Aug 5, 2010 at 15:06, Kristina Chodorow wrote:
> I was asleep for the first 12 hours of this discussion, but I really like
> having the mongo extension's documentation in the manual and I hope it can
> stay.
>
> I don't want to see the docs site buckle under its own weight or have the
> do
I was asleep for the first 12 hours of this discussion, but I really like
having the mongo extension's documentation in the manual and I hope it can
stay.
I don't want to see the docs site buckle under its own weight or have the
docs maintainers so overwhelmed that the documentation quality suffer
On Thu, Aug 5, 2010 at 2:44 PM, Pierre Joye wrote:
> I don't see what's the code has to do with the code. As long as the
> doc is in php-doc, what or where is the problem?
with the ..doc.. :)
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
On Thu, Aug 5, 2010 at 12:37 PM, Hannes Magnusson
wrote:
>> We knew that when we accepted this extension and I have no problem
>> with continuing to publish the mongo documentation. Or to be more
>> clear, I see no reason to change anything in our policy right now.
>
> I have a big problem with i
On Thu, 5 Aug 2010, Hannes Magnusson wrote:
> This thread is about mongo (with general explanation of how things work).
> Mongo uses nothing of the PHP infrastructure, other then maybe PECL
> packaging. They have external repo, bug tracker and support channels -
> just like xdebug.
>
> We have no
On Thu, 5 Aug 2010, Pierre Joye wrote:
> However I have more issues with extensions like xdebug when they use
> nothing but the web site to release their code. They should just
> create their own channel and that's it.
And I would have done so if that possibility existed when Xdebug
started. X
On Thu, Aug 5, 2010 at 11:59, Pierre Joye wrote:
> On Thu, Aug 5, 2010 at 11:44 AM, Hannes Magnusson
> wrote:
>
>> This thread is about mongo (with general explanation of how things work).
>> Mongo uses nothing of the PHP infrastructure, other then maybe PECL
>> packaging. They have external repo
On Thu, Aug 5, 2010 at 11:44 AM, Hannes Magnusson
wrote:
> This thread is about mongo (with general explanation of how things work).
> Mongo uses nothing of the PHP infrastructure, other then maybe PECL
> packaging. They have external repo, bug tracker and support channels -
> just like xdebug.
On Thu, Aug 5, 2010 at 11:22, Pierre Joye wrote:
> We never forced (and we decided to) to use php.net's repository.
Ofcourse not. But if they choose to use our infrastructure they can
use our infrastructure for docs too.
If they choose to not do so, they effectively choose to not use our
docs in
On Thu, Aug 5, 2010 at 11:22, Pierre Joye wrote:
> On Thu, Aug 5, 2010 at 11:12 AM, Hannes Magnusson
> wrote:
>> On Thu, Aug 5, 2010 at 10:58, Pierre Joye wrote:
>>> hi,
>>>
>>> On Thu, Aug 5, 2010 at 10:50 AM, Hannes Magnusson
>>> wrote:
>>>
I suppose the definition of a 'PECL extension'
On Thu, Aug 5, 2010 at 11:12 AM, Hannes Magnusson
wrote:
> On Thu, Aug 5, 2010 at 10:58, Pierre Joye wrote:
>> hi,
>>
>> On Thu, Aug 5, 2010 at 10:50 AM, Hannes Magnusson
>> wrote:
>>
>>> I suppose the definition of a 'PECL extension' if if its packaged and
>>> released on pecl.php.net (like xde
On Thu, Aug 5, 2010 at 10:58, Pierre Joye wrote:
> hi,
>
> On Thu, Aug 5, 2010 at 10:50 AM, Hannes Magnusson
> wrote:
>
>> I suppose the definition of a 'PECL extension' if if its packaged and
>> released on pecl.php.net (like xdebug for example).
>> But we do have the problem though of not havin
hi,
On Thu, Aug 5, 2010 at 10:50 AM, Hannes Magnusson
wrote:
> I suppose the definition of a 'PECL extension' if if its packaged and
> released on pecl.php.net (like xdebug for example).
> But we do have the problem though of not having access to the code if
> its not in PHP SVN, and therefore w
On Thu, Aug 5, 2010 at 10:42, Pierre Joye wrote:
> hi,
>
> On Thu, Aug 5, 2010 at 10:18 AM, Hannes Magnusson
> wrote:
>> On Wed, Aug 4, 2010 at 22:59, Kristina Chodorow wrote:
>>> kristina Wed, 04 Aug 2010 20:59:18 +
>>>
>>> Revision: http://svn.php.net/viewvc
hi,
On Thu, Aug 5, 2010 at 10:18 AM, Hannes Magnusson
wrote:
> On Wed, Aug 4, 2010 at 22:59, Kristina Chodorow wrote:
>> kristina Wed, 04 Aug 2010 20:59:18 +
>>
>> Revision: http://svn.php.net/viewvc?view=revision&revision=301862
>>
>> Log:
>> mongo extension
On Aug 5, 2010, at 1:25 AM, Derick Rethans wrote:
> On Thu, 5 Aug 2010, Hannes Magnusson wrote:
>
>> On Wed, Aug 4, 2010 at 22:59, Kristina Chodorow wrote:
>>> kristina Wed, 04 Aug 2010 20:59:18 +
>>>
>>> Revision: http://svn.php.net/viewvc?view=revision&rev
On Thu, 5 Aug 2010, Hannes Magnusson wrote:
> On Wed, Aug 4, 2010 at 22:59, Kristina Chodorow wrote:
> > kristina Wed, 04 Aug 2010 20:59:18 +
> >
> > Revision: http://svn.php.net/viewvc?view=revision&revision=301862
> >
> > Log:
> > mongo extension is now maint
On Wed, Aug 4, 2010 at 22:59, Kristina Chodorow wrote:
> kristina Wed, 04 Aug 2010 20:59:18 +
>
> Revision: http://svn.php.net/viewvc?view=revision&revision=301862
>
> Log:
> mongo extension is now maintained on github
Hmh. There is one quite large consequence
31 matches
Mail list logo