Hi!
I) Wiki
One option is to setup a wiki, the proposed choice was using dokuwiki,
which seems to support a flexibile auth system (so that we can use cvs
auth by default and fall back to a dokuwiki account for new guys that do
not yet have a cvs account), ACL's (so that we can control where n
Hello Lukas,
Monday, February 25, 2008, 5:04:45 PM, Pierre wrote:
> On Mon, Feb 25, 2008 at 3:59 PM, Derick Rethans <[EMAIL PROTECTED]> wrote:
>> On Sat, 23 Feb 2008, Lukas Kahwe Smith wrote:
>>
>> > Personally I prefer going with a wiki, because I do not have much
>> affection
>> > with CVS f
On 25.02.2008, at 17:20, Stefan Marr wrote:
Pierre Joye schrieb:
Limiting the RFC to existing php.net's member sound like a bad idea
and create CVS accounts only for a RFC does not sound any better.
I would rather use the wiki for the complete process. Once a RFC
reached a "stable" status, we
Pierre Joye schrieb:
Limiting the RFC to existing php.net's member sound like a bad idea
and create CVS accounts only for a RFC does not sound any better.
I would rather use the wiki for the complete process. Once a RFC
reached a "stable" status, we can add it to a RFC repository.
Would agree
On Mon, Feb 25, 2008 at 3:59 PM, Derick Rethans <[EMAIL PROTECTED]> wrote:
> On Sat, 23 Feb 2008, Lukas Kahwe Smith wrote:
>
> > Personally I prefer going with a wiki, because I do not have much affection
> > with CVS for these kinds of documents (actually I do think that the
> README's
> > sho
On Sat, 23 Feb 2008, Lukas Kahwe Smith wrote:
> Personally I prefer going with a wiki, because I do not have much affection
> with CVS for these kinds of documents (actually I do think that the README's
> should be in CVS, which is why I worked with Hannes on creating the current
> php.net/reST in
