Newsgroups: php.internals,php.pecl.dev Path: news.php.net Xref: news.php.net php.internals:96263 php.pecl.dev:14019 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21039 invoked from network); 6 Oct 2016 08:44:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Oct 2016 08:44:51 -0000 Authentication-Results: pb1.pair.com header.from=leight@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=leight@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.52 as permitted sender) X-PHP-List-Original-Sender: leight@gmail.com X-Host-Fingerprint: 209.85.218.52 mail-oi0-f52.google.com Received: from [209.85.218.52] ([209.85.218.52:36190] helo=mail-oi0-f52.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 56/8B-23443-20F06F75 for ; Thu, 06 Oct 2016 04:44:50 -0400 Received: by mail-oi0-f52.google.com with SMTP id m72so13966844oik.3; Thu, 06 Oct 2016 01:44:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+fY9Ovif22CgeWW8O5ih5KvA3C4L375pIHGZjBccQC0=; b=QS9EmbNJ+xexccYRKjOWc2FX9MuNrZa6HPoqJaLY80UVHXHl6gOfX2bGX6B0LMyaUG bEabNGJqV0vetgVBtwPnXptf/MEmY8mWTvSJ4cHDY93bgMfbVWlQxEfYlWmIknBgvwf5 tRUH18P91ap8dxhcH8PoHveGlGjCdYbn0sAHl8SPVCMJKsCJJM4IZXAeUVHW46BmEQL2 HQDhF5LoPkt3bYpR09sHyhUp0oWgxoyl19jVfZFBqsWTsssCK6gIWcdL0LknFGH4XfVP LBo/uEDqgH3IyPkzw8Av/ynX0aMANA2S5LQbfzQQ2JYBqdE7oeRQI2hVKKPLvrxnhg7T 02nQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+fY9Ovif22CgeWW8O5ih5KvA3C4L375pIHGZjBccQC0=; b=X31Kg5XJfUhFFH7u59/9n/jnT2VEFQDn3ljfoN7dzbxS3dp2+n2R2cil3BXwHwmQ9m Vj6WQwmNidqYNnra40j33iAti1/AHJbKehIs8UwzmAQBKnGAhdkGYzJHl6y47hZWkUEk XtGRDfYr3Xqh8A6rz/KyEX3PztRc93WmMaH6NNp17DMrW1amgAWPG7yeeSO9cCWpxpCQ 3qvJCm5WDs2qmGSF96RYEOkv3olK+CHPRXWJ3vZKDueV3o9jC4bm8yO8b0TgBYFY/oj9 Lb08XG8hxC9CHe2ocGIA+blcG0f0FNJQrfZILYOIDnW3WDJM9pIOo2LSFq/b+L63fhaU Ni7A== X-Gm-Message-State: AA6/9RmRuaSBjVITxNP4Rhaeb+L3ddBQmMAoh83yFOID7SCMxniIoUwAufSiXfA52DigZ2DA4Cj9F8cGbGVNyA== X-Received: by 10.157.37.44 with SMTP id k41mr8544899otb.110.1475743487976; Thu, 06 Oct 2016 01:44:47 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.60.199 with HTTP; Thu, 6 Oct 2016 01:44:47 -0700 (PDT) In-Reply-To: References: Date: Thu, 6 Oct 2016 09:44:47 +0100 Message-ID: To: Derick Rethans Cc: pecl-dev@lists.php.net, internals@lists.php.net Content-Type: text/plain; charset=UTF-8 Subject: Re: [PECL-DEV] Intention to move mcrypt to PECL From: leight@gmail.com (Leigh) On 5 October 2016 at 20:11, Derick Rethans wrote: > It should be migrated properly, and also to GIT. I prefer that it is > released with my username as "lead", as I wrote a big deal of it. > > cheers, > Derick I'm not sure what you mean by "properly", what steps do you think I'll miss out? (My intention was always to ask for a php.net git repo for it) Of course you (and Sascha) should be listed as lead (I'll leave the "active" flags up to you - not sure if this is supposed to mean in general, or on the extension itself), I have little interest in maintaining this extension myself. My motivation is to remove it from master as soon as possible, so those testing or experimenting with future releases get an early indication of what is coming, rather than it happening at 7.2 beta and people only getting a couple of months. However the RFC said remove and move to PECL, so I am trying to follow what we agreed on, and get it moved to PECL prior to deleting it from master. Would you like to handle this migration yourself?