> > - Project status reports once a month for every project > > Totally agree on this one!
OK. I'll give you Release Engineering's "status reports" for September, October, and November: September: taking a well-deserved break October: taking a well-deserved break November: taking a well-deserved break How about other projects that rely on things like upstream's release cycle? What about projects that just maintain ebuilds? Here's the games team's "status reports" for every month: "Fixed more bugs, added more packages, cleaned up some ebuilds." Now, perhaps what everyone would like, instead, would be status reports *where necessary* from certain projects? In fact, the council has been discussing asking a few projects about the status on some of their tasks. The main reason for this is for communications purposes. Basically, we'd just get a "Hey, where are you at on $x?" response from the teams. I don't *want* to drown projects in bureaucracy and paperwork. I want them to *accomplish* things, instead. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
