Then I just can’t wait to see it happen :]

That’s the plan

I don’t know if that’s what supposed to happen in the future, but it would be great it this became some kind of a portal, like netvibes or iGoogle.

There would be lots of widgets, one for any Fedora Application, and each one could choose the ones he wants to see, and where. I, as a package maintainer and ambassador, would like to see informations about builds and marketing issues. An artist would choose different widgets, etc…

I think this is some kinda security measure which u guys are missed out in u r site.

We chose TurboGears over Django for *many* reasons, but mainly because we wanted the flexibility and power to utilize the best pre-existing components out there, such as SQLAlchemy, Pylons, ToscaWidgets, Mako/Genshi, etc for various layers of the stack — without being locked into a gigantic monolithic ‘reinvent every wheel’ framework such as Django. By being fully WSGI compliant, we are also able to wield a vast plethora of WSGI middleware, such as WebError/repoze.{profile,squeeze,who}/etc. There is nothing stoping anyone from writing a Moksha application using Django components, but we don’t want to lock people into a specific [subpar] technology from the start.

With regard to the “slowness” of various apps such as bodhi, pkgdb, fas; that is mostly caused by database lag, and also due to the fact that each request to bodhi/pkg triggers a *few* JSON calls to FAS. In the case of Moksha, we have resolved that issue by utilizing extensive caching of things like credentials, so we don’t have to tax fas every request.