Hi, Am 11.11.2011 10:09, schrieb Koen Kooi: >> I don't recall any general requirement that one needs to seek permission >> from the TSC before acting on what seems like essentially a minor >> operational matter. When did this become the policy? > > Ever since the TSC has been formed. You never noticed it since the second > TSC was so shockingly passive.
the job of the TSC is sketched in the TSC Charter like this: "To govern access to all technical aspects of OpenEmbedded, this includes official git trees, openembedded-devel mailing list, bug trackers, QA systems, and others as the TSC sees fit." In this context my interpretation would be that the TSC grants permissions for write access to the Git tree but nothing more. And further control related to the responsible use of Git is not defined and IMHO never was. Phil has the required permissions to create a layer, so why he would have to ask? If there are really members out there who interpret this sentence as "you have to ask the TSC for everything related to use of the Git server" we need to discuss the charter again. If we do not make this more clear it won't take long and someone steps up claiming that the TSC would have to accept any single commit :-/ Greetings Florian -- The dream of yesterday Florian Boor is the hope of today Tel: +49 271-771091-15 and the reality of tomorrow. Fax: +49 271-771091-19 [Robert Hutchings Goddard, 1904] [email protected] http://www.kernelconcepts.de/en _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
