Martinos Dev Meetings Topics

This is a list of future Martinos Dev meeting topics. Martinos Dev meets at 2pm on Wednesdays in the CSRL meeting room in Building 149. Please add requests or volunteer to present your own topics.

Topics

• 10/26: JoshSnyder - Code review.

• 11/2: NickSchmansky - Use of splint to verify and standardize code.

• 11/9: DennisJen - Comparison of IDEs and project management tools.

• 11/16: Cancelled
• 11/23: Vacation

• 11/30: DavidTuch - Interruption management

• 12/7: Town hall meeting

• 12/14: FreeSurferWiki tutorial

• 12/21: Vacation

Reserve Topics

Topics which can be used if a scheduled speaker becomes unavailable.

DavidTuch - Permutation algorithm

Requests

• using Doxygen, http://www.stack.nl/~dimitri/doxygen/ (nick)

• applying Knowledge Management tools to extract an ontology from the Freesurfer mailing list (to categorize emails), discuss these topics: http://www.searchtools.com/info/classifiers.html (nick)

Resources from past meetings

Interruption Management

• [http://www.google.com/search?hl=en&q=life+hacks]

• [http://www.43folders.com/]

• [http://interruptions.net/literature/Dekel-OOPSLA04.pdf]

• [http://domino.research.ibm.com/cambridge/research.nsf/0/8fa06db80b048edf85256ed80064a301?OpenDocument]

Process Tool and IDE Comparisons

• [http://www.nmr.mgh.harvard.edu/~dsjen/process/ProjectManagementOutline.html Process Tool Comparisons Outline]

  • Plone plugins we'll use:

    • [http://plone.org/products/zepp Zepp Workflow]

    • [http://plone.org/products/poi Poi Issue Tracking]

• [http://www.nmr.mgh.harvard.edu/~dsjen/process/IDEMindMapOutline.html IDE Comparisons]

  • Interesting Eclipse plugins:

    • [http://www.eclipse.org/cdt/ CDT (C++ Plugin)]

    • [http://www.eclipse-plugins.info/eclipse/plugin_details.jsp?id=1166 CDTSplint (Splint Plugin]

    • [http://subclipse.tigris.org Subclipse (SVN Plugin)]

    • [http://subclipse.tigris.org PyDev (Python plugin)]

Code Review

• [http://www.processimpact.com/articles/inspects.html Process]

• Pretty printing source code from Linux: enscript -r -2 -C -E<language> -P <printer> <filename>, where language is c or cpp, printer is the name of your printer as you would pass it to lpr, and filename is the .c or .cpp file. This will queue the file to the printer.

In-house Code

• RudolphPienaar has put together a [http://www.nmr.mgh.harvard.edu/~rudolph/software/toolsAndUtilities/internal/internal.html page] to keep track of code developers have available for in-house use. Please feel free to email him to contribute your own code.