2009-12-21

Re: [Tccc] Conference costs and ComSoc transparency

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Some further context...

Virgilio Rodriguez wrote:
...
> The above ENDS the participation of the academic side.
>
> Further evidence of this, see a direct quote from Prof. Roy previous
> message:
> "I was Vice-Chair of a Comsoc Conference, I did not see a full budget. I
> asked recently the TPC Chair(s) for upcoming ComSoc conference as to
> whether he had seen a full budget, and the answer was no."
>
> So, obviously, the academic side has very little or nothing to do with
> money. If there is a money/budget problem, one has to look elsewhere.

Sumit was vice-TPC chair. As Henning points out, TPCs have very little
involvement with the finances of a meeting.

There are many meetings where the general chair is also an academic -
e.g., Prof. Kurose was general co-chair of Infocom 2009. It is not
uncommon to have academics primarily involved with the TPC, and industry
primarily involved with the general planning. Many meetings benefit from
industrial support that industrial chairs are more likely to arrange.

> It is beyond me, why aren't the people who actually manage the money
> being the ones addressing money issues.

Program chairs make decisions for individual meetings, but those budgets
are always approved and reviewed by the Comsoc. Fred *is* one of the
people who helps do that - he has helped organize and advise numerous
conferences. I have done the same within the ACM and IEEE.

We have been addressing money issues since they have been raised. Fred
has been coordinating with others within the Comsoc to provide useful
information for the basis of continued discussion.

Joe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAksvmR0ACgkQE5f5cImnZrsk+QCeI4UPuGeCRcyHwHHhdAJxNvw4
k0gAoIHJgyRwYltihd36c1Lyt2rMXae/
=6mAz
-----END PGP SIGNATURE-----
_______________________________________________
Tccc mailing list
Tccc@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/tccc

No comments: