Welcome to TiddlyWiki created by Jeremy Ruston, Copyright © 2007 UnaMesa Association
Sadly, we sometimes have to wave goodbye to one of our Osmonauts as they move on to new pastures. Happily we get to keep in touch and love hearing about their exploits out in the big wide world.
!~Osmo-Alumni
|[img[James|images/photo_james.jpg]]|''James Shi''[[curiousjames.wordpress.com|http://curiousjames.wordpress.com]][[flickr.com/photos/jamesshi/|http://www.flickr.com/photos/jamesshi/]][[twitter.com/dr1ft3r|http://twitter.com/dr1ft3r]]|
|[img[Phil W|images/photo_philw.jpg]]|''Phil Whitehouse'' [[philwhitehouse.blogspot.com|http://philwhitehouse.blogspot.com]] [[flickr.com/photos/philliecasablanca|http://flickr.com/photos/philliecasablanca/]][[twitter.com/casablanca|http://twitter.com/casablanca/]] |
As a teenager, while his friends played with games consoles, Andrew got his kicks from a salvaged [[PDP-11 minicomputer|http://en.wikipedia.org/wiki/Programmed_Data_Processor]]. He has an unhealthy obsession with devices, operating systems and computer networks, and was introduced to open source via Linux back in 1995.
At BT, Andrew has been responsible for setting up Design's Open Source Focus Group, and he is a strong advocate of open computing platforms.
If you're popping in to the office, Andrew will have a cup of tea with milk and sugar and a chocolate brownie.
[[carrierdetect.com|http://carrierdetect.com]]
[[flickr.com/photos/carrierdetect|http://flickr.com/photos/carrierdetect/]]
[[twitter.com/9600|http://twitter.com/9600/]]
31st October 2007
This one day session at BT Centre in London explored the risks and benefits of open source.
[[Phil Whitehouse]] [[blogged about the event|http://philwhitehouse.blogspot.com/2007/11/open-source-in-bt.html]]. He also [[uploaded several photos to Flickr|http://www.flickr.com/photos/philliecasablanca/sets/72157603247958469/]].
We have two presentations of note; first [[Doc Searls|http://en.wikipedia.org/wiki/Doc_Searls]] (who co-wrote the [[Cluetrain Manifesto|http://www.cluetrain.com/]] and is currently the Senior Editor of [[Linux Journal|http://en.wikipedia.org/wiki/Linux_Journal]]) gave an excellent presentation on //Why All Business Will Be Based On Open Source//:
<html>
<object type="application/x-shockwave-flash" width="400" height="300" data="http://www.vimeo.com/moogaloop.swf?clip_id=858888&server=www.vimeo.com&fullscreen=1&show_title=1&show_byline=1&show_portrait=0&color="> <param name="quality" value="best" /> <param name="allowfullscreen" value="true" /> <param name="scale" value="showAll" /> <param name="movie" value="http://www.vimeo.com/moogaloop.swf?clip_id=858888&server=www.vimeo.com&fullscreen=1&show_title=1&show_byline=1&show_portrait=0&color=" /></object><br />
</html>
Secondly, [[Jeremy Ruston]] who heads the [[Osmosoft team|Welcome]], gave a talk on //How to Start an Open Source Project//:
<html>
<object type="application/x-shockwave-flash" width="400" height="300" data="http://www.vimeo.com/moogaloop.swf?clip_id=856110&server=www.vimeo.com&fullscreen=1&show_title=1&show_byline=1&show_portrait=0&color="> <param name="quality" value="best" /> <param name="allowfullscreen" value="true" /> <param name="scale" value="showAll" /> <param name="movie" value="http://www.vimeo.com/moogaloop.swf?clip_id=856110&server=www.vimeo.com&fullscreen=1&show_title=1&show_byline=1&show_portrait=0&color=" /></object><br />
</html>
[[BarCamp Brighton 3|http://barcampbrighton.org/]] is taking place on 6/7 September 2008 at the University of Sussex. Osmosoft is [[buying the beers|http://barcampbrighton.org/2008/07/09/the-beers-are-on-osmosoft/]]!
~BarCamp London 4 took place at the Capital Radio building on Charing Cross Road on 31 May and 1 June 2008. [[Phil Whitehouse]], [[Phil Hawksworth]], [[James Shi]], [[Simon McManus]] and [[Frederik Dohr]] came along.
[[Phil Whitehouse]] wrote a [[blog post|http://philwhitehouse.blogspot.com/2008/06/barcamp-london-4.html]] about the event, and also uploaded several photos to [[Flickr|http://www.flickr.com/photos/philliecasablanca/sets/72157605358581861/]].
8th/9th September 2007
Barcamp is an [[unconference|http://en.wikipedia.org/wiki/Unconference]] intended to bring together technical professionals in Brighton and people in town for dConstruct to learn and co-work.
Osmosoft was delighted to be one of the sponsors of this event. More information available at the [[BarCampBrighton web site|http://barcamp.org/BarCampBrighton]]
More personal reflections on the event can be found on [[Phil Whitehouse's blog|http://philwhitehouse.blogspot.com/search/label/barcampbrighton07]], as well as [[on his Flickr profile|http://www.flickr.com/photos/philliecasablanca/sets/72157603211141013/]].
Blaine is a Canadian transplant to Northern Ireland via San Francisco, where he made [[Twitter|http://twitter.com]] do things no website had done before. In addition to being a primary author on the [[OAuth|http://oauth.net/]] specification and active in the [[Jabber|http://www.jabber.org/]] community, he is a frequent contributor to various open source projects.
At Osmosoft, Blaine is focused on making the web a little more responsive and a little more human. When not at work he's either busy travelling or procrastinating on uploading photos from his trips.
If you're popping into the office, Blaine will have a small double ristretto cappuccino in ceramic, with a small plain biscotti if you're feeling decadent.
[[romeda.org|http://romeda.org]]
[[flickr.com/photos/lattice|http://flickr.com/photos/lattice/]]
[[twitter.com/blaine|http://twitter.com/blaine]]
Osmosoft attended ~BlogTalk (official site [[here|http://2008.blogtalk.net/]]) in Cork on 3/4 March 2008. As well as running a stall, we also showcased an improved version of RippleRap. An archive of the ~RippleRap file containing all the notes taken at the conference can be found [[here|http://www.ripplerap.com/BlogTalk2008/blogtalk.html]].
The head of our team, [[Jeremy Ruston]], gave a presentation about the acquisition of Osmosoft by BT and TiddlyWiki's corresponding move into the Enterprise.
[[Phil Whitehouse]] wrote a [[blog post|http://philwhitehouse.blogspot.com/2008/03/blogtalk-wash-up.html]] reflecting on the experience, and the team published [[several photos on Flickr|http://www.flickr.com/groups/osmosoft/pool/tags/blogtalk/]].
Chris has been designing and developing with open software and open systems since the early nineties with a focus on collaboration and collaborative tools.
These past few years his focus has been on open web ~APIs that allow people to connect stuff here with other stuff there, learning as they go.
At Osmosoft, Chris is focused on TiddlyWeb and other server side aspects of TiddlyWiki.
[[http://cdent.tumblr.com|http://cdent.tumblr.com]]
[[http://www.flickr.com/photos/cdent|http://www.flickr.com/photos/cdent]]
[[http://twitter.com/cdent|http://twitter.com/cdent]]
{{{
Background: #111
Foreground: #888
PrimaryPale: #222
PrimaryLight: #18f
PrimaryMid: #333
PrimaryDark: #014
SecondaryPale: #ffc
SecondaryLight: #fe8
SecondaryMid: #999
SecondaryDark: #841
TertiaryPale: #eee
TertiaryLight: #ccc
TertiaryMid: #999
TertiaryDark: #666
Error: #f88
Darkest: #000
Brightest: #fff
Darker: #111
Dark: #333
TextOnDark: #ccc
DullTextOnDark: #888
BrightOnDark: #eee
DullOnDark: #666
SubtleOnDark: #444
Magenta:#D71F85
}}}
We'd love to hear from you if you have any questions, comments or want to get involved with the work we are doing. Either email us at [[hello@osmosoft.com|mailto:hello@osmosoft.com]] or contact one of us directly through the links posted on our [[profiles|Welcome]]. Or come and visit us in our office!
Our address is:
Osmosoft
Room 404 (no, really!)
Westminster Telephone Exchange,
1a Broadway Street,
London,
~SW1H 0AY
!Directions by tube
The nearest station is St James Park. Exit onto Broadway and follow the road towards New Scotland Yard. The BT Telephone Exchange is the tall building opposite New Scotland Yard with the blue doors.
<html>
<iframe width="425" height="350" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="http://maps.google.co.uk/maps/ms?hl=en&geocode=&near=w1&ie=UTF8&om=1&oe=UTF8&msa=0&msid=110460987146491014064.00045e0415158c8c4023e&ll=51.498303,-0.134029&spn=0,0&output=embed&s=AARTsJprSZFLZIACyNLpP5Ao_VDhnIhxuA"></iframe><br /><small><a href="http://maps.google.co.uk/maps/ms?hl=en&geocode=&near=w1&ie=UTF8&om=1&oe=UTF8&msa=0&msid=110460987146491014064.00045e0415158c8c4023e&ll=51.498303,-0.134029&spn=0,0&source=embed">View Larger Map</a></small>
</html>
<!--{{{-->
<div class='title' macro='view title'></div>
<div class='toolbar' macro='toolbar +saveTiddler -cancelTiddler deleteTiddler'></div>
<div class='editor' macro='edit title'></div>
<div macro='annotations'></div>
<div class='editor' macro='edit text'></div>
<div class='editor' macro='edit tags'></div><div class='editorFooter'><span macro='message views.editor.tagPrompt'></span><span macro='tagChooser'></span></div>
<!--}}}-->
We frequently attend, sponsor or host public events. If you are interested in meeting us to talk about our open source projects, or have something you'd like to share with us, seeking us out at events is a good way to make contact.
!!Open Source Show 'n' Tell
Osmosoft organises frequent [[Open Source Show 'n' Tell]] sessions, held in or near [[our offices|Contact us]] in London and everyone is welcome to attend, doubly so if you've got something to show!
We also occasionally host [[Hackathons]] - a chance for likeminded developers to come together and develop software. This is also an opportunity for those interested in TiddlyWiki to get help and support in developing on this platform.
!!Previous events
You can find demos, videos and resources that have been presented at previous events here:
TiddlyPac - Seattle, 26 July 2008
TiddlyRose - Portland, 23 July 2008
[[OSCon 2008]] - Portland, 23-25 July 2008
[[OpenTech 2008]] - London, 5 July 2008
[[TiddlyWest]] - San Francisco, 18 June 2008
[[Supernova 2008]] - San Francisco, 16-18 June 2008
[[BarCamp London 4]] - London, 31 May / 1 June 2008
[[next08]] - Hamburg, 15 May 2008
[[VRM 2008]] - Munich, 21/22 April 2008
[[Future of Web Design]] - London, 17 April 2008
[[UKUUG OpenMoko talk]] - London, 9 April 2008
[[BlogTalk]] - Cork, Ireland, 3/4 March 2008
[[Le Web 3]] - Paris, 10/11 December 2007
[[BT Open Source - Open for Business]] - London, 31 October 2007
[[Future of Web Apps 2007]] - London, 3-5 October 2007
[[TiddlyAnniversary]] - London, 21 September 2007
[[BarCampBrighton 2007]] - Brighton, 8/9 September 2007
[[dConstruct 2007]] - Brighton, 7 September 2007
[[Wiki Wednesday]] - London, 4 July 2007
[[Supernova 2007]] - San Francisco, June 2007
As a long-time TiddlyWiki contributor, Frederik has been coerced into leaving the comfort of Germany to serve in [[Osmosoft Towers|Contact us]]. He is a self-described geek, open-source advocate, and can easily obsess about
tiny details.
Apart from pretending to be a coding monkey on occasion, Frederik has a keen interest in enhancing collaboration and capturing reference knowledge.
If you're popping in to the office, Frederik will have a cup of unsweetened black coffee and whatever food he might find agreeable in these strange lands.
[[fnd.lewcid.org/blog|http://fnd.lewcid.org/blog/]]
[[twitter.com/fnd|http://twitter.com/fnd/]]
3rd-5th October 2007
Several [[Osmosoftonians|Osmosoftonian]] attended the Future of Web Apps (FOWA) event from 3rd-5th October 2007. You can find information about the event at the [[FOWA website|http://www.futureofwebapps.com/past-events.html#londonOct07/]].
[[Phil Whitehouse]] [[wrote several blog entries during the event|http://philwhitehouse.blogspot.com/search/label/FOWA]], and uploaded [[a set of photos to flickr|http://www.flickr.com/photos/philliecasablanca/sets/72157603208138462/]].
[[FOWA|http://london2008.futureofwebapps.com/]] takes place in London from 8-10 October 2008, although we won't be attending the workshops on the 8th - just the main conference on the 9th and 10th. Hopefully see you there!
The Future of Web Design conference took place in London on 17 April 2008. You can find out more on the [[official website|http://www.futureofwebdesign.com/]].
[[Paul Downey]], [[Phil Hawksworth]] and [[Phil Whitehouse]] attended this event. Paul created some terrific [[sketchnotes|http://www.flickr.com/photos/psd/2421674128/]] recording the event, and Phil Whitehouse published a [[blog post|http://philwhitehouse.blogspot.com/2008/04/future-of-web-design.html]] and a [[set of photos|http://www.flickr.com/photos/philliecasablanca/sets/72157604587677664/]].
Osmosoft occasionally organised hackathons, where developers can meet and develop software together.
!Previous events
The previous hackathon received a detailed review on the [[Heisse Online website|http://www.heise-online.co.uk/open/Community-Live-Osmosoft-s-TiddlyWiki-Hackathon-and-Pizza-on-Rails--/features/111336]].
Jeremy is the only real constant in Osmosoft, the company he set up in 2005, that BT acquired in May 2007. He is the original creator of TiddlyWiki, the open source product at the heart of Osmosoft.
After a career creating inspiring software, Jeremy is now BT's Head of Open Source Innovation. This roughly means that he is responsible for the development of BT's participation in the open source industry. He also looks pretty funky in aviators, and [[can fit inside a small cupboard|http://www.flickr.com/photos/philliecasablanca/1320086480/]].
If you're popping into the office, Jeremy will have a cappuccino and a pain au chocolat.
[[jermolene.wordpress.com|http://jermolene.wordpress.com]]
[[flickr.com/photos/jermy|http://flickr.com/photos/jermy/]]
[[twitter.com/jermolene|http://twitter.com/jermolene/]]
Jon has been on the scene for just under two years but is making a name for himself as someone who really "gets" the web and how it affects our lives.
Jon is an able technologist and is particularly keen on showing how much "programming" you can do these days without being able to code.
If you're popping in to the office, Jon will have a cappuccino and a pain au chocolat.
[[jayfresh.wordpress.com|http://jayfresh.wordpress.com]]
[[flickr.com/photos/jayfresh/|http://www.flickr.com/photos/jayfresh/]]
[[twitter.com/jayfresh|http://twitter.com/jayfresh/]]
Jon has been working on the development of web based applications in the webapp widget world. He would describe himself as an experimental developer who likes to see the IT world differently.
Right now he is interested in information/data visualisation.
If you're popping into the office, it's best not to ask Jon what he will have as he is very unpredictable, even whether or not he will take milk or sugar is uncertain, but anything chocolatey on the side should go down well.
[[http://www.jonrobson.me.uk|http://www.jonrobson.me.uk]]
[[http://www.flickr.com/photos/24701860@N05/|http://www.flickr.com/photos/24701860@N05/]]
[[http://twitter.com/rakugojon|http://twitter.com/rakugojon]]
Paris, 10/11 December 2007
Le Web 3 is a conference which took place in Paris on 10/11 December 2007, where we shared a stall with BT and unveiled a event dossier tool called RippleRap.
JP Rangaswami, MD of BT Design, gave a presentation at Le Web 3, abley assisted by our very own [[Phil Hawksworth]], and demonstrating our ~RippleRap product. Here is the video:
<html>
<center><object width="320" height="240"><param name="movie" value="http://vpod.tv/leweb3/393628/flash/nVideoPlayer"></param><param name="allowfullscreen" value="true"></param><embed src="http://vpod.tv/leweb3/393628/flash/nVideoPlayer" type="application/x-shockwave-flash" width="320" height="240" allowfullscreen="true"></embed></object></center>
</html>
JP's presentation version of RippleRap can be seen [[here|jp/leweb.html#Terror]] (after clicking on this link, scroll down for the "next" button). You can also see the entire transcript [[here|Le Web 3 Transcript]].
Here are the team's blog entries about the event, including our reflections on the introduction of ~RippleRap:
*[[Phil Whitehouse|http://philwhitehouse.blogspot.com/2007/12/le-web-morning-after.html]]
*[[Paul Downey|http://blog.whatfettle.com/2008/01/04/on-twitter-constraints/]]
*[[Phil Hawksworth|http://www.hawksworx.com/journal/category/leweb3/]]
The team also [[uploaded several photos to Flickr|http://www.flickr.com/groups/osmosoft/pool/tags/leweb3/]].
This is a transcript of JP Rangaswami's talk given at [[Le Web 3]].
''Moderator:'' Moving along to our next speaker, probably best known for [[Confused of Calcutta|http://www.confusedofcalcutta.com]], his blog, but you might also know him as the Managing Director of BT Design, please welcome to the stage, coming down from the stairway, JP Rangaswami.
!Why Enterprise 2.0...Isn't
''Opening comments''
Hello. Good morning, everyone. I had the opportunity a few months ago to spend time with a guy called Alan Kay who was responsible, pretty much, for creating what we know today as windows in terms of an interface. Nearly 30 years ago, Alan said, "The best way to predict the future is to invent it".
30 years have passed and when I met him in San Diego I asked him what he felt about it and his response was, "JP, you know, spending time in large enterprises, I get the feeling that the best way to predict the future now is to prevent it". That's what large enterprises can do, but before I get onto that, it's trying to understand what people like Alan meant in order to give you the context of why I believe that Enterprise 2.0 is not really happening as yet.
You can imagine what happened in the late 1960s with Engelbart and Kay in terms of the mouse, the pointer, the click, the desktop as providing individuals with the right to consume structured information. It took us nearly 15 years after that with the advent of Excel, or ~VisiCalc more like, spreadsheets, small databases, word processors, storyboard tools to say that we then managed to give individuals and enterprises the right to produce structured information and it took a decade beyond that before we started having the concept of the browser and access to unstructured information so that the individual could now manipulate unstructured information.
However, that was not where the web was meant to be and one of the reasons people even us the word Web 2.0 is to describe an environment where the web became writable. The web was always meant to be writable, it was writable, so when I talk about Enterprise 2.0, I look at it in the context of empowering individuals. The empowerment of the individual is at the heart of what modern Web 2.0 or Enterprise 2.0 is. The customer gets in control, the web becomes live, writable. These things are absolutely critical to understand what it is we mean when we say Enterprise 2.0.
''Terror''
What happens when you start talking about an individual being in control in an enterprise? Fundamentally, it is abject terror. People who like control are very, very uncomfortable with disaggregating control and giving it to individuals. This is not difficult or unusual. From the time we had priests, then through to doctors, through to lawyers and even IT departments, the concepts have been the same: speak in a foreign language, put smoke and mirrors between you and everybody else, make it very, very difficult for somebody else to understand what it is you are doing and then claim this is complex, you will not understand it.
That is what large enterprises do as well. We build immune system barriers in to obfuscate, complicate, make complex and corrupt things that happen inside the firm so that when youngsters walk into the firm they have to have all their ingenuity taken out of them. It is something along the lines of what an assembly line does, even in a school. You take individuality and then you reduce standard deviation by having processes that just say, "Any colour you like, as long as it's black". That's what enterprises do: reduce standard deviation rather than allow for individuality, so I wanted to just run very quickly through some of the reasons why people in enterprises are not adopting 2.0 techniques and what we can do about it.
''Decaffeinating Ts''
However, I want to give you some context and an apology to Loic and to the organisers of the ~LeWeb, because last year I was meant to be here and I pulled out on the last day. I pulled out for a strange reason: part of my body gave up and I had a major heart attack and when I had the heart attack it was slightly difficult to travel and I have had to make quite a lot of lifestyle changes since, at least one of which is that I do not drink caffeinated tea, which is why this section of the agenda is called 'Decaffeinating Tea' because I wanted to look at some particular Ts within an enterprise that need decaffeinating, so bear with me, humour me on this.
''Trust''
I do not know how many of you know the origin of the word 'bankrupt', but the merchants of Lombardy used to sit down on benches and talk to each other. If somebody within their group let them down, didn't keep their word, somebody would go and pick up the bench the guy sat on, break it in two and make it quite difficult for the person to sit down again. A breakdown of trust was what bankruptcy was about because the banco the person was sitting on was rupto.
Trust is at the heart of any sort of community activity and should be at the heart of any enterprise.
Instead, what do we do? Let me tell you. We build systems that say, "It is all right to have a conversation with another person and to copy their boss in". How to really build trust, a CC button; I am going to ask you to do something and I am going to copy your boss in. It should be called an "ass-cover" button, but somehow AC does not sound the same. They cannot tell me it is "carbon copy" because you can save sent mail anyway.
However, if CC was not bad enough, what else can you do? I am going to have a conversation with you and tell your boss without telling you. Wow. This is really going to build trust. A BCC button. Who thought that up? What value is there in trying to create collaboration, trust, commitment to each other when you had hidden conversations in public that way?
That is what large enterprise thinkers do when you are not careful and when you break down trust, you cannot legislate for ethics. You cannot possibly legislate for ethics. As far as I am concerned, Enron was Sarbox-compliant. It does not prove a thing. Ticked boxes do not a prison make.
The way we are going to have to work on it is to regenerate the trust we used to have and we have the tools to do it; yet sharing is not part of the concept of how an enterprise works.
''Team''
In order for trust to be meaningful, you do not have the concept of trust unless you also have the concept of people working together, people working as a team. However, if you look at the incentives within the enterprise, very rarely are the incentives anything other than hierarchically managed and controlled. The hierarchy then lends itself down to individual incentives, individual targets where "I'm all right, Jack, I will look after myself, you look after yourself", becomes the rule. We have spoken for many years about knowledge management and sharing, but most of the time, what you actually see in a large enterprise is inside the person's head, the person does not want to share.
However, human beings are communal beings. Man is a social animal, man is not an island. If that is the case, why does it happen that you take a normal human being, put him into an enterprise and he suddenly has to be clawing his way up an organisational ladder, scratching each other's eyes out, not sharing information? Why do these behaviours persist? They persist largely because the incentives are not aligned. You have incentive systems.
There was a guy called Chandler who in the late 1960s formulated a law that said that it is not true any more that strategy creates structure; it has now reached a stage where with large organisations, the structure can also create strategy. How you are organised has great impact on the things you can or cannot do and sadly for many institutions we are still organised not to share. We build silos, we build walls, we do not allow activity between the silos; lateral movement in a firm is prevented rather than augmented or even encouraged. That creates problems.
''Time''
Onto the next one. This is a strange T: time. I have nothing against Google, I think they are a fine company, but one of the reasons I get confused is when people tell me this is a great thing to separate 20% of a person's time and have them allocated to some activity or another, because it is not the 20% that worries me, it is the other 80%.
I think we are already should be living in a world where we concentrate on outputs not inputs. For my staff, if they get what they are meant to get done, what do I care what they do with their time because we do not live in a clock-punching world? I do not look at what time somebody comes in and what time somebody leaves. I do not even look as to whether the person comes into the office: many of my staff are completely disaggregated, they live at home or they come in to see me when they need to, but why celebrate the idea that 20% of the time you are actually allowed to do what you want?
I am worried about the other 80%, because I want my guys to do what they want in order to get value for the firm all 100% of the time and the modern generations think that way, they do not understand inputs and we need to be careful about it.
There is one other element about time that we need to understand in an enterprise which is that particularly when computing started entering the enterprise, what came in was batch thinking. Batch thinking became bad thinking. It was all right to tell you that truth was a snapshot that someone prepared according to some conventional representation yesterday. I am no accountant, but I am aware that when I look at most financial statements, the only truth I see is a cash position. Everything else is some form of conventional representation. It is symbols which you do not necessarily understand. It is words that reflect things other than what is said, because it is nothing more than convention. We need to understand that, but today's generation do not actually think of time the same way, they do not accept batch, everything has happened to them. We accuse them of instant gratification, but actually they do not have the same delays that we have had, that we allow, and this enters the enterprise.
''Technology''
I do not particularly like ~PowerPoint and I thought to myself, "How am I going to allow a multicultural audience to try and follow what I am saying when I am trying to say it at very high speed?" and I thought, "Okay, I will give in and I will use some form of presentation technology and use the same letter to make my points to make my points to help people to understand". However, I was grinding my teeth on my way back here after the Led Zep concert to say, "How will I use ~PowerPoint? I do not like doing it".
Yes, I was there and when I came here, I thought, "I know what!" I already had the technology. Some of the guys who came here, they built something called RippleRap, which is fundamentally a wiki on a stick to be able to work with in order to say I do not have to be online to work on a wiki, I can synchronise what I am writing when I reconnect later and in its simplest form, what you are seeing this presentation on is RippleRap. It is TiddlyWiki which is an open-source tool that we not only use, that we promote because we acquired the company that built it.
That is the way we try to think and that is very, very important for modern generations. The reason I bring up this technology is that those of you who follow my blog are already aware that things have changed to the point that in an enterprise, there appear to be only four types of applications that are needed:
*Some form of search, where you do not put in a hard coded customer ID or product ID in order to get a screen back as a response; you put in a wild card or a term to get search tools. It is much closer to your Google experience in the sense that search has moved from deterministic delving into your silos of information to probabilistic and relevance-related delving into a much wider pool of information, so one thing the knowledge worker does is search for information within the firm.
*The next thing that that person does is that you are not going to put in an enquiry screen to get a hard coded response again from some enterprise resource system. You are just going to put in again a need to understand the single data element that has changed and this is closer to what the new generation understand as an RSS feed. Let me publish and subscribe to something and let me indicate the conditions by which I subscribe to it.
*The final thing you need is some form of fulfilment. At a layer of abstraction, there is no difference between booking a meeting room, booking a flight or buying a stock or selling it. You need to have some authority to do what you are doing, identify yourself, have some way of paying for this good or service that you are reserving, internal or external, and then having the good or service delivered to you.
This is what enterprises do, but to make all these things happen - search, syndication or subscription and fulfilment - you need conversation, and what Web 2.0 is really about within the enterprise is really in bringing together of blogs, of wikis, of instant messaging, of collaborative tools of today, rather than the point tools of the past, in order to engender learning across silos.
Doc Searls, a good friend of mine, is in the audience and he would like to speak later. The Cluetrain Manifesto, which he and three other guys wrote is a critical part of even my pantheon, but David Weinberger, who is not here today, is rumoured to have said, 'Hyperlinks subvert hierarchies' and that is at the heart of what can be done in anything to do with technology. The firm throws hierarchy at you, but the tools that we have can subvert those hierarchies and create a much richer experience within the enterprise.
''Teenagers''
Why are these things important? Why am I thinking so hard and so long about the youth of today? It is for a reason; Danny Rimer in the last session alluded partly to it. For most of my life, when you had new technology, you had to be 29 to 40, usually male and usually working in aerospace or defence or investment banking in order to get to play with toys. The technology adoption curve was about a successful professional working in an industry with a high and fat profit margin.
That has changed. Today, if I go home with two mobile phones bought duty free and give one to my wife and one to my son and say, "No instructions, I want to see which one of you can power it up, take a photograph and email it or MMS it", I know my son would beat my wife every time.
Danny was referring to the fact that the kids of today get involved in technology much earlier. That technology adoption curve has sharply inverted in the past decade where much of what is new now gets played with by Generation M or Generation Y, depending on what literature you read, a mobile, multi-tasking and multi-media generation. Their tools are different. They come trained for the workforce. You do not have to teach them how to use the tools within the enterprise, you have to learn how to take their tools and embed them in the enterprise, because they come trained. They are already fully aware. The experience of the consumer teenager at home is already better than the literate 40-year-old in the enterprise in terms of access to information. Things have changed, which brings me to my final point.
''Today''
If you look at today, today is a wonderful place to be. The technology is there, but the talent is there as well, because this generation represents something completely different. They are interested in the values, they are interested in what the firm stands for.
In my father's generation, a person probably had one job. Job mobility was low, you joined a company for life, the company looked after you and it was a worthwhile relationship.
In my generation, I am probably going to have seven jobs. Mobility has increased and the covenant relationship between the enterprise and the employee has changed. It has broken down in many respects.
In my son's generation, it is actually going to be that he has seven jobs as well, but with a difference: the seven jobs are at the same time, because the next level of disaggregation of employment is taking place in front of us.
Everything to do with our life is moving to becoming something that looks like a war for talent, because Moore's law has given us tremendous price performance, Metcalfe's law has given us the value of network effects, Gilder's law has given us virtually free bandwidth, but human longevity during that period has not scaled. Man used to live maybe 77 years, now he lives 79. As a result, simplicity and convenience become very, very important and in an enterprise particularly, we have to squeeze every bit of it, because as things get commoditised, you have to know where you are going to be able to make your money to survive. The historical lock-ins are either illegal or inappropriate. Customers stay with a firm because of the value the firm provides them with and not because they are unable to move.
''Closing remarks''
In ending, I just want to remind you guys what you hold in your hands, many of you, and how that relates to the enterprise of tomorrow. 100 years ago if you worked for a bank, you were only allowed to use the company pen, because you had ledgers, you had folios and you had to make sure you used the right quill pen to enter the details into the ledgers.
Now, imagine telling a new kid you are trying to hire, "By the way, when you work for us, you will only use the company pen". Actually, we are telling them that, because the laptop they carry is their device: they personalise it, they skin it, they put stickers and decos and labels on it, it is their device to carry and transport the whole pile of completely personal attributes.
In the same sort of not-quite-anti-Google statement, I have always lived in worlds where people said, "Ban direct dial telephones from desks because people will waste time. Ban the carrying of ~BlackBerrys, people will waste time. Ban Facebook, people will waste time".
What is this concept of wasting time unless you focus on inputs? We live in a world where enterprises have to focus on outputs, where the generation that is coming forward will want to treat devices like laptops as if they were their own, they have not just a demand, but they are used to a life where it is any device, any form of connection, anywhere, any time and they can multi-task. We should not think that this has not arrived. It is a very William Gibson time. The future is here, it is just unevenly distributed. That is where we are.
My own staff keep teaching me by how they use things. I needed a demonstration of TiddlyWiki. How did that demonstration reach me when I was in a different country? He just took a video of the demo, stuck it on ~YouTube and sent me a one-time tag, because you can hide in plain sight. You stick something onto ~YouTube and you have not tagged it, you cannot find it. If you give a one-time tag like ~X371PGQ9, who the hell is going to look for that tag? However, because I have that tag, I can walk into ~YouTube and pick up the demo they have sent me.
Similarly, when I wanted to understand what to do about ~OpenSocial and I spoke to one of my guys, he just built a quick slide, took a photograph of it and Flickred it to me. Again, the attachment was sent by email, actually within Facebook, and the photograph that was attached was in Flickr.
We have the technology today. It is called the web, but we have to learn how enterprises are going to break down the walls that put them into prisons and become porous and allow connectivity between the enterprise and the customer again.
That same connectivity is also between the enterprise and its partners, its supply chain and the individuals who will become tomorrow's ~CIOs, tomorrow's ~CEOs: these guys are people who do not think like me. I am on my way out of life, I am on my second half, I have turned 50. I am relaxed about things. The kids of today expect something different.
The tools of today allow us to do something different and all I have to leave you with is the knowledge that Enterprise 2.0 does not happen not because the technology is not there, not because the will of the youth is not there, but because of people like me. We stand in the way. It is time to get out of the way, which is what I am going to do now. Thank you very much for listening.
''Participant'': Thank you. Thank you so much. What you do not know, but I know, is that JP was scheduled to speak last year and had a heart attack and we are so happy you are in excellent shape.
''JP Rangaswami'': Delighted to be here.
''Participant'': Well, we are delighted, and JP, I was following Twitter a little bit as you were talking and if you do track ~LeWeb, you should see your comments, they all say, "Oh wow! An enterprise talk that does not suck!" That is great, you were fantastic. Thank you so much.
''JP Rangaswami'': And Phil, thanks for driving.
''Participant'': Thank you, JP.
Code released by Osmosoft to the open source community will be released under a [[BSD licence|http://en.wikipedia.org/wiki/BSD_license]].
We believe that the prime measure of health of an open source project is adoption, closely followed by external contributions. For Osmosoft, the benefits of wider adoption outweigh the benefits of forcing participants to return their amended code (or any associated proprietary code) to the community, which would be required under e.g. one of the [[GPL licences|http://en.wikipedia.org/wiki/GNU_General_Public_License]].
In any event, it is hoped that most people using the code will feel compelled to return their improvements to the community, as they stand to benefit from the same scrutiny and collaboration that made the initial code worth using in the first place.
Here is the licence template:
Copyright (c) <YEAR>, <OWNER>
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
* Neither the name of the <ORGANIZATION> nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
<!--{{{-->
<style type="text/css">
#contentWrapper {display:none;}
#splashScreen {display:block;}
/*{{{*/
body {background:#111; color:#888;}
a {color:#333;}
a:hover {background-color:[[ColorPalette::PrimaryMid]]; color:[[ColorPalette::Background]];}
a img {border:0;}
h1,h2,h3,h4,h5,h6 {color:#841; background:transparent;}
h1 {border-bottom:2px solid #ccc;}
h2,h3 {border-bottom:1px solid [[ColorPalette::TertiaryLight]];}
.button {color:#014; border:1px solid [[ColorPalette::Background]];}
.button:hover {color:[[ColorPalette::PrimaryDark]]; background:#fe8; border-color:#999;}
.button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::SecondaryDark]];}
.header {background:[[ColorPalette::PrimaryMid]];}
.headerShadow {color:[[ColorPalette::Foreground]];}
.headerShadow a {font-weight:normal; color:[[ColorPalette::Foreground]];}
.headerForeground {color:[[ColorPalette::Background]];}
.headerForeground a {font-weight:normal; color:#222;}
.tabSelected{color:[[ColorPalette::PrimaryDark]];
background:#eee;
border-left:1px solid [[ColorPalette::TertiaryLight]];
border-top:1px solid [[ColorPalette::TertiaryLight]];
border-right:1px solid [[ColorPalette::TertiaryLight]];
}
.tabUnselected {color:[[ColorPalette::Background]]; background:#999;}
.tabContents {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::TertiaryPale]]; border:1px solid [[ColorPalette::TertiaryLight]];}
.tabContents .button {border:0;}
#sidebar {}
#sidebarOptions input {border:1px solid [[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel {background:[[ColorPalette::PrimaryPale]];}
#sidebarOptions .sliderPanel a {border:none;color:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:hover {color:[[ColorPalette::Background]]; background:[[ColorPalette::PrimaryMid]];}
#sidebarOptions .sliderPanel a:active {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::Background]];}
.wizard {background:[[ColorPalette::PrimaryPale]]; border:1px solid [[ColorPalette::PrimaryMid]];}
.wizard h1 {color:[[ColorPalette::PrimaryDark]]; border:none;}
.wizard h2 {color:[[ColorPalette::Foreground]]; border:none;}
.wizardStep {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];
border:1px solid [[ColorPalette::PrimaryMid]];}
.wizardStep.wizardStepDone {background:[[ColorPalette::TertiaryLight]];}
.wizardFooter {background:[[ColorPalette::PrimaryPale]];}
.wizardFooter .status {background:[[ColorPalette::PrimaryDark]]; color:[[ColorPalette::Background]];}
.wizard .button {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryLight]]; border: 1px solid;
border-color:#ffc [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryDark]] [[ColorPalette::SecondaryPale]];}
.wizard .button:hover {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::Background]];}
.wizard .button:active {color:[[ColorPalette::Background]]; background:[[ColorPalette::Foreground]]; border: 1px solid;
border-color:[[ColorPalette::PrimaryDark]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryPale]] [[ColorPalette::PrimaryDark]];}
.wizard .notChanged {background:transparent;}
.wizard .changedLocally {background:#80ff80;}
.wizard .changedServer {background:#8080ff;}
.wizard .changedBoth {background:#ff8080;}
.wizard .notFound {background:#ffff80;}
.wizard .putToServer {background:#ff80ff;}
.wizard .gotFromServer {background:#80ffff;}
#messageArea {border:1px solid [[ColorPalette::SecondaryMid]]; background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]];}
#messageArea .button {color:[[ColorPalette::PrimaryMid]]; background:[[ColorPalette::SecondaryPale]]; border:none;}
.popupTiddler {background:[[ColorPalette::TertiaryPale]]; border:2px solid [[ColorPalette::TertiaryMid]];}
.popup {background:[[ColorPalette::TertiaryPale]]; color:#666; border-left:1px solid [[ColorPalette::TertiaryMid]]; border-top:1px solid [[ColorPalette::TertiaryMid]]; border-right:2px solid [[ColorPalette::TertiaryDark]]; border-bottom:2px solid [[ColorPalette::TertiaryDark]];}
.popup hr {color:[[ColorPalette::PrimaryDark]]; background:[[ColorPalette::PrimaryDark]]; border-bottom:1px;}
.popup li.disabled {color:[[ColorPalette::TertiaryMid]];}
.popup li a, .popup li a:visited {color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border: none;}
.popup li a:active {background:[[ColorPalette::SecondaryPale]]; color:[[ColorPalette::Foreground]]; border: none;}
.popupHighlight {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
.listBreak div {border-bottom:1px solid [[ColorPalette::TertiaryDark]];}
.tiddler .defaultCommand {font-weight:bold;}
.shadow .title {color:[[ColorPalette::TertiaryDark]];}
.title {color:[[ColorPalette::SecondaryDark]];}
.subtitle {color:[[ColorPalette::TertiaryDark]];}
.toolbar {color:[[ColorPalette::PrimaryMid]];}
.toolbar a {color:[[ColorPalette::TertiaryLight]];}
.selected .toolbar a {color:[[ColorPalette::TertiaryMid]];}
.selected .toolbar a:hover {color:[[ColorPalette::Foreground]];}
.tagging, .tagged {border:1px solid [[ColorPalette::TertiaryPale]]; background-color:[[ColorPalette::TertiaryPale]];}
.selected .tagging, .selected .tagged {background-color:[[ColorPalette::TertiaryLight]]; border:1px solid [[ColorPalette::TertiaryMid]];}
.tagging .listTitle, .tagged .listTitle {color:[[ColorPalette::PrimaryDark]];}
.tagging .button, .tagged .button {border:none;}
.footer {color:[[ColorPalette::TertiaryLight]];}
.selected .footer {color:[[ColorPalette::TertiaryMid]];}
.sparkline {background:[[ColorPalette::PrimaryPale]]; border:0;}
.sparktick {background:[[ColorPalette::PrimaryDark]];}
.error, .errorButton {color:[[ColorPalette::Foreground]]; background:#f88;}
.warning {color:[[ColorPalette::Foreground]]; background:[[ColorPalette::SecondaryPale]];}
.lowlight {background:[[ColorPalette::TertiaryLight]];}
.zoomer {background:none; color:[[ColorPalette::TertiaryMid]]; border:3px solid [[ColorPalette::TertiaryMid]];}
.imageLink, #displayArea .imageLink {background:transparent;}
.annotation {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; border:2px solid [[ColorPalette::SecondaryMid]];}
.viewer .listTitle {list-style-type:none; margin-left:-2em;}
.viewer .button {border:1px solid [[ColorPalette::SecondaryMid]];}
.viewer blockquote {border-left:3px solid [[ColorPalette::TertiaryDark]];}
.viewer table, table.twtable {border:2px solid [[ColorPalette::TertiaryDark]];}
.viewer th, .viewer thead td, .twtable th, .twtable thead td {background:[[ColorPalette::SecondaryMid]]; border:1px solid [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::Background]];}
.viewer td, .viewer tr, .twtable td, .twtable tr {border:1px solid [[ColorPalette::TertiaryDark]];}
.viewer pre {border:1px solid [[ColorPalette::SecondaryLight]]; background:[[ColorPalette::SecondaryPale]];}
.viewer code {color:[[ColorPalette::SecondaryDark]];}
.viewer hr {border:0; border-top:dashed 1px [[ColorPalette::TertiaryDark]]; color:[[ColorPalette::TertiaryDark]];}
.highlight, .marked {background:[[ColorPalette::SecondaryLight]];}
.editor input {border:1px solid [[ColorPalette::PrimaryMid]];}
.editor textarea {border:1px solid [[ColorPalette::PrimaryMid]]; width:100%;}
.editorFooter {color:[[ColorPalette::TertiaryMid]];}
#backstageArea {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::TertiaryMid]];}
#backstageArea a {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstageArea a:hover {background:[[ColorPalette::SecondaryLight]]; color:[[ColorPalette::Foreground]]; }
#backstageArea a.backstageSelTab {background:[[ColorPalette::Background]]; color:[[ColorPalette::Foreground]];}
#backstageButton a {background:none; color:[[ColorPalette::Background]]; border:none;}
#backstageButton a:hover {background:[[ColorPalette::Foreground]]; color:[[ColorPalette::Background]]; border:none;}
#backstagePanel {background:[[ColorPalette::Background]]; border-color: [[ColorPalette::Background]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]] [[ColorPalette::TertiaryDark]];}
.backstagePanelFooter .button {border:none; color:[[ColorPalette::Background]];}
.backstagePanelFooter .button:hover {color:[[ColorPalette::Foreground]];}
#backstageCloak {background:[[ColorPalette::Foreground]]; opacity:0.6; filter:'alpha(opacity:60)';}
/*}}}*/
/*{{{*/
body { background-color:[[ColorPalette::Background]]; font: normal 13px/1.5em Arial, sans-serif; color:[[ColorPalette:TextOnDark]];}
div.constrainer { width:800px; margin:0 auto 0 auto; overflow:hidden; clear:both; }
input.txtOptionInput {border-style:none; margin:0; padding:4px; color:#444; background:#fff url(./images/bg_search.png) repeat-x top left;}
div.header { background:[[ColorPalette::Darker]] url(images/lights.png) repeat-x center 70px; position:relative;}
div.header div.headerShadow { height:160px; top:0; left:0; }
div.header div.headerShadow span.siteTitle { position:absolute; top:40px; left:0; width:201px; height:43px; text-indent:-9999px; overflow:hidden; background:transparent url(images/logo.png) no-repeat top left;}
div.header div.headerShadow span.siteSubtitle { position:absolute; top:20px; right:0; width:196px; height:32px;text-indent:-9999px; overflow:hidden; background:transparent url(images/from_bt.png) no-repeat top left; }
div.header div.headerForeground { display:none; }
#controlBar { background-color:[[ColorPalette::Darkest]]; color:[[ColorPalette:TextOnDark]]; border-bottom:solid 1px [[ColorPalette::DullOnDark]]; }
#controlBar a { color:[[ColorPalette::DullOnDark]]; border-style:none; font-size:0.8em;}
#controlBar a:hover { color:[[ColorPalette::TextOnDark]]; background-color:[[ColorPalette::Darkest]]; }
#controlBar div.constrainer a { margin-right:2em; }
#controlBar div.sliderPanel { margin:2em 0;}
#controlBar div.sliderPanel a { margin-right:0;}
#messageArea {z-index:9999;}
#displayArea { margin:0; float:left; width:530px;}
#mainMenu {display:none;}
#sidebar {position: relative; margin:1em 0 4em 0; float:right; width:220px; text-align:right;}
#sidebar a {color:[[ColorPalette::Magenta]]; font-size:1.7em; font-weight:normal;line-height:1.4em;}
#sidebar a:hover {color:[[ColorPalette::Brightest]]; background-color:[[ColorPalette::Background]];}
#sidebar a.button {font-size:1.2em; color:#777; clear:right; border-style:none;}
#sidebar a.button:hover {color:#ccc; background-color:[[ColorPalette::Background]]; }
#sidebar input.txtOptionInput {width:170px; margin:4px 0 0 8px; }
div.tiddler {margin:0; padding:0 0 4em 0;}
div.tiddler a { color:#ddd;}
div.tiddler a:hover { color:[[ColorPalette::Magenta]]; background:[[ColorPalette::Background]];}
div.tiddler div.subtitle { display:none; }
div.tiddler div.toolbar { text-align:left; margin-left:0.5em; display:inline;}
div.tiddler div.toolbar > a.button { color:[[ColorPalette::SubtleOnDark]]; border-width:0;}
div.tiddler div.toolbar > a.button:hover { color:[[ColorPalette::BrightOnDark]]; background:[[ColorPalette::Darker]];}
div.tiddler div.title { font-size:2em; margin-left:0; color:[[ColorPalette::Brightest]]; display:inline; font-weight:normal;}
div.tiddler div.viewer { font-size:1.05em; margin:0 2em 0 0; padding-top:0.3em; width:430px; color:[[ColorPalette::Foreground]]; line-height:1.3em;}
div.tiddler div.viewer img { float:left; clear:left; margin:0 1em 1em 0; zoom:1;}
div.tiddler div.viewer h1, div.tiddler div.viewer h2, div.tiddler div.viewer h3, div.tiddler div.viewer h4 { border-bottom:solid 1px #333; padding:0.3em 0; margin:0.2em 0 0.2em 0; }
div.tiddler div.viewer h1 {color:#eee; font-size:1.4em; margin:1em 0 0.2em 0; }
div.tiddler div.viewer h2 {color:#eee; font-size:1.3em; margin:1em 0 0.2em 0;}
div.tiddler div.viewer h3 {color:#999; font-size:1.2em;}
div.tiddler div.viewer h4 {color:#999; font-size:1em;}
div.tiddler div.tagged { background-color:[[ColorPalette::Background]]; border-width:0; margin:0 0 2em 0;}
div.tiddler div.tagged ul li.listTitle { display:none; }
div.tiddler div.tagged ul li a { font-size:1em; display:block; border-style:none; margin-bottom:0; padding:0 0 0 16px; text-decoration:none; background:transparent url(images/tag.png) no-repeat 0 0.2em; color:#333; }
div.tiddler div.tagged ul li a:hover { color:#ccc; background:transparent url(images/tag.png) no-repeat 0 0.2em;}
div.tiddler div.tagging { float:none; border:solid 1px #222; padding:3px; background-color:#000; overflow:hidden; clear:both; zoom:1;}
div.tiddler div.tagging ul li { float:left; margin:0 1em 0 0; color:#666; }
div.tiddler div.tagging ul li a { color:[[ColorPalette::Magenta]]; }
div.tiddler div.tagging ul li a:hover { color:#fff; background-color:#000; }
div.tiddler table {margin:0; border-width:0px; }
div.tiddler table tr { border-width:0px; }
div.tiddler table tr td { border-width:0px; vertical-align:top; }
div.tiddler table tr td * { float:left; clear:left; }
div.tiddler div.viewer pre { font-size:0.9em; margin:0 0 1em 0; padding:1.2em; border:solid 1px #444; background-color:#222; color:#aaa; }
div.tiddler div.txtMainTab div.tabset {height:1.4em;}
div.tiddler div.txtMainTab div.tabset a.tab {border-style:none; background-color:transparent; color:[[ColorPalette::Magenta]]; padding:0.15em 0.6em;}
div.tiddler div.txtMainTab div.tabset a.tabSelected {border:solid 1px #ccc; border-bottom:solid 3px [[ColorPalette::Background]]; background-color:[[ColorPalette::Background]]; color:#ccc;}
div.tiddler div.txtMainTab div.tabset a.tabUnselected:hover {color:#fff;}
div.tiddler div.txtMainTab div.tabContents {background-color:transparent; border-style:none; border-top:solid 1px #444;}
div.tiddler div.txtMainTab ul { list-style:none; margin:0; padding:0.5em 0; }
div.tiddler div.txtMainTab ul li { padding:0 20px;}
div.tiddler div.txtMainTab ul li a { font-weight:normal; line-height:1.3em; margin:0.2em 0; }
div.tiddler div.txtMainTab ul li.listTitle { border-top:solid 1px #222 ;margin:0; padding:0.5em 0 0.2em 20px; font-size:1.5em; color:#555; }
div.tiddler div.txtMainTab ul li.listLink { margin:0; padding:0 0 0 20px; }
div.tiddler div.txtMainTab ul:first-child li.listTitle { border-style:none; }
#popup { border:solid 1px #000; padding:0;}
#popup.popup li a { background-color:#000; color:[[ColorPalette::Foreground]]; text-align:left; padding:0.1em 0.3em;}
#popup.popup li a:hover { background-color:[[ColorPalette::Magenta]]; color:#fff;}
#popup.popup li.listBreak div {border-bottom:solid 0px #111; border-top:solid 1px #333; margin:0;}
form.wizard {font-size:0.8em;}
form.wizard input.txtOptionInput {font-size:1em; }
/*}}}*/
</style>
<!--}}}-->
<!--{{{-->
<div id="splashScreen">
<div id='controlBar'><div class='constrainer' tiddler='controlBar' refresh='content'></div></div>
<div class='header'>
<div class='constrainer'>
<div class='headerShadow'>
<span class="siteTitle">osmosoft</span>
<span class="siteSubtitle">open source applications from BT</span>
</div>
<div class='headerForeground'>
<span class="siteTitle">osmosoft</span>
<span class="siteSubtitle">open source applications from BT</span>
</div>
</div>
</div>
<div id='mainMenu' refresh='content' tiddler='MainMenu'></div>
<div class='constrainer'>
<div id='displayArea'>
<div id='messageArea'></div>
<div id="s_tiddlerDisplay"><div id="splashId_Welcome" class="tiddler">
<div class="title">Welcome</div>
<div class="toolbar"><br></div>
<div class="subtitle"><span>YourName</span>, <span>27 August 2008</span> (<span>created</span> <span>26 June 2007</span>)</div>
<div class="viewer">Osmosoft is the open source innovation arm of <a target="_blank" title="External link to http://www.bt.com/" href="http://www.bt.com/" class="externalLink">BT</a>. We're a small team of techies that have a passion for open source software, with our main focus being on the TiddlyWiki product.<br><br>We have an <a target="_blank" title="External link to http://www.twitter.com/Osmosoft" href="http://www.twitter.com/Osmosoft" class="externalLink">Osmosoft twitter feed</a> and a <a target="_blank" title="External link to http://www.vimeo.com/osmosoft" href="http://www.vimeo.com/osmosoft" class="externalLink">video channel on Vimeo</a>.<br><br><h1>Meet the team</h1>You can follow our work by subscribing to our individual blogs or, if you prefer, read just the Osmosoft-related blog entries. <br><br><table class="twtable"><tbody><tr class="evenRow"><td><img src="images/photo_jeremy.jpg" alt="Jeremy" title="Jeremy"></td><td align="left"><strong>Jeremy Ruston</strong> <a target="_blank" title="External link to http://jermolene.com" href="http://jermolene.com" class="externalLink">Treat with Jermolene</a> <a target="_blank" title="External link to http://flickr.com/photos/jermy/" href="http://flickr.com/photos/jermy/" class="externalLink">flickr.com/photos/jermy</a><a target="_blank" title="External link to http://twitter.com/jermolene/" href="http://twitter.com/jermolene/" class="externalLink">twitter.com/jermolene</a></td></tr><tr class="oddRow"><td><img src="images/photo_andrew.jpg" alt="Andrew" title="Andrew"></td><td align="left"><strong>Andrew Back</strong> <a target="_blank" title="External link to http://carrierdetect.com" href="http://carrierdetect.com" class="externalLink">carrierdetect.com</a> <a target="_blank" title="External link to http://flickr.com/photos/carrierdetect/" href="http://flickr.com/photos/carrierdetect/" class="externalLink">flickr.com/photos/carrierdetect/</a><a target="_blank" title="External link to http://twitter.com/9600/" href="http://twitter.com/9600/" class="externalLink">twitter.com/9600</a></td></tr><tr class="evenRow"><td><img src="images/photo_blaine.jpg" alt="Blaine" title="Blaine"></td><td align="left"><strong>Blaine Cook</strong> <a target="_blank" title="External link to http://romeda.org" href="http://romeda.org" class="externalLink">romeda.org</a> <a target="_blank" title="External link to http://flickr.com/photos/lattice/" href="http://flickr.com/photos/lattice/" class="externalLink">flickr.com/photos/lattice/</a><a target="_blank" title="External link to http://twitter.com/blaine/" href="http://twitter.com/blaine/" class="externalLink">twitter.com/blaine</a></td></tr><tr class="oddRow"><td><img src="images/photo_chris.jpg" alt="Chris" title="Chris"></td><td align="left"><strong>Chris Dent</strong> <a target="_blank" title="External link to http://cdent.tumblr.com" href="http://cdent.tumblr.com" class="externalLink">http://cdent.tumblr.com</a> <a target="_blank" title="External link to http://www.flickr.com/photos/cdent" href="http://www.flickr.com/photos/cdent" class="externalLink">http://www.flickr.com/photos/cdent</a><a target="_blank" title="External link to http://twitter.com/cdent" href="http://twitter.com/cdent" class="externalLink">http://twitter.com/cdent</a></td></tr><tr class="evenRow"><td><img src="images/photo_fnd.jpg" alt="Frederik" title="Frederik"></td><td align="left"><strong>Frederik Dohr</strong> <a target="_blank" title="External link to http://fnd.lewcid.org/blog/" href="http://fnd.lewcid.org/blog/" class="externalLink">fnd.lewcid.org/blog</a><a target="_blank" title="External link to http://twitter.com/fnd/" href="http://twitter.com/fnd/" class="externalLink">twitter.com/fnd</a></td></tr><tr class="oddRow"><td><img src="images/photo_jon.jpg" alt="Jon L" title="Jon L"></td><td align="left"><strong>Jon Lister</strong> <a target="_blank" title="External link to http://jayfresh.wordpress.com" href="http://jayfresh.wordpress.com" class="externalLink">jayfresh.wordpress.com</a><a target="_blank" title="External link to http://www.flickr.com/photos/jayfresh/" href="http://www.flickr.com/photos/jayfresh/" class="externalLink">flickr.com/photos/jayfresh/</a><a target="_blank" title="External link to http://twitter.com/jayfresh/" href="http://twitter.com/jayfresh/" class="externalLink">twitter.com/jayfresh</a></td></tr><tr class="evenRow"><td><img src="images/photo_jonr.jpg" alt="Jon R" title="Jon R"></td><td align="left"><strong>Jon Robson</strong> <a target="_blank" title="External link to http://www.jonrobson.me.uk" href="http://www.jonrobson.me.uk" class="externalLink">www.jonrobson.me.uk</a><a target="_blank" title="External link to http://www.flickr.com/photos/24701860@N05/" href="http://www.flickr.com/photos/24701860@N05/" class="externalLink">flickr.com/photos/24701860@N05/</a><a target="_blank" title="External link to http://twitter.com/rakugojon/" href="http://twitter.com/rakugojon/" class="externalLink">twitter.com/rakugojon</a></td></tr><tr class="oddRow"><td><img src="images/photo_martin.jpg" alt="Martin" title="Martin"></td><td align="left"><strong>Martin Budden</strong> <a target="_blank" title="External link to http://martinswiki.com" href="http://martinswiki.com" class="externalLink">martinswiki.com</a><a target="_blank" title="External link to http://www.twitter.com/buddenisms" href="http://www.twitter.com/buddenisms" class="externalLink">twitter.com/buddenisms</a></td></tr><tr class="evenRow"><td><img src="images/photo_mm.jpg" alt="Michael" title="Michael"></td><td align="left"><strong>Michael Mahemoff</strong> <a target="_blank" title="External link to http://softwareas.com/" href="http://softwareas.com/" class="externalLink">softwareas.com</a><a target="_blank" title="External link to http://www.twitter.com/mahemoff" href="http://www.twitter.com/mahemoff" class="externalLink">twitter.com/mahemoff</a></td></tr><tr class="oddRow"><td><img src="images/photo_nick.jpg" alt="Nick" title="Nick"></td><td align="left"><strong>Nick Webb</strong> <a target="_blank" title="External link to http://www.erraticmusings.com" href="http://www.erraticmusings.com" class="externalLink">erraticmusings.com</a><a target="_blank" title="External link to http://www.flickr.com/photos/nickwebb/" href="http://www.flickr.com/photos/nickwebb/" class="externalLink">flickr.com/photos/nickwebb/</a><a target="_blank" title="External link to http://twitter.com/nickwebb" href="http://twitter.com/nickwebb" class="externalLink">twitter.com/nickwebb</a></td></tr><tr class="evenRow"><td><img src="images/photo_paul.jpg" alt="Paul" title="Paul"></td><td align="left"><strong>Paul Downey</strong> <a target="_blank" title="External link to http://blog.whatfettle.com" href="http://blog.whatfettle.com" class="externalLink">blog.whatfettle.com</a> <a target="_blank" title="External link to http://flickr.com/photos/psd/" href="http://flickr.com/photos/psd/" class="externalLink">flickr.com/photos/psd</a><a target="_blank" title="External link to http://twitter.com/psd/" href="http://twitter.com/psd/" class="externalLink">twitter.com/psd</a></td></tr><tr class="oddRow"><td><img src="images/photo_philh.jpg" alt="Phil" title="Phil"></td><td align="left"><strong>Phil Hawksworth</strong> <a target="_blank" title="External link to http://www.hawksworx.com" href="http://www.hawksworx.com" class="externalLink">www.hawksworx.com</a><a target="_blank" title="External link to http://flickr.com/photos/philhawksworth/" href="http://flickr.com/photos/philhawksworth/" class="externalLink">flickr.com/photos/philhawksworth</a><a target="_blank" title="External link to http://twitter.com/philhawksworth/" href="http://twitter.com/philhawksworth/" class="externalLink">twitter.com/philhawksworth</a></td></tr><tr class="evenRow"><td><img src="images/photo_simon.jpg" alt="Simon" title="Simon"></td><td align="left"><strong>Simon McManus</strong> <a target="_blank" title="External link to http://simonmcmanus.com" href="http://simonmcmanus.com" class="externalLink">simonmcmanus.com</a><a target="_blank" title="External link to http://flickr.com/photos/simonmcmanus/" href="http://flickr.com/photos/simonmcmanus/" class="externalLink">flickr.com/photos/simonmcmanus</a><a target="_blank" title="External link to http://twitter.com/simonmcmanus/" href="http://twitter.com/simonmcmanus/" class="externalLink">twitter.com/simonmcmanus</a></td></tr></tbody></table><br>Past Osmonauts are immortalised in the alumni section.</div>
<div class="tagClear"></div>
</div>
</div>
</div>
<div id='sidebar' refresh='content' tiddler='SideBar'></div>
</div>
</div>
<!--}}}-->
<script type="text/javascript">
document.getElementById("splashScreen").style.display="none";
</script>
Martin is 50% an [[Osmosoftonian]], the other half being a ~UnaMesean (for more about ~UnaMesa, see the [[faqs|faq]]). But he can usually be found in our office, and is very much considered one of our own.
A long time senior member of the TiddlyWiki community, while not wiki-hacking he enjoys fell-walking and other outdoorsy shenanigans.
If you're offering, Martin would like coffee with skimmed milk, no sugar, and chocolate chip cookies.
[[martinswiki.com|http://martinswiki.com]]
Michael has been developing for the web since the mid '90s and has always been interested in usability and front-end design. He set up the [[Ajax Patterns wiki in 2005|http://ajaxpatterns.org/]] and authored [[Ajax Design Patterns|http://oreilly.com/catalog/9780596101800/]] for O'Reilly the following year. He's a keen user and advocate of open source, and has released his Ajax efforts - writings and software - under open licensing models.
BT's widget and ~OpenSocial strategy has been his recent focus, and he ran the London ~OpenSocial hackathon in conjunction with Google in early 2008.
If you're popping into the office, Michael will have a cup of Miso soup and a shiny red apple, thanks.
[[softwareas.com|http://softwareas.com/]]
[[twitter.com/mahemoff|http://www.twitter.com/mahemoff]]
Since he was a scruffy teenager Nick has been running start-ups. His most recent was an organic breakfast business. No longer making breakfasts at 5am, Nick is now our specialist in Tiddlypreneurship. He will be demonstrating the benefits of Open Source to entrepreneurs and small businesses.
If you're popping in to the office, Nick will have a cappuccino and a [[financier|http://en.wikipedia.org/wiki/Financier_(pastry)]] from the local coffee shop.
[[erraticmusings.com|http://www.erraticmusings.com]]
[[flickr.com/photos/nickwebb/|http://www.flickr.com/photos/nickwebb/]]
[[twitter.com/nickwebb|http://twitter.com/nickwebb]]
[[OSCon 2008|http://en.oreilly.com/oscon2008/]] was an open source conference which took place in Portland, Oregon, from 21-25 July 2008. Our parent company, BT, sponsored the event.
We announced the launch of the new [[BT open source website|http://www.bt.com/opensource]] at the event, as well as BT's strategic partnership with [[FOSSBazaar|http://fossbazaar.org]].
[[Jeremy Ruston]] gave two talks at the event:
*''Open Source Innovation in the Enterprise'': You can see the [[presentation material|http://www.osmosoft.com/innovation/]], as well as playing with the [[Project Cecily demo|http://www.osmosoft.com/cecily]] (requires Safari version 3 or higher).
*''Learning from Airports'': Here's a photo of [[Jeremy in action|http://www.flickr.com/photos/x180/2705787396/]], and a video of the talk can be seen below:
<html>
<embed src="http://blip.tv/play/AcXkRIT3Pg" type="application/x-shockwave-flash" width="320" height="260" allowscriptaccess="always" allowfullscreen="true"></embed>
</html>
[[Phil Whitehouse]] has also uploaded a [[set of photos to Flickr|http://www.flickr.com/photos/philliecasablanca/sets/72157606345715675/]] from the event.
Finally, there were two ~TiddlyWiki-related events which took place in the area at this time; TiddlyRose in Portland and TiddlyPac in Seattle.
Osmosoft organises frequent Open Source Show 'n' Tell sessions, held in or near our offices in London and everyone is welcome!
Anyone can give a talk so long as there's an open source angle, and we usually go for drinks afterwards, so please feel free to [[get in touch|Contact us]] if you'd like to come along!
Videos and other assets from previous sessions can be found here:
[[Open Source Show 'n' Tell - 4 July 2008]]
[[Open Source Show 'n' Tell - 5 June 2008]]
[[Open Source Show 'n' Tell - 8 May 2008]]
[[Open Source Show 'n' Tell - 15 November 2007]]
We don't have a detailed record of our first Open Source Show 'n' Tell session, but there are some random photos which [[Phil Whitehouse]] uploaded to [[his Flickrstream|http://www.flickr.com/photos/philliecasablanca/sets/72157603203270348/]].
This event will take place at 3pm on 24 September 2008. The location will be the Haymarket Room on the second floor of [[our offices|Contact us]], and everyone is welcome! If you'd like to come along, or even better give a talk [[let us know|Contact us]]!
The most recent Open Source Show 'n' Tell session took place on 4 July 2008. Videos of the sessions can be found on the [[Osmosoft video channel on Vimeo|http://vimeo.com/album/21282]]. Sessions include:
*Ben Hood presents...A Server in a Browser
*Chris Barrington presents...~CloudCamp London
*[[Martin Budden]] presents...the ~UnaMesa Disabled Village Children Project
*[[Phil Hawksworth]] and [[Paul Downey]] present...~RippleRap at the Personal Democracy Forum
*Michael Mahemoff presents...~OpenSocial
Most of the sessions from the Open Source Show 'n' Tell event on 5 June 2008 were recorded, and they can be seen on the [[Osmosoft video channel|http://www.vimeo.com/album/16834]]. These videos include:
*Adrian De Groot presents...KDE 4 on Open Solaris
*Paul J.Adams presents....~SQO-OSS
*[[Jeremy Ruston]] presents...why BT is interested in ~TiddlyWiki
*[[Phil Hawksworth]] presents...RippleRap Update
*[[Jon Lister]] presents...Peoplesoft Offline
*[[Jeremy Ruston]] presents...New features in Safari
*Polecat presents...~CladoPeG
*Cefn Hoile presents...Semaphore SMS, ~Power-Pointless, Paraglide mash-ups, and the Scratch Drag'n'Drop programming language
*Tony ~Garnock-Jones presents...~JavaScript diff3, merging, and DVCS
*Sebastien ~Canellas-Guille presents...Dojo Framework
In addition, a series of collaborative sketchnotes created at the event can be seen [[on Flickr|http://www.flickr.com/photos/philliecasablanca/sets/72157605461797914/]].
All of the sessions from the Open Source Show 'n' Tell event on 8 May were recorded, and and are available to view on the [[Osmosoft's video channel|http://vimeo.com/album/14240]].
These videos include:
*[[Phil Hawksworth]] presents...TeamTasks
*[[Paul Downey]] presents...using TeamTasks for Agile
*Alexis Richardson presents...the Elastic Server
*[[Jon Lister]] presents...~TiddlyTemplating
*Robbie Clutton presents...Call Flow
*[[Paul Downey]] presents...Test Driven Development
*Kerry Buckley presents...Git revision control
*Saq Imtiaz presents...~UnaMesa
*[[Simon McManus]] presents...[[ccTiddly v1.6|ccTiddly]]
*Chris Dent presents...TiddlyWeb
In addition, several photos were taken during and after the event, and were uploaded to Flickr by [[Phil Whitehouse|http://www.flickr.com/photos/philliecasablanca/sets/72157604963150341/]] and [[Paul|http://www.flickr.com/photos/psd/2476139787/]] [[Downey|http://www.flickr.com/photos/psd/2476418464/]].
We're thrilled to announce that Osmosoft is sponsoring [[OpenTech|http://www.ukuug.org/events/opentech2008]] this year! As part of this sponsorship we're running a competition at the event.
~OpenTech 2008 is taking place in London on 5 July 2008, and is billed as "an informal, low cost one-day conference on technology, society and low-carbon living, featuring Open Source ways of working and technologies that anyone can have a go at".
The competition will see developers pitting their wits against each other in a TiddlyWiki stand-off. Prizes include a [[BUG (plus four modules)|http://www.buglabs.net/products]] and a [[GP2X Linux powered handheld games console|http://gp2x.co.uk/]].
You can find out more about the competition [[here|OpenTech Competition]].
There will also be an ~OpenTech edition of RippleRap.
Hope to see you there!
The ~TiddlyWiki ~OpenTech competition took place on 5 July 2008. Find out the results [[here|OpenTech 2008]].
Here are the Terms and Conditions for the [[OpenTech 2008]] competition, which took place on 5 July 2008:
#The competition is open to anyone attending ~OpenTech 2008, with the exception of employees of BT or Osmosoft.
#The prizes are 1 first prize of a [[BUG, plus 4 modules|http://www.buglabs.net/products]], 1 second prize of a [[GP2X Linux powered handheld games console|http://gp2x.co.uk]] and 1 third prize of a selection of O'Reilly books.
#No cash alternative is available for any prize. The Promoter reserves the right to substitute a prize of equivalent or greater value if this is necessary for reasons beyond its control.
#To enter, participants must present their submission at the "Venue" room at lunchtime (1pm-2pm) on the day of the ~OpenTech 2008 event.
#The winners will be chosen by an independent panel of judges. Winners will be announced at the end of the Event.
#The Judges' decision is final and no correspondence will be entered into. Entries that do not comply in full with these rules may be disqualified.
#The Promoter is British Telecommunications plc, 81 Newgate Street London ~EC1A 7AJ.
These interface options for customising TiddlyWiki are saved in your browser
<<option chkRegExpSearch>> RegExpSearch
<<option chkCaseSensitiveSearch>> CaseSensitiveSearch
<<option chkAnima
