Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.martin@wandisco.com
 designates 209.85.216.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50D30EC4.5000300@wandisco.com>
References: <50D30EC4.5000300@wandisco.com>
Date: Thu, 20 Dec 2012 14:40:59 +0000
Message-ID: 
 <CAEZ-ge58hj47JpMAkyX8Baaw0o30msxJbjFdeKHjfgW9H4tytQ@mail.gmail.com>
Subject: Re: i.a.o/bloodhound data as fixture for testing?
From: Gary Martin <gary.martin@wandisco.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=485b397dd3b5353a8804d149b8b4

--485b397dd3b5353a8804d149b8b4
Content-Type: text/plain; charset=UTF-8

With time to think about it, there are the email addresses in the cc fields
that should probably be swapped for fake ones. Anything else I missed?

Cheers,
    Gary

On 20 December 2012 13:12, Gary Martin <gary.martin@wandisco.com> wrote:

> Hi,
>
> The work I did yesterday for a basic way of loading and dumping data was
> with the view to helping developers work with more realistic data.
>
> So, before I do anything too rash, would it make sense for us to use the
> database from issues.apache.org/bloodhound as a fixture?
>
> Perhaps with the exception of some entries in the permission table, I
> don't think there is anything much that is unavailable through the site
> itself with anonymous permissions so I don't *think* that there would be
> any sensitive data to worry about. It seems worth a sanity check anyway to
> see if I have missed anything.
>
> If that works for everyone, I don't intend to provide attachments as part
> of the fixtures yet. If, for example, you eventually wanted to test how the
> new search components are doing with the searching within attachments
> (assuming that this is something we would want to be able to do), this
> would not yet provide for that. Also, there will clearly be actual errors
> associated with the missing files. Also, I am only likely to keep
> permissions for the anonymous, authenticated and the 'admin' user who will
> get TRAC_ADMIN permissions but that should be fairly easy for developers to
> sort out.
>
> So, any concerns?
>
> Cheers,
>     Gary
>

--485b397dd3b5353a8804d149b8b4--