-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30-06-10 15:19, Holger Freyther wrote:
> In regard to the TSC, what mode of operation do you propose? We freeze > the tree until all items are implemented in the order they are proposed? > We find people driving a topic? In this specific case you (or the TSC) choose to work on a extremely intrusive and controversial *cosmetic* change first instead of tackling the some of the (IMO more important) items agreed on earlier: * making QA checks be enabled by default * promoting new style staging and converting existing recipes * promoting bbclassextend and converting existing recipes * fixing nativesdk By skipping over those, without saying why and going for the cosmetic change the TSC is sending out a signal that they do NOT care about quality, only appearance. In the past I was proud about how OE handled things by the things you yourself created, like insane.bbclass, the first edition of tinderbox, etc. But recently only 2 groups of OE developers seem to care about quality, the SHR and angstrom folk. Those are the only 2 distros that have the QA checks enabled. Due to the nature of OE other benefit from the awesome work Martin and Khem have been doing, but it feels a bit one sided to me. Since nearly all OE developers can't work fulltime on OE, I would propose that the TSC sends out a few "call to action" mails, describing the tasks that need doing and some guidance on how they want to see it done. I will *gladly* help out, but I need to know what needs doing and avoid duplicate work. It would help to have a "completed action items", "in progress action items" and "action items that noone is working on" list in the TSC minutes (or wiki) to keep track of stuff. And of course a big thank you to all the people working on QA that I didn't mention. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFMLFgrMkyGM64RGpERAtCVAJ4xp7Lxx91AwSUN7DgEwxasSjr4gACgi2/n qbbTDqsfC2RlFjxhRglNtZ4= =zIjM -----END PGP SIGNATURE----- _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
