Ethics of the Technical Papers Review Process
1. Protect Ideas
As a reviewer for SIGGRAPH, you have the responsibility to protect the confidentiality of the ideas represented in the papers you review. SIGGRAPH submissions are by their very nature not published documents. The work is considered new or proprietary by the authors; otherwise they would not have submitted it.
Of course, their intent is to ultimately publish to the world, but most of the submitted papers will not appear in the SIGGRAPH proceedings. Thus, it is likely that the paper you have in your hands will be refined further and submitted to some other journal or conference, or even to SIGGRAPH next year. Sometimes the work is still considered confidential by the author's employers. These organizations do not consider sending a paper to SIGGRAPH for review to constitute a public disclosure. Protection of the ideas in the papers you receive means:
- Do not show the paper to anyone else, including colleagues or students, unless you have asked them to write a review, or to help with your review. See the Review Process section of Frequently Asked Questions for more details on how to properly include a colleague or student in the review process.
- Do not show videotapes to non-reviewers.
- Do not use ideas from papers you review to develop new ones.
- In previous years, these guidelines said: "After the review process, destroy all copies of papers and videos that are not returned to the senior reviewer and erase any implementations you have written to evaluate the ideas in the papers, as well as any results of those implementations." However, this year SIGGRAPH is starting a new process for revised papers that were rejected from a previous SIGGRAPH conference, where the authors can choose to release the previous reviewers' names, so that the same reviewers can be reassigned. Therefore, there is a chance that you will be asked in the future to review such a resubmission, and you may need your notes, marked manuscripts, or implementations. So you may keep them if necessary, but please be careful to insulate the ideas you learned from the review from your own research, and from your colleagues and students. Also, please be aware that your reviews may be perused by other future SIGGRAPH reviewers.
2. Avoid Conflict of Interest
As a reviewer of a SIGGRAPH paper, you have a certain power over the reviewing process. It is important for you to avoid any conflict of interest. Even though you would, of course, act impartially on any paper, there should be absolutely no question about the impartiality of review. Thus, if you are assigned a paper where your review would create a possible conflict of interest, you should return the paper and not submit a review. Conflicts of interest include (but are not limited to) situations in which:
- You work at the same institution as one of the authors.
- You have been directly involved in the work and will be receiving credit in some way. If you're a member of the author's thesis committee, and the paper is about his or her thesis work, then you were involved.
- You suspect that others might see a conflict of interest in your involvement. For example, even though Microsoft Research in Seattle and Beijing are in some ways more distant than Berkeley and MIT, there is likely to be a perception that they are "both Microsoft," so folks from one should not review papers from the other.
- You have collaborated with one of the authors in the past three years (more or less). Collaboration is usually defined as having written a paper or grant proposal together, although you should use your judgment.
- You were the MS/PhD advisor of one of the authors or the MS/PhD advisee of one of the authors. Funding agencies typically consider advisees to represent a lifetime conflict of interest. SIGGRAPH has traditionally been more flexible than this, but you should think carefully before reviewing a paper you know to be written by a former advisee.
The blind reviewing process will help hide the authorship of many papers, and senior reviewers will try hard to avoid conflicts. But if you recognize the work or the author and feel it could present a conflict of interest, send the paper back to the senior reviewer as soon as possible so he or she can find someone else to review it.
3. Be Serious
The paper publishing business in SIGGRAPH is very serious indeed: careers and reputations hinge on publishing in the proceedings, academic tenure decisions are based on the proceedings, and patent infringement cases have discussed whether something was considered novel enough to publish in the proceedings.
This does not mean that we cannot have any fun in the paper sessions. But it does mean that we have a responsibility to be serious in the reviewing process. You should make an effort to do a good review. This is obvious. But one of the complaints we have heard about the SIGGRAPH review process is that some reviews can be so sketchy that it looks like the reviewer did not even seem to take the time to read the paper carefully. A casual or flippant review of a paper that the author has seriously submitted is not appropriate. In the long run, casual reviewing is a most damaging attack on the SIGGRAPH conference. There is no dishonor in being too busy to do a good review, or to realize that you have over-committed yourself and cannot review all the papers you agreed to review. But it is a big mistake to take on too much, and then not back out early enough to allow recovery. If you cannot do a decent job, give the paper back and say so. But please, do it early so that the senior reviewer has time to select another reviewer before the deadline.
4. Be Professional
Belittling or sarcastic comments may help display one's wit, but they are unnecessary in the reviewing process. The most valuable comments in a review are those that help the authors understand the shortcomings of their work and how they might improve it. If you intensely dislike a paper, give it a low score. That makes a sufficient statement.
5. In Summary
Adherence to ethics makes the whole reviewing process more complicated and sometimes less efficient. But convenience, efficiency, and expediency are not good reasons to contravene ethics. It is precisely at those times when it would be easier or more efficient to bend the rules that it is most important to do the right thing. Ultimately, spending that energy and time is an investment in the long-term health of the technical-paper sessions, the conference, and the community of computer graphics researchers.