-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Gianelloni wrote: >>> - 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. > Hear, hear! ++ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFI8ZJrsJQqN81j74RAt5GAJ9UletQJrSllbOuk4WG1Ro+XEvlLQCfY9VE bLWnmc2rJ6Z6Mx9dmvnEQ7I= =JbqS -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
