Newsgroups: php.doc,php.internals Path: news.php.net Xref: news.php.net php.doc:969384463 php.internals:67810 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 49098 invoked from network); 25 Jun 2013 16:05:31 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jun 2013 16:05:31 -0000 X-Host-Fingerprint: 217.114.211.68 unknown Date: Tue, 25 Jun 2013 12:05:30 -0400 Received: from [217.114.211.68] ([217.114.211.68:14243] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DE/34-49518-9CFB9C15 for ; Tue, 25 Jun 2013 12:05:30 -0400 To: phpdoc@lists.php.net,internals@lists.php.net References: <4ED7146272E04A47B986ED49E771E347BB4DF6F231@Ikarus.ameusgmbh.intern> <51C94A8A.1040800@2bepublished.at> User-Agent: slrn/0.9.9p1 (SunOS) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: X-Posted-By: 217.114.211.68 Subject: Re: [PHP-DEV] Moving PHP documentation to Git repository From: dsp@php.net (David Soria Parra) On 2013-06-25, Ferenc Kovacs wrote: > there were some initial discussion and work done on moving the docs to git, > see > https://wiki.php.net/doc/git > http://git.php.net/?p=3Dweb/doc-editor.git;a=3Dshortlog;h=3Drefs/heads/GIT_= > READY > http://marc.info/?l=3Dphpdoc&m=3D132321958514090&w=3D2 > > but it seems that we lost momentum, but I think that this isn't a technical > problem, just lack of interest (svn and the online editor just works for > the regulars), maybe others have different opinions on this. > and I'm fairly certain that the slow integration of the patches also not a > technical problem as well. > I think that it would worth more to figure out and fix the underlying > problem which causes the current delay for integrating the incoming patches= > . > moving to git/github without fixining the underlying issue would only mean > that we switched to pull requests not getting accepted in a timely > manner(which is unfortunately common with our other git/github repos). generally speaking i am in favor in moving more and more to git. we lost momentum and I am stuck with a new job and RMing. I can help with technical questions but don't hav emuch time implementing it.