The trees and flowers are starting to bloom, which means it's time again for Google Summer of Code to get into full swing. As we try to do every year, we want to have a project or two focused on Camino. We've had some very good contributions in the past and have found it an excellent way to get students involved in our community and in open-source in general. While they do get paid for the work, I think everyone would agree that the primary reward is the experience gained from being a part of a real project, writing real code, with real deadlines.
To get the ball rolling, we've seeded our SoC wiki with some ideas and past projects so you can gauge the level of commitment and workload that gets approved. This list is far from comprehensive. We'd love for you to suggest something new! The best part is you don't have to volunteer to do it, just suggest it so that someone else can take your idea and run with it. To suggest ideas, all you need is a wiki account which you can get by joining us in #camino on irc.mozilla.org and asking ss or ardissone for an account (we've locked down registration due to past spamming).
What if you want to participate in Camino's SoC? Pick a suggestion from the vetted list on the wiki and write up a proposal on how you'd go about accomplishing the task over the course of the Summer. The more detailed you can be, the easier is for us to gauge whether or not you know what you're talking about and how successful you would probably be. Applications are submitted via Google's site and are accepted March 23 - April 3. Feel free to come and discuss your proposal with us in #camino before you submit it. We'll be able to help point out areas that need further detail and ensure you're on the right track.
That doesn't give us much time to get a list of great ideas for people who want to apply, so put on your thinking caps! I can't wait!
After being a Twitter member for a few days, and a Facebook member for much longer, it's hard to reconcile the two.
I know it's simple to have everything you tweet show up on your Fb, but that doesn't seem right to me. For starters, their structure is fundamentally different. Fb wants something in the form "Mike is watching dancing bears" while nobody on twitter posts that way. So if you tweet, it can end up awkward and wrong in Fb ("Mike Dancing bears, oh my!"). Then there's the re-tweets, hashes, and messages that are totally out of place in a Fb status ("Mike RT @ryanseacrest It's Chuck Norris' 69th birthday today"). The two great tastes just don't taste great together.
So I'm left updating status in two places, which I really don't want to do. As a result, I find myself ignoring Fb, which is a shame because it's a great way to stay in touch with (and locate) old friends. Maybe I'll just have to suck that part up.
What's the lure to Twitter for me? I think it's fun watching celebrities be real and normal people. It's fun watching them send messages to each other. It's fun that you can even send messages to them and they *read them*! Whether it's Shaq or Ryan Seacrest, John Mayer, Carla Hall, or Dr Drew, or just people that you know (or those that you don't!), this *is* new media. PTI tweets to get topics for the day's show. Why even have reporters? Why involve the middle-man? Let the people speak for themselves. Immediate and unfiltered.
So what to do about Fb? What to do, what to do? I'll get back to you. In the meantime, don't be shocked if I'm not updating my Fb status as often as I used to.
I've decided to jump feet-first into the 21st century and start tweeting. Don't ask me why. If anyone cares, I'm at http://twitter.com/mikepinkerton
The tail end of last week saw the quiet release of Camino 2.0 beta2. We're getting pretty close and I'm really excited about the progress the team has made. Especially with some of the (I'll say it: wacko!) features other projects have recently debuted, the team has stayed true to their goals and beliefs about simple software. I believe our users will appreciate that.