=== nha is now known as Guest63334 [07:04] [SLIDE 1] [07:05] [SLIDE 1] [07:05] jono: Please also advertise a URL of your slides for those not using lernid :) [07:05] testing [07:05] (or make lernid do this at class start) [07:05] persia, will do [07:05] just testing right now [07:05] [SLIDE 1] [07:05] Cool! [07:06] [SLIDE 2] [07:06] [SLIDE 3] [07:06] [SLIDE 1] [07:06] all seems to be working :-) === einand_ is now known as einand === kermiac_ is now known as kermiac === kermiac is now known as kermiac_ === andylockran is now known as Webalizer === Webalizer is now known as andylockran === tobias is now known as Guest87382 === Goomba is now known as Guest32140 === Guest32140 is now known as gooomba [14:01] test [14:02] mhall119|work: yes [14:03] sorry, seeing if Lernid works [14:03] I had to setup an SSH tunnel and change my /etc/hosts file [14:04] but finally I can enjoy lernid from work [14:04] Hi All, Ubuntu class had a session on Python for beginners last week, do you know where I can look at that session? [14:05] http://irclogs.ubuntu.com/ [14:05] which day was the python session? [14:06] no sure if it was last thursday or friday [14:06] the 25th [14:07] thanks [14:08] found it.. tnx gotik [14:16] mhall119|work: what did you change your hosts file to get lernid to tunnel? [14:19] wharp: I did ssh -L 6667:irc.freenode.net:6667 $myserver [14:19] then I had to set 127.0.0.1 as irc.freenode.net in /etc/hosts [14:20] so when Lernid connects to irc.freenode.net:6667, it connets to localhost:6667, which tunnels to the real irc.freenode.net:6667 [14:20] huh, that's not how I've done it in the past, but then again, I can't get it working atm so what do I know [14:22] because irc.freennode.net is hard coded in lernid, and port 6667 is assumed from somewhere (I couldn't figure out how to set a specific ip) [14:22] I did it this was [14:22] way [14:23] Permission denied (publickey).! [14:23] hemanth: you need to have ssh access to $myserver [14:24] for that matter, you need to have a server, $myserver is a placeholder [14:25] are there any open severs? yes i know abut that access, as my machine is an ssh server with dydns as of now [14:25] I don't know of any open servers, no [14:26] if you can ssh to your server, that would work [14:26] mhall119|work,shh tunneling with gmail server worked for you? [14:26] huh? ssh with gmail? [14:27] I ssh into my webserver [14:27] ah, nice, it works, thanks mhall119|work [14:28] mhall119|work, got it, but my asking another question like have you tried ssh to gmail [14:28] nope [14:29] I didn't think gmail offered that kind of access [14:29] i had tried it once, but i do blv they have ssh thinge [14:30] cool [14:30] I had no idea [14:32] 8001 can also be used ? like ssh -L 8001:irc.freenode.net:8001 localhost, cos i m getting bind address already in use, as i'm connected to irc with another client [14:32] not for the local port, Lernid assumes 6667 [14:33] but if freenode listens on port 8001, you should be able to do that [14:33] unless you wanted to do some kind of iptables port forwarding [14:34] what is achieved my tunnel actually ? in this scenario, i had tunneled to servers to achieve more stable connect for a longer duration [14:34] but that would affect your other client too [14:34] hemanth: at work I am behind a firewall that blocks IRC [14:34] but the firewall doesn't block ssh [14:34] so I can make an ssh tunnel to the outside of the firewall, and send IRC traffic over that tunnel [14:35] mhall119|work, ha ha ok :) i missed the main part so was confused what was going on uber kool +1 to power of GNU/Linux [14:36] yes, ssh==win all the time [14:36] hacking==win==happy :) [14:38] mhall119|work, found ssh for gmail ssh -g -L 5223:talk.google.com:5223 -N you@yourserver.com [14:39] hemanth: I'll check that out, thanks [14:39] mhall119|work, np :) [15:12] what's the topic [15:12] ? [15:13] agbemenu: opening ceremonies start in ~ 45 minutes [15:18] test, if lernid opens every page, even if there is no session running: https://wiki.ubuntu.com/Lernid [15:18] https://wiki.ubuntu.com/UbuntuOpportunisticDeveloperWeek [15:31] just testing irssi. http://www.google.de [15:31] https://wiki.ubuntu.com/UbuntuOpportunisticDeveloperWeek === johnsie is now known as Guest46344 === avantman42 is now known as avantman42|work === MartyMcFly is now known as Guest32394 [15:56] Mornin [15:56] morning [15:57] Me [15:58] nearly there :) [15:58] Hey jono [15:59] :) === parth is now known as Guest17784 [16:00] nhandler_: hello. since you're in the Contacts page, what about adding a link in the wiki page to the irclogs of the sessions? ;) === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - http://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Event: Ubuntu Opportun istic Developer Week - Current Session: Welcome! Ubuntu For Opportunistic Developers - Jono Bacon - Instructor: jono || Questions in #ubuntu-classroom-chat === Goomba is now known as Guest6221 [16:01] alright! [16:01] lets just wait a min for late folks to join :) [16:01] [SLIDE 1] [16:01] Lernid folks, click on the Session tab to see the slides [16:02] Lernid may go a little grey while it downloads the slides [16:02] but it will come back :) [16:03] ok, non Lernid folks can grab the slides at http://www.jonobacon.org/files/uodw-welcome.pdf === Guest6221 is now known as gooomba [16:03] welcome everyone to Ubuntu Opportunistic Developer Week! woooooooo! [16:03] [SLIDE 1] [16:04] click Session to see the slides folks [16:04] I know a bunch of you, but some of you are new here, so let me first explain who I am [16:04] my name is Jono Bacon and I am the Ubuntu Community Manager working at Canonical [16:04] my job is to help grow a fun, productive and inspiring Ubuntu community: a place where we can all be together to celebrate an ethos, and work together to help build awesome software and community facilities around that ethos [16:04] [SLIDE 2] [16:04] Ubuntu is a way of life, a philosophy and an ideal: and being part of this incredible community is heaps of fun [16:05] our community is a phenomenal place to be: this picture was taken at our Ubuntu Developer Summit (UDS) in Barcelona [16:05] each UDS is where we get together to discuss, design and plan our next version of Ubuntu [16:05] right now, we are working on this baby [16:05] [SLIDE 3] [16:05] Lucid. [16:06] hehe I am cut and pasting to a part way through and then I start typig [16:06] typing :) [16:06] Ubuntu 10.04 Lucid Lynx will be the most exciting Ubuntu release in our history [16:06] ...so far [16:06] :) [16:06] I think this release really defines who we are, where we have been and where we are going, and it packs some stunning features such as social networking build right into the desktop, incredible boot speed, refined look and feel, software center improvements, new apps and more [16:07] so...Ubuntu Opportunistic Developer Week, let me explain the idea behind the event [16:07] [SLIDE 4] [16:07] Ubuntu is here to help people learn, create and interact [16:07] when I first put these slides together, it was for a talk in LA that was doing at SCALE [16:08] there I was throwing together a description of my talk, and the words "learn, create and interact" just popped into my head [16:08] [SLIDE 5] [16:08] I then realized that this is a process in which each word helps us define and learn from the next one [16:08] we have all been passionate about build a system in which you can not only consume free software easily, but to also build a system, framework and tools that help you to collaborate [16:09] if you can easily LEARN how to be creative, you can CREATE and that can help you INTERACT with those people who use your creations or other creators [16:09] [SLIDE 6] [16:09] Ubuntu Opportunistic Developer Week is all about kicking off a set of ideas that inspire you good folks to CREATE [16:10] the whole point of the week is to break down the gap between having a cool idea and going ahead to implement it [16:10] [SLIDE 7] [16:10] this gets to the core of the Ubuntu philosophy - we are who we are because of who we all are [16:10] if we can break down the barriers to people creating, we can all create together, continuing to build an incredible platform and set of tools that lets *everyone* create, irrespective of their interest or discipline [16:11] [SLIDE 8] [16:12] with this goal in mind, I have been working hard really to socialize the term "Opportunistic Developers" [16:12] Opportunistic Developers are people like you and me: people who have cool ideas for software, but are not necessarily programmers by definition - we are people who have the ability to write code, but we write it for fun, often in our spare time, working on projects that are specifically interesting to us [16:12] [SLIDE 9] [16:13] the platform that really changed this was the iPhone - much as it niggles at our free software tendencies, Apple did an incredible job not only delivering a device that people loved, but also a platform that harnessed the create ideas from opportunistic developers [16:13] developers have written everything from serious exercise apps to apps where you press a button and it makes a fart noise [16:13] in the opportunistic developer world, all apps are welcome, irrespective of how specialized or niche: you want to write an app for a specific service or site? go ahead! [16:13] the goal here is *enabling creativity*, irrespective of how it will manifest :-) [16:14] Ubuntu provides an absolutely incredible platform for this: we have facilities for creating applications, using multimedia, networking, creating graphics, and all manner of other things [16:14] while Ubuntu supports many languages and frameworks, we are particularly big fans of Python, and Python is simple, effective and can do pretty much anything you need it to do with the vast library of plug-ins and modules that we ship - this makes it a stunning platform for writing programs that are fun and interesting to you [16:15] this week provides a week of sessions on a wide variety of topics that explain how you can get started with this platform [16:15] now, to really get the most out of this week, I would recommend you each think of a program to write [16:15] think of something fun and interesting and simple for you to focus your efforts on [16:15] it could be a serious app that helps you life, or something silly and fun [16:16] whatever it might be, think of something over the next hour and use that as your focus for making that happen this week [16:16] I have also created a challenge this week for you all [16:16] to think of an app, see how much progress you make on it and send me screenshots on Friday so I can blog about it and show it off [16:16] more details on this are at http://www.jonobacon.org/2010/02/25/the-grand-app-writing-challenge/ [16:17] so, let's look at the collaborative development process [16:17] [SLIDE 10] [16:17] creating programs follows this broad four step process [16:18] in this session I am going to talk about some of the work going on to help this process [16:18] [SLIDE 11] [16:18] we actually have an incredible platform for building software [16:18] this diagram basically explains some of our key components [16:18] firstly, we have a tonne of ideas [16:19] you lovely people tell me your ideas every day, and it is part of my job to help you realize them and see them happen [16:19] ideas are great, but we want to convert them into software that people can run [16:19] so we have a bunch of development environments, with GNOME and KDE as good examples, which help this happen [16:20] they both offer great facilities for writing integrated top-class apps [16:20] personally I don't care which environment you use, just use at least one :) [16:20] we then have Launchpad and Bazaar [16:20] these tools provide facilities in which we can collaborate together on software [16:20] bzr helps you share source code with each other [16:21] and Launchpad provides facilities for hosting code, bug reports, answers and a wide range of other things [16:21] so at this point you could create software, but software is pointless unless people use it [16:21] so the Debian packaging system, which we use in Ubuntu, comes next [16:22] with it you can create packages which are simple to install and install all of their dependencies too [16:22] finally, how do we deliver these packages? [16:22] Launchpad has a wicked-cool feature called Personal Package Archives [16:22] this is basically your very own Debian package archive where you can publish your software [16:22] and it can appear in the Ubuntu Software Center [16:23] so...we have an end to end set of tools for making software and delivering it [16:23] I now want to talk through some of the tools available and work going on which makes our four steps: imagine, create, collaborate and publish easier [16:23] [SLIDE 12] [16:24] the first thing we need to do is break down this insane idea that writing programs is for other people [16:24] that "I am not smart enough" to write a program [16:24] or that "only proper programmers write programs" [16:24] I can assure you that you all have the ability to unlock an incredible world of creativity [16:24] you just need to learn some key tools, and Python is an absolute doddle to use [16:25] to help break this down I have organized this week and I have been blogging up a storm on Planet Ubuntu and Planet GNOME about this [16:25] everyone *can* do it [16:25] you just need to give it a shot: think of a cool app to write, use the sessions this week to have a go at writing it and do it :) [16:26] you have nothing to lose [16:26] [SLIDE 13] [16:26] the next step is getting to the fun [16:26] this was a term Rick Spencer said to me once that stuck with me [16:26] the whole idea here is that we want to make software development so easy on Ubuntu that you don't need to suffer through the complexities that surround making software [16:27] in the past, build systems, Makefiles and other crap complicated things [16:27] all the things that did not involve writing code created a blocker for writing code [16:27] so we are keen to fix this [16:27] a great starting point here, and one encouraged throughout the week is Quickly [16:27] [SLIDE 14] [16:27] quickly is a tool which lets you create new apps easily [16:28] it has a bunch of templates such as ubuntu-project that create apps for a particular environment or use case [16:28] creating an app is simple: [16:28] quickly create ubuntu-project mycoolapp [16:28] bang that into a terminal and you have a new app [16:29] (btw, you can install quickly from the software center or with: sudo apt-get install quickly) [16:29] [SLIDE 15] [16:29] editing code in quickly is simple [16:29] inside the new directory you created (e.g. mycoolapp) [16:29] whack in: quickly edit [16:29] it loads all the code into GEdit [16:29] simple [16:30] [SLIDE 16] [16:30] editing your user interface is simple with glade [16:30] just type in: [16:30] quickly glade [16:30] and finally, if you want to run your app [16:30] [SLIDE 17] [16:30] type in: quickly run [16:30] creating a new app and getting started is really quick and simple [16:31] we recommend that you all create your new apps with quickly in this way [16:31] Rick Spencer has a quickly session later today [16:31] :) [16:31] also, if you want to get started writing programs, when you have created your new app, inside the new directory it creates, just run: quickly tutorial [16:31] it will show you how to create buttons, and have them do stuff :) [16:32] [SLIDE 18] [16:32] we have been really keen to help optimize how people collaborate together too [16:32] we have some key tools which people use to work together, such as Launchpad and bzr [16:32] let me explain broadly how this works and a new project which is making this whole process easier [16:33] [SLIDE 19] [16:33] imagine you want to fix a bug [16:33] this is basically how it works [16:33] 1. choose a bug to fix [16:33] this usually involves looking at bug reports on Launchpad [16:33] 2. download the code with bzr [16:33] 3. work on the code you downloaded to fix it [16:34] 4. commit the changes you made locally: this process basically generates a set of changes which represent your bug fix [16:34] 5. you then "push" you code: this is where you upload your changes to your account on Launchpad [16:34] 6. attach the branch with your bug fix in it to the original bug report [16:35] 7. finally, you propose your bug fix to be merged into the original project so everyone can use it [16:35] so it boils down to: decide what you want to fix, grab the code, fix it, identify the changes to share, upload them, propose them for inclusion in the main project [16:35] while incredible flexible, this is quite complex to get your head around === yofel_ is now known as yofel [16:36] believe me, you get the hang of it, but it takes a few times to get used to it [16:36] Martin Owens (doctormo on IRC) has been working on a tool to build this workflow into the desktop [16:36] it is caled Ground Control [16:36] let me explain how it works for fixing a bug [16:36] [SLIDE 19] [16:37] [SLIDE 20] [16:37] you first identify a bug to fix [16:37] like this one, which is a test bug I added to the groundcontrol project [16:37] [SLIDE 21] [16:38] now go to the file manager in Ubuntu, and groundcontrol when installed (which is not on a default Ubuntu) will have a Projects directory in your home directory [16:38] when you view that directory it adds a few buttons to nautilus at the top [16:38] if you click on the second button 'Fetch Project' you can select a project to work on [16:38] [SLIDE 22] === tobias is now known as Guest11438 [16:39] it then pops up this dialog box [16:39] you can enter a project name, such as ground control, and it displays them in the dialog [16:39] select it and click ok [16:39] [SLIDE 23] [16:39] this will then create a 'groundcontrol' directory in Projects [16:39] now if you want to fix a bug, click the 'Fix Bug' button [16:40] [SLIDE 24] [16:40] here you can search for a bug: type in search terms or the bug number and it will list all the bugs that match your search [16:40] [SLIDE 25] [16:40] when you select bug and click ok, the code is download into a folder called "bugfix-lp-" [16:41] this is the branch where you will fix the bug [16:41] [SLIDE 26] [16:41] now go into that folder where the code is and fix the bug [16:41] imagine I just add some content to the README file as a test [16:41] [SLIDE 27] [16:41] when you have edited any of the files you will see an Upload Fix button appear [16:41] when your bugfix is ready, just click the button [16:42] [SLIDE 28] [16:42] this dialog then pops up [16:42] it asks you what changes you made: here summarize what you did to fix the bug [16:42] this is the commit message [16:42] [SLIDE 29] [16:42] you then see this dialog [16:43] this is where you can type in a message that the main project maintainers see when you propose your bug fix for merging - this gives you an opportunity to tell them your bugfix is good to be merged in [16:43] [SLIDE 30] [16:43] when you click OK, the bug fix is uploaded, attached to the bug report and the merge proposal is made [16:44] you will now see a View Request button [16:44] [SLIDE 31] [16:44] click that and you can see the merge request that was made [16:44] here it says that I am proposing a fix for this bug to the ground control project [16:44] the owners of that project can now go and approve my fix if they like [16:44] [SLIDE 32] [16:44] and here you can see the bugfix branch added to my bug report [16:45] as you can see, Ground Control merges the command line functionality right into bzr [16:45] making development much easier [16:45] [SLIDE 33] [16:45] so the final element is visability [16:45] visibility, rather :) [16:45] making it really simple for people to access your software and use it [16:46] this is all about packaging [16:46] packaging is a complex art, and one that many people struggle with [16:46] fortunately, Quickly makes it simple [16:46] [SLIDE 34] [16:46] if you want to create a local package, just run: quickly package [16:47] quickly uses a tool called distutils-extra that will look at all the python modules you use and set them as dependencies for the package [16:47] so if I have this in my program: [16:47] import gstreamer [16:47] quickly package will make sure my program has the gstreamer packages installed [16:47] :) [16:48] now, if you want to share your package with others, you can run: quickly release 0.1 [16:48] this will release a 0.1 version of your software and publish it to your PPA in Launchpad [16:48] this makes it possible for anyone else to grab your software and use it [16:48] and because it is a PPA, all future updates will be automatically delivered to them [16:49] [SLIDE 35] [16:49] something we have been working on in Lucid is to raise the visibility of PPAs [16:49] and they are now displayed in the Ubuntu Software Center === angel_ is now known as anhelido [16:49] this means that you can use these awesome tools to make your software and publish it easily via the Ubuntu Software Center [16:49] :) [16:50] so [16:50] [SLIDE 36] [16:50] I am a bug fan of eating your own dog food [16:50] so I have written some apps that highlight how this platform has enabled me, very much of a non-coder, to write software [16:50] a few examples... [16:50] [SLIDE 37] [16:50] Acire [16:51] so named after my wife, it is her name backwards: Erica [16:51] this is a tool which provides a library of Python examples which you can use [16:51] I just released a new version, see http://www.jonobacon.org/2010/02/26/acire-0-3-released/ for details [16:51] [SLIDE 38] [16:51] Lernid [16:51] which many of you are using to view this week :) [16:52] I was really keen to create an app which made connecting to events such as this really simple [16:52] so I created Lernid, added the ability to show slides and websites, the local schedule etc [16:52] now mbudde is maintaining Lernid as I am busy with other things, thanks Michael! :) [16:52] finally [16:52] [SLIDE 39] [16:53] as some of you will know, I do a podcast called Shot Of Jaq [16:53] you can check it out at http://www.shotofjaq.org [16:53] Shot Of Jaq is a podcast which provides the first 10mins of a discussion and we encourage others to join us and continue the discussion on the website [16:54] it is all about discussion, so I have been writing an app called App Of Jaq which specifically builds Shot Of Jaq into your desktop [16:54] it is specific, and niche, but remember, that is cool for opportunistic developers :) [16:54] so there we have it [16:54] [SLIDE 40] [16:54] a key resource which I set up for this is #ubuntu-app-devel on freenode [16:55] this is a channel filled with folks who are writing software [16:55] it is a great place to ask questions, share progress on your apps and more [16:55] also, the very final session every day this week is a hacking party [16:55] head over to that channel and spend a few hours hacking on your new app [16:56] and you can be around others to ask questions and more [16:56] hacking together is tonnes of fun :) [16:56] [SLIDE 41] [16:56] ok, we only have a few mins [16:56] any questions? [16:57] NilsR70, Do we have to share copyright with Canonical when we use Launchpad? [16:57] no [16:57] :) [16:57] eviltwin44, Isn't Acire something which would be much better suited as a website where people can submit snippits and people comment on them? [16:58] I deliberately made the library of snippets a separate project (http://www.launchpad.net/python-snippets) so you can provide any UI to thenm [16:58] Acire is a desktop UI, and you could have a web UI if you like [16:58] I am a desktop guy, and having it on the desktop is great for editing code, running snippets etc [16:58] w1nGNUtz, QUESTION: Do you have plans to integrate quickly, glade in any of the existing IDEs so that the user doesn't need to swtich bettween command line and gedit? [16:59] w1nGNUtz, most Linux hackers like using text editors and command line for running comands [16:59] commands [16:59] but there is no reason why someone could not create an IDE [16:59] too many people don't get started developing on Linux because of an IDE: it is a false prophecy, there are great tools such as GEdit and Glade to provide the equivalent functionality [16:59] ok, folks, thanks! [17:00] I am done, next up is aquarius who will get you all started with CouchDB! :-) === ChanServ changed the topic of #ubuntu-classroom to: Welcome to the Ubuntu Classroom - http://wiki.ubuntu.com/Classroom || Support in #ubuntu || Upcoming Schedule: http://is.gd/8rtIi || Event: Ubu ntu Opportunistic Developer Week - Current Session: CouchDB support in your app with DesktopCouch - Stuart Langridge - Instructor: aquarius || Questions in #ubuntu-classroom-chat [17:01] thanks very much, jono! [17:01] Hi, all. Welcome to CouchDB support in your app with DesktopCouch. [17:01] I'm Stuart Langridge, desktopcouch architect. Normally I'm in disguise as a cool guy, but today I'm going to drop that disguise and talk about databases. [17:01] Over the next hour I'm going to explain what desktopcouch is, how to use it, who else is using it, and some of the things you will find useful to know about the project. [17:01] [SLIDE 1] [17:02] If you were part of Ubuntu Developer Week, you might find you know a lot of this! [17:02] but this is *opportunistic* developer week :) [17:02] I'll talk for a section, and then stop for questions. [17:02] Please feel free to ask questions in #ubuntu-classroom-chat, and I'll look at the end of each section to see which questions have been posted. Ask at any time; you don't have to wait until the end of a section. [17:02] You should prefix your question in #ubuntu-classroom-chat with QUESTION: so that I notice it :-) [17:03] Since I'm talking about databases, some of this is necessarily a bit technical. Do please ask questions or ask me to go over something again. [17:03] So, firstly, what's desktopcouch? [17:03] Well, it's giving every Ubuntu user a CouchDB on their desktop. [17:03] CouchDB is a "document-oriented database". If you're familiar with SQL databases, where you define a table and then a table has a number of rows and each row has the same columns in it...this is not like that. [17:03] In fact, CouchDB spearheads the "NoSQL" movement, which is all about new database stuff that isn't mired in a mass of SQL that belongs in the 1980s. [17:03] SQL was good for its time. Like, say, Purple Rain by Prince. Now, though...there's something better. [17:04] [SLIDE 1] [17:04] Instead of regimented tables and rows, in CouchDB you store "documents", where each document is a set of key/value pairs. Think of this like a Python dictionary, or a JSON document. === carlos is now known as Guest92650 [17:04] So you can store one document like this: [17:04] { "name": "Stuart Langridge", "project": "Desktop Couch", "hair_colour": "red" } [17:05] and another document which is completely different: [17:05] { "name": "Stuart Langridge", [17:05] "outgoings": [ [17:05] { "shop": "In and Out Burger", "cost": "$12.99" } , [17:05] { "shop": "Ferrari dealership", "cost": "$175000" } [17:05] ] [17:05] } [17:05] The interface to CouchDB is pure HTTP. Just like the web. It's RESTful, for those of you who are familiar with web development. [17:05] This means that every programming language already knows how to speak it, at least in basic terms. [17:05] [SLIDE 2] [17:06] CouchDB also comes with an in-built in-browser editor, so you can look at and browse around and edit all the data stored in it. [17:06] So, the desktopcouch project is all about providing these databases for every user, so each user's applications can store their data all in one place. [17:07] You can have as many databases in your desktop Couch as you or your applications want, and storage is unlimited. [17:07] well, assuming you have an infinitely large hard drive, anyway. [17:07] Desktop Couch is built to do "replication", synchronizing your data between different machines. So if you have, say, Firefox storing your bookmarks in your desktop Couch on your laptop, those bookmarks could be automatically synchronized to your Mini 9 netbook, or to your desktop computer. [17:08] They can also be synchronized to Ubuntu One, or another running-in-the-cloud service, so you can see that data on the web, or synchronize between two machines that aren't on the same network. [17:08] [SLIDE 3] [17:09] So you've got your bookmarks everywhere. Your own personal del.icio.us, but it's your data, not locked up solely on anyone else's servers. === w1nGNUtz_ is now known as w1nGNUtz [17:09] Imagine if your apps stored their preferences in desktop Couch. Santa Claus brings you a new laptop, you plug it in, pair it with your existing machine, and all your apps are set up. No work. [17:10] But sharing data between machines is only half the win. The other half is sharing data between applications. [17:10] I want all my stuff to collaborate. I don't want to have to "import" data from one program to another, if I switch from Thunderbird to Evolution to KMail to mutt. [17:10] I want any application to know about my address book, to allow any application to easily add "send this to another person", so that I can work with people I know. [17:11] I want to be able to store my songs in Banshee and rate them in Rhythmbox if I want -- when people say that the Ubuntu desktop is about choice, that shouldn't mean choosing between different incompatible data silos. I can choose one application and then choose another, you can choose a third, and we can all cooperate on the data. [17:11] My choice should be how I use my applications, and how they work; I shouldn't have to choose between underlying data storage. With apps using desktopcouch I don't have to. [17:11] All my data is stored in a unified place in a singular way -- and I can look at my data any time I want, no matter which application put it there! Collaboration is what the open source desktop is good at, because we're all working together. It should be easy to collaborate on data. [17:11] That's a brief summary of what desktopcouch *is*: any questions so far before we get on to the meat: how do you actually Use This Thing? [17:12] pecisk> QUESTION: How CouchDB stores data? Multiple files, or something else? [17:12] each database is stored in a separate file, but you never, ever have to care about that :) Like how you don't have to care exactly how MySQL stores your databases [17:12] brunogirin> QUESTION: how do you control what apps see what data? === cjohnston|cell_ is now known as cjohnston|cell [17:13] brunogirin, at the moment you can't limit which apps can see which databases, but it woul dbe possible to add that if there was a need for it -- authentication to desktopcouch is done with OAuth specifically for ths sort of thing [17:14] osteenbergen> QUESTION: Which programs are supported today?? [17:14] any program that wants to use desktopcouch can do so! [17:15] danielbell> QUESTION: is there any limits on what kind of data you can store in a couchdb? can you store whole paragraphs of text - will it retain formatting like linebreaks and stuff like that? [17:15] no limit to what you can store. Line breaks will be retained. [17:15] ab28> QUESTION: Data migration and replication is possible with CouchDB? [17:16]