1 / 23

Writing a Publishable USENIX/SAGE Technical Paper

Writing a Publishable USENIX/SAGE Technical Paper. Joshua S. Simon <jss@colltech.com> Collective Technologies April 8, 1998. Quickest way to get published. Bribe the Committee We may be easy But we’re not cheap!. Overview. Why? What the Committee looks for Increasing your chances.

madeleine
Download Presentation

Writing a Publishable USENIX/SAGE Technical Paper

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Writing a Publishable USENIX/SAGE Technical Paper Joshua S. Simon <jss@colltech.com> Collective Technologies April 8, 1998

  2. Quickest way to get published • Bribe the Committee • We may be easy • But we’re not cheap! Writing a Publishable USENIX/SAGE Technical Paper

  3. Overview • Why? • What the Committee looks for • Increasing your chances Writing a Publishable USENIX/SAGE Technical Paper

  4. Why me? • Attendee & busybody • LISA 1994-1998 • USENIX 1995-1998 (1999?) • Program Committee, LISA 97 • Practicum Track advisor, LISA 98 • Program Committee, LISA 99 Writing a Publishable USENIX/SAGE Technical Paper

  5. Why you? • Why not? • Companies want their name associated with published papers • Managers need justification to send people to conferences • Good for your recognition in the field • Good for your career Writing a Publishable USENIX/SAGE Technical Paper

  6. What the Committee looks for • Extended abstract • Relevance • Presentation • Quality • Overall • Comments Writing a Publishable USENIX/SAGE Technical Paper

  7. Extended abstract • Maximum 5 pages • Can be in outline format • but include paragraphs! • Can you write clearly about your topic? • Can you organize your thoughts well? • Can you convey sufficient information to readers? Writing a Publishable USENIX/SAGE Technical Paper

  8. Extended abstract (continued) • Include graphs, figures, & tables • if central to the paper • don’t count against the page limit • Include notes to the Committee Writing a Publishable USENIX/SAGE Technical Paper

  9. Relevance • Is the paper appropriate for a USENIX conference? • Marketing papers • The Australian emu’s mating habits • Is the work of interest to some or all of the attendees? • Will some or all of the attendees want to attend a talk on this paper? Writing a Publishable USENIX/SAGE Technical Paper

  10. Presentation • Is the paper readable? • Is the language understandable? • Is the problem well-stated? • Are the goals of the solution well-stated? • Are the tests of the solution well-stated? • Are the results well-stated? Writing a Publishable USENIX/SAGE Technical Paper

  11. Quality • Does the abstract briefly & clearly state the goals and conclusions • Is the work technically correct? • Is the work any good? • A new sort algorithm running in O(n5) isn’t • A new sort algorithm running in O(1) is • Are the references sufficient? Writing a Publishable USENIX/SAGE Technical Paper

  12. Overall • Should we accept this paper? • Not an average of the previous 3 values • Presentation, Relevance, and Quality can be improved between abstract and final paper • Fudge factors for intangibles allowed • Is it “fun”? Writing a Publishable USENIX/SAGE Technical Paper

  13. Comments • Qualifications of the reviewer • Written feedback for the author • Comments for the Committee only Writing a Publishable USENIX/SAGE Technical Paper

  14. Questions we ask • What are the weakest and/or least understandable parts of this work • with respect to its presentation? • with the technical aspects? • Are the goals correct? • if not, how should they be changed? Writing a Publishable USENIX/SAGE Technical Paper

  15. More questions we ask • If you think this paper should not be accepted, what needs to be done to it to change your mind? Writing a Publishable USENIX/SAGE Technical Paper

  16. Statistics • LISA 96 • accepted 29 of 76 papers (38%) • 1,058 of >1,650 attendees new to LISA (64%) • LISA 97 • accepted 23 of 56 papers (41%) • LISA 98 • accepted 30 of 63 papers (48%) • 1,985 attendees Writing a Publishable USENIX/SAGE Technical Paper

  17. 1998 LISA attendee affiliations Writing a Publishable USENIX/SAGE Technical Paper

  18. Increasing your chances • Be clear & concise • Have an outline of the paper • Include the introduction • Include graphs, figures, & tables • Include references • Answer the questions the Committee asks • Bribe the Committee Writing a Publishable USENIX/SAGE Technical Paper

  19. LISA ’99 conference info • Extended abstracts due: May 25 • Notification to authors: June 30 • Final papers due: September 19 • Technical sessions: November 10-12 • Location: Seattle, Washington Writing a Publishable USENIX/SAGE Technical Paper

  20. Incentives • Intangible • Recognition in the field • More “fudge factor” in future submissions • Tangible • Cash awards: Best Paper & Best Student Paper • One author of each paper gets complementary registration to the technical sessions Writing a Publishable USENIX/SAGE Technical Paper

  21. Online resources • USENIX web site, http://www.usenix.org/ • LISA ’99 CFP, http://www.usenix.org/events/lisa99/cfp/cfp.html • LISA ’99 Topics, .../cfp/cfp5.html • LISA ’99 Submission Guidelines, .../cfp/guidelines.html • Submitting an abstract, .../cfp/submit.html Writing a Publishable USENIX/SAGE Technical Paper

  22. Questions • Who are you? • What do you want? • Why are you here? • Do you have anything worth living for? Writing a Publishable USENIX/SAGE Technical Paper

  23. Questions Writing a Publishable USENIX/SAGE Technical Paper

More Related