Changes between Version 1 and Version 2 of org/meetings/2018NetworkTeamHackfestSeattle/LargePatches


Ignore:
Timestamp:
Jun 6, 2018, 8:11:23 PM (13 months ago)
Author:
catalyst
Comment:

clean up formatting

Legend:

Unmodified
Added
Removed
Modified
  • org/meetings/2018NetworkTeamHackfestSeattle/LargePatches

    v1 v2  
    1 List of large patches over last couple of years:
     1== List of large patches over last couple of years ==
    22
    3 List of big big patches
     3* Big big patches
     4  - V3 onion patch series
     5  - Rust build system changes
     6  - Rust protover
     7  - Protover voting changes
     8  - KIST and the schedulers
     9  - Shared Random
     10  - Guard overhaul (prop 271)
     11  - Consensus diff stuff
    412
    5 - V3 onion patch series
     13* Not merged
     14  - Bridge guards (prop 188)
     15  - KIST v1
     16  - All the datagram tor papers
     17  - Cell nageling 7743?
     18  - All those research papers
    619
    7 - Rust build system changes
     20* Pervasive but not big:
     21  - crypto.h refactor
     22  - free macros
    823
    9 - Rust protover
    10 
    11 - Protover voting changes
    12 
    13 - KIST and the schedulers
    14 
    15 - Shared Random
    16 
    17 - Guard overhaul (prop 271)
    18 
    19 - Consensus diff stuff
    20 
    21 
    22 Not merged
    23 
    24 - Bridge guards (prop 188)
    25 
    26 - KIST v1
    27 
    28 - All the datagram tor papers
    29 
    30 - Cell nageling 7743?
    31 
    32 - All those research papers
    33 
    34 Pervasive but not big:
    35 
    36 - crypto.h refactor
    37 
    38 - free macros
    39 
    40 
    41 
    42 
    43 Insights:
     24== Insights ==
    4425
    4526- Start small
    46 
    4727- We should offer to do the changes needed.
    48 
    4928- Offer feedback like "for next time..."
    50 
    5129- Can we tag org members on trac? (So people know whether they are getting feedback from somebody who seriously knows what's up)
    52 
    53 - We need to get our message across in a positive way, and say "hey, you need
    54   to get to know us".
    55 
    56 - Maybe we should say more about what to expect when you talk to us and send
    57   in a patch.
    58 
    59 - Try to be more welcoming and less intimidating to potential contributors
    60 -- we have high standards, but we could be kinder about helping people
    61 meet them.
    62 
    63 
    64 
    65 - What to expect (both for an individual contribution and for integrating
    66 into the team?)
    67 
    68 - Learning conventions of how the team works is important -- some of this
    69 we don't write down for various reasons.  Also it can be intimidating if
    70 we write all of it down in one place.  Maybe high-level overviews are best.
    71 
     30- We need to get our message across in a positive way, and say "hey, you need to get to know us".
     31- Maybe we should say more about what to expect when you talk to us and send in a patch.
     32- Try to be more welcoming and less intimidating to potential contributors -- we have high standards, but we could be kinder about helping people meet them.
     33- What to expect (both for an individual contribution and for integrating into the team?)
     34- Learning conventions of how the team works is important -- some of this we don't write down for various reasons.  Also it can be intimidating if we write all of it down in one place.  Maybe high-level overviews are best.