<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sebastian Rahtz on Ariadne</title>
    <link>http://www.ariadne.ac.uk/authors/sebastian-rahtz/</link>
    <description>Recent content in Sebastian Rahtz on Ariadne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 29 Jul 2005 23:00:00 +0000</lastBuildDate>
    
	<atom:link href="http://www.ariadne.ac.uk/authors/sebastian-rahtz/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Building Open Source Communities: 4th OSS Watch Conference</title>
      <link>http://www.ariadne.ac.uk/issue/44/oss-watch-rpt/</link>
      <pubDate>Fri, 29 Jul 2005 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/44/oss-watch-rpt/</guid>
      <description>When people get together and talk about open source, there are three things that come into the conversation early on. Firstly, they argue about open source licences; secondly, they ask &#34;but is it really free?&#34;; and thirdly, they state that &#34;it&#39;s all about the community&#34;. That last one is definitely worth unpacking further.
When a new project starts, or an existing project is being assessed, everyone will ask &#34;what sort of community does it have?</description>
    </item>
    
    <item>
      <title>Looking for a Google Box?</title>
      <link>http://www.ariadne.ac.uk/issue/42/rahtz/</link>
      <pubDate>Sun, 30 Jan 2005 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/42/rahtz/</guid>
      <description>Most Web sites of any size want to offer a facility to perform a free-text search of their content. While we all at least claim to believe in the possibilities of the semantic web, and take care over our navigation aids and sitemaps, we know that sooner or later our readers want to type &#39;hedgehog&#39; into a search box. Yes, even http://www.microsoft.com [1] returns plenty of hits if you try this.</description>
    </item>
    
    <item>
      <title>Support Models for Open Source Deployment</title>
      <link>http://www.ariadne.ac.uk/issue/40/oss-watch-rpt/</link>
      <pubDate>Thu, 29 Jul 2004 23:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/40/oss-watch-rpt/</guid>
      <description>OSS Watch&#39;s [1] second national conference focused on an often articulated anxiety concerning how an institution will answer the question of support when considering the deployment of open source software. OSS Watch is a pilot advisory service set up by the Joint Information Systems Committee (JISC) to provide UK Higher and Further Education with neutral and authoritative guidance about free and open source software. Whereas OSS Watch&#39;s inaugural conference in December 2003 [2] presented an overview of the entire field, this event concentrated on what is sometimes thought to be the single most significant barrier to institutional take-up of open source software.</description>
    </item>
    
    <item>
      <title>OSS Inaugural Conference: Open Source Deployment and Development</title>
      <link>http://www.ariadne.ac.uk/issue/38/oss-watch-rpt/</link>
      <pubDate>Fri, 30 Jan 2004 00:00:00 +0000</pubDate>
      
      <guid>http://www.ariadne.ac.uk/issue/38/oss-watch-rpt/</guid>
      <description>OSS Watch [1] is a pilot advisory service set up by the Joint Information Systems Committee (JISC) to provide UK higher and further education with neutral and authoritative guidance about free and open source software and related standards. Although it is rather small, (a staffing of 1.25 full-time equivalent (FTE)), this new service has stakeholders ranging from IT directors and managers developing institutional IT strategies that acknowledge the role that open source software does (and will continue to) play; to IT staff deploying software across universities and colleges; and to software developers seeking advice on how to release their work as open source.</description>
    </item>
    
  </channel>
</rss>