Sage Days 46: Hawaii -- computational number theory, etc. -- PROJECTS

Single Cell Server

People: Jason Grout, William Stein

Make the single cell server use stunnel for ssl support. Benefits: this makes websockets more reliable, and of course makes the server more secure.
Make the single cell server highly available, i.e., deployed on multiple machines in multiple locations, with no single point of failure. Currently, this is VERY hard because of the use of SQLite.

Salvus: Worksheet Views

People: William Stein, Jason Grout

Worksheets in Salvus have numerous "views" -- JSON, LaTeX, PDF, print, XML, etc. -- do a polished implementation of all of these. This is a 100% frontend CoffeeScript development project. The basic skeleton is completely in place.

Sage.math cluster

People: William Stein, Keith Clawsen, Volker Braun, Jason Grout

KVM -- Address some specific needs of the combinat group on combinat.math.washington.edu. (See William for details.)
KVM -- Move the single cell server into a virtual machine.
KVM -- Figure out how to do live snap-shotting of virtual machine's RAM for infinite computations.
Hardware -- make a plan for disk, power supply (and other?) upgrades.

The Patch Referee Award

People: William Stein, Keith Clawson

Design and implement a weekly award to the person who referees the most trac stuff, for some arbitrary definition. Keith and William have done some work on this. Things to decide:
- definition of "most" -- this is social -- what do you think.
- the prize itself: money (e.g., amazon.com gift certificate) or something else?
- How to implement: use trac postgresql, etc.

Salvus UI Testing and Design

People: William Stein

No significant thought has gone into the user interface of Salvus -- it's been all about implementing functionality, with basically no thought about where buttons are located, whether or not there are menus, how things are named, colored, and laid out, etc. For this project, you would simply try out salvus -- there are NO INSTRUCTIONS YET -- and sketch on paper how you think the user interface could be better laid out. Salvus mainly uses http://twitter.github.com/bootstrap/, so keep the widgets, colors, etc., available there in mind. This requires only a web browser, paper, and pencil.

Make some paper sketches of how *you* would lay out the UI.
What should be in the help/tutorial for Salvus? What questions would you want answered?
What are you top priority things to be user-configurable? Color schemes? Key to evaluate code (shift-enter)?

Note: Basically all development has so far been done Google Chrome under Linux.

Salvus: New Implementations of things that are in Sagenb