Shared Development Environments
- Atom
- Visual Studio Code
- Screen share in one of the communication tools
Communication
Institutions generally have communication channels that are available for use by developers for collaboration. Some of the common communication tools are listed in alphabetical order. As groups form, one of the members in the group can host from the platform they have available.
Video chat...
Text chat...
- Slack - recommended as this is the platform used by the Samvera community
- developer-congress channel - used for general discussions of interest for the whole group
- direct messages - used for sub-groups as they form
Helpful Hints on How to use Visual Studio
Thanks to Chris Colvard (Deactivated) for creating these hints for the 2019 Dev Congress.
- Install Visual Studio Code. It is free and has Win/Mac/Linux versions.
- Next install the Live Share Extension Pack. This includes the Live Share plugin and the Live Share Audio and Chat plugins.
- Once these are installed, read the quickstart for joining a live share.
- If you want, read the longer documentation about all you can share (editors, shells, servers, etc.) during the live share.
- During the Dev Congress, one person can create the live share, send the live share link on slack, and then others will join. The host doesn't need to be the person leading the swarm but should already have a checkout of the code and the test suite passing locally. The host should have a stable network connection to avoid others being kicked off the live share session. Also note that regardless of who makes code changes they will appear in any commits as the host of the live share so the host should always use `co-authored-by` in the commit messages to credit all who worked on the commit.
Helpful Hints on Using Zoom Effectively
Thanks to david.schober for providing these hints from online conferences
Zoom Regular
(limit 300 people Northwestern)
- manual acceptance of each person
- can screen share
- Record meeting?
Zoom webinars
- enhanced registration
- Needs a request (from Northwestern) at least
- everyone comes in silent
Recommendation:
- Each room leader should host their own zoom meeting
- Get a protocol for Zoom bombing (immediately shut it down)
- Use a password
- Follow university guideline(s) for Zoom