|
SNUG Bylaws
SNUG Authors
1. Authors must qualify to attend SNUG in order to write a paper for SNUG.
2. Authors are required to submit both a paper and a presentation.
3. Authors (at least one from each authoring team) are required to present their accepted papers at SNUG. Attendance (and travel expenses, if applicable) to the conference should be approved by the author's management prior to submitting an abstract.
4. The author(s) presenting at the conference must possess strong command of the language in which the conference is being conducted, and must be able to present clearly in that language.
5. Authors are expected to review and adhere to guidelines as outlined in the SNUG Author's Kit
SNUG Abstracts
1. Acceptance decisions are based on abstract submissions. The technical committee reserves the right to retract the acceptance if, upon review of the paper, the paper focuses on topics not clearly identified in the original abstract.
2. Abstracts submitted after the Call for Papers deadline has passed may only be considered and accepted for incomplete sessions.
3. New, original abstracts will receive preference when being considered for acceptance. Previously published work will be considered on a case-by-case basis.
4. The same abstract may be submitted to more than one SNUG conference, and will be considered independently for each conference.
5. Papers which *focus* on custom scripts/tools should indicate whether those scripts/tools will be made available. This availability will factor into the paper acceptance decision. Papers which focus on a process that *reference* custom scripts/tools are not required to make those tools/scripts available in the paper, but it is still preferred that the tools/scripts be made available.
SNUG Papers
1. Each paper will be assigned to a SNUG technical committee member for review.
2. Each paper will be assigned to a Synopsys engineer for internal review.
3. Papers should be based on either Synopsys Tools or on general design methodology.
4. The technical committee reserves the right to reject any paper which focuses on third party proprietary tools.
5. Any paper reviewed by the assigned reviewer(s) and found to contain incorrect information shall go under further technical review.
5a. If the content of a paper is found to be incorrect by all reviewers AND the author refuses to change the paper, the technical chairperson reserves the right to remove the paper from the conference program.
6. If a paper focuses on unreleased Synopsys tools which will be unavailable to the general public at the time of the conference, the author(s) may have to wait to present their paper at a future conference, after the tool has been released to the general public by Synopsys.
7. The technical chairperson reserves the right to remove from the conference program any paper that appears to be marketing focused.
SNUG Presentations
1. After the final presentation submission is made, the presentation may not be altered.
SNUG Awards
There are five awards and two honorable mentions presented at SNUG (awards vary from conference to conference):
- First Place, Best Paper
- Second Place, Best Paper
- Third Place, Best Paper
- Best New Presenter
- Technical Committee Award
- Technical Committee Honorable Mention (2)
1. Only new paper submissions will be considered for any awards at SNUG. In the case of papers re-submitted with significant changes, the Technical Chair of that SNUG will determine whether the paper is considered new or not.
2. In order to be considered for any award, the SNUG paper must be authored by at least one end-user. Papers authored by Synopsys employees only are ineligible for any of the above mentioned awards.
Additionally, papers presented solely by Synopsys employees at SNUG, regardless of other end-user authors listed, are ineligible for the 'Best Paper' awards and 'Presenter' award.
3. If a paper qualifies for more than one award, the most lucrative award will take precedence and that paper will be removed from the running for any other award. If there is a tie based on the amount of remuneration, the Best User Paper Award takes precedence, followed by the Technical Committee Award.
4. Final papers submitted after the published deadline may not be eligible for the Technical Committee Award.
We will make every effort at the conference to recognize and praise award winning papers that are being re-presented and high scoring papers presented by Synopsys employees at SNUG.
Technical Committee Award Voting Process
1. The Technical Committee chairs will create guidelines on how to read for the TC award and publish them to the technical committee members. These are guidelines, not requirements, that may help you as you read the papers. They will be in-line with the author's guidelines on how to write a good paper.
2. The TC chair, along with the SNUG program manager, will assign the first and second round paper assignments to the TC members. As much as possible this will be based on the TC members’ areas of expertise.
Round One Voting
Each TC member will read the papers in their session, and possibly an additional paper, such that each paper gets at least 3 votes. The papers will be scored on a scale of 0-5 and the top 6 will advance to round two. In addition, if a TC member feels strongly that a specific paper should advance regardless of its score, they can nominate it directly. The TC chair will have the final decision on whether to advance the paper or not. At least 6 and no more than 10 papers will advance to round two.
Round Two Voting
The TC chair will assign papers to each TC member. Each paper needs to be read by 50% of the members of the TC, and each TC member needs to read at least 50% of the round two papers. They will be scored on a scale of 0-5. Exclusions (ie: TC members' papers being in the final round) will be dealt with by the TC chair and may change some of these numbers.
SNUG Technical Committee Membership
1. Technical committee members must qualify to attend SNUG in order to participate on the technical committee.
2. Technical committee members must have at least 2 years design experience with Synopsys tools.
3. Technical committee members must have previous experience in writing or reviewing technical papers.
4. Synopsys employees may act as members on the technical committee, as needed.
5. Final approval to add a member will come from the technical chairperson and the program manager.
Role of the SNUG Technical Committee Member
1. Technical committee members should expect to commit ~30 hours over five months.
2. Technical committee members review and accept/reject abstracts.
3. Technical committee members act as a sub-committee chair, upon request (duties to include, but not limited to, suggesting accept/reject decisions for abstracts, writing session summaries for assigned session(s), moderating a session at the conference, if in attendance).
4. Technical committee members review papers and presentations (duties to include working with the authors to guide the development of their papers/slides, giving suggestions on paper/slides improvements).
5. Technical committee members advise authors on issues such as dry-runs, presentation tips, etc.
6. Technical committee members participate in scheduled technical committee conference calls.
7. Technical committee members act as session moderators at the conference, upon request. (Typically the sub-committee chairs will be assigned as moderators.)
8. Technical committee members vote on the Technical Committee Award paper.
9. Technical committee members make suggestions/recommendations regarding the overall conference.
10. It is preferred that technical committee members attend the conference, though attendance is not mandatory.
Role of the SNUG Technical Chairperson
1. The technical chairperson organizes abstracts into session groups to be reviewed by subcommittees. As part of this session grouping of abstracts, the executive committee recommends to the subcommittees which abstracts should be accepted or rejected and which ones need more information.
2. The technical chairperson organizes subcommittees and appoints subcommittee chairs with the program manager.
3. The technical chairperson sends abstract rejection emails.
4. The technical chairperson ensures that the technical committee includes members with expertise in all areas of Synopsys tools. Adds new members to the committee in areas which lack expert coverage, as needed. Users are preferred, then Synopsys employees if needed.
5. The technical chairperson coordinates the Technical Committee Award.
6. The technical chairperson works closely with SNUG Program Manager to find panels/guest speakers/ or other special events for the conference.
7. The technical chairperson leads technical committee conference calls.
8. The technical chairperson acts as Master of Ceremonies at the conference:
- Welcomes attendees during the general session
- Introduces the Keynote speaker/ Guest speakers
- Announces "Best Paper" and "Technical Committee" awards
- Moderates the technical committee review meeting at the conference
SNUG Technical Chairperson Guidelines
1. The technical chairperson role is a one- to three-year commitment, with a maximum term of three years (per conference). Status of the technical chairperson's role will be reviewed annually by the technical chairperson and program manager.
2. Any member who serves on the technical committee for three or more years is eligible to be the technical chairperson.
3. When it is time to select a new technical chairperson, the current technical chairperson and the SNUG Program Manager identify a qualified candidate. The current technical chairperson contacts that committee member to explain the responsibilities of the technical chairperson, and to gauge interest. If the committee member is interested in the position, the current technical committee chairperson nominates the committee member to the entire committee and all committee members are asked to accept or reject the nomination. The current technical committee chairperson collects the votes and maintains voters' privacy. The majority vote decides. If the majority rejects the nomination, then a new qualified candidate is identified.
Role of the SNUG Program Manager
1. The SNUG Program Manager drives and tracks milestones, deadlines, and variations of the conference.
2. The SNUG Program Manager manages and executes Call for Papers, conference content, registration, and web content.
3. The SNUG Program Manager maintains the technical committee website.
4. The SNUG Program Manager advises and directs core team, SNUG authors, technical committee chairperson and technical committee.
5. The SNUG Program Manager facilitates internal paper reviews.
6. The SNUG Program Manager leads the SNUG core team meetings and assigns action items.
7. The SNUG Program Manager works directly with customers to solicit papers and to stimulate conference attendance.
8. The SNUG Program Manager drives technical authors and technical committee members through the qualifying, reviewing, and publication process of technical papers.
9. The SNUG Program Manager makes final decisions regarding logistics, artwork, web content, and program agenda.
10. The SNUG Program Manager manages SNUG budget, cross-charges, and collection.
Rules to Modify and/or Update SNUG Bylaws
1. The SNUG Bylaws apply to member SNUG conferences. The charter member conferences are SNUG San Jose, SNUG Boston, and SNUG Europe.
2. Other SNUGs can apply to become members at any time by submitting a letter to the Governing Board. This letter will be reviewed and voted on by the Governing Board within 30 days. A 2/3 majority vote is required to admit a new member.
3. The SNUG Bylaws are governed by the current and immediate-past Technical Chairs of member SNUGs, as well as the SNUG program manager(s) who form the Governing Board.
4. All Governing Board members must also be Technical Committee Members of a member SNUG. In the event that a member leaves the board for any reason, no substitutions will be made.
5. Any Technical Committee Member of a member SNUG can petition for a change to the bylaws. That petition will be reviewed and voted on by the Governing Board within 30 days. A 2/3 majority is required to change the bylaws.
6. Any deadlocks in the Governing Board are to be resolved by the SNUG Program Manager(s).
7. Proposals submitted to the Governing Board that are not approved are not eligible for re-submission for one year.
8. All member SNUGs must abide by the latest rules in effect at the time of their Call for Papers.
|
