incubator-bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olemis Lang <ole...@gmail.com>
Subject Re: [Apache Bloodhound] #156: Local copy of bloodhound part of Apache repo for browse functionality
Date Fri, 10 Aug 2012 20:05:24 GMT
On 8/10/12, Dave Brondsema <dave@brondsema.net> wrote:
> On 8/9/12 7:17 PM, Gary Martin wrote:
>> On 09/08/12 16:36, Greg Stein wrote:
>>> On Aug 9, 2012 11:33 AM, "Dave Brondsema" <dave@brondsema.net> wrote:
>>>> That sounds great.  AFAIK an NFS mount will be fine for Allura to read
>>> from.
>>>> By the way, I've subscribed to the bloodhound-dev list also.  It seems
>>>> that allura and bloodhound have a lot in common: python code/project
>>>> management tools both going through incubation :)
>>> Hehe... actually, I've considered raising the idea of plugging BH into
>>> Allura. Guess this is a good time to do just that :-)
>>>
>>> Cheers,
>>> -g
>>>
>>
>> Certainly a very interesting idea. Would this be considered consistent
>> with Allura's plans though?
>>
>
> A key part of Allura's architecture is the pluggability of "tools".  A
> standalone BloodHound tool for Allura could be developed without
> affecting the Allura platform at all.
>
> That said, a lot of the benefit of Allura is in using the core models
> which would give you unified searching, permissions, cross-linking
> between tools, etc.  So you couldn't reap those benefits without a lot
> of customization to BloodHound.
>
>

AFAICS something in our schedule related to this may be #142 [1]_ , isn't it ?

.. [1] #142 	Product-specific permissions
        (https://issues.apache.org/bloodhound/ticket/142)

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

Mime
View raw message