Ted Leung wrote:
I wasn't coming (consciously at least) from "this is the way apache
does it", since the project-{user,dev} convention is used in a lot of
places. And I know that we would like to have unified community.
You might not have been but I was -- at least my imperfect understanding
of it. :) If I understand correctly, apache projects operate very
independently -- the glue that holds them together has to do with common
rules about how the projects operate as communities, not technology
decisions or feature decisions or common users.
I'm just pointing out the need for a shared space across osaf projects
for issues beyond governance and community (this list) which we indeed
already have (the design list).
But I don't know if our users will want that. I do know that people don't
like to get more e-mail than necessary. I can easily imagine that
there are people who only use one of Chandler or Scooby who will be
annoyed to get (lots) of e-mail about the project/product that they
don't use. We can certainly start with a single user list, but if we
are moderately successful, there's going to be a huge amount of traffic.
As Mimi pointed out elsewhere, the one-or-more-user-list issue isn't a
short term problem (as we have no user lists at the moment), so perhaps
it falls into the "we'll cross that bridge when we get there" category.
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
