OpenSourceMalaria:Technical Operations: Difference between revisions
Mike Robins (talk | contribs) (New page: This provides an outline of the technical and development operations for the Open Source Malaria (OSM) project. This document is intended to provide an outline of the technical and develo...) |
Mike Robins (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{OpenSourceMalaria}} | |||
This provides an outline of the technical and development operations for the Open Source Malaria (OSM) project. | This provides an outline of the technical and development operations for the Open Source Malaria (OSM) project. | ||
Revision as of 04:20, 20 November 2013
This provides an outline of the technical and development operations for the Open Source Malaria (OSM) project.
This document is intended to provide an outline of the technical and development operations for the Open Source Malaria (OSM) project. It also includes some related information about social media accounts.
Main website
The main website for the project can be found here. The project activity is pulled directly from the OSM Github organisation. The source for the site is also available, the pulling activity uses Ruby/Sinatra.
Lab notebook
Users use the open source lab notebook Labtrove (previously Lablog) a PHP web application developed by the University of Southampton. Currently the primary malaria blogs run on malaria.ourexperiment.org on a Debian server at the University of Southampton.
Odd jobs
For random jobs where we require hosting/a bit of compute the tendency is to use Nectar, a cloud based provider for academic and research institutions in Australia. It provides two free instances to researchers with reasonable enough specs that they can be used for most jobs. Debian or Ubuntu is typically the flavour of choice, but Nectar provides a wide range of images and snapshots including versions of Scientific Linux. For jobs which may require significantly more processing we may rely instead upon EC2 instances.
Communication
There are several different means used for communication, with email being the least favoured (due to a lack of openness).
OSM has a Twitter account, as well as a Google+ account. In addition Youtube account is used to post the recorded videos of meetings.
The primary means of communicating issues including admin, chemistry and technical related queries is the Github account. The current todo list, tagged with the category of issue it relates to can be found on the 'Issues' tab of the OSM to do list repo.
Github
Almost all code and data is resident on one of the Github repositories for the OpenSourceMalaria organisation account. If the data you are looking for cannot be found there, or you are looking for experimental data the best place to probably look is the Labtrove blog. If you still are unable to find something, post an issue on the Github todo list and someone can attempt to address the issue.
Online Meetings
Online meetings use Adobe Connect provided and hosted by the University of Sydney. As with everything else, these meetings are open to everyone and each meeting is recorded and subsequently uploaded to the OSM youtube account.
- Mike Robins 20:00, 26 October 2013 (EDT):
