From 4bb472c47546af379b16836a7c4d969fe123efe8 Mon Sep 17 00:00:00 2001 From: Kyle Auble Date: Mon, 17 Sep 2012 22:47:02 -0500 Subject: Move Contributing content to wiki --- templates/de/contributing.template | 402 ------------------------------------ templates/en/contributing.template | 330 ----------------------------- templates/he/contributing.template | 325 ----------------------------- templates/pt/contributing.template | 346 ------------------------------- 4 files changed, 1403 deletions(-) delete mode 100644 templates/de/contributing.template delete mode 100644 templates/en/contributing.template delete mode 100644 templates/he/contributing.template delete mode 100644 templates/pt/contributing.template diff --git a/templates/de/contributing.template b/templates/de/contributing.template deleted file mode 100644 index d1875d4..0000000 --- a/templates/de/contributing.template +++ /dev/null @@ -1,402 +0,0 @@ - - - -

Mitarbeit an Wine

- -

Man ist schnell etwas überwältigt, wenn man neu bei Wine ist. Ja, es gibt viele Dinge - zu tun, aber wo fängst Du am besten an? Gibt es etwas Leichtes, mit dem Du loslegen kannst? - Gibt es etwas, das nicht detaillierteste Kenntnisse des Windows API und der Wine-Interna verlangt? - Was, wenn Du C nicht kennst? Oder wenn Du gar kein Programmierer bist?

-

Nun, hier sind ein paar Projekte, die Dir einen Einstieg geben könnten. Bitte beachte, dass - diese Übersicht keine offizielle Ansage ist, was an Wine getan werden sollte. Es ist einfach - eine Liste von Dingen, die wichtig und nützlich sind. In jedem Fall freuen wir uns über - Deine Rückmeldung. Ebenso lass uns bitte wissen, wenn Dir ein Projekt einfällt, das wir - zu dieser Übersicht hinzufügen sollten.

-

Viele Projekte können sogar durchgeführt werden, wenn Du kein C Programmierer bist oder - Du keine detaillierten Kenntenisse der Windows-Interna hast. Gib uns Bescheid, wenn Du Interesse - hast, ein bestimmtes Projekt anzugehen.

-

Hier sind ein paar Anhaltspunkte, die Dir helfen, loszulegen:

- -
    -
  1. Allgemeine Arbeiten -
      -
    1. Erstelle Fonts
      2. -
    2. Zeichne Icons für Wine
      3. -
    3. Werde verantwortlich für eine Anwendung
      4. -
    4. Fehlersuche und Unterstützung
      5. -
    -
    2. -
  2. Entwicklung -
      -
    1. Einige Entwicklungsaufgaben
      2. -
    2. Konformitätstests
      3. -
    3. Dokumentation der Windows API Funktionen
      4. -
    4. Portiere Deine Windows-Anwendung auf Wine
      5. -
    5. Führe einen fokussierten Code Review durch
      6. -
    -
    3. -
  3. Sonstiges -
      -
    1. Schreiben von Dokumentation
      2. -
    2. Lokalisierungsarbeit
      3. -
    3. Public Relations
      4. -
    4. Spenden
      5. -
    -
    4. -
- -

Zeichne Icons für Wine

- -

Wegen des Copyrights kann Wine keine Windows-Icons eins zu eins übernehmen. Wir - müssen sie also neu zeichnen und dabei ein ähnliches Design beibehalten, damit - Anwender nicht vollkommen verloren sind. Trotzdem müssen sie unterschiedlich genug - sein (und eventuell schöner). Du kannst dies sehen, wenn du einen Dateiauswahldialog - öffnest.

-

Benötigte Fertigkeiten/Kenntnisse:

- - -

AppDB: Werde verantwortlich für eine Anwendung

- -

Ein weiterer sehr wichtiger Aspekt des Testens von Wine ist der regelmäße - Gebrauch oder Test von echten Anwendungen und das schnellstmögliche Melden von - Regressionsfehlern an die Wine-Entwickler. So können Regressionen früh - entdeckt werden, während die Anzahl der Änderungen, die durchsucht werden - müssen, noch gering und der Wine-Entwickler, der die Änderung durchgeführt - hat, noch verfügbar ist. Ein weiterer Grund, warum Deine Unterstützung - besonders wertvoll ist, ist dass die Wine-Entwickler wahrscheinlich selbst keinen - Zugriff auf die Anwendung haben (sie können nicht alle Anwendungen kaufen) oder sie - nicht gut genug kennen, um sie ordentlich testen zu können.

-

Du kannst sogar noch mehr helfen, in dem Du die Verantwortung für eine Anwendung - übernimmst, das heißt dass Du den Eintrag der Anwendung in der AppDB (en) pflegst. Viele Anwendungen können - zum Laufen gebracht werden (oder besser zum Laufen gebracht werden), indem einfach nur - die richtige Kombination von nativen (Windows) und mitgelieferten (Wine) Bibliotheken - verwendet wird. Indem du die Anwendung mit verschiedenen Kombinationen von Bibliotheken - testest und deine Ergebnisse in dem entsprechenden Eintrag in der AppDB dokumentierst, - hilfst du anderen Nutzern von Wine, mit der Anwendung produktiv zu sein. Damit machst - Du Wine für eine größere Anzahl von Menschen nützlicher.

-

Benötigte Fertigkeiten/Kenntnisse:

- - -

Fehlersuche und Unterstützung

-

Weil es so viele Windows-Anwendungen gibt, und weil nur sehr wenige von - diesen perfekt funktionieren, bekommen wir viele Fragen von Anwendern, - viele Fehlerbeschreibungen, die diagnostiziert werden müssen, und dann - viele Fehler, die behoben werden müssen.

-

Deswegen sind Fehlerdiagnose und Unterstützung zwei eng verwandte - Aktivitäten, die sehr wichtig für Wine sind. Wir brauchen also - Leute, die Willens sind, die Fragen und Probleme, die in der Newsgroup, auf - wine-users und in Bugzilla auftauchen, zu beantworten und anschließend - zu vorzusortieren:

- -

Auf Dan Kegels Wine QA Project (en) Website - findest du eine Schritt für Schritt Anleitung für neue Freiwillige für - die Wine-Qualitätssicherung.

-

Benötigte Fertigkeiten/Kenntnisse:

- -

Weitere Informationen findest du auf unserer Fehlersichtungs Seite.

- -

Entwicklung

- -

Einige Entwicklungsaufgaben

- -

Konformitätstests

- -

Das Ziel der Konformitätstests für Wine ist sicherzustellen, dass das Verhalten - der Wine APIs konform zu den entsprechenden Windows APIs ist. Da es viele Windows-Versionen - von 95 bis 7 gibt, brauchen wir sowohl Leute, die die Tests schreiben, als auch Freiwillge, - die die Tests unter Windows ausführen. Die Test-Suite ist noch weit davon entfernt, - komplett zu sein, aber jedes kleine Bisschen hilft.

- -

Benötigte Fertigkeiten/Kenntnisse:

- - -

Dokumentation der Windows API Funktionen

- -

Der Hauptgrund ist, dass MS beim Wechsel zu neuen APIs dazu tendiert, die komplette - Dokumentation der alten (z.B. Windows 3.1) zu entfernen. Das Ziel ist, eine - unabhängige Dokumentation des Windows APIs zu schreiben. Da wir das komplette API neu - implementieren, wäre es eine gute Praxis, das was wir implementieren auch zu dokumentieren. - Wir sollten uns insbesondere auf die Askpekte konzentrieren, die in der "offiziellen" - Dokumentation nicht gut abgedeckt sind, wie z.B. Unterschiede zwischen Dokumentation und - tatsächlichem Verhalten, Fehler, plattformspezifische Aspekte und alles das, was - normalerweise unvollständig ist (was passiert, wenn man einen NULL Pointer übergibt, - wenn der Puffer zu klein ist, ...) Ohne solch eine Dokumentation gibt es für neue - Entwickler keine Möglichkeit herauszufinden, ob eine seltsame Eigenart in der - Implementierung unbedeutend oder ein (Un-)Feature ist, auf das sich einige Programme verlassen. - Während Wine reift werden diese Probleme wichtiger und wichtiger.

-

Benötigte Fertigkeiten/Kenntnisse:

- - -

Portiere Deine Windows-Anwendung auf Wine

- -

Wenn Du selbst an einer Windows-Anwendung arbeitest, könnte eine Portierung auf Wine - der beste Anfang sein, Code zu Wine beizutragen. Du kannst damit anfangen, zu versuchen, - die Anwendung unter Wine laufen zu lassen und sie danach mit Wine zu kompilieren. Ich - schlage deshalb vor, mit einer Anwendung zu beginnen, an der Du normalerweise arbeitest, - weil du natürlich Zugriff auf den Quellcode hast. Und außerdem weißt Du, - wie sie funktioniert, weil du sie programmierst. Darüberhinaus kannst Du Probleme von - beiden Seiten angehen: füge Traces sowohl in Deine Anwendung als auch in Wine ein. - Kombiniert vereinfacht es die Suche danach, was wo warum schiefläuft, sehr. Und - da Du schon weißt, was Wine eigentlich tun sollte, bist du dann auch besser dazu - in der Lage, den Fehler in Wine zu beheben. Alternativ kannt Du auch Beispiele aus - Programmierlehrbüchern testen. Ein Paket, mit dem Du direkt loslegen und die - Ergebnisse auf einer Website dokumentieren kannst, findest du - hier (en).

-

Benötigte Fertigkeiten/Kenntnisse:

- - -

Führe einen fokussierten Code Review durch

- -

Ein normaler 'allgemeiner' Code Review kann ziemlich langweilig und ineffizient sein. - Wenn Du allerdings nach etwas speziellem suchst, kann das eine produktive Art und Weise - sein, Fehler zu finden und zu beheben. Normalerweise fängst Du damit an, dir ein - Thema auszusuchen. Ich habe beispielsweise einmal Code gefunden, der strncpy verwendet - hat, ohne sicherzustellen, dass das Ergebnis mit '\0' abschließt. Meistens - verbessert man dann nur den Code an dieser Stelle und macht dann mit anderen Sachen weiter. - Aber wieviele ähnliche schwer zu findene Fehler würde das an anderen Stellen - bestehen lassen? Also traf ich die Entscheidung, alle Verwendungen von strncpy - zu überprüfen. Das kann einige Zeit kosten und so nicht immer möglich sein - (schreib mir falls Du einen speziellen Fehler im Auge, aber keine Zeit dafür hast). - Auf jeden Fall ist es eine nette Weise, sich in den Code hineinzufinden und Du kannst - Fehler finden, ohne monatelange Erfahrung mit Wines Code zu brauchen.

-

Sei allerdings vorgewarnt, dass deine Änderungen von vielen Entwicklern kritisch - durchleuchtet werden, da sie über viele Bereiche verteilt sein werden. Da deine - Änderungen außerdem wahrscheinlich keine offensichtlichen Fehlerbehebungen - sein werden, kannst du auf (begründeten) Widerstand treffen. Stell sicher, dass - deine Änderungen tatsächlich einen Fehler beheben und nicht einfach nur ein - Problem unter den Teppich kehren (insbesondere, wenn es sich um Compiler-Warnungen - handelt). Kosmetische Verbesserungen oder unnötige Änderungen sind generell - nicht willkommen (aber ich gebe zu, dass es manchmal schwer ist, zu widerstehen).

-

Hier sind einige Vorschläge:

- -

Benötigte Fertigkeiten/Kenntnisse:

- - -

Sonstiges

- -

Schreiben von Dokumentation

- -

Wine hat einen ständigen Bedarf an Aktualisierungen der Dokumentation. Wine - hat seine "Anleitungen (en)", wie den Wine User - Guide etc. Die SGML-Quellen der Anleitungen befinden sich in einem - separate Git Zweig.

-

Weitere wichtige Dokumentationen sind die README Datei und die man pages und - anderen Dateien im documentation Verzeichnis.

-

Deine Aufgabe wäre es sicherzustellen, dass jeder Patch, der von einem - Entwickler beigetragen wird, der das Konfigurationsverhalten von Wine irgendwie - ändert, so schnell wie möglich ordentlich dokumentiert wird. Dazu - müsstest Du neue Funktionalitäten testen und eventuell auch die - Entwickler fragen, was ihr Patch im Einzelnen macht (und vergiss nicht, den - Entwicklern einen zu verpassen, die die Arbeitsweise ihres Patches überhaupt - nicht dokumentiert haben!).

-

Die Aktualisierung der Dokumentation findet statt, in dem Du "Git Diffs" der - entsprechenden Dateien an wine-patches schickst.

- -

Benötigte Fertigkeiten/Kenntnisse:

- - -

Lokalisierungsarbeit

- -

Des weiteren brauchen wir lokalisierte Versionen der Wine Guides und - man pages. Dafür brauchen wir viele Helfer, die Willens sind, - Änderungen an der englischen Dokumentation in Fremdsprachen zu - übersetzen. Falls Du uns mit einer bestimmten Sprache helfen willst, - dann melde Dich bitte bei uns dafür an!

-

Momentan suchen wir Helfer für folgende Übersetzungen:

- -

Wir brauchen außerdem ein "QuickStart/Howto" Dokument, das grundlegende Hilfe - für die Installation und Konfiguration von Wine mit etwas mehr Details als die - README-Datei gibt, aber gleichzeitig viel kürzer als der Wine User Guide ist - (könnte auch ein Kapitel dieser Anleitung sein). Dieses Dokument müsste dann - in mehrere Sprachen übersetzt werden, was es zumindest etwas einfacher für - Anwender, die kein Englisch sprechen, machen würde, Wine zu installieren und - einzurichten.

-

Benötigte Fertigkeiten/Kenntnisse:

- - -

Public Relations

- -

Momentan haben wir fast gar kein Public Relationship Management. Das sollte sich - verbessern.

-

Die einzige Form von PR, die wir momentan haben, läuft auf "Eulen nach Athen - tragen" hinaus, da wir nur Artikel auf IT Websites haben (die allermeisten befassen sich - ausschließlich mit Linux!). Wir sollten eine viel breitere Berichterstattung - auf den traditionellen, eher Windows-lastigen Websites haben, und, am wichtigsten, in - Zeitungen, um der Allgemeinheit Erleuchtung zu bringen!

-

Daher ginge bei dieser Arbeit darum, Artikel zu schreiben, die sowohl in regionalen - als auch überregionalen Zeitungen und Online Publikationen erscheinen sollen.

-

Benötigte Fertigkeiten/Kenntnisse:

- - -

Spenden

- -

Durch die Unterstützung des Wine Party Fonds kannst du Deine - Anerkennung der Wine Entwickler demonstrieren. Die Einnahmen werden - für Entwickler-Treffen wie z.B. zukünftige Wine Konferenzen - verwendet, oder in einigen Fällen, um Dokumentation zu kaufen.

-

Die Organisation - Software Freedom Conservancy (en) verwaltet momentan unsere Spenden. - Falls Du Fragen hast oder sonstige Hilfestellung brauchst, besuch - bitte die SFC Website.

-

Die Software Freedom Conservancy Organisation erfüllt die - Anforderungen nach Artikel 501(c)(3), so dass Spenden an diese, so weit das - Gesetz erlaubt, von der Steuer abgesetzt werden können (gilt - für die USA).

- -

Möglichkeiten zu spenden:

- - - - - - - - - - -
- -
- - - - - - - - - $
- -
- 		über Google Checkout
-
- - - - - - -
- 		über PayPal
- -

Darüberhinaus kannst Du Bargeld, Schecks oder internationale Zahlungsanweisungen - in US Währung an untenstehende Adresse senden:

-
Wine Project
-Software Freedom Conservancy, Inc.
-137 MONTAGUE ST STE 380
-Brooklyn, NY 11201-3548
-USA
diff --git a/templates/en/contributing.template b/templates/en/contributing.template deleted file mode 100644 index 0d019f3..0000000 --- a/templates/en/contributing.template +++ /dev/null @@ -1,330 +0,0 @@ - - - -

Contributing to Wine

- -

It's easy to be a bit overwhelmed when you're new to Wine. Yes there may be a lot of things to - do but where should you start? Is there anything simple that can get you started? Is there - anything you can do that does not require an intimate knowledge of the Windows API and of - Wine internals? What if you don't know C? Or if you're not a programmer in the first place?

-

So here are a few projects that might provide you with a starting point. Note that this list - is not an official statement of what should be done on Wine or anything. It's just a list of - things that are important and useful. In any case we welcome your feedback. Similarly, if you - can think of projects to add to the list let us know too.

-

Many projects can be performed even if you are not a C programmer or if you don't have an intricate - knowledge of the Windows internals. Let us know if you are interested in tackling a given project.

-

Here are a few items to help you get started:

- -
    -
  1. General maintenance -
      -
    1. Creating fonts
      2. -
    2. Drawing icons
      3. -
    3. Maintaining applications
      4. -
    4. Bug hunting and support
      5. -
    -
    2. -
  2. Development -
      -
    1. Some development tasks
      2. -
    2. Conformance tests
      3. -
    3. Documentation of the windows API functions
      4. -
    4. Port your Windows application to Wine
      5. -
    5. Perform a focused code review
      6. -
    -
    3. -
  3. Miscellaneous -
      -
    1. Documentation writing
      2. -
    2. Localization work
      3. -
    3. Public relations
      4. -
    4. Donations
      5. -
    -
    4. -
- -

Bug hunting and support

-

Because there are so many Windows applications out there, and because - very few of them work perfectly, we get a lot of questions from users, - many bug reports that need to be diagnosed and then many bugs to fix.

-

Thus bug diagnosis and support are two closely related activities that are - very important to Wine. So we need people willing to answer the questions - and issues that pop up on wine-users and Bugzilla, and then - to triage them:

- -

See also Dan Kegel's Wine QA Project page for - a step-by-step introduction for new Wine QA volunteers.

-

Required skills:

- -

For more information, see our bugs triage page.

- -

Development

- -

Some development tasks

- -

Conformance tests

- -

The goal of Wine conformance testing is to make sure that the behavior - of Wine APIs conforms to that of the corresponding Windows APIs. As there are many versions - of Windows from 95 to 7 we need people to write tests as well as volunteers to run - them on Windows. The test suite is far from complete but every little bit helps.

- -

Required skills:

- - -

Documentation of the Windows API functions

- -

The main reason is that as MS moves to new APIs it tends to remove all documentation - of the old ones (e.g. Win 3.1). The goal is to write an independent documentation - of the Windows API. Since we are re implementing all this API it would be a good coding - practice to also document what we implement. We should in particular concentrate on aspects - that are not very well covered in the 'official' documentation like discrepancies with the - official documentation, bugs, platform specific aspects, and all these things that are typically - not very well covered like what happens if you pass a NULL pointer, if the buffer is too small, ... - Without such a documentation new developers have no way of telling whether some strange quirk in - the implementation is insignificant or is actually a (mis)feature that some programs rely on. - As Wine matures such problems will become more and more important.

-

Required skills:

- - -

Port your Windows application to Wine

- -

If you are working on a Windows application, porting it to Wine may be the best way to - get started for contributing code to Wine. You can start by trying to run it in Wine and - then try to compile it with Wine. The reason I suggest to start with an application you - normally work on, is that first you obviously have access to the source code and second, - since you programmed it, you know how it works. Furthermore you can attack the problem - from both sides: put traces in your application and in Wine. All this combined together - and makes it much easier to detect where Wine is doing something wrong, what and why. - Then, since you already know what Wine is supposed to do, you're also in a better position - to provide a fix. You can also test the examples of a programming book in Wine. A kit to get - started and create Web pages showing the results is available - here.

-

Required skills:

- - -

Perform a focused code review

- -

A regular 'random' code review can be pretty boring and inefficient. But I think that - if you are looking for something specific it can be a productive way of finding and fixing - bugs. Typically you would start by picking a subject. For instance I once found code that - was using strncpy without making sure the resulting string would be '\0' terminated. - One would normally fix this specific piece of code and move on. But how many similar hard - to find bugs would this leave elsewhere? So I decided to check all instances of strncpy. - This can take some time so one cannot always do it (drop me a line if you think of some - specific bug to look for but you don't have time). But it's a nice way to get acquainted - with the code and you can actually find bugs without needing months of experience on - Wine code.

-

But be warned though that since your changes will be scattered throughout Wine they - will be scrutinized by many developers. Furthermore since your changes probably will - not be direct obvious bug fixes, there may be (founded) resistance. Make sure your - changes are indeed a fix, not something that will just hide the problem under the carpet - (especially with compilation warnings). Also cosmetic fixes, unnecessary changes are - generally not welcome (but I admit it's sometimes hard to resist).

-

Here are a few starting points:

- -

Required skills:

- - -

Miscellaneous

- -

Documentation writing

- -

Wine is in constant need of documentation updates. Wine has its - "Guides", like the Wine User Guide etc. - The SGML source of the Guides can be found in a - separate Git tree.

-

Other important documentation items are the README file - and also the man pages and other files in the documentation/directory.

-

Your job would be to make sure that every patch a developer submits - that changes the Wine configuration behaviour in any way gets documented - properly as soon as possible. This would be done through testing new - functionality and optionally asking developers about what their patch truly - does (and of course don't forget to beat up developers that don't document - the workings of their patch at all!).

-

The documentation updates would be done by sending "git diff"s of the - relevant files to wine-patches.

-

Requirements:

- - -

Localization work

- -

We need help translating Wine resources into foreign languages. What this - covers is common dialogs such as the 'File Open' or 'Print' dialogs, - informational messages such as the crash dialog, some standard error - messages, but also the builtin tools such as Wine notepad. When not - translated these can really impair Wine usability for non-English - speakers.

-

Luckily these are now all translated through standard PO files which makes - this task relatively easy. For detailed instructions on how to help, see our - Translating guide.

- -

We also need to have localized versions of the Wine Guides, README and man - pages. For this to work, we'll need many people willing to translate - changes to the main English documentation into foreign languages. If you're - willing to register for work on a certain language, then please sign up - with us!

-

While being a relatively small part of the documentation, the README and - man pages are probably its most important components. So if you can help - with these we would really be grateful.

-

We also need a 'QuickStart/Howto' document that would describe the basic instructions - for installing and configuring Wine in a bit more details than the README while being much - smaller than the Wine User Guide (it could actually be a chapter of that guide). Then that - document could be translated in multiple languages which would at least make it easier for - non-English speaking people to set up and install Wine.

-

Requirements:

- - -

Public relations

- -

Currently we almost have no Public Relationship management at all. - This should change for the better.

-

Currently almost the only form of PR is "preaching to the choir", - since we're having articles on online IT sites (by far most are Linux only!). - We should have much more coverage on traditional Window'ish sites and, - most importantly, in dead-tree newspapers, to enlighten the general public - also known as The Great Unwashed Masses!

-

Thus such a job would involve writing articles to be presented in - both large and local newspapers and also online publications.

-

Requirements:

- - -

Wine Development Fund

- -

The purpose of the Wine Development Fund is to show appreciation to Wine -developers by collecting funds for developer meetings, such as Wine -Conferences, or in some cases to purchase documentation.

- -

The organization that currently manages our donations is the -Software Freedom -Conservancy. If you have any questions or are otherwise in need -of further assistance please visit the SFC site.

- -

The Software Freedom Conservancy is a 501(c)(3) organization, and -donations made through it are fully tax-deductible to the extent -permitted by law.

- -

Ways to contribute:

- - - - - - - - - - -
- -
- - - - - - - - - $
- -
- 		via Google Checkout
-
- - - - -
- 		via PayPal
- -

You can also send cash, cheque or international money order in US funds to:

- -
Wine Project
-Software Freedom Conservancy, Inc.
-137 MONTAGUE ST STE 380
-Brooklyn, NY 11201-3548
-USA
diff --git a/templates/he/contributing.template b/templates/he/contributing.template deleted file mode 100644 index 594ddb2..0000000 --- a/templates/he/contributing.template +++ /dev/null @@ -1,325 +0,0 @@ - - - -

תרומה ל־Wine

- -

It's easy to be a bit overwhelmed when you're new to Wine. Yes there may be a lot of things to - do but where should you start? Is there anything simple that can get you started? Is there - anything you can do that does not require an intimate knowledge of the Windows API and of - Wine's internals? What if you don't know C? Or if you're not a programmer in the first place?

-

So here are a few projects that might provide you with a starting point. Note that this list - is not an official statement of what should be done on Wine or anything. It's just a list of - things that are important and useful. In any case we welcome your feedback. Similarly, if you - can think of projects to add to the list let us know too.

-

Many projects can be performed even if you are not a C programmer or if you don't have an intricate - knowledge of the Windows internals. Let us know if you are interested in tackling a given project.

-

Here are a few items to help you get started:

- -
    -
  1. תחזוקה כללית -
      -
    1. יצירת גופנים
      2. -
    2. ציור סמלים (אייקונים) ל־wine
      3. -
    3. בעלי יישומים
      4. -
    4. ציד באגים ותמיכה
      5. -
    -
    2. -
  2. תכנות -
      -
    1. משימות שדורשות תכנות
      2. -
    2. בדיקות הסתגלות
      3. -
    3. תיעוד של פונקציות ה־API של windows
      4. -
    4. הסבת יישום ה־Windows שלך ל־Wine
      5. -
    5. הכנסת סקירת קוד ממוקדת
      6. -
    -
    3. -
  3. שונות -
      -
    1. כתיבת תיעוד
      2. -
    2. עבודות תרגום
      3. -
    3. יחסי ציבור
      4. -
    4. תרומות כלכליות
      5. -
    -
    4. -
- -

ציור סמלים (אייקונים) ל־Wine

- -

אין באפשרות Wine למחזר את הסמלים של Windows באופן מובהק עקב נושאי זכויות יוצרים. לכן עלינו לצייר אותם מחדש - ולשמור על עיצוב דומה כדי שהמשתמשים לא ילכו לאיבור לחלוטין, כל זאת תוך הפיכתם לשונים מספיק (ואולי - אף נאים מספיק). ניתן לראות כאלה כשפותחים דו־שיח לבחירת קבצים.

-

כישורים נדרשים:

- - -

מסד נתוני היישומים: מתחזקי יישומים

- -

Another very important aspect of Wine testing is to use or test real - applications regularly and report regressions as soon as possible to the Wine - developers. This way regressions are caught early, while the set of changes - to search through is still small and the Wine developer who made the change - still around. Another reason why your contribution is especially - valuable is that Wine developers probably do not have access to the - application (they cannot buy all the applications out there) or do not know - it well enough to test it properly.

-

You can help even further by becoming an 'application maintainer', that is by - maintaining that application's entry in the Application Database. Many - applications can be made to run (or run better) by using just the right mix - of native (Windows) and built-in (Wine) libraries. By testing the application - with various library mix and then documenting your results in the - corresponding Application Database entry, you will help other Wine users be - productive with that application, thus making Wine useful to a greater number - of people.

-

כישורים נדרשים:

- - -

ציד באגים ותמיכה

-

Because there are so many Windows applications out there, and because - very few of them work perfectly, we get a lot of questions from users, - many bug reports that need to be diagnosed and then many bugs to fix.

-

Thus bug diagnosis and support are two closely related activities that are - very important to Wine. So we need people willing to answer the questions - and issues that pop up on the newsgroup, wine-users and Bugzilla; and then - to triage them:

- -

ניתן גם לעיין בעמוד מיזם אבטחת האיכות של Wine - שנכתב על ידי דן קיגל כדי לערוך היכרות שלב אחר שלב למתנדבי אבטחת האיכות של Wine.

-

כישורים נדרשים:

- - -

תכנות

- -

מספר משימות תכנותיות

- -

בדיקות הסתגלות

- -

The goal of Wine's conformance testing is to make sure that the behavior - of Wine's APIs conforms to that of the corresponding Windows API. As there are many versions - Window's from 95 to XP we need people to write the test as well as volunteers to run - the test on Windows. The test suite is far from complete but every little bit helps.

- -

כישורים נדרשים:

- - -

תיעוד של פונקציות ה־API של Windows

- -

The main reason is that as MS moves to new APIs it tends to remove all documentation - of the old ones (e.g. Win 3.1). The goal is to write an independent documentation - of the Windows API. Since we are re implementing all this API it would be a good coding - practice to also document what we implement. We should in particular concentrate on aspects - that are not very well covered in the 'official' documentation like discrepancies with the - official documentation, bugs, platform specific aspects, and all these things that are typically - not very well covered like what happens if you pass a NULL pointer, if the buffer is too small, ... - Without such a documentation new developers have no way of telling whether some strange quirk in - the implementation is insignificant or is actually a (mis)feature that some programs rely on. - As Wine matures such problems will become more and more important.

-

Required skills:

- - -

הסבת יישום ה־Windows שלך ל־Wine

- -

If you are working on a Windows application, porting it to Wine may be the best way to - get started for contributing code to Wine. You can start by trying to run it in Wine and - then try to compile it with Wine. The reason I suggest to start with an application you - normally work on, is that first you obviously have access to the source code and second, - since you programmed it, you know how it works. Furthermore you can attack the problem - from both sides: put traces in your application and in Wine. All this combined together - and makes it much easier to detect where Wine is doing something wrong, what and why. - Then, since you already know what Wine is supposed to do, you're also in a better position - to provide a fix. You can also test a programming book's examples in Wine. A kit to get - started and create Web pages showing the results is available - here.

-

כישורים נדרשים:

- - -

הכנת סקירת קוד ממוקדת

- -

A regular 'random' code review can be pretty boring and inefficient. But I think that - if you are looking for something specific it can be a productive way of finding and fixing - bugs. Typically you would start by picking a subject. For instance I once found code that - was using strncpy without making sure the resulting string would be '\0' terminated. - One would normally fix this specific piece of code and move on. But how many similar hard - to find bugs would this leave elsewhere? So I decided to check all instances of strncpy. - This can take some time so one cannot always do it (drop me a line if you think of some - specific bug to look for but you don't have time). But it's a nice way to get acquainted - with the code and you can actually find bugs without needing months of experience on - Wine's code.

-

But be warned though that since your changes will be scattered throughout Wine they - will be scrutinized by many developers. Furthermore since your changes probably will - not be direct obvious bug fixes, there may be (founded) resistance. Make sure your - changes are indeed a fix, not something that will just hide the problem under the carpet - (especially with compilation warnings). Also cosmetic fixes, unnecessary changes are - generally not welcome (but I admit it's sometimes hard to resist).

-

הנה כמה נקודות התחלה:

- -

כישורים נדרשים:

- - -

שונות

- -

כתיבת תיעוד

- -

Wine is in constant need of documentation updates. Wine has its - "Guides," like the Wine User Guide etc. - The SGML source of the Guides can be found in a - separate Git tree.

-

Other important documentation items are the README file - and also the man pages and other files in the documentation/directory.

-

Your job would be to make sure that every patch a developer submits - that changes the Wine configuration behaviour in any way gets documented - properly as soon as possible. This would be done through testing new - functionality and optionally asking developers about what their patch truly - does (and of course don't forget to beat up developers that don't document - the workings of their patch at all!).

-

The documentation updates would be done by sending "git diff"s of the - relevant files to wine-patches.

-

Requirements:

- - -

עבודות תרגום

- -

Also, we need to have localized versions of the Wine Guides and man - pages. For this to work, we'll need many people willing to translate - changes to the main English documentation into foreign languages. If you're - willing to register for work on a certain language, then please sign up - with us!

-

At this time we are looking for people who can translate.

- -

We also need a 'QuickStart/Howto' document that would describe the basic instructions - for installing and configuring Wine in a bit more details than the README while being much - smaller than the Wine User Guide (it could actually be a chapter of that guide). Then that - document could be translated in multiple languages which would at least make it easier for - non-english speaking people to set up and install Wine.

-

Requirements:

- - -

יחסי ציבור

- -

Currently we almost have no Public Relationship management at all. - This should change for the better.

-

Currently almost the only form of PR is "preaching to the choir", - since we're having articles on online IT sites (by far most are Linux only !). - We should have much more coverage on traditional Window'ish sites and, - most importantly, in dead-tree newspapers, to enlighten the general public - also known as The Great Unwashed Masses!

-

Thus such a job would involve writing articles to be presented in - both large and local newspapers and also online publications.

-

Requirements:

- - -

Wine Development Fund

- -

The purpose of the Wine Development Fund is to show appreciation to Wine -developers by collecting funds for developer meetings, such as Wine -Conferences, or in some cases to purchase documentation.

- -

The organization that currently manages our donations is the -Software Freedom -Conservancy. If you have any questions or are otherwise in need -of further assistance please visit the SFC site.

- -

The Software Freedom Conservancy is a 501(c)(3) organization, and -donations made through it are fully tax-deductible to the extent -permitted by law.

-

דרכים לתרומה:

-
-
- - - - Our PayPal Account -
-
- -

You can also send cash, cheque or international money order in US funds to:

-
Wine Project -Software Freedom Conservancy -1995 Broadway FL 17 -New York, NY 10023-5882
diff --git a/templates/pt/contributing.template b/templates/pt/contributing.template deleted file mode 100644 index 772214f..0000000 --- a/templates/pt/contributing.template +++ /dev/null @@ -1,346 +0,0 @@ - - - -

Contribuir para o Wine

- -

É fácil ficar deslumbrado quando se é novo no Wine. Sim há muitas coisas a - fazer mas onde deve começar? Há algo simples que o possa levar a começar? - Há algo a fazer que não requer um conhecimento íntimo da API Windows e dos - interiores do Wine? E se não souber C? Ou se não for sequer um programador?

-

Então aqui estão alguns projectos que podem providenciar um ponto de partida. - Note-se que esta lista não é uma declaração oficial do que deve ser feito no - Wine nem nada. É apenas uma lista de coisas que são importantes e úteis. Em - qualquer caso o feedback é bem vindo. Igualmente, se pensar em projectos que - podem ser adicionados a esta lista diga-nos também.

-

Muitos projectos podem ser efectuados mesmo que não seja um programador de C - ou que não tenha um conhecimento profundo dos interiores do Windows. Diga-nos - se estiver interessado em abordar um certo projecto.

-

Aqui estão alguns items para o ajudar a começar:

- -
    -
  1. Manutenção Geral -
      -
    1. Criar Fontes
      2. -
    2. Desenhar Icons para o Wine
      3. -
    3. Donos de aplicações
      4. -
    4. Caça ao Bug e relatório
      5. -
    -
    2. -
  2. Desenvolvimento -
      -
    1. Algumas tarefas de desenvolvimento
      2. -
    2. Testes de conformidade
      3. -
    3. Documentação das funções da API Windows
      4. -
    4. Portabilizar as suas aplicações Windows no Wine
      5. -
    5. Efectuar uma revisão ao código
      6. -
    -
    3. -
  3. Vários -
      -
    1. Escrita de Documentação
      2. -
    2. Trabalho de tradução
      3. -
    3. Relações públicas
      4. -
    4. Donativos
      5. -
    -
    4. -
- -

Desenhar Icons para o Wine

- -

O Wine não pode reutilizar os icons do Windows por causa dos direitos de Autor. - Por isso temos de redesenhá-los, mantendo um design semelhante para que os - utilizadores não se sintam perdidos, mas fazendo-os diferente o suficiente - (e talvez até melhores). Poderá ver isto ao abrir uma janela de selecção de - ficheiro.

-

Habilidades necessárias:

- - -

Base de dados de aplicações: Controlador de aplicação

- -

Outro aspecto muito importante de testes ao Wine é o uso ou teste regular de - aplicações reais e reportar regressões assim que possível aos programadores do - Wine. Deste modo as regressões são apanhadas cedo, enquanto o espectro de - alterações a procurar é ainda pequeno e o programador do Wine que fez a mudança - ainda se encontra por aí. Outra razão pela qual a sua contribuição é - especialmente valiosa é que os programadores do Wine provavelmente não têm acesso - à aplicação (eles não podem comprar todas as aplicações que há por aí) ou não a - conhecem bem o suficiente para a testarem devidamente.

-

Você pode ajudar ainda mais se se tornar um 'Controlador da Aplicação', isto é - controlar o espaço dessa aplicação na Base de Dados de aplicações. - Muitas aplicações podem ter de ser executadas (ou executadas melhor) com o uso - certo de uma mistura de bibliotecas nativas (Windows) ou built-in (Wine). Ao - testar a aplicação com várias misturas de bibliotecas e documentando os seus - resultados no espaço correspondente na Base de Dados de Aplicações, você vai - ajudar outros utilizadores do Wine a serem produtivos com essa aplicação, - assim tornando o Wine útil para um maior número de pessoas.

-

Habilidades necessárias:

- - -

Caça ao Bug e relatório

-

POrque há tantas aplicações Windows por aí, e porque muito poucas delas - funcionam perfeitamente, temos muitas questões de utilizadores, muitos - relatórios de bugs que necessitam de ser diagnosticados e depois muitos bugs - a corrigir.

-

Por isso o diagnóstico e suporte a bugs são duas actividades muito próximas - que são muito importantes para o Wine. Portanto precisamos de pessoas com - vontade de responder às questões e assuntos que surgem nos newsgroups, wine-users - e Bugzilla; e depois dár-lhes uma triagem:

- -

Ver também a página Projecto Wine QA - do Dan Kegel para uma introdução passo-a-passo para novos voluntários de - Wine QA.

-

Habilidades necessárias:

- - -

Desenvolvimento

- -

Algumas tarefas de desenvolvimento

- -

Testes de Conformidade

- -

O objectivo dos testes de conformidade do Wine é ter a certeza de que o - comportamento das APIs do Wine é conforme o das APIs Windows. Como há muitas - versões do Windows desde o 95 ao XP precisamos de pessoas que escrevam os - testes assim como voluntários para correr o teste no Windows. A suite de testes - está longe de completa mas todos os bocadinhos ajudam.

- -

Habilidades necessárias:

- - -

Documentação das funções das APIs Windows

- -

A principal razão é que assim que a MS avança para novas APIs tende - a remover a documentação das antigas (e.g. Win 3.1). O objectivo é - escrever uma documentação independente das APIs Windows. Dado que estamos a - reimplementar todas estas APIs seria uma boa prática de codificação também - documentar aquilo que implementamos. Devíamos concentrar-nos particularmente - em aspectos que não estão muito bem cobertos pela documentação 'oficial' tais - como discrepâncias com a documentação oficial, bugs, especificidades das plataformas, - e todas essas coisas que não estão tipicamente bem cobertas como o que acontece - se passarmos um ponteiro NULL, se o buffer for pequeno demais, ... Sem uma - documentação desse género novos programadores não têm maneira de saber se um - comportamento estranho numa implementação é insignificante ou é realmente uma - característica (ou defeito) em que alguns programas confiam. À medida que o - Wine amadurece problemas desses tornam-se mais e mais importantes.

-

Habilidades necessárias:

- - -

Portabilizar as suas aplicações Windows para o Wine

- -

Se está a trabalhar numa aplicação Windows, portabilizá-la para o Wine pode - ser a melhor maneira de iniciar uma contribuição de código para o Wine. Pode - começar por tentar corrê-la no Wine e depois tentar compilá-la no Wine.A razão - pela qual eu sugiro começar com uma aplicação em que normalmente trabalha, é - que em primeiro lugar tem obviamente acesso ao código fonte e em segundo, - sendo o programador dela, sabe como a aplicação funciona. Para além disso pode - atacar o problema dos dois lados: fazer um rastreio tanto na sua aplicação - como no Wine. Tudo isto em conjunto torna mais fácil detectar onde é que o Wine - está a fazer algo de errado, o quê e porquê. Depois, dado que já sabe o que o - Wine é suposto fazer, está numa posição melhor para providenciar uma correcção. - Pode também testar exemplos de livros de programação no Wine. Um kit para se - iniciar e criar páginas Web a mostrar os seus resultados está disponível - aqui.

-

Habilidades necessárias:

- - -

Efectuar uma revisão ao código

- -

Uma revisão de código 'aleatória' regular pode ser bastante aborrecida e - ineficiente. Mas penso que se estiver a procurar algo específico pode ser uma - forma produtiva de encontrar e corrigir bugs. Tipicamente inicia-se por escolher - um objectivo. Por exemplo uma vez eu encontrei código que usava o strncpy sem - ter a certeza de que a string resultante terminava em '\0'. Normalmente corrige-se - esse pedaço de código e segue em frente. Mas quantos bugs semelhantes e difíceis - de encontrar é que restavam noutras partes? E então decidi verificar todas as - chamadas ao strncpy. Isto demora algum tempo e portanto não pode estar sempre - a ser feito (deixe-me uma mensagem se pensar em algum bug específico a procurar - e não tiver tempo para isso). Mas é uma maneira simpática de se familiarizar - com o código e pode realmente encontrar bugs sem precisar de meses de experiência - no código do Wine.

-

Mas fica avisado que dado que as suas mudanças ficam espalhadas por todo o Wine - elas serão escrutinadas por muitos programadores. Para além disso dado que as - suas alterações não são provavelmente correcções de bugs directas pode haver - resistência (com fundamento). Tenha a certeza de que as suas alterações são - realmente correcções, não algo que vai esconder o problema debaixo do tapete - (especialmente em avisos de compilação). Também as correcções cosméticas, - desnecessárias, não são geralmente bem vindas (mas eu admito que algumas vezes - são difíceis de resistir).

-

Aqui estão alguns pontos de arranque:

- -

Habilidades necessárias:

- - -

Vários

- -

Escrita da Documentação

- -

O Wine está constantemente a necessitar de actualizações à documentação. - O Wine tem os seus "Guias" tais como - o Wine User Guide etc. O código fonte SGML pode ser encontrado numa - árvore Git à parte.

-

Outros items de documentação importantes são o ficheiro README, as páginas - man e outros ficheiros no directório de documentação.

-

O seu trabalho seria certificar-se de que a cada correcção que um programador - submete que altera o comportamento da configuração do Wine de qualquer modo - seja documentada devidamente o mais rápido possível. Isto seria feito testando - a nova funcionalidade e opcionalmente perguntando ao programador o que é que o - seu patch faz realmente (e claro não se esqueça de bater em programadores que - não documentam nada do funcionamento dos seus patchs!).

-

As actualizações à documentação seriam efectuadas enviando "diffs git" dos - ficheiros relevantes para o wine-patches.

-

Requisitos:

- - -

Trabalho de tradução

- -

Também precisamos de versões traduzidas dos Guias do Wine e páginas man. - Para isso funcionar, precisamos de muitas pessoas com vontade de traduzir - alterações à documentação principal em Inglês para outras línguas. Se - estiver interessado em fazer trabalho numa certa língua, então por favor - junte-se a nós!

-

Actualmente estamos a procura de pessoas que possam traduzir:

- -

Nós também precisamos de um 'QuickStart/Howto' que descreva as instruções básicas - para instalar e configurar o Wine com um bocado mais de detalhe que o README - mas sendo mais pequeno que o Wine User Guide (pode até ser um capítulo desse Guia). - Depois esse documento poderá ser traduzido para múltiplas línguas o que faria - mais fácil pelo menos para pessoas que não falam inglês a instalação do Wine.

-

Requisitos:

- - -

Relações Públicas

- -

Actualmente não temos quase nenhuma gestão de Relações Públicas. - Isto deve mudar para melhor.

-

Actualmente quase a única forma de RP é "pregar ao coro", dado que temos - artigos em sites de TI (mas a maioria é Linux apenas!). Devíamos ter maior - cobertura em sites Windows tradicionais, mas mais importante, em jornais de - papel, para iluminar o grande público também conhecido por The Great Unwashed Masses!

-

Assim este trabalho envolveria escrever artigos para serem apresentados em - jornais de pequena e grande escala e também em publicações online.

-

Requisitos:

- - -

Fundo de Desenvolvimento do Wine

- -

O propósito do Fundo de Desenvolvimento do Wine é mostrar apreço aos programadores - Wine colectando fundos para reuniões de desenvolvimento, tais como a WineConf, - ou em alguns casos para comprar documentação.

- -

A organização que regula actualmente as nossas doações é a -Software Freedom Conservancy. - Se tiver alguma questão ou precisar de mais esclarecimentos por favor visite - o site da SFC.

- -

A Software Freedom Conservancy é uma organização 501(c)(3), e donativos feitos - através dela são deduzíveis em impostos dentro do permitido por lei.

-

Maneiras de contribuir:

-
-
- - - - Nossa conta PayPal -
-
- -

Pode também enviar dinheiro, cheques ou ordens de câmbio internacionais em - fundos dos Estados Unidos para:

-
Wine Project -Software Freedom Conservancy -1995 Broadway FL 17 -New York, NY 10023-5882
-- 1.7.9.5