From Fedora Project Wiki
(Created page with '= EPEL SIG タスク = This page describes all open tasks that are on the todo-list of the EPEL special interest group (SIG) as well as the schedule for the next...')
 
Line 1: Line 1:
= EPEL SIG タスク =
+
= EPEL 運営委員会 =
  
This page describes all open tasks that are on the todo-list of the [[EPEL SIG|  EPEL special interest group (SIG)]]  as well as the schedule for the next [[EPEL/Meetings| EPEL SIG meeting on IRC]] .
 
  
Feel free to add easy task to the list of [[EPEL/Tasks/Misc|  miscellaneous easy tasks]] or just mail the epel-devel list. If the task if more complicated please instead create a separate tracking page by using one of the existing pages as a template; that separate tracking page should list some background and goals around the task as well as its current status. If you need help contact the epel-devel list.
 
  
All small and big tasks should have at least one owner assigned who is responsible for driving a task. He should make sure the tracking page is up2date and make sure things are moving and get realized in time -- without owners it often happens that tasks linger around without process.
+
== 全般 ==
  
If you want to help getting a task finished get in contact with the owners -- they are often glad if someone helps them as the owners often have lots of other tasks to work on in the Fedora Project as well.
+
An EPEL Steering Committee was formed by FESCo as a governing body for EPEL. The committee consist of seven members -- the initial one was filled with the first seven EPEL SIG members who were also those who invested most of the time and work for the EPEL idea in the beginning.
  
{{Anchor|Tasks}}
+
Currently these people are members of the EPEL Steering Committee:
== タスク/ほしい物リスト ==
 
  
# Prepare for EL-6 builds
+
* Mike Mc<code></code>Grath ([[MikeMcGrath| mmcgrath]] )
# solve incompatible upgrades problem
+
* Michael Stahnke ([[MichaelStahnke| stahnma]] )
# Regular running of broken deps list
+
* Kevin Fenzi ([[KevinFenzi| nirik]] )
 +
* Xavier Lamien ([[XavierLamien| SmootherFrOgZ]] )
 +
* Andy Gospodarek ([[AndyGospodarek| Gospo]] )
 +
* Jeff Sheltren ([[JeffSheltren| Jeff_S]] )
 +
* Karsten Wade ([[KarstenWade| quaid]] )
 +
* Stephen J Smoogen ([[StephenSmoogen| smooge]] ) (''Chair'')
  
== 次回ミーティング ==
+
The EPEL Steering Committee tries to work in the open and doesn't want to use it's influence as governing body. That means:
  
=== ミーティングを開始するためのテンプレート ===
+
* if you want to do something "new" in EPEL-land just tell the others about it on the mailing list about it. If nobody yells for a few days consider you plans accepted and go ahead
  
This template is used during the meeting start by the meeting chair to open the meeting; feel free to add your nick to the list of nicks in the "meeting ping"
+
* Topics in EPEL-land are discussed and decided in open-to-all IRC meetings and on the mailing lists; all EPEL contributers can send in their vote ot their options via mail if they cannot make the meeting.
<pre>
 
#startmeeting EPEL (YYYY-MM-DD)
 
#meetingname epel
 
#topic init process / agenda
 
gather agenda
 
</pre>
 
  
Here is the topic list -- it's used in the weekly EPEL SIG's meeting and thus contain some formating stuff for setting the Channel topics and related things.
+
* Important topics are discussed on the list (epel-devel-list) before they being voted upon.  The goal is to find a consensus that seems to works for the majority of people involved.
  
{{Anchor|TopicsForThisWeek}}
+
* Meeting summaries are sent to the list, wiki, and to FESCo. They may be rediscussed in FESCo meetings, if necessary.  FESCo retains authority over EPEL decisions and can exercise a veto on a voted-upon topic.  FESCo can exercise this veto in the FESCo meeting that follows the release of the public summary that included the decision under veto.  FESCo is guaranteed at least 24 hours for research, deliberation, and discussion, regardless of meeting schedules.  This procedure is similar to the interaction between FESCo and the Packaging Committee.
  
=== 今週のミーティングの議題 ===
+
* Each point that receives strong opposition on the list after it got decided will get revisited once in the next meeting if someone asks for it
  
<pre>
+
* if it comes to hard decisions where no agreement can be found only the votes from the steering committee members count; for an item under vote to gain approval, a minimum of four members must agree on it to form a consensus.  If that can't be reached (contentious votes where people are abstaining can create such situations) then all Steering Committee members have to vote and then the majority of votes wins. The goal is to have a consensus between Committee members; sometimes that isn't possible.
/topic EPEL SIG Meeting | Status Reports | Revive them?
 
/topic EPEL SIG Meeting | Package Reports: Orphans in EPEL?
 
/topic EPEL SIG Meeting | Standing Issues: | all
 
/topic EPEL SIG Meeting | Free discussion around EPEL
 
</pre>
 
  
=== ミーティング終了するためのテンプレート ===
+
The EPEL Steering Committee does not handle issues around theoretical Packaging, for example, everything around writing specfiles. This is the purview of the Packaging Committee to manage.  On the other hand, practical packaging, for example, maintenance and update policy for EPEL, is regulated by the EPEL Steering Committee.
  
<pre>
+
The goal is to let the EPEL Steering Committee work on it's own, that is, without FESCo involvement, for all things that are specific to EPEL. Sometimes it might be necessary to solve issues hand-in-hand with FESCo or other SIGs, for example, resolving conflicts between EPEL and the Packaging Committee.
/me will close the meeting in n
+
 
-- MARK -- Meeting end
+
General discussions occur on-list before voting.  However, large-scale and controversial topics require extra care. To make sure all steering committee, SIG, and community members have time to provide their voice on a topic, scheduled votes on such topics are announced 24-hours in advance of the vote.  Small items may be brought to vote in a meeting or on-list without a prior announcement; this keeps the project moving swiftly without needless bureacracy.  Decisions may always be revisted, if there is a need to.
#endmeeting
+
 
</pre>
+
== 運営委員会議長 ==
 +
 
 +
The EPEL Steering Committee is conducted by the Steering Committee Chairmen.  The chair's responsibilities are:
 +
 
 +
* Keep the pieces together
 +
 
 +
* Prepare and run the SIG meetings
 +
 
 +
* Issue and coordinate the votings in the meetings and in the wiki, to prevent chaos that might arise if anybody would issue votings
 +
 
 +
* Write the meeting and general "what happened" summaries, then send the to the list and FESCo for discussion
 +
 
 +
* Report to FESCo, try to be available for questions in FESCo meetings and on the lists
 +
 
 +
* Make sure all requests on the mailing lists regarding EPEL feel heard
 +
 
 +
* Make sure EPEL is running fine, which includes "make contributors and users happy"
 +
 
 +
Note that the chair doesn't have to do all of the above personally. The chair is responsible for making sure ''someone'' does these roles. ;-)
  
 
----
 
----
 
[[Category:EPEL]]
 
[[Category:EPEL]]

Revision as of 03:21, 15 May 2010

EPEL 運営委員会

全般

An EPEL Steering Committee was formed by FESCo as a governing body for EPEL. The committee consist of seven members -- the initial one was filled with the first seven EPEL SIG members who were also those who invested most of the time and work for the EPEL idea in the beginning.

Currently these people are members of the EPEL Steering Committee:

The EPEL Steering Committee tries to work in the open and doesn't want to use it's influence as governing body. That means:

  • if you want to do something "new" in EPEL-land just tell the others about it on the mailing list about it. If nobody yells for a few days consider you plans accepted and go ahead
  • Topics in EPEL-land are discussed and decided in open-to-all IRC meetings and on the mailing lists; all EPEL contributers can send in their vote ot their options via mail if they cannot make the meeting.
  • Important topics are discussed on the list (epel-devel-list) before they being voted upon. The goal is to find a consensus that seems to works for the majority of people involved.
  • Meeting summaries are sent to the list, wiki, and to FESCo. They may be rediscussed in FESCo meetings, if necessary. FESCo retains authority over EPEL decisions and can exercise a veto on a voted-upon topic. FESCo can exercise this veto in the FESCo meeting that follows the release of the public summary that included the decision under veto. FESCo is guaranteed at least 24 hours for research, deliberation, and discussion, regardless of meeting schedules. This procedure is similar to the interaction between FESCo and the Packaging Committee.
  • Each point that receives strong opposition on the list after it got decided will get revisited once in the next meeting if someone asks for it
  • if it comes to hard decisions where no agreement can be found only the votes from the steering committee members count; for an item under vote to gain approval, a minimum of four members must agree on it to form a consensus. If that can't be reached (contentious votes where people are abstaining can create such situations) then all Steering Committee members have to vote and then the majority of votes wins. The goal is to have a consensus between Committee members; sometimes that isn't possible.

The EPEL Steering Committee does not handle issues around theoretical Packaging, for example, everything around writing specfiles. This is the purview of the Packaging Committee to manage. On the other hand, practical packaging, for example, maintenance and update policy for EPEL, is regulated by the EPEL Steering Committee.

The goal is to let the EPEL Steering Committee work on it's own, that is, without FESCo involvement, for all things that are specific to EPEL. Sometimes it might be necessary to solve issues hand-in-hand with FESCo or other SIGs, for example, resolving conflicts between EPEL and the Packaging Committee.

General discussions occur on-list before voting. However, large-scale and controversial topics require extra care. To make sure all steering committee, SIG, and community members have time to provide their voice on a topic, scheduled votes on such topics are announced 24-hours in advance of the vote. Small items may be brought to vote in a meeting or on-list without a prior announcement; this keeps the project moving swiftly without needless bureacracy. Decisions may always be revisted, if there is a need to.

運営委員会議長

The EPEL Steering Committee is conducted by the Steering Committee Chairmen. The chair's responsibilities are:

  • Keep the pieces together
  • Prepare and run the SIG meetings
  • Issue and coordinate the votings in the meetings and in the wiki, to prevent chaos that might arise if anybody would issue votings
  • Write the meeting and general "what happened" summaries, then send the to the list and FESCo for discussion
  • Report to FESCo, try to be available for questions in FESCo meetings and on the lists
  • Make sure all requests on the mailing lists regarding EPEL feel heard
  • Make sure EPEL is running fine, which includes "make contributors and users happy"

Note that the chair doesn't have to do all of the above personally. The chair is responsible for making sure someone does these roles. ;-)