Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65380
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAH-PCH5H-3Nsi=gU33Pz6=HpbDKrD90RKktW56JLhHbQv6a1TA@mail.gmail.com>
References: <CAH-PCH6o4tM_tWLh7CMMQM947Z_s=NEtJEnKWjVe6kROOi1R+A@mail.gmail.com>
	<5107CBF8.7030503@zerocue.com>
	<CAH-PCH5H-3Nsi=gU33Pz6=HpbDKrD90RKktW56JLhHbQv6a1TA@mail.gmail.com>
Date: Tue, 29 Jan 2013 14:32:09 +0100
Message-ID: <CAH-PCH4Q39Cc-+STgfVABmGdLb9qcmybUuhpPz6Q3F=NKC3UHA@mail.gmail.com>
To: Clint Priest <cpriest@zerocue.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=14dae9341071a4542e04d46d6b40
Subject: Re: [PHP-DEV] moving some READMEs to the wiki
From: tyra3l@gmail.com (Ferenc Kovacs)

--14dae9341071a4542e04d46d6b40
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Jan 29, 2013 at 2:31 PM, Ferenc Kovacs <tyra3l@gmail.com> wrote:

>
>
>
> On Tue, Jan 29, 2013 at 2:17 PM, Clint Priest <cpriest@zerocue.com> wrote=
:
>
>>
>> On 1/29/2013 5:21 AM, Ferenc Kovacs wrote:
>>
>> Hi,
>>
>> I think some of the README files currently present in the php-src repo
>> would be better kept in the wiki and some of them are already
>> duplicated/made redundant by our existing wiki pages.
>>
>>
>>  Definitely a good idea, possibly a better one might be to have a link
>> to the github repo version? Then it's always the latest while still bein=
g
>> able to keep the files in the repo...
>>
>>
>> --
>> -Clint
>>
>
> We have something like that already: http://php.net/reST/
> But I don't really like that because it introduces it's own meta markup s=
o
> the files are still readable plaintext but are having some basic formatti=
ng
> when viewed on the web.
> And not just that, but personally I think that it would be better if for
> documentation purposes we could be using the documentation infrastructure
> what we already have here and we also have a wiki where we could put the
> process/management related stuff.
> I fail to see why would somebody expect to find our release policy in the
> release tarball or how would it help that you have a GIT readme when you
> get the source already.
> Another thing that comes to mind is that we would have a better ACL if we
> could keep them in the docs/wiki as currently we can't hand out write
> access to those files without also handing out write access for the whole
> php-src repo Of Of course re-arranging the directory structure and creati=
ng
> a new karma line for those files or managing the contributions through Pu=
ll
> Requests could also work.
> But I think that it is only a legacy stuff that we have those files in th=
e
> repo: we didn't had internals documentation or a wiki, so we just put
> everything to the repository.
>
>
> --
> Ferenc Kov=C3=A1cs
> @Tyr43l - http://tyrael.hu
>

cc'ing the list.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--14dae9341071a4542e04d46d6b40--