title: Gulp.js conventions for tasks names
body: <p>Are there any conventions for writing Gulpfiles, namespacing the tasks, structuring the config file etc? </p>
  
  <p>Maybe there are some basic common-sense things that can be taken from Grunt world? </p>
  
  <p>How do you deal with structuring the Gulpfile as if you were to quit your job and the next JS developer would come and intuitively understand how to build the project?</p>