Sardines is an experiment in organizing a tiered, distributed wiki that is motivated by Open Science.
Imagine research that takes place in a lab and is recorded and documented on an electronic platform such as a blog or wiki. It’s reasonable to conceive that the researcher may want to keep a closer hold on their findings for a short time in order to polish and confirm, before releasing it into the open.
This being said, it would be nice if the data, before being released publicly, were available within the entire research lab or institution. It’d also be great if the publication process seemed relatively seamless and that the interfaces for local private edits and global public edits be similar. To cap it all off, people “downstream” (i.e. in the lab) should automatically get updates when changes are made available “upstream.”
Example
Distributed document versioning
In this example, there is one public server and two private servers; labs Alpha and Beta each have a private instance of the server running so that they are assured of privacy. Lab Alpha has published version 3 of its research, although they have an internal copy which is more recently updated. The published version is available on the public server and is made known to Lab Beta’s server. Lab Beta has private research which it has not yet released.
Notes
It may very well be the case that this idea constitutes “too much software,” and a simple published-state property on a central wiki would suffice.
In my last term at RIT, I took a course titled Innovation and Invention with Dr. Jon Schull. It was rather experimental, with a breakneck pace and minimal organization that was both highly productive and rewarding. It has continued to flourish, and has significant overlap with the new Collaboratorium at RIT.
As part of this course, I worked on a multitouch display (see my project log for the multitouch table). Matthew Kampschmidt and I gave a talk that introduces multitouch technology and applications, as well as the fundamentals behind FTIR (Frustrated Total Internal Reflection).
I gave a talk in January 2007 for my Language Processors and Compiler Construction course at RIT on Rockit, a parser generator library for Ruby. I touched on versions 0.3.8 and 0.7.2, which are GLR and PEG driven, respectively.
I gave a talk at RubyConf 2006, detailing my project for the Google Summer of Code 2006. I worked on type inference for the purpose of code completion in the Ruby Development Tools Eclipse plugin with Chris Williams as my mentor. Chris has gone on to work with Aptana on RadRails.
You can read the archives of my project blog.
I gave a talk at our second Rochester on Rails meetup in January 2006 that is an entry-level introduction to Rails (circa 1.13) . It covers the history, reasons you may use it in a project, and basic architecture of Rails.
I gave a talk at our second Rochester on Rails meetup in January 2006 that gives a brief and basic introduction to the syntax of Ruby 1.8, along with a few nice language features.
Hey, what’s up. I’m Jason. I love code, science, and building cool stuff.
Some awesome stuff:
I go to:
Some stuff I did before:
Elsewhere on the internet:
You can get in touch with me at jason dot p dot morrison at gmail.
I’ve installed Mephisto to try and organize my thoughts and projects. We’ll see how this goes!
My old content is available at About.
My resume was last updated April 3, 2007, and is available in PDF.
