From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (dan.rpsys.net [93.97.175.187]) by mail.openembedded.org (Postfix) with ESMTP id 0DA176077E; Tue, 18 Jun 2013 16:23:21 +0000 (UTC) Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r5IGTQOb003158; Tue, 18 Jun 2013 17:29:26 +0100 X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9t518rRPogft; Tue, 18 Jun 2013 17:29:26 +0100 (BST) Received: from [192.168.3.10] (rpvlan0 [192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id r5IGTNqh003152 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 18 Jun 2013 17:29:25 +0100 Message-ID: <1371572589.20823.143.camel@ted> From: Richard Purdie To: openembedded-members Date: Tue, 18 Jun 2013 17:23:09 +0100 X-Mailer: Evolution 3.6.4-0ubuntu1 Mime-Version: 1.0 Cc: tsc , openembedded-core Subject: OE, the TSC and the future X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jun 2013 16:23:22 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit I think its fair to say that OpenEmbedded has changed quite a bit over the last few years. Prior to the Yocto Project, OE struggled to figure out how to engage with the commercial side of the ecosystem and how to scale and I think there have been many positive changes in the way everything works, not least with the layers approach and the pull model for changes. Whilst the ecosystem has changed, the structures that make up OE such as the TSC have not changed that much. They were setup to address problems which in some cases no longer exist for example. We're coming up to the next round of TSC elections, the board is aware of this but have asked that we figure out the TSC's role going forward before those elections. There has been limited discussion about this on the members list previously, it was met with a lot of silence but I do think the time is right to think about things a bit. I should note that whilst I did take an action from the TSC to start a discussion and that the TSC does have some ideas in mind, I'm primarily expressing personal views here, not those of the TSC. Other TSC members are more than capable of expressing their own views! In brief summary the TSC has been doing two main things, acting as a task force and also being able to make a decision when needed. The latter has not happened much at all, the main work was as a task force on various issues, firstly engaging with the Yocto Project and figuring that out, more recently dealing with infrastructure issues and generally ensuring the health of OE. I don't think the task force should be limited to the TSC members although it can be lead by them (or delegated). As such I think the TSC would like to see that element get opened up to a public IRC meeting, maybe monthly at a set time when people get together and discuss those topics. The TSC members could be responsible for giving that process and meeting some kind of structure but it would be open to all. The decision making element of the TSC would remain with them, likely done by calling a special meeting as needed (we haven't needed many official decisions). At this point I'll open that to discussion. Any objections or other proposals? Speaking of TSC elections, I know I'm due for re-election first. I'm also due to be away for a few weeks shortly so I'd like to make it known that I would like to stand for re-election. I've hopefully done some good for OE over what amounts to nearly a decade (scary when put like that!) and I'm not quite done yet! :) Cheers, Richard