Kubuntu Tutorials Day

June Team Reports

The following message was recently sent out to the loco-contacts mailing list. For those of you who might not subscribe to that list, I am reposting the message here.

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA256

Hello,

As the month is starting to reach its end, it is time to get your team
reports finished up. Last month, I proposed switching to a new style [1]
for team reports that takes advantage of include tags on the wiki. Since
then, over a dozen teams have switched to the new style. For those teams
that have switched, there is no longer a need to copy your reports to the
collective team report page for June [2]. However, you still need to ensure
that you have updated your report to include all of your team’s activities
for the past month. If you have not switched to the new reporting style, I
would strongly urge you to do so. It will make team reports easier for both
you and me. However, if you insist on using the older reporting style, please
remember to copy your report over to the collective team report. These team
reports will show up in the Ubuntu Weekly Newsletter [3] and several blog
posts on the Planet. They are a great way to let the rest of the community
know what your team has been up to. If your team is currently not creating a
team report each month, you can read [4] to get started. The goal is to have
all teams produce a team report each and every month.

Thanks,
Nathan Handler

[1] https://wiki.ubuntu.com/BuildingCommunity/TeamReporting/HowTo
[2] https://wiki.ubuntu.com/TeamReports/June2009
[3] https://wiki.ubuntu.com/UbuntuWeeklyNewsletter
[4] https://wiki.ubuntu.com/BuildingCommunity/TeamReporting
—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.4.9 (GNU/Linux)

iQEcBAEBCAAGBQJKPEUYAAoJECM1+z85M6fOxjsH+wUDkgQZLZ0fhbOUNOBkGe/r
jNsxvx8YIbHv55j/IOdR1Xw9hyWQtg7DU8/mWK+5uOJJyvh3dLP9+Gvda9Ba2uLx
UpgM+qaDElYTignk1BgSwz2hftx8xflpRJRYnqELyJv9KVCK6qzYd1HhXvIAidSD
r/Ci3OxTxlHMAxktfwsq+A/yFpIeGjD1moQJX3aB8hY9OheaABBMD5VvJ9xiHYBR
czuDETf7y9oS67FccUAZnMr4O9SY5bUdnm+MyBc7yizq3vf5ftO0/vYPtAUS8SmB
iplGfTIlGcpyKpdqV7kFVC4f3pwxyvkLb7Gk1jNWrRb8Gxaw8re8sdr8eX3oxVk=
=Mkq9
—–END PGP SIGNATURE—–

Ubuntu Global Jam

In order to help get the word out, we are encouraging all users to blog about the Ubuntu Global Jam. This event used to be called the Ubuntu Global Bug Jam. However, in order to make the event even better, and to open it up to a wider audience, we have decided to rename it to the Ubuntu Global Jam, and to focus on more areas of contributing than just bugs. If your LoCo is interested in participating in this event, please add an entry to the correct table on the wiki. Even if you are unable to fill out all of the columns right now, please add an entry. This will allow us to get an idea for how many teams are interested and planning on participating. If you have never run a jam like this before, information is available on the wiki. There will also be meetings on the third Thursday of every month in #ubuntu-meeting on Freenode to help plan and prepare for the jam. These meetings are a great place to share any ideas that you might have on how to make the jams even better. Finally, there will also be several IRC sessions and live streams coming up in the next few months (thanks to Jorge Castro and Jono Bacon) about how to run a successful jam. I would strongly encourage anyone who is running a jam to try and attend at least one of these sessions. The dates for the sessions can be found on the bottom of this wiki page. Once again, please spread the word about Ubuntu Global Jam to as many people as you can. Blog/Tweet/Dent about it, send an email to your LoCo mailing list, tell people about it on IRC, or even tell people in real life. The more people that participate, the bigger a success this event will be.

Ubuntu-Chicago Key Signing / Planning Event

For anyone living in or near Chicago, we will be holding a Key Signing / Planning event on Sunday, June 28th, from 2:00 pm untill 6:00 pm. The event will take place at onShore Networks: 1407 W Chicago Ave., Chicago, IL 60642. Here is the email that got sent out to the mailing list the other day

On Sunday, June 28, from 2:00 pm until 6:00 pm, we will be holding
the first Ubuntu Chicago event of the Summer [1]. This event will
serve two purposes. It will be a key signing party as well as a
planning meeting. Key signing parties are a great way to extend the
web of trust. This is very important if you are involved in
Ubuntu/Debian development, since GPG keys are used to verify your
identity and allow developers to upload to the repositories. In order
to ensure that this key signing event goes smoothly, please be sure to
bring some government issued identification in order to allow other
people to verify your identity. Also, please print out your GPG key
fingerprint, which can be generated with 'gpg --fingerprint <KEYID>'.
So for me, I would enter 'gpg --fingerprint 3933A7CE'.

Besides the key signing portion of the event, we will also be taking
time to plan some future events. These events will include
Packaging/Bug/Documentation Jams, as well as several other activities.
If you have some ideas for future sessions that we should hold, or are
interested in helping to lead one of these sessions, please let us
know at the meeting.

The owners of onShore Networks have kindly permitted us to use their
offices for our meeting. Therefore, the upcoming meeting will take
place at onShore Networks [2]: 1407 W Chicago Ave., Chicago, IL 60642.
We hope to see you all there.

[1] https://wiki.ubuntu.com/ChicagoTeam/Projects
[2] https://wiki.ubuntu.com/ChicagoTeam/Meetings/MeetingLocations#onShore%20Networks

If you know anyone who lives in the area and would be interested in attending, please pass this information on to them. The event is open to anyone, and we hope to see a nice turnout.

2Wire 802.11B USB Wireless Adapter

I have had an old desktop computer sitting on the floor beneath my desk for a while now. Since it did not have access to the internet, I was limited in what I could use it for. I recently got back my old 2Wire 802.11B USB Wireless Adapter, which I had lent to a relative. I have been spending the past few hours searching the web to try and get it working with Ubuntu 9.04. So far, I have been unsuccessful. I figured that I would try and ask the lazyweb for help. If anyone out there has gotten this wireless adapter working with Ubuntu, I would greatly appreciate it if you could outline what you did in the comments. Thanks a lot!

A Few Ubuntu-related Bookmarks

Andrew recently blogged about some Ubuntu-related Ubiquity Scripts that he made. I personally find that Ubiquity gets in the way of my normal workflow. For the past year or so, I have been using special Firefox bookmarks to easily and quickly access various Ubuntu/Debian resources. Let me start with an example.

In many debian/changelog entries, people will use (LP: #123456) to close a bug on Launchpad. I created a bookmark that would allow me to type ‘lp 123456′ in my address bar, and be instantly taken to that bug on Launchpad. This is what the bookmark looks like:

Name: Launchpad Bug

Location: https://launchpad.net/bugs/%s

Keyword: lp

Did you notice the %s in the Location field? That will be replaced by any text after the keyword. So in the above example where I entered ‘lp 123456′, the %s would be replaced by 123456.

Here are some other special bookmarks that I have created; please note, I am only going to post the bookmark Name and Location fields. It should be pretty obvious what the bookmark does, but if you have any confusion, please ask in the comments.

—————————————————–

Name: apt-url

Location: apt:%s

—————————————————–

Name: Search packages.debian.org

Location: http://packages.debian.org/search?keywords=%s

—————————————————–

Name: Launchpad Person/Team

Location: https://launchpad.net/~%s

—————————————————–

Name: Report a bug

Location: https://bugs.launchpad.net/ubuntu/+source/%s/+filebug

—————————————————–

Name: Source package in Ubuntu

Location: https://launchpad.net/ubuntu/+source/%s

—————————————————–

Name: Bugs with Tag in Ubuntu

Location: https://bugs.launchpad.net/ubuntu/+bugs?orderby=-datecreated&field.tag=%s

—————————————————–

Name: Debian Bug

Location: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%s

—————————————————–

Name: Debian Package Tracking System

Location: http://packages.qa.debian.org/common/index.html?src=%s

—————————————————–

Name: Search packages.ubuntu.com

Location: http://packages.ubuntu.com/search?keywords=%s

—————————————————–

Name: Ubuntu Manpage Search

Location: http://manpages.ubuntu.com/cgi-bin/search.py?q=%s

—————————————————–

Name: REVU Package

Location: http://revu.ubuntuwire.com/p/%s

—————————————————–

I hope that you all enjoy these bookmarks.

Internet speed meme

Continuing the recent internet speed meme, I decided to see what Speedtest.net had to say about my download/upload speeds. Here are my results:

Debian pkg-perl team

In order to start contributing more to Debian, I have started helping out with the pkg-perl team. I sent an email to the mailing list, and was quickly added to the team on Alioth. Using dh-make-perl, I was able to quickly package my first Perl module. Then, by following the subversion guide, I was able to upload it to the svn repository used by the team. The package was quickly reviewed by a Debian Developer on the pkg-perl team, and once all necessary changes were made, the package was uploaded.

Since then, I have worked on several other Perl modules. All of them were quickly reviewed, and sponsored once correct. The other members of the team have been very kind and helpful with answering any questions I might have.

If you are looking for a way to start contributing to Debian and have an interest in Perl, I would strongly recommend joining the pkg-perl team.

Team Reporting

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA256

Hello everyone,

At Nick Ali’s request, I will now be be managing the Team Reports [1].
I would like to take this time to mention a few things other things
concerning the reports. First, as the month of May comes to an end, it
is time to update your team’s report page. Be sure to also update the
collective team report page [2] for May.

In an effort to make it easier for teams to maintain their report
pages, I am proposing moving towards a new reporting style that takes
advantage of the ‘Include’ feature on the wiki. Details about how to
use this new style can be found at [3]. If you switch to this new
style, it will no longer be necessary to update the collective team
report [2] each month.

Thanks,
Nathan Handler

[1] https://wiki.ubuntu.com/TeamReports
[2] https://wiki.ubuntu.com/TeamReports/May2009
[3] https://wiki.ubuntu.com/BuildingCommunity/TeamReporting/HowTo
—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.4.9 (GNU/Linux)

iQEcBAEBCAAGBQJKF19qAAoJECM1+

z85M6fO9GcH/AuSF/kBdShdn2Wuo2i83/6A
ta7RnWYmXt4hKNuEtoA+KSCwOqmquuFgezHZN/dAMeFJ0/lEhJT0Kt/EYVsMV/2q
4qRTAZ92TFehSIntFNvukrADnZHww7xnW/9xKda81pdOrTv14MOCR9T2chbSEel6
bTBII8ebQ2bh4tLWrLB5A5WXg81VA9XXw/1wkvB6SjOvwovIr2a7I7vCms8RUCBO
Zwr7/cbAeUxiNCRQ4/pAdLG78BixaA6DbH0At96xsWUjhkCrInL0pctblRY6h/Jd
ZwbB4sponSH9ZXEYJRhUKaFVF8PLOeLTWqSfUfugGMLRjz0C+FVATqowm83NP8o=
=hICT
—–END PGP SIGNATURE—–

New GnuPG Key

—–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA256

- —–BEGIN PGP SIGNED MESSAGE—–
Hash: SHA1

Sun, 10 May 2009 15:15:15 -0500

Because of the recently announced attack [0] against the SHA-1 digest
algorithm, I finally decided to move away from my old 1024-bit DSA
OpenPGP key, landing to a shiny new 2048-bit RSA one.

[0] http://eurocrypt2009rump.cr.yp.to/837a0a8086fa6ca714249409ddfae43d.pdf

The old key will continue to be valid for some time, but I prefer all
future correspondence to come to the new one. I would also like this
new key to be re-integrated into the web of trust. This message is
signed by both keys to certify the transition.

The old key was:

$ gpg –with-fingerprint –list-keys 57F795E8
pub   1024D/57F795E8 2008-04-25
Key fingerprint = 2CA5 1131 578D 9175 0A54  B0E8 4BB3 6254 57F7 95E8
uid                  Nathan Handler <nhandler@ubuntu.com>
uid                  Nathan Handler <mrcheatr@gmail.com>
uid                  Nathan Handler <nathan.handler@gmail.com>
uid                  Nathan Handler <nhandler@kubuntu.org>
uid                  Nathan Handler <nhandler@nubuntu.org>
sub   2048g/B980FFDC 2008-04-25
$

And the new key is:

$ gpg –with-fingerprint –list-keys 3933A7CE
pub   2048R/3933A7CE 2009-05-10
Key fingerprint = F30E EA8C 3446 F59E F0DB  433C 2335 FB3F 3933 A7CE
uid                  Nathan Handler <nhandler@ubuntu.com>
uid                  Nathan Handler <mrcheatr@gmail.com>
uid                  Nathan Handler <nathan.handler@gmail.com>
uid                  Nathan Handler <nhandler@nubuntu.org>
uid                  Nathan Handler <nhandler@kubuntu.org>
$

To fetch my new key from a public key server, you can simply do:

gpg –keyserver keyserver.ubuntu.com –recv-keys 3933A7CE

If you already know my old key, you can now verify that the new key is
signed by the old one:

gpg –check-sigs 3933A7CE

If you don’t already know my old key, or you just want to be double
extra paranoid, you can check the fingerprint against the one above:

gpg –fingerprint 3933A7CE

If you are satisfied that you’ve got the right key, and the UIDs match
what you expect, I’d appreciate it if you would sign my key:

gpg –sign-key 3933A7CE

Lastly, if you could upload these signatures, I would really appreciate
it. You can either send me an e-mail with the new signatures (if you
have a functional MTA on your system):

gpg –armor –export 3933A7CE | mail -s ‘OpenPGP Signatures’ nhandler@ubuntu.com

You could also use caff(1) from http://pgp-tools.alioth.debian.org/
(signing-party package on Debian GNU systems):

caff 3933A7CE

Or you can just upload the signatures to a public keyserver directly:

gpg –keyserver keyserver.ubuntu.com –send-key 3933A7CE

Please let me know where you upload your signatures, if there is any
trouble, and sorry for the inconvenience.

Regards,
Nathan Handler
- —–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkoG9bYACgkQS7NiVFf3lejcWgCcDZszRcW9tcMklGbUl1B0xVo6
ogIAn2EkN1D1QqVllzz5QmBB/7m6lRrE
=+3uH
- —–END PGP SIGNATURE—–
—–BEGIN PGP SIGNATURE—–
Version: GnuPG v1.4.9 (GNU/Linux)

iQEcBAEBCAAGBQJKBvW+AAoJECM1+z85M6fOLacH/jtCoqlsmlfmtfcUzfcbO+LV
5FGAzD9Kb471xurp/SEEn7R4JOG9n7xsOQCwM9QOwYfnGilKXI2/gv3i5cmXYg4l
ITcdnVagh2AfRVjw5Az+Xee5kQoBqDNMFlmWkybK4aNSA679CWtgzRlF9pj99LwN
7Q0XEgdvDE1ZBwnSUXwgNBoRTopJN/tWqNDC5tKw0eozNV22qbf4kn81rmV2brNj
7xBqtXCNDELnHKFVPHFP2w4ahrlqHaWhFRQ4GeJrwnYg6lyBmHo/CJCBPa2shX+p
HGM9F/684oD1pTBRxylWYwteG75pJiFjShMe//Jj0ZBauenXH8IUZiImbyVdKXU=
=gcIP
—–END PGP SIGNATURE—–