Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103579 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 43285 invoked from network); 7 Dec 2018 19:17:53 -0000 Received: from unknown (HELO mail-qt1-f178.google.com) (209.85.160.178) by pb1.pair.com with SMTP; 7 Dec 2018 19:17:53 -0000 Received: by mail-qt1-f178.google.com with SMTP id r14so4947056qtp.1 for ; Fri, 07 Dec 2018 07:44:02 -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:from:date :message-id:subject:to:cc; bh=jIrdi49d8A7KpZrFSQxAoHYGRXD0ekGS7MDISPm9i4g=; b=B2qT8eHpWxfDsAZhwumrzrGK8KKBenBSdApWHuH5cN9/ooGiSJSv2ufPs6qO/ffz3P oU49ZfF2ILZLYaGfCCfFzElVhscAAXUM2j7hFU2JHcuY/7kmMLskQawZyJHIsJGiF1Oj IRM8LgJ32jkx/K49KoCbCjVkWXnMvZZ3mqzcdXR1thcANNyvU9JiX/CkJY4mt9XbZgrr 1hmZomeix+KLQ8rcnzX36gH0YjR907eWJ2i35gPKw+zbtwt0C8NPWp/Bhb5TXXLZK+lb Su35EcAcxIiAjl6d/Kjp7SGEpeYPdh9HSYi/mCZBsOem0cAvRvsBhzgJgz+yJdwoxcWE FZtQ== X-Gm-Message-State: AA+aEWbThT02nQxyN5UVIJ6y7qBggU4/10Y/egyoU1OgiszNIjH4TIRN bf5f7fdzqKBZMWZLbc27tn1kUGcQpYyhXCPcL/dTew== X-Google-Smtp-Source: AFSGD/UVUZnMrK9SAlov+hUlZ1NjXJ3+MoKd4rj2Ldc3tLF7ktygd/oOPmQxT9wILwdVlB4IQEacomB6BQ2miPwmLaA= X-Received: by 2002:a0c:e9c4:: with SMTP id q4mr2542958qvo.18.1544197442326; Fri, 07 Dec 2018 07:44:02 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 7 Dec 2018 09:43:51 -0600 Message-ID: To: Kris Craig Cc: rican7@gmail.com, PHP internals Content-Type: multipart/alternative; boundary="000000000000036806057c707c5a" Subject: Re: [PHP-DEV] Official Twitter Account From: pollita@php.net (Sara Golemon) --000000000000036806057c707c5a Content-Type: text/plain; charset="UTF-8" On Fri, Dec 7, 2018 at 12:38 AM Kris Craig wrote: > Have we ever considered automating these social media posts? Not just > Twitter, but Reddit, as well. A bot could be setup to monitor for > announcements and repost them to social media without it having to be done > manually. > > It's not a terrible idea. We've got an API to list current releases.... somewhere (if not, making one is trivial given our data structures). Having a cron job live somewhere with an API key is a small step from there. The hard part is deciding on the text. For example, "this is a security (or bugfix) release" is salient. Personally, I quite enjoy giving flavorful announcements. Lastly, there's noise; I think that usually we'll want these to be batched, and each branch has a different RM (except when I'm doing 7.1 for joe). -Sara --000000000000036806057c707c5a--