Newsgroups: php.doc,php.internals Path: news.php.net Xref: news.php.net php.doc:969384464 php.internals:67813 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55229 invoked from network); 25 Jun 2013 16:30:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Jun 2013 16:30:34 -0000 Authentication-Results: pb1.pair.com header.from=klaussilveira@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=klaussilveira@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.42 as permitted sender) X-PHP-List-Original-Sender: klaussilveira@gmail.com X-Host-Fingerprint: 209.85.215.42 mail-la0-f42.google.com Received: from [209.85.215.42] ([209.85.215.42:60990] helo=mail-la0-f42.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 35/95-49518-8A5C9C15 for ; Tue, 25 Jun 2013 12:30:33 -0400 Received: by mail-la0-f42.google.com with SMTP id eb20so12294319lab.29 for ; Tue, 25 Jun 2013 09:30:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=vYcdRolrUPitsRZOJxVm00/kIYUKBRa7jxbxbQE5qjQ=; b=drcn6XLkxSHaanY1xBhbjeUMBONU+mG8B5ZioY/edjwa3lhbIHDvxfCJPZmi8fLzr7 BbtqjwWflj30ur4qJEkSYfFFtQCq93CM9nPylHXl2MOJFnKC1O4pT3XWGqdqtGOcS/AG B4BIIhlclrCRXZ4NjRB3Y4HfyzIg7867ya1GqPsZ6i1KZ6Ax9Rr6gBagRBqMnhduRKeY 1n7hY/HZeWjuRNgGOicsbppxdq9y0dqiBiOnW7WaoxhcUDU4TM4i1CmJro3m7aee1/E3 YN8tBf9K+SGpc0NSXid1Qu4gKMALfQNswrLPRshGIovzfyG5F2gI2yVU0EZhMVRrGt58 m2Yg== MIME-Version: 1.0 X-Received: by 10.112.201.138 with SMTP id ka10mr234052lbc.72.1372177829850; Tue, 25 Jun 2013 09:30:29 -0700 (PDT) Sender: klaussilveira@gmail.com Received: by 10.114.184.174 with HTTP; Tue, 25 Jun 2013 09:30:29 -0700 (PDT) In-Reply-To: References: <4ED7146272E04A47B986ED49E771E347BB4DF6F231@Ikarus.ameusgmbh.intern> <51C94A8A.1040800@2bepublished.at> Date: Tue, 25 Jun 2013 13:30:29 -0300 X-Google-Sender-Auth: I4kGRtwmLG_rvDer4RPhIE-cUzs Message-ID: To: David Soria Parra Cc: phpdoc@lists.php.net, internals@lists.php.net Content-Type: multipart/alternative; boundary=001a11c266be1df63504dffd0c2d Subject: Re: [PHP-DOC] Re: [PHP-DEV] Moving PHP documentation to Git repository From: klaussilveira@php.net (Klaus Silveira) --001a11c266be1df63504dffd0c2d Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jun 25, 2013 at 1:05 PM, David Soria Parra wrote: > 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. > I'm also in favor of moving to Git. The amount of contributions to the brazilian portuguese translation would be much more significant if we had a streamlined contribution system, which pull requests on Github allow quite easily. What are the current problems of Git migration? --001a11c266be1df63504dffd0c2d--