From bloodhound-dev-return-1514-apmail-incubator-bloodhound-dev-archive=incubator.apache.org@incubator.apache.org Thu Jan 3 23:25:38 2013 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 07586EE39 for ; Thu, 3 Jan 2013 23:25:38 +0000 (UTC) Received: (qmail 2188 invoked by uid 500); 3 Jan 2013 23:25:37 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 2172 invoked by uid 500); 3 Jan 2013 23:25:37 -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 2160 invoked by uid 99); 3 Jan 2013 23:25:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jan 2013 23:25:37 +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.172 as permitted sender) Received: from [209.85.223.172] (HELO mail-ie0-f172.google.com) (209.85.223.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jan 2013 23:25:31 +0000 Received: by mail-ie0-f172.google.com with SMTP id c13so18786517ieb.17 for ; Thu, 03 Jan 2013 15:25:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=iACAVtJfPlfO4oN4ZsN1sjKDh3gcgIJVHFNUbcREudE=; b=aG3oVEbk4CzN1idu8pApOqkL+mk5ehXc+khv8CHnXUe0PrUYLoHTyWexZaaW/hbYfJ RY1Xhw4/nwONjb5uOFXUJhqBJN8WF1tdgKngy9U48ipusL1ZI0i+4mz3Cdy35FWQ57uY jBQXd5d/qbTkh4MY8KpR/N0TjQ9heydM/0xg6YslOFPtsSDPILUcdIwANQWvxDAQzh3G k+sT/QwBCa2sROMhgDIeT+bvS3UAAhm/PSJZgoGJUjqki/7uupDGdkAc89Nli6FnXmRD Vmh96hdYXxCH269t/z0cGaLDzmz9JmlM9Kews9mjQu/xns6u7j4lW2T48a+ktjkgFAus Vl8Q== MIME-Version: 1.0 Received: by 10.50.106.135 with SMTP id gu7mr38794911igb.111.1357255511082; Thu, 03 Jan 2013 15:25:11 -0800 (PST) Received: by 10.50.1.44 with HTTP; Thu, 3 Jan 2013 15:25:10 -0800 (PST) In-Reply-To: References: Date: Thu, 3 Jan 2013 18:25:10 -0500 Message-ID: Subject: Re: AccountManagerPlugin 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/3/13, Ryan Ollos wrote: > Hello Bloodhound devs, > :) [...] > > For now, I just wanted to list some of the features that are on the table > for upcoming releases, and give the Bloodhound community the chance to > comment on what might be most important to tackle for upcoming releases. I > will consider focusing my efforts according to whatever feedback I receive. > The following is a list that I've loosely prioritized according to my > current thinking: In general I like the approach of merging related functionality , so here I go ... [...] > 3. #1001: Implement an extensive XmlRpc interface good to know . If there's anything I can do to help , please let me know . [...] > 9. Integrate the PermRedirectPlugin [...] IMO this should be higher in the list , as this will allow us to reduce the number of dependencies in installer scipt . > 10. Enhance the plugin's macros by integrating the UserStatsMacro and > WikiStatsMacro. > What's the relationship between AccountManagerPlugin and WikiStatsMacro o.O ? I mean at least by the name the later is not related neither with accounts nor with management , but wiki instead . That's what it looks unrelated to me . OTOH , these are plugins related to TracGVizPlugin , so it'd be very nice if solutions for both would be implemented in such a way that they could be easily reused as foundations for implementing corresponding GViz data sources . Hopefully you'll hear more about this subject soon . [...] > > I still think we can target > AnnouncerPlugin integration to Bloodhound for Q2 of this year. > TBH ... Q1 schedule would be *very* nice ... though I quite understand your position . -- Regards, Olemis. Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article: