(HERE WE GO AGAIN) |
No edit summary |
||
| Line 1: | Line 1: | ||
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. | 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 [[:Category:Community Architecture|Community Architecture]] team as a general programmer and guy who does stuff out in the community. It's kinda generic. | |||
== Automating community statistics: <code>datanommer</code> == | == Automating community statistics: <code>datanommer</code> == | ||
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 <code>datanommer</code> 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 == | == Improving Fedora's brand == | ||
asdfljdflja | asdfljdflja | ||
Revision as of 06:21, 4 August 2010
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
asdfljdflja