Man, redesign a web site for a few days and everything goes
to hell!
Anyway, just wanted to add my two cents to this issue.
On Wednesday, Denison University in Ohio added it's name to
the list
of organizations running Bricolage. Over the summer, with
various
planning taking place over the past year, we migrated our
official
campus content into the new system. This was about 20,000
pages and
media combined. Training is ongoing with our maintainers.
We have a
number of kinks to still work out, but I feel like we will
ultimately
be successful. For those interested, here's what we were
able to do
with Bricolage. http://www.denison.edu
If someone wants to add us to the list of organizations
using the
product, please do.
However, David reducing his involvement *has* left a
leadership
vacuum and a raft of updates to be done. In addition to
the Apache
2 migration, there is a redevelopment of the permissions
model that
was outlined and then shelved, an improved workflow model,
and
additional work to address the many inconsistencies and
admining gaps
in the interface. Furthermore, the AJAX improvements can
not be
rolled out soon enough. These are only a few things that I
can think
of off the top of my head - there are many more ways the
project can
be improved major ways. If we tell ourselves that it has
"matured"
and has no need for more major improvements, then it is as
good as dead.
So there is much to do and much uncertainty. I think if a
more
organized developer agenda were set up, with a roadmap for
when we
want to accomplish things and an assessment of what is
possible, that
alone could reduce uncertainty and help set a direction
going
forward. So if there's any way I can help with that on the
wiki or
by working with the developers, I'd like to offer that.
This project can and will thrive. It has a solid
foundation. All it
needs is a little direction.
-Matt
|