----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49067/#review139143 -----------------------------------------------------------
I'm wondering if we should just seed this list with Mesosphere employees for now, mainly to play safe. Some of the affiliations in this list are out-of-date and some might not even be public knowledge. Better to let users send PRs than us including them. I was thinking that we could maybeaeadd sending a PR t to this file as a s step in our new contributor workflow. AFFILIATIONS.yml (line 82) <https://reviews.apache.org/r/49067/#comment204291> pull this to the top? AFFILIATIONS.yml (line 120) <https://reviews.apache.org/r/49067/#comment204290> s/Mesosphere/Microsoft/ ? AFFILIATIONS.yml (line 353) <https://reviews.apache.org/r/49067/#comment204287> pull name to the top? AFFILIATIONS.yml (line 366) <https://reviews.apache.org/r/49067/#comment204286> s/Mesosphere/Twitter/? - Vinod Kone On June 22, 2016, 7:05 a.m., Artem Harutyunyan wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/49067/ > ----------------------------------------------------------- > > (Updated June 22, 2016, 7:05 a.m.) > > > Review request for mesos, Joris Van Remoortere and Vinod Kone. > > > Repository: mesos > > > Description > ------- > > Added AFFILIATIONS.yml file. > > > Diffs > ----- > > AFFILIATIONS.yml PRE-CREATION > > Diff: https://reviews.apache.org/r/49067/diff/ > > > Testing > ------- > > Parsed the file with a test script to validate the syntax and generate the > list of contributors currently missing from the file. > > > Thanks, > > Artem Harutyunyan > >
