On Tue, Jan 29, 2013 at 2:31 PM, Ferenc Kovacs <tyr...@gmail.com> wrote:
> > > > On Tue, Jan 29, 2013 at 2:17 PM, Clint Priest <cpri...@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 being >> 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 so > the files are still readable plaintext but are having some basic formatting > 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 creating > a new karma line for those files or managing the contributions through Pull > Requests could also work. > But I think that it is only a legacy stuff that we have those files in the > repo: we didn't had internals documentation or a wiki, so we just put > everything to the repository. > > > -- > Ferenc Kovács > @Tyr43l - http://tyrael.hu > cc'ing the list. -- Ferenc Kovács @Tyr43l - http://tyrael.hu
