ProjectIdeas

(legacy summary: Things you can work on if you're interested in contributing)

Project Ideas for Potential Contributors

• Figure out what prevents popular JavaScript libraries from cajoling (like jQuery, Prototype, and others).
  • Either improve the coverage of our DOM wrappers or submit patches to the libraries.
  • Contributor must know JavaScript.
  • Contributor must be comfortable working with the Document Object Model in web browsers.
  • If the problems are insurmountable (unlikely, but possible) then the popular libraries will need taming.
• Create an Auditor framework for SES code
  • Contributor must know JavaScript.
  • An understanding of object-capabilities principles would be helpful.
  • One auditor should be able to prove that certain objects are immutable
• Static analysis and optimization
  • Plenty of places optimization could occur
    • removal of temporary JavaScript variables
    • removal of type checks and other runtime checks
    • improving the speed of the rewriter
    • etc.
  • Contributor must know Java, and it would be better if they knew JavaScript
• Ambient-authority-to-capability membrane
  • Take a username and password for a site and attenuate that authority so it can be doled out in smaller pieces
    • Given the URL of a webpage and authentication info, rewrite the page so that all URLs point back to the rewriter (a membrane)
    • Remove all content from the page except the whitelisted parts, allowing finer divisions of authority than not all-or-nothing
  • Contributor must know object-capabilities principles.
• Shahar-related project ideas
• Bridge building between Joe-E, GWT, and Caja
  • For example, Identify the intersection of GWT and Joe-E, and adapt GWT to compile it to Caja-compatible, Joe-E-security preserving JavaScript.
• Suggest something!
• Tech writing doesn't qualify for a GSoC project, but if you're a tech writer, we'd love to have you write documentation! See DocumentationIdeas.