On Feb 3, 2006, at 5:30 PM, Katie Capps Parlante wrote:
I think what I'm arguing here is that there be a unified community
around the product design for the user-facing projects. One design
list. One user list. Not every user will use the web application
and the hosting service and the gui client, but many will use
several and we want a consistent experience that makes sense.
I think that implies that designers, users, and for the large part
testers and documenters will be interested in the suite of
projects, and it makes sense to foster one community around this.
Yes, this is different from how apache does it, but I think our
situation here is different.
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.
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.
----
Ted Leung Open Source Applications Foundation (OSAF)
PGP Fingerprint: 1003 7870 251F FA71 A59A CEE3 BEBA 2B87 F5FC 4B42
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
