On Mon, 2006-04-24 at 12:23 -0400, Michael Tiemann wrote: > On Mon, 2006-04-24 at 12:08 -0400, Warren Togami wrote: > > > 3) Make package announcements backed by a database > > -------------------------------------------------- > > We should have all of this information stored in a database. Generated > > from this database are a number of both push & pull representations like: > > - Package update and security advisory list announcements > > - RSS feeds > > - Canonical package update website (links from RSS feed point here) > > - Metadata for pirut and pup > > > > http://people.redhat.com/wtogami/temp/fedora-updates.png > > Luke Macken's previous work on the Fedora Update tracking system that we > > currently use only internally give us a head start in these goals. It > > would be fairly easy to build upon this existing foundation, but only > > after we achieve a few other objectives. (Putting the Fedora Updates > > system in the public requires some design considerations for proper > > handling of Embargo and possibly other aspects related to the Fedora > > distribution merge.) > > > > Thoughts? > > I will volunteer to help with the database design and testing, and > feature enhancement requests. I prefer to write SQL to C++ these days-- > go figure! I cannot volunteer to actually run the production system, > but do think it would be fun to make this system a window into Fedora > development. > Yes. The ability of people outside of Red Hat to check the status and even resolve issues is important. Rahul
