Send G3D check-in messages to g3d-users?

[Morgan McGuire]

When we created the g3d-users and g3d-developers list, there were 10 active G3D developers. So, we needed a separate list to keep people using the library from being overwhelmed by the traffic on the developer list discussing API changes and posting commit messages.

Today, we have two G3D developers and G3D is relatively stable. There are usually about 10 commit messages per week. We also aren't making frequent releases, depending on most users to pull from SVN and build the library themselves. This means that the average G3D user might be very interested to know what is being committed to the library.

I propose that we keep the g3d-developers list active for design discussions that we want archived (or should the number of developers increase), but that we change our practice to sending commit messages directly to g3d-users.

Is there anyone on the g3d-user list who would prefer that Mike and I not send commit messages to g3d-users?

-m

Prof. Morgan McGuire

Department of Computer Science

Williams College