In this section, we cover the highlights of Planet Fedora - an aggregation of blogs from Fedora contributors worldwide. This edition covers highlights from the past three weeks.
Contributing Writer: Adam Batkin
The big news these days was the debut of opensource.com/. As Jan Wildeboer described it: "Finally. A place to discuss, learn, promote everything open...We started this community to allow people from all across the world, regardless of job and skills, to communicate and foster more Open. Let’s look (far) beyond software. Lets talk about the Open Everything that this world so desperately needs."
Karsten Wade followed-up on what opensource.com is and isn't. "I’ve been watching some of the discussion around it and have some comments about a bit of confusion some folks are having. Please pass this along."
Greg DeKoenigsberg posted about Fedora's Goals. "I’m glad to see a lot of thoughtful discussion around the topic of Fedora’s larger goals, and I’m particularly glad to see some new blood driving the discussion. Fedora’s ability to attract outstanding new talent to the party is one of the things that makes it such a remarkable project."
Paul W. Frields added some additional points about Fedora's goals. "The ability of any Fedora contributor to scratch his or her own itch is one of the strengths of our community. It has yielded many exceptional contributors, brought volunteer leadership to many of our project teams, and produced a steady enough stream of young contributors to merit an annual scholarship recognizing their achievements."
Michael DeHaan was amazed by Gource, "an amazing program for visualizing commit history in a git-based code project. What I like about it is that it can also show what areas of the project are active in an easy to understand way, to show whether there is community around a whole project or just aspects of it."
If you have ever tried to work with CVS and struggled with the fact that the output from "cvs status" is mostly useless, particularly with large projects, Till Maas has</ref>http://blogs.23.nu/till/2010/01/cvs-status-parser-script/</ref> the answer. "I quickly wrote a simple MIT-licensed python script that creates an output like modern scms do."