anchor.diff:  1. Instructions on how to build a project on GitLab.
     * Here is some [documentation](https://docs.gitlab.com/ee/gitlab-basics/create-project.html) on how to build a project within GitLab.
   
  -We also received a many responses stating we should not change or add anything, and that GitLab is an awesome place to work. This is great that team members feel this way, and People Ops will continue to strive to create a culture where team members are satisfied and engaged. Want to see where most of these changes were made? Check out the [issue](https://gitlab.com/gitlab-com/peopleops/issues/122)!
  +We also received a many responses stating we should not change or add anything, and that GitLab is an awesome place to work. This is great that GitLabbers feel this way, and People Ops will continue to strive to create a culture where GitLabbers are satisfied and engaged. Want to see where most of these changes were made? Check out the [issue](https://gitlab.com/gitlab-com/peopleops/issues/122)!
   
   ### Feedback from September 2016, and presentation of responses
   
  
positive.code: 
  By sending out our Feedback Form (find the link to the "open" form by accessing
  [this "closed" document](https://docs.google.com/document/d/12ZAACGeS2_nz6AFXqf78x9iv2LB_hyX9fcT4s9nJF4M/edit))
  we gather feedback from the team members anonymously. We then share the main highlights
  and concerns / wishes / things people wonder about with the entire team by discussing
  them during our [Team Call](https://about.gitlab.com/handbook/#team-call) and posting
  all topics that came up along with their responses here (with the exception of
  
negative.code: 
  ### _October 10th, 2015_
  
  Anniversary of our first ever summit in Amsterdam with 25 GitLabbers.
  
  
  ## Team Stories
  