Brent Vukmer <bvukmer at blackboard.com> wrote:
> The BFAV originally modelled the current harvesting process very closely.  Trying to extend it to also model the project-Swiki-page process makes the BFAV packages more complicated, increases the amount of QA I Should Be Doing, etc. Frankly I just don't know if it's needed.  I may just remove the functionality.  Is anybody else using the KCP Viewer?  Any votes for keeping it? 

The KCP team could, IMO, now use the regular process using the BFAV,
since the BFAV itself allows *[KCP]* filters, but that's up to them.
Either way, I vote for dropping it. The Swiki is used mostly by the KCP
team and myself (since I do the final approval most of their work). I
don't mind checking their stuff out using their own tools, and it is
definitely not as important as the BFAV itself. Since the BFAV is
currently doing an important job, and quite a few people are using it,
its simplicity is important. 

Daniel