=== popey changed the topic of #ubuntu-classroom to: Ubuntu Open Week info: Information and Logs: https://wiki.ubuntu.com/UbuntuOpenWeek | Ubuntu classroom transcripts: https://wiki.ubuntu.com/ClassroomTranscripts | Please ask questions in #ubuntu-classroom-chat not here | Next session starts at 15:00 UTC on Fri Oct 26th === Lumiere is now known as Lumiere|DCUnited [07:25] hello === sourcode_ is now known as sourcode [11:12] hello people [11:12] anyone already in Boston? [11:13] jcastro: ping === annma is now known as ann_away === Mez is now known as Mez|Away === Mez|Away is now known as Mez === Mez is now known as Mez|Away === Mez|Away is now known as Mez === MrM is now known as mrmonday === ann_away is now known as annma === zul_ is now known as zul === Mez is now known as Mez|Away === Mez|Away is now known as Mez === Mez is now known as Mez|Away === Mez|Away is now known as Mez === Mez is now known as Mez|Away === Mez|Away is now known as Mez === Mez is now known as Mez|Away === Mez|Away is now known as Mez === scraisyi is now known as scraisy === Mez is now known as Mez|Away === Mez|Away is now known as Mez === mzungu_ is now known as mzungu [13:37] w007!!? [13:37] netsplit === harrison1 is now known as harrisony [14:58] @now [14:58] Current time in Etc/UTC: October 26 2007, 13:58:18 - Next meeting: Kernel Team in 4 days [16:02] Hola ! [16:08] Hola, hay alguien ahi? === uhutu is now known as barcc [16:11] isn't there due to be a session on now? [16:11] dgjones: There is. I'm trying to track down the person who is due to give it. [16:12] rite, wondered what was happening [16:13] mrevell, do you mind a quick pm? [16:13] dgjones: Not at all [16:13] no classes today? [16:14] bahadunn: There will be as of 16.00 UTC. [16:14] what time is it now in UTC? [16:14] 15:00? [16:15] @now [16:15] It's 15.15 in UTC [16:15] thought so [16:15] ok thanks [16:15] I guess I could have looked at the schedule [16:15] oh well [16:15] sorry for wasting you guys time [16:15] we are here anyways [16:16] The schedule on https://wiki.ubuntu.com/UbuntuOpenWeek doesn't say it's canceled. Is it tehn? [16:16] the new ubuntu looks nice [16:16] got it running in qemu [16:17] first one to successfully run in qemu for me [16:17] bahadunn: what problems did you have with other distros in qemu? [16:18] FayZee_: some funky error that I cannot recall [16:18] bahadunn, did you try Mandriva Spring 2007 or even the lately released 2008? [16:19] FayZee_: no [16:19] FayZee_: I have strong hate for mandriva [16:20] FayZee_: debian runs fine on the qemu and also debian/kfreebsd runs fine on the qemu [16:20] Hi guys - could you move chat to the -chat channel please? [16:21] So is Launchpad Personal Package Archives officially canceled/postponed? [16:21] Sorry [16:21] FayZee_: I'm going to set it as cancelled. Unfortunately, I can't find the person who was due to give it. === Martinp24 is now known as Martinp23 [16:36] annma: hi [16:37] jcastro: hi [16:37] jcastro: my plane was cancelled [16:37] I could not even reach Paris [16:37] yikes! [16:37] big strike in France [16:37] I mailed the travel agency but it looks I won't make it [16:37] :( [16:45] * Hobbsee waves [16:45] * DShepherd waves === neuro|irssi is now known as neuro_ [16:48] Hey all, it seems like the session got cancelled, but if you have questions about ppa's, some of us around should be able to answer them. [16:49] wont be a normal session, i know. but it seems that some people have turned up. [16:50] is it possible to have a team ppa just be an aggregate of its members ppa? [16:51] I dont think so. [16:51] is there a limit on the amount of space one is allotted for a ppa? [16:51] DShepherd, about a Gb or so i "think" but it can be enlarged on request. [16:52] DShepherd: it appears to be 1gb, but I dont think they've done the quotas yet, as people can't remove things. [16:52] * DShepherd goes to check the size of assault cube [16:55] do you think it's OK for a project to be "served" only through a PPA or should better opt to be included in the official repositories nad use the PPA only for testing (and other) purposes? [16:55] when is the mythbuntu session?? its 16:55 pm at the moment. [16:55] @now utc [16:56] brobostigon: 2 hours [16:56] kostkon: well PPA's are still in beta, and aren't 100% reliable yet. but it should be OK for a small project [16:56] so 19:00 pm [16:56] Current time in Etc/UTC: October 26 2007, 15:55:51 - Next meeting: Kernel Team in 4 days [16:56] kostkon: if you put it into the official repositories, you're going to be able to reach everyone - whereas if you only have it in a ppa, they have to manually edit the lines of their sources list, to include the repository. [16:56] kostkon: for that reason, you're probably better off putting it into ubuntu. [16:57] kostkon: but, either works. As for speeds and such for downloading, I couldn't tell you. [16:58] any more questions? [17:00] Can I have a pony? [17:00] PriceChild: Yes, but only if you wash the dishes [17:01] PriceChild: no. [17:01] Okay, are you ready to rock? Or at least to have a session about Launchpad Translations? [17:01] @pony | PriceChild [17:01] mrevell: sounds good. over to you :) === PriceChild changed the topic of #ubuntu-classroom to: Ubuntu Open Week info: Information and Logs: https://wiki.ubuntu.com/UbuntuOpenWeek | Ubuntu classroom transcripts: https://wiki.ubuntu.com/ClassroomTranscripts | Please ask questions in #ubuntu-classroom-chat not here | Current Session: Introduction to Launchpad - Matthew Revell [17:01] :) [17:01] Hello! My name is Matthew Revell and I work for Canonical as part of the Launchpad team. [17:02] Welcome to this session, which is all about one of Launchpad's applications, Translations. [17:02] I'm going to introduce you to Launchpad Translations and tell you: [17:02] * what it does [17:02] * how it works [17:02] * a little about how Ubuntu uses it. [17:03] I'll also be pleased to take your questions at the end of the session. [17:03] However, the developers who work on Launchpad Translations are in a high intensity sprint right now, so I may have to pass on some questions. That's not to say you won't get an answer! [17:04] But I may ask you to mail me [17:04] Most week days you can find me as mrevell on Freenode. I hang out in #launchpad. [17:04] You can also email me - matthew.revell@canonical.com. [17:04] You can get in touch with the Launchpad team by sending an email to feedback@launchpad.net [17:05] Okay, so let's get going! [17:05] [17:05] A quick overview of Launchpad Translations [17:05] ------------------------------------------- [17:05] [17:05] One of the great advantages that the open source development model gives us is that it's relatively easy for people who use software to translate it into their own language. [17:06] Much free software uses GNU GetText for localisation. [17:06] Developers put markers in their code to show where a GetText should insert strings of interface text. [17:06] So, if I'm using some software in Spanish, GetText will insert the appropriate Spanish interface text. [17:07] If, however, I'm using Hindi, GetText will insert the Hindi text. [17:07] GetText has a simple file format where people can specify which text should be presented for each language. [17:07] All that a translator needs to know is what the original English text means and how to translate it into their own language. [17:08] However, this way of working means that translators need to download each GetText file and work alone. [17:09] It also means that translators have to work like coders - they need to learn how to use GetText's file format, they may need to learn how to use whatever version control system the project uses and, in many cases, get write access to it. [17:09] Launchpad Translations takes the pain out of translating software into different languages. [17:09] Using a simple web interface, it makes it easy for people to translate just one line of text (what Launchpad Translations calls a string) or take an entire project and translate it into their language. [17:10] It can import and export GetText's file formats, making it ideal for translating a huge number of free software projects. [17:10] It can even make suggested translations. [17:10] [17:11] People power [17:11] ------------ [17:11] [17:11] Right now, Launchpad Translations has: [17:11] [17:11] * 25,223 translators [17:12] * working 243 languages [17:12] * with 833,733 strings of translated text. [17:12] [17:12] It's probably fair to say that more people are working to translate free software using Launchpad than in any other single way. [17:12] This brings with it huge advantages, both for Ubuntu and the other projects using Launchpad for translations. [17:12] For example... [17:12] When the Jokosher audio editor started using Launchpad for translations, the Jokosher team didn't actually tell anyone. [17:12] They simply put their translation templates online in Launchpad and left them. [17:12] Within a couple of weeks they had translation efforts in 18 different languages! [17:13] The community of translators using Launchpad is large but, also, Launchpad makes it incredibly easy to translate software. [17:13] [17:13] Simple web interface [17:13] -------------------- [17:13] [17:13] Let's take a look at Ubuntu's page in Translations: [17:13] [17:13] https://translations.launchpad.net/ubuntu [17:13] [17:14] Straight away, if you're looking to translate parts of Ubuntu into your language you can see how much work needs to be done for Gutsy. [17:14] Let's pick Esperanto: [17:14] [17:14] https://translations.edge.launchpad.net/ubuntu/gutsy/+lang/eo [17:14] [17:14] You can see various different packages in Gutsy and how well translated into Esperanto they are. [17:14] [17:14] Green, purple and light blue all represent translated text. [17:15] Red means that there's still work to be done. [17:15] Now, you can find which Gutsy package needs you most and dive in! [17:15] You see that most of "yelp" has been translated but not quite all. [17:15] Let's dive in and have a look and what needs to be done. [17:15] [17:15] https://translations.launchpad.net/ubuntu/gutsy/+source/yelp/+pots/yelp/eo/+translate?batch=10&show=untranslated [17:15] [17:15] These are all the "yelp" strings that remain untranslated in Esperanto. [17:15] [17:15] As you can see, Launchpad shows you the English and gives you a text box in which to make the Esperanto translation. [17:16] At the top is "Page not found". [17:16] If we knew the Esperanto equivalent for that phrase, we could type it in, scroll to the bottom of the page and click "Save and continue". [17:16] Simple! [17:17] [17:17] Suggestions [17:17] ------------ [17:17] [17:17] As you probably realise, the same phrases crop up in software quite often. [17:17] Take a look at the fourth translation down on the page we've just been looking at: [17:17] "File not found" [17:17] There isn't a translation yet for the "yelp" package but Launchpad has seen "File not found" translated into Esperanto before. [17:17] So, it makes a suggestion. [17:17] In fact, it makes several and tells us which package each comes from and who made the translation. [17:18] Ne trovis dosieron - Used in kbabel in Ubuntu Dapper package "kdesdk" by Donald Rogers on 2007-07-30 [17:18] Netrovita dosiero - Used in gqview in Ubuntu Gutsy package "gqview" by Antonio Codazzi (la Filozofo) on 2007-06-11 [17:18] ERARO: dokumento ne trovita - Used in koffice in Ubuntu Gutsy package "koffice" by Steffen Pietsch on 2006-04-21 [17:18] Dosiero ne trovita: - Suggested in ooo-basic in Ubuntu Breezy package "openoffice.org2" by Leo on 2006-03-20 [17:18] [17:18] Now, I can decide which of these I want to use and judge which one might be best according to where it was used and who made the translation. [17:18] [17:18] hi [17:19] Translation teams [17:19] ----------------- [17:19] [17:19] Ubuntu has a number of translations teams. [17:19] This is controlled using something we call 'Translation Groups'. [17:19] You can see Ubuntu's translations groups at: [17:20] https://translations.launchpad.net/translations/groups/ [17:20] This provides a mapping between languages and the teams that translate are responsible for translating them. [17:20] Translation teams look after the QA of translations. [17:20] Members of translation teams should *only* be trusted translators: they will have full power over translations for that language, and you should NOT let anyone in. [17:21] Some upstreams have complained about bad translations, and most of them were due to badly managed teams (i.e. teams allowing anyone in). So, be strict about who you let in :) [17:21] At the moment, to organise work you need to coordinate outside Launchpad: use mailing lists, IRC, Jabber or whatever. We will be solving this. [17:22] When you make a translation on an Ubuntu package, most of the time you're actually making a suggested translation. [17:22] A member of the appropriate translation team will then approve or decline your text. [17:22] ja, in opleiding maakt dat toch nog geen zak uit want ge doet toch niks [17:22] This makes sure that anyone can get involved, with minimal effort, but helps maintain the quality and consistency of translations. [17:23] However, if you are a member of the translation team you can submit translations directly. [17:23] [17:23] Future [17:23] ------ [17:23] [17:23] We've got big plans for the future, and some of the priorities are the following: [17:23] [17:23] Search for translations (yes, infamous bug 44 in LP) [17:23] Native support for other translation formats (Mozilla, OpenOffice.org...) [17:23] Improved mechanisms for upstream cooperation [17:24] Make team management more flexible and powerful [17:24] We welcome suggestions on what should we focus on!. [17:24] [17:24] Trivia and tips [17:24] --------------- [17:24] [17:25] This section comes from our the Launchpad Translations developers and it's their tips and tricks for using LP Translations. [17:25] When uploading, choose 'Published upload' if you don't want to override others' translations that have happened in the meantime. [17:25] You can download PO files to find a specific string in it (many have done this already) [17:26] For Ubuntu, start translating from the top of https://translations.beta.launchpad.net/ubuntu/feisty/+lang/sr (for Serbian): they are sorted by priority. [17:26] Sorry, that URL should be: [17:27] https://translations.launchpad.net/ubuntu/feisty/+lang/sr [17:27] Don't forget to update Last-Translator field when translating via PO files, and also never remove or change X-Rosetta-Export-Date field from PO header (or you won't be able to re-import it). [17:27] Use Google with "site:translations.launchpad.net" to search for strings as a workaround. This will commonly give you pointer to someone's translations page, but you can pick a template name from there, visit it, and switch over to your own language. [17:27] regards from Serbia [17:27] You can use [nbsp] to get non-breaking spaces if you've got problems inserting them directly (Firefox is known to be buggy with them). [17:28] No need to email us back with 'thank you' for automatic exports (though, we indeed appreciate those :). [17:28] When you get message that your language is missing plural forms, either email us at feedback@launchpad.net, or file a ticket using https://answers.launchpad.net/rosetta/ [17:29] [17:29] Finding out more about Launchpad [17:29] ----------------------- [17:29] [17:29] #launchpad here on Freenode is where you can find Launchpad developers. [17:30] The launchpad-users list is also a great place to discuss Launchpad, get help from members of the team and make suggestions. [17:30] You can sign up at: [17:30] http://lists.ubuntu.com/mailman/listinfo/launchpad-users [17:31] There's documentation at: help.launchpad.net - I'm personally working on that and appreciate any suggestions you may have. [17:31] And if you want to get to try out new Launchpad features before anyone else, you can join the Launchpad Beta Testers team. Here's a guide for signing up: [17:31] https://help.launchpad.net/JoiningLaunchpadBetaTesters [17:31] [17:32] Well, I seem to have finished somewhat early. So, if you have any questions, please fire away! Although, as I say, the Translations developers aren't available at the moment, so I may have to come back to you with answers. [17:34] QUESTION: How do you solve conflicts between translations in LP and those of upstream? [17:35] samgee: For Ubuntu packages, translations made in Launchpad take priority. We don't send translations upstream automatically, although they can of course export translations from Launchpad. Better coordination with upstreams is an area that we're going to work on over the coming months, I believe. [17:35] Question: Is there a list of file formats that can be converted to .po files? [17:38] spd106: I'm told that the best place to start is the Translate Toolkit at http://translate.sourceforge.net/ [17:39] Any more questions? [17:41] QUESTION: Do translation for each release stop after 18 months? What about LTS? [17:41] spd106: You can continue with translation so long as the Ubuntu release is supported. [17:49] Thank you everyone for attending this session. I'll be back at the top of the hour for the BLueprint session. Right now, I need to go get a drink, so I'll see you in 11 minutes! [17:50] Thanks mrevell. [17:53] mrevell, are you doing "Planning features and sprints in Launchpad" as well? [17:55] PriceChild: I am [17:55] cool :) === PriceChild changed the topic of #ubuntu-classroom to: Ubuntu Open Week info: Information and Logs: https://wiki.ubuntu.com/UbuntuOpenWeek | Ubuntu classroom transcripts: https://wiki.ubuntu.com/ClassroomTranscripts | Please ask questions in #ubuntu-classroom-chat not here | Current Session: Planning features and sprints in Launchpad - Matthew Revell === Black_Ch2os is now known as Black_Chaos [18:00] Right, who's ready to rock? [18:00] Etc [18:00] :) [18:01] Hello! My name is Matthew Revell and I work for Canonical as part of the Launchpad team. [18:01] Welcome to this session, which is all about one of Launchpad's applications, Blueprint. [18:01] I'm going to introduce you to Blueprint and tell you: [18:01] * what it does [18:01] * how it works [18:01] * a little about how Ubuntu uses it. [18:02] I'll also be pleased to take your questions at the end of the session. [18:02] Before I continue, I want to let you know how you can get in touch with me and the Launchpad team. [18:02] Most week days you can find me as mrevell on Freenode. I hang out in #launchpad. [18:03] You can also email me - matthew.revell@canonical.com. [18:03] You can get in touch with the Launchpad team by sending an email to feedback@launchpad.net [18:03] Okay, so let's get going! [18:03] [18:03] What is a blueprint? [18:03] --------------------- [18:03] [18:03] In the design of physical objects, a blueprint is a plan of action. [18:03] [18:04] It takes the ideas of an individual or group of people and turns them into dimensions, angles, materials and so on. [18:04] [18:04] A blueprint in Launchpad is similar: it helps individuals and groups of people to tell the world about an idea, a new feature or an entirely new project. [18:05] The important difference between a traditional blueprint and the blueprints in Launchpad is that Launchpad's blueprints don't end with publication. [18:05] Instead, a blueprint in Launchpad tracks the progress of an idea from conception to implementation. [18:05] Sound complicated? [18:05] Don't worry: it's not at all :) [18:05] We've designed Blueprint - the Launchpad application - to be as simple as possible. [18:06] If all you want is to write a few sentences describing your idea and then publish it, you can do that with Blueprint. [18:06] If, however, you want to: [18:06] [18:06] * track who is responsible for implementation and approval [18:06] * link the blueprint to a branch of code that implements it [18:06] * target your blueprint to a particular software release [18:06] * track the dependencies required for your blueprint's implementation [18:06] * and more.... [18:06] [18:06] ...then Launchpad Blueprint can help you with those too. [18:06] [18:07] Blueprint doesn't force any particular project management methodology on you. Instead, it allows you to use however much or little you want. [18:07] [18:07] Let's take a closer look [18:07] ------------------------ [18:07] [18:07] Each Blueprint belongs to a particular project. [18:07] That means you can see lists of all the ideas, proposals or suggestions that are "out there" for a given project. [18:08] For example, Ubuntu has more than 1,000 such blueprints, in various states of completion or discussion: [18:08] https://blueprints.launchpad.net/ubuntu [18:08] [18:08] Each Blueprint has a priority, a "definition" status, and a "delivery" status. [18:08] [18:08] Anybody can contribute Blueprints for any project - there is no way to prevent someone from posting their ideas. [18:09] [18:09] However, the project leaders can set the priority - which means the extent to which they endorse the idea, or think it is important to implement soon. [18:09] The "definition" status tells you whether or not the project has reached consensus on how the idea should be implemented. [18:09] [18:10] In some projects there will be a person, or team of people, who will approve the plan. [18:10] In others, plans are considered unnecessary or harmful, so this value is less important. [18:10] In Ubuntu, they try to have a senior contributor review and approve any significant piece of work that is planned for any given release. [18:10] Of course, lots happens without these plans, but it does give some certainty that the various plans gel well, and that people have thought about the most important issues before they commit to getting something done in a particular release. [18:10] [18:11] Finally, the "delivery" status is all about implementation and execution. [18:11] It tells you whether the work has been done, or whether it is on track to be done. [18:11] Each blueprint also has a: [18:11] [18:11] * "Drafter" - the person who is responsible for setting out the idea [18:11] * "Assignee" - the person who is going to implement the ideas set out in the blueprint [18:11] * "Reviewer" - the person who'll check the work on the blueprint. [18:11] [18:12] You can see these in the top right of the page, alongside the implementation status, priority and a definition. [18:12] Where to put the details [18:12] ------------------------- [18:12] [18:12] Launchpad itself only contains a summary of the Blueprint - usually just the introductory paragraph - and then a URL to the location of the real document. [18:12] [18:13] In some cases, the single paragraph (or sentence) is enough, but it's more typical to keep the full document in a wiki, where members of the community can easily collaborate. [18:13] [18:13] Just having a list of proposals and ideas in one place is useful, even if, as in the case of Ubuntu, there are clearly many more ideas than developers! [18:13] [18:13] It's convenient to be able to point new members of the community at a single place where those ideas are catalogued and to allow people to gravitate towards the pieces they are most interested in. [18:13] [18:13] People can subscribe to Blueprints and get notifications when their status changes and even when the wiki document they are in is updated. [18:13] [18:14] Newcomers can easily see which ideas are important to the project leaders, and which are not, so they can choose to focus their contributions on those pieces most likely to be accepted into the project. [18:14] [18:14] [18:14] Linking blueprints [18:14] ------------------ [18:14] [18:14] Launchpad allows you to link a blueprint and a bug, or a blueprint and a branch of code. [18:14] [18:15] This allows people to see how pieces of work relate to one another. [18:15] [18:15] It's very useful, for example, to be able to see the code that implements a blueprint evolving over time. [18:15] It's also possible to link blueprints to one another, indicating rough dependencies. [18:16] This lets you map out the order in which pieces of work should be implemented. [18:16] [18:16] Let's take a look at an example of the dependency chart that Launchpad produces: [18:18] https://blueprints.launchpad.net/ubuntu/+spec/printer-sharing [18:18] This is a very simple example. This particular blueprint depends on one other. The current blueprint is shown in red. The other blueprint is in grey, which shows that it has been implemented. [18:18] [18:19] Release management [18:19] --------------- [18:19] [18:19] The most useful aspect of Launchpad's blueprint tracker, however, is the ability to group the blueprints that describe chunks of work that the project thinks are important to track for the next major series. [18:19] [18:20] Here's the list for Gutsy: [18:20] https://blueprints.launchpad.net/ubuntu/gutsy [18:20] [18:20] These are blueprints that have been reviewed by the team [18:21] and that they agreed should be worked on during the Gutsy cycle. [18:21] In general, about 80% of the planned feature goals have landed in each Ubuntu release. [18:21] Ubuntu choose to ship on time, rather than necessarily waiting till every feature lands. However, different projects can adopt different release management goals. [18:22] The important thing, of course, is that everyone can see where the project stands on any particular item. [18:22] Sometimes you may want to group just the blueprints that are relevant for an interim release. For that, Launchpad has what we call milestones. [18:23] [18:23] Milestones [18:23] ------------ [18:23] [18:23] We've discussed projects and series, which are the major ways in which we keep track of the progress of a free software project in Launchpad. [18:23] [18:24] Milestones are a very lightweight way to organise a group of bugs or blueprints. [18:24] A milestone is a point in time, or a test release, for which you need to keep track of a few bugs or blueprints. [18:24] [18:24] In Launchpad, you can easily create a milestone, and then link bugs or blueprints to that milestone as a way of saying "we think these items are worth keeping track of as we get closer to that date". [18:24] [18:25] Here's an example milestone. It's the 1.1.11 milestone for the whole Launchpad project and is what we're working on now, due for release in November: [18:25] https://launchpad.net/launchpad/+milestone/1.1.11 [18:25] [18:26] As you can see on that page, there are a number of blueprints targeted against the milestone, just as there were earlier when we look at Gutsy's blueprints. [18:27] In the Launchpad team, we make a new release every four to five weeks. This means that we're making iterative improvements to Launchpad quit frequently. So, each release isn't a major release. [18:28] Bug<--->Blueprint links [18:28] ----------------------- [18:28] [18:28] Earlier, I menetioned that you can link bugs and blueprints. [18:28] Let's take a look at the Bazaar project for an example. === pleia2_ is now known as pleia2 [18:29] https://code.launchpad.net/bzr/ [18:29] [18:30] This is a list of all the branches of the Bazaar project that Launchpad knows about. [18:30] Scroll down and you'll see three types of icon beside the branch names: [18:30] * A small bug. [18:30] * A warning triangle. [18:30] * Some blue papers. [18:30] [18:31] That last one is indicates that the branch is linked to a blueprint. [18:31] [18:31] Sprints and meetings [18:31] ------------------- [18:31] [18:32] Many free software projects use real-world meetings to thrash ideas or as development sprints. [18:32] Launchpad helps you to organise such meetings and use a list of blueprints as the meeting's agenda. [18:33] Ubuntu's six-monthly Ubuntu Developer Summits are an ideal example of such a meeting. [18:33] Let's take a look at what's planned for next week's UDS in Cambridge, Massachusetts. [18:34] https://launchpad.net/sprints/uds-boston-2007 [18:34] [18:35] Using the two panels in the left-hand sign of the page, you can see when the meeting is, who's organising it and who is attending. [18:35] You can also sign yourself up as an attendee. [18:35] In the central part of the page is a "full current agenda" link, which takes us to: [18:35] https://launchpad.net/sprints/uds-boston-2007/+specs [18:35]