Module: website
Branch: master
Commit: 19bf3e2df1bff2c6325a81c40f8f108cbc7e859b
URL: http://source.winehq.org/git/website.git/?a=commit;h=19bf3e2df1bff2c6325a81…
Author: Jeff Zaroyko <jeffzaroyko(a)gmail.com>
Date: Mon Jun 8 09:50:34 2009 -0500
website: remove section about bugzilla FIXME keyword indicating a tasklist, this keyword is discouraged/up for removal since nearly every application outputs fixmes.
---
templates/de/contributing.template | 9 ---------
templates/en/contributing.template | 8 --------
templates/pt/contributing.template | 7 -------
3 files changed, 0 insertions(+), 24 deletions(-)
diff --git a/templates/de/contributing.template b/templates/de/contributing.template
index 7c0ab2e..be57a75 100644
--- a/templates/de/contributing.template
+++ b/templates/de/contributing.template
@@ -165,15 +165,6 @@
verlangen, dass Du mit Lex/Yacc umgehen kannst. Falls du also
spezielles Domänenwissen hast, dann guck doch mal über
die Liste drüber.</li>
- <li id="FIXMEs"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&a…">FIXMEs (en)</a>:
- Diese Liste enthält Aufgaben, deren Komplexität zwischen
- den Aufgäbchen und den Aufgaben liegt. Die hier aufgeführten
- Probleme sind gut diagnostiziert; mit anderen Worten, wir wissen,
- welche Funktion oder Funktionalität fehlt oder fehlerhaft ist.
- Und auch wenn der Fehler nicht unbedingt einfach zu beheben ist,
- sollte trotzdem weder extensives Wissen über mehrere Bereiche
- von Wine noch eine umfängliche Reorganisation des Quellcodes
- von Wine vonnöten sein.</li>
<li id="tasklist"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&a…">Aufgaben (en)</a>:
Hier sind die größeren Entwicklungsaufgaben aufgeführt.
Guck hier nach, wenn du an einem der größeren /
diff --git a/templates/en/contributing.template b/templates/en/contributing.template
index 3aee073..a652f33 100644
--- a/templates/en/contributing.template
+++ b/templates/en/contributing.template
@@ -145,14 +145,6 @@
Some tasks also draw on non-Wine specific knowledge. For instance
a task may require being knowledgeable in Lex/Yacc so if you have
an expertise in a given domain you may want to scan it.</li>
- <li id="FIXMEs"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&a…">FIXMEs</a>:
- This list contains tasks that are intermediate between those found
- in the Task list and the Task lets. Issues found in this list are
- well diagnosed, that is, we know which function or functionality is
- missing / buggy. And while the fix may not be very easy to
- implement, it normally is not thought to require extensive
- knowledge of multiple areas of Wine, or extensive reorganization
- of the Wine code.</li>
<li id="tasklist"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&a…">Tasklist</a>:
The major development tasks are listed there. This is the place to
check out if you want to get involved in one of the larger /
diff --git a/templates/pt/contributing.template b/templates/pt/contributing.template
index ed61e56..4009d74 100644
--- a/templates/pt/contributing.template
+++ b/templates/pt/contributing.template
@@ -151,13 +151,6 @@
também se focam em conhecimento não específico do Wine. Por exemplo uma
tarefa pode necessitar que seja um conhecedor de Lex/Yacc, portanto se você
tem vasta experiência num certo domínio pode querer procurar por ele.</li>
- <li id="FIXMEs"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&a…">FIXMEs</a>:
- Esta lista contém tarefas que são intermédias entre a Task List e a Task lets.
- Assuntos encontrados nesta lista estão bem diagnosticados, isto é, sabe-se
- qual a função ou funcionalidade em falta / incompleta. E enquanto o arranjo
- possa não ser muito fácil de implementar, normalmente não é necessário um
- conhecimento de múltiplas áreas do Wine ou uma reorganização extensa do
- código Wine.</li>
<li id="tasklist"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&a…">Tasklist</a>:
As maiores tarefas de desenvolvimento estão listadas aqui. Este é o lugar a
visitar se se quer envolver num dos projectos maiores, a longo prazo. Bugs
Module: website
Branch: master
Commit: 86180f8d954647fdc6782fbb92448719d6ec9dcc
URL: http://source.winehq.org/git/website.git/?a=commit;h=86180f8d954647fdc6782f…
Author: Jeff Zaroyko <jeffzaroyko(a)gmail.com>
Date: Mon Jun 8 09:49:48 2009 -0500
website: fix capitalisation of GIT -> Git, consistent with usage on the Git homepage since it's not really an acronym
---
templates/de/devel.template | 2 +-
templates/en/cvs.template | 4 ++--
templates/en/devel.template | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/templates/de/devel.template b/templates/de/devel.template
index 087eba6..4957064 100644
--- a/templates/de/devel.template
+++ b/templates/de/devel.template
@@ -62,7 +62,7 @@ Hilfsmittel, die wir unseren Entwicklern zur Verfügung stellen.</p>
<tr bgcolor="#ffffff">
<td>
- <a href="http://wiki.winehq.org/GitWine">GIT</a>
+ <a href="http://wiki.winehq.org/GitWine">Git</a>
</td>
<td valign="top">
Wir nutzen Git zur Quellcodeverwaltung. Auf dieser Seite findest Du Informationen über den Umgang damit.
diff --git a/templates/en/cvs.template b/templates/en/cvs.template
index f742f86..358ba0b 100644
--- a/templates/en/cvs.template
+++ b/templates/en/cvs.template
@@ -3,8 +3,8 @@
<h1 class="title">The Wine CVS Tree</h1>
-<p><strong>Note: We are switching development from CVS to <a href="http://git.or.cz">Git</a>.
- Instructions for using the <a href="{$root}/site/git">Wine GIT tree</a>
+<p><strong>Note: We have switched development from CVS to <a href="http://git.or.cz">Git</a>.
+ Instructions for using the <a href="{$root}/site/git">Wine Git tree</a>
can be found on the <a href="http://wiki.winehq.org/GitWine">GitWine</a>
page on the <a href="http://wiki.winehq.org">Wine Wiki</a>.</strong></p>
diff --git a/templates/en/devel.template b/templates/en/devel.template
index 82b9f1d..ddb54a8 100644
--- a/templates/en/devel.template
+++ b/templates/en/devel.template
@@ -64,7 +64,7 @@ various resources available for our developers.</p>
<tr bgcolor="#ffffff">
<td>
- <a href="http://wiki.winehq.org/GitWine">GIT</a>
+ <a href="http://wiki.winehq.org/GitWine">Git</a>
</td>
<td valign="top">
We use the source management tool Git. More information on how to use it can be found on this page.
Module: website
Branch: master
Commit: 690d5fb3489022ac5a4405a1d4784fb39cdaeb76
URL: http://source.winehq.org/git/website.git/?a=commit;h=690d5fb3489022ac5a4405…
Author: Jeff Zaroyko <jeffzaroyko(a)gmail.com>
Date: Mon Jun 8 09:49:18 2009 -0500
website: mention bugzilla registration on sending_patches
---
templates/en/sending_patches.template | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/templates/en/sending_patches.template b/templates/en/sending_patches.template
index f185117..d4b2ac6 100644
--- a/templates/en/sending_patches.template
+++ b/templates/en/sending_patches.template
@@ -38,6 +38,8 @@ or anywhere else to the Git tree.)
<li>Use standard C, avoid C++ comments and inline variable declarations.
<li>Read the diff and make sure it contains only what you want in it.
+
+ <li>Register an account on the Wine bugzilla with the email address you use to send patches.
</ul>
<p>Accepted patches will appear in the <a href="{$root}/site/forums">wine-cvs</a> mailing list.