Difference between revisions of "TSC"

From Openembedded.org
Jump to: navigation, search
(2013 Minutes)
(Outstanding items (sorted by occurence))
Line 33: 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
+
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, at jefro@jefro.net. 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.
* Make the insane.bbclass mandatory, make it default to only complain
+
* Ongoing campaign to deprecate/remove old recipes (use common sense, allow review)
+
* Rename org.openembedded.dev to master
+
* Document revert policy on Wiki
+
* Document TSC issue escalation procedure
+
  
 
= TSC mailing list archive =
 
= TSC mailing list archive =

Revision as of 21:56, 22 May 2013

Contents

OE Technical Steering Committee

The TSC consists of 5 people who are elected by, and ultimately be answerable to, the members of the OE e.V.

Here is the working copy of the new TSC charter.

The TSC meets approximately every two weeks.

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:

  • Richard Purdie (RP) - elected Jul 2011
  • Khem Raj (khem) - elected Oct 2011
  • Paul Eggleton (bluelightning) - elected Dec 2011
  • Mark Hatle (fray) - elected Mar 2012
  • Koen Kooi (koen) - elected Apr 2012

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.

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, at jefro@jefro.net. 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.linuxtogo.org/pipermail/tsc/

Meeting Minutes

2013 Minutes

2012 Minutes

2011 Minutes

2010 Minutes

Personal tools
Namespaces

Variants
Actions
Navigation
Categories
OE services
Toolbox