silverlab/megavista — Issue #4: Startup tasks from megavista meeting
Author: racheldenison
Created: 2011-11-28 01:53:58+00:00
State: open

Hi Silver Lab,

At the megavista meeting on Wednesday, we came up with a list of things to do to get started using the version control system. Here is what we decided, and who is responsible for doing the various startup tasks:

1. Try the entire git workflow, especially the most common situation of working on and syncing your local and remote megavista repositories ("megavista" on your laptop with your user remote, eg. "cgratton"). Everyone should do this before our next meeting with Fernando and should note places where you run into problems. These will be good questions for Fernando.

2. As a lab, we should try the entire git workflow, including the process of initiating and accepting a pull request to "silverlab". Alina will be responsible for getting this started by adding the mrVista_utils code to the "silverlab_vista_tools" directory.

3. We want to test the speed of scripts run from megavista code that lives on the local hard drive compared to code that lives on Plata. This will inform whether people want to download a personal megavista repo on each machine they work from, or whether they will use their megavista repo in their Plata1 home directory (which we agreed would be the default). Summer, you were voted to be in charge of these speed tests since it seems like you have some experience with speed issues. Will you be able to do this?

4. Repo locations and naming conventions on lab computers -- Alina has updated the wiki with the conventions we decided on. See Git / Installing Git & Megavista.

5. Git and Megavista info on wiki -- Caterina has organized and expanded the "FP tutorial" in the Git folder on the wiki.

6. We decided that everyone should make their own matlab startup file specific to their megavista path. So there will be no generic startup megavista functions on lab computers.

7. We decided that issues that arise related to megavista should be communicated about via github as an issue (like this one!), in order to keep a lab-wide record of all issues. We should make a habit of documenting all megavista bugs/development/use issues in this way. Documentation describing resolved issues can be added to the wiki when appropriate.

8. I also have a note that we decided to add computer-specific compiled flies to gitignore, but I didn't note down who would be in charge of this (?)

Cheers,

Rachel