Valpara so, Chile I love it when people understand that a happy hacker working at midnight is better than an unhappy hacker working on a set in stone schedule. Kudos to Igalia for that. Your code should explain and defend itself My written expression teacher says Your text should be good enough to explain and defend itself . This applies to code too. I confirmed this at the expense of Xan s patience. It s a common situation: when the maintainer reviews your patch you are not around to explain it, or present the rationale you put into the change. The solution? well, simple, your patch and commit log should explain by themselves.

Don t just post a patch and do this.
Review it yourself. I saw, after realising how much ping-pong Xan and I had to play to get a patch in, that my patches lacked a harder review by myself before being posted. You have to be your first reviewer. Be a severe judge of your patch, ask yourself if you would accept such a patch, if you would like a commit message like that, if that variable name is really good, if someone could quickly grasp what s it all about, etc. Get into the flippy flops of the maintainer, don t assume everything is obvious to everyone.

• #574192 typespeed: "typespeed: package purge (after dependencies removal) fails"
  apply patch for postrm from BTS and upload to DELAYED/2
• #574217 libpdl-netcdf-perl: "libpdl-netcdf-perl: package purge (after dependencies removal) fails"
  fix postrm and upload to DELAYED/2
• #576639 libpath-dispatcher-perl: "Path::Dispatcher::Declarative is now a separate distribution, breaks prophet"
  upload after the split-off package is ACCEPTED (pkg-perl)
• #577861 src:libpadre-plugin-vi-perl: "libpadre-plugin-vi-perl: FTBFS: tests fail"
  rules: run under xvfb (pkg-perl)
• #577890 src:libpadre-plugin-autoformat-perl: "libpadre-plugin-autoformat-perl: FTBFS: tests fail"
  rules: run under xvfb (pkg-perl)
• #577909 src:libpadre-plugin-xml-perl: "libpadre-plugin-xml-perl: FTBFS: tests fail"
  rules: run under xvfb (pkg-perl)

So it s no surprise that Google, like other technology and telecommunications companies, regularly receives demands from government agencies to remove content from our services. Of course many of these requests are entirely legitimate, such as requests for the removal of child pornography (1). We also regularly receive requests from law enforcement agencies to hand over private user data. Again, the vast majority of these requests are valid and the information needed is for legitimate criminal investigations. However, data about these activities historically has not been broadly available. We believe that greater transparency will lead to less censorship (2).

Do your statistics cover all categories of content removals? No. Our policies and systems are set up to identify and remove child pornography whenever we become aware of it, regardless of whether that request comes from the government. As a result, it s difficult to accurately track which of those removals were requested by governments, and we haven t included those statistics here.

* Chinese officials consider censorship demands as state secrets, so we cannot disclose that information at this time.

• [1] http://www.ted.com/talks/sam_harris_science_can_show_what_s_right.html
• [2] http://www.ted.com/talks/lang/eng/dan_gilbert_asks_why_are_we_happy.html
• [3] http://www.ted.com/talks/dan_barber_how_i_fell_in_love_with_a_fish.html
• [4] http://www.ted.com/talks/gary_lauder_s_new_traffic_sign_take_turns.html
• [5] http://www.ted.com/talks/alan_siegel_let_s_simplify_legal_jargon.html
• [6] http://www.ted.com/talks/tim_berners_lee_the_year_open_data_went_worldwide.html
• [7] https://penta.debconf.org/dc9_schedule/events/381.en.html
• [8] http://www.thebigmoney.com/articles/money-trail/2010/03/19/bust-out?page=full
• [9] http://www.ted.com/talks/mark_roth_suspended_animation.html
• [10] http://www.ted.com/talks/pawan_sinha_on_how_brains_learn_to_see.html
• [11] http://www.ted.com/talks/adora_svitak.html
• [12] http://www.nytimes.com/2010/04/04/magazine/04animals-t.html
• [13] http://browsershots.org/
• [14] http://www.publishersweekly.com/article/456751-Can_You_Survive_a_Benevolent_Dictatorship_.php

#!/bin/bash
set -e
set -u

var1="something with
space and
linefeeds"
var1=$ var1//
/_ 
echo $var1

VAR1=$ VAR1##sync:archive: 

1. In the 'main' stream, search a section that was filmed by the camera which we are trying to align.
2. Hit 'l' to create a label
3. Search for the exact same frame in the camera stream. It may help to disable playback for the 'main' stream temporarily to visually verify that the frame is the same in the compositor window.
4. Move the cursor to that frame, and create another label.
5. If the streams are indeed desynced, then one of the tracks will lead, and the other will follow. If the leading track is the 'main' track, arm the main track and any tracks that you have already synced before, and make sure to remember the audio tracks. If, on the other hand, this is the camera track, then only arm that camera track. At any rate, make sure to disarm the track(s) that are following.
6. Use the control and arrow keys to select the first label. Use control, shift, and the arrow keys to select the section up to the second label.
7. At the bottom right of the program window, you can see three entry boxes with time indexes. The first is the time index to your first label; the third the time index to your second label; an in between those, the second is the length of the interval from the first label to the second label. Set the contents of the first box to all-zeroes, to move the selection to the beginning of the time line; then press tab (to move to the second entry box) and enter (to confirm that you wish to create a selection of that length at the beginning of the timeline).
8. Press Shift-Space to insert silence at the location of the selection. This will move the armed tracks to the right, and not touch the not armed tracks.
9. If you did everything right, the two tracks should now be aligned. Move the cursor to the second label, and verify that this is true by disabling 'play' for the main track and any tracks in between the main track and the track you're syncing. The frame in the compositor window should not change if you re-enable the main track. If it does, use 'z' for undo, remove your labels and try again.

1. Select the region where you wish to select another camera.
2. Arm the camera track that you wish to copy from, and make sure not to arm any other track.
3. Hit 'c' to copy the clip at that point.
4. Disarm the camera track, and arm the 'override' track
5. Without moving or removing the selection, hit 'v' to paste onto the override track.

• Calendar or clock with alarms.
• E-book reader that syncs content from a server.
• IM or email client that notifies the user of new messages.
• Shopping list that pops up whenever you are near the store.

1. Because all web standards should have names that sound like Harry Potter creatures.

cdp ()  
  cd "$(python -c "import os.path as _, $ 1 ; \
    print _.dirname(_.realpath($ 1 .__file__[:-1]))"
  )"
 

$ cdp twisted.web
$ pwd
/usr/share/pyshared/twisted/web
$ ls
_auth/  domhelpers.py  html.py  iweb.py  resource.py
[..]

$ cdp subprocess
$ pwd
/usr/lib/python2.5
$ ls subprocess.py
subprocess.py

• [1] http://lwn.net/Articles/330985/
• [2] http://marc.info/?l=selinux&m=122538041011707&w=2

/join #debian-miniconf-berlin

/join #debian-miniconf-berlin

1. When you switch between Ubuntu and Windows, it won t boot the first time. Second and subsequent boots are fine, but the first one just reboots immediately. I suspect this would be the same for all GNU/Linux distributions.
2. I didn t realise that the current ndisgtk (or the underlying ndiswrapper?) couldn t use Win7 drivers. Once I downloaded some XP drivers, it worked. There are some native drivers for the rtl8192 but I didn t have time to go compiling on it yet.

WebKit2 is nothing more than the second version of that interface, with a whole lot of changes on what you can expect from it, and on how it interacts with WebCore, and the platform-specific API and UI. First of all, the first WebKit was not API stable, and that interface was usually not made public by the various ports - they only exposed their platform-specific APIs. WebKit2 is being designed to provide a stable, cross-platform, C-based, non-blocking public API. This is huge. It will allow cross-platform code to be written without having to consider language, and port differences for basic functionality. The second big change is the API will be made fully non-blocking. Currently most things you do are asynchronous already, but some of them may be completed in a synchronous ways (like, loading a string into WebKit instead of an URI). This is important for responsiveness, and is also a very important need for what comes next: process splitting. WebKit2 will bring into WebKit proper the concept of splitting the UI process from the Web process, similar to what Chromium has. It also much more awesome than what Chrome has for a large number of reasons, including, but not limited to:

1. It s being contributed directly to the WebKit project, in a cross-platform way that lets ports such as WebKitGTK+ take advantage of it, instead of being shipped directly into Safari, like Google does with Chrome;
2. The process separation goes bellow the API layer, meaning that all complexity involved in managing the process separation is handled by the library, and hopefully none of it leaks to the application using it; that means that applications like Devhelp and Yelp will be able to take advantage of this without having to make their lives more complicated;