foobar rawhide weather report

[Máirín Duffy]

Hey,

I was going over the requirements for $foobar and I was thinking about
the Rawhide weather report idea we had (check the upper right corner of
the mockup https://fedoraproject.org/w/uploads/c/ce/FooBar.png )

The idea was basically we'd keep track of how broken rawhide was on a
given day and report that as a parody of a weather report. I don't know
if something like that would be useful, but if so, I think it should
factor into the requirements.

Similarly, there's an idea in the mockup to show live dents (please
let's not use twitter). That might also need to factor in the
requirements if we decide this design idea is worth pursuing.

~m

[Jef Spaleta]

2009/7/14 Máirín Duffy :
> The idea was basically we'd keep track of how broken rawhide was on a
> given day and report that as a parody of a weather report. I don't know
> if something like that would be useful, but if so, I think it should
> factor into the requirements.

Useful? that I can't say. But humorous and personable...yes.

Just to play devil's advocate you could also play around with a forest
fire danger level theme.
http://www.fs.fed.us/r5/shastatrinity/images/nra/photos/vic-photos/smokey-cl...

"Only you can prevent Rawhide Breakage"

But the rawhide postcasting (thats the opposite of forecasting right?)
report probably probably has a better website feel to it.

-jef"I look forward to being able to build predictive models based on
historical rawhide weather data and actually predict tomorrow's
rawhide weather."spaleta

[Mel Chua]

> 2009/7/14 Máirín Duffy :
> > The idea was basically we'd keep track of how broken rawhide was on a
> > given day and report that as a parody of a weather report. I don't know
> > if something like that would be useful, but if so, I think it should
> > factor into the requirements.

Totally. Love. This. Idea. Whenever I see the mockup I look at the 
forecast and start laughing. Added to 
https://fedoraproject.org/wiki/FooBar#Design_requirements.

This actually makes a nice use case / litmus test for how easy it is to 
get little custom tweaks into our platform choice, 'cause it's pretty 
tough to distinguish them otherwise (going off our current requirements 
list and comparing it to the platforms listed on the wiki page, without 
looking at other important things like "how responsive is upstream"?) 
Any zikula experts in the audience who can chime in and say "yeah, 
zikula can do that, and it's this hard/easy"?

My $0.02: for sanity, nifty features like this should be automated as 
much as possible - autogenerate the forecast based on buildbot, say.

--Mel