Greg and I have been obsessed with tasty and healthy sweet potatoes lately, and have incorporated it into the unlikeliest of places...like breakfast pancakes!
In January I was sad, but not surprised, to see the Rocky Mountain News shut down. They made a cool video did some nice retrospective posts, and shut down the operations. Since then the Denver Post (which was kind of a part owner of the Rocky) has picked up some of the more popular journalists and probably some of the other staff.
So, some of the staffers, photographers and journalists got together and decided they were going to do things right. They weren't going to be driven by corporate greed like the evil capitalists, they were just going to do the news and make enough money to keep the business rolling. They created a site I Want My Rocky as a rallying point for the former employees of the news and as a place to gather interest in a proposed online-only pay-for-content news source.
Old Media: Guess what, you're old and you're doing it wrong
I was most recently drawn to the site by a post from Cindy House - one of the main people in the post-RMNews project - about New models, new challenges. She talks about how they haven't been successful in getting a readership, so they can't afford good content, so they can't build the readership. So, they're going to start providing consulting services, specifically: "Web design, search engine optimization and editing/writing services to other businesses."
So, how good are their consulting services?
Often the homepage for a service provider is weak. This is the so-called "Cobbler’s Son Has No Shoes" effect. However, there are some painful mistakes on the IWantMyRocky site which are actively hurting their efforts. Let's look at the home page:
How is babby formed? We needed to know.
We think we found out.
In all seriousness, little Henry Otto (as we call the baby in utero) is now 3 months along and due in the middle of March. Yay procreation!
(p.s. let's face it: it was only a matter of time before we became breeders)
I hate trying to remember which version of RAID does what. Maybe this will help:
The code freeze for Drupal 7.x is looming large on the horizon. From that point on we will be limited in what kinds of changes we can get into Drupal core. For some the code freeze is a time of relief: it means we are down to bug fixes and the final release should be coming soon. For others it is a hard time - bug fixing isn't always as fun as adding new features.
So, as we head into feature freeze it seemed like a good time to run some statistics on who has been contributing the most to Drupal 7.x so far.
Contributors to Drupal 7.x. Through August 10th
Following on from previous times that I've run these stats, I've published documentation of the process to get the data on groups.drupal.org. This time I went straight to the commit messages stored in database tables on drupal.org This has the benefit of counting new files as well as old files (the last times I did this it only counted changes to existing files).
So, who are the top 10 people based on the number of times their name is in a commit message?
The total number of mentions is 3133, so those top 10 are responsible for roughly 33% of the code. On the flip side, people with 3 or fewer mentions are responsible for roughly 15% of the code. We still have a long tail of 222 people who are mentioned in only one message. We see a fairly typical "long tail" distribution: the people who are most involved do a lot of the work, but the people who only get mentioned a few times each are still responsible for a large number of commits when aggregated together.
|Commit mentions||Count of people with that number|
Times Square got some new lane lines for biking and, apparently, horses.