If you don’t follow debian-vote, you have
missed this.
It’s really worth a read before casting your final vote on this issue. As I explained in my
reply to Russ, this vote is not about details but whether we want to have an intermediate level between DD and nothing, or not.
If you don’t give an initial policy, then people against DM will use that “hole” to block it because “it’s not how DM must be done” (and then you’ll need another GR to define a correct implementation and overrule those who are blocking). Yet people keep mixing issues when discussing DM. For some, DM is okay if we had a working NM system. For some, DM would be okay if the responsibility to give upload rights didn’t rely on DD but on a sort of QA committee. For some, DM would be okay if it were integrated in NM. There are also people who are opposed to this second class of contributors but I don’t think they are a majority. Still we might loose a nice opportunity because people want to solve too many things at once instead of doing a first step in a new direction.
Well, I am impressed. Iceowl slipped through NEW in just a few hours. Many thanks to our ftp-masters … well done!
Two screenshots Iceowl and its Icedove extension:
I've been busy doing various things, so I've not had a chance to
blog much lately. Time for a quick catch-up...
We've had a bit of a development panic at work, so I've been
working longer hours than normal. The scary thing is (and I've noticed
this in the past too), I seem to enjoy the job more when there's real
pressure involved. That's not to say I want it to
always be
stressful, but we've had more fun with a small group of us really
concentrating on a single project, working well together.
Outside of work, I've been really quite relieved to take a bit of a
break from Debian stuff since Debconf has finished. Debconf (as
always) was a really good way to be re-enthused about working on
Debian, but it has taken me several weeks to get over it
physically.
I've finally finished upgrading all of my machines at home to
Etch. In most cases it was easy, but the final one left was lump, the
firewall/mail/web/foo server. I'd chickened out of upgrading it
for quite a while due to the sheer number of services it hosts, and
also the substantial amount of local config it therefore holds. In the
end, things were thankfully mostly painless. The nice thing about
doing the upgrade was that finally lots of new software has suddenly
become readily available. Amongst other things, I've added iodine and
openvpn, and now I'm looking into playing with voice over IP (probably
Asterisk). My Nokia E70 has a VOIP client and wifi, so in theory I
should be able to use my regular mobile phone as a voip handset on my
wireless network at home and just get cheaper outbound calls. Yay!
I visited my friend Matthew a couple of weeks ago, and also helped
him upgrade/install his network of Debian machines. Unfortunately, his
main workstation (dual AMD64 goodness) is still left just running
Windows. BIOS/SATA RAID - just say NO! No matter what we did on that
machine, we could not make it dual-boot XP and Debian without forcing
him to reinstall it all from scratch. :-(
The SPI board elections have just
finished.
Congratulations to the new mugs^H^H^H^Hmembers of the board, and best
of luck in doing a good job. And comiserations to the people who lost
- I'm sure most of you would have been good, useful board members
too.
We're having a final Debconf 7 wrapup meeting next weekend in York,
where we're hoping to get the final conference report finished. There
are a few more T-shirts to get finished and delivered to people and
the sponsorship bags to go out, then it's all done for this
year. It'll be good to meet up with people again anyway.
Oh, and not long now until the
big BBQ at my
place. I've started getting some supplies in already, and I'm looking
forwards to a bunch of geeks coming round to wreck my house again. Or
something... *grin*
Last but not least - I'm changing ISPs shortly.
Noodles and
Huggie have provided
excellent service for nearly 3 years, but are exiting the business and
moving on to other things. So I'll be moving my home ADSL back to
UKFSN shortly. Hopefully the
disruption will be minimal.
* Yes, they can upload crappy packages but we can ask to revoke an account.
* Yes, they can upload crappy packages but someone must sponsor the 1st upload.
* Yes, they can upload crap but a DD is advocating them. If they are smart enough to fool a DD to get an DM account then they are smart enough to fool him for the DD process.
* Yes, they can seek sponsors but finding sonsors is not that easy (At least for me).
Perhaps there's a way to identify the DM uploads so we can do more checks "not part of the process" ?
read more
I recently received an email from
RSA inviting me to read their blog (after having requested an evaluation copy of one of their products). They invited me to “join the conversation“. Often blogs are described as a “conversation” and I’ve been considering whether that analogy is appropriate.
The Collaborative International Dictionary of English v.0.48 has the following definition: Usage: Conversation , Talk . There is a looser sense of these words, in which they are synonymous; there is a stricter sense, in which they differ. Talk is usually broken, familiar, and versatile. Conversation is more continuous and sustained, and turns ordinarily upon topics or higher interest. Children talk to their parents or to their companions; men converse together in mixed assemblies.
There are instances of blogging that can approximate conversation when bloggers cite each other’s articles in turn and leave comments on each other’s blogs. But it’s usually not that continuous and sustained. An occasional patterin is that blogger A writes a post, blogger B writes a post disagreeing with it, blogger A comments on blogger B’s post, and that’s usually the end of it. Usually it’s just a case of multiple bloggers writing posts representing their own opinions with occasional references to other blogs and no sustained interaction. The blogging interaction seems to more closely resemble academics presenting papers with alternate solutions to a problem than a conversation.
One factor that I believe defines conversation but which isn’t mentioned in the dictionary is that the parties involved have an equal standing. The comments section of a blog is not such a forum, the blogger has a significantly more powerful voice (at least in connection with their own blog) than the people who comment. Someone who posts a comment may have it deleted, and it if is left then a rebuttal in another post will be seen by a significantly larger number of people (the number of people who read comments on a post is a tiny minority of the people who read the post). This doesn’t preclude conversation between bloggers who are of equal popularity in a community, for example most readers of my blog come from
Planet Linux Australia and
Planet Debian so any blogger who is also syndicated on those sites has an equal voice to me.
Another factor in conversation is whether responses are even read. Many blogs don’t accept comments and it’s never certain that a blogger will see a track-back from a blog that references one of their posts. When one party ignores the other (or appears to do so) then there is no conversation.
I’m not aware of whether a conversation with RSA people would be possible. While their blog refuses to send content to my Planet installation I guess I’m not going to find out…
Is the lack of conversation a bad thing? One problem with conversation is that it often degenerates into what GCIDE defines as talk, while that is good for a friendly mailing list (EG your local LUG) it isn’t so good for the exchange of technical information. A compounding problem for mailing lists is the number of posts that can not be interpreted without the context of a thread of discussion. This often makes mailing lists unreasonably difficult to use in the search for answers to technical problems. When reading google search results I will usually read blog URLs before mailing list posts as a blog post will usually stand alone and either give me an answer or be obviously not related to my problem - sometimes I have to read a dozen messages in a list discussion to determine that it’s not going to help me!
To improve things in this regard I plan to increase the number of posts I write with solutions to random technical problems that I encounter with the aim of providing a resource for google searches and to randomly inform people who read my blog. I find such posts by other people quite useful, I often get inspired to implement a technology after reading a blog post about it - there are many things that have a low priority in my todo list because they seem difficult, a blog post that reveals them to be easier than expected and advises how to avoid common problems can really make a difference!
Share This
I've been struggling with gettext most of the day but I've finally got the solution! gpe-cash builds an application and a shared library (with API, -dev, -dbg and -doc). Source files for the application contain translatable strings, as do source files for the shared library. Unable to find documentation for how this should work with gettext, I got no end of path related errors.
Here's the clue: Keep ./po/ for the $PACKAGE.pot file, add ./po-foo/ for the second POT file. My mistake was to try to use
po/ and
src/po or
src/po and
src/foo/po.
Then, remove the symlinked Makefile.in.in from
po-foo/ and copy the file from
po/ so that the
po-foo/Makefile.in.in can be edited to change the value of
GETTEXT_PACKAGE to the alternate file.
Then, add the LINGUAS file to each po directory.
Add
po-foo/ to the configure.ac output.
I also switched from glib_gettextize to gettextize (switching the configure.ac macros at the same time). I'm not sure if this is strictly necessary (and it added quite a lot of stuff to both po/ directories) but I'm not keen on breaking what I've just spent all day fixing!
Committed to
cashutil SVN: r619.
This weekend, we tidied the garden a little. This involved some gardening
and throwing away rubbish.
Thirteen large bin bags of garden waste, and a skip full of doors,
concrete and metal tubing later, we've finished the easy tasks. Next week
the new door and paving slabs arrive, so the hard work can begin. I
haven't been sleeping too well recently so bought a herbal sleep remedy
today, but I don't think I'll need any help tonight.
In other news,
Jekyll
finished last night. An excellent series with some interesting twists and
a good mix of horror and comedy, I highly recommend it to anyone who can
watch it (I believe it's being aired on BBC America next Saturday, and I'm
sure its all over the interwebs).
This is probably the last GUADEC roundup to hit the Planets, considering
that it finished a week ago. But, hey, I've been busy.
GUADEC was, as usual, a blast. Less sun, sea, and beach parties than last
year; more rain, clouds, and parties in fake-Australian bars with too-loud
music. If the weather was better we could have hijacked the landlocked
beach, which would have been fun.
As an educational conference I totally failed at GUADEC, out of an entire
week of talks I managed to attend a grand total of seven talks. Between
the GNOME Mobile meeting sprawling across two afternoons, a few meetings
with clients, occasional attending our stand and having to leave Thursday
afternoon meant that there just wasn't enough time.
As a photographic experience I
mostly
failed. I took more photos at Matthew's excellent
Clutter
Foo talk than the rest of GUADEC itself, and more photos at the
ping pong tournament than the others combined. From playing with my
camera at the tournament I now know that the Sigma 17-70 lens is no way up
to the challenge of sports photography: too slow and too short. My next
lens however will be Sigma's new 30mm f/1.4, I've been eyeing it for a
while now and Daf had given in to temptation so I could have a play with
it. Sports photography will have to wait.
As a member of the organising team however, I don't think I totally
failed. There were a few last minute snafus in the schedule but on the
whole it appeared to hold together, the main problem being there being
just too many good talks on at the same time. Congratulations of course
are due to Paul, Thomas, Bastien and Rob, who kept the conference running
on track all week.
Next year, Istanbul. That
will be interesting.
NP: F♯ A♯ ∞, Godspeed You! Black Emperor
From
two
sources
I have read today about the almost
secret deal signed by Chile Goverment with Microsoft.
The deal, in most pure Orwell style, means that all kind of computer driven
activity in the administration will be held with MS software. Even, education
will be only made with their software, with no posibility of teaching any other
alternative. This obviously will make very child in Chile captive of MS software.
Against this deal, a movement has arisen:
Movimiento de Liberaci n Digital.
We should ask governments only the freedom of choice. This doesn't mean that they have to support
every OS out there so any citizen can interact with administration with the format
he just developed some ours ago, but they should be using open standards
that anyone could implement in their software. We have to teach them
that using the most common used standard is not the same than using
an open standard.
Being in any reasonably large free software project one tends to be
confronted with endless little annoyances, frustrations and letdowns. Often
it happens that these little things keep growing in our perception the
longer they last and the more they trouble us.
In these times it is good to be reminded that the actual thing we invest
so much time and energy in is not those little issues that often annoy us
so much, but the overlying ideal of free software which is still a great
thing, even in view of all the little frustrations that we have to deal
with when working on it.
Yesterday I had one of these little experiences that just remind you,
just how good a thing free software is:
- At Thu, 26 Jul 2007 14:38:49 I filed a whishlist bug against a software
I recently started using.
- At Sat, 28 Jul 2007 19:04:35 the bug had been passed on to the
software's upstream and I got an email from the upstream author telling me
that the feature I wanted was already in the current development version of
the software, where I could download the tar.bz2 and how to contact him on
jabber.
- At about half to ten I downloaded the code, rolled it into a package
and tried it, but couldn't get the new feature to work, so I wrote another
email.
- An half hour later I got an answer telling me what I'd done wrong. I
fixed my mistake, tested the new feature and found that it did right what I
wanted. However, there was one more option I thought would be useful so I
contacted the author via jabber.
- In the following 2.5 hours he implemented the additional option that I
had asked for, renamed a button I found a bit unintuitive and fixed two
bugs I discovered in the process of testing the new feature, sending me new
code versions to test after every change.
- I am now using the software with the new feature I asked for and with
all the options I wanted from a homemade package but expect the proper
Debian package to show up in the archive any day.
- The whole process took three days.
... and this is exactly why free software (and the people in it) is so
great. Because if there is something you'd think would be useful, all you
have to do is ask and maybe lend a little help in testing and you got it.
And this is why it's worth to put up with all the little annoyances,
frustrations and letdowns that working with humans brings with it. Even if
they sometimes seem to be overwhelming.
PS: I know that there are also enough examples where things didn't go as
smooth as this one. But this just makes it more worth and important to
highlight and appreciate these examples where everything just worked out
perfectly and not just take them as granted.
So, inbetween posting rants and fuming at all the things that tick you
off, how about if you think of a nice FLOSS experience you had and
share it with the rest of the world?
tags 388218 + pending
tags 270533 + pending
thanks
Ladies and Gentleman,
I am finally happy to mark this pending … upload should go to sid
today.
iceowl is the unbranded sunbird standalone application.
lightning, the sunbird based thunderbird extension will be called
iceowl-extension … and will be usable in icedove + thunderbird.
I will announce on debian planet once those are uploaded.
Have fun,
– Alexander
I'm getting myself ready to take off for
Taipei for
Wikimania 2007. It's going to be an exciting event -- my first time in
Taiwan, too.
I've been ambiguous about Wikimania each year, but I seem to keep going. The stated purpose of the conference is to be
solely for Wikipedia and other Wikimedia projects, but people seem to keep coming who don't have anything to do with Wikimedia projects, so I figure I might as well go, too. I like finding out what other people are doing with
MediaWiki, and I like getting pumped up about
Open Content, the Wiki Way, and freedom of information around the world.
I hope that eventually more general-purpose wiki conferences like
RecentChangesCamp and
WikiSym will get more public attention, and participation by Wikimedians, in the future. It would relieve some pressure on Wikimania to be something it doesn't seem to want to be.
I'm going to be speaking about
Extending wikis with social networking tools. We've done some interesting work with this on
Wikitravel Extra, and I plan on using the same technique for other wiki sites in the future. I think it's a powerful way to enhance the unity of consensus knowledge with a multiplicity of varying opinions.
I'm also looking forward to the
Debian Birthday Party 2007, thrown by local Debianistas. It should be a lot of fun! There's also a
Creative Commons conference happening during Wikimania, which will be pretty interesting. Lots to do in Taiwan this year.
tags:
wiki wikimania wikimedia wikipedia debian taiwan taipei
WYSIWYG and MediaWiki
I've been an advocate of WYSIWYG editing in MediaWiki for 3 years now. So I'm interested to see that the core dev group for FCKeditor have gone the distance to make a real, working WYSIWYG plugin for MediaWiki. The extension has just about everything that I'd want from a WYSIWYG mode for MW:
- It stores articles as Wikitext. Since in-browser editors generate HTML, plugins often try to store HTML in the wiki database, but this conflicts so much with other parts of the site, it's unworkable.
- It's implemented as a MediaWiki extension. This makes it possible for MW installations to experiment with the tool and remove it if they don't like it. It also shows that the tool isn't too invasive and should work with other extensions.
- It supports templates, tables, images, and citations. A lot of the advanced syntax for MediaWiki is supported.
- It's optional for users. Users can switch to Wikitext any time they're editing a page, and users who don't like WYSIWYG at all can turn it off with a user preference toggle.
I think that this tool has the capability to be the WYSIWYG editor for MediaWiki. The previous effort using Wikiwyg didn't handle most of these points. Jimmy Wales gave an impassioned keynote at Wikimania 2006 about the need for WYSIWYG editing on Wikipedia and elsewhere, and I hope we can use the FCKeditor MediaWiki extension to meet that need.
tags: wiki wysiwyg mediawiki fckeditor wikiwyg
Thanks to
Centauri Dreams for the pointer to the ESA DARWIN proposal now
here (high-resolution version also
here).
DARWIN is a space mission to detect the presence of life on other planets by
spectroscopy: looking for
biomarkers such as the presence of Ozone, water and methane together on terrestrial-sized planets. These are groups of gases that collectively would imply the presence of life.
Unfortunately it appears that DARWIN is slipping: its not currently hardware-funded, and has a planned launch-date of 2020, having slipped from 2012. This is when NASAs alternative
Terrestrial Planet Finder and
Space Interferometry Mission have been defunded indefinitely.
At the same time, the French
COROT mission has just announced its
first month-long series light-curves.
COROT hunts for Earth-sized planets: it's a small space telescope that stares at the same patch of sky for long periods, looking for changes in the
amount of light from stars that indicate a planet passing in front of a star.
It has been much more successful than expected, having already announced its
first exoplanet detection in April.
NASA is also launching a similar mission,
Kepler, in 2008.
So we face the prospect that any day now we may know of Earth-sized planets in a
Habitable zone, and yet be over a decade from determining if they could contain life.
So do we have any other tricks up our sleeves? Other possibilities include
the
James Webb Space Telescope, the successor to the Hubble. With a launch planned in 2013, it would be able to determine
some atmospheric features found in COROT detections, but would be too expensive to do the planet-hunting Darwin could do. Perhaps this could be imroved with occulters such
as
UMBRAS (thanks to
enzo).
Other novel detection missions include the
Voyager Interstellar Mission
(
via), reusing exisiting 'end-of-life' spacecraft as telescopes.
And finally, could ground-based telescopes do it?
tests have just started on a new 10M telescope
in the Canaries that could help; in terms of larger scopes, colleagues of mine in
NUI Galway have been collaborating on the design of
Euro50,a proposed 50 M telescope. Together with new techniques such as
spectral deconvolution (via
via) may help.
Tags astronomy, exoplanets
Because of the social networking and needing-to-be-registered of it
all, I had to sign up for another website to keep track of one of my
friends' goingses-onses. The sign-up process reminded me of a circus
freakshow of the "Step on inside -- if you dare! And buy a bottle
of our snake oil!" (insert knowing, taunting laugh) variety.
Tell me how PUMPED you feel after reading the comments they added
after I filled in the various fields:
Email address: Nicely put!
First name: So that's what they call you!
Last name: Classy last name, I have to admit!
Username: Creative!
I agree to the Terms of Service: ...I dare you to un-click
that!
End of registration: To make sure you're as awesome as you
claim, please visit your email's inbox for our verification email
(I'm positive that more exclamation points were ejaculated all over
my screen at this point but I closed the window too quickly to be sure.)
Activation confirmation emancipation proclamation: Wonderful,
the hardest part is now over! Time to Enjoy! (With a capital
E!!!!)
It might as well have been written by Dr. Bronner himself:
Email address: Godliness!
First name: If I'm not for me, who am I? Nobody!
Last name: Enlarge the positive!
Username: WE'RE ONE! ALL-ONE! EXCEPTIONS ETERNALLY? NONE!
ABSOLUTE NONE!
I agree to the Terms of Service: Warning! Keep Out of Eyes! Wash
Out with Water! Don't Drink Soap! Dilute! Dilute! or Wet Skin Well!
End of registration: Whatever unites mankind is better than
whatever divides us!
Activation confirmation ALL-ONE! clean sensation: WELCOME TO
SPACESHIP EARTH!!
Even if I did nothing else this summer, I feel like I could look back on
just today and feel that I'd a long summer full of lots of summer fun.
Maybe that's how memory works for me, suddenly I'm fully aware and stashing
away every instant, as we jounce down Anna's very rutted and muddy road, in
a trailer pulled by a four-wheeler. Later, taking a swim in the creek, I
find that Lucy loves to chase splashes as they arc through the air, and try
to catch them in her mouth. I get the dog to bound higher and higher out of
the water, and then dissolve in a puddle of hilarity. Then I find out she
also likes to chase gravel thrown into the creek. We do this for an hour or
so, and I find a very strangly shaped rock, that turns out to have metal
in it. There was also grilling of every vegetable that could be pulled out of
the garden, and lots of hard work loading many loads of cinderblocks into
that trailer.
Now I'm in my tent enjoying the rain and adding alsa support to
hotkeys.
Following
my previous article, I had some interesting comments introducing me to
git-filter-branch (which is a new function coming from cogito’s
cg-admin-rewritehist). This command is really designed to rewrite the history and you can do much more changes… it enabled me to fix the dates/authors/committers/logs of all the commits that were created with git_load_dirs. It can also be used to add one or more “parent commits” to any commit.
In parallel I discovered some problems with the git repository that I created: the tags were no more pointing to my master branch. This is because
git rebase won’t convert them while rewriting history.
This lead me to redo everything from scratch. This time I used
git-filter-branch instead. The man page even gives an example of how to link two branches together as if one was the predecessor of the other. Here’s how you can do it: let’s bind together “old” and “new”… the resulting branch will be “new-rewritten”.
$ git rev-parse old
0975870bb1631379f2da798fa78736a4fe32960a
$ git checkout new
$ git-filter-branch --tag-name-filter=cat --parent-filter \
"sed -e 's/^$/-p 0975870bb1631379f2da798fa78736a4fe32960a/'" \
new-rewritten
[...]
Rewritten history saved to the new-rewritten branch
Short explanation: the only commit without a parent commit (thus matching the empty regex “^$”) is the root commit and this one is changed to have a parent (-p) which is the last commit of the branch “old”.
At the end, you remove all the temporary branches, keep only what’s needed and repack everything to save space:
$ git branch -D old new
$ git prune
$ git repack -a -d
The DebConf 7 videos needed some post-processing, mostly to recover
missing pieces from tape. I've done a large part of that, but it's
not yet complete.
The
video team
to-do list has details of the recordings that still need work, and
the sessions that we believe were not recorded. Please
tell us if we did
record some of these, and we will have another look through our tapes
for them.
The conversion to "publication" formats (i.e. small enough to offer
for download) was started at the conference and I have continued this
at home over the past 2 weeks. Unfortunately this has been
interrupted by some hardware failures. It looks like the CPUs in two
of my PCs were running hot enough to be damaged (slowly) but not hot
enough to trigger an alarm or automatic shutdown. The remaining
conversions will be running mostly on my laptop, which is pretty fast
and should be able to finish conversion of the recordings that are in
a good state in about 2 days. However, some of the converted files
may be broken and need some manual attention.
My upload bandwidth is only 448 kbit/s so the high-quality files
will take about a week to upload.
As ever, the video files are being published on
meetings-archive.debian.net.
In
my previous post, I briefly mentioned my K750i Sony-Ericsson mobile phone. I received it as a birthday gift this year, to replace my aging but trustworthy Nokia 3210 and, as with any multifunctional digital device, there was a learning curve during the adoption period. While some features were gladly and swiftly taken into use, some of the handset's usability issues became my pet peeve and, among them, the localization pack wins the jackpot.
First, let's make one thing clear: I fully understand that memory constraints prevent manufacturers from including support for every language known to man, so a handset can only be loaded with a limited set of languages for the User Interface and for T9 predictive text input dictionaries. My issue is with the concept of grouping languages by linguistic families or continental areas, when compiling the localization packs for those handsets.
In this particular case, I had a choice between the Baltic or Nordic packs. The former has UI language support for Estonian, Latvian, Lithuanian, Polish, Russian and Ukrainian, while the later has support for Finnish and the Scandinavian languages; English is also included in both cases. T9 support is a strangely mixed bag: the Baltic pack only includes predictive input for the Slavic languages, while the Nordic pack supports all the languages of its UI.
What's my problem with the above language combinations? For starters, I'm in Finland. We don't interact with Danes or Icelanders outside very occasional pan-Nordic meetings and that mostly concerns politicians. Meanwhile, average Finns travel for work and play to Estonia and Russia on a fairly regular basis, which makes sense, since they are neighboring countries. However, available language packs don't take this into account.
How should this be resolved?
Either language packs are produced with specific countries in mind, rather than generic geographic areas, or the users should be allowed to freely mix and match among all available languages and get the result flashed into their handset at purchase time.
The K750i language pack for Finland should therefore include: Finnish, Swedish, Estonian, Russian, English and Norwegian (essentially the current Nordic language pack, but with Danish and Icelandic replaced with Estonian and Russian). Then again, this only covers official state languages. Sam dialects, anyone? I guess not, because we'd soon be exceeding the handset's capacity. Hmm...
Thus, the only real solution is to allow people to freely mix and match UI and T9 languages of their choice at purchase time.
As a bonus, this would allow me to drop Norwegian and replace it with Joual... ... c lisse, French and finally have a language pack that I can truly find useful. I can easily picture a Transylvanian engineer working in Finland wanting to get Romanian support or a Kurdish immigrant preferring Turkish support instead.
Sony-Ericsson, how about it?
I really enjoyed OSCon. This was the first conference I've been to in years where I've felt a bit sad that it's over. I met a lot of interesting people, enjoyed most of the talks I attended (and especially this morning's keynotes), and also enjoyed Portland. I recommend OSCon. Last year, I went to Usenix ATC. Compared to Usenix, OSCon had more talks that were relevant to things I'm interested in, more people that I met with similar interests, more people that I knew online and met in person, and a more broad program. The one criticism I would level at OSCon is that it has a disproportionately high number of web-related talks.
On to other items...
Portland
Probably the friendliest "big city" I've ever seen. Everyone from cab drivers to bus drivers seems to go out of their way to be helpful and friendly. Somewhat different from, say, Chicago or Los Angeles.
The climate is very nice and the transit system is excellent as well. While it doesn't move as fast as below-ground systems, since it has to work within traffic, one nice thing for visitors is that you actually get to see the city and see potential places to stop. Last year, we went from Boston to Cambridge on the T, but you don't see much except a whole lot of concrete along the way.
The Japanese Gardens are wonderful and deserve a visit.
Compared to Indianapolis, where we lived for awhile, Portland has some nicer parks, and a better transit system. I think that Indianapolis had a nicer walking path. Portland had a lot of friendly people, including many that worked for TriMet. MAX was very nice, with frequent departures. The TriMet system had scattered electronic signs about the MAX lines, streetcar stops, and even some bus stops I think. These listed how many minutes until the next departure in each direction, and were very helpful. Stations were announced audibly and on signs on-board. There was helpful information at stops and platforms.
Indianapolis has a really quite awful transit system, which consists of, let's see, regular buses and small buses. These run infrequently, are known for not being on-time, and a former co-worker had trouble with them just not showing up at times. They also all seemed to run between downtown and the outskirts. So if you wanted to go from one area towards the outskirts to another area there, you'd have to go towards downtown and back out.
Because of all this, I never rode IndyGo, and wouldn't ever encourage visitors to. TriMet was very different, and if I lived in Portland, I'd want to live close to MAX.
Hotel
The DoubleTree Lloyd Center is a nice, friendly hotel. Everyone here has noticed that the elevators inexplicably stop on the 2nd floor every time they go down, but other than that, we have had no real problems (other than some water dripping onto the desk when we first were here, but maintenance fixed that). It's annoying that they charge for in-room Internet access, but that is unfortunately typical for hotels of this class.
The room is also a bit small, but has worked out OK. The hotel is very close to a MAX stop, and fairly close to the Lloyd Center mall, which is convenient. The staff is very friendly and helpful as well, especially the concierge staff, which are great and helping visitors find their way around the city and the transit system.
They give you cookies on check-in, but Terah was disappointed that they didn't offer any without nuts.
Restaurants
I had opportunities to eat with various people from OSCon, some Portland area people, and of course, Terah and Jacob.
Portland has some good restaurants, and a few more iffy ones...
The Multnomah Grill in our hotel was one of the iffy ones. I had the ribs, which were not at all good. The prices were about in line with other Portland restaurants, which is too bad because the food wasn't. Because of all that, I just couldn't bring myself to try the other restaurant in the hotel, Eduardo's Mexican/American Cantina.
I had heard about Jake's Famous Crawfish from a passenger on the train. It was also listed on the OSCon wiki restaurants page. It's a historic century-old restaurant, with excellent seafood. I had parmesean-crusted Alaskan Halibut, which was very good.
I also went to the Newport Seafood Grill, which is within walking distance of the hotel, just on the other side of the Lloyd Center mall. It was also good; I had a tuna dish served rare, with a sauce that complimented it well.
Blossoming Lotus Cafe is a vegan cafe in the Pearl District. I hadn't ever been to one of those before. It was OK, but not all that great.
Across the street was Sweet Masterpiece, a chocolate and coffee house. Excellent chocolate made in-house, all sorts of desserts, and good coffee.
Rock Bottom in downtown has some surprisingly good food options. I was there with a group of local and OSCon Haskellers, and it was a little bit hard to follow conversation all the time due to the background noise, but that's to be expected in this sort of place. I'm not into beer, but those that were enjoyed their selection, I think.
I also went to a couple of chains: Quizno's and Ben and Jerry's. Both were about what you'd expect from those chains. Good ice cream of course at Ben & Jerry's.
OSCon provided breakfast and lunch free to paid attendees. Breakfast consisted of a selection of various fruits, slightly stale pastries, and bagels. On the tutorial days, lunch was pre-made boxed lunch. For what it was, it was OK. On Wednesday and Thursday, lunch was served hot in buffet lines. They had chicken both days, which looked identical. I had tried it Wednesday so knew not to bother Thursday. Wednesday they also had salmon with cranberries, which was good. Their salads, breads, etc. were OK.
Oregon Convention Center
This is where OSCon was held. A very nice, but incredibly huge, building. They say it covers the equivalent of 13 square city blocks, and if you look on a map, you can see that it is indeed quite large. There was a lot of walking to get to everything, even though OSCon took up only one part of this huge place. Restrooms in particular were not in very convenient locations to just about anything. But it was a nice place and I wouldn't mind being there again next year.
Hey folks, we released some minutes ago finally
Debian-Edu/Skolelinux 3.0r0 ?Terra? which is based on Debian 4.0
with some modifications to work out-of-the box. Here are the
releasenotes:
Oslo - July 22., 2007
Skolelinux 3.0 is ready. This is an community release with
comprehensive support from regional and national projects in
Germany, Spain, France, Greece and Norway. The Skolelinux project
is now a part of Debian under the name Debian-Edu. Several other
projects have made additional functionality to Skolelinux tailored
for national needs. Skolelinux now supports more than 50
countries.
whats new in skolelinux 3.0:
based on Debian 4.0 ?etch? and therefore compatible to LSB 3.1,
using kernel 2.6.18 and KDE 3.5.5 Full support for networked Thin
clients,
?LowFat (diskless) clients, Workstations and Laptops.
With the
?LowFat clients users got full PC functionality with
extremely low maintenance cost. The use of
?LowFat clients gives full support for sound, video, USB
memory stick?s and DVDs without the need for a local
installation.
Skolelinux now got more than 80 applications selected for
pedagogic uses, supporting more than 50 languages. Many new
applications are introduced in addition to popular classic as
GCompris, KDE-Edu, Iceweasel (unbranded version of Firefox) and
?OpenOffice.org.
Installation is a breeze: Both the installation and source code
for all software are now distributed on a single DVD now supporting
three different processor platforms as i386, PowerPC and AMD64.
This makes it more easy to choose hardware, and to study the
recipes behind the software. Those interested can exercise their
freedom to learn, participate and share knowledge more easily.
Installation CDs are also available, but requires a working
Internet connection for installation.
about skolelinux
Skolelinux is a complete tailored software solution for the
needs of any educational institution or school. It is a ready
computer system were the school does not need to piece together the
components. Skolelinux is the result of the work of the Debian Edu
project and Debian Edu is an official Debian subproject. It is
installed in a great number of schools in Norway, Germany, France
and other countries. Municipalities and Commercial Service
Providers run Skolelinux across multiple schools, operated and
maintained centrally. Service providers report that the ?lowfat
clients? require half the maintenance cost of other desktop
alternatives.
The next milestone of Skolelinux development will be to merge
the Debian-based
?LinEx distro into Debian Edu. Currently
?LinEx is used by more than 250,000 students and public
employees in the region of Extremadura in Spain.
in depth
Lowfat clients is also known as Diskless workstations. They run
applications locally on the client. All software comes from the
server instead of locally from the client hard drive. Recommended
minimum requirement for client machines is > 256 MB RAM and 800
MHz CPU. Skolelinux now got improved tools for system surveillance
and maintenance. Roadmap for next merging of
?LinEx and Debian-Edu: *
http://wiki.debian.org/DebianEdu/LinEx2DebianEdu-Roadmap
Please note that the documentation for the 3.0 Terra release is
only available in English at the moment and contains some rough
edges. We have considered releasing before the end of the summer
holidays more important and we will fix those rough edges in the
coming weeks, when we also expect more translations to show up.
Those fixes will be included in the upcoming 3.0 r1 release.