After some discussions with some other developers, I think it might be
a good idea to explore how the OACS community can improve its approach
to collaborative development.
Right now, I think the OACS community is head and shoulders above any
other free software project that I'm aware of. I'm on the mailing list
of quite a few projects simply to keep abreast of other systems, and I
have yet to come across one with a community that is as knowledgeable
and helpful as OACS. We've got some top of the line hackers here and
we've got a lot fewer arrogant curmudgeons than most communities have
(that's a compliment, btw :)).
That being said, some have pointed out that a lot of development goes
on in private. That means that a lot of the important decisions
regarding infrastructure and architecture are not done terribly
transparently. I am as guilty as anyone else in this regard and have
chosen this approach for many projects, for instance some email
dialogues I've had about the admin UI and others regarding ETP.
However, I think that I made a mistake in these times.
Since we're about to release beta, and many of these discussions
probably took place in private in order to expedite the porting
process, we should seriosly consider making a community wide effort to
make development conversations and decisions more transparent for the
next release or generation of OACS.
I don't think that I'm entirely the right person to propose ways to
facilitate this transparency, but I would like to pose this commitment
to the community. But I'll also make it a policy at Musea to try and
discuss general development approaches more public, especially with
regards to ETP.
Any thoughts or comments would be appreciated.