Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103951 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 7270 invoked from network); 31 Jan 2019 22:53:17 -0000 Received: from unknown (HELO mail-vs1-f50.google.com) (209.85.217.50) by pb1.pair.com with SMTP; 31 Jan 2019 22:53:17 -0000 Received: by mail-vs1-f50.google.com with SMTP id n13so2695764vsk.4 for ; Thu, 31 Jan 2019 11:33:15 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=sWGKT8jikrUKB8AcGb6ArQa+4fPfNmdoEWtqm9x11g8=; b=K73iacegXq2/5Cj/9nsmafQi/FW8whSkgIYfNCsI7Tiy8Nq4uubcht/GOuOIyUTocg jqwyoGDKRIxiELqp+Po0Qvmrc6hpCTwtNlORsPVzIIjcYcvQx6dkl0xw8Mg5qbjMNXUd J8f5PWPxlg3ZQEYhnvcu7yore9Xx2UpOtOGGN6+triDGmdR3tlvCyUzj4z+YKzU5ctD5 n11ZqzRVkLwht63J++qhNkvZzBMgDDDa1F8rz4Wm5Vh1RwwIyUD/jG8pPgkd7SLDqpr9 rGgqI7jPbndW1gCM6kODu+CHJSgAz35J36a1sJC5BIrhlqw183gNMGzKx7l54vJxP5mq 4BUg== X-Gm-Message-State: AJcUukemA6cnfZDrWYY8slGThK74t+pWtpLCCg1Eh+UGvJEva1fFw5zJ OHepcH+OtT6qaqlr4I0AsYfWH/kXJ9J8gi/UaR0= X-Google-Smtp-Source: ALg8bN7M/PHDlK78lGWqCSm3e+434G7dSCF53NqGZV90iKJbOkkGlVqUK/1NH7Oq9aI63vLG7O0lPATLef8xF0prERU= X-Received: by 2002:a67:d684:: with SMTP id o4mr15986015vsj.174.1548963194581; Thu, 31 Jan 2019 11:33:14 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Reply-To: bishop@php.net Date: Thu, 31 Jan 2019 14:32:50 -0500 Message-ID: To: Stanislav Malyshev Cc: PHP internals Content-Type: multipart/alternative; boundary="000000000000fbb8420580c61826" Subject: Re: [PHP-DEV] PHAR maintainer? From: bishop@php.net (Bishop Bettini) --000000000000fbb8420580c61826 Content-Type: text/plain; charset="UTF-8" On Sun, Jan 20, 2019 at 9:01 PM Stanislav Malyshev wrote: > Hi! > > PHAR is pretty widely used component of PHP ecosystem, as I understand, > but all people listed as maintainers for the extension haven't been > active in the project for a decade. Is there somebody still willing to > take care of it? > I've been fixing phar bugs here and there over the last year, and I'm happy to take on a more diligent process to maintain ext/phar officially. Do we have, anywhere, a maintainers guide that talks about the maintainers' responsibilities? bishop --000000000000fbb8420580c61826--