Compilation of Ubuntu Planet's blogs from around the world
Please subscribe to RSS Feed! :)
Please subscribe to RSS Feed! :)
Ubuntu Malaysia
Kelantan Ubuntu LoCo Team
User login
Navigation
Who's new
- mayonks
- naiimullah
- iwe
- bizkut
Who's online
There are currently 0 users and 1 guest online.
Subscribe to Ubuntu Malaysia by e-mail
Search
Technology
Please Note: This is only relevant to single-user desktop installations of Linux. The issues I will discuss here don’t apply to servers. In fact, the exact opposite applies there.
“Don’t run as root” is an oft-repeated mantra of *nix security. While I agree 100%, it’s not as big on the desktop as some would think. I’d like to point out why here. I still believe you shouldn’t login as root, but I also believe that it’s up to each user to make their own decision.
Think about the data on your computer. What matters to you? E-Mail? Documents? Images? Most of us have things like family photos, financial records, personal communications, saved passwords, or other sensitive or irreplaceable data. This is what we want to protect. When I backup my desktop, I backup my home directory. I don’t backup my OS install, software, or anything else that is not private or difficult to replace. Think of this as the “important stuff.”
So, let’s talk about the important stuff. What users have access to YOUR important stuff? Most likely, your own user, and the root user. So, great, not running as root eliminates one of the possible users that can access your file. So what user do you run as? Your own user. So it’s pretty obvious that not running as root doesn’t restrict access to the important stuff.
Need proof that your data is no safer under your own user? Think about running “rm -rf /” as root or as your own user. What happens to your data either way? It’s gone. Don’t run this, just think about it.
So what do you gain by not running as root? Well, your system is a lot less likely to be the victim of an ongoing compromise. As root, an attacker can modify your operating system to their liking. Think that’s not much? Guess what: your ssh client now sends the username, host, and password for any system you connect to to a server in China. Or maybe new files you create are uploaded to an anonymous file-sharing site on the internet. Perhaps every key you touch is recorded to grab usernames, passwords, credit card numbers, and your most personal conversations. Or maybe an attacker uses your computer as a middle man for downloading child pornography. That will be fun to explain to the FBI.
So, obviously some things need to run as root: system configuration tools, for example. However, running these using sudo limits your exposure to just these utilities, rather than the thousands (millions?) of lines of code in a full desktop environment.
In short, if you want to run as root on your desktop, go for it. But know the risks, and know the consequences. On the other hand, don’t chant “don’t login as root” as if it’s a magic bullet for security.
Original Source: http://feedproxy.google.com/~r/PlanetGeorgia/~3/gGvw4Zd0XyU/
So. Someone made some stats about GNOME and it turns out that some people are very angry and some people are defensive and others are angrily defensive and many are indifferent (but I’ve not seen any angry indifference yet, although Mr Stedfast’s post comes close).
I work for Canonical, so it’s hard for me to pretend I have no bias in this. I’ve been a GNOME user for much longer, but I’ve not contributed to the project in any meaningful sense, mainly because I’m a sysadmin who codes some rubbish in his spare time. Therefore you might wish to largely ignore anything I say.
I have a myriad of reactions to this, all of them my own and just as subjective as anyone else’s, but there’s one that I think is at least novel in amongst the discussion I’ve seen so far…
Where do we go from here?
Is it the case that the angry people will only ever be happy if the defensive people hire tons of engineers with a job description of “go hack cool GNOME stuff, but only within GNOME’s processes/domain”? If so, how many is enough? (Note that I am a lowly sysadmin, this does not constitute anything close to a committment to doing anything, I cannot speak on behalf of those who sign my paycheques, I speak only for myself ;)
Or is it the case that better dialogue and understanding between the angry people and the defensive people will lead to a broader appreciation of the different roles that different organisations (and the forgotten individuals who make up the majority of code owners in GNOME) bring to the table in this great game we call the Linux desktop? If so, who should be having that dialogue and why aren’t they doing it already?
Or is it the case that the angry people are actually angry about something more fundamental and should actually turn their anger on their own paymasters for paying them to make a cool desktop, but not then taking it to the masses in any meaningful sense?
Or is it the case that this is The Internet and you can barely open a web page without someone shoving a thundering firehose of bile into your face, and we should all do our best to just get on doing the awesome things we do and be happy that we are alive and happy?
I’m certainly going to do the last one no matter what happens, but I think it would generally be more useful for people to be talking about solutions than arguing about who is the most or least evil. I’m not a GNOME member/contributor/founder/boardmember or otherwise invested party, I just use it, so my words are irrelevant :)
Please enjoy your day :)
Original Source: http://www.tenshu.net/archives/2010/07/30/wheeeeeeeeeeeeeeeeee/
So. Someone made some stats about GNOME and it turns out that some people are very angry and some people are defensive and others are angrily defensive and many are indifferent (but I’ve not seen any angry indifference yet, although Mr Stedfast’s post comes close).
I work for Canonical, so it’s hard for me to pretend I have no bias in this. I’ve been a GNOME user for much longer, but I’ve not contributed to the project in any meaningful sense, mainly because I’m a sysadmin who codes some rubbish in his spare time. Therefore you might wish to largely ignore anything I say.
I have a myriad of reactions to this, all of them my own and just as subjective as anyone else’s, but there’s one that I think is at least novel in amongst the discussion I’ve seen so far…
Where do we go from here?
Is it the case that the angry people will only ever be happy if the defensive people hire tons of engineers with a job description of “go hack cool GNOME stuff, but only within GNOME’s processes/domain”? If so, how many is enough? (Note that I am a lowly sysadmin, this does not constitute anything close to a committment to doing anything, I cannot speak on behalf of those who sign my paycheques, I speak only for myself ;)
Or is it the case that better dialogue and understanding between the angry people and the defensive people will lead to a broader appreciation of the different roles that different organisations (and the forgotten individuals who make up the majority of code owners in GNOME) bring to the table in this great game we call the Linux desktop? If so, who should be having that dialogue and why aren’t they doing it already?
Or is it the case that the angry people are actually angry about something more fundamental and should actually turn their anger on their own paymasters for paying them to make a cool desktop, but not then taking it to the masses in any meaningful sense?
Or is it the case that this is The Internet and you can barely open a web page without someone shoving a thundering firehose of bile into your face, and we should all do our best to just get on doing the awesome things we do and be happy that we are alive and happy?
I’m certainly going to do the last one no matter what happens, but I think it would generally be more useful for people to be talking about solutions than arguing about who is the most or least evil. I’m not a GNOME member/contributor/founder/boardmember or otherwise invested party, I just use it, so my words are irrelevant :)
Please enjoy your day :)
Original Source: http://www.tenshu.net/archives/2010/07/30/wheeeeeeeeeeeeeeeeee/
Earlier this week at GUADEC, the always affable Dave Neary presented his GNOME Census work. Unfortunately, I was not there to see it, but I read his excellent post on the topic.
One of the reactions from the survey was that Red Hat are responsible for 16% of the contributions to GNOME whereas Canonical are responsible for a measly 1%.
Of course, this has generated some flame, such as a particularly angry post from Greg DeKoenigsberg and the rather pithy response from Jeffrey Stedfast. Greg is clearly pissed, and Jeffrey is clearly pissed at Greg being pissed, and I suspect Greg is going to get even more pissed at Jeffrey being pissed. The worse thing is that they are both going to be pissed at me for this blog post.
First I want to put these figures in perspective and then I want to talk about how we read the figures we do have.
I think the GNOME Census report is excellent, and it provides some excellent visibility into contributions in GNOME, but it only takes into account upstream contributions to GNOME itself. What the report doesn’t take into account are upstream contributions that are built on the GNOME platform but (a) not part of official GNOME modules, and (b) hosted and developed elsewhere, such as Launchpad. As such, while the report is accurate for showing code and contributions accepted into GNOME, there are also many projects built on GNOME technology that are not taken into account due to non-inclusion in GNOME modules or being developed outside of GNOME infrastructure.
As a general rule, Canonical staff develop inside Launchpad. The reason is simple; Launchpad and Bazaar provide a powerful development environment that was also built by Canonical and we therefore have lots of internal skills and best practice based on these tools. Launchpad is also a fundamental component in Ubuntu development and all the software we develop ultimately ships in Ubuntu, so using the same development forge makes sense. Finally, the site is a Free Software and Open Source project, so there really no philosophical reason to move, testified by the 18,000+ Free Software projects happily using Launchpad already.
Canonical is actively developing upstream desktop software, but doing it in Launchpad. Some examples include:
- notify-osd
- Messaging Menu
- Application Indicators
- Indicator Applet
- Indicator Date Time Applet
- Sound Indicator
- Me Menu
- Indicator Global Menu
- Unity
This is by no means the full list, and is other work such as Simple Scan, the Hardware Drivers tool, Computer Janitor, and more. Many of these contributions (such as Application Indicators and Simple Scan) could bring real value to GNOME, but they have not been accepted. I know that the Canonical engineers who work on them would be delighted if they were included in GNOME.
The above list also doesn’t include significant upstream investment in other areas such as Upstart, Bazaar, Launchpad, and a full team building Ubuntu. I don’t want to turn this into a “who contributed more” competition, but I think for some to suggest Canonical is a bad citizen who is not contributing upstream code is unreasonable. To suggest that Canonical has limited code inside approved GNOME modules is fair.
So that was the first thing I wanted to clarify; Canonical does invest heavily in upstream work, but GNOME is not the only home for upstream contributions.
If there is one thing that the GNOME Census has really outlined is that we should all be proud of Red Hat and their contributions to GNOME. You only have to take a look at all the red items on this image to get a feeling for the wonderful work that Red Hat is doing inside GNOME. Novell too. Look the green items in there; Novell has done a wonderful job maintaining many modules inside GNOME. In fact, there are many companies investing inside GNOME modules and inside GNOME infrastructure. I don’t believe it would be fair to undermine these contributions in any way; they are testament to the ethos of those companies and their commitment to GNOME. All of the people working at those companies are doing good work within the spirit of Free Software.
Likewise, I don’t think it is fair to undermine Canonical’s contributions just because many of them exist outside of GNOME. Our engineers are also doing good work within the spirit of Free Software. I have never claimed for a second that Canonical are equal to Red Hat and Novell in terms of our accepted contributions in GNOME; it is clear that there are far few contributions from Canonical staff inside accepted GNOME modules, but this does not for a second mean that Canonical is not (a) producing upstream contributions and (b) heavily invested in the GNOME platform. Ubuntu, our primary product is a GNOME desktop, and the vast majority of our engineers are GNOME users and developers and they work every day on a GNOME based product.
So in a nutshell, this is my take: both Red Hat and Canonical invest heavily in Open Source development, but they do it in different ways and different places. The GNOME Census clearly outlines that within GNOME modules, Red Hat are doing far more, but that doesn’t mean that Canonical are sitting on their thumbs and doing nothing, far from it.
Original Source: http://www.jonobacon.org/2010/07/30/red-hat-canonical-and-gnome-contributions/
The Augen Android tablet being sold in Kmart stores at the moment is (shockingly) running a 2.6.29 kernel and Android 2.1 on top of that. It's also (shockingly) currently impossible to get hold of the source code for the kernel - Augen (whose corporate address is a small unit in Florida) say that the software comes installed on the units by the OEM and they don't have any access to the source either. This isn't an excuse, of course, and they say that they hope to have it on their website within the next few days - but even so, it seems that the Android device GPL violation trend is still on course. It'll be interesting to see what the long-term outcome of this kind of violation is, especially with these devices increasingly being sold by mainstream stores.
Original Source: http://mjg59.livejournal.com/126162.html
After many months kubuntu.org got a new look, complete with new logo. Many thanks to Ofir for his patience in seeing this through.
During the Platform sprint in Prague I took Aurelien Gateau, doko and a couple of nice chaps from SuSE Prague canoeing on the awesome whitewater course near the city centre.
Looking confident at the top
This flatwater is easy
King of the wave
This blury photo is the last anyone has seen of Aurelien, if you live downstream of Prauge please look out for him in his blue canoe
<!--break-->
Original Source: http://www.kdedevelopers.org/node/4292
Do you want to be part of the Ubuntu News Team? Do you want to be part of a long standing and growing part of the Ubuntu Community? Looking for a place to contribute. Then the Ubuntu News Team is for you!
The Ubuntu News Team via the Ubuntu Weekly Newsletter boasts of bringing more than 200 Issues full of what’s happening in and with Ubuntu and the community that surrounds it. This happens as we gather and summarize those happenings a week at a time to record as well as report how Ubuntu matures through all it’s growing pains and we want you to be part of the team!
First let me say we have some wonderful people who continue to donate many weekend hours to producing the Ubuntu Weekly Newsletter but we could always use more help.
In a perfect world we would have all the summaries written by Friday afternoon and all that would need to happen on Sunday would be adding the Stats, Updates and Security portions along with the editing. As it is right now myself and a few others spend upwards of 10-15 hours each Sunday to get UWN out the door. In the case of weekends when I’m traveling on Sundays then there are times when the newsletter often goes out a day or two later than our announced published dates. (Sorry about that by the way)
Take a look at Issue 200, 201, 202, and 203 to get an idea of what we are writing about and in the meantime let me tell you a little about each section and how you can help.
We often get asked about people writing original content for the newsletter. The newsletter right now reports and summarizes posts that have been added other places. However in the near future you will be able to submit original content to the Fridge. - More about the Fridge in another post though.
LoCo News – Do you like to find out what is happening with all the LoCo Teams. Would you like to report and summarize what the various teams are writing about? This section is just as it sounds – we report on what the LoCo Teams are doing.
Launchpad News – This comes from the Launchpad (LP) Team blog. Most of the time these posts are short enough to include in there entirety sometimes we have to summarize them, but Matthew Revell and the other LP team members usually write very clear and concise items to share with the world about what’s going on with LP. So if you want to check for Launchpad news and be responsible for adding it to the news letter lets talk.
The Planet - This section is a little tricky but we’re all smart so it’s easy to figure out. Depending on what people are writing about this could be added to The Planet, General Community News, Blogosphere, or even In Other News sections of the newsletter. However If you feel like you want to search Planet Ubuntu each week and add the summaries to the planet section we can work it all out.
In The Press – This section is where we post those articles that have been written about Ubuntu in the Press. This usually means those print publications that also have a web presence. However there are some exceptions and again - if it’s a good story then we can figure out where it needs to go 
In the Blogosphere – these are blogs that are main stream but may not have a print publication, or commercial backing behind it. However, blogs from the planet often get included here as well.
In Other News – this is about those items that are related to Ubuntu - such as great Linux Stories, Canonical press releases, Canonical Partners who write about Ubuntu or other Corporations that discuss Ubuntu. However, those really quirky and fun stories that are related to Ubuntu in some for or fashion that doesn’t really fit in any other area can go here as well.
Featured Podcasts – this is summaries of podcasts/videocasts such as the Ubuntu UK Podcast, Full Circle Magazine Podcasts, Ubuntu Podcasts, At Home with Jono Bacon Community Q&A UStream TV casts. If there are other Ubuntu related casts that should be on the list we need to know that as well. So if you are interested making sure these casts get included in the newsletter that would be great!
Weekly Ubuntu Development Team Meetings – We try to offer the meeting minutes for the Development teams that are list on the Fridge Calendar. While some teams don’t really have formal meeting minutes some teams do. If you would like to verify the links each week and make sure we aren’t missing any teams then this the section for you!
Xubuntu, Kubuntu, Edubuntu - If you are on one of these teams we could always use your help to make sure we include the current news about these derivatives as well.
Currently we have people working on summarizing links or posting to some of the areas but it is the same people giving up part of their precious weekends and while all of us enjoy and like being part of bringing this to the community – the quote – “many hands make light work” really rings true here and if we could get a couple dedicated people per section then people could trade off what weeks they can cover and make the whole process an even more enjoyable one for everyone.
We are also looking at adding an HTML version of the newsletter to be sent to folks via a mail service like mail chimp. Right now we don’t have true matrix for what people are reading or clicking on 1st for the newsletter. It would be nice to have those figures. So if you are interested in being part of this test HTML newsletter please email me and let me know – akgraner * ubuntu * com. This will also allow us to include photo’s, videos and some formating that the current plain text version does not. The plain text, and the wiki versions will still be available. If you want to help with this process please let me know that as well.
I have to thank all those folks who currently give of their time to make the newsletter what it is – Lizar Siri, J. Scott Gwin, Penelope Stowe, Mike Holstein, Nigel Babu, Daniel Caleb, Jonathan Carter, Nathan Handler, and all the folks who continue to write about Ubuntu so we can bring you UWN each week!
Here are some links to help you learn even more about the Ubuntu Weekly Newsletter. Thanks in advance for your continued support and help in making this an even better source of information for the busy Ubuntu user/contributor/developer.
Ubuntu Weekly Newsletter Wiki – https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/
Checklist and Editing Policy Wiki – https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/EditingPolicies
HowTo Guide for the Newsletter – https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/EditingPolicies/HowToEdit
Newsletter Publication Schedule – https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Schedule
Section Guidelines and Suggestions – https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/SectionGuidelines
We also have a googledoc, wiki page and ietherpad areas for you to work on the newsletter at as I am aware that some people prefer to work on UWN in places other than the wiki. This also keeps editing conflicts down to a minimum on Sundays when everyone is working together on UWN.
So stop by #ubuntu-news on freenode or email me and lets get you started on your way to contributing to UWN. Looking forward to hearing from you! Many Thanks!
Original Source: http://akgraner.com/?p=627
.jpg)
Welcome to the Ubuntu Weekly Newsletter. This is Issue #203 for the week July 18th - July 24th and is available here.
In this issue we cover:
- Last call for Maverick server papercuts
- Ubuntu Maverick open for translation
- Native readers: extending the Beta
- MOTU Interview: Maia Kozheva (sikon / LucidFox)
- An Interview With Silver Fox
- Ubuntu Developer Week Re-Cap
- Ubuntu Stats
- Approval and Re Approval Process
- LoCo Council July Meeting minutes
- Delivering the Ubuntu Colombia Contact
- Stepping Down from Ubuntu Bangladesh
- Dun Laoghaire July Geeknic
- Ubuntu-fr at Les Vieilles Charrues
- Launchpad News
- Ubuntu at Non-Technical Events
- More cleansweep.
- Discussion request: multilingual posts on Planet Ubuntu or not?
- The Official Ubuntu Book – 5th Edition
- This week in design – 23 July 2010
- Getting Started with Ubuntu 10.04 is now available in Greek!
- How to Ask Smart Questions by Martin Owens
- Ubuntu One iphone client, source code released
- Ubuntu Translation Teams Healthcheck
- An invitation to join Ubuntu’s Q&A group on Shapado.com
- Akademy 30 second interviews, Eben Moglen, Helsinki, Prague
- “Blog about what you’re doing”
- Bugs vs Blueprints
- In The Press
- In The Blogosphere
- Windows or Ubuntu?
- Linux Box To Market Ubuntu
- Dell drops Ubuntu PCs from website… for now
- Is Linux Too Much for One Mere Mortal to Handle?
- Rackspace’s Risky Open Cloud Bet
- Featured Podcasts
- Weekly Ubuntu Development Team Meetings
- Upcoming Meetings and Events
- Updates and Security
- and much much more!
- Amber Graner
- J Scott Gwin
- Liraz Siri
- Nathan Handler
- Penelope Stowe
- Daniel Calab
- And many others
This issue of The Ubuntu Weekly Newsletter is brought to you by:
If you have a story idea for the Weekly Newsletter, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!
Except where otherwise noted, content in this issue is licensed under a Creative Commons Attribution 3.0 License BY SA Creative Commons License
Original Source: http://fridge.ubuntu.com/node/2090
I have always been a fan of helping in any way I can to encourage people to support small organizations and businesses who are doing their best to be successful by working hard and providing a friendly, honest service.
For the earlier part of this week I am in The Hague at GUADEC, and I stumbled across a small espresso shop that is the embodiment of these kinds of small business. It is impeccably clean, the food is awesome, the coffee is fantastic, it is good value, and the guy who runs the shop is the definition of kind and welcoming. Oh, and it has great wi-fi too. 
So, I wanted to share with all my friends who are visiting GUADEC too to come and support this guy’s small business, drink some coffee and leach his Internet.
The address is: 7 o’clock Espressobar, Wagenstraat 187 2512 AW Den Haag and if you are walking back to the hotel before you walk over the small bridge you will see it on the left with a big Coca-Cola sign above it.
More details on the website.
Original Source: http://www.jonobacon.org/2010/07/27/awesome-guadec-espresso-and-coffee-bar/
Tony Whitmore (@tonywhitmore) blogged about The Quest for Originality which got me thinking about the podcast that we make with @ciemon, @daviey and @lauracowen.
Over the weekend at OrgCon there was some discussion of originality. The subject was brought up when talking about the creative business, with original works being “worth” something, perhaps more than a digital facsimile of some work. So for example a concert is a one off live event is worth paying for, whereas an MP3 is “worth” less because in part it’s easily duplicated and thus lacks originality. (I’ve paraphrased and perhaps twisted the meaning of the discussion to suit this post, but I’m sure you know what I mean).
I guess there’s a couple of things that I think of in relation to being original. There’s originality with reference to the ‘competition’ and originality in terms of us not being stale over time. Both require some effort to achieve, and in my mind we should be doing both.
Competition in podcasting is hard to define. People have a finite amount of time in their lives to listen to podcasts, so we’re competing with other things people would rather be doing, like spending time with family, programming .. or whatever else our listeners do in their ‘spare’ time. People also listen during a commute, jog or some otherwise ‘dead’ air-time. So we have to be compelling or people will do ‘other things’ than listen.
People thus have a limited amount of time to listen to podcasts, and will thus only consume a limited number of shows. I doubt anyone listens to every FLOSS/Linux podcast, but I’m sure most people have tried them all to see which they prefer. So we need to appeal to people if we want people to listen to the show.
I do want people to listen to the show by the way. Whilst we do this for fun (and no financial profit), if nobody downloaded the show I think we’d probably stop doing it. The idea of being on stage to the sound of one hand clapping doesn’t appeal (to me at least). Others are happy to continue making a show no matter how many people listen.
There are of course other podcasts which do pretty much the same as us, Tuxradar and Full Circle Magazine are two good examples with a similar format, but with their own style. Then there’s the likes of Linux Action Show, Linux Outlaws and The Linux Link Tech Show who all have their own style and niche. Every podcast is clearly different, with presenters having their own expression, shows of varying duration, different personalities, quality and frequency. None (including ours) are perfect, all are serving a segment of the market successfully.
Within our own podcast we’ve evolved slightly over the 2.5 seasons we’ve been running, but for the most part the format has stuck. We have introduced new segment ideas, and refined various elements of the show, but in general we’ve stuck with a formula that works for us, and gets us some listeners.
Right now each episode gets downloaded about 5K times in the week after release with a long tail of 13 weeks to hit 10K downloads. After a year each episode hits around 18K and after two years each episode hits around 32K downloads. Clearly as with every podcast, we have no idea how many of those downloads translate into listens. We’re not so naive to think they all do, but we don’t know what the proportion of downloads to listens is, and I don’t think we ever will do. On that subject, for the record, I don’t think we need to do any kind of survey or tracking to try to figure that number out. I’m personally happy to know that some thousands of people download it and some of them listen to it.
When we started I think we had some original concepts compared to others within our space. We’re family friendly, (usually) well prepared, not North-American (not that being American is a problem, but many FLOSS/Linux podcasts come from there, so it’s nice to have one with a non-American ‘accent’ in my opinion), (mostly) above average audio quality, (generally) on time with a regular schedule and made by contributors to the Ubuntu project rather than bystanders. Whilst other podcasts had some of those elements, not many had all.
Since then we’ve perhaps stagnated, and whilst we have introduced new concepts and made changes at the ‘backend’ to streamline the way we produce the show, we haven’t had much in the way of revolutionary changes that the listeners would notice. The big question is I guess is ‘should we?’.
We could do as Linux Outlaws and TLLTS do and have a live part of the show. We tried this in the past but technical barriers (like Tony having a crap internet connection) stymed that. It’s also tricky in that we take tea breaks and eat cake between segments, rather than record it in one go. We could open the show up to have callers phone-in now we have a nice telephony setup. Maybe we should drop the ‘season’ system and just produce a show constantly with no breaks. We could change the duration, presenters, format, style or any other part of the content, but again, ‘should we?’.
There is the danger that we could break something that didn’t need fixing. Perhaps it is broken and we just don’t know that. Perhaps we’re in danger of burning out on a treadmill to churn out episodes that we don’t enjoy, if we don’t change. I don’t know. Do you?
Original Source: http://popey.com/blog/2010/07/27/change-for-changes-sake/
