UK Linux User Groups

Recently there has been some fire flowing about Canonical in the community. These concerns started off as sporadic at first and then we saw a small blog avalanche (blogalanche, if you will) as a number of folks piled onto the ride.

I feel somewhat trapped in the middle of all of this. On one hand I work at Canonical and I believe Canonical are acting in the honorable interests of Ubuntu in helping to build a competitive and forward-looking Free Software platform, but I also feel a sense of personal responsibility when I see unhappy members of our community who are concerned with different aspects of how Canonical engages. Essentially, I sympathize with both sides of this debate; both have the best interests at heart for Ubuntu.

From my perspective there is a balance that needs to be struck. Our community needs to be transparent and open, but also nimble to react to opportunities (such as the convergence story), but also Canonical play an important role in helping us to drive Ubuntu to the masses. We need to be able to work in a way that maintains our Ubuntu values but also gives Canonical the opportunity to get our platform out to the market effectively to reach these users.

I believe one cannot exist without the other; Canonical cannot deliver this vision without our community and Ubuntu would be significantly debilitated if there was no Canonical providing staff, resources, and other investment into Ubuntu. Canonical is not evil, and the community is not entitled; we all just need to step back and find some common ground and remember that we are all in the circle of friends.

This symbol is as potent to me as it was back in 2004.

When I got interested in Linux back in 1998 and wanted to make it my career, my primary motivation was to bring freedom of technology to everyone. This is what attracted me to Ubuntu and ultimately working at Canonical. I don’t want to be rude to other distros who are quite happy within their remit of making a great OS for Linux enthusiasts, but I frankly don’t want to settle for that. I want Ubuntu to be the choice for Linux enthusiasts, but for us to not stop there and also bring Free Software to people who have not yet been blessed by it, and who may be new to technology and the opportunities it provides.

Achieving that goal is not just as simple as making the source code available for the platform and setting up a bunch of mailing lists. It means delivering simple and elegant user experiences built for the needs of our users, consistent and beautiful design, professional-grade quality, strong hardware and software partner relationships, certification across a range of hardware profiles, training, responsive security, diverse marketing and advocacy campaigns, and many other areas. Both Canonical and the community contribute extensively to provide these things that we need to get over that chasm, and importantly, each provides things that the other cannot.

It turns out that building this simple, ubiquitous Free Software experience for everyone is hard. We can’t just settle for the tried and tested approach of pulling the latest upstream software and integrating it into a single Operating System. That is tough, intensive and grueling work in itself, but to achieve the goals I mentioned above we need to be constantly challenging ourselves to innovate and go faster in how we deliver this innovation to our users. We need to always challenge the status quo…not for the sake of being different, but for the sake of not restricting ourselves to tradition and instead helping us to be better at what we do, and ultimately achieve our goals of getting Ubuntu into the hands of more people.

We saw this challenge with Unity: that was a tough, but necessary decision. While we suffered over the firestorm around Unity, I think it ultimately put us in a better position, and now we have a single convergent user interface that spans across multiple devices and we will soon have a single convergent Unity code-base across these devices too. In an era where desktop shipments are down due to the impact of phones and tablets, we are no longer trapped in a form factor that has had a decreasing scope of opportunity for us; the desktop is just one part of our wider convergence vision. This opens up the market for Ubuntu and the Free Software and Open Source values we encompass. While some people in some comment boxes will still bring the hate about Unity, I think that overall it has put us in a position to get Free Software in the hands of more people than if we didn’t make that difficult decision, and the sheer level of interest in Ubuntu for the phone, tablet, TV, and desktop is testament to that.

Put it in my pocket, on my lap, on my desktop, and hang it on my wall.

While making tough decisions is important, it is also important that we maintain our Ubuntu values too. One core value is that our platform and community are open for discussion and participation, so everyone is welcome to help put their brick in the wall. Our archive has long been open and there are many ways to contribute, and while some of these projects were secret before-hand, now everything is out in the open and available for participation. Some may disagree with the rationale of keeping things private, but particularly in the case of Phone and Tablet, the “big-reveal” helped us to have a big splash and generate more press interest and partner inquiries, and thus help us along to our vision.

Importantly though, we made the source and community on-ramp available as soon as we feasibly could. The code for Unity, Ubuntu Touch, and Mir is publicly available, and we are eager to invite people to join and shape those projects. This week we also ran our very first online UDS, with the goal of making the Ubuntu planning process as open and accessible to all as possible, not just those who could travel, and on a more regular cadence. All of the videos, notes and blueprints from that event are archived here. I am confident for the next event we will have an even smoother, better-run UDS, with even more participation.

We are now in a position with a clearly articulated vision around convergence and cloud orchestration, full source availability, daily builds of images, and public mailing lists and IRC channels to have those conversations. Everything is available in public blueprints and tracked at status.ubuntu.com, and we have many outreach campaigns to help our community participate in this vision, such as the core apps project, port-o-thon, regular cadance testing, charm quality improvements, SDK participation, and other areas. Our community should expect our projects to be open, accessible and collaborative, and if they are not, please raise your concerns with the Canonical engineering managers, or talk to me either publicly on my weekly Q&A video hangout at 7pm UTC every Wednesday on Ubuntu On Air, or privately at jono@ubuntu.com, or by contacting me on Freenode IRC – my nick is jono. My door is always open.

Things are never perfect in a community, and I am not suggesting we are perfect either, but I believe we are at the cusp of an incredible opportunity to get Free Software and open technology into the hands of the masses, not just by wishing it to be true, but because there is genuine market opportunity for it to be true.

Post LTS.  You start a rolling release. This gets all the goodness in that you want.  6 months in you take a fortnight out. Week one stabilize, week two ISO testing.  The resulting ISO is then supported with security back ports for the next 6 months till the next ISO is stabilized and so on till you get to the 6 months for the next lts.  Here you go back to the more tried and tested release method so this release is solid, stable and ready for the next 5 years.

This I think gives users a regular cadence they are used to. Gives people like system 76 a regular OEM install it has security back ports from the continuing rolling release.  It gives app devs a set of libs for 6 months that won't change.  And means there is only a fortnight slow down for the devs.

Plus the community driven derivatives can continue to use their current 6 monthly cadence. Everyone is happy :-)

I just wanted to post a quick blog entry thanking everyone who joined the first day of our inaugural online Ubuntu Developer Summit today. Overall we didn’t see many glitches in our plan of how to run the event, and we also gathered some fantastic feedback for things we can improve and extend upon next time.

If you want to see what happened in the sessions today, you can view the schedule and view any of the recorded hangouts.

Before we get into the second day tomorrow, I just wanted to invite any comments and suggestions for what worked well, what worked less well etc, to see if we can make any adjustments for the second day. Thanks in advance for your suggestions!

If I don’t see you until tomorrow, we look forward to beginning Day 2 at 2pm UTC tomorrow! Be sure to see the schedule and join us in the sessions!

Tomorrow we will be running our very first online Ubuntu Developer Summit. The event will take place over two days and span a range of different tracks: Community, Client, Cloud & Server, App Developers, and Foundations. We have never run an event like this before, but we have prepared extensively to deliver the best online UDS experience we can. When UDS is complete we will then review any rough edges and fix those up for the next event in May.

With this being a new event, I wanted to share some key tips about how to get participate.

For Everyone

UDS takes place on Tues 5th – Wed 6th March 2013 from 2pm UTC. Please note: the original time was 4pm UTC, but we brought the event forward by two hours.

The full event is taking place online and everyone is welcome to join, irrespective of whether you are an active contributor to the community, a partner, a business, an enthusiast, or anyone else. We will be using Google+ Hangouts On Air to stream video from the active participants in the session, and we also provide quick embedded access to IRC, note-taking, and more.

The event will kick off on Tuesday at 2pm UTC with a keynote session. There will then be two hours of sessions, then an hour of plenaries, and then another two hours of sessions. On the Wednesday we will kick off into sessions at 2pm, and have lightning talks in the normal plenary slot. Jorge Castro is taking care of the plenary talks and lightning talks; reach out to him if you want to run a lightning talk.

There are five tracks, with each (apart from Foundations) having two video streams. Each track has two track leads:

• Client – Jason Warner, Sebastien Bacher
• Server and Cloud – Antonio Rosales, Daviey Walker
• Community – Jono Bacon, Daniel Holbach
• App Developers – Alan Pope, David Planella
• Foundations – Steve Langasek

You can find all sessions listed at summit.ubuntu.com. Just visit the session you are interested in at the time of the session to view it; everything is included on the session page. You don’t need anything other than a web browser to view sessions but you will need a Google+ account to actively participate in a hangout.

For Track Leads

You should have all received an email from me about how to schedule sessions and how to start and stop the video streams.

Remember to ensure your Google+ is verified (Michael Hall should have checked this with you).

You and your co-track lead should pick one of the two tracks you have for your track and take care of setting up those streams.

Five minutes before a session (e.g. 1.55pm) is due to begin you should start the video stream and update the session in summit.ubuntu.com with the hangout and broadcast URLS. Likewise, 55 minutes into a session (e.g. 2.55pm), be sure to stop the hangout. We need to start and stop the video streams to ensure the recordings are broken up into the different hour long chunks. Required participants will automatically see a link on the session page to invite them to join a hangout – this page does not auto-reload though, so you may want to ask them to refresh the page to join.

Please keep an eye on the sessions on your track and interact with the session leaders to ensure that any required participants can be invited to the session as needed. There may be times as the session is running that people will need to be invited to join the hangout (e.g. IRC participants) – you need to be available to do this when the session leader needs you. If you are not actively participating in the session, feel free to just mute your mic and keep an eye on IRC or listen for when you are needed.

Instructions for starting and stopping the streams is at https://wiki.ubuntu.com/UDS/Sessions.

For Session Leaders

As a session leader your responsibility is to run a quality session, and to ensure that the topic gets a good level of discussion, work is planned and distributed, and the blueprint gets updated with the agreed work items.

Some tips:

• Make sure your Internet connection and computer are working well in advance of the session. We recommend you stop any software or services that is using your net connection (e.g. switch off any downloads or other video streaming).
• The video hangouts will be started and stopped by the track leads (see above) – if you need to invite a new person to a hangout, ask the track lead to invite them.
• In your session you will have people in the hangout speaking as well as people on IRC offering their contributions too. Be mindful of the IRC contributors, and repeat comments and statements of interest from IRC.
• Think of the hangout as the inner ring of the fishbowl at a physical UDS. Unfortunately there only 10 seats on the hangout, so we need to ensure the most active participants are in the hangout. People in the hangout should be speaking and actively participating. If you have an active participant on IRC and have free seats on the hangout, be sure to invite them to the hangout. Likewise, if you see someone who is not contributing on the hangout and there is someone active on IRC, ask the hangout person to move to IRC to open up a slot to invite the IRC person and bring them into the hangout.
• At the beginning of the session, explain the goals and purpose of the session and encourage people to take notes in the embedded etherpad.
• Have the discussion in the session, and be sure to help everyone participate as much as possible. Remember, you should try to keep the most active members in the hangout.
• 10 minutes before the end of the session summarize the key decisions and log work items on the blueprint that are assigned to people. This will provide a great set of next steps to move forward with that blueprint.

For Attendees

Joining a session is easy – just look at the schedule and click on a session to view it. On each session page you can see the video stream, the embedded IRC channel, and the embedded etherpad collaborative note taking. You can also see links to the blueprint and other related content.

You don’t need anything other than a web browser to view sessions but you will need a Google+ account to actively participate in a hangout.

If you want to chat to others in general about UDS, you can also join #ubuntu-uds on freenode.

All sessions will be recorded and available on the schedule when they are completed.

I just want to echo Tony’s appeal to help three year-old Sam who was diagnosed with high risk neuroblastoma, a particularly aggressive cancer. It has spread from the main tumor into his bones and bone marrow. That makes it a class 4 cancer, the most advanced on the scale. The long term survival rate for high risk neuroblastoma is 40%.

As Tony shares:

The good news is that Sam is responding well to chemotherapy. But Sam’s oncologist at Manchester Children’s Hospital has recommended that Sam receives immunotherapy treatment so that his own body can recognise and attack the neuroblastoma if it returns.

The most successful treatment is not available in the UK because some of the drugs are still being trialled. It costs over £250,000 in the US. Which is why Sam desperately needs your help. Carl and Christine are trying to raise the money to send Sam for treatment in the US.

If you would like to donate to help Sam, that would be brilliant. In the UK you can just text SAMS67 and the amount you’d like to donate (£1, £2 £3 £4 £5 or £10) to 70070. Alternatively you can donate on-line at the Sam Shaw Just Giving page. It’s Sam’s fourth birthday this week, so it would be a great birthday present to give him.

Also be sure to join the appeal’s Facebook page.

Your donation to Sam will have an incredible impact on his life as well as his parents, Christine and Carl, who must be having a hell of a time right now dealing with all of this. Let’s all show them that we care by helping them to cover their son’s treatment.

Day 1

Me: "So as you can see the menu across the top already has six entries, I'm not sure there is room for a seventh one?
Customer: "It would be good if it was possible.
Me: "I'll try and see if it looks OK."

Day 2
Me: "OK the menu bar now has seven entries. We had to remove the language choice feature but it's done and amazingly does not look squashed.
Customer: "Brilliant."

Day 3
Customer: "Can you add three more entries please?

"Mummy, why is daddy smacking his face off the desk?"

Arbitrary tweets made by TheGingerDog (i.e. David Goodwin) up to 01 March 2013

• Why do all network file systems suck so much? (2013/02/26)
• To do list : 1) benchmark NFS clients to stop the minions moaning at work. 2) phpunit + spell check generated html. “Hygine” FTW! (2013/02/26)
• I suppose I’d better stare at the women doing water-robics or something. (2013/02/26)
• Check out the #zombiesrun profile for GingerDog https://t.co/JiRnHMqxv0 (2013/02/25)
• RT @phpclasses: PHP Job: Software Engineer (Mobile) (telecommute) t.co/B8b39UceNE (2013/02/22)
• Apparently generating SSH key pairs is too difficult for someone who claims to be a programmer. *sigh* (2013/02/20, Bromsgrove, Worcestershire)
• At the dentists again. (2013/02/20, Bromsgrove, Worcestershire)
• The boss of Iceland comes across as a tit in one clip on the BBC news website. #horse #fail (2013/02/19, Bromsgrove, Worcestershire)
• Scientific tests have shown it is possible to eat too much chocolate :-/ (2013/02/18, Bromsgrove, Worcestershire)
• Today I’m 22. Sort of. 0×22. (2013/02/17, Bromsgrove, Worcestershire)
• Coo. All clear. For now. #AtLeastMyBloodIsRed (2013/02/14, Bromsgrove, Worcestershire)
• Stupid nose. Stop bleeding! I know I ran for 30 mins after it started. But even so …. Soldering iron welcome #DIYMedicine (2013/02/14, Bromsgrove, Worcestershire)
• For the purposes of science (content testing and to ensure they’re horse free) … (I blame @moreteadoctor ) t.co/0u6VFFtM (2013/02/14, Bromsgrove, Worcestershire)
• Going running has become fun after using @ZombiesRunGame … Not sure what my character is going to do with all the underwear he’s found (2013/02/13, Bromsgrove, Worcestershire)
• RT @mikko: TV Emergency Alert System in Montana hacked to interrupt the broadcast, warning that the dead are rising from graves: http:// … (2013/02/12)
• RT @DrunkRogue68: Resignation refused I think as lightning strikes St Peter’s Basilica as Pope resigns t.co/hRnoDGFF (2013/02/12)
• 3/10 b60 #uksnow thin layer. Sticking. Falling reasonably well. (2013/02/11, Bromsgrove, Worcestershire)
• The trees and things outside are covered in a thin layer of dandruff again. I must remember to buy some better shampoo…. (2013/02/11, Bromsgrove, Worcestershire)
• Perhaps I’ll stop listening to t.co/rSOONpOc soon … one day…. #Groovelectric (2013/02/11)
• It doesn’t seem ideal weather for kite flying. t.co/SsGCQurx (2013/02/09)
• So far this morning – “… You’re not a real [monster,] dad” and “you’re not a proper grown up!”. #children #noParentingBadgesForMe (2013/02/09)
• Weee… faster broadband (~18mbit) is appreciated @BeBroadband … but where’s your FTTC ? (2013/02/08)
• BeThere (ISP) are offering to renew my ADSL for £18/month (saving £4). Yet they have it half price (£11/month) on their front page. Hmm. (2013/02/07)
• It’s tempting to answer the PPI phone calls / texts – just to waste their time / money. (2013/02/06)
• RT @StackParenting: Should you let a toddler win? t.co/96WV3d9T #toddler (2013/02/05)
• I wish I hadn’t started making a work related to do list. It keeps growing. (2013/02/02)

Big shout out to the awesome community over at XDA Developers who have been getting involved in the Ubuntu Touch Port-o-thon to bring the Ubuntu Touch images to more and more devices. Daniel Holbach kicked off the port-o-thon the day after we released the code and images last week, and we are already seeing fantastic work going on.

When the initial announcement hit their forum it generated over a 100 posts within a day and there is currently 101 pages of posts on that thread. There is also an Ubuntu Touch Subforum which has seen over 4000 posts already. We are just blown away by the level of interest.

As you can see on the devices wiki page we are already seeing some fantastic work going on to port Ubuntu Touch to additional devices. Here are some great examples of this work (click each link to see the XDA Developers thread):

• Galaxy Nexus (toro)
• Galaxy Nexus (toroplus)
• Sony Xperia S
• Sony Xperia T
• Samsung Galaxy Note II
• Samsung Galaxy Note
• Asus Transformer Infinity
• Nexus One
• Galaxy Tab 2 10.1 Wifi
• Asus Transformer Pad TF300T

Awesome work!

I asked David Planella and Daniel Holbach on my team to kick off a regular engagement with XDA Developers to help us grow an great relationship together. The first call was today and we are kicking some ideas around of how to work more closely together. Stay tuned for more!

Some of you may have seen the news about us transitioning to an online Ubuntu Developer Summit and running the event every three months. If you didn’t see the news, you can read it here. I just wanted to share my personal perspective on this change.

For a long time now I have been attending Ubuntu Developer Summits as part of my work, but for the last event in Copenhagen my wife was about to give birth and so I attended the event remotely. As someone who has been heavily involved in the planning and execution of UDS for the last 10 or so events, I was intimately aware of the remote participation features of the event, but I had never actually utilized them myself. I was excited to dive into the sessions remotely and participate.

For the sessions I dialed into I found the remote participation worked well, but not as well as it could. Sometimes it was a little difficult to hear people (despite us alway encouraging speakers to sit near the middle of the fishbowl), and for the sessions I wasn’t able to actively participate in (due to the timezone differences), only some of those sessions had videos available that I could review after the session had ended. As such, this made it something of a challenge at times to get an overall view of the event; it depended on attendees taking good notes (which generally happens), but I missed the specifics of the discussions.

Remote participation has always been a critical part of UDS and I think it worked efficiently as it could, but these issues were primarily due to the challenge of delivering an in-person event to an online audience and the practicalities therein.

Of course, the real challenge is getting you people to eat these things.

The move to an online event effectively solves the majority of these issues: every single session will be recorded and available for viewing after the fact (which is awesome for not only attendees, but also for the press, partners and others), and with everyone in the hangout facing a webcam and a microphone, the quality of the content should be better too.

For those people who can’t join the session hangout video stream, IRC participation is available, and those IRC discussions will be logged too and provided in addition to the video of the session and the Etherpad notes. This provides a great overview of all the content and discussion in the session.

An online event is also going to open up the event to more potential participants. There are many folks who either can’t physically travel or justify the travel expenses or time away from their work and family commitments who can now participate in the event by simply opening their web browser. With the wide focus in Ubuntu across the desktop, devices and the cloud, we need more specialists rather than fewer to guide us on our mission, and the online event will make it easier for those folks to attend. I think that this will result in wider and more diverse discussion, ultimately helping us to do a better job planning UDS.

Some folks have expressed a concern about not having as much face-to-face time as in a physical event. Of course, video-conferencing will never ultimately replace being in the same room as someone, but I think much of that personal connection is still shared via hangouts. As an example, my team at Canonical used to have team meetings on Skype or a Conference Call and ever since we switched to Google+ Hangouts the sense of personal connection and team spirit has skyrocketed. Sure, it doesn’t replace being in the same room, but when we balance out the benefits of an online event for the reasons I mentioned earlier, it seems like a reasonable trade-off to me.

Iterative Improvements

One thing that many folks don’t see from behind the scenes of planning the physical UDSs is that we have always taken an really rigorous approach to improving and refining the event. This not only includes the structure of the event, but we have iterated after every detail to improve room layouts, A/V needs, timing, remote participation requirements, scheduling patterns, and more. Every detail of UDS has been scrutinized after every event, and the survey we send out is reviewed with a fine tooth comb, all with the goal of squeezing out as much efficiency as possible so the time everyone commits to UDS is as worthwhile as possible.

We are still exploring the alleged productivity-enhancing benefits of light ping-pong.

With UDS previously happening every six months this has helped us to build a pretty bullet proof formula for the physical event, and many attendees comment at each UDS about just how efficient it is and how much gets done. This is largely due to this iterative refinement process.

The first online UDS takes place next week and I think we have a pretty good plan for it, but we are going to go through exactly the same process for reviewing how each event goes and buffing off the rough edges so that works better and more efficiently each time. With us now doing a UDS every three months it should not take too long to get us into a winning formula, and our community are an essential part of helping us to refine these different pieces. As I mentioned in the announcement blog, after the second event we are also going to take a general look to see if an online UDS is serving the needs of the project well in terms of how we plan Ubuntu development.

Got Questions?

I am sure many of you will still have questions about the new format of UDS. Tomorrow (Wednesday) at 7pm UTC. I will be doing my usual weekly Q+A videocast on Ubuntu On Air and will dedicate part of the session to covering how the online event will work and answering your questions. Feel free to bring your UDS and any other questions to the session!

A few days ago we announced Ubuntu for Tablets; the next piece on our wider Ubuntu convergence story. The tablet joins the Phone, TV, Ubuntu for Android, and the Desktop. See an excellent hands-on video review of the current developer build from Engadget.

Today the source and images for Ubuntu for Phones and Tablets (collectively known as Ubuntu Touch) was released.

I know there is some anticipation regarding this release and I just wanted to share a few facts to ensure we are all on the same page:

1. Both Phone and Tablet code and images are available – today we are releasing two things for both the phone and the tablet. Firstly, if you simply want to run the software on a spare device, you can install the images on your device without caring about the code. If on the other hand you want to see the code (and contribute to it) we are also making this available too so that you can build, explore, and hack on it.
2. This is unfinished and in-development software – it is important to remember that this is in-development software and as such is not finished yet. You are going to find that some features and applications are missing, and you will likely find bugs. We wanted to release the code and images early so that our community can try the software, provide feedback, and be able to join the development effort. With this goal to get the content out early we just want to ensure everyone fully understands that this is not yet a final product. I strongly recommend you only install the code/images on a spare handset/tablet and not your main phone/tablet due to the fact it is in-development code.
3. A limited set of devices are supported – the images are only available for the Galaxy Nexus, Nexus 4, Nexus 7, and Nexus 10; these are the devices that our development team has been working towards. We appreciate that you may have a different phone or tablet, but unfortunately support for other devices is not currently planned. We will however be kicking off an outreach campaign soon to encourage and support our community in porting the code to other devices. Stay tuned for more!
4. A new SDK is available also – in addition to the release of the code and images we have also released a new version of the SDK which includes a number of new features, most usefully the ability to deploy a QML app to a device so you can run it!
   • Ubuntu SDK application templates and wizard
   • QML2 UI designer
   • Templates for testing framework and internationalization
   • Deploy QML applications on an Ubuntu Phone/Tablet device
   • Basic terminal (ssh, adb) connectivity tools to the device
5. Know where to find help – if you have questions or queries you should post your questions to Ask Ubuntu by clicking here.

I am sure you are now chomping at the bit to grab the images, check out the code, and get the new SDK release! Go and find all the details here.

Customer: "I'm upgrading CAD and apparently I need 16 Grand of memory."
Colleague: "Bwahahahahaha"

16GB

Oops.
A few months ago, we (that is: Jono and I, the greatest sysadmin team the world have ever known) moved various things around on various servers. And in the course of this action, we completely forgot to put the Shot of Jaq website somewhere. So shotofjaq.org currently is down.
As I say, oops.
Anyway, we haven’t lost the audio (we’re not that bad), so I trawled archive.org for all the episode descriptions and threw them together into a brief listing of all the SoJ episodes with download links. You can therefore see Shot of Jaq again at http://www.kryogenix.org/shotofjaq.html.
Sorry about that, all. We’re rubbish. Let this be a lesson to you.

This tweet has to have been the most popular thing I have ever said. At time of posting it has gained 80 retweets, 25 favourites and many replies/questions.

Work recently bought me a new workstation, so the 1st thing I always do is to dual boot with Ubuntu.

Some might consider me an edge case user. Though as a developer, I like a rather particular set-up. That is, 3 wide screen monitors with the central one rotated 90 degrees for my IDE.

This is something that Windows gets right without having to dig about installing things. While Linux distros have always struggled (in my experience).

Because my tweet gained quite a few questions, I thought it best to reply to them here for everybody to see.

@ankitvad asks what specs. I use for Ubuntu.
Titanium Rimless Glasses from Spex4Less.com
Couldn’t resist, sorry

Dell Alienware X51
CPU: i7
Memory: 8GB
Graphics card: nVidia GeForce GTX 660
Storage: 1TB HDD (Windows) 120GB SSD (Linux)
Mouse: Logictech M570 trackball
OSs: Window 7 SP1, Ubuntu 12.10 64bit
Monitors: 2 x 22″ Dell, 1 x 22″ LG

All 3 monitors are connected to the one graphics card. Two by DVI and one by HDMI.

As I said, this is a working system from a fresh install without updates being applied or any 3rd party packages installed. So the default graphics driver is doing quite well these days

The only downside to this is that the default graphics driver is dog slow and won’t let me play games on Steam The next step will be to get the nVidia binary driver working.

Customer: "I've been sent an email from Russia but ESET Anti Virus has quarantined it."
Engineer: "And?"
Customer: "Well I want to read it."
Engineer: "But it clearly has a virus?"
Customer: "Can you read it?"
Engineer: "No, it has a virus."
Customer: "Should I get them to send it again then?"
Engineer: "You can but I suspect that too will be infected."
Customer: "Is there a way to stop ESET quarantining it?"
Engineer: "Yes, get the sender to clean the viruses off their machine."

Mankind has reached it's evolutionary peak.

Customer: "Is xyz there?"
Me: "I'm afraid he's at lunch."
Customer: "Well he was logged into my machine and I cant close the box."
Me: "Oh, well as I said he's at lunch. If you're desperate, reboot the PC that will sever the link."
Customer: "Cant you close it?"
Me: "I do not have access to his machine, I don't know the password."
Customer: "I need to sort some stuff out on my machine."
Me: "Well this is why I suggested rebooting. If you can hang on xyz will be back in say an hour."
Customer: "Nobody will be here, I need to go out."
Me: "Well reboot then?"
Customer: "But I don't want to do that."
Me: "Then wait for xyz"
Customer: "But I need this stuff now."
Me: "I have no other solutions for you."

/me smacks head off desk!

I had this idea for a little fun literary project.

Tweet the first line of a story. Anyone can reply with what they want the second line to be. You choose the best one of those lines — the one which best fits your desire for how the story should go; this is what stops it descending into a big game of Consequences — and retweet it. It’s a collaborative literary thing. Then people reply with their choice of a third line; repeat until the story reaches a satisfactory conclusion.

Anyone can read the whole story by just reading the tweet stream of the story account. The first couple of tweets should explain the game.

I think this’d actually work, apart from a technical flaw: when the story account retweets a second line from someone, an @-reply to that goes to the someone, not the story account. (Well, it’ll probably go to both, but that’s still annoying and shortens the tweet too much. )

Nevertheless, if someone does this, I’d enjoy contributing a line now and then.

Using Symfony2, DQL and knplabs/knp-paginator-bundle – how to get around “Cannot count query which selects two FROM components, cannot make distinction”

video platform video management video solutionsvideo player

See the video here

The Community Leadership Summit 2013 brings together community leaders, organizers and managers and the projects and organizations that are interested in growing and empowering a strong community. The event pulls together the leading minds in community management, relations and online collaboration to discuss, debate and continue to refine the art of building an effective and capable community.

This year the event takes place on 20th – 21st July 2013 (the weekend before OSCON) in Portland, Oregon and is the fifth anniversary of the event and I am determined to make it bigger, better, and more valuable than ever. Over the previous four events CLS has become the primary annual meeting place for community leadership, and every year we get an absolutely wonderful and diverse attendance spanning technology, education, government, science and more.

At the heart of Community Leadership Summit 2013 is an open unconference-style event in which everyone who attends is welcome to lead and contribute sessions on any topic that is relevant. These sessions are very much discussion sessions: the participants can interact directly, offer thoughts and experience, and share ideas and questions. These unconference sessions are also augmented with a series of presentations from leaders in the field, panel debates and networking opportunities.

Sponsorship

I am currently getting the wheels in motion for the sponsorship for CLS13 and I just wanted to invite any organizations reading this who might be interested in sponsoring the event. CLS is not a particularly expensive event to put on, but I want to expand the usual sponsorship this year to add a little more polish than usual to the event. As such, I am looking for companies or might be interested in supporting the event and getting exposure to community leaders across a range of industries, but with a strong focus on technology.

One of the messages I emphasize in my opening plenary is that the sponsors of the event don’t buy editorial direction or influence (as the event is very focused on being free, open, and attendee-content driven), and as such sponsorship of CLS is very much an affirmation of support of the event for the right reasons. As such, association with CLS as a sponsor has typically reflected very well on those companies who have sponsored in the past. Such companies have included Intel, Microsoft, Black Duck, Oracle, O’Reilly, OpenNMS, and others.

If you are interested in supporting CLS, please drop me an email to jono@jonobacon.org. Thanks!

Example user ‘iain’

sudo mkdir -p /chroot/iain/home/iain
sudo useradd -M -d /home/iain iain
sudo passwd iain
sudo chwon iain: /chroot/iain/home/iain

sudo nano -w /etc/ssh/sshd_config
# At the end of the file, add:

Match User paypoint
    ChrootDirectory /chroot/iain
    AllowTCPForwarding no
    X11Forwarding no
    ForceCommand internal-sftp

sudo /etc/init.d/ssh restart

I had a need to add ACL rules to entities at the repository level.

My biggest struggle was getting dependancy injection working.

This is what I finally came up with after a fresh mind and an instant coffee: