Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75941 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 6429 invoked from network); 23 Jul 2014 09:25:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2014 09:25:11 -0000 Authentication-Results: pb1.pair.com header.from=hello@apfelbox.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=hello@apfelbox.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain apfelbox.net from 37.139.17.48 cause and error) X-PHP-List-Original-Sender: hello@apfelbox.net X-Host-Fingerprint: 37.139.17.48 mail.apfelbox.net Received: from [37.139.17.48] ([37.139.17.48:51034] helo=mail.apfelbox.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 86/D5-21666-57F7FC35 for ; Wed, 23 Jul 2014 05:25:10 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.apfelbox.net (Postfix) with ESMTP id 720CC120B68; Wed, 23 Jul 2014 09:25:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at mail.apfelbox.net Received: from mail.apfelbox.net ([127.0.0.1]) by localhost (mail.apfelbox.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6_C1sv6FthZw; Wed, 23 Jul 2014 09:25:02 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1971.5\)) In-Reply-To: <53CF7EC8.3020807@sugarcrm.com> Date: Wed, 23 Jul 2014 11:24:55 +0200 Cc: Christian Stoller , Rowan Collins , "internals@lists.php.net" Content-Transfer-Encoding: quoted-printable Message-ID: <3E99EDD0-CF5C-40BA-8971-1C2E52A96F3D@apfelbox.net> References: <53CEE5A4.6080701@sugarcrm.com> <53CF7229.3020501@gmail.com> <4ED7146272E04A47B986ED49E771E347BBE376850A@Ikarus.ameusgmbh.intern> <53CF7EC8.3020807@sugarcrm.com> To: Stas Malyshev Subject: Re: [PHP-DEV] PHP Language Specification From: hello@apfelbox.net (Jannik Zschiesche) Hi, > On 23.07.2014, at 11:22, Stas Malyshev wrote: >=20 > Hi! >=20 >> Another idea would be a Git repository with the specification as >> markdown files. This would allow creating Pull Requests via GitHub. >=20 > I think facilitating discussion and feedback is more important than > change tracking for now, but given github also has issues facility it > may actually work. I'm not sure if markdown is expressive enough = though > (e.g. it does not have sub/superscripts AFAIK). maybe some of the symfony folks can say something about that? They are = hosting their docs on github, using reStructuredText and it seems to = work reasonably well? Cheers Jannik=