Team development and source control
It's easy for development team members to collaborate under Hubzero. All the users listed on the development team of a tool have access to that tool's repo. So, dev team members can check out tool code to their home directory and tinker with it, merge changes, check it back in, etc.
You can create a subdirectory of your home directory, called 'apps' or the like, where you check out shared tool codes. Then you can run our local Jupyter tool there to work on those notebook codes.
Our tools are under source control in the Hubzero environment. The source control software used by default is subversion, also known as 'svn'. A handy reference for subversion can be found here: http://svnbook.red-bean.com/
Example: To check out the current version of a tool called toolio to the current directory:
svn checkout https://vhub.org/tools/toolio/svn/trunk .
Note that when you are first creating a tool you can opt to mark it as a git repo (svn is the default selection).
In general in the Hubzero environment we can finely control the availability of tools and datasets. You can mark a resource as accessible by any group or set of individual users. Do this in the tool metadata page when you first create a tool, or when you are editing it to prepare for a new release.
The way we have GHub (theghub.org) set up now, it is a sub-group of the VHub (vhub.org) installation. So, if you mark something as a ghub resource, all the ghub group members can access it. If you prefer you can limit access to a small number of users.