Output from the python EKG
People have asked, so here's what it looks like so far.http://ynemoy.fedorapeople.org/ekg/graph.test.003.html
I can't believe it
I came in on schedule. In rewriting EKG, i made a few estimates and handed them off to Max as a set of deliverables. Unfortunately, reality got in the way and the man hour schedule got pushed off course a bit because of real world hours, namely taking care of school work and other things. I also had to stick in a bunch of haskell work in, as we've finally gotten some amazing momentum going there.On the way, i decided to get fancy too. I realized that we would need to have a framework in EKG that could give us room to grow in looking at the things we analyze. I took some of the lessons i learnt doing the framework for Devshell and applied them roughly to EKG. Because of this, i ran into some technical issues handling multiple inheritance in Python. Let's just say that multiple inheritance, while it has it's uses, can end up really bad. Several reworkings later, i was a full week of real time off schedule.
This design decisions has paid off immensely. As a result, it took me 4 man-hours tonight to put together the basics of the reporting element. It's not quite as sophisticated as the version 2 grapher, nor does it do kevin bacon graphs yet, but it at least has the number one asked for feature, deltas. People, and by people, i mean the persons that pay me, want to see a numerical difference per month, per quarter, and per year, and all this is per domain.
I also took it one step further. You can even get the deltas of a particular month or quarter over multiple years. It's actually just a general purpose algorithm that can do any delta query on any collection of counts.
When I made the original estimates, i estimated around 4-8 hours for recreating the grapher tool. According to my timer, i've spent 4 man-hours on it tonight. It's closer to 6 or 8 because of constant fidgeting and moving around; i've been very ADD tonight for some reason.
Next up for EKG
Currently i'm spitting out HTML with string fudging. There are some nice libraries for generating HTML, i need to package one i like for Fedora and include it. I could also use templates, but i'm sick of doing things the MVC way, and i want to experiment more with Object-Proxy development.
Michael DeHaan's found a pretty cool javascript library that has some pretty widgets for tracking changes, and doing pretty pie graphs. Problem is, is that it will need some nice TLC to make it useable, and then pacakged as well. Things should get interesting.
I should also do a couple of blog posts about some of the cool tricks i put into EKG to make it work. Maybe we should think of a Fedora related Python code snippet database too.
An Anecdote about why doing the wrong thing is bad.
Actually, this should be obvious to some, but, apparently, people love to do the wrong thing.Taken from: ext4, application expectations and power management by Matthew Garrett
<quote>
[1] xfs behaves like ext4 in this respect, so the obvious argument is that all our applications have been broken for years and so why are you complaining now. To which the obvious response is "Approximately anyone who ever used xfs expected their data to vanish if their machine crashed so nobody used it by default and seriously who gives a shit". xfs is a wonderful filesystem for all sorts of things, but it's lousy for desktop use for precisely this reason.
</quote>
Once i was using XFS as my desktop file system. Anyone who knows me knows i like to do things differently just because i can. That's just how i do things.
One day, my system decides that it wants to crash, probably something to do with JBoss, but i don't remember exactly. (Not to offend JBoss developers, i was using a version that wasn't meant to work.) When i bring my computer back up, Firefox complains that there's something wrong and i can't start it again. I essentially lost my entire Firefox profile.
Let's be honest here, XFS is probably a bad idea to be used for a desktop. Let's just pretend someone's running an LTSP server on top of XFS. Or rather, someone's running that on ext4. Let's just forget about the LTSP part then, an average user. I'm sure alot of Firefox profiles have gone down screaming in flames. I'm sure some one has used this as an excuse to blame Firefox for being shitty, and then gone off blaming Open Source for being so bad.
The real problem isn't exactly what one programmer made as a mistake. A huge percentage of code is copy and paste from other projects. It's really easy for mistakes to persist over a large number of projects. I really can't blame Firefox for being any more at fault than XFS, Fedora, Open Source, or Buddha. This was just a moment where i went "Aha! This explains everything". Well mostly everything.
GSoC 2009 as a Feature
Following my previous blog post, i've jotted down a few more notes about how to do GSoC projects as Fedora features. It's really just a rough draft and could probably do with a few examples and links and other things. You can find it here:User:Ynemoy/GSOC_2009
This is really relevant to both potential Students and Mentors. I'm hoping that for at least some of the projects, people will be willing to experiment using this workflow to make things happen.
Google Summer of Code is on.
It's official, there will be a GSoC this year. Once again i am looking to mentor someone this summer. Last summer, it was a complete failure. I feel as if there was not enough passion about the project to motivate my student.This summer i would like to do something very different. Currently, Google is taking applications from mentoring organizations, which means that it is not even time for students to get started putting together their applications. I think it is fairly likely though that Fedora will have a few spots available at least. Therefore if you're looking to get a head start, this is just the blog post you want to be reading.
Given the success of the Feature List in Fedora, i want to model a project around that. I want to find someone who is passionate about an idea, and is willing to communicate it to the world. What i would like to see from an interested student in the next few weeks is a very open ended project proposal. It can cover any aspect of Open Source, but it has to be written as a Feature proposal. The goal is to produce a Fedora feature. You can do it as part of other concurrent development in Fedora or as a completely new concept. What's important is that it has to be innovative enough to be worth putting in the Release Notes.
I'll probably write more about this idea in the next few days. But if you have that itch you're looking to scratch in the Fedora and Linux world, you can get started right away.
Last but not least, if you put together a Feature proposal and submit it as a GSoC project, but do not make the cut, remember, you can still work on the project. As a student, contributing an entire "Feature" is an amazing resume item.
I'm a packager
Bug 426751 - (ghc-X11) Review Request: ghc-X11 - A Haskell binding to the X11 graphics library.Reported: 2007-12-25 15:15 EDT by Yaakov Nemoy
Modified: 2009-03-03 06:26 EDT
I'm in your Fedora messing with your CVS.
It's been a fun adventure :D
Abonneren op:
Posts (Atom)