From Fedora Project Wiki

Here's a summary of stuff I did during the two months I was in and out of Raleigh, NC, for my summer internship with Red Hat in 2010.

I work for Red Hat's Community Architecture team as a general programmer and guy who does stuff out in the community. It's kinda generic.

Automating community statistics: datanommer

At the end of the summer, I have a much clearer goal of how I want to (help) automate the gathering and analysis of statistics within Fedora than I did at this time last year or even at the beginning of this summer.

Instead of attempting to solve every person's statistical questions in a web interface that does not update very often, we're writing code that grabs information from each application or "thing" we use in our community to communicate and get things done. A subset of that information will be generated into graphs automatically on Fedora's infrastructure, but the bulk of it is meant to be run locally for one's own research and hypotheses.

The application is called datanommer and is community-neutral — currently the only data-grabbing code is for MediaWiki-powered wikis, and it's been tested with fedoraproject.org/wiki and the English Wikipedia (works just fine). It's written in Python, which makes it the easiest for others to contribute to.

The next steps:

  • Write more code to download more data from more applications
  • Write more code to create more types of graphs
  • Write documentation
    • ... especially on creating complex queries (chaining different pieces of data together)
  • Fix the ugly code in cli.py:main
  • Get some data analysis integrated into Fedora Infrastructure

Improving Fedora's brand

Collaboration is key

There were a ton of people who helped out and made my life sane while I worked on this. Máirín Duffy and others lurking in #fedora-design helped with making me feel better about my mockups and final SVGs. Emily Dirsh (a recent Design Bounty Ninja) created an INTERACTIVE WEB APPLICATION (whoa) to test our options for text fonts. Pam Chestek helped me understand trademark law a little better than I used to.

One thing I've learned is that if you want to thrive in an open source community, you have to delegate responsibility (so you don't go mad) and then be able to bring back together those contributions, and this is a great example of that.

I spent a lot of time between last year's internship and this one tracking down original SVGs for all of Fedora's common logos, cleaning up the SVGs, and writing a new revision of the current logo usage guidelines as new brand guidelines, encompassing logos, colors, fonts, and more. This has been done in cooperation with the Design Team and Red Hat Legal (props to Pam Chestek).

There was an attempt this summer to get this done, but I had so many things that I was working on at once that this item got neglected a little bit. What's done:

  • All logos with a TM symbol in them (Fedora logos and Fedora Remix logos) have had their SVGs finalized.
  • Changes have been approved to adjust fonts in the FUDCon logo and Foundations artwork.
  • MgOpen Modata has been deprecated in favor of Comfortaa and Cantarell (with a fallback to the Droid Sans family for Cantarell).

What needs to be finished up:

  • Body text for the guidelines — just having pictures doesn't make it obvious enough to most people what you mean.
  • Changes made to adjust fonts in the FUDCon logo and Foundations artwork, and approved by the Design Team folk.
  • fedora-logos-free.tar.gz tarball made and hosted somewhere.
  • Guidelines moved out of draft and announced everywhere and anywhere. Add pizazz about doing brand the open source way.