Difference between revisions of "TSC"

From Openembedded.org
Jump to: navigation, search
(2012 Minutes)
(Update for changes over the last year)
(14 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
=OE Technical Steering Committee=
 
=OE Technical Steering Committee=
  
The TSC consists of 5 people and will be elected by, and ultimately be answerable to, the members of the OE e.V.
+
The TSC consists of 5 people who are elected by, and ultimately be answerable to, the members of the OpenEmbedded organisation.
  
 
Here is the [[TSCCharter | working copy]] of the new TSC charter.
 
Here is the [[TSCCharter | working copy]] of the new TSC charter.
 +
 +
The TSC meets on an irregular basis, but is happy to hold meetings on request if there are issues to discuss.
 +
 +
The TSC discusses technical issues for the direction of OpenEmbedded. Note that the TSC is NOT chartered with actually doing all of the work discussed, but they do make every effort to locate resources to do that work.
  
 
= Members =
 
= Members =
Line 9: Line 13:
 
In order by election:
 
In order by election:
  
* Richard Purdie (RP) - elected Jul 2011
+
* Martin Jansa (JaMa) - elected Jun 2015
* Khem Raj (khem) - elected Oct 2011
+
* Richard Purdie (RP) - elected Oct 2015
* Paul Eggleton (bluelightning) - elected Dec 2011
+
* Khem Raj (khem) - elected Oct 2015
* Mark Hatle (fray) - elected Mar 2012
+
* Paul Eggleton (bluelightning) - elected Oct 2015
* Koen Kooi (koen) - elected Apr 2012
+
* Mark Hatle (fray) - elected Oct 2015
  
Each member serves a two-year term. During election time, one member may stand for election every two months. The next election will be for Richard Purdie's seat in July, 2013.
+
Each member serves a two-year term. During election time, one member may stand for election every two months.
  
 
= Responsibilities =
 
= Responsibilities =
  
On a day-to-day basis the TSC will be responsible for making
+
On a day-to-day basis the TSC is responsible for making
 
tactical policy decisions, resolving disputes between contributors,
 
tactical policy decisions, resolving disputes between contributors,
 
administering access control to the git tree, and generally promoting
 
administering access control to the git tree, and generally promoting
Line 29: Line 33:
 
the technical steering committee, the decision should be respected as a democratic decision.
 
the technical steering committee, the decision should be respected as a democratic decision.
  
= Outstanding items (sorted by occurence) =
+
= TSC issue escalation procedure =
* Convert remaining recipes to new style staging
+
 
* Make the insane.bbclass mandatory, make it default to only complain
+
The best way to agendize an issue for the TSC is to send email to one of the TSC members or to [mailto:jefro@jefro.net Jefro], the curator. The issue will be added to the agenda for the next meeting. If the issue is particularly urgent, a specific TSC meeting may be called.
* Ongoing campaign to deprecate/remove old recipes (use common sense, allow review)
+
 
* Rename org.openembedded.dev to master
+
= TSC mailing list archive =
* Document revert policy on Wiki
+
 
* Document TSC issue escalation procedure
+
http://lists.openembedded.org/pipermail/tsc/
 +
 
 +
= Meeting Minutes =
  
= TSC list archive =
+
== 2013 Minutes ==
http://lists.linuxtogo.org/pipermail/tsc/
 
  
= 2012 Minutes =
+
* [http://lists.openembedded.org/pipermail/tsc/2013-February/000362.html 29 January 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-February/000363.html 12 February 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000365.html 26 February 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-March/000366.html 19 March 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-April/000367.html 8 April 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-May/000368.html 23 April 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-May/00037.html 7 May 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000372.html 21 May 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000373.html 4 June 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-June/000381.html 18 June 2013]
 +
* [http://lists.openembedded.org/pipermail/tsc/2013-August/000393.html 2 July 2013]
 +
* 16 July 2013
 +
* 30 July 2013 (public meeting)
 +
* 13 August 2013 (cancelled)
 +
* 27 August 2013
  
The TSC meets approximately every two weeks.
+
== 2012 Minutes ==
  
 
* [http://lists.linuxtogo.org/pipermail/tsc/2012-January/000330.html 3-Jan-2012]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2012-January/000330.html 3-Jan-2012]
Line 65: Line 84:
 
* [http://lists.linuxtogo.org/pipermail/tsc/2012-October/000356.html 25-Sep-2012]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2012-October/000356.html 25-Sep-2012]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2012-October/000357.html 9-Oct-2012]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2012-October/000357.html 9-Oct-2012]
 +
* [http://lists.linuxtogo.org/pipermail/tsc/2012-November/000358.html 23-Oct-2012]
 +
* [http://lists.linuxtogo.org/pipermail/tsc/2012-December/000359.html 6-Nov-2012]
 +
* [http://lists.linuxtogo.org/pipermail/tsc/2013-January/000360.html 20-Nov-2012]
 +
* [http://lists.linuxtogo.org/pipermail/tsc/2013-January/000361.html 4-Dec-2012]
  
= 2011 Minutes =
+
== 2011 Minutes ==
  
 
* [http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-February/029974.html 14-Feb-2011]
 
* [http://lists.linuxtogo.org/pipermail/openembedded-devel/2011-February/029974.html 14-Feb-2011]
Line 75: Line 98:
 
* [http://lists.linuxtogo.org/pipermail/tsc/2011-March/000208.html 25-Mar-2011]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2011-March/000208.html 25-Mar-2011]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2011-April/000224.html 31-Mar-2011]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2011-April/000224.html 31-Mar-2011]
* [http://lists.linuxtogo.org/pipermail/tsc/2011-April/000232.html 10-Apr-2011] (face to face at ELC 2011)
+
* [http://lists.linuxtogo.org/pipermail/tsc/2011-April/000232.html 10-Apr-2011]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2011-May/000241.html 28-Apr-2011]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2011-May/000241.html 28-Apr-2011]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2011-May/000240.html 05-May-2011]
 
* [http://lists.linuxtogo.org/pipermail/tsc/2011-May/000240.html 05-May-2011]
Line 100: Line 123:
 
* [http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014563.html 13-Dec-2011]
 
* [http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014563.html 13-Dec-2011]
  
= 2010 Minutes =
+
== 2010 Minutes ==
  
 
* [http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-June/020655.html June 2010]
 
* [http://lists.linuxtogo.org/pipermail/openembedded-devel/2010-June/020655.html June 2010]

Revision as of 23:00, 13 March 2016

OE Technical Steering Committee

The TSC consists of 5 people who are elected by, and ultimately be answerable to, the members of the OpenEmbedded organisation.

Here is the working copy of the new TSC charter.

The TSC meets on an irregular basis, but is happy to hold meetings on request if there are issues to discuss.

The TSC discusses technical issues for the direction of OpenEmbedded. Note that the TSC is NOT chartered with actually doing all of the work discussed, but they do make every effort to locate resources to do that work.

Members

In order by election:

  • Martin Jansa (JaMa) - elected Jun 2015
  • Richard Purdie (RP) - elected Oct 2015
  • Khem Raj (khem) - elected Oct 2015
  • Paul Eggleton (bluelightning) - elected Oct 2015
  • Mark Hatle (fray) - elected Oct 2015

Each member serves a two-year term. During election time, one member may stand for election every two months.

Responsibilities

On a day-to-day basis the TSC is responsible for making tactical policy decisions, resolving disputes between contributors, administering access control to the git tree, and generally promoting good development practice.

Decision Making

Decisions are made where necessary by majority vote. Once a decision is made by the technical steering committee, the decision should be respected as a democratic decision.

TSC issue escalation procedure

The best way to agendize an issue for the TSC is to send email to one of the TSC members or to Jefro, the curator. The issue will be added to the agenda for the next meeting. If the issue is particularly urgent, a specific TSC meeting may be called.

TSC mailing list archive

http://lists.openembedded.org/pipermail/tsc/

Meeting Minutes

2013 Minutes

2012 Minutes

2011 Minutes

2010 Minutes