adriennedecker
commented
11 years ago Same comment - copy/past happy. The only changes are in the section "More Detailed Suggestions"
And a mistake already. The line: Some examples of information that should be relayed through the submission process for panels:
Should read: Some examples of information that should be relayed through the review process for panels:
New content for: http://sigcse2014.sigcse.org/reviewers/guide_panels.php
Guidelines for Reviewers of Panels Your job as a reviewer of Panels is an important one. Through your reviews you have the opportunity to help the authors and to improve the quality of the symposium. Below are some general guidelines for writing good Panel reviews: • Your job is to write detailed reviews, even for excellent proposals. Tell the authors why you liked their proposal, so that they know what made it successful. • If you believe that the proposal is poorly written or poorly thought-out, provide constructive criticism to help the authors. • The best reviews clearly justify the reviewer's choice of rating. The least valuable review gives a low score with no written comments. This simply tells the authors that they have been unsuccessful, with no indication of how or why. It is of no help to the members of the Program Committee, who are charged with making program decisions based on your reviews. • Although SIGCSE requires all Panel proposals to be polished work, the authors will have a brief opportunity to improve their proposals before camera-ready copy is due. Your detailed feedback may help improve a panel and, as a result, the conference. • DISTINCTION BETWEEN PANELS AND SPECIAL SESSIONS: Panels present multiple perspectives on a specific topic. Special sessions are an opportunity to customize and experiment with the SIGCSE conference format (e.g. a seminar on a new topic, a committee report, or a forum on curriculum issues)
More Detailed Suggestions Some examples of information that should be relayed through the submission process for panels: • Summary of Submission: o Please summarize the submission in 2-4 sentences in your own words. Please DO NOT copy/paste the abstract into this section. • Strengths of this Submission (Some sample questions to guide your responses in this section): o Is the panel topic suitable for the symposium? o Do you expect that the level of interest in the panel would be high? o Are the particular presenters appropriate? Does their expertise match the panel topic? (Remember that Panel reviewing is not blind.) o Does the proposal appropriately place the topic in the larger context of Computer Science education? Are the authors aware of a range of ideas on the topic? If appropriate, do the authors cite related work? (In evaluating this, please keep in mind that proposals are limited to two pages, so it is unreasonable to expect a detailed "Related Work" section or a long bibliography.) o Is the structure of the panel presentation reasonable? Is the topic a good one for a panel? Is there some other format that would be more appropriate (e.g., a special session, workshop or paper)? o Will the speakers represent multiple views and offer distinct ideas? o Will the speakers be able to present their views in the time allotted (75 minutes total), while leaving time for questions or audience participation (30 minutes suggested)? o A typical panel consists of 4 participants including the moderator. If there are more than 4, have they convinced you that everyone will be able to speak and that time will still be available for audience participation? o
• Comments for Authors/Areas for Improvement o Is the proposal well-written? Is it clear and well-organized? Are there any technical errors? o Do you have any suggestions for the authors ... ... to improve the proposal itself (either for publication in the proceedings or for submission to a future symposium)? ... to improve the quality of the presentation, if accepted? Obviously this list is not exhaustive. The Program Committee and authors will appreciate your views on other issues as well.