Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99164 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 83927 invoked from network); 25 May 2017 08:10:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 May 2017 08:10:19 -0000 Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 209.85.192.170 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 209.85.192.170 mail-pf0-f170.google.com Received: from [209.85.192.170] ([209.85.192.170:36771] helo=mail-pf0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id D2/53-10292-96196295 for ; Thu, 25 May 2017 04:10:18 -0400 Received: by mail-pf0-f170.google.com with SMTP id m17so160280169pfg.3 for ; Thu, 25 May 2017 01:10:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basereality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TBitxEu8h1B3cqzPCLTDIZ1cfoMxedMn+HQ0aLtwZlc=; b=WAGL/wCve1bzsXtV82Esy2vECJU3aVoPL2cU/3uaumO/tWgbHVi91VjiM1KrZJu+up 2h6XnlATgXw6Gw6jyIFTWj8dJtkb42RJdT2vQ4yw+sRVQ+fR4S9n6AWypqMe27+10agh 1suhj02NeNv4f106Fo5W0UFpt+40HtiM/eFXNcGzGU00nrpe2Hy70qWS0W0XC4k8fpbI 5AooLZ5wXp6TMwv4qVQ0Ey90AGyq4OonVHZbX8Q3RlJyUiSOzBDOe4OUg7PIJLIU+tWm rpwQlpRbNlMQBhu5m+JzVQ+fd19lxaGjEhrC0FXBHx7CAV1zZfj0PezqIEhtzcxWmi6Z P8Jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TBitxEu8h1B3cqzPCLTDIZ1cfoMxedMn+HQ0aLtwZlc=; b=ObCPHUXkoaALaDGM1XDOlZfSdUfV2fYAhr/ajSPF8Egve990Ff3oJXs8Q+3IuCrUkr 9SgNgc4PRaxjyQKRM7dfvCGRLschB8GgGS4hZM1U5X6AW1bQhaFHgqTU72CY74hdUMsy F/peyxr6e8L6HOxJsTVuDeDVgF3v57uB0AMl6J5dIjWOPT0OM9booixCBwX3UMPyaUw2 ggJWu4EZX5rqSFf2ciIlQ4dfy5d6/7jaZh2nqqMvgv23HRvzYO7w1SqJCDiKXHgLZIcr BLHBAO7xMYGW3BfC4cy5DcbRYZmGpFUk61IISYe88fNHSKPc89brqPeSDMQZ+Zb8uKv9 3YwA== X-Gm-Message-State: AODbwcDyr7hP7vpt/6Qqx1xTRSd6pFeKb9TBWk/JgwKWnCMGZsT1pBn5 Qr8aEgvFpEb+wRV/zL3Zb7ne+NlrQLYe X-Received: by 10.98.35.150 with SMTP id q22mr13982294pfj.220.1495699813969; Thu, 25 May 2017 01:10:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.151.163 with HTTP; Thu, 25 May 2017 01:10:13 -0700 (PDT) X-Originating-IP: [77.99.17.151] In-Reply-To: References: <44F2A014-7DA2-49EF-A706-342C5657B615@gmail.com> Date: Thu, 25 May 2017 09:10:13 +0100 Message-ID: To: Alan Pope Cc: Rowan Collins , "internals@lists.php.net" Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] Snapping php From: danack@basereality.com (Dan Ackroyd) On 10 May 2017 at 15:05, Alan Pope wrote: > so we can understand why some software developers aren't keen on > investing time to make a snap. You work for a commercial organisation - which is fine btw!. If a commercial entity invests time + money in doing some activity, they'd expect to see some commercial benefit. If a purely open source project invests time in producing more binary distributions, the only result they would see would be an increased workload due to whoever is producing binaries is the first line of support for issues with those binaries. The current system, where PHP and the extensions are packaged by Ubuntu, Debian, Centos etc people, who are then the first line of call for bugs on that platform, prevents a large number of platform specific bugs from reaching the PHP team. > make their software > available to a considerably wider audience via our snappy store Two things: i) I don't think the PHP project would actually get a considerably wider audience by starting to release snaps. PHP is kind of available in quite a few places already. ii) The PHP project is already constrained by a lack of development resources. Having someone manage these snaps and also triage the increased number of platform specific issues is unlikely to be something we could cope with. cheers Dan