- dgraph uses glock  for dependency management
- Go 1.6 has vendoring enabled by default
- glock has conditional support for vendoring as that is implemented in a branch  
- Recent node js fiasco  and go best practices  for other projects clearly indicate that vendoring is an important and useful practice
- Seems like other projects that are facing the similar issue are moving away from glock e.g. cockroachdb  
Is there a plan in place for dgraph to start vendoring dependencies?
glide  and govendor  seem to be good candidates for using the /vendor directory feature for golang for dependency management
- Discuss doesn’t let me assign this into dev or technical category, might be something related to permissions.
- Apologies for unclickable links, as a new user I cannot have more than 2 urls in my post.