<?xml version="1.0" encoding="iso-8859-15"?>
<feed xmlns="http://www.w3.org/2005/Atom">
 <title>WikiRing Blog (combined)</title>
<subtitle type="html">Get on the scene</subtitle>
<updated>2010-01-20T22:56:26Z</updated><link rel="self" type="application/atom+xml" href="http://wikiring.com/Blog/WebAtomCombined" />
<link rel="alternate" type="text/html" hreflang="en" href="http://wikiring.com/Blog/WebAtomCombined" /><generator uri="http://wikiring.com/TWiki/BlogPlugin">
  TWiki TWiki-5.0.0, Wed, 23 Jan 2008, build 16283, BlogPlugin $Rev$
</generator>
<id>tag:wikiring.com,2010-03-09:Blog.WebAtomCombined</id>
<rights>Copyright &#169; 2010 WikiRing Partnership</rights>
<entry>
<title> Paula Jenna replies on "Hostile takeover of Open Source Project TWiki"</title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogComment12" />
<id>tag:wikiring.com,2010-01-20:Blog.BlogComment12</id>
<updated>2010-01-20T22:56:26Z</updated>
<published>2010-01-13T04:38:43Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml"> <b>Thanks</b>   <p />I think im gonna start a wiki for web hosting. Could any one point me at a link for a how to on getting started. Which interface to use ..etc.
<p />
Thank you 
<p />
Paula J 
</div>
</content>
<author>
<name>Paula Jenna</name><uri>http://wikiring.comMain/</uri>
</author>
<p />
<p />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> gmc replies on "Development of Foswiki and TWiki &#8211; get the facts (Part 1)"</title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogComment9" />
<id>tag:wikiring.com,2009-11-17:Blog.BlogComment9</id>
<updated>2009-11-17T13:04:24Z</updated>
<published>2009-11-17T13:04:24Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml"> <b>Some other sources underwriting your results</b>   <p />Sven Dowideit made a reasonable comment on IRC as well, with links to some objective sources that confirm your analysis:
<p />
11:31 &lt;@SvenDowideit&gt; http://foswiki.org/Tasks/HallOfFame and http://develop.twiki.org/~twiki4/cgi-bin/view/Bugs/HallOfFame shows those 
                      stats reasonably too
<p />
Quite dramatic indeed! 
</div>
</content>
<author>
<name>gmc</name><uri>http://wikiring.comMain/</uri>
</author>
<p />
<p />
<contributor>
<name>KoenMartens</name>
</contributor>
</entry>
<entry>
<title> Development of Foswiki and TWiki &#8211; get the facts (Part 1) </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry36" />
<id>tag:wikiring.com,2009-11-17:Blog.BlogEntry36</id>
<updated>2009-11-17T12:34:21Z</updated>
<published>2009-11-17T09:55:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  It is often claimed that only a few developers moved from TWiki to Foswiki, therefore the first article will look at who are/were active core developers of both projects.<p /><style>
.oldmember{
color:#ccc;
}
.DISheadline{
background-color:#ddd;
font-weight:bold;
text-align:center;
}
.memberaction{
width:100px;
text-align:center;
}
</style>
<h2> Number of core developers </h2>
The analysis focus on core development of both projects, as this is a major indicator for the health of a software project. This is because you need a lot more knowledge and background for developing the core product than for writing an extension with a clearly defined API.
<p />
<h3> Claim </h3>
<p />
<blockquote><i>"We have healthy downloads, an active user community, and a very active support community. However, we are a smaller developer community than we used to be."</i> <br>Source: Blog post by Peter Thoeny (Twiki.net) &#8211; 11 Nov 2009</blockquote>
<p />
<h3> Fact </h3>
<p />
<table class="twikiTable" style="margin-left:3em">
<tr><th class="headline" colspan="3">Developers of TWiki and Foswiki</th></tr>
<tr><td align="center"></td><td></td><td align="center"></td></tr>
<tr><th class="headline" colspan="3">Core contributers</th></tr>
<tr><td>PeterThoeny</td><td></td><td></td></tr>
<tr><td>SopanShewale</td><td></td><td></td></tr>
<tr><td class="oldmember">CrawfordCurrie</td><td class="memberaction"></td><td>CrawfordCurrie</td></tr>
<tr><td class="oldmember">KoenMartens</td><td class="memberaction"></td><td>KoenMartens</td></tr>
<tr><td class="oldmember">MichaelDaum</td><td class="memberaction"></td><td>MichaelDaum</td></tr>
<tr><td class="oldmember">RafaelAlvarez</td><td class="memberaction"></td><td>RafaelAlvarez</td></tr>
<tr><td class="oldmember">AndreUlrich</td><td class="memberaction"></td><td>AndreUlrich</td></tr>
<tr><td class="oldmember">TravisBarker</td><td class="memberaction"></td><td>TravisBarker</td></tr>
<tr><td class="oldmember">ArthurClemens</td><td class="memberaction"></td><td>ArthurClemens</td></tr>
<tr><td class="oldmember">GilmarSantosJr</td><td class="memberaction"></td><td>GilmarSantosJr</td></tr>
<tr><td class="oldmember">LynnwoodBrown</td><td class="memberaction"></td><td>LynnwoodBrown</td></tr>
<tr><td class="oldmember">OliverKrueger</td><td class="memberaction"></td><td>OliverKrueger</td></tr>
<tr><td class="oldmember">ColasNahaboo</td><td class="memberaction"></td><td>ColasNahaboo</td></tr>
<tr><td class="oldmember">KennethLavrsen</td><td class="memberaction"></td><td>KennethLavrsen</td></tr>
<tr><td class="oldmember">MarkusUeberall</td><td class="memberaction"></td><td>MarkusUeberall</td></tr>
<tr><td class="oldmember">SvenDowideit</td><td class="memberaction"></td><td>SvenDowideit</td></tr>
<tr><td class="oldmember">AntonioTerceiro</td><td class="memberaction"></td><td>AntonioTerceiro</td></tr>
<tr><td class="oldmember">WillNorris</td><td class="memberaction"></td><td>WillNorris</td></tr>
<tr><td class="oldmember">MartinCleaver</td><td class="memberaction"></td><td>MartinCleaver</td></tr>
<tr><th class="headline" colspan="3">New to core development</th></tr>
<tr><td class="oldmember">SebastianKlus</td><td class="memberaction"></td><td>SebastianKlus</td></tr>
<tr><td class="oldmember">OlivierRaginel</td><td class="memberaction"></td><td>OlivierRaginel</td></tr>
<tr><td class="oldmember">EugenMayer</td><td class="memberaction"></td><td>EugenMayer</td></tr>
<tr><td class="oldmember">LarsEik</td><td class="memberaction"></td><td>LarsEik</td></tr>
<tr><td class="oldmember">IsaacLin</td><td class="memberaction"></td><td>IsaacLin</td></tr>
<tr><td class="oldmember">GeorgeClark</td><td class="memberaction"></td><td>GeorgeClark</td></tr>
<tr><td class="oldmember">AndrewJones</td><td class="memberaction"></td><td>AndrewJones</td></tr>
<tr><th class="headline" colspan="3">New developers</th></tr>
<tr><td></td><td class="memberaction"></td><td>SeanMcCarthy</td></tr>
<tr><td></td><td class="memberaction"></td><td>RobManson</td></tr>
<tr><td></td><td class="memberaction"></td><td>BenBeijer</td></tr>
<tr><td></td><td class="memberaction"></td><td>RaulFRodriguez</td></tr>
<tr><td></td><td class="memberaction"></td><td>MarkSchumann</td></tr>
<tr><td></td><td class="memberaction"></td><td>MichaelTempest</td></tr>
<tr><td></td><td class="memberaction"></td><td>AndrewPantyukhin</td></tr>
<tr><td></td><td class="memberaction"></td><td>DrakeDiedrich</td></tr>
<tr><td></td><td class="memberaction"></td><td>PaulHarvey</td></tr>
<tr><td class="headline">2 Core Contributers</td><td class="headline"></td><td class="headline">32 Core Contributers</td></tr>
</table>
<p />
<h3> Statement </h3>
<h4> Developer community: </h4>
Look at the list of developers contributed to the core of both projects since the commercial takeover of Twiki.net. The TWiki.org development community has dropped to almost nothing &#8211; only Peter and his employee Sopan is left. Whereby all other TWiki.org core developers moved to Foswiki.org. Together with new developers, Foswiki has almost doubled its core contributors! 
<p />
<div style="margin-left:3em">
<table cellspacing="0" id="table1" cellpadding="0" class="twikiTable" rules="rows" border="1">
	<tbody>
		<tr class="twikiTableOdd twikiTableRowdataBgSorted0 twikiTableRowdataBg0">
			<td bgcolor="#ffffff" valign="top" class="twikiTableCol0 twikiFirstCol"> &nbsp; </td>
			<th bgcolor="#687684" colspan="2" valign="top" class="twikiTableCol1"> <font color="#ffffff">Number of core contributors</font> </th>
		</tr>
		<tr class="twikiTableEven twikiTableRowdataBgSorted1 twikiTableRowdataBg1">
			<td bgcolor="#edf4f9" valign="top" class="twikiTableCol0 twikiFirstCol"> &nbsp; </td>
			<th bgcolor="#687684" valign="top" class="twikiTableCol1"> <font color="#ffffff">before commercial takeover<br>of TWiki.org (2008-10-27)</font> </th>
			<th bgcolor="#687684" valign="top" class="twikiTableCol2 twikiLastCol"> <font color="#ffffff">one year later (2009-10-27)</font> </th>
		</tr>
		<tr class="twikiTableOdd twikiTableRowdataBgSorted0 twikiTableRowdataBg0">
			<th bgcolor="#687684" valign="top" class="twikiTableCol0 twikiFirstCol"> <font color="#ffffff">TWiki.org</font> </th>
			<td bgcolor="#ffffff" align="center" valign="top" class="twikiTableCol1"> <b>18</b> </td>
			<td bgcolor="#ffffff" align="center" valign="top" class="twikiTableCol2 twikiLastCol"> <b>2</b> </td>
		</tr>
		<tr class="twikiTableEven twikiTableRowdataBgSorted1 twikiTableRowdataBg1">
			<th bgcolor="#687684" valign="top" class="twikiTableCol0 twikiFirstCol twikiLast"> <font color="#ffffff">Foswiki.org</font> </th>
			<td bgcolor="#edf4f9" align="center" valign="top" class="twikiTableCol1 twikiLast"> <b>n/a</b> </td>
			<td bgcolor="#edf4f9" align="center" valign="top" class="twikiTableCol2 twikiLastCol twikiLast"> <b>32</b> </td>
		</tr>
	</tbody></table>
</div>
<p />
<h3> Healthy Downloads: </h3>
Yes, lots of users still download the old TWiki code as they don&#180;t know about Foswiki and its progress. Our marketing was very bad as we are better in concentrating on improvements than in talk about it. Sadly even most of our old TWiki user community don&#180;t know about Foswiki and may wonder why there is no progress on TWiki.org.
<p />
<h3> Sources </h3>
<p />
As the analysis is based on open source, you can easily check the correctness of the data by yourself. For the first analyzation I used the following sources: <ul>
<li> TWiki.org SVN trunk/core
</li> <li> Foswiki.org SVN trunk/core
</li></ul> 
<p />
Don't miss the rest of the series:  <ul>
<li> Introduction <p /><b>Tags</b>: community, foswiki, opensource, twiki  
</li></ul> 
</div>
</content>
<author>
<name>AndreUlrich</name><uri>http://wikiring.comMain/AndreUlrich</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="community" label="community" />
<category term="foswiki" label="foswiki" />
<category term="opensource" label="opensource" />
<category term="twiki" label="twiki" />
<contributor>
<name>AndreUlrich</name>
</contributor>
</entry>
<entry>
<title> Development of Foswiki and TWiki &#8211; get the facts (Intro) </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry35" />
<id>tag:wikiring.com,2009-11-17:Blog.BlogEntry35</id>
<updated>2009-11-17T12:08:40Z</updated>
<published>2009-11-14T16:57:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  One year after the commercial take over of TWiki.org its time look how TWiki and its successor Foswiki performed. A small blog series will cover facts and give you insight into the development status of both projects.<p />
<h2> Intro </h2>
<p />
As a Wiki consultancy we regulary got asked about different projects and how good they are. In case of TWiki.org and Foswiki.org customers are very irritated and cannot see the difference. The fact that Foswiki is based on TWiki, but got developed much further within the last year is not obvious to most users. Contrary to the fact that Foswiki is the superior product, TWiki still has the better recognition marketing wise.
<p />
In order to help our customers getting an insight into the development of both projects I will do an analysis and compile the results in an understandable way. The results will be published in a small series of articles.
<p />
The first analysis will be based on core development of both projects, as this is a major indicator for the health of a software project. This is because you need a lot more knowledge and background for developing the core product than for writing an extension with a clearly defined API.
<p />
As the analysis will be based on open source, you can easily check the correctness of the data by yourself. For the first analyzation I will use the following sources: <ul>
<li> TWiki.org SVN trunk/core
</li> <li> Foswiki.org SVN trunk/core
</li></ul> 
<p />
Stay tuned and see how Foswiki and TWiki developed over the past year.
<p />
Continue reading at: <ul>
<li> Development of Foswiki and TWiki - get the facts (Part 1) <p /><b>Tags</b>: community, fork, foswiki, opensource, twiki  
</li></ul> 
</div>
</content>
<author>
<name>AndreUlrich</name><uri>http://wikiring.comMain/AndreUlrich</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="community" label="community" />
<category term="fork" label="fork" />
<category term="foswiki" label="foswiki" />
<category term="opensource" label="opensource" />
<category term="twiki" label="twiki" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> Foswiki-1.0.7 released </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry34" />
<id>tag:wikiring.com,2009-09-21:Blog.BlogEntry34</id>
<updated>2009-09-21T11:18:05Z</updated>
<published>2009-09-21T10:25:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  The amount of improvements is impressive. The bug fixing carousel passed another lap and pace increases noticeably as new high potential contributors have joined the Foswiki core team. This is easily the best release we ever had. 
<p />
<div id="" class="imageFloat imageFloat_right " style=""></div><p />And this is not all. The Fosswiki Association e.V. has just recently been founded formally. The first constitutive general assembly will take place within the next two months to ratify its articles, vote for the board and convert virtual beers into physical ones.
Maybe it will take place around Nov 20. This would be a great date as we could celebrate Foswiki's first anniversary having decided on the new project's name one year before.
<p />
<br clear="all" />
Read the full release notes and go grab it here. <p /><b>Tags</b>: community, foswiki, opensource, release  
</div>
</content>
<author>
<name>MichaelDaum</name><uri>http://wikiring.comMain/MichaelDaum</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="community" label="community" />
<category term="foswiki" label="foswiki" />
<category term="opensource" label="opensource" />
<category term="release" label="release" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> Foswiki and TWiki reviews on Sourceforge </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogPage1" />
<id>tag:wikiring.com,2009-11-03:Blog.BlogPage1</id>
<updated>2009-11-03T10:19:47Z</updated>
<published>2009-09-21T00:00:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  <p /> 
</div>
</content>
<author>
<name>MichaelDaum</name><uri>http://wikiring.comMain/MichaelDaum</uri>
</author>
<p />
<p />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> Foswiki.org running on a new server </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry33" />
<id>tag:wikiring.com,2009-08-24:Blog.BlogEntry33</id>
<updated>2009-08-24T10:13:38Z</updated>
<published>2009-08-24T09:43:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  <div id="" class="imageFloat imageFloat_right " style=""></div> 
We are all quite excited about the recent and upcoming changes on the Foswiki project. Now Koen Martens has set up a new hardware for the Foswiki main server and migrated the site. Big big thanks to Koen 
and his company Sonologic hosting it and all people that donated money to buy the new iron. <p />Here are some pictures:
<p />
<div class="igp"><div class="igpThumbNails"><table class="igpThumbNailsTable"><tr>
<td width="50%" class="igpThumbNail"></td>
<td width="50%" class="igpThumbNail"></td>
</tr>
<td width="50%" class="igpThumbNail"></td>
<td width="50%" class="igpThumbNail"></td>
</tr>
</tr>
</table></div>
</div>
 <p /><b>Tags</b>: community, foswiki, hardware, server  
</div>
</content>
<author>
<name>MichaelDaum</name><uri>http://wikiring.comMain/MichaelDaum</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="Sponsorship" label="Sponsorship" />
<category term="community" label="community" />
<category term="foswiki" label="foswiki" />
<category term="hardware" label="hardware" />
<category term="server" label="server" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> ClearQuest interface for Foswiki (and TWiki) </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry32" />
<id>tag:wikiring.com,2009-06-04:Blog.BlogEntry32</id>
<updated>2009-06-04T12:12:18Z</updated>
<published>2009-06-04T11:14:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  Is there any interest in such an interface?<p />For the last couple of years, C-dot Consultants has been working with a client to develop a plugin that interfaces to the well known (and quite excellent) IBM ClearQuest bug tracking and workflow management system. This interface allows Wiki users to make queries into the ClearQuest database, and present the results of those queries in tabular and graphical form. The interface was developed for the client's internal use, and has been heavily used by a large number of people for quite some time. It has proven to be very reliable. It occurred to us that it might be of some use to other enterprises who use ClearQuest. If you are interested, please contact me. <p /><b>Tags</b>: clearquest, foswiki, ibm, integration, plugin, tracking, wikiapps  
</div>
</content>
<author>
<name>CrawfordCurrie</name><uri>http://wikiring.comMain/CrawfordCurrie</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="clearquest" label="clearquest" />
<category term="foswiki" label="foswiki" />
<category term="ibm" label="ibm" />
<category term="integration" label="integration" />
<category term="plugin" label="plugin" />
<category term="tracking" label="tracking" />
<category term="wikiapps" label="wikiapps" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> New WebDAV plugin for Foswiki (and TWiki) </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry31" />
<id>tag:wikiring.com,2009-05-11:Blog.BlogEntry31</id>
<updated>2009-05-11T10:19:29Z</updated>
<published>2009-05-08T11:04:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  The new WebDAV plugin provides direct access to files stored within the Wiki for desktop applications such as Word, Excel and PowerPoint.
<p />KontextWork and C-Dot Consultants have worked together to create the WebDAVContrib, a brand new Web DAV implementation for Foswiki and Apache 2.
<p />
Web DAV (Web-based Distributed Authoring and Versioning) is a set of extensions to the Hypertext Transfer Protocol (HTTP) that allows users to edit and manage files collaboratively on remote World Wide Web servers.
<p />
The new Web DAV module maps Foswiki content &#8211; webs, topics and attachments &#8211; to a directory structure, and exports it using the Web DAV protocol. It allows users to work with Foswiki content using the tools they are most familiar with, without compromising on Foswiki features. For example attachments can be opened, manipulated and saved right within desktop applications such as Microsoft Office, Open Office, Adobe Photoshop (and many more). Wiki webs can be opened in file browsers such as Windows Explorer, and wiki topics can be edited using many different text editors.
<p />
The new plugin is a completely new Perl implementation of Web DAV, written specifically for Apache 2, and has been extensively tested using the standard litmus tests. It works over HTTP and secure HTTPS, fully respects Foswiki permissions, and can be used with all standard Apache authentication methods. A version for TWiki is also available.
<p />
The WebDAVContrib is currently undergoing final pre-release testing. Contact Andre Ulrich for availability and pricing. <p /><b>Tags</b>: documentmanagement, foswiki, integration, webdav  
</div>
</content>
<author>
<name>CrawfordCurrie, AndreUlrich</name><uri>http://wikiring.comMain/CrawfordCurrie, AndreUlrich</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="documentmanagement" label="documentmanagement" />
<category term="foswiki" label="foswiki" />
<category term="integration" label="integration" />
<category term="webdav" label="webdav" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> Improve PublishContrib </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry30" />
<id>tag:wikiring.com,2009-05-08:Blog.BlogEntry30</id>
<updated>2009-05-08T11:46:57Z</updated>
<published>2009-05-08T09:22:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  I've been thinking about doing some more work on the PublishContrib, to make it more useful for people who want controlled publishing processes, for example those who publish process manuals.<p />Here are some of the requirements I've been thinking about:    <ol>
<li> More flexible specification of publish sets, including publishing groups of webs
</li> <li> Record keeping (who published what, when, and what they published) 
</li></ol> 
<p />
Michael Daum has related, but slightly different requirements. 
Michael publishes by copying content to a static web where it is picked up by a different CMS. So he has a common requirement to specify publish sets, but has additional requirements such as unpublishing, and automation of approval processes. Anyway, the upshot of the conversation was that we should have some common way of specifying "publish sets". The current method &#8211; regexes in the publish topic &#8211; is so crude as to be laughable. The obvious approach to specifying publish sets would be to use WebNotify, but as Michael points out that's far too geeky. Another approach would be to think about "specification" and focus on the UI, perhaps build on the SubScribePlugin. Another approach would be to use a wiki app to gather published content into one place, similar to the genwebnotify.pl approach taken to generate the notification mails from the Foswiki:Tasks web. Record keeping means maintaining unforgeable records of a publishing event. That means stamping the published docs with publishing information, including the history in the published data, and publishing to publish-event specific targets (e.g. directories named by the current date). 
<p />
It would be interesting to hear what other ideas people have had. <p /><b>Tags</b>: automation, cms, content, foswiki, plugin, publishing, wikiapps, workflow  
</div>
</content>
<author>
<name>CrawfordCurrie</name><uri>http://wikiring.comMain/CrawfordCurrie</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="Sponsorship" label="Sponsorship" />
<category term="automation" label="automation" />
<category term="cms" label="cms" />
<category term="content" label="content" />
<category term="foswiki" label="foswiki" />
<category term="plugin" label="plugin" />
<category term="publishing" label="publishing" />
<category term="wikiapps" label="wikiapps" />
<category term="workflow" label="workflow" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> MichaelDaum replies on "Hostile takeover of Open Source Project TWiki"</title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogComment8" />
<id>tag:wikiring.com,2008-11-21:Blog.BlogComment8</id>
<updated>2008-11-21T11:30:25Z</updated>
<published>2008-11-21T11:30:25Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">    <p />Aron, thanks for your warm words about TWiki. We still appreciate it, as we are all still deeply linked to our roots. These are roots that we left behind now as we build up the TWiki successor called <strong>Foswiki</strong> right now.
<p />
Thanks also for offering that we all are welcome to come over to DekiWiki. I really am a fan of DekiWiki and highly appreciate the gr8 work MindTouch does to produce such a high quality product.
<p />
However, TWiki somewhat became our second nature, so most, if not all developers stay on course doing whatever we always did, just faster and not threatened by Peter's trademark. 
<p />
I only wished he would not see a need to turn around and use
the trademark against the core of TWiki, its own community. <em>That</em> was not for the best of the project for sure. Peter obviously did not assess the situation clear enough coming to the conclusions and actions as outlined in the above posting. 
<p />
Most probably, this is not for the best of TWiki.net either, as it might have become "radioactive" for more venture investments. They might milk the open sources for some time but the product already starts to rotten with TWiki.net not able to execute.
<p />
Not so Foswiki. The number of people that take part is just amazing as proven by pure number of submissions in the recent surveys to find the new brand name.
<p />
TWiki was in the transition from one governance model with a sole dictator to another one with an elected board of directors and an association to promote the project and take care of legal matters. This process failed and Peter installed an even more restrictive dictatorship by ruling the project from within his new company called TWiki.net. 
<p />
Frankly, we have seen this coming and we tried to keep the project true Open Source. From TWiki's perspective we failed. From Foswiki's perspective we now work unleashed from the curse of a bad governance structure. 
<p />
Just have a look at http://foswiki.org. This new old community is working like crazy to get the new release out. And we will do it. It will be a much better wiki than TWiki ever was. All of the roadmap for TWiki-5 will be executed on Foswiki. The Foswiki Association, the formal body for this project, will come to live very soon. 
<p />
So basically, we just get what we want. It only needs a bit more work. All these efforts are more than worth it as the new site already shows. And we just started.
This is only weeks ago and look at it&#8230;
<p />
Note, that these are the <em>same</em> people that have formerly been known as the TWiki community. Just imagine how badly TWiki was managed looking at the unleashed energy and abilities that people can now unfold on the new project. 
<p />
And we are not done with it. It's renovation &amp; innovation time. 
</div>
</content>
<author>
<name>MichaelDaum</name><uri>http://wikiring.comMain/</uri>
</author>
<p />
<p />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> MartinSeibert replies on "Hostile takeover of Open Source Project TWiki"</title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogComment6" />
<id>tag:wikiring.com,2008-11-21:Blog.BlogComment6</id>
<updated>2008-11-21T11:39:55Z</updated>
<published>2008-11-21T10:05:04Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml"> <b>I did not see any Core developers leave!</b>   <p />Hi Aaron,
<p />
I am sorry. But I have been involved in TWiki for quite some time now. I did see all active developers to switch from TWiki to Foswiki (formerly NextWiki). I believe that your post is merely trying to attract our developers.
<p />
Please name any developer who changed. That would be really interesting. 
<p />
</div>
</content>
<author>
<name>MartinSeibert</name><uri>http://wikiring.comMain/</uri>
</author>
<p />
<p />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> Birthday Nr. 0 for Foswiki, the Free and Open Source Wiki </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry29" />
<id>tag:wikiring.com,2008-11-19:Blog.BlogEntry29</id>
<updated>2008-11-19T13:35:53Z</updated>
<published>2008-11-19T10:34:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  The community formerly known as TWiki.org has entered the home stretch to strip off its burdens of the past.<p />On November 18th, the community has voted for a new name for the project that recently forked off TWiki.org and which hit the front pages recently under the working title NextWiki. So welcome the new old player.
<p />
<div style="text-align:center;font-weight:bold">
Happy birthday to Foswiki.
</div>
<p />
This is the start of a great new brand that is about to evolve at foswiki.org
The tagline of the project is 
<p />
<cite>
The Free and Open Source Wiki
</cite>
<p />
which obviously is reprocessing the trauma of the Hostile takeover of the Open Source Project TWiki
but also targets at its best competitors in the market segment, which are <em>not</em> Open Source.
<p />
It remains to be seen if this new project will be able to catch up with the field, as it
was dropping behind recently, according to the Magic Quadrant for Social Software, 2008. In this paper, Gartner categorizes TWiki as a niche player only whereas it was on par with Socialtext in the Magic Quadrant for Team Collaboration and Social Software, 2007. That might be the result of the long paralysis caused by the governace crisis over the recent years on the TWiki project, which finally culminated in the recent fork 3 weeks ago.
<p />
This paralysis obviously has been overcome as the new project Foswiki shows an impressive amount of activities by all members. Long-time contributors, that went on strike as the trademark issues on TWiki started to manifest, now show an outburst of activities, committing and impressive stream of updates and bugfixes to the new platform. Surely, a vast amount of work is related to rebranding the software by pinching the string "TWiki" out of every place. 
<p />
The questionnaire on finding the new brand name for the project had an impressive 100 submissions spot on just within a few days. There was a prior survey among the community to find out about its likings for a new name that had even more submissions. Compare this with just a hand full of members that dared to voice up on the old TWiki project during all of its quarrels. That's over now and people obviously have fun again to volunteer. 
<p />
There was already very positive feedback on the cheers-and-donate mailing list coming from outside. One of which says:
<p />
<cite>
The new website is very appealing and the first impression is not "bitter" but
"better", so keep that up! A big cheer for everyone involved in this
initiative!!
</cite>
<p />
Still, according to the criteria for a product to be listed on the Magic Quadrant study by Gartner, it seems quite probable that TWiki will drop out on 2009, as it lost its community which created the product before. Regarding its Open Source process, TWiki can be considered dead and with it goes its core engine. Foswiki, on the other side, now continues work on the engine with a lot of verve, but won't show up easily on a forthcoming 2009 Magic Quadrant as it still has to build up its new brand and user base. However, as most authors of extensions have moved to Foswiki and now maintain their work on the new platform, moving from TWiki to Foswiki is a natural choice to keep up with upstream updates and improvements.
<p />
TWIKI.NET, the new owner of TWiki.org, won't rest and just watch. They are actively working on interesting applications to address intranet needs build on top of the TWiki engine. The fact that
this software can be used to build applications like that is great in its own and TWIKI.NET does score in that field as far as can be seen from outside. But of how much value are such applications in the long run, when the platform they are build on erodes? TWIKI.NET is funded by venture capital paying a bunch of developers in Asia and elsewhere. Time will show if that business plan pays off to cope with all the open road works that they have to face all alone now. Good luck from WikiRing.
 <p /><b>Tags</b>: community, fork, foswiki, opensource, twiki  
</div>
</content>
<author>
<name>MichaelDaum</name><uri>http://wikiring.comMain/MichaelDaum</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="community" label="community" />
<category term="fork" label="fork" />
<category term="foswiki" label="foswiki" />
<category term="opensource" label="opensource" />
<category term="twiki" label="twiki" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> JohnSmith replies on "Hostile takeover of Open Source Project TWiki"</title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogComment5" />
<id>tag:wikiring.com,2008-10-30:Blog.BlogComment5</id>
<updated>2008-10-30T18:21:30Z</updated>
<published>2008-10-30T18:21:30Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">    <p />Looks like yet another captain has thrown it's Titanic onto iceberg. We all remember Joomla vs Mambo clashing. Now, who cares of Mambo if there is Joomla? Seems to be quite similar case. I hope you will have same success as Jumla did once.. 
</div>
</content>
<author>
<name>JohnSmith</name><uri>http://wikiring.comMain/</uri>
</author>
<p />
<p />
<contributor>
<name>JohnSmith</name>
</contributor>
</entry>
<entry>
<title> Aaron Fulkerson replies on "Hostile takeover of Open Source Project TWiki"</title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogComment4" />
<id>tag:wikiring.com,2008-10-30:Blog.BlogComment4</id>
<updated>2008-10-30T00:36:34Z</updated>
<published>2008-10-30T00:36:34Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">    <p />Hi all. I'm one of the founders of www.MindTouch.com. We make MindTouch Deki (sometimes called DekiWiki). I've been following the coming storm at TWiki for a little bit. Primarily because I've become aware of some core TWiki developers switching their development projects to MindTouch Deki. Secondarily because MindTouch is also open source and we develop a product that loosely competes with TWiki. In fear of stirring up more s**t I want to chime in here. 
<p />
First let me say I do not know all the details of this mess, but I've met Peter and I think he's a stand up guy who is undoubtedly trying to do what he thinks is best for the TWiki project. Moreover, I think TWiki was way ahead of others players in this space for a long time. So, kudos to all of you.
<p />
Trademark aside, who owns the copyright for the Twiki codebase? Does any one entity? In open source, trademark is nice, but copyright is king.
<p />
I'm writing because I wanted to make two points. 
<p />
First. Building a business on an open source project is a balancing act. On one side you're trying to build a sustainable business by creating revenue through customer acquisition. On the other side you have a desire to do what's best for the community of users (distinct from customers), developers, system integrators and VARs. If you're not careful you can put these groups at odds and look like an asshole or even worse, really hurt your business. This balancing act is especially challenging when you're building on a project like TWiki that has been around <em>forever</em> and has had a significant amount, or perhaps even the majority, of development from the community. I believe the easiest way to find balance is to have an open source core that the company(ies) can add value to in the form of development and services or even sell commercial layers of additional functionality on top of this. In this way the devs and users win and also the company(ies) are able to create clear differentiation that helps in the customer acquisition effort. You don't have to look far to see that these are the most successful open source projects and businesses. Apache Web Server is an example of this. So is SugarCRM. In both cases you have an open core that others can build and sell additional value on top of, be it open source, closed source or services.
<p />
Second. As previously mentioned there have been many TWiki developers that have migrated to development on MindTouch Deki. I encourage you to take a look at this project and product. It's modern architecture and high quality user experience is being cited as a reason for the switch. http://mindtouch.com/technology is a good resource to learn more about the architecture, http://mindtouch.com/demo provides some demo vids of the platform in action and you may download the FOSS version and source code at the developer community: http://wiki.developer.mindtouch.com
<p />
I want to reiterate that Peter and the guys at TWiki.net are surely trying to do what they think is best for the project as a whole. In every case it is true that what is best for the project is also best for the business. And vice-versa. Although sometimes it takes a misstep to realize this. I think it's interesting to juxtapose Acquia/Drupal with what's going on here with TWiki.org/.net. Being on the outside, it's easy to see what was done well and what was done poorly by these two entities. 
<p />
Best of luck gang and I hope you'll take a look at MindTouch.    
</div>
</content>
<author>
<name>Aaron Fulkerson</name><uri>http://wikiring.comMain/</uri>
</author>
<p />
<p />
<contributor>
<name>AaronFulkerson</name>
</contributor>
</entry>
<entry>
<title> MichaelDaum replies on "Hostile takeover of Open Source Project TWiki"</title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogComment3" />
<id>tag:wikiring.com,2008-10-29:Blog.BlogComment3</id>
<updated>2008-10-29T18:58:40Z</updated>
<published>2008-10-29T18:58:40Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml"> <b>Slashdotted</b>   <p />Lots of comments on slashdot. 
</div>
</content>
<author>
<name>MichaelDaum</name><uri>http://wikiring.comMain/</uri>
</author>
<p />
<p />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> Hostile takeover of Open Source Project TWiki </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry28" />
<id>tag:wikiring.com,2008-10-29:Blog.BlogEntry28</id>
<updated>2008-10-29T13:24:42Z</updated>
<published>2008-10-29T10:54:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  Yesterday, 2008-10-27: 21:00 GMT, just a minute before the regular TWiki release meeting, the company TWIKI.NET announced unilaterally that the best for the TWiki.org project would be for them to take over governance. With it comes a complete lock down of the community site. From that minute on, all long-time contributors have lost access to their code. Counter-reaction: the community has left the building, leaving TWIKI.NET without a contributing community. Question: is it a sensible move for a venture capital firm that depends on a healthy Open Source community to lock it out? <p /><div id="" class="imageFloat imageFloat_right " style=""></div>
Access to the site
is only granted if contributors agree to a set of newly installed terms and conditions dictated by TWIKI.NET, a company founded by Peter Thoeny 12 months ago. His power to do so grows out of two sources: (a) he is the sole owner of the trademark on TWiki and (b) he is sponsoring the server hardware and thus had root access.
<p />
And now he has triggered the trademark gun and fired the TWiki community. He even repeatedly threatened people on the #twiki IRC channel that "[he has] been advised by one of [his] investors, Wilson Sonsini Goodrich and Rosati,  that [they] need to protect [their] trademark". Clearly, their VC people have no picture of the situation other than their own return of investment. Sure, protecting a registered trademark is what it is all about. But threatening the community that has been working on TWiki on a volunteer basis for the recent 10 years that way is a bit strong. Too strong for the TWiki community.
<p />
If there was ever any hope to re-establish a relationship of trust and faith to create a win/win situation by combining community &amp; commerce, this is totally gone now. Thoeny installed himself as BDFL (Benevolvent Dictator for Life) again, despite being rejected by a community vote during the TWiki Summit in Berlin last month.
<p />
During the TWiki Summit in Berlin 4+5 September 2008, it became clear that Thoeny has sold part of his trademark rights to his venture capital funded company. Part of that deal was that while he remains ownership on the trademark itself, TWIKI.NET gained the sole right to exploit the brand on a commercial basis. This created a completely new situation for the Open Source project and all of its already existing commercial eco-system. As a consequence, TWIKI.NET was asked to grant a perpetual license to the community to secure the legal situation for contributors and commercial stakeholders, a license that would only have formalized the way TWiki has been running for more than 10 years with Thoeny promising to "take care of the brand".
<p />
As faith in him as a leader diminished over the years, and the foreboding of a trademark problem increased, the community asked Thoeny to write down the rights he has granted orally before. Which he didn't. Instead he pulled the trademark trigger in a move he calls "relaunching the project" to "weed out" the good and the bad. Trust in Thoeny as a leader diminished last but not least when his role as a community leader became more and more mixed up with his interests as a CTO of TWIKI.NET, up to the point where he obviously showed more interest to cement a genuine marketing advantage for TWIKI.NET. 
<p />
The rise of his newly created company continually eroded willingness to contribute to TWiki as an Open Source project. People were more and more irritated by the changed rules of the game. The community has been watching the actions of TWIKI.NET with a lot of interest, in the hope that they would add significant value to this very successful project. Unfortunately, they took an approach of recasting the success of the product, created with years of volunteer work, as their own success. 
<p />
That's where Open Source shows its ugliest face. And there's definitely no beauty in this shock therapy, even though Tom Barton, CEO of TWIKI.NET says: "the beautiful thing about open source is you don't need to recognize the authority of TWiki.net". What an irony to close another very sad chapter. The last one for TWiki.org as we knew it before.
<p />
The appearance of TWIKI.NET on the scene forced a governance crisis TWiki was not able to overcome, despite the good progress that was made up to a couple of hours before. On the TWiki Summit in Berlin last month, a democratically elected Interim Board of Directors was founded whose sole agenda was to negotiate the conditions under which this governance crisis could have been overcome. 
<p />
The plan was to create a TWiki Association consisting of a Board of Directors and a General Assembly following the example of KDE e.V. The board itself would have created so called Task Teams that manage the operational part of the project to a finer granularity.
<p />
The members of the Interim Board of Directors were in the process of creating the Articles of Association and were prepared for the next logical move in an ever growing project, organizing it similarly to other projects in the Open Source business. This formal body would also have been an entry path for sponsors and other organizations willing to partner with TWiki as a project. No such thing was available before. The only way outside parties could have made donations was to give them directly to Thoeny and thereby TWIKI.NET. 
<p />
This was the case when Sun donated server hardware to power the TWiki.org community site. Sun sponsored TWiki as an Open Source project, not TWIKI.NET. However, there was no entity other than Thoeny and TWIKI.NET to handle these opportunities and resources. It now is clear that the access to these server resource has been used against the TWiki community itself by locking it out.
<p />
The democratically elected Interim Board of Directors of TWiki has been displaced by the trademark holder of TWiki as a final chord on the governance crisis. Now, Thoeny is sending around emails to high profile contributors individually to invite them to come back subordinate to the governance of TWIKI.NET. He obviously seems to be in hope that people will do so once the situation has settled. Quite far-fetched and not very likely to happen. Those same contributors who implemented the features he is praising aloud as the shiny new TWiki, are far too displeased by his hostile behavior to be willing to go back to business as usual.
<p />
TWIKI.NET is striving to repaint their move as a "new opportunity". What they don't see is that they have put their own business case into severe danger. They just lost the horse power for a product that they were selling. They have been signaling to the community that they don't have the manpower for certain developments and were seeking for help, even willing to pay work for hire. Another error. Adding money as an incentive to Open Source is changing the game completely. Before, people volunteered as part of an act of free speech. Add money to it and nobody will work for free anymore. This poisoned the dynamics.
<p />
The current situation is that all core developers have left the ship and joined a new undertaking with the working title NextWiki. This is a fork based on the current code in TWiki that will soon be released under a new name. The goals of NextWiki are clear. Basically, the plan is to found an Association as a formal body for the project, including the reorganization of its governance down to all operational questions, as was in progress for the TWiki project.
<p />
The result will be a much strengthened new player, much more agile as it just got rid of the reason for TWiki's ongoing paralysis. 
<p />
There remains a message for TWiki's users: no worries, we continue working, faster and more productive than ever before, embedded in a volunteer-friendly environment. Sure, this fork now introduces a new choice that was not there before. Well, it <em>was</em> there before and it was introduced by TWIKI.NET, not those guys that "asked for a fork". TWiki users already had the choice between TWIKI.NET's product (a rebranded version of an old TWiki release, packaged as a VMware image), or Open Source TWiki, most recent stable version. This choice more or less remains available with the difference that you will get the real thing from a new site, reworked to be real Open Source, backed up by a large and highly motivated community as a guarantor for continuity and innovation. 
<p />
<p />
<p />
 <p /><b>Tags</b>: community, fork, opensource, twiki  
</div>
</content>
<author>
<name>MichaelDaum</name><uri>http://wikiring.comMain/MichaelDaum</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="fork" label="fork" />
<category term="twiki" label="twiki" />
<category term="opensource" label="opensource" />
<category term="community" label="community" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> PerlPlugin </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry25" />
<id>tag:wikiring.com,2009-05-08:Blog.BlogEntry25</id>
<updated>2009-05-08T11:39:10Z</updated>
<published>2008-08-02T13:44:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  A new plugin uses the Safe module in Perl to constrain perl scripts in TWiki topics so they are safe to execute on your server.<p />We recently developed a TWiki plugin to support execution of Perl scripts that are written in TWiki topics. The scripts are executed on the server, and of course that means we have to do everything possible to ensure those scripts don't open security holes.For years Perl has had the Safe module, a clever package that provides a tightly constrained execution environment for Perl <code>eval</code> statements. Perl compiles all its code to a rich set of high level opcodes, which are then run on a virtual machine. By limiting the set of opcodes that are allowed to be run in the container, the Safe module can be used to create a very secure execution environment.For example, most people would consider the perl 'backtick' operator to be very dangerous, as it allows the caller arbitrary access to the shell. Backtick has a corresponding Perl opcode &#8211; called <code>backtick</code> &#8211; and to disable it, all we have to do is to remove it from the set of legal opcodes. The Perl developers have even gone so far as to classify the operators according to the usual safety concerns that a caller may have, making it relatively easy to decide which to allow, and which to exclude.Of course there's more to safety than that. We also have to be sure that the code being executed only has access to the namespaces we want it to have access to. The default condition for scripts run in a safe container is that they can only access the namespace of the container. We have to explicitly grant the container access to other namespaces when we create it.Of course there are potential risks with allowing any sort of script execution on your server, but in the case of a web server behind a corporate firewall, those risks are relatively small, and the 'Safe' module helps to make sure that such scripts are well controlled.The new TWiki plugin, called the PerlPlugin, is released under the GPL and is available to all WikiRing consultants for deployment on client sites. <p /><b>Tags</b>: perl, plugin, security  
</div>
</content>
<author>
<name>CrawfordCurrie</name><uri>http://wikiring.comMain/CrawfordCurrie</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="perl" label="perl" />
<category term="plugin" label="plugin" />
<category term="security" label="security" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
<entry>
<title> GordonMcGregor replies on "STC Spring Event highlights Technical Communicator's issues"</title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogComment2" />
<id>tag:wikiring.com,2008-04-28:Blog.BlogComment2</id>
<updated>2008-04-28T15:22:24Z</updated>
<published>2008-04-28T15:22:24Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml"> <b>only a year later</b>   <p />but it was worth coming here just to see that 'The Machine is Us/ing Us' video. For once this 'web 2.0' thing actually made sense about what is different. 
</div>
</content>
<author>
<name>GordonMcGregor</name><uri>http://wikiring.comMain/</uri>
</author>
<p />
<p />
<contributor>
<name>GordonMcGregor</name>
</contributor>
</entry>
<entry>
<title> Moving from Jot Spot to TWiki </title>
<link rel="alternate" type="text/html" href="http://wikiring.com/Blog/BlogEntry24" />
<id>tag:wikiring.com,2009-05-08:Blog.BlogEntry24</id>
<updated>2009-05-08T11:39:20Z</updated>
<published>2008-03-28T11:57:00Z</published>
<content type="xhtml">
<div xmlns="http://www.w3.org/1999/xhtml">  How to convert Jot Spot data to TWiki<p />With the recent announcement  about the new Google Sites application, a number of former Jot Spot customers have decided to migrate to TWiki. WikiRing partner C-Dot Consultants has been engaged to help, and this post describes our experiences.
<p />
Jot Spot stores topic data in an XML database. Within that database, actual topic data is stored as "decorated HTML"; the basic topic content is HTML, within which Jot applications are embedded using Jot Spot's proprietary script, which uses XML tags.
<p />
Because of some fairly fundamental architectural differences between Jot Spot and TWiki it's not simple to automate the conversion of Jot Spot <em>applications</em> to TWiki. Fortunately our clients have not invested heavily in developing Jot applications, but have instead chosen to use the applications that Jot Spot provide by default. So the focus of our work has been to: <ol>
<li> Convert existing Jot Spot topics to TWiki, with minimal formatting loss
</li> <li> Map a subset of Jot applications (most notably the Bug Reporter) to TWiki
</li></ol> 
<p />
Fortunately we were able to secure an XML dump of the Jot Spot database. This has alllowed us to perform the conversion without relying on the patchy availability of the Jot Spot site. Conversion of Jot topics has been achieved by leveraging a couple of existing technologies: <ul>
<li> The SAX XML parser from CPAN
</li> <li> The open-source HTML to TML convertor we wrote for WYSIWYG editor integration into TWiki
</li></ul> 
<p />
SAX allows us to parse the Jot XML, pick out the form fields, and identify the subset of the topics suitable for passing on to the HTML to TML convertor. The HTML to TML convertor is already a proven technology, used every day with the Tiny MCE integration in TWiki, so it is robust and minimises formatting loss.
<p />
On the receiving side, we have customised the publicly available TWiki:Plugins.BugsContrib to support the data fields from the reporter in Jot Spot. We have had to develop a number of new reporting screens, something which has been made much simpler by the use of the <code>type="query"</code> search we contributed to TWiki 4.2.
<p />
It's cheering to note how similar the structure of a Jot Spot topic is to a TWiki topic. I guess you could call it convergent evolution! <p /><b>Tags</b>: conversion, google, jotspot  
</div>
</content>
<author>
<name>CrawfordCurrie</name><uri>http://wikiring.comMain/CrawfordCurrie</uri>
</author>
<category term="WikiRing" label="WikiRing" />
<category term="conversion" label="conversion" />
<category term="google" label="google" />
<category term="jotspot" label="jotspot" />
<contributor>
<name>MichaelDaum</name>
</contributor>
</entry>
 </feed>