Topics of interest to the Conference on Reliable Awesome Projects (no acronyms please) include
Systems-ish thingsPapers on all other topics will be rejected, including anything tangentially related to AI.
PL things (if you must)
DBMS stuff (if you must)
Reviewing of full papers will be done by the Conference on Reliable Awesome Projects (no acronyms please) program committee, which consists of me (Remzi). Papers must use a typeface no smaller than 10 point, and be no longer than TEN (10) 8.5" by 11" pages including everything (text, figures, references, and so forth).
All papers must be submitted as PDF.
Submissions will be judged on originality, significance, interest, clarity, relevance, and correctness. Unlike most other conferences, all papers will be accepted and distributed via the online electronic proceedings. Thus, submit and join us in celebrating Conference on Reliable Awesome Projects (no acronyms please) !
Title and Author List: should be self-evident.One good way to structure a paper is to find a paper you liked in class and copy its structure (loosely).
Abstract: Describe in short what you do, how you do it, and the results.
Introduction: Spend a little more time. Motivate the problem. Start with generalities, and narrow in on your problem. Describe your approach. What is good about it? Potential weaknesses? Summarize results. Give an outline of the rest of the paper.
Related Work: Write about other similiar work. What is different than what you did? What is similar? Try to draw general conclusions about what others have missed.
Description of what you did/built: Use pictures and words to show what you did. Be detailed. Think about how to organize what you are doing.
Results: Graphs and tables, all clear and understandable. Full description of each experiment and the results. What is the point of each graph? What conclusions can you draw from it?
Conclusions: Appropriately drawn from the work described, as general as possible, with a hint of "lessons learned"; what did you get out of the study? Summary is what you did; conclusions are what you learned.
Some suggested readings (to make you a better writer):
Read this paper about how to write a technical paper
Read this paper about how to write sentences, paragraphs, etc.
And, of course, read Strunk and White. Many times.
If you plan on using latex (which is great for this sort of thing), click
here for an example Latex template
(in tar format). If you plan on using MS Word, please make sure you know how to generate PDF. Also, make sure to make your paper non-ugly, which is hard if using Word.
Authors of all papers will be expected to provide an
to their paper, and to the
described in their paper. Papers, software, and data will all be collected for inclusion in an electronic version of the symposium. Also, make sure to include your