Apr 14 2013

Association. Comments on some definitions

Hello everybody

On April 10th, a common TC (Technical committee, for now = all active developers) + Council meeting took place. Logs will be posted. Here is the agenda and summary.

Best,
OMA secretary

Agenda point:
Technical committee, council and all-active-developers (“cooker”) definitions and their relations. Suggestions to discuss.

This occasion is used to once more invite all active developers to enter Association and speak out (even they are not members) about any concerns they have. Association is to serve these concerns and solve issues, this is exactly why it was founded.

Result summary:
Here are some main definitions, which were agreed.

Definition for clarity:
Cooker community = OpenMandriva Association. (This means, there exists just one community, involving everybody. There is no separate “cooker” community).

This includes developers, translators, artwork people, marketing people, etc. Everyone that likes or contribute, including users, testers, those who do support – is part of this broader community (community is a term to refer to the active devs, inactive developers and users and sporadic contributors)

Any contributor/member/developer/manager could be free will contributor or paid by sponsors through the Association.

Everyone has the same chances and no one is going to be protected or treated in any special way.
 

1. Some notes on wording and extras:
Cooker is OMA’s, but contribution is open

Cooker is also the active/rolling development of the OMA project.

It is also meant to be a base for other projects outside of OMA’s scope (it’s more inclusive of people who want to use the code base to build something else).

The project predates the association, and MDV saying they were giving the project to the community predates the association. The association was set up to help support the project. It could potentially support other projects too if it wanted.

It’s possible to contribute in the community and have no involvement with the association.

TC (Technical committee).
The TC is a form of representation inside the cooker community.

Currently TC involves all active developers.

The next TC (whenever it comes, tomorrow or much later) is to be the most valuable and experienced members, or natural born leaders that take the front.

Who can be in TC?
The members of the “cooker community” who are also OMA member, (s)elected by “cooker community” (with some possible argumented recommendations from council). TC acts as the projects engine and communicator with all other involved parties, including council, and takes the technical responsibilities. Veto power (if needed in some extreme case not easily solvable) on decisions and selection of members is a shared responsibility of the council (representing the majority of the community that shares the same ideas) and the TC itself, that regulates the technical responsibilities.

(TC members need to be OMA’s members. There are exceptions possible, given full mutual agreement (cooker including council).

(to be defined ASAP with cooker: exact roles, who should be in the TC (from the point of view of functions, next step asap: ideas for candidacies).

Project leader (s).
Members of the TC, responsible for overall route and development. Take decisions based on extensive consultations with cooker members. Take the RESPONSIBILITY for decisions in case of conflicts or attempts of hijack. If it can solve it by itself, or the decision taken is in conflict with other TC members, a joint decision need to be taken, reverting the power to the unity of the community.

Council:
The directive body of the Association, responsible for coordinating overall work and resources. Important to remember: council consists of members of the association, and is designed to represent everybody in the Association, and is elected by the members.

Council does not have own opinion as such, these people are elected to represent members (this means, that when council speaks, it is not just a blunt group of people out of nowhere: they were elected to represent community. They do not produce their own opinions, they represent).
 

2. Association as an entity: why founded, for whom and it’s functions
Membership in OMA is free and open to anybody, no obligations or restrictions. OMA’s goal is to make the project’s distro successful (by providing resources, infrastructure, marketing, attracting sponsors, etc.).

Normally OMA members should include both all cooker community + other non technical contributors.

We use this chance to say once again: contributors are most welcome to join OMA, the association was founded to serve your needs. Become a member and influence decisions, elect your representatives, participate and form the common work with your input and opinion.

If anybody was bypassed with invitation so far, we apologize, this was not the intention. Association is young, it all just starts. Doors are wide open.

The association is representing a lot of people that share the same vision for the future of the, soon to be, best linux distro of the world

Normally all cooker community should be OMA members if they share the goal to make the distro successful.
 

3. Distro name issue.
The temporary solution is go with a distro with no name for

Now. We still don’t have the appropriate technical resources (support on ABF) in place to a multi-name/multi-spin distro right now, and we never discussed this topic thoroughly so can we agree on having no-name now, not to go into that? The issue caused enough trouble already.

Reason is simple: if we were to decide now, how would we do that? Vote? By who?

Just decision of several people? Who?

We can make support on ABF for shared packages with different spins to support generating multiple distro, changing even the name, and we probably want to include some discussion on how our merit ( based on xxxx TM) should be approached.

So whatever spin we want, we need support on ABF first and then we can even let the RPM patched to be “nothing” , and the spins can tag the names appropriately depending on the platform used to compile

So, no name for now, until we can find a proper way to do it.

We could call the distro cooker, or some other fancy codename.

And each spin can name the ISO and artwork the way they want.

There is a suggestion to have Innominata (Latin for noname) as temporary name. Most people in a meeting said they are in favor of it, however, a separate discussion will be started by Gmoro in cooker ML for that.

Update: Joao Patricio drafts a suggestion on rules, how we choose the name. Draft to be discussed all together (details of procedure to come soon). The target is to have the rules and fully common community decision on the name before the release is out. For the moment “Innominata” takes the place as a placeholder.

Attention! If the topic is important for you, please follow it in general ML and the blog, in order to supply your opinion on time.
 

4. Recent conflict, summary from Association and suggestion for discussion/closing the topic.
Postponed to next week. Gmoro will post an agenda and confirm the time.Hallo allerseits

Am 10. April, einem gemeinsamen TC (Technical Committee, jetzt = alle aktiven Entwickler) + Tagung stattfand.
Die Zusammenfassung enthält einige Definitionen geklärt und erläutert.

OMA secretary

Tagesordnungspunkt:
Technischer Ausschuss, Rat und all-active-Entwickler (“Cooker” Definitionen und ihre Beziehungen. Vorschläge zu diskutieren.

Dieser Anlass wird verwendet, um noch einmal laden alle aktiven Beitragszahler Verband geben und sprechen (auch sie sind nicht Mitglieder) über alle Bedenken, die sie haben. Vereins ist es, diese Bedenken zu dienen und lösen Probleme, das ist genau, warum es gegründet wurde.

Ergebnis Zusammenfassung:
Hier sind einige der wichtigsten Definitionen, die vereinbart wurden.

Definition für Klarheit:
Cooker Community = OpenMandriva Association. (Das bedeutet, es gibt nur eine Gemeinschaft, an denen jedermann. Es gibt keine separate “Cooker” community).

Dazu gehören Entwickler, Übersetzer, artwork Menschen, Marketing-Leute, usw. Jeder, oder mag beitragen, einschließlich der Nutzer, Tester, diejenigen, die Unterstützung brauchen – ist Teil dieser größeren Gemeinschaft (Community ist ein Begriff, um zu den aktiven Entwicklern beziehen, inaktive Entwickler und Nutzer und sporadische Mitwirkenden)

Jeder Einsender / member / Entwickler / Manager konnte den freien Willen Einsender sein oder bezahlt von Sponsoren durch die Association.

Jeder hat die gleichen Chancen und niemand wird geschützt oder in einer besonderen Art und Weise behandelt werden.
 

1. Einige Anmerkungen zum Wortlaut und Extras:
Cooker ist OMA, aber Beitrag ist offen

Cooker ist auch die aktive / fortlaufenden Entwicklung des OMA-Projekt.

Es soll auch eine Basis für andere Projekte außerhalb des Anwendungsbereichs OMA (es ist mehr inklusive der Menschen, die die Code-Basis zu verwenden, um etwas anderes bauen wollen) sein.

Das Projekt älter als die Vereinigung und MDV sagen, sie gaben das Projekt in der Gemeinde schon vor der Vereinigung. Der Verein wurde zur Unterstützung des Projekts gesetzt. Es könnten andere Projekte unterstützen auch, wenn es wollte.

Es ist möglich, in die Gemeinschaft zu leisten und haben keine Auseinandersetzung mit dem Verein.

TC (Technical Committee).
Der TC ist eine Form der Darstellung in der Cooker-Community.

Derzeit TC beinhaltet alle aktiven Entwickler.

Der nächste TC (wann immer es geht, morgen oder erst viel später) ist die wertvollste und erfahrenen Mitgliedern, oder natürliche geboren Führer, die vor zu nehmen.

Wer kann in TC sein?
Die Mitglieder des “Cooker Gemeinschaft”, die auch OMA-Mitglied(er), von “Cooker Gemeinschaft” (mit einigen möglichen argumented Empfehlungen council) gewählt. TC fungiert als Motor und Kommunikator Projekte mit allen anderen Beteiligten, einschließlich des Rates, und nimmt die technische Verantwortung. Vetorecht (wenn in einigen extremen Fall nicht leicht lösbar erforderlich) auf Entscheidungen und Auswahl der Mitglieder ist eine gemeinsame Aufgabe des Rates (die die Mehrheit der Gemeinschaft, die die gleichen Ideen teilt) und der TC selbst, die die technische Verantwortung regelt.

(TC Mitglieder müssen OMA-Mitglieder sein. Es gibt Ausnahmen möglich, bei voller gegenseitigem Einvernehmen (Cooker inklusive council).

(ASAP mit Cooker definiert werden: genaue Rolle, die in der TC sein sollte (aus der Sicht der Funktionen nächsten Schritt so schnell wie möglich: Ideen für Kandidaturen).

Project Leader (s).
Mitglieder des TC, zuständig für die allgemeine Route und Entwicklung. Entscheidungen über umfangreiche Konsultationen mit Cooker Mitglieder. Nehmen Sie die Verantwortung für Entscheidungen im Fall von Konflikten oder Versuche der Entführung. Wenn sie von selbst lösen können, oder die Entscheidung ist in Konflikt mit anderen TC Mitglieder müssen eine gemeinsame Entscheidung getroffen werden, die Macht zurückkehrt, um die Einheit der Gemeinschaft.

Rat:
Die Richtlinie Organ des Vereins, verantwortlich für die Koordination gesamte Arbeit und Ressourcen. Wichtig zu beachten: Rat setzt sich aus Mitgliedern des Vereins, und wurde entwickelt, um alle in der Vereinigung vertreten und wird von den Mitgliedern gewählt.

Rat nicht über eigene Meinung als solche, diese Leute gewählt werden, um Mitglieder (dies bedeutet, dass, wenn der Rat spricht, es ist nicht nur ein stumpfes Gruppe von Menschen aus dem Nichts darstellen:. Wurden sie gewählt, um Gemeinschaft zu repräsentieren sie nicht produzieren ihre eigene Meinung vertreten sie).
 

2. Verband als eine Einheit: warum gegründet, für wen und seine Funktionen
Mitgliedschaft in OMA ist kostenlos und für jedermann offen, keine Verpflichtungen oder Einschränkungen. OMA ist das Ziel, um das Projekt erfolgreich Distribution (durch die Bereitstellung von Ressourcen, Infrastruktur, Marketing, zieht Sponsoren, etc.).

Normalerweise OMA Mitglieder sollten sowohl alle Cooker Community + anderen nicht technischen Mitwirkenden.

Wir nutzen diese Chance, um noch einmal sagen: Mitwirkende sind herzlich eingeladen, OMA beizutreten, wurde der Verein gegründet, um Ihre Bedürfnisse zu dienen. Werden Sie Mitglied und Entscheidungen beeinflussen, wählen Sie Ihre Vertreter, teilnehmen und bilden die gemeinsame Arbeit mit Ihrer Eingabe und Meinung.

Wenn jemand umgangen wurde mit Einladung so weit, wir entschuldigen uns, das war nicht die Absicht. Verband ist jung, es ist alles nur beginnt. Die Türen sind weit geöffnet.

Der Verband vertritt eine Menge Leute, die die gleiche Vision teilen für die Zukunft der, bald sein, am besten Linux-Distribution der Welt

Normalerweise werden alle Cooker Gemeinschaft sollte OMA Mitglieder sein, wenn sie das Ziel, um die Distribution erfolgreich zu teilen.
 

3. Distro Namen Thema.
Die vorübergehende Lösung ist, gehen Sie mit einer Distribution ohne Namen für

Jetzt. Wir wissen immer noch nicht über die entsprechenden technischen Ressourcen (Unterstützung auf ABF) anstelle einer multi-name/multi-spin Distribution gerade jetzt, und wir haben nie diskutiert dieses Thema gründlich, so können wir uns auf das No-Name jetzt zustimmen, nicht gehen in das? Das Problem verursacht schon genug Ärger.

Grund dafür ist einfach: Wenn wir jetzt entscheiden, waren, wie würden wir das tun? Abstimmen? Von wem?

Nur Entscheidung von mehreren Personen? Wer?

Wir können auf die Unterstützung ABF machen für gemeinsame Pakete mit unterschiedlichen Spins zu unterstützen Erzeugen mehrerer Distribution, ändern sogar den Namen, und wir wollen wahrscheinlich einige Diskussionen darüber, wie unser Verdienst (basierend auf xxxx TM) angegangen werden sollte beinhalten.

Also, was wir Spin wollen, brauchen wir Unterstützung auf ABF ersten und dann können wir auch damit der RPM gepatcht “nichts” zu sein, und die Spins können die Namen geeigneter Weise abhängig von der verwendeten Plattform zu kompilieren markieren

Also, kein Name für jetzt, bis wir finden einen geeigneten Weg, um es zu tun.

Wir könnten die Distribution Cooker, oder eine andere ausgefallene Codenamen.

Und jeder Spin nennen kann die ISO-und Grafik, wie sie wollen.

Es ist ein Vorschlag, Innominata (lateinisch für noname) als temporäre Namen haben. Die meisten Menschen in einer Sitzung gesagt, sie sind für es wird jedoch eine separate Diskussion Gmoro in Cooker ML dafür gestartet werden.

Update: Joao Patricio entwirft einen Vorschlag über die Regeln, wie wir den Namen zu wählen. Entwurfs alle zusammen diskutiert werden (Details der Verfahren in Kürze). Das Ziel ist es, die Regeln und voll gemeinsame Gemeinschaft Entscheidung über den Namen haben, bevor die Freigabe erfolgt. Für den Moment “Innominata” tritt an die Stelle als Platzhalter.

Achtung! Wenn das Thema ist wichtig für Sie, folgen Sie bitte es im Allgemeinen ML und dem Blog, um Ihre Meinung zu Zeit zu liefern.
 

4. Aktuelle Konflikte, Zusammenfassung aus Verband und Anregung zur Diskussion / Schließung des Themas ein.Bonjour à tous,

Le 10 Avril, une réunion commune CT (comité technique = maintenant tous les développeurs actifs) + Conseil a eu lieu. Les journaux seront publiés. Voici l’ordre du jour et le résumé.

Cordialement,
Kate Lebedeff
Secrétaire OMA

Point de l’ordre du jour:
Comité technique, conseil et développeurs actifs («cooker») : définitions et relations. Suggestions pour en discuter.

Cette occasion est utilisée pour inviter une fois de plus tous les développeurs actifs à entrer dans l’association et parler (même ils ne sont pas membres) sur les préoccupations qu’ils ont. L’association sert à répondre à ces préoccupations et résoudre les problèmes, c’est exactement ce pourquoi elle a été fondée.

Résumé:
Voici quelques définitions principales, qui ont été approuvés.

Définition pour plus de clarté:
Communauté cooker = Association OpenMandriva. (Cela signifie qu’ il existe une seule communauté, impliquant tout le monde. Il n’y a pas de communauté « cooker » séparée).

Cela inclut les développeurs, traducteurs, les graphistes, les gens du marketing, etc. Tout ceux qui apprécient ou contribuent, y compris les utilisateurs, les testeurs, ceux qui prennent en charge un travail, font partie de cette communauté au sens large (communauté est un terme pour désigner les devs actifs, les développeurs inactifs, les utilisateurs et contributeurs occasionnels)

Tout contributeur/membre /développeur /gestionnaire peut être bénévole ou payé par les sponsors à travers l’Association.

Tout le monde a les mêmes chances et personne ne sera protégé ou traité d’une manière particulière.
 

1. Quelques notes sur la formulation et extras
Cooker fait partie de OMA (OpenMandriva Association), mais la contribution est ouverte.

Cooker est également le développement actif du projet OMA.

Il est également censé être une base pour d’autres projets en dehors de la portée de l’OMA (c’est plus inclusive des personnes qui veulent utiliser la base de code pour construire quelque chose d’autre).

Le projet est antérieur à l’association, et MDV en disant qu’elle donnait le projet à la communauté est antérieure à l’association. L’association a été créée pour aider et soutenir le projet. Elle pourrait soutenir d’autres projets aussi si elle le voulait.

Il est possible de contribuer et n’avoir aucune implication dans l’association.

CT (comité technique)
Le CT est une forme de représentation à l’intérieur de la communauté de cooker.

Actuellement le CT implique tous les développeurs actifs.

La réunion CT suivante (que ce soit demain ou plus tard) doit être composé des membres les plus précieux et expérimentés, ou des leaders naturels qui prennent le devant.

Qui peut être dans le CT?
Les membres de la «communauté cooker” qui sont également membre de l’OMA, élus/choisis par la «communauté cooker» (avec quelques possibles recommandations argumentées du conseil). Le CT agit comme le moteur des projets et communique avec toutes les autres parties concernées, y compris le conseil et prend les responsabilités techniques. Le droit de veto (si nécessaire dans certains cas extrêmes difficilement résoluble) sur les décisions et les choix des membres est une responsabilité partagée du Conseil (représentant la majorité de la communauté qui partage les mêmes idées) et le CT lui-même, qui réglemente les responsabilités techniques.

(Les membres du CT doivent être membres de l’OMA. Des exceptions sont possibles, si accord mutuel (cooker incluant le conseil).

(À définir aussitôt que possible avec cooker: rôles exacts, qui devraient être dans le CT (du point de vue des fonctions, la prochaine étape dès que possible: des idées pour les candidatures).

Chef(s) de projet
Membre(s) du CT, responsable pour la feuille de route et le développement global. Il prend des décisions fondées sur des consultations approfondies avec les membres de cooker. Il prend la responsabilité des décisions en cas de conflits ou de tentatives de détournement. S’il ne peut trouver de solution par lui-même, ou si la décision prise est en conflit avec les autres membres du CT, une décision conjointe doit être prise, retournant le pouvoir à l’unité de la communauté.

Conseil:
L’élément directeur de l’Association, responsable de la coordination des travaux et des ressources globales. Important à retenir: le conseil est composé de membres de l’association, et est conçu pour représenter tout le monde dans l’Association, et est élu par les membres.

Le conseil n’a pas d’opinion propre par lui-même, ces personnes sont élues pour représenter les membres (ce qui signifie que, lorsque le conseil parle, ce n’est pas seulement un groupe brut de personnes sorti de nulle part: elles ont été élues pour représenter la communauté. Elles ne produisent pas leur propres opinions, elles représentent).
 

2. Association comme entité: fondée pour quelle raison, pour qui et quelles fonctions ?
L’adhésion à l’OMA est gratuite et ouverte à tout le monde, pas d’obligations ou restrictions. L’objectif de l’OMA est de faire de la distribution une réussite (en fournissant des ressources, des infrastructures, du marketing, des sponsors attirer, etc.)

Normalement membres de l’OMA doivent inclure à la fois toute la communauté cooker + les autres contributeurs non techniques.

Nous utilisons cette occasion pour dire encore une fois: les contributeurs sont les bienvenus dans l’OMA, l’association a été fondée pour répondre à vos besoins. Devenez membres et influencez les décisions, élisez vos représentants, participez et travaillez en commun grâce à votre venue et votre opinion.

Si nous avons oublié d’inviter quelqu’un à ce jour, nous nous excusons, ce n’était pas notre intention. L’association est jeune et commence tout juste. Les portes sont grandes ouvertes.

L’association représente beaucoup de gens qui partagent la même vision de l’avenir de la, bientôt, meilleure distro linux du monde

Normalement toute la communauté cooker devrait être membre de l’OMA si elle partage l’objectif de faire une distribution réussie.
 

3. question du nom de la Distro
La solution temporaire est d’aller vers une distribution sans nom

Maintenant : nous n’avons pas encore les moyens techniques en place (support sur ABF – Automatic Build Farm) pour une distribution multi-nom/multi-spin (multi variante) en ce moment, et nous comme n’avons jamais discuté de ce sujet à fond, pouvons-nous convenir de n’avoir pas de nom maintenant ? La question a causé assez d’ennuis déjà.

La raison est simple: si nous décidions maintenant, comment le ferions-nous ? Voter ? Par qui ?

Juste une décision de plusieurs personnes ? Qui ?

Nous pouvons nous appuyer sur ABF pour les paquets partagés avec différents spins pour soutenir la génération de multiples distros, même en changeant le nom, et nous voulons probablement inclure une discussion sur la façon dont notre contribution (basé sur xxxx TM) doit être envisagée.

Donc, quel que soit la variante désirée, nous devons nous appuyer sur ABF d’abord et ensuite nous pouvons même laisser les RPMs patchés pour être «sans nom», et les variantes peuvent étiqueter les noms appropriés en fonction de la plate-forme utilisée pour compiler.

Donc, pas de nom pour l’instant, jusqu’à ce que nous puissions trouver une bonne façon de le faire.

Nous pourrions l’appeler la distribution cooker, ou un autre nom de code de fantaisie.

On peut comme on veut nommer l’ISO et inclure les éléments graphiques de chaque variante.

Il a été suggéré d’avoir Innominata (« sans nom » en latin) comme nom temporaire. La plupart des personnes lors de la réunion ont dit qu’elles sont en faveur de celui-ci, cependant, un débat distinct sera lancé par Gmoro dans la liste cooker pour cela.

Mise à jour: Joao Patricio rédige une proposition sur des règles, la façon dont nous choisissons le nom. Le projet sera discuté tous ensemble (détails de la procédure à venir bientôt). L’objectif est d’avoir des règles et des décisions pleinement communes sur le nom avant la sortie de la release. Pour le moment “Innominata” en tient lieu.

Attention! Si le sujet est important pour vous, s’il vous plaît suivez la liste de diffusion générale et le blog, afin de donner votre opinion à temps.
 

4. Conflits récents, résumé par l’Association et suggestion de discussion/clôture du sujet
Reporté à la semaine prochaine. Gmoro publiera un ordre du jour et confirmera l’heure.

Librement traduit par jcl. En cas d’ambiguité, se reporter au texte original en anglaisHello everybody

On April 10th, a common TC (Technical committee, for now = all active developers) + Council meeting took place. Logs will be posted. Here is the agenda and summary.

Best,
Kate Lebedeff
OMA secretary

Agenda point:
Technical committee, council and all-active-developers (“cooker”) definitions and their relations. Suggestions to discuss.

This occasion is used to once more invite all active developers to enter Association and speak out (even they are not members) about any concerns they have. Association is to serve these concerns and solve issues, this is exactly why it was founded.

Result summary:
Here are some main definitions, which were agreed.

Definition for clarity:
Cooker community = OpenMandriva Association. (This means, there exists just one community, involving everybody. There is no separate “cooker” community).

This includes developers, translators, artwork people, marketing people, etc. Everyone that likes or contribute, including users, testers, those who do support – is part of this broader community (community is a term to refer to the active devs, inactive developers and users and sporadic contributors)

Any contributor/member/developer/manager could be free will contributor or paid by sponsors through the Association.

Everyone has the same chances and no one is going to be protected or treated in any special way.
 

1. Some notes on wording and extras:
Cooker is OMA’s, but contribution is open

Cooker is also the active/rolling development of the OMA project.

It is also meant to be a base for other projects outside of OMA’s scope (it’s more inclusive of people who want to use the code base to build something else).

The project predates the association, and MDV saying they were giving the project to the community predates the association. The association was set up to help support the project. It could potentially support other projects too if it wanted.

It’s possible to contribute in the community and have no involvement with the association.

TC (Technical committee).
The TC is a form of representation inside the cooker community.

Currently TC involves all active developers.

The next TC (whenever it comes, tomorrow or much later) is to be the most valuable and experienced members, or natural born leaders that take the front.

Who can be in TC?
The members of the “cooker community” who are also OMA member, (s)elected by “cooker community” (with some possible argumented recommendations from council). TC acts as the projects engine and communicator with all other involved parties, including council, and takes the technical responsibilities. Veto power (if needed in some extreme case not easily solvable) on decisions and selection of members is a shared responsibility of the council (representing the majority of the community that shares the same ideas) and the TC itself, that regulates the technical responsibilities.

(TC members need to be OMA’s members. There are exceptions possible, given full mutual agreement (cooker including council).

(to be defined ASAP with cooker: exact roles, who should be in the TC (from the point of view of functions, next step asap: ideas for candidacies).

Project leader (s).
Members of the TC, responsible for overall route and development. Take decisions based on extensive consultations with cooker members. Take the RESPONSIBILITY for decisions in case of conflicts or attempts of hijack. If it can solve it by itself, or the decision taken is in conflict with other TC members, a joint decision need to be taken, reverting the power to the unity of the community.

Council:
The directive body of the Association, responsible for coordinating overall work and resources. Important to remember: council consists of members of the association, and is designed to represent everybody in the Association, and is elected by the members.

Council does not have own opinion as such, these people are elected to represent members (this means, that when council speaks, it is not just a blunt group of people out of nowhere: they were elected to represent community. They do not produce their own opinions, they represent).
 

2. Association as an entity: why founded, for whom and it’s functions
Membership in OMA is free and open to anybody, no obligations or restrictions. OMA’s goal is to make the project’s distro successful (by providing resources, infrastructure, marketing, attracting sponsors, etc.).

Normally OMA members should include both all cooker community + other non technical contributors.

We use this chance to say once again: contributors are most welcome to join OMA, the association was founded to serve your needs. Become a member and influence decisions, elect your representatives, participate and form the common work with your input and opinion.

If anybody was bypassed with invitation so far, we apologize, this was not the intention. Association is young, it all just starts. Doors are wide open.

The association is representing a lot of people that share the same vision for the future of the, soon to be, best linux distro of the world

Normally all cooker community should be OMA members if they share the goal to make the distro successful.
 

3. Distro name issue.
The temporary solution is go with a distro with no name for

Now. We still don’t have the appropriate technical resources (support on ABF) in place to a multi-name/multi-spin distro right now, and we never discussed this topic thoroughly so can we agree on having no-name now, not to go into that? The issue caused enough trouble already.

Reason is simple: if we were to decide now, how would we do that? Vote? By who?

Just decision of several people? Who?

We can make support on ABF for shared packages with different spins to support generating multiple distro, changing even the name, and we probably want to include some discussion on how our merit ( based on xxxx TM) should be approached.

So whatever spin we want, we need support on ABF first and then we can even let the RPM patched to be “nothing” , and the spins can tag the names appropriately depending on the platform used to compile

So, no name for now, until we can find a proper way to do it.

We could call the distro cooker, or some other fancy codename.

And each spin can name the ISO and artwork the way they want.

There is a suggestion to have Innominata (Latin for noname) as temporary name. Most people in a meeting said they are in favor of it, however, a separate discussion will be started by Gmoro in cooker ML for that.

Update: Joao Patricio drafts a suggestion on rules, how we choose the name. Draft to be discussed all together (details of procedure to come soon). The target is to have the rules and fully common community decision on the name before the release is out. For the moment “Innominata” takes the place as a placeholder.

Attention! If the topic is important for you, please follow it in general ML and the blog, in order to supply your opinion on time.
 

4. Recent conflict, summary from Association and suggestion for discussion/closing the topic.
Postponed to next week. Gmoro will post an agenda and confirm the time.

[notice]Alcuni articoli vengono mantenuti nella versione originale inglese poichè contengono informazioni tecniche o legali che la traduzione potrebbe involontariamente alterare.[/notice]Olá a todos.

No dia 10 de abril, ocorreu uma reunião entre o TC (Comitê Técnico, por agora = todos os desenvolvedores ativos) + o Conselho. Logs serão publicados. Aqui está a agenda e resumo.

Cumprimentos,
Secretária OMA

Ponto da agenda:
Comitê Técnico, Conselho e todos os desenvolvedores ativos (“cooker”), definições e as suas relações. Sugestões para discutir.

Esta ocasião é usada mais uma vez para convidarmos todos os desenvolvedores ativos para entrar na Associação e falar (mesmo que não sejam membros) sobre quaisquer preocupações que tenham. A Associação serve para resolver estas preocupações e problemas, é exatamente por isso que foi fundada.

Resumo:
Aqui estão algumas definições principais, que foram acordadas.

Definição para maior clareza:
Comunidade Cooker = Associação OpenMandriva. (Isto significa que existe apenas uma comunidade, envolvendo todos. Não há nenhuma comunidade “cooker” em separado).

Isso inclui desenvolvedores, tradutores, profissionais de arte, profissionais de marketing, etc. Todo mundo que gosta ou contribui, inclusive os usuários, testadores, aqueles que dão suporte – fazem parte desta comunidade em geral (comunidade é um termo para se referir aos devs ativos, desenvolvedores inativos e aos usuários e colaboradores esporádicos).

Qualquer contribuidor/membro/desenvolvedor/gerente pode ser voluntário ou pago por patrocinadores através da Associação.

Todo mundo tem as mesmas oportunidades e ninguém será protegido ou tratado de qualquer maneira especial.
 

1. Algumas notas sobre palavras e extras:
Cooker é da OMA, mas a contribuição está aberta.

Cooker é também o desenvolvimento ativo/constante do projeto OMA.

Também pretende ser uma base para outros projetos fora do âmbito da OMA (inclusivo para pessoas que querem usar o código base para construir outra coisa).

O projeto é anterior à associação, e a MDV diz que eles estavam dando o projeto para a comunidade já antes da associação. A associação foi criada para ajudar a apoiar o projeto. Poderia também apoiar outros projetos, se quisesse.

É possível contribuir na comunidade e não ter nenhum envolvimento com a associação.

TC (Comitê Técnico).
O TC é uma forma de representação dentro da comunidade Cooker.

Atualmente o TC envolve todos os desenvolvedores ativos.

O próximo TC (quando aparecer, quer se trate amanhã ou mais tarde) é para ser os membros mais valiosos e experientes, ou líderes natos que levam a frente.

Quem pode estar no TC?
Os membros da “comunidade Cooker”, que também são membros OMA, eleitos pela “comunidade Cooker” (com algumas possíveis recomendações do Conselho). O TC funciona como o motor de projetos e comunicador com todas as outras partes envolvidas, incluindo o conselho, e assume as responsabilidades técnicas. Poder de veto (se necessário, em alguns casos extremos que não são facilmente solucionáveis​​) em decisões e escolhas dos membros é uma responsabilidade partilhada entre o Conselho (que representa a maioria da comunidade que compartilha as mesmas idéias) e o próprio TC, que regula as responsabilidades técnicas.

(Membros do TC devem ser membros da OMA. Há exceções possíveis, dado pleno acordo mútuo (incluindo o conselho e o Cooker).

(a ser definido o mais rápido possível com o Cooker: papéis exatos que deveriam estar no TC (do ponto de vista das funções, o próximo passo o mais cedo possível: idéias para candidaturas).

O(s) líder(es) do projeto.
Os membros do TC são responsáveis pelo rumo e desenvolvimento global. Tomam decisões com base em amplas consultas com os membros do Cooker. Assumem a responsabilidade por decisões em casos de conflitos ou tentativas de roubos. Se ele não poder resolvê-lo por si mesmo, ou a decisão tomada está em conflito com outros membros do TC, uma decisão conjunta deve ser tomada, revertendo o poder para a unidade da comunidade.

Conselho:
O corpo diretivo da associação, responsável por coordenar o trabalho geral e recursos. Importante lembrar: o conselho é composto por membros da associação, é projetado para representar todos na Associação, e é eleito pelos membros.

O Conselho não tem opinião própria, como tal, estas pessoas são eleitas para representar os membros (o que significa que, quando o conselho fala, não é apenas um grupo fechado de pessoas do nada: foram eleitas para representar a comunidade. Elas não produzem as suas opiniões próprias, elas representam).
 

2. Associação como uma entidade: por que foi fundada, para quem e quais funções
A participação na OMA é gratuita e aberta a qualquer pessoa, sem obrigações ou restrições. O objetivo da OMA é fazer a distro do projeto bem sucedida (por meio de recursos, infraestrutura, marketing, captação de patrocinadores, etc.)

Nos membros da OMA devem estar incluídos ambos, todos da comunidade Cooker + outros contribuintes não técnicos.

Usamos essa oportunidade para dizer mais uma vez: contribuintes são muito bem-vindos para se juntar a OMA, a associação foi fundada para atender suas necessidades. Torne-se um membro e influencie nas decisões, eleja seus representantes, participe e trabalhe em conjunto com a sua contribuição e opinião.

Se alguém não foi informado do convite até agora, pedimos desculpas, essa não era a intenção. Associação é jovem, e está a iniciar. As portas estão abertas.

A associação está representando uma grande quantidade de pessoas que compartilham as mesmas visões para o futuro da, em breve, melhor distro linux do mundo.

Normalmente todos da comunidade Cooker devem ser membros OMA se eles compartilham o objetivo de tornar a distro bem sucedida.
 

3. Questão do Nome da Distro.
A solução temporária é ir com uma distro com nenhum nome.

Agora. Nós ainda não temos os recursos técnicos adequados (suporte na ABF) para uma distro multi-nome/multi-spin, e nós nunca discutimos esse assunto cuidadosamente, de modo que podemos concordar em ter nenhum nome agora, ou vamos entrar nessa? O assunto já causou bastantes problemas.

A razão é simples: se tivéssemos que decidir agora, como faríamos isso? Votar? Por quem?

Apenas decisões de várias pessoas? Quem?

Nós podemos fazer o suporte na ABF para pacotes compartilhados com spins diferentes para apoiar a criação de distro múltiplas, mudando até mesmo o nome, e provavelmente vamos querer ter alguma discussão sobre como nosso mérito (baseado em xxxx TM) deve ser abordado.

Assim, qualquer spin que queremos, primeiro precisamos de apoio na ABF e depois podemos até deixar o RPM para ser “nada”, e os spins pode marcar os nomes de forma adequada, dependendo da plataforma utilizada para os compilar.

Assim, nenhum nome por enquanto, até que possamos encontrar uma maneira correta de fazê-lo.

Poderíamos chamar à distro cooker, ou algum outro codinome.

E cada spin pode nomear a ISO e obras de arte da maneira que querem.

Há uma sugestão para que Innominata (latim para sem nome) como nome temporário. A maioria das pessoas em uma reunião disseram que são a favor dela, no entanto, uma discussão em separado será iniciada por Gmoro na ML do Cooker para isso.

Atualização: João Patrício elabora uma sugestão de regras, como podemos escolher o nome. Sugestão a ser discutida em conjunto (detalhes do procedimento para vir em breve). A meta é fazer com que as normas e a decisão da comunidade seja totalmente comum sobre o nome antes do lançamento. Para o momento “Innominata” toma o lugar.

Atenção! Se o assunto é importante para você, por favor, siga-o na ML geral e no blog, a fim de dar a sua opinião na hora.
 

4. Recente conflito, resumo da associação e sugestão para discussão/fechando o tópico.
Adiada para a próxima semana. Gmoro irá publicar uma agenda e confirmar a hora.

(Tradução por Raul Liota da Rosa)

1 comment

    • Vandenabeele on July 12, 2013 at 9:19 am

    Bonjour,
    Je suis content de voir que le projet Mandriva-Linux va continuer
    J’ai utilisé Linux depuis Mandrake 6 jusqu’à Mandriva Linux 2010
    J’étais ennuyé de ne plus retrouver cet OS pour les particuliers

    Cordialement
    un utilisateur lambda

Comments have been disabled.