| Buff |  | 23 CHF / 18 euros |
| Black polo |  | 31 CHF / 25 euros |
| Rugby polo |  | 50 CHF / 40 euros |
| Mousepad |
 | 13 CHF / 10 euros |
The Fay compiler is a simple way to build fairly
comprehensible javascript code from Haskell source.
It occurs to me that it should be rather easy to modify Fay to emit perl
code rather than javascript. This would allow contributing things like
plugins to various perl programs, without writing perl.
Of course, the same idea could probably be used to compile Haskell to other
languages like python, but perl seems particularly well suited as a second
Fay target, since javascript and it have quite similar syntax and similar
support for features like closures which Fay relies on.
I do not have time to work on this idea myself. It would be a good project
for a beginning Haskell programmer. You probably don't even need to fully
understand monads to do it! Essentially, look at
Fay output examples,
translate them from javascript to perl, and then much of the code changes
in Fay would probably be in simple string generation code.
Privacy note: as always, I will be trying to balance the need for people to get lots of pictures as fast as possible with privacy of people, who do not want to be in published photos. The way this has been done before and will be done this time (at least from my side) is that:
I was very excited to go to Debconf13, but in the last minute I caught some kind of virus and went down with fever in the night before the flight. I am sure Wouter will take over group photo duties. And I will just take this week of vacation to rest up and check out the video streaming 
A hectic day and now we use GMime for all MIME-fu.
This has allowed me to decode headers correctly, setup MIME parts
properly in outgoing mails with attachments, and cleanup the
code-base.
The next release of Lumail will contain basically just this change,
as it is pretty drastic. But first I need to work out how to make
binaries for Squeeze compiled against the back-ported version of
gmime-2.6.x.
(Previously we used libmimetic. Which was awesome in its way, but
caused me some pain with RFC 2047 header-decoding.)
Hi everyone! We now have both Qt4 and Qt5 in the archive. Those using Qt4 should not need to make any changes in their packages, although you can be extra-safe with a few steps. Don't rush, just read below.
[no pictures here, just a short report].
Today DebConf, this year's edition of the annual Debian developer
conference, started with two inspiring talks about Debian proper, one by
Lucas Nussbaum, the other by Joey Hess.
This also means that yesterday DebCamp ended, the period preceeding
DebConf and dedicated to working on Debian together with others.
Here's a short report from my point of view:
I arrived here on Tuesday, the first day of DebCamp. I immediately fell
in love with the venue, & despite the early stage of setup, everything I
needed was working fine for me from the very start.
Like in previous years, I used the time to do work in the Debian Perl
Group, especially taking advantage of the presence of other team members.
That's the great thing about DebCamp & DebConf: collaborating in
real-life & real-time, from quickly asking a question over sitting
together to think about solutions for a problem to "just" chatting &
thereby developping ideas for the future.
In the previous days I
This is just a quick note that the video streams of DebConf13 will be available at the following URLs:
Cloud is passing the hype curve and we are seeing more stable developments and offerings on the market. Lately I ve been playing with RedHat s Openshift. Openshift is a PaaS (Platform as a Service) offering that intends to be an alternative for vendors such as Heroku. The focus for such offerings is to give developers enough flexibility and tools that handle the application deployment and maintenance process in a way that is integrated with their existing development workflow and tools.
I ve been using Heroku for a while to deploy small to medium size projects. I liked the tools and developer-centered experience they offer. Openshift is quite new on the market and it comes in two flavors: Openshift Online, which is a PaaS service, and Openshift Enterprise, which allows organization to setup a PaaS within their own infrastructure. Both of them powered by the Openshift origin software. I ll not compare Heroku vs. Openshift feature by feature but from my experience I can tell that Openshift is far from mature and will need to give developers more features to increase adoption.
When developing applications for Openshift developers are given a set of application stack components, similar to Heroku s buildpacks. They call them cartridges. You can think of them as operating system packages, since the idea is the same: have a particular application stack component ready to be used by application developers. Most of the cartridges offered by the service are base components such as application server, programming language interpreters (Ruby, Python, etc), web development frameworks and data storage, such as relational and non-relational databases. Cartridges are installed inside a gear, which is a sort of application container (I believe it uses LXC internally). Unsurprisingly this Openshift component doesn t leverage on existing packaging for RHEL 64bit, the OS that powers the service. I d expect such things from the RedHat ecosystem.
I had to develop a cartridge to have a particular BI engine to be used as embed component by application developers. After reading docs and reference I realized this can be piece of cake, since I have packaging experience. Wrong. Well, quite so. The tricky part for Openshift Online is that it does not offer enough information on the cartridge install process so you can see what s going wrong. To be able to see more details on the process you ll need to setup an Openshift origin server and use it as a testing facility. Turns out that having a Origin server to operate correctly is also a challenging task and consumed a lot of my time. Over the recent weeks I ve learned from origin developers that such features are on the road map for the upcoming releases. That s good news.
One of the challenges I had, and still have to figure out, is that unlike the normal cartridges mine didn t required to launch any service. Since it is a BI engine I just needed to configure and deploy to an application server such as JBoss. Cartridge format requires to have a sort of service init.d script under bin along with setup, install and configuration scripts that are ran on install. Although every day I become more familiar with origin and Openshift internals I still have work to do. Nice thing is that I was already familiar with LXC and Ruby-based applications so I could figure where things are placed and where to look for errors on origin quite easily. The cartridges are on my github account if you care to take a look and offer advice.
I'm going to debconf13. After been in debian for quite a long time, I finally will see in person some of those mail address I see for so long.
If you're tempted to add a platform-specific quirk to a Linux driver, pause and do the following:
So... Well, contrary to the popular sentiment in Planet Debian, this year I'm very sorry to inform that...
This is the first DebConf I miss in ten years, so... Yes, it's a big bummer for me. I'm not attending because this year, DebC(amp onf) coincide with the two first weeks of classes at my university And as a new teacher, I cannot afford to miss it!
Anyway, but that should not stand in the way to attend a nice Debian 20th anniversary party!
Parties will be held around the world. (Didn't find your city? Plan something and add it *now!*). In Mexico City, the nice guys at the very interesting Rancho Electr nico hackerspace took the lead, and organized the following activities:
Don't you yet know the hackerspace? You should go there! It's in a very centric location, just two blocks West from Metro San Antonio Abad (Juan Lucas Lassaga 114, col. Obrera). And the only two times I have been there, it has been good fun. Surely this Saturday we can have a nice party as well!
The planned activities are from 13:30 to 20:30. See you there!
Weblate 1.6 is already two weeks out without any regressions, so now it's time to think about features for 1.7.
I definitely want to improve support for monolingual translation formats as they currently suffer by various metadata issues (eg. checks not working correctly). This requires quite big change in underlying database, but I think it's quite manageable.
When talking about checks, I want to make them configurable per project as global configuration is quite limiting for shared sites like hosted Weblate.
I will definitely need to touch registration and authentication, either by supporting latest django-registration API or to move some other solution with support for federated login. Which of these approaches will be used depends on my time, what is always the most limiting factor.
This might sound as too few features, but I'd like to make releases more often, so that should fit into this plan. However if you want to push for some feature, you still have two days to fund something on Catincan!
Filed under: English Weblate 0 comments Flattr this!
Small update as someone was complaining about the lack of pictures from DebCamp on planet.
Not to worry, everything is going fine, and some of the most important stuff is ready
You can see a few pictures from the gallery. The view from the venue is quite outstanding (it was better when there was some sun on Tuesday, but my camera battery was out ).
On my TODO-list:
I will arrive at DebConf 2013 on Sunday afternoon. In case you are interested
in Go (the programming language), systemd, i3 or getting your package reviewed,
please talk to me! :-)
Looking forward to meeting many of you in real life.
With the number of female software engineers standing at 20.9% [1], recruitment of females into the industry is a major concern. A friend of mine, Rosemary Francis who's MD of Ellexus, has a great talk about this issue. It mentions various methods you can use to tailor your job applications to be more attractive to females, by simply being careful not to exclude or put off potential applicants.
However, there is also a very poor way of doing so, which is highly sexist and plays to stereotypes. As we can see from Bloopark's hiring page, this is exactly what they have done.
Web developer (m)Really? New pair of shoes? Pictures of nail varnish? They're in a relationship with code? And why does the male version need to have a girlfriend rather than a boyfriend? [1] US Bureau of Labor Statistics (BLS) - ftp://ftp.bls.gov/pub/special.requests/lf/aa2010/aat11.txt
Need for programming
You are addicted to PHP, MySQL and Javascript since years? Your life makes no sence without programming? Your girlfriend doesn't understand, why you start learning the fifth php framework and your parents say, your head is full of unix and linux. Do you want to talk to us about this? We want to invite you to an anonymous or maybe very personal meeting. No worries, we will bring you to a team that understands you and will support your passion of programming. Web developer (f)
Beautiful und sexy code wanted
We are convinced that woman are great programmers. Woman write sexy code: neat and clean. Many of them have long relationship... with PHP5, MySQL and Javascript. They like to talk and communication is essential in our work. Female programmers get along with customers very well and take such a good care of code quality, as if it is a pair of their new shoes. The best thing is that their detailed documentation and code organisation match the rules of Feng-Shui. Are you a female programmer with passion? May we invite you for coffee?
Next.