Ted Leung wrote:
* A project has its own development team, or set of people who are
coding on the project (set of committers)
A project has its own community, which includes code contributors, and
designers, testers, documenters, localizers, and users. The community
around a project is more than the developers.
Totally agree that the community around an open source project is more
than the developers.
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.
specific projects as opposed to all of them. At that point our QA
staff out to be functioning in a role more like the Issue manager
described by Fogel
<http://producingoss.com/html-chunk/share-management.html#issue-manager>.
The whole bug council plays this role (at least for Chandler).
Cheers,
Katie
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
