Edit Info Other
Login

Diff for "SteeringCommittee"

Differences between revisions 3 and 4
Revision 3 as of 2007-04-16 20:10:32
Size: 2642
Editor: HansdeGoede
Comment:
Revision 4 as of 2007-04-16 22:15:08
Size: 2651
Comment: Axel doesn't veto anything, just nobody wants to be (legally) responsible.
Deletions are marked like this. Additions are marked like this.
Line 32: Line 32:
In case the decision is around something legal, each project contributer will Legal issues require unanimous decisions of the committee. Each project contributer will
Line 36: Line 36:
People providing the main public hosting capability have a veto power here, as
they are the one bearing the greatest legal risk.
For issues in the legal gray area where for example a resolution can only be found at court,
the legal liability can be passed to someone vouching for this resuming full legal responsibility.
Line 55: Line 55:
Opinions between the members of rpmfusion differ on the legality of libdvdcss, however since Axel bears the legal responsibility for the infra he is providing, he gets a veto in this. Thus since Axel is against this (and he is not alone in this) libdvdcss will not be included in the rpmfusion repository. Opinions between the members of rpmfusion differ on the legality of libdvdcss, however no one
is ready to vouch for it resuming the legal responsibilities. Therefore libdvdcss is being dropped.
See also the comments on legal issues above.

Steering Committee

Below is the text of the mail describing the Steering committee, this text was approved unanimously:

We create a committee with one representative per repo (I know not all repo's are equal in size, but lets ignore that). This committee will solve / decide on various issues if / when they are raised. I would like to suggest the following representatives:

Atrpms

Axel

Dribble

Hans *

Freshrpms

Matthias

Livna

Thorsten **

* Notice that I'm not the Dribble project lead, Ian is, but since Dribble is rather small I think its best to have a representative who is active outside Dribble and FE (livna) too, Ian is ok with this.

** Notice that Thorsten is not the Livna project lead, but he is one of the driving persons behind it in the past months and Anvil (the Livna initiator) agreed that Thorsten should represent Livna in this effort

Decision making is done as followes:

  • some issue is raised on the list
  • its discussed on the list
  • if there is consensus the committee can make an official decision by email votes send to the other 3 members
  • if there is no consensus the committee will first have some internal discussion (email or irc) and then vote
  • Once a decision has been made it will be put on the wiki and send to the list, this will not only include the decision, but also the motivation why this was decided.

Legal issues require unanimous decisions of the committee. Each project contributer will have to decide for himself what this means for him personal (iow anyone is free to walk away at any moment, although that is the last thing that we want).

For issues in the legal gray area where for example a resolution can only be found at court, the legal liability can be passed to someone vouching for this resuming full legal responsibility.

Other Repositories

When other repositories later want to join rpmfusion, they can elect a representative to represent them in the decision making committee too.

Decisions

Which infrastructure to use

  1. Axel's / atrpms infra will be used as master repository and also as primary building infra
  2. PIX / livna's infra will be used as a mirror
  3. Matthias has offered freshrpms infra as mirror and we will gladly use that

What todo about libdvdcss

Opinions between the members of rpmfusion differ on the legality of libdvdcss, however no one is ready to vouch for it resuming the legal responsibilities. Therefore libdvdcss is being dropped. See also the comments on legal issues above.

SteeringCommittee (last edited 2014-09-03 14:27:36 by XavierLamien)