anchor.diff:  
   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
  +we gather feedback from GitLabbers 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
  
positive.code: #### "What do you wish we had / What are you wondering about"
  
  1. "Contractor or employee? Worried about job security as a contractor."
     * We value all team members equally, regardless of the legal arrangement that
     you have with GitLab. Due to legal restrictions and the difficulty of having
     people be employees outside of the US or NL (where we have a legal entity), a
     large portion of the team are contractors (21 out of 46). At GitLab, as everywhere
  
negative.code: 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 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
  
  