Hash: SHA1
Hi, all,
This is a final update to the revision of the TCCC process for endorsing
meetings. Portions of the previous procedures have been revised as
follows, based on feedback from the Comsoc.
- indicate that we "endorse", rather than are
"technical cosponsor"
- indicate that we require *three* TPC reps, rather than 1
We have been glad to coordinate this with the Comsoc, and note that our
procedures are being considered to suggest some possible revisions to
the Comsoc procedures, notably:
- receive request two months before any due date
current Comsoc is 'in advance of the meeting' only
- allow Comsoc tech cosponsorship without requiring
proceedings in Xplore
current Comsoc process requires Xplore,
this conflicts with, e.g., ACM (and their Dlib)
- encourage the Comsoc to retain indication of which TCs
endorse a meeting, i.e.:
"IEEE Comsoc technical cosponsor, TCCC endorsed"
- reduce the decision turnaround from 6-8 weeks to 3-4 weeks
- reduce the number of reps from 3 (we need only 1)
- indicate that endorsement carries no weight until
Comsoc technical cosponsorship is granted
- additional mechanisms to address post-endorsement
changes to the meeting
These new procedures are now in effect, and will be posted to the TCCC
web pages shortly.
Joe (TCCC Chair)
- -------------------------------------
The TCCC endorses meetings in support of IEEE Comsoc technical
cosponsorship. Please see the Comsoc website for their procedures on
applying for Comsoc technical cosponsorship. TCCC reviews applications
for Comsoc technical cosponsorship as a regular part of that process,
but we will also provide early feedback for applicants in advance of
their submitting formally to the Comsoc.
Note that TCCC endorsement by itself is never provided; we provide early
intent to endorse meetings submit through the Comsoc process. TCCC
endorsement must not be indicated until Comsoc technical cosponsorship
has been granted.
Rules for TCCC endorsement:
- - like the Comsoc technical cosponsorship, TCCC endorsement is granted
to events on a per-instance basis; repeated events (e.g., of a series)
must reapply for each new instance
- - like the Comsoc, TCCC does not permit meetings to identify themselves
as "pending" TCCC endorsement, nor should they use TCCC or IEEE logos
until endorsement *and* in-cooperation with the Comsoc has been granted
- - like the Comsoc, TCCC expects requests for endorsement to be made in
sufficient advance of the meeting.
- - TCCC endorsement is intended for meetings whose primary
focus is computer communications (including meetings bridging computer
communications with disparate fields)
- - TCCC reiterates the purpose of endorsement, which, as noted on the
Comsoc sponsorship application, include:
"The endorsement helps to ensure that the technical program falls within
the committee's scope, that there is a quality, independent peer review
process for paper selection, and that three members of the ComSoc TC
will be active members of the event's technical program committee."
As a result, TCCC determines responses to requests for endorsement based
on the following criteria:
a) the meeting is in-scope for TCCC
b) that the meeting has a peer review process in which
every submission* receives at least three substantive
and independent reviews
*excepting only those declined due to process (format, late,
etc.) or scope (widely out of scope, or widely out of context
for a technical meeting)
b) the meeting has an appropriate TPC
c) the meeting is demonstrably non-profit
d) the meeting has an acceptance rate and acceptance rate
history (where applicable) appropriate to the meeting type
e) the request is made in advance of all aspects of the meeting
TCCC shall specifically require the application be received at
least *two months* prior to the deadline for the initial
due date for responses to the call for participation for
any part of the meeting (papers, posters, panel chairs,
track/symposium topics, tutorials, etc.)
f) TCCC shall be permitted to select or appoint three
TPC members to monitor and report back on the above points,
(or shall approve three existing TPC members who are TCCC
members, at the TCCC's discretion)
- - The requirements for submitting a request for TCCC endorsement
consists of sending a copy of the following information to
any TCCC officer:
- date and location information
- info on the two most recent meetings
number of submissions
accept rate (percent accepted)
amount of time on reviewed submissions vs other
i.e., invited papers, speakers, panels
number of reviews per paper
- names, affiliations, and locale of the following:
general chair
program chair
TPC members
- description of the focus of the meeting
(1 paragraph or a draft call for papers)
- description of the components of the meeting
i.e., fraction of the meeting time on each of:
reviewed submissions
invited submissions
panels
invited speakers
co-located workshops, demos, etc.
- description of the review process
number of reviewers, paper length, approx.
intended acceptance rate
- description of the budget overheads of the meeting
i.e., non-profit status, extent of support
to parent/sponsoring entity
- brief description of why TCCC endorsement is requested
If endorsement is granted to an event, we offer:
- - The meeting may indicate TCCC endorsement ("Endorsed by TCCC") on the
primary meeting web pages, the proceedings, and other promotional
material (e-mails, paper announcements, etc.), **after** the meeting
receives Comsoc in-cooperation status.
- - The meeting site / publications may include the TCCC logo, **after**
the meeting receives Comsoc in-cooperation status.
- - TCCC will cross-list info on the meeting on our web pages, and note
our endorsement at our meetings
During the period of TCCC endorsement of an event, we expect
the following:
- - The meeting shall notify the TCCC on any significant changes to info
provided in the application (at which point the application will
be re-reviewed)
- - The meeting shall allow for 3 TCCC members on the TPC, to be confirmed
after endorsement is determined. TPC members already in TCCC may, at the
discretion of TCCC, be selected for this purpose. The appointed members
will report back to the TCCC on the paper review process and file a
brief (1 paragraph) report to the email list.
Regarding any changes to a meeting once endorsed:
- - once a TC endorses a meeting, the representatives to that meeting
should be tracking and reporting back on substantive changes to process
or organization (large increase/change in the TPC, large number of
additional side-meetings, etc.)
- - it is understandable to add workshops, tutorials, or other side
meetings after endorsement/support is determined, but these should be
commensurate with being ancillary (side meetings shouldn't overtake the
core meeting goals), and related to the core meeting
If proceedings of the side meetings is intended to be available via
Xplore, that general decision needs to be made at the time of
endorsement/support.
If details of such meetings are known at the time of endorsement, then
the decision of endorsing the meeting will be contingent on endorsing
its side meetings.
If the details of such meetings are to be decided post
endorsement, then the TCCC reserves the right to decide on
endorsement of side meetings on a per-side-meeting basis, and the
endorsement of the core meeting is made agreeing to this right.
Any changes that result in Comsoc withdrawal of technical cosponsorship
will result in TCCC withdrawal of endorsement. Any changes that result
in TCCC withdrawal of endorsement will result in a report to the Comsoc
and recommendation that they withdraw technical cosponsorship.
- ---
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkqcC3IACgkQE5f5cImnZrvAGACg5XlAe+tOHI6csjPr9uNsHxV6
rwoAmgN2ttzLlKY2PBC6vjVPn/IPhaYb
=/WPb
-----END PGP SIGNATURE-----
_______________________________________________
Tccc mailing list
Tccc@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/tccc
Posts
No comments:
Post a Comment