Changes between Initial Version and Version 1 of org/meetings/2017Montreal/Notes/Rust


Ignore:
Timestamp:
Oct 12, 2017, 4:05:48 AM (17 months ago)
Author:
asn
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2017Montreal/Notes/Rust

    v1 v1  
     1= rust retrospective =
     2== critical things to do before deciding about rust ==
     3=== rust builds on windows ===
     4=== platform support ===
     5 *  takeaways: their support goals is quite like our support goals
     6 *  need to make sure that rust will work well in mobile!!!
     7 *  get in touch with tor mobile people so that they can try rust in mobile!!!
     8 *  (maybe not all parts of tor need to run on mobile?)
     9=== need tor team members experienced with rust ===
     10=== need non-trivial rust code in tor ===
     11=== need reproducible builds / reproducible rust? ===
     12 *  ximin working on this for debian
     13 *  tor browser team will have to figure this out anyway, since ffox 59 ESR (late june 18) will include rust
     14 *  maybe we should try helping tor browser team?
     15 *  next dev meeting is march 18 so before ffox 59. so that's good.
     16 *  who else from debian can help with this?
     17
     18== status update ==
     19=== chelsea's protover code reviewed by rust people. a few review pooints need to be addressed
     20=== rust people found the ffi code pretty good
     21
     22== future ==
     23=== optional off-by-default rust in 0.3.3 ===
     24=== also, get a few more modules going in 0.3.3 ===
     25 *  chelsea's protover as a first candidate
     26 *  dirauths in rust?
     27 *  use isis ed25519-dalek code in tor (needs audit by people who know how to edit that sort of code!!!)
     28=== also, get more feedback from people to try rust in various platforms (variety of OSes, mobile, compilers, etc.) ===
     29=== also, speak to our linux packagers and inform them that we are doing rust and let us know if they envision any problems with it ===
     30=== also, write a blog post about rust support and our platform support policy + our timeline ===
     31
     32=== need some sort of verification mechanism to ensure that C files and rust files are in sync ===
     33
     34=== pair up with different peopple everytime when working on rust stuff to propagate knowledge ===
     35
     36=== how to fit the rust stuff easier into our sponsor roadmap?? ==
     37 *  the modularization proposal?
     38 *  the dos resistance grant? (no crashes!)