Message from discussion
AAR Move to Core?
Received: by 10.115.74.1 with SMTP id b1mr406247wal.1175042499026;
Tue, 27 Mar 2007 17:41:39 -0700 (PDT)
Received: by r56g2000hsd.googlegroups.com with HTTP;
Wed, 28 Mar 2007 00:41:33 +0000 (UTC)
X-IP: 71.234.217.53
From: "Gregory Brown" <gregory.t.br...@gmail.com>
To: "Ruby Reports" <ruby-reports@googlegroups.com>
Subject: Re: AAR Move to Core?
Date: Wed, 28 Mar 2007 00:41:33 -0000
Message-ID: <1175042493.827851.316710@r56g2000hsd.googlegroups.com>
In-Reply-To: <854296f50703270624x254319dar2692afac63cfb13a@mail.gmail.com>
References: <854296f50703270624x254319dar2692afac63cfb13a@mail.gmail.com>
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.1) Gecko/20070126 BonEcho/2.0.0.1,gzip(gfe),gzip(gfe)
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
On Mar 27, 9:24 am, "Michael Milner" <mikem...@gmail.com> wrote:
> Unless anyone has serious objections, we're planning on moving
> acts_as_reportable into Ruport core. This will allow us to provide
> ActiveRecord integration from core Ruport and also eliminate the confusion
> we've noted with installing the plugin. This will only apply to the data
> collection parts of AAR, basically what currently resides in trunk. It
> doesn't apply to the experimental stuff I've been doing with views, that
> would need to be split into a different plugin with a different name.
>
> Please let us know of any thoughts/objections, otherwise this will be
> happening soon.
I mentioned this before, but might as well throw it out on the list.
1) We need to make sure if AAR lives in Ruport, it's not Rails
specific.
My biggest interest in it is for standalone / camping use, so I don't
think
Ruport should be lugging around a ton of Rails support. Of course,
a couple handlers to hook things up right are just fine.
2) It needs coverage before it can move into trunk, so while you're
welcome
to open up a branch for it whenever you want in the Ruport repos,
we'll
need close to full coverage for the essentials before it can move into
0.9
3) We need to keep it's scope limited to data acquisition. I don't
have
any issue at all with us firing up some plugins to add in extra
features,
but we can't let it bloat if it's in core.
I say, unless anyone is very pissed about this, go ahead and move it
in as soon as you're ready. :)
|
