[WINEHQ] Removed references to obsolete bugzilla keywords: tasklet, tasklist
Alexandru Băluț
alexandru.balut at gmail.com
Thu Jun 10 03:22:11 CDT 2010
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winehq.org/pipermail/wine-patches/attachments/20100610/a401ec16/attachment.htm>
-------------- next part --------------
From ce608421f31f4db7046aac53448a1a0a7422e49d Mon Sep 17 00:00:00 2001
From: Alex Balut <alexandru.balut at gmail.com>
Date: Thu, 10 Jun 2010 09:57:25 +0200
Subject: Removed references to obsolete bugzilla keywords: tasklet, tasklist
---
templates/de/contributing.template | 64 ------------------------------------
templates/en/contributing.template | 58 --------------------------------
templates/en/status/todo.template | 2 -
templates/pt/contributing.template | 28 ----------------
4 files changed, 0 insertions(+), 152 deletions(-)
diff --git a/templates/de/contributing.template b/templates/de/contributing.template
index fd4ee1d..ff3333d 100644
--- a/templates/de/contributing.template
+++ b/templates/de/contributing.template
@@ -148,70 +148,6 @@
<p>Der vollständige Implementierungsstatus kann auf der
<a href="{$root}/site/status">Wine Status Seite</a> überprüft werden.</p>
-<p>In der folgenden Liste kannst Du eine Entwicklungsaufgabe finden:</p>
-<ul>
- <li id="tasklets"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&keywords=tasklet&keywords_type=anywords">Aufgäbchen (en)</a>:
- Diese Liste umfasst Aufgaben, die einen genau umrissenen und
- begrenzten Umfang haben. Wenn Du neu bei Wine dabei bist oder nur
- begrenzt Zeit hast, ist diese Liste für Dich. Die Aufgaben in dieser
- Liste haben meistens mit Fehlerbehebungen zu tun, die nur wenige
- Funktionen betreffen, implementieren einige neue und angemessen
- einfache APIs, oder implementieren einfache Erweiterungen eines
- bestehenden APIs. Einige können einen größeren
- Umfang haben, sind dann aber in kleinere Einheiten aufgeteilt,
- so dass Du einzelne Einheiten umsetzen kannst, und trotzdem am Ende etwas
- hast, was submitted werden kann. Einige Aufgaben verlangen Wissen,
- das nichts mit Wine zu tun hat. Zum Beispiel kann eine Aufgabe
- 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="tasklist"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&keywords=tasklist&keywords_type=anywords">Aufgaben (en)</a>:
- Hier sind die größeren Entwicklungsaufgaben aufgeführt.
- Guck hier nach, wenn du an einem der größeren /
- längerfristigen Projekte beteiligt sein willst. Fehler, die hier
- aufgeführt werden, haben die folgenden Eigenschaften:
- <ul>
- <li>sie betreffen eher Neuentwicklungen (z.B. neue Funktionalität,
- signifikante Umstrukturierung existierender Funktionalität
- oder neue Treiber für Sound/Video/usw.) als einfache
- Fehlerbehebungen wie oben beschrieben</li>
- <li>sie sind relativ gut definiert, zumindest was die erwartete
- Funktionalität betrifft, eventuell auch bezüglich der
- Implementierungsdetails</li>
- <li>sie beinhalten normalerweise eine Erklärung, warum diese
- Entwicklung gewünscht ist</li>
- </ul>
- </li>
-<!-- [Maik] the following two sections seem obsolete -->
-<!--
- <li id="wine_1_x"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&target_milestone=1.0.0&order=bugs.bug_severity">Wine 1.x</a> task overviews:
- Regroups the issues that need to be resolved before Wine 1.0 can
- be released. One word about Wine 1.0: Wine 1.0 does not mean that
- Wine will run all Windows applications. It means that:
- <ul>
- <li>Wine is ready for use by the general public for selected
- applications (that set will be determined by what Wine supports,
- not the other way around)</li>
- <li>Applications based on an old version of Wine/Wine lib will
- work with a new version of the Wine server</li>
- <li>The stable branches of Wine should not suffer major
- regressions. An application that works in 1.0.x should work in
- 1.0.y if y>x.</li>
- </ul>
- </li>
- <li>Wine 0.9.0 is the first step towards these goals:
- <ul>
- <li>When the items in this list have been completed, we release
- 0.9.0</li>
- <li>at this point we should be ready to have increased user
- participation for using, testing and documenting Wine</li>
- <li>During 0.9.1, 0.9.2, etc. we do a progressive code freeze</li>
- <li>Then when everything is frozen we release 1.0</li>
- <li>After 1.0.0 we will have stable and unstable branches</li>
- </ul>
- </li>
--->
-</ul>
<h3 id="conf_tests">Konformitätstests</h3>
diff --git a/templates/en/contributing.template b/templates/en/contributing.template
index ed69567..0f9d81e 100644
--- a/templates/en/contributing.template
+++ b/templates/en/contributing.template
@@ -131,64 +131,6 @@
<p>The overall implementation status of Wine can be checked on the
<a href="{$root}/site/status">Wine Status page</a>.</p>
-<p>See the following task lists to find a development task:</p>
-<ul>
- <li id="tasklets"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&keywords=tasklet&keywords_type=anywords">Tasklets</a>:
- This list regroups tasks that have a well-defined and limited
- scope. If you are new to Wine or only have a limited amount of time,
- this list is meant for you. Tasks on this list typically
- involve fixing bugs that only touch on a couple of functions,
- implementing a couple new reasonably simple APIs or simple
- extensions to an existing API. Some may have a wider scope but
- would then be composed of smaller chunks so that you can tackle
- only one chunk and still have something that can be submitted.
- 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="tasklist"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&keywords=tasklist&keywords_type=anywords">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 /
- longer-term projects. Bugs placed in this list have the following
- characteristics:
- <ul>
- <li>they concern new development (e.g. new functionality, significant
- restructuring of existing functionality or new drivers for
- sound/video/etc.) rather than simply bug fixes of the types
- found in the previous lists</li>
- <li>they are reasonably well-defined, at least in the
- functionality to be provided if not in the implementation details</li>
- <li>normally include a rational for why such development is desirable</li>
- </ul>
- </li>
-<!-- the following two sections are obsolete
- <li id="wine_1_x"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&target_milestone=1.0.0&order=bugs.bug_severity">Wine 1.x</a> task overviews:
- Regroups the issues that need to be resolved before Wine 1.0 can
- be released. One word about Wine 1.0: Wine 1.0 does not mean that
- Wine will run all Windows applications. It means that:
- <ul>
- <li>Wine is ready for use by the general public for selected
- applications (that set will be determined by what Wine supports,
- not the other way around)</li>
- <li>Applications based on an old version of Wine/Wine lib will
- work with a new version of the Wine server</li>
- <li>The stable branches of Wine should not suffer major
- regressions. An application that works in 1.0.x should work in
- 1.0.y if y>x.</li>
- </ul>
- </li>
- <li>Wine 0.9.0 is the first step towards these goals:
- <ul>
- <li>When the items in this list have been completed, we release
- 0.9.0</li>
- <li>at this point we should be ready to have increased user
- participation for using, testing and documenting Wine</li>
- <li>During 0.9.1, 0.9.2, etc. we do a progressive code freeze</li>
- <li>Then when everything is frozen we release 1.0</li>
- <li>After 1.0.0 we will have stable and unstable branches</li>
- </ul>
- </li>
--->
-</ul>
<h3 id="conf_tests">Conformance tests</h3>
diff --git a/templates/en/status/todo.template b/templates/en/status/todo.template
index b71563b..828fc1f 100644
--- a/templates/en/status/todo.template
+++ b/templates/en/status/todo.template
@@ -284,6 +284,4 @@ avicap32: "Video Capture"
</ul>
<br>
-For the full 1.0 Bug List, please see <a href="http://bugs.winehq.com/buglist.cgi?keywords=tasklist">Tasklist</a>
-
<p> </p>
diff --git a/templates/pt/contributing.template b/templates/pt/contributing.template
index c947031..baaf979 100644
--- a/templates/pt/contributing.template
+++ b/templates/pt/contributing.template
@@ -138,34 +138,6 @@
<p>O estado geral da implementação do Wine pode ser verificado na página
<a href="{$root}/site/status">Wine Status</a>.</p>
-<p>Veja a seguinte lista de tarefas para encontrar uma tarefa de desenvolvimento:</p>
-<ul>
- <li id="tasklets"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&keywords=tasklet&keywords_type=anywords">Tasklets</a>:
- Esta lista agrupa tarefas que têm um âmbito bem definido e limitado.
- Se você é novo no Wine ou apenas tem algum tempo livre, esta lista é a indicada
- para si. Tarefas nesta lista envolvem tipicamente corrigir bugs que tocam
- apenas num par de funções, implementar umas poucas APIs simples ou extensões
- simples a uma API existente. Algumas podem abranger um pouco mais mas podem
- ser decompostas em bocados mais pequenos para que se possa abordar apenas
- um bocado e mesmo assim obter algo que pode ser submetido. Algumas tarefas
- 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="tasklist"><a href="http://bugs.winehq.org/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Wine&keywords=tasklist&keywords_type=anywords">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
- desta lista têm as seguintes características:
- <ul>
- <li>Eles necessitam de novo desenvolvimento (e.g. nova funcionalidade,
- reestruturação significativa de funcionalidade existente ou novos
- drivers para som, video, etc.) ao invés de simples arranjos dos encontrados
- nas listas anteriores.</li>
- <li>Estão razoavelmente bem definidos, pelo menos na funcionalidade a ser
- fornecida se não nos detalhes da implementação</li>
- <li>Normalmente incluem um raciocínio para tal desenvolvimento ser desejável</li>
- </ul>
- </li>
-</ul>
<h3 id="conf_tests">Testes de Conformidade</h3>
--
1.7.0.4
More information about the wine-patches
mailing list