[Debtags-commits] [svn] r2214 - in web/trunk: . js
Enrico Zini
enrico at alioth.debian.org
Wed Dec 20 16:13:24 CET 2006
Author: enrico
Date: Wed Dec 20 16:13:24 2006
New Revision: 2214
Modified:
web/trunk/edit-tips.html
web/trunk/edit.html
web/trunk/js/tips.js
Log:
Updated editing tips. Thanks to Justin B Rye
Modified: web/trunk/edit-tips.html
==============================================================================
--- web/trunk/edit-tips.html (original)
+++ web/trunk/edit-tips.html Wed Dec 20 16:13:24 2006
@@ -26,7 +26,7 @@
<ul>
<li>
- <p><i>Short of ideas? Let the tag search suggest you.</i></p>
+ <p><i>Short of ideas? Let the tag search give you a hint.</i></p>
<p>If you want to represent a concept but you do not know how, choose "Tag
search" and try looking for that concept just like you would look for it on
Google. In many cases you will get a useful tag suggestion for it.
@@ -34,17 +34,17 @@
</li>
<li>
<p><i>Every package should have a role.</i></p>
- <p>Contrarily to most other facets in Debtags, the Role facet is designed to
- be applicable to all packages in Debian.</p>
+ <p>Contrary to most other facets in Debtags, the Role facet is designed to be
+ applicable to all packages in Debian.</p>
<p>Try to find a suitable role for the package you are tagging. If you think
that there is no applicable role, use the tag <tt>role::TODO</tt> to mark a
possible gap in the tag vocabulary.
</p>
</li>
<li>
- <p><i>Every software should be implemented in one or more languages.</i></p>
+ <p><i>Every piece of software should be implemented in one or more languages.</i></p>
<p>For all software in Debian, there should be an <tt>implemented-in::*</tt>
- tag that applies to most of its code. However, tt is often hard to know what
+ tag that applies to most of its code. However, it is often hard to know what
<tt>implemented-in::*</tt> tag to use without looking at the source of a
package.</p>
<p>If you are the maintainer of the package, or have looked at its source
@@ -54,14 +54,14 @@
</li>
<li>
<p><i><tt>devel::lang:*</tt> and <tt>implemented-in::*</tt> are different.</i></p>
- <p>Take perl, for example: it's <tt>devel::lang:perl</tt>, but it is
+ <p>Take lua5.1, for example: it's <tt>devel::lang:lua</tt>, but it is
<tt>implemented-in::c</tt>.</p>
</li>
<li>
<p><i>If the name is similar, the tags may not be.</i></p>
<p>Take for example <tt>k3b</tt> and <tt>k3b-i18n</tt>: the former package
- contain a very good software to create CDs and DVDs. The latter package does
- not contain software, but data files containing translated strings.</p>
+ contains a very good application to create CDs and DVDs. The latter package
+ does not contain software, but data files containing translated strings.</p>
<p><tt>role::app-data</tt> is a good tag for <tt>k3b-i18n</tt>. You should
not tag <tt>k3b-i18n</tt> as <tt>x11::application</tt>, because it does not
contain any X11 application.</p>
@@ -77,10 +77,9 @@
<p>Most of the data packages in Debian are things like arch-independent support
packages for arch-dependent software, which one normally would not want to
see as the result of a package search.</p>
- <p>There are non-software packages in Debian to create a new set of
- categories. For those few other packages, like anarchism, bible-kjv-text,
- c++-annotations, cfi-en, diveintopython, hwb, newbyedoc, use
- <tt>role::data</tt>.</p>
+ <p>There are some data packages in Debian that don't fit the category of
+ "application data". For those few other packages, like anarchism,
+ bible-kjv-text, or cfi-en, use <tt>role::data</tt>.</p>
</li>
<li><p><i>culture::* tags are for culture-specific packages.</i></p>
<p>Use <tt>culture::*</tt> tags to mark only those packages that are
Modified: web/trunk/edit.html
==============================================================================
--- web/trunk/edit.html (original)
+++ web/trunk/edit.html Wed Dec 20 16:13:24 2006
@@ -1,6 +1,8 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html lang="en">
<!-- TODO:
+ http://www.alistapart.com/articles/userproofingajax
+
give some per-facet intro when a facet is selected
< h01ger> and make a developer-view, with all packages per developer and show a graph per developer :)
@@ -19,6 +21,9 @@
Get maintainer/comaintainer package list from
http://qa.debian.org/data/ddpo/results/ddpo_maintainers, where # indicates a
comaintained package.
+
+ tag -> facet hints
+ proper FAQ
-->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Modified: web/trunk/js/tips.js
==============================================================================
--- web/trunk/js/tips.js (original)
+++ web/trunk/js/tips.js Wed Dec 20 16:13:24 2006
@@ -1,9 +1,9 @@
var tips = [
-"<p><i>Short of ideas? Let the tag search suggest you.</i></p><p>If you want to represent a concept but you do not know how, choose \"Tag\n search\" and try looking for that concept just like you would look for it on\n Google. In many cases you will get a useful tag suggestion for it.\n </p>",
-"<p><i>Every package should have a role.</i></p><p>Contrarily to most other facets in Debtags, the Role facet is designed to\n be applicable to all packages in Debian.</p><p>Try to find a suitable role for the package you are tagging. If you think\n that there is no applicable role, use the tag <tt>role::TODO</tt> to mark a\n possible gap in the tag vocabulary.\n </p>",
-"<p><i>Every software should be implemented in one or more languages.</i></p><p>For all software in Debian, there should be an <tt>implemented-in::*</tt>\n tag that applies to most of its code. However, tt is often hard to know what\n <tt>implemented-in::*</tt> tag to use without looking at the source of a\n package.</p><p>If you are the maintainer of the package, or have looked at its source\n code before, then please take some time to choose an\n <tt>implemented-in::*</tt> tag for it: it is a quick and easy task for you,\n but hard for many others.</p>",
-"<p><i><tt>devel::lang:*</tt> and <tt>implemented-in::*</tt> are different.</i></p><p>Take perl, for example: it's <tt>devel::lang:perl</tt>, but it is\n <tt>implemented-in::c</tt>.</p>",
-"<p><i>If the name is similar, the tags may not be.</i></p><p>Take for example <tt>k3b</tt> and <tt>k3b-i18n</tt>: the former package\n contain a very good software to create CDs and DVDs. The latter package does\n not contain software, but data files containing translated strings.</p><p><tt>role::app-data</tt> is a good tag for <tt>k3b-i18n</tt>. You should\n not tag <tt>k3b-i18n</tt> as <tt>x11::application</tt>, because it does not\n contain any X11 application.</p><p>The same idea usually applies to those packages that end with\n <tt>-data</tt>, <tt>-common</tt> and <tt>-sound</tt>. Shared libraries and\n <tt>-dev</tt> packages have similar names, but very different use: think\n <tt>libc6</tt> and <tt>libc6-dev</tt>.</p>",
-"<p><i>Data packages need very few tags.</i></p><p>Debtags does not provide many categories for <tt>role::app-data</tt>\n packages besides <tt>role::app-data</tt> and sometimes a <tt>made-of::*</tt>\n tag. The reason is because Debian is mainly distributing software.</p><p>Most of the data packages in Debian are things like arch-independent support\n packages for arch-dependent software, which one normally would not want to\n see as the result of a package search.</p><p>There are non-software packages in Debian to create a new set of\n categories. For those few other packages, like anarchism, bible-kjv-text,\n c++-annotations, cfi-en, diveintopython, hwb, newbyedoc, use\n <tt>role::data</tt>.</p>",
+"<p><i>Short of ideas? Let the tag search give you a hint.</i></p><p>If you want to represent a concept but you do not know how, choose \"Tag\n search\" and try looking for that concept just like you would look for it on\n Google. In many cases you will get a useful tag suggestion for it.\n </p>",
+"<p><i>Every package should have a role.</i></p><p>Contrary to most other facets in Debtags, the Role facet is designed to be\n applicable to all packages in Debian.</p><p>Try to find a suitable role for the package you are tagging. If you think\n that there is no applicable role, use the tag <tt>role::TODO</tt> to mark a\n possible gap in the tag vocabulary.\n </p>",
+"<p><i>Every piece of software should be implemented in one or more languages.</i></p><p>For all software in Debian, there should be an <tt>implemented-in::*</tt>\n tag that applies to most of its code. However, it is often hard to know what\n <tt>implemented-in::*</tt> tag to use without looking at the source of a\n package.</p><p>If you are the maintainer of the package, or have looked at its source\n code before, then please take some time to choose an\n <tt>implemented-in::*</tt> tag for it: it is a quick and easy task for you,\n but hard for many others.</p>",
+"<p><i><tt>devel::lang:*</tt> and <tt>implemented-in::*</tt> are different.</i></p><p>Take lua5.1, for example: it's <tt>devel::lang:lua</tt>, but it is\n <tt>implemented-in::c</tt>.</p>",
+"<p><i>If the name is similar, the tags may not be.</i></p><p>Take for example <tt>k3b</tt> and <tt>k3b-i18n</tt>: the former package\n contains a very good application to create CDs and DVDs. The latter package\n does not contain software, but data files containing translated strings.</p><p><tt>role::app-data</tt> is a good tag for <tt>k3b-i18n</tt>. You should\n not tag <tt>k3b-i18n</tt> as <tt>x11::application</tt>, because it does not\n contain any X11 application.</p><p>The same idea usually applies to those packages that end with\n <tt>-data</tt>, <tt>-common</tt> and <tt>-sound</tt>. Shared libraries and\n <tt>-dev</tt> packages have similar names, but very different use: think\n <tt>libc6</tt> and <tt>libc6-dev</tt>.</p>",
+"<p><i>Data packages need very few tags.</i></p><p>Debtags does not provide many categories for <tt>role::app-data</tt>\n packages besides <tt>role::app-data</tt> and sometimes a <tt>made-of::*</tt>\n tag. The reason is because Debian is mainly distributing software.</p><p>Most of the data packages in Debian are things like arch-independent support\n packages for arch-dependent software, which one normally would not want to\n see as the result of a package search.</p><p>There are some data packages in Debian that don't fit the category of\n \"application data\". For those few other packages, like anarchism,\n bible-kjv-text, or cfi-en, use <tt>role::data</tt>.</p>",
"<p><i>culture::* tags are for culture-specific packages.</i></p><p>Use <tt>culture::*</tt> tags to mark only those packages that are\n especially useful to people who are part of a specific culture.</p><p>Do not use <tt>culture::*</tt> tags to mark that a package (like\n <tt>b2evolution</tt>) has been translated into some languages: if the tags\n were used that way, with time all applications in Debian would have all\n <tt>culture::*</tt> tags, and the <tt>culture::*</tt> tags would become\n useless.</p><p>However, do use <tt>culture::*</tt> tags for packages that only provide\n localisation, like <tt>openoffice.org-l10n-it</tt>: they do provide\n special support for a specific culture.</p>"
];
More information about the Debtags-commits
mailing list