Collaborative Tools • Sharing Knowledge: Media Wiki and other collaborative tools -- Matt Bellis • Sharing Code: Distributed version control and social development -- Joe Blaylock • Sharing Science: SSRL Remote Lab -- Thomas Eriksson • Sharing Results: Reading, writing, citing and sharing HEP-- Travis Brooks • Collaboration tools: What is (or should be) centrally supported at SLAC -- Tony Johnson • Favorite collaboration tools for science -- open mike
19
Embed
Collaborative Tools Sharing Knowledge: Media Wiki and other collaborative tools -- Matt Bellis Sharing Code: Distributed version control and social development.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Collaborative Tools
• Sharing Knowledge: Media Wiki and other collaborative tools -- Matt Bellis
• Sharing Code: Distributed version control and social development -- Joe Blaylock
• Sharing Science: SSRL Remote Lab -- Thomas Eriksson• Sharing Results: Reading, writing, citing and sharing
HEP-- Travis Brooks• Collaboration tools: What is (or should be) centrally
supported at SLAC -- Tony Johnson• Favorite collaboration tools for science -- open mike
Collaboration tools: What is (or should be) centrally supported at SLAC
SLAC Web Tools• There was a time when SLAC led the world in collaborative web tools for science
– That time was 1991 – and back then it didn’t take very much
Collaborative tools at SLAC (20 years on)• Centrally Supported Tools– Confluence Wiki– JIRA web based issue tracking– Forum– (Share point)– Single sign-on service (crowd)
• What tools should be centrally supported (if any)?– Discussion
Confluence Wiki
• Installed for use by Glast/Fermi in 2004• Rapidly adopted by collaboration
– Very mild learning curve• people just pick it up
– Became focal point for software development and later physics analysis discussion• Recently modified documents page provided
easy way to see what was happening in the collaboration
• Although installed initially for Fermi many other groups started using it– 2010 support migrated from Fermi to
Current usage• >100 spaces• Used by many experiments and groups
Creating a Confluence Space• Create a personal space– Login (with SLAC windows or unix password)– Click “Your Name” in top menu and select
• “Create Personal Space”
• Create a space for your group/project/experiment– Send e-mail to [email protected]
• Name of space• Brief description of space• Who will be the administrator(s) of the space• Who should be able to view space (everyone, anyone logged in, specific
group of users)• Who should be able to edit the space• Whether “collaborators” without existing SLAC accounts should be able
JIRA Issue Tracker• Web based issue tracker• Used at SLAC since about ~2000
– Adopted by Fermi in 2003 for tracking issues in software development
– Centrally supported by computing division since 2010• More than a bug tracker
– Track issues and feature requests– Allow users/developers to comment on and discuss issues– Allows bugs/features to be associated with specific future release
• Lightweight project planning
– Designed from outset as entirely web based product• All administration can be done by web• Well suited for distributed development of software
– Very flexible permission/notification scheme– Custom workflows allow specialized use
• Tracking configuration control requests• Tracking mc simulation requests
JIRA screenshot
Using JIRA on your project
• E-mail [email protected]– Requested name, description, adminstrator(s) – Explain how you plan to use JIRA• JIRA has many configuration options so the more you
can describe anticipated use the faster your project can be set up
• Discussion software such as hypernews has been very popular on BaBar and other experiments
• IT steering committee + Scientific computing steering committee + Computing division have recently set up discussion forum software for use at SLAC– Initially restricted to discussion of computing
• Intended to encourage peer-2-peer discussion on topics of general interest• Mechanism for bi-directional communication with steering committee
• Available to anyone with a SLAC windows or unix login (or approved collaborators)– https://forum.slac.stanford.edu/
• You are encouraged to use it– At least to tell us how we can make it more useful