Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0952EE0A1 for ; Tue, 22 Jan 2013 22:03:15 +0000 (UTC) Received: (qmail 18687 invoked by uid 500); 22 Jan 2013 22:03:15 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 18669 invoked by uid 500); 22 Jan 2013 22:03:14 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 18660 invoked by uid 99); 22 Jan 2013 22:03:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jan 2013 22:03:14 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URIBL_BLACK X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of olemis@gmail.com designates 209.85.223.182 as permitted sender) Received: from [209.85.223.182] (HELO mail-ie0-f182.google.com) (209.85.223.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Jan 2013 22:03:09 +0000 Received: by mail-ie0-f182.google.com with SMTP id s9so12573059iec.27 for ; Tue, 22 Jan 2013 14:02:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=9wqAsO04XDovJfPMpez0WHP+HfgZzE+dJoO10wZOGnE=; b=BYZjOk0CbG+uniHHE6Qyi5bhSGjrU8EiwKw8RFS+/8w0au5vo1cedGX7o3jR8Dtg1+ tkok9MJXXouz6w9Y6z6lTNURJJJFCcNVGgy94EyATMm9Un8REvmHUaRkXJjAwq/6jfCw lACnxubTuevAswGKRiht96Hb9BMxp+BEIWvk1KUafysrOiiCEsiJpo0N6awtmeJzCvL3 oEBEpfdRMs41sWJRA/W4mCMyQZWyI/Nysx63N9ohm6Cbkq9yx14R6RwWGX94C2arzzF7 +8zlFd96SKQvkJpVIYsCc9MwdLtP+5LklLQfygahKsa/2zYj6x9AST8o+/+u3HiSRddg /r8w== MIME-Version: 1.0 X-Received: by 10.50.149.168 with SMTP id ub8mr12957246igb.111.1358892168183; Tue, 22 Jan 2013 14:02:48 -0800 (PST) Received: by 10.50.1.44 with HTTP; Tue, 22 Jan 2013 14:02:48 -0800 (PST) In-Reply-To: <98F0BC97-DB2F-47E3-9105-7ED674F739EC@wandisco.com> References: <98F0BC97-DB2F-47E3-9105-7ED674F739EC@wandisco.com> Date: Tue, 22 Jan 2013 17:02:48 -0500 Message-ID: Subject: Re: Announcing releases: where our users are From: Olemis Lang To: bloodhound-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 1/22/13, Joachim Dreimann wrote: > Our Release Process Wiki currently only states that we should announce it on > the Apache mailing lists: > > To: announce@apache.org, general@incubator.apache.org > Cc: bloodhound-dev@incubator.apache.org > I reckon we need to do more. We've had very little outside interest as far > as I can tell. > > Our potential users and contributors may not listen to these lists at all, > but they are active elsewhere on the 'net. > > I've had a few small successes getting people interested using Twitter > (@apbloodhound), just announcing releases and asking for feedback really. I > will continue to promote Bloodhound that way, and I'd be happy or someone > else to chip in (I'll share the password with a person committed to > helping). > > Release managers should have some responsibility in promoting releases in my > opinion. Blogs/Forums/Mailing lists.. > > What do others think? Do you have suggestions on where to promote Apache > Bloodhound? > The most obvious place that comes into my mind is trac-users ML ... but I don't whether that might considered *subversive* , spam-ish and / or inappropriate . Beyond that I write articles for TuxInfo magazine (Argentina) . It's published on a monthly frequency . Last article published in December . Other mags I am familiar with are : - The Python Papers (English language , Australia or New Zealand afaicr) - Programmez (French language, France) Another approach could be python and similar mailing lists . I could forward the announcements to python-es@... but I guess the third IPMC vote for release in general@... should come first ;) -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: