diff options
| author | Thomas Lange <lange@debian.org> | 2023-10-06 12:45:37 +0200 |
|---|---|---|
| committer | Thomas Lange <lange@debian.org> | 2023-10-06 12:45:37 +0200 |
| commit | 9f5b551837a8d4c6a8c9346cf4c44755b863a813 (patch) | |
| tree | 0856db540a5d047169c7b6513e04d38306bff237 /greek | |
| parent | 794834c196b3285bb39846e22bfab051860258ab (diff) | |
remove a lot of files which are not translations but only copies of the english version
Diffstat (limited to 'greek')
429 files changed, 0 insertions, 37487 deletions
diff --git a/greek/Bugs/Access.wml b/greek/Bugs/Access.wml deleted file mode 100644 index 2338be718f5..00000000000 --- a/greek/Bugs/Access.wml +++ /dev/null @@ -1,61 +0,0 @@ -#use wml::debian::template title="Debian BTS — access methods" NOHEADER=yes NOCOPYRIGHT=true -#use wml::debian::translation-check translation="24307c5e15886d4d81e4db3a68318d1824cca824" maintainer="galaxico" - -# the explicit links to https://bugs.debian.org/ without anchors are -# included because of the text version, do not remove them - -<h1>Methods of accessing the bug tracking system logs</h1> - -<h2>Accessing active bug reports</h2> - -<p>Each message received at or sent by the bug processing system is -logged and made available in a number of ways.</p> - -<p>The primary access method is to use the web pages. See the -forms on the <a href="./">main BTS page</a> at -<code>https://bugs.debian.org/</code></p> - -<p>There is a <a href="server-request">mailserver</a> which can send -bug reports as plain text on request. To use it send the word -<code>help</code> as the sole contents of an email to -<code>request@bugs.debian.org</code> (the <code>Subject</code> of the -message is ignored), or read the instructions <a href="server-request">on -the World Wide Web</a> or in the file <code>bug-log-mailserver.txt</code>.</p> - -<h2>Accessing archived bug reports</h2> - -<p>Each closed bug report is archived 28 days after the last message -relating to it is received and filed. This means that it is no longer -possible to access it or change anything about it using the -<code>control</code> and <code>service</code> bots. However, the -reports are still accessible for viewing.</p> - -<p>You can search the bug report archive using the <a href="./">WWW -forms</a> at <code>https://bugs.debian.org/</code>, simply select the -<q>archived bugs</q> option.</p> - -<p>Note that it doesn't contain the oldest closed bug reports, only those -after #40000, approximately.</p> - -<h2>Accessing the raw bug data</h2> - -<p>If you need to get hold of the raw data used by the bug tracking system, -you can mirror it using rsync from bugs-mirror.debian.org. The relevant -modules are bts-spool-db (for the active bug spool), bts-spool-archive (for -bugs that have been closed for a while and thus archived), and -bts-spool-index (for the bug index files).</p> - -<p>As of August 2020, the active spool is about 18GB and the archived -spool is about 105GB. If you only need a sample for testing purposes, please -consider downloading only part of the active spool rather than the whole -thing.</p> - -<p>Please do not rely on *.status files in the bug spools, as they are -obsolete, for compatibility purposes only, and will be removed at some point -in the future. Use the *.summary files instead.</p> - -<hr /> - -#use "otherpages.inc" - -#use "$(ENGLISHDIR)/Bugs/footer.inc" diff --git a/greek/Bugs/Developer.wml b/greek/Bugs/Developer.wml deleted file mode 100644 index 985e63c825d..00000000000 --- a/greek/Bugs/Developer.wml +++ /dev/null @@ -1,471 +0,0 @@ -#use wml::debian::template title="Debian BTS — developer info" NOHEADER=yes NOCOPYRIGHT=true -#include "$(ENGLISHDIR)/Bugs/pkgreport-opts.inc" -#use wml::debian::translation-check translation="40a57e26c62893be7c80d82f1772999f68d51179" maintainer="galaxico" - -<h1>Information regarding the bug processing system for package - maintainers and bug triagers</h1> - -<p>Initially, a bug report is submitted by a user as an ordinary mail -message to <code>submit@bugs.debian.org</code> which must include - a <code>Package</code> line (see <a href="Reporting">Bug Reporting - Instructions</a> for more information). This will then be -given a number, acknowledged to the user, and forwarded to -<code>debian-bugs-dist</code>. If the <code>Package</code> line contains a -package which has a known maintainer, -the maintainer will get a copy too.</p> - -<p>The <code>Subject</code> line will have -<code>Bug#</code><var>nnn</var><code>:</code> added, and the -<code>Reply-To</code> will be set to include both the submitter of the -report and <var>nnn</var><code>@bugs.debian.org</code>.</p> - -<ul class="toc"> - <li><a href="#closing">Closing bug reports</a></li> - <li><a href="#followup">Followup messages</a></li> - <li><a href="#severities">Severity levels</a></li> - <li><a href="#tags">Tags for bug reports</a></li> - <li><a href="#forward">Recording that you have passed on a bug report</a></li> - <li><a href="#owner">Changing bug ownership</a></li> - <li><a href="#maintincorrect">Incorrectly listed package maintainers</a></li> - <li><a href="#requestserv">Reopening, reassigning and manipulating bugs</a></li> - <li><a href="#subscribe">Subscribing to bugs</a></li> - <li><a href="#subjectscan">More-or-less obsolete subject-scanning feature</a></li> - <li><a href="#x-debian-pr">Obsolete <code>X-Debian-PR: quiet</code> feature</a></li> -</ul> - -<h2><a name="closing">Closing bug reports</a></h2> - -<p>Debian bug reports should be closed when the problem is fixed. Problems -in packages can only be considered fixed once a package that includes the -bug fix enters the Debian archive.</p> - -<p>Normally, the only people that should close a bug report are the -submitter of the bug and the maintainer(s) of the package against which the -bug is filed. There are exceptions to this rule, for example, the bugs filed -against unknown packages or certain generic pseudo-packages. A bug can also -be closed by any contributor if the bug is for an <strong>orphaned</strong> -package or if the maintainer of a package has missed closing it. It is very -important to mention the version in which the bug was fixed. When in doubt, -don't close bugs, first ask for advice on the debian-devel mailing list.</p> - -<p>Bug reports should be closed by sending email to -<var>nnn</var><code>-done@bugs.debian.org</code>. The message body -needs to contain an explanation of how the bug was fixed.</p> - -<p>With the emails received from the bug tracking system, all you need -to do to close the bug is to make a Reply in your mail reader program -and edit the <code>To</code> field to say -<var>nnn</var><code>-done@bugs.debian.org</code> instead of -<var>nnn</var><code>@bugs.debian.org</code> -(<var>nnn</var><code>-close</code> is provided as an alias for -<var>nnn</var><code>-done</code>).</p> - -<p>Where applicable, please supply a <code>Version</code> line in the -<a href="Reporting#pseudoheader">pseudo-header</a> of your message when -closing a bug, so that the bug tracking system knows which releases of the -package contain the fix.</p> - -<p>The person closing the bug, the person who submitted it and the -<code>debian-bugs-closed</code> mailing list will each get a notification -about the change in status of the report. The submitter and the mailing list -will also receive the contents of the message sent to -<var>nnn</var><code>-done</code>.</p> - - -<h2><a name="followup">Followup messages</a></h2> - -<p>The bug tracking system will include the submitter's address and the bug -address (<var>nnn</var><code>@bugs.debian.org</code>) in the <code>Reply-To</code> -header after forwarding the bug report. Please note that these are two -distinct addresses.</p> - -<p> -Any developer wishing to reply to a bug report should simply reply -to the message, respecting the <code>Reply-To</code> header. This will -<strong>not</strong> close the bug.</p> - -<p>Do <em>not</em> use the <q>reply to all recipients</q> or <q>followup</q> -feature of your mailer unless you intend to edit down the recipients -substantially. In particular, see that you don't send followup messages -to <code>submit@bugs.debian.org</code>.</p> - -<p> -Messages can be sent to the following addresses -in order to be filed in the bug tracking system: -</p> - -<ul> -<li> -<var>nnn</var><code>@bugs.debian.org</code> — such messages are also sent -to the package maintainer and forwarded to <code>debian-bugs-dist</code>, -but <strong>not</strong> to the submitter; -</li> -<li> -<var>nnn</var><code>-submitter@bugs.debian.org</code> — these are also sent -to the submitter and forwarded to <code>debian-bugs-dist</code>, -but <strong>not</strong> to the package maintainer; -</li> -<li> -<var>nnn</var><code>-maintonly@bugs.debian.org</code> — these are only sent -to the package maintainer, <strong>not</strong> to the submitter -or <code>debian-bugs-dist</code>; -</li> -<li> -<var>nnn</var><code>-quiet@bugs.debian.org</code> — these are only -filed in the bug tracking system (as are all the above), -<strong>not</strong> sent to anyone else. -</li> -</ul> - -<p>For more information about headers to suppress ACK messages and how -to send carbon copies using the Bug Tracking System, see the -<a href="Reporting">instructions for reporting bugs</a>.</p> - - -<h2><a name="severities">Severity levels</a></h2> - -<p>The bug system records a severity level with each bug report. This is -set to <code>normal</code> by default, but can be overridden either by -supplying a <code>Severity</code> line in the pseudo-header when the -bug is submitted (see the -<a href="Reporting#pseudoheader">instructions for reporting -bugs</a>), or by using the <code>severity</code> command with the -<a href="#requestserv">control request server</a>.</p> - -<p>The severity levels are:</p> - -<dl> -<dt><code>critical</code></dt> -<dd>makes unrelated software on the system (or the whole system) -break, or causes serious data loss, or introduces a security hole on -systems where you install the package.</dd> - -<dt><code>grave</code></dt> -<dd>makes the package in question unusable or mostly so, or causes -data loss, or introduces a security hole allowing access to the -accounts of users who use the package.</dd> - -<dt><code>serious</code></dt> -<dd>is a <a href="$(DOC)/debian-policy/">severe -violation of Debian policy</a> (roughly, it violates a <q>must</q> or <q>required</q> -directive), or, in the package maintainer's or release manager's opinion, makes the package -unsuitable for release.</dd> - -<dt><code>important</code></dt> -<dd>a bug which has a major effect on the usability of a package, without -rendering it completely unusable to everyone.</dd> - -<dt><code>normal</code></dt> -<dd>the default value, applicable to most bugs.</dd> - -<dt><code>minor</code></dt> -<dd>a problem which doesn't affect the package's usefulness, and is -presumably trivial to fix.</dd> - -<dt><code>wishlist</code></dt> -<dd>for any feature request, and also for any bugs that are -very difficult to fix due to major design considerations.</dd> -</dl> - -<p>Certain severities are considered -<em><a href="https://bugs.debian.org/release-critical/">release-critical</a></em>, -meaning the bug will have an impact on releasing the package with the -stable release of Debian. Currently, these are <strong>critical</strong>, -<strong>grave</strong> and <strong>serious</strong>. For complete and -canonical rules on what issues merit these severities, see the list of -<a href="https://release.debian.org/testing/rc_policy.txt">release-critical -issues for the next release</a>.</p> - -<h2><a name="tags">Tags for bug reports</a></h2> - -<p>Each bug can have zero or more of a set of given tags. These tags are -displayed in the list of bugs when you look at a package's page, and when -you look at the full bug log.</p> - -<p>Tags can be set by supplying a <code>Tags</code> line in the -pseudo-header when the bug is submitted (see the -<a href="Reporting#pseudoheader">instructions for reporting bugs</a>), -or by using the <code>tags</code> command with the -<a href="#requestserv">control request server</a>. -Separate multiple tags with commas, spaces, or both.</p> - -<p>The current bug tags are: <bts_tags>. Here is some detailed info -about the tags:</p> - -<dl> - -<dt><code>patch</code></dt> - <dd>A patch or some other easy procedure for fixing the bug is included in - the bug logs. If there's a patch, but it doesn't resolve the bug - adequately or causes some other problems, this tag should not be used.</dd> - -<dt><code>wontfix</code></dt> - <dd>This bug won't be fixed. Possibly because this is a choice between two - arbitrary ways of doing things and the maintainer and submitter prefer - different ways of doing things, possibly because changing the behaviour - will cause other, worse, problems for others, or possibly for other - reasons.</dd> - -<dt><code>moreinfo</code></dt> - <dd>This bug can't be addressed until more information is provided by the - submitter. The bug will be closed if the submitter doesn't provide more - information in a reasonable (few months) timeframe. This is for bugs like - <q>It doesn't work</q>. What doesn't work?</dd> - -<dt><code>unreproducible</code></dt> - <dd>This bug can't be reproduced on the maintainer's system. Assistance - from third parties is needed in diagnosing the cause of the problem.</dd> - -<dt><code>help</code></dt> -<dd>The maintainer is requesting help with dealing with this bug. - Either the maintainer does not have the skills necessary to fix this - bug and desires collaboration, or is overloaded and wants to - delegate this task. This bug might not be suitable for new - contributors unless it is also tagged with the <code>newcomer</code> - tag.</dd> - -<dt><code>newcomer</code></dt> - <dd>This bug has a known solution but the maintainer requests - someone else implement it. This is an ideal task for new - contributors who wish to get involved in Debian, or who wish to - improve their skills.</dd> - -<dt><code>pending</code></dt> - <dd>A solution to this bug has been found and an upload will be made soon.</dd> - -<dt><code>fixed</code></dt> - <dd>This bug is fixed or worked around (by a non-maintainer upload, for - example), but there's still an issue that needs to be resolved. This tag - replaces the old <q>fixed</q> severity.</dd> - -<dt><code>security</code></dt> - <dd>This bug describes a security problem in a package (e.g., bad - permissions allowing access to data that shouldn't be accessible; buffer - overruns allowing people to control a system in ways they shouldn't be - able to; denial of service attacks that should be fixed, etc). Most - security bugs should also be set at critical or grave severity.</dd> - -<dt><code>upstream</code></dt> - <dd>This bug applies to the upstream part of the package.</dd> - -<dt><code>confirmed</code></dt> - <dd>The maintainer has looked at, understands, and basically agrees with - the bug, but has yet to fix it. (Use of this tag is optional; it is - intended mostly for maintainers who need to manage large numbers of open - bugs.)</dd> - -<dt><code>fixed-upstream</code></dt> - <dd>The bug has been fixed by the upstream maintainer, but not yet in the - package (for whatever reason: perhaps it is too complicated to backport - the change or too minor to be worth bothering).</dd> - -<dt><code>fixed-in-experimental</code></dt> - <dd>The bug has been fixed in the package of the experimental - distribution, but not yet in the unstable distribution.</dd> - -<dt><code>d-i</code></dt> - <dd>This bug is relevant to the development of debian-installer. It is - expected that this will be used when the bug affects installer development - but is not filed against a package that forms a direct part of the - installer itself.</dd> - -<dt><code>ipv6</code></dt> - <dd>This bug affects support for Internet Protocol version 6.</dd> - -<dt><code>lfs</code></dt> - <dd>This bug affects support for large files (over 2 gigabytes).</dd> - -<dt><code>l10n</code></dt> - <dd>This bug is relevant to the localisation of the package.</dd> - -<dt><code>a11y</code></dt> - <dd>This bug affects accessibility for users with disabilities. It - particularly impacts usability by people who rely on assistive (or - other adaptive) technology to use the system/package.</dd> - -<dt><code>ftbfs</code></dt> - <dd>The package fails to build from source. If the bug is assigned to a - source package, that package fails to build. If the bug is assigned - to a binary package, the affected source packages fail to build. The - tag is applicable to non-standard build environments (e.g. using - Build-Depends from experimental), but the severity should be below - serious (release critical) in such cases.</dd> - -<dt><bts_release_tags></dt> - <dd>These are release tags, which have two effects. When set on a bug, - the bug can only affect the particular release (though it may also affect - other releases if other release tags are set) but otherwise normal - buggy/fixed/absent rules apply. The bug also should not be - archived until it is fixed in the release.</dd> - -<dt><bts_release_ignore_tags></dt> - <dd>This release-critical bug is to be ignored for the purposes of - releasing the particular release. <strong>These tags should only be used by the release - manager(s); do not set it yourself without explicit authorization from - them.</strong></dd> - -</dl> - -<p>Some info on distribution-specific tags: - the -ignore tags ignore the bug for the purposes - of testing propagation. The release tags indicate that the bug in - question should not be archived until it is fixed in the set of - releases specified. The release tags also indicate that a bug should - only be considered buggy in the set of releases specified. [In other - words, the bug is <strong>absent</strong> in any release whose - corresponding release tag is <strong>not</strong> set if any release - tags are set; otherwise the normal found/fixed rules apply.] -</p> - -<p> - Release tags should <strong>not</strong> be used if proper - versioning of the bug would achieve the desired effect, as they - require manual addition and removal. If you are unsure if a release - tag is required, contact the Debian BTS Administrators - (<email "owner@bugs.debian.org">) or the release team for advice. -</p> - -<h2><a name="forward">Recording that you have passed on a bug report</a></h2> - -<p>When a developer forwards a bug report to the developer of the -upstream source package from which the Debian package is derived, -they should note this in the bug tracking system as follows:</p> - -<p>Make sure that the <code>To</code> field of your message to the author -has only the author(s) address(es) in it; put the person who -reported the bug, -<var>nnn</var><code>-forwarded@bugs.debian.org</code> -and <var>nnn</var><code>@bugs.debian.org</code> in the -<code>CC</code> field.</p> - -<p>Ask the author to preserve the <code>CC</code> to -<var>nnn</var><code>-forwarded@bugs.debian.org</code> when they reply, so that -the bug tracking system will file their reply with the original -report. These messages are only filed and are not sent on; to send a -message as normal, send them -to <var>nnn</var><code>@bugs.debian.org</code> as well.</p> - -<p>When the bug tracking system gets a message at -<var>nnn</var><code>-forwarded</code> it will mark the relevant bug as -having been forwarded to the address(es) in the <code>To</code> field -of the message it gets, if the bug is not already marked as forwarded.</p> - -<p>You can also manipulate the <q>forwarded to</q> information by sending -messages to <a href="server-control"><code>control@bugs.debian.org</code></a>.</p> - - -<h2><a name="owner">Changing bug ownership</a></h2> - -<p>In cases where the person responsible for fixing a bug is not the -assigned maintainer for the associated package (for example, when the -package is maintained by a team), it may be useful to record this fact -in the bug tracking system. To help with this, each bug may -optionally have an owner.</p> - -<p>The owner can be set by supplying an <code>Owner</code> line in the -pseudo-header when the bug is submitted (see the -<a href="Reporting#pseudoheader">instructions for reporting bugs</a>), -or by using the <code>owner</code> and <code>noowner</code> commands -with the <a href="#requestserv">control request server</a>.</p> - - -<h2><a name="maintincorrect">Incorrectly listed package maintainers</a></h2> - -<p>If the maintainer of a package is listed incorrectly, this is -usually because the maintainer has changed recently, and the new -maintainer hasn't yet uploaded a new version of the package with a -changed <code>Maintainer</code> control file field. This will be -fixed when the package is uploaded; alternatively, the archive maintainers -can override the maintainer record of a package manually, for example if -a rebuild and reupload of the package is not expected to be needed soon. -Contact <code>override-change@debian.org</code> for changes to the -override file.</p> - - -<h2><a name="requestserv">Reopening, reassigning and manipulating bugs</a></h2> - -<p>It is possible to reassign bug reports to other packages, to reopen -erroneously-closed ones, to modify the information saying to where, if -anywhere, a bug report has been forwarded, to change the severities -and titles of reports, to set the ownership of bugs, to merge and unmerge -bug reports, and to record the versions of packages in which bugs were -found and in which they were fixed. This is done by sending mail to -<code>control@bugs.debian.org</code>.</p> - -<p>The <a href="server-control">format of these messages</a> is -described in another document available on the World Wide Web or in -the file <code>bug-maint-mailcontrol.txt</code>. A plain text version -can also be obtained by mailing the word <code>help</code> to the -server at the address above.</p> - -<h2><a name="subscribe">Subscribing to bugs</a></h2> - -<p>The bug tracking system also allows bug submitters, developers and other -interested third parties to subscribe to individual bugs. This feature can be -used by those wishing to keep an eye on a bug, without having to subscribe to a -package through the <a href="https://tracker.debian.org">Debian Package -Tracker</a>. All messages that are received at -<var>nnn</var><code>@bugs.debian.org</code>, are sent to subscribers.</p> - -<p>Subscribing to a bug can be done by sending an email to -<var>nnn</var><code>-subscribe@bugs.debian.org</code>. The subject and body of -the email are ignored by the BTS. Once this message is processed, users are -sent a confirmation message that they will need to reply to before they are -sent the messages relating to that bug.</p> - -<p>It is also possible to unsubscribe from a bug. Unsubscribing can be done by -sending an email to <var>nnn</var><code>-unsubscribe@bugs.debian.org</code>. The -subject and body of the email are again ignored by the BTS. Users will be sent -a confirmation message which they must reply to if they wish to be unsubscribed -from the bug.</p> - -<p>By default, the address subscribed is the one found in the <code>From</code> -header. If you wish to subscribe another address to a bug, you will need to -encode the address to be subscribed into the subscription message. This takes the form of: -<var>nnn</var><code>-subscribe-</code>\ -<var>localpart</var><code>=</code>\ -<var>example.com</var><code>@bugs.debian.org</code>. -That example would send <code>localpart@example.com</code> a subscription message -for bug <var>nnn</var>. The <code>@</code> sign must be encoded by changing it -to an <code>=</code> sign. Similarly, an unsubscription takes the form -<var>nnn</var><code>-unsubscribe-</code><var>localpart</var>\ -<code>=</code><var>example.com</var><code>@bugs.debian.org</code>. -In both cases, the subject and body of the email will be forwarded to the email -address within the request for confirmation.</p> - -<h2><a name="subjectscan">More-or-less obsolete subject-scanning feature</a></h2> - -<p>Messages that arrive at <code>submit</code> or <code>bugs</code> whose -Subject starts <code>Bug#</code><var>nnn</var> will be treated as -having been sent to <var>nnn</var><code>@bugs.debian.org</code>. This is both -for backwards compatibility with mail forwarded from the old -addresses, and to catch followup mail sent to <code>submit</code> by -mistake (for example, by using reply to all recipients).</p> - -<p>A similar scheme operates for <code>maintonly</code>, -<code>done</code>, <code>quiet</code> and <code>forwarded</code>, -which treat mail arriving with a Subject tag as having been sent to -the corresponding <var>nnn-whatever</var><code>@bugs.debian.org</code> address.</p> - -<p>Messages arriving at plain <code>forwarded</code> and -<code>done</code> — ie, with no bug report number in the address — and -without a bug number in the Subject will be filed under <q>junk</q> and -kept for a few weeks, but otherwise ignored.</p> - - -<h2><a name="x-debian-pr">Obsolete <code>X-Debian-PR: quiet</code> feature</a></h2> - -<p>It used to be possible to prevent the bug tracking system from -forwarding anywhere messages it received at <code>debian-bugs</code>, -by putting an <code>X-Debian-PR: quiet</code> line in the actual mail -header.</p> - -<p>This header line is now ignored. Instead, send your message to -<code>quiet</code> or <var>nnn</var><code>-quiet</code> (or -<code>maintonly</code> or <var>nnn</var><code>-maintonly</code>).</p> - -<hr /> - -#use "otherpages.inc" - -#use "$(ENGLISHDIR)/Bugs/footer.inc" diff --git a/greek/Bugs/Reporting.wml b/greek/Bugs/Reporting.wml deleted file mode 100644 index 693ccbbe8fa..00000000000 --- a/greek/Bugs/Reporting.wml +++ /dev/null @@ -1,518 +0,0 @@ -#use wml::debian::template title="Debian BTS - reporting bugs" NOHEADER=yes NOCOPYRIGHT=true -#use wml::debian::translation-check translation="387a1b1ba7d55da8110abcaf96b5711187791f78" maintainer="galaxico" - -<h1>How to report a bug in Debian using reportbug</h1> - -<a name="reportbug"></a> -<p>We strongly recommend that you report bugs in Debian using the -<code><a -href="https://packages.debian.org/stable/utils/reportbug">reportbug</a></code> -program.</p> - -<p> -reportbug is installed by default on most systems. -If it is not available, it can be installed using the -package management tool available on your system. -</p> - -<p> -reportbug can be started from the system section of the menu or -by running <code>reportbug</code> via the command-line. -</p> - -<p>It will guide you through the bug reporting process step by step.</p> - -<p>If you have questions that the interactive prompts of reportbug do -not resolve, you can refer to the rest of the documentation below or ask the <a -href="mailto:debian-user@lists.debian.org"> Debian user mailing -list</a>.</p> - - -<h1> How to report a bug in Debian using email - (and advanced usage of reportbug)</h1> - -<h2>Important things to note <strong>before</strong> sending your bug -report</h2> - -<a name="whatpackage"></a> -<h3>What package does your bug report belong to?</h3> -<p>You need to know what package your bug report should be filed -against. See <a href="#findpkgver">this example</a> for -information on how to find this information. (You will use this -information to <a href="#filedalready">see if your bug report -has been filed already.</a>) -</p> - -<p>If you are unable to determine which package your bug report should -be filed against, -please send e-mail to the <a href="mailto:debian-user@lists.debian.org"> -Debian user mailing list</a> asking for advice.</p> - -<p>If your problem doesn't -relate just to one package but some general Debian service, there are -several <a href="pseudo-packages">pseudo-packages</a> or even -<a href="../MailingLists/">mailing lists</a> that you can use -to relay your message to us instead.</p> - -<a name="filedalready"></a> -<h3>Has your bug report been filed already?</h3> -<p>You should check to see if your bug report has already been filed -before submitting it. You can see which bugs have been filed in -a specific package using the -<a href="./#pkgreport">package option of the bug search form</a>. -If there is an existing bug report #<var><number></var>, -you should submit your comments by sending e-mail to -<var><number></var>@bugs.debian.org instead of reporting a -new bug.</p> - -<h3>Send multiple reports for multiple bugs</h3> -<p>Please don't report multiple unrelated bugs — especially ones in -different packages — in a single bug report.</p> - -<h3>Don't file bugs upstream</h3> -<p>If you file a bug in Debian, don't send a copy to the upstream software -maintainers yourself, as it is possible that the bug exists only in -Debian. If necessary, the maintainer of the package will forward the -bug upstream.</p> - -<h2>Sending the bug report via e-mail</h2> - -<p>You can report bugs in Debian by sending an e-mail to -<a href="mailto:submit@bugs.debian.org"><code>submit@bugs.debian.org</code></a> -with a special format described below. <code>reportbug</code> (<a -href="#reportbug">see above</a>) will properly format the e-mails for you; -please use it!</p> - -<h3>Headers</h3> -<p>Like any e-mail you should include a clear, descriptive -<code>Subject</code> line in your main mail header. The subject you -give will be used as the initial bug title in the tracking system, so -please try to make it informative!</p> - -<p>If you'd like to send a copy of your bug report to additional recipients -(such as mailing lists), you shouldn't use the usual e-mail headers, but -<a href="#xcc">a different method, described below</a>.</p> - -<h3><a name="pseudoheader">Pseudo-headers</a></h3> -<p>The first part of the bug report are the pseudo-headers which contain -information about what package and version your bug report applies to. -The first line of the message body has to include a pseudo-header. -It should say:</p> - -<pre> -Package: <packagename> -</pre> - -<p>Replace <code><packagename></code> with the <a href="#whatpackage">name of the package</a> which -has the bug.</p> - -<p>The second line of the message should say:</p> - -<pre> -Version: <packageversion> -</pre> - -<p>Replace <code><packageversion></code> with the version of the package. -Please don't include any text here other than the version itself, as the -bug tracking system relies on this field to work out which releases are -affected by the bug.</p> - -<p>You need to supply a correct <code>Package</code> line in the -pseudo-header in order for the bug tracking system to deliver the message -to the package's maintainer. See <a href="#findpkgver">this example</a> for -information on how to find this information.</p> - -<p>For other valid pseudo-headers, see <a -href="#additionalpseudoheaders">Additional pseudo-headers</a></p> - -<h3>The body of the report</h3> -<p>Please include in your report:</p> - -<ul> -<li>The <em>exact</em> and <em>complete</em> text of any error -messages printed or logged. This is very important!</li> -<li>Exactly what you typed or did to demonstrate the problem.</li> -<li>A description of the incorrect behavior: exactly what behavior -you were expecting, and what you observed. A transcript of an -example session is a good way of showing this.</li> -<li>A suggested fix, or even a patch, if you have one.</li> -<li>Details of the configuration of the program with the problem. -Include the complete text of its configuration files.</li> -<li>The versions of any packages on which the buggy package depends.</li> -<li>What kernel version you're using (type <code>uname -a</code>), your -shared C library (type <code>ls -l /lib/*/libc.so.6</code> or -<code>apt show libc6 | grep ^Version</code>), and any other details about -your Debian system, if it seems appropriate. For example, if you had a -problem with a Perl script, you would want to provide the version of the -`perl' binary (type <code>perl -v</code> or <code>dpkg -s perl | grep -^Version:</code>).</li> -<li>Appropriate details of the hardware in your system. If you're -reporting a problem with a device driver please list <em>all</em> the -hardware in your system, as problems are often caused by IRQ and I/O -address conflicts.</li> -<li>If you have <a -href="https://packages.debian.org/stable/utils/reportbug">reportbug</a> - installed the output of - <code>reportbug --template -T none -s none -S normal -b --list-cc - none -q <package></code> -will also be useful, as it contains the output of maintainer specific -scripts and version information.</li> -</ul> - -<p>Include any detail that seems relevant — you are in very little danger -of making your report too long by including too much information. If -they are small, please include in your report any files you were using -to reproduce the problem. (If they are large, consider making them -available on a publicly available website if possible.)</p> - -<p>For more advice on how to help the developers solve your problem, -please read <a href="https://www.chiark.greenend.org.uk/~sgtatham/bugs.html"> -How to Report Bugs Effectively</a>.</p> - - -<h2><a name="example">An Example Bug Report</a></h2> - -<p>A bug report with header and pseudo-header looks something like this:</p> - -<pre> - To: submit@bugs.debian.org - From: diligent@testing.linux.org - Subject: Hello says `goodbye' - - Package: hello - Version: 1.3-16 - - When I invoke `hello' without arguments from an ordinary shell - prompt it prints `goodbye', rather than the expected `hello, world'. - Here is a transcript: - - $ hello - goodbye - $ /usr/bin/hello - goodbye - $ - - I suggest that the output string, in hello.c, be corrected. - - I am using Debian GNU/Linux 2.2, kernel 2.2.17-pre-patch-13 - and libc6 2.1.3-10. -</pre> - - -<h2><a name="xcc">Sending copies of bug reports to other addresses</a></h2> - -<p>Sometimes it is necessary to send a copy of a bug report to somewhere -else besides <code>debian-bugs-dist</code> and the package maintainer, -which is where they are normally sent.</p> - -<p>You could do this by CC'ing your bug report to the other address(es), -but then the other copies would not have the bug report number put in -the <code>Reply-To</code> field and the <code>Subject</code> line. -When the recipients reply they will probably preserve the -<code>submit@bugs.debian.org</code> entry in the header and have their -message filed as a new bug report. This leads to many duplicated -reports.</p> - -<p>The <em>right</em> way to do this is to use the -<code>X-Debbugs-CC</code> header. Add a line like this to your -message's mail header:</p> -<pre> - X-Debbugs-CC: other-list@cosmic.edu -</pre> -<p>This will cause the bug tracking system to send a copy of your report -to the address(es) in the <code>X-Debbugs-CC</code> line as well as to -<code>debian-bugs-dist</code>.</p> - -<p>If you want to send copies to more than one address, add them -comma-separated in only one <code>X-Debbugs-CC</code> line.</p> - -<p>Avoid sending such copies to the addresses of other bug reports, as -they will be caught by the checks that prevent mail loops. There is -relatively little point in using <code>X-Debbugs-CC</code> for this -anyway, as the bug number added by that mechanism will just be replaced -by a new one; use an ordinary <code>CC</code> header instead.</p> - -<p>This feature can often be combined usefully with mailing -<code>quiet</code> — see below.</p> - -<a name="additionalpseudoheaders"></a> -<h1>Additional Pseudoheaders</h1> - -<h2><a name="severities">Severity levels</a></h2> - -<p>If a report is of a particularly serious bug, or is merely a feature -request, you can set the severity level of the bug as you report -it. This is not required however, and the package maintainer will assign an -appropriate severity level to your report even if you do not (or pick -the wrong severity).</p> - -<p>To assign a severity level, put a line like this one in the -<a href="#pseudoheader">pseudo-header</a>:</p> - -<pre> -Severity: <<var>severity</var>> -</pre> - -<p>Replace <<var>severity</var>> with one of the available severity -levels, as described in the -<a href="Developer#severities">advanced documentation</a>.</p> - -<h2><a name="tags">Assigning tags</a></h2> - -<p>You can set tags on a bug as you are reporting it. For example, if -you are including a patch with your bug report, you may wish to set the -<code>patch</code> tag. This is not required, however, and the developers -will set tags on your report as and when it is appropriate.</p> - -<p>To set tags, put a line like this one in the -<a href="#pseudoheader">pseudo-header</a>:</p> - -<pre> -Tags: <<var>tags</var>> -</pre> - -<p>Replace <<var>tags</var>> with one or more of the available tags, -as described in the -<a href="Developer#tags">advanced documentation</a>. -Separate multiple tags with commas, spaces, or both.</p> - -<pre> -User: <<var>username</var>> -Usertags: <<var>usertags</var>> -</pre> - -<p>Replace <<var>usertags</var>> with one or more usertags. -Separate multiple tags with commas, spaces, or both. If you specify a -<<var>username</var>>, that user's tags will be set. Otherwise, -the e-mail address of the sender will be used as the username.</p> - -<p>You can set usertags for multiple users at bug submission time by -including multiple User pseudo-headers; each Usertags pseudo-header -sets the usertags for the preceding User pseudo-header. This is especially -useful for setting usertags for a team with multiple users, setting -usertags for multiple teams, or setting the -<a href="https://wiki.debian.org/Teams/Debbugs/ArchitectureTags">architecture usertags</a> -for bugs affecting multiple architectures. -</p> - -<pre> -User: <<var>first-username</var>> -Usertags: <<var>first-username usertags</var>> -User: <<var>second-username</var>> -Usertags: <<var>second-username usertags</var>> -</pre> - -<h2>Setting Forwarded</h2> -<pre> -Forwarded: <var>foo@example.com</var> -</pre> - -<p> -will mark the newly submitted bug as forwarded to foo@example.com. See -<a href="Developer#forward">Recording that you have passed on a bug -report</a> in the developers' documentation for details. -</p> - -<h2>Claiming ownership</h2> -<pre> -Owner: <var>foo@example.com</var> -</pre> - -<p> -will indicate that foo@example.com is now responsible for fixing this -bug. See <a href="Developer#owner">Changing bug ownership</a> in the -developers' documentation for details. -</p> - -<h2>Source Package</h2> -<pre> -Source: <var>foopackage</var> -</pre> - -<p> -the equivalent of <code>Package:</code> for bugs present in the source -package of foopackage; for most bugs in most packages you don't want -to use this option. -</p> - -<h2><a name="control">Control Commands</a></h2> -<pre> -Control: <var>control commands</var> -</pre> - -<p> -Allows for any of the commands which must be sent to -<code>control@bugs.debian.org</code> to work when sent to <code>submit@bugs.debian.org</code> or -<code>nnn@bugs.debian.org</code>. -1 initially refers to the current - bug (that is, the bug created by a mail to submit@ or the bug - messaged with nnn@). Please see <a href="server-control">the - server control documentation</a> for more information on the - control commands which are valid.</p> - -<p>For example, the following pseudoheader in a message sent - to <code>12345@bugs.debian.org</code>:</p> - -<pre> -Control: retitle -1 this is the title -Control: severity -1 normal -Control: summary -1 0 -Control: forwarded -1 https://bugs.debian.org/nnn -</pre> - -<p>would cause 12345 to be retitled, its severity changed, summary set, -and marked as forwarded.</p> - - - -<h2>X-Debbugs- headers</h2> -<p>Finally, if your -<acronym title="Mail User Agent" lang="en">MUA</acronym> -doesn't allow you to edit the headers, you can -set the various <code>X-Debbugs-</code> headers in the -<a href="#pseudoheader">pseudo-headers</a>.</p> - - -<h1>Additional information</h1> - -<h2>Different submission addresses (minor or mass bug reports)</h2> - -<p>If a bug report is minor, for example, a documentation typo or a trivial -build problem, please adjust the severity appropriately and send it to -<code>maintonly@bugs.debian.org</code> instead of <code>submit@bugs.debian.org</code>. -<code>maintonly</code> will forward the report to the package maintainer -only, it won't forward it to the BTS mailing lists.</p> - -<p>If you're submitting many reports at once, you should definitely use -<code>maintonly@bugs.debian.org</code> so that you don't cause too much redundant -traffic on the BTS mailing lists. Before submitting many similar bugs you -may also want to post a summary on <code>debian-bugs-dist</code>.</p> - -<p>If wish to report a bug to the bug tracking system that's already been -sent to the maintainer, you can use <code>quiet@bugs.debian.org</code>. Bugs sent to -<code>quiet@bugs.debian.org</code> will not be forwarded anywhere, only filed.</p> - -<p>When you use different submission addresses, the bug tracking system will -set the <code>Reply-To</code> of any forwarded message so that the replies -will by default be processed in the same way as the original report. That -means that, for example, replies to <code>maintonly</code> will go to -<var>nnn</var><code>-maintonly@bugs.debian.org</code> instead of -<var>nnn</var><code>@bugs.debian.org</code>, unless of course one overrides this -manually.</p> - - -<h2>Acknowledgements</h2> - -<p>Normally, the bug tracking system will return an acknowledgement to you -by e-mail when you report a new bug or submit additional information to an -existing bug. If you want to suppress this acknowledgement, include an -<code>X-Debbugs-No-Ack</code> header or pseudoheader in your e-mail -(the contents of this header do not matter). If you report a new bug -with this header, you will need to check the web interface yourself to -find the bug number.</p> - -<p>Note that this header will not suppress acknowledgements from the -<code>control@bugs.debian.org</code> mailserver, since those acknowledgements may -contain error messages which should be read and acted upon.</p> - -<h2>Spamfighting and missing mail</h2> - -<p>The bug tracking system implements a rather extensive set of rules - designed to make sure that spam does not make it through the BTS. - While we try to minimize the number of false positives, they do - occur. If you suspect your mail has triggered a false positive, feel - free to contact <code>owner@bugs.debian.org</code> for assistance. - Another common cause of mail not making it through to the BTS is - utilizing addresses which match procmail's FROM_DAEMON, which - includes mail from addresses like <code>mail@foobar.com</code>. If - you suspect your mail matches FROM_DAEMON, - see <a href="https://manpages.debian.org/cgi-bin/man.cgi?query=procmailrc">procmailrc(5)</a> - to verify, and then resend the mail using an address which does not - match FROM_DAEMON.</p> - - -<h2>Bug reports against unknown packages</h2> - -<p>If the bug tracking system doesn't know who the maintainer of the -relevant package is it will forward the report to -<code>debian-bugs-dist</code> even if <code>maintonly</code> was used.</p> - -<p>When sending to <code>maintonly@bugs.debian.org</code> or -<var>nnn</var><code>-maintonly@bugs.debian.org</code> you should make sure that -the bug report is assigned to the right package, by putting a correct -<code>Package</code> at the top of an original submission of a report, -or by using <A href="server-control">the -<code>control@bugs.debian.org</code> service</A> to (re)assign the report -appropriately.</p> - - -<h2><a name="findpkgver">Using <code>dpkg</code> to find the package and -version for the report</a></h2> - -<p>When using <code>reportbug</code> to report a bug in a command, say -<code>grep</code>, the following will automatically select the right package -and let you write the report right away: <code>reportbug --file $(which -grep)</code></p> - -<p>You can also find out which package installed it by using <code>dpkg ---search</code>. You can find out which version of a package you have -installed by using <code>dpkg --list</code> or <code>dpkg --status</code>. -</p> - -<p>For example:</p> -<pre> -$ which apt-get -/usr/bin/apt-get -$ type apt-get -apt-get is /usr/bin/apt-get -$ dpkg --search /usr/bin/apt-get -apt: /usr/bin/apt-get -$ dpkg --list apt -Desired=Unknown/Install/Remove/Purge/Hold -| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed -|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) -||/ Name Version Description -+++-==============-==============-============================================ -ii apt 0.3.19 Advanced front-end for dpkg -$ dpkg --status apt -Package: apt -Status: install ok installed -Priority: standard -Section: base -Installed-Size: 1391 -Maintainer: APT Development Team <deity@lists.debian.org> -Version: 0.3.19 -Replaces: deity, libapt-pkg-doc (<< 0.3.7), libapt-pkg-dev (<< 0.3.7) -Provides: libapt-pkg2.7 -Depends: libapt-pkg2.7, libc6 (>= 2.1.2), libstdc++2.10 -Suggests: dpkg-dev -Conflicts: deity -Description: Advanced front-end for dpkg - This is Debian's next generation front-end for the dpkg package manager. - It provides the apt-get utility and APT dselect method that provides a - simpler, safer way to install and upgrade packages. - . - APT features complete installation ordering, multiple source capability - and several other unique features, see the Users Guide in - /usr/doc/apt/guide.text.gz - -</pre> - -<a name="otherusefulcommands"></a> -<h2>Other useful commands and packages</h2> - -<p> -The <kbd>querybts</kbd> tool, available from the same package as -<a href="https://packages.debian.org/stable/utils/reportbug">reportbug</a>, -provides a convenient text-based interface to the bug tracking system.</p> - -<p>Emacs users can also use the debian-bug command provided by the -<code><a href="https://packages.debian.org/stable/utils/debian-el">\ -debian-el</a></code> package. When called with <kbd>M-x -debian-bug</kbd>, it will ask for all necessary information in a -similar way to <code>reportbug</code>.</p> - -<hr /> - -#use "otherpages.inc" - -#use "$(ENGLISHDIR)/Bugs/footer.inc" diff --git a/greek/Bugs/otherpages.inc b/greek/Bugs/otherpages.inc deleted file mode 100644 index 0254c44ac18..00000000000 --- a/greek/Bugs/otherpages.inc +++ /dev/null @@ -1,18 +0,0 @@ -<p>Other BTS pages:</p> - -<ul> - <li><a href="./">Bug tracking system main contents page.</a></li> - <li><a href="Reporting">Instructions for reporting bugs.</a></li> - <li><a href="Access">Accessing the bug tracking system logs.</a></li> - <li><a href="Developer">Information for developers on the bug tracking - system.</a></li> - <li><a href="server-control">Developers' information on manipulation - of bugs using the e-mail control interface.</a></li> - <li><a href="server-refcard">Mailservers' reference card.</a></li> - <li><a href="server-request">Requesting bug reports by e-mail.</a></li> -# <li><a href="db/ix/full.html">Full list of outstanding and recent bug -# reports.</a></li> -# <li><a href="db/ix/packages.html">Packages with bug reports.</a></li> -# <li><a href="db/ix/maintainers.html">Maintainers of packages with bug -# reports.</a></li> -</ul> diff --git a/greek/Bugs/pseudo-packages.wml b/greek/Bugs/pseudo-packages.wml deleted file mode 100644 index f2b5f05c05f..00000000000 --- a/greek/Bugs/pseudo-packages.wml +++ /dev/null @@ -1,25 +0,0 @@ -#use wml::debian::template title="Debian BTS - pseudo-packages" NOHEADER="true" NOCOPYRIGHT=true -#use wml::debian::translation-check translation="482085cdd7ca98a1a3142933dbb60ab68c4c36e5" maintainer="galaxico" - -<H1>Debian bug tracking system pseudo-packages</H1> - -<p>This page lists the pseudo-packages available for use in the -<code>Package:</code> line in bug reports. - -<p>See the <a href="Reporting">instructions for reporting a bug</a> for -details of how to specify a <code>Package:</code> line. - -<hrline> - -# Translators: to get translated descriptions create a file -# $yourlang/Bugs/pseudo-packages.translated-description -# See http://cvs.debian.org/webwml/polish/Bugs/pseudo-packages.translated-description?rev=1.1&cvsroot=webwml&content-type=text/vnd.viewcvs-markup -# for the format - -#use "$(ENGLISHDIR)/Bugs/pseudo-packages.inc" - -<hrline> - -#use "otherpages.inc" - -#use "$(ENGLISHDIR)/Bugs/footer.inc" diff --git a/greek/Bugs/server-control.wml b/greek/Bugs/server-control.wml deleted file mode 100644 index 431d195c24a..00000000000 --- a/greek/Bugs/server-control.wml +++ /dev/null @@ -1,751 +0,0 @@ -#use wml::debian::template title="Debian BTS — control server" NOHEADER=yes NOCOPYRIGHT=true -#include "$(ENGLISHDIR)/Bugs/pkgreport-opts.inc" -#use wml::debian::translation-check translation="d11193e66dd678156a1f8aa4c02b5ec7ae7eb116" maintainer="galaxico" - -<h1>Introduction to the bug control and manipulation mailserver</h1> - -<p> -Just as <code>request@bugs.debian.org</code> allows the <a -href="server-request">retrieval of bug data and documentation by -email</a>, <code>control@bugs.debian.org</code> allows bug reports to -be manipulated in various ways. -</p> - -<p> -The control server works just like the request server, except that it -has some additional commands; in fact, it's the same program. The two -addresses are only separated to avoid users making mistakes and -causing problems while merely trying to request information. -</p> - -<p> -Since the commands specific to the control server actually change -the status of a bug, a notification about processing the commands is -sent to the maintainer of the package(s) the changed bugs are assigned -to. Additionally the mail to the server and the resulting changes are -logged in the bug report and thereby available in the WWW pages. -</p> - -<p> -Please see the -<a href="server-request#introduction">introduction to the request server</a> -available on the World Wide Web, in the file -<code>bug-log-mailserver.txt</code>, or by sending -<code>help</code> to either mailserver, for details of the basics of -operating the mailservers and the common commands available when -mailing either address. -</p> - -<p> -The <a href="server-refcard">reference card</a> for the -mailservers is available via the WWW, in -<code>bug-mailserver-refcard.txt</code> or by email using the -<code>refcard</code> command. -</p> - - -<h1>Commands available at the control mailserver</h1> - - <table style="margin-left:auto;margin-right:auto"> - <tr> - <td align="center">General</td> - <td align="center">Versioning</td> - <td align="center">Duplicates</td> - <td align="center">Misc.</td> - </tr> - <tr> - <!-- General --> - <td valign="top"> - <ul class="nodecoration"> - <li><a href="#reassign">reassign</a></li> - <li><a href="#severity">severity</a></li> - <li><a href="#tag">tags</a></li> - <li><a href="#retitle">retitle</a></li> - <li><a href="#submitter">submitter</a></li> - <li><a href="#affects">affects</a></li> - <li><a href="#summary">summary</a></li> - <li><a href="#outlook">outlook</a></li> - </ul> - </td> - <!-- Versioning --> - <td valign="top"> - <ul class="nodecoration"> - <li><a href="#found">found</a> | <a href="#notfound">notfound</a></li> - <li><a href="#fixed">fixed</a> | <a href="#notfixed">notfixed</a></li> - <li><a href="#reopen">reopen</a></li> - <!-- <dt>(close)</dt> Deprecated --> - </ul> - </td> - <!-- Duplicates --> - <td valign="top"> - <ul class="nodecoration"> - <li><a href="#merge">merge</a> | <a href="#unmerge">unmerge</a></li> - <li><a href="#forcemerge">forcemerge</a></li> - <li><a href="#clone">clone</a></li> - </ul> - </td> - <!-- Misc. --> - <td valign="top"> - <ul class="nodecoration"> - <li><a href="#thanks">thanks</a></li> - <li><a href="#comment">#</a></li> - <li><a href="#forwarded">forwarded</a> | <a href="#notforwarded">notforwarded</a></li> - <li><a href="#owner">owner</a> | <a href="#noowner">noowner</a></li> - <li><a href="#block">block</a> | <a href="#unblock">unblock</a></li> - <li><a href="#archive">archive</a> | <a href="#unarchive">unarchive</a></li> - <li><a href="server-request#user">user</a> | - <a href="server-request#usertag">usertag</a> | - <a href="server-request#usercategory">usercategory</a></li> - </ul> - </td> - </tr> - </table> - -<dl> - <dt><a name="reassign"><code>reassign</code> <var>bugnumber</var> - <var>package</var> [ <var>version</var> ]</a></dt> - <dd> - <p> - Records that bug #<var>bugnumber</var> is a bug in <var>package</var>. - This can be used to set the package if the user forgot the - pseudo-header, or to change an earlier assignment. No notifications - are sent to anyone (other than the usual information in the processing - transcript). - </p> - - <p> - If you supply a <var>version</var>, the bug tracking system will note - that the bug affects that version of the newly-assigned package. - </p> - <p> - You can assign a bug to two packages at once by separating the - package names with a comma. <em>However</em>, you should only do - this if the bug can be fixed by a change to <em>either</em> - package. If this is not the case, you - should <a href="#clone">clone</a> the bug and reassign the clone - to the other package. - </p> - </dd> - - - <dt><a name="reopen"><code>reopen</code> <var>bugnumber</var> - [ <var>originator-address</var> | <code>=</code> | <code>!</code> ]</a></dt> - <dd> - <p> - Reopens #<var>bugnumber</var> and clears all fixed versions if it is closed. - </p> - - <p> - By default, or if you specify <code>=</code>, the original submitter is - still as the originator of the report, so that they will get the ack - when it is closed again. - </p> - - <p> - If you supply an <var>originator-address</var> the originator will be - set to the address you supply. If you wish to become the new - originator of the reopened report you can use the <code>!</code> - shorthand or specify your own email address. - </p> - - <p> - It is usually a good idea to tell the person who is about to be - recorded as the originator that you're reopening the report, so that - they will know to expect the ack which they'll get when it is closed - again. - </p> - - <p> - If the bug is not closed then reopen won't do anything, not even - change the originator. To change the originator of an open bug report, - use the <code>submitter</code> command; note that this will inform the - original submitter of the change. - </p> - - <p> - If the bug was recorded as being closed in a particular version of a - package but recurred in a later version, it is better to use the - <code>found</code> command instead. - </p> - </dd> - - - <dt><a name="found"><code>found</code> <var>bugnumber</var> [ - <var>version</var> ]</a></dt> - <dd> - <p> - Record that #<var>bugnumber</var> has been encountered in the given - <var>version</var> of the package to which it is assigned. - <var>version</var> may be a fully qualified version, - of the form <var>sourcepackagename/version</var>. - </p> - - <p> - The bug tracking system uses this information, in conjunction with - fixed versions recorded when closing bugs, to display lists of bugs - open in various versions of each package. It considers a bug to be open - when it has no fixed version, or when it has been found more recently than - it has been fixed. - </p> - - <p> - If no <var>version</var> is given, then the list of fixed versions for - the bug is cleared. This is identical to the behaviour of - <code>reopen</code>. - <var>version</var> may be a fully qualified version, of the - form <var>sourcepackagename/version</var>. - </p> - - <p> - This command will only cause a bug to be marked as not done if no - version is specified, or if the <var>version</var> being marked - found is equal to or greater than the highest <var>version</var> - marked fixed. (If you are certain that you want the bug marked as - not done, use <code>reopen</code> in conjunction - with <code>found</code>.) - </p> - - <p> - This command was introduced in preference to <code>reopen</code> - because it was difficult to add a <var>version</var> to that command's - syntax without suffering ambiguity. - </p> - </dd> - - - <dt><a name="notfound"><code>notfound</code> <var>bugnumber</var> - <var>version</var></a></dt> - <dd> - <p> - Remove the record that #<var>bugnumber</var> was encountered in the - given <var>version</var> of the package to which it is assigned. - <var>version</var> may be a fully qualified version, of - the form <var>sourcepackagename/version</var>. - </p> - - <p> - This differs from closing the bug at that version in that the bug is not - listed as fixed in that version either; no information about that version - will be known. It is intended for fixing mistakes in the record of when a - bug was found. - </p> - </dd> - - - <dt><a name="fixed"><code>fixed</code> <var>bugnumber</var> - <var>version</var></a></dt> - <dd> - <p> - Indicate that bug #<var>bugnumber</var> was fixed in the given - <var>version</var> of the package to which it is assigned. - <var>version</var> may be a fully qualified version, of the - form <var>sourcepackagename/version</var>. - </p> - - <p> - This does <em>not</em> cause the bug to be marked as closed, it - merely adds another version in which the bug was fixed. Use the - bugnumber-done address to close a bug and mark it fixed in a - particular version. - </p> - </dd> - - - <dt><a name="notfixed"><code>notfixed</code> <var>bugnumber</var> - <var>version</var></a></dt> - <dd> - <p> - Remove the record that bug #<var>bugnumber</var> has been fixed in - the given <var>version</var>. - <var>version</var> may be a fully qualified version, of the - form <var>sourcepackagename/version</var>. - </p> - - <p> - This command is equivalent to <code>found</code> followed by - <code>notfound</code> (the found removes the fixed at a particular - version, and notfound removes the found) with the exception that - the bug is not reopened if the found version is greater than any - existing fixed version. It is intended for fixing mistakes in the - record of when a bug was fixed; in most cases, you actually want - <code>found</code>, not <code>notfixed</code>. - </p> - </dd> - - - <dt><a name="submitter"><code>submitter</code> <var>bugnumber</var> - <var>originator-address</var> | <code>!</code></a></dt> - <dd> - <p> - Changes the originator of #<var>bugnumber</var> to - <var>originator-address</var>. - </p> - - <p> - If you wish to become the new originator of the report you can use - the <code>!</code> shorthand or specify your own email address. - </p> - - <p> - While the <code>reopen</code> command changes the originator of other - bugs merged with the one being reopened, <code>submitter</code> does not - affect merged bugs. - </p> - </dd> - - - <dt><a name="forwarded"><code>forwarded</code> <var>bugnumber</var> - <var>address</var></a></dt> - <dd> - <p> - Notes that <var>bugnumber</var> has been forwarded to the upstream - maintainer at <var>address</var>. This does not actually forward the - report. This can be used to change an existing incorrect forwarded-to - address, or to record a new one for a bug that wasn't previously noted - as having been forwarded. <var>address</var> should generally be a - URI, or possibly an email address. Using a URI where possible - allows tools to query a remote bug tracking system (such as - bugzilla) for a bug's status. - </p> - - <p> - Example usage: - </p> - - <pre> - forwarded 12345 http://bugz.illa.foo/cgi/54321 - </pre> - </dd> - - - <dt><a name="notforwarded"><code>notforwarded</code> - <var>bugnumber</var></a></dt> - <dd> - <p> - Forgets any idea that <var>bugnumber</var> has been forwarded to any - upstream maintainer. If the bug was not recorded as having been - forwarded then this will do nothing. - </p> - </dd> - - - <dt><a name="retitle"><code>retitle</code> <var>bugnumber</var> - <var>new-title</var></a></dt> - <dd> - <p> - Changes the title of a bug report to that specified (the default is - the <code>Subject</code> mail header from the original report). - Will also change the titles of all bug reports which this bug is - merged with. - </p> - </dd> - - - <dt><a name="severity"><code>severity</code> <var>bugnumber</var> - <var>severity</var></a></dt> - <dd> - <p> - Set the severity level for bug report #<var>bugnumber</var> to - <var>severity</var>. No notification is sent to the user who reported - the bug. - </p> - - <p> - Severities are <bts_severities>. - </p> - - <p> - For <a href="Developer#severities">their meanings</a> please - consult the general developers' documentation for the bug system. - </p> - </dd> - - <dt><a name="affects"><code>affects</code> <var>bugnumber</var> - [ <code>+</code> | <code>-</code> | <code>=</code> - ] <var>package</var> [ <var>package</var> ... ]</a></dt> - <dd> - <p> - Indicates that a bug affects another package. In the case - where <var>bugnumber</var> causes breakage in <var>package</var> - even though the bug is actually present in the package to which - it is assigned, this causes the bug to be listed by default in - the bug list of <var>package</var>. This should generally be - used where the bug is severe enough to cause multiple reports - from users to be assigned to the wrong package. <code>=</code> - sets the affects to the list of packages given, and is the - default action if no packages are given; <code>-</code> removes - the given packages from the affects list; <code>+</code> adds - the given packages to the affects list, and is the default if - packages are given. - </p> - </dd> - - <dt><a name="summary"><code>summary</code> <var>bugnumber</var> - [<var>message number</var> | <var>summary text</var>]</a></dt> - <dd> - <p> - Selects a message to use as a summary of a bug. The first - non-pseudoheader/non-control paragraph of that message is parsed and set as the - summary of the bug which is displayed on the top of the bug - report page. This is useful in cases where the original report - doesn't correctly describe the problem or the bug has many - messages which make it difficult to identify the actual problem. - </p> - <p> - If <var>message number</var> is not given, clears the - summary. <var>message number</var> is the message number as - listed in the bugreport cgi script output; if - a <var>message number</var> of 0 is given, the current message - is used (that is, the message which was sent to - control@bugs.debian.org which contains the summary control - command). - </p> - <p> - If <var>message number</var> is not numerical and not the empty - string, it is assumed to be the text to set the summary to. - </p> - </dd> - - <dt><a name="outlook"><code>outlook</code> <var>bugnumber</var> - [<var>message number</var> | <var>outlook text</var>]</a></dt> - <dd> - <p> - Selects a message to use as the outlook for fixing a bug (or the - current status of fixing a bug). The first - non-pseudoheader/non-control paragraph of that message is parsed - and set as the outlook of the bug which is displayed on the top - of the bug report page. This is useful to coordinate with others - who are working on fixing this bug (for example, in an bug - squashing party). - </p> - <p> - If <var>message number</var> is not given, clears the - outlook. <var>message number</var> is the message number as - listed in the bugreport cgi script output; if - a <var>message number</var> of 0 is given, the current message - is used (that is, the message which was sent to - control@bugs.debian.org which contains the outlook control - command). - </p> - <p> - If <var>message number</var> is not numerical and not the empty - string, it is assumed to be the text to set the outlook to. - </p> - </dd> - - - <dt><a name="clone"><code>clone</code> <var>bugnumber</var> <var>NewID</var> - [ <var>new IDs</var> ... ]</a></dt> - <dd> - <p> - The clone control command allows you to duplicate a bug report. It is - useful in the case where a single report actually indicates that multiple - distinct bugs have occurred. <q><var>New IDs</var></q> are negative numbers, - separated by spaces, which may be used in subsequent control commands to - refer to the newly duplicated bugs. A new report is generated for each - new ID. - </p> - - <p> - Example usage: - </p> - - <pre> - clone 12345 -1 -2 - reassign -1 foo - retitle -1 foo: foo sucks - reassign -2 bar - retitle -2 bar: bar sucks when used with foo - severity -2 wishlist - clone 123456 -3 - reassign -3 foo - retitle -3 foo: foo sucks - merge -1 -3 - </pre> - </dd> - - - <dt><a name="merge"><code>merge</code> <var>bugnumber</var> - <var>bugnumber</var> ...</a></dt> - <dd> - <p> - Merges two or more bug reports. When reports are merged opening, - closing, marking or unmarking as forwarded and reassigning any of the - bugs to a new package will have an identical effect on all of the - merged reports. - </p> - - <p> - Before bugs can be merged they must be in exactly the same state: - either all open or all closed, with the same forwarded-to upstream - author address or all not marked as forwarded, all assigned to the - same package or package(s) (an exact string comparison is done on the - package to which the bug is assigned), and all of the same severity. - If they don't start out in the same state you should use - <code>reassign</code>, <code>reopen</code> and so forth to make sure - that they are before using <code>merge</code>. Titles are not required - to match, and will not be affected by the merge. Tags are not required - to match, either, they will be joined. - </p> - - <p> - If any of the bugs listed in a <code>merge</code> command is already - merged with another bug then all the reports merged with any of the - ones listed will all be merged together. Merger is like equality: it - is reflexive, transitive and symmetric. - </p> - - <p> - Merging reports causes a note to appear on each report's logs; on the - WWW pages this includes links to the other bugs. - </p> - - <p> - Merged reports are all expired simultaneously, and only when all of - the reports each separately meet the criteria for expiry. - </p> - </dd> - - - <dt><a name="forcemerge"><code>forcemerge</code> <var>bugnumber</var> - <var>bugnumber</var> ...</a></dt> - <dd> - <p> - Forcibly merges two or more bug reports. The settings of the first - bug listed which must be equal in a normal merge are assigned to - the bugs listed next. Tags are joined as usual. To avoid typos erroneously merging bugs, - bugs must be in the same package. See the text above for a - description of what merging means. - </p> - - <p> - Note that this makes it possible to close bugs by merging; you - are responsible for notifying submitters with an appropriate close - message if you do this. - </p> - </dd> - - - <dt><a name="unmerge"><code>unmerge</code> <var>bugnumber</var></a></dt> - <dd> - <p> - Disconnects a bug report from any other reports with which it may have - been merged. If the report listed is merged with several others then - they are all left merged with each other; only their associations with - the bug explicitly named are removed. - </p> - - <p> - If many bug reports are merged and you wish to split them into two - separate groups of merged reports you must unmerge each report in one - of the new groups separately and then merge them into the required new - group. - </p> - - <p> - You can only unmerge one report with each <code>unmerge</code> - command; if you want to disconnect more than one bug simply include - several <code>unmerge</code> commands in your message. - </p> - </dd> - - - <dt><a name="tags"><!-- match tags too --></a><a name="tag"><code>tags</code> <var>bugnumber</var> [ <code>+</code> | - <code>-</code> | <code>=</code> ] <var>tag</var> [ <var>tag</var> - ... ] [ <code>+</code> | <code>-</code> - | <code>=</code> <var>tag</var> ... ] ]</a></dt> - <dd> - <p> - Sets tags for the bug report #<var>bugnumber</var>. No notification - is sent to the user who reported the bug. Setting the action to - <code>+</code> means to add each <var>tag</var> - following, <code>-</code> means to remove each <var>tag</var> - following, and <code>=</code> means to set the following tags to - the list provided. Intervening <code>+</code>, <code>-</code>, - or <code>=</code> change the action for the tags following. The - default action is adding. - </p> - - <p> - Example usage: - </p> - - <pre> - \# same as 'tags 123456 + patch' - tags 123456 patch - - \# same as 'tags 123456 + help security' - tags 123456 help security - - \# add 'fixed' and 'pending' tags - tags 123456 + fixed pending - - \# remove 'unreproducible' tag - tags 123456 - unreproducible - - \# set tags to exactly 'moreinfo' and 'unreproducible' - tags 123456 = moreinfo unreproducible - - \# remove the moreinfo tag and add a patch tag - tags 123456 - moreinfo + patch - </pre> - - <p> - Available tags currently include <bts_tags>. - </p> - - <p> - For <a href="Developer#tags">their meanings</a> please consult the - general developers' documentation for the bug system. - </p> - </dd> - - - <dt><a name="block"><code>block</code> <var>bugnumber</var> <code>by</code> - <var>bug</var> ...</a></dt> - <dd> - Note that the fix for the first bug is blocked by the other listed bugs. - </dd> - - - <dt><a name="unblock"><code>unblock</code> <var>bugnumber</var> - <code>by</code> <var>bug</var> ...</a></dt> - <dd> - Note that the fix for the first bug is no longer blocked by the other - listed bugs. - </dd> - - - <dt><a name="close"><code>close</code> <var>bugnumber</var> [ - <var>fixed-version</var> ] (deprecated)</a></dt> - <dd> - <p> - Close bug report #<var>bugnumber</var>. - </p> - - <p> - A notification is sent to the user who reported the bug, but (in - contrast to mailing <var>bugnumber</var><code>-done@bugs.debian.org</code>) the - text of the mail which caused the bug to be closed is <strong>not</strong> - included in that notification. The maintainer who closes a report - needs to ensure, probably by sending a separate message, that the user - who reported the bug knows why it is being closed. - The use of this command is therefore deprecated. See the - developer's information about <a href="Developer#closing">how to - close a bug properly</a>. - </p> - - <p> - If you supply a <var>fixed-version</var>, the bug tracking system - will note that the bug was fixed in that version of the package. - </p> - </dd> - - - <dt><a name="package"><code>package</code> [ <var>packagename</var> ... - ]</a></dt> - <dd> - <p> - Limits the following commands so that they will only apply to bugs - filed against the listed packages. You can list one or more packages. If - you don't list any packages, the following commands will apply to all - bugs. You're encouraged to use this as a safety feature in case you - accidentally use the wrong bug numbers. - </p> - - <p> - Example usage: - </p> - - <pre> - package foo - reassign 123456 bar 1.0-1 - - package bar - retitle 123456 bar: bar sucks - severity 123456 normal - - package - severity 234567 wishlist - </pre> - </dd> - - - <dt><a name="owner"><code>owner</code> <var>bugnumber</var> - <var>address</var> | <code>!</code></a></dt> - <dd> - <p> - Sets <var>address</var> to be the <q>owner</q> of #<var>bugnumber</var>. - The owner of a bug claims responsibility for fixing it. - This is useful to share out work in cases where a - package has a team of maintainers. - </p> - - <p> - If you wish to become the owner of the bug yourself, you can use the - <code>!</code> shorthand or specify your own email address. - </p> - </dd> - - - <dt><a name="noowner"><code>noowner</code> <var>bugnumber</var></a></dt> - <dd> - Forgets any idea that the bug has an owner other than the usual - maintainer. If the bug had no owner recorded then this will do nothing. - </dd> - - - <dt><a name="archive"><code>archive</code> <var>bugnumber</var></a></dt> - <dd> - Archives a bug that had been archived at some point in the past - but is currently not archived if the bug fulfills - the requirements for archival, ignoring time. - </dd> - - - <dt><a name="unarchive"><code>unarchive</code> <var>bugnumber</var></a></dt> - <dd> - Unarchives a bug that was previously archived. Unarchival should - generally be coupled with reopen and found/fixed as appropriate. Bugs - that have been unarchived can be archived using archive assuming the - non-time based archival requirements are met. You should not be - using unarchive to make trivial changes to archived bugs, such as - changing the submitter; its primary purpose is to allow for the - reopening of bugs which have been archived without the - intervention of BTS administrators. - </dd> - - - <dt><a name="comment"><code>#</code>...</a></dt> - <dd> - One-line comment. The <code>#</code> must be at the start of the line. - The text of comments will be included in the acknowledgement sent to the - sender and to affected maintainers, so you can use this to document the - reasons for your commands. - </dd> - - - <dt><a name="thanks"><code>quit</code></a></dt> - <dt><code>stop</code></dt> - <dt><code>thank</code></dt> - <dt><code>thanks</code></dt> - <dt><code>thankyou</code></dt> - <dt><code>thank you</code></dt> - <dt><code>--</code></dt> - <!-- #366093, I blame you! --> - <!-- <dt><code>kthxbye</code></dt> --> - <!-- See... I documented it! --> - <dd> - On a line by itself, in any case, possibly followed by - whitespace, tells the control server to stop processing the - message; the remainder of the message can include explanations, - signatures or anything else, none of it will be detected by the - control server. - </dd> -</dl> - -<hr /> - -#use "otherpages.inc" - -#use "$(ENGLISHDIR)/Bugs/footer.inc" diff --git a/greek/Bugs/server-refcard.wml b/greek/Bugs/server-refcard.wml deleted file mode 100644 index b8d423b56cf..00000000000 --- a/greek/Bugs/server-refcard.wml +++ /dev/null @@ -1,94 +0,0 @@ -#use wml::debian::template title="Debian BTS — mail server reference card" NOHEADER=yes NOCOPYRIGHT=true -#include "$(ENGLISHDIR)/Bugs/pkgreport-opts.inc" -#use wml::debian::translation-check translation="edf7479a4ad0dfcf1c56fed4b143f6f261fd1d6d" maintainer="galaxico" - -<h1>Mail servers' reference card</h1> - -<p>Full documentation of the mail servers is available on the WWW, in the -files -<a href="server-request">bug-log-mailserver.txt</a> and -<a href="server-control">bug-maint-mailcontrol.txt</a> or by -sending the word <code>help</code> to each mailserver.</p> - -<h2>Synopsis of commands available at <code>request@bugs.debian.org</code></h2> - -<ul> -<li><code>send</code> <var>bugnumber</var></li> -<li><code>send-detail</code> <var>bugnumber</var></li> -<li><code>index</code> [<code>full</code>]</li> -<li><code>index-summary by-package</code></li> -<li><code>index-summary by-number</code></li> -<li><code>index-maint</code></li> -<li><code>index maint</code> <var>maintainer</var></li> -<li><code>index-packages</code></li> -<li><code>index packages</code> <var>package</var></li> -<li><code>send-unmatched</code> [<code>this</code>|<code>0</code>]</li> -<li><code>send-unmatched</code> <code>last</code>|<code>-1</code></li> -<li><code>send-unmatched</code> <code>old</code>|<code>-2</code></li> -<li><code>getinfo</code> <var>filename</var> <small>(ftp.debian.org/debian/doc/*)</small></li> -<li><code>help</code></li> -<li><code>refcard</code></li> -<li><code><a href="$(BUGS)/server-control#thanks">thanks</a></code></li> -<li><code>#</code>... <em>(comment)</em></li> -<li><code>debug</code> <var>level</var></li> -</ul> - -<h2>Synopsis of extra commands available at <code>control@bugs.debian.org</code></h2> - -<ul> -<li><code>reassign</code> <var>bugnumber</var> <var>package</var> - [ <var>version</var> ]</li> -<li><code>severity</code> <var>bugnumber</var> <var>severity</var></li> -<li><code>reopen</code> <var>bugnumber</var> - [ <var>originator-address</var> | <code>=</code> | <code>!</code> ]</li> -<li><code>found</code> <var>bugnumber</var> [ <var>version</var> ]</li> -<li><code>notfound</code> <var>bugnumber</var> <var>version</var></li> -<li><code>submitter</code> <var>bugnumber</var> - <var>originator-address</var> | <code>!</code></li> -<li><code>forwarded</code> <var>bugnumber</var> <var>address</var></li> -<li><code>notforwarded</code> <var>bugnumber</var></li> -<li><code>owner</code> <var>bugnumber</var> - <var>address</var> | <code>!</code></li> -<li><code>noowner</code> <var>bugnumber</var></li> -<li><code>retitle</code> <var>bugnumber</var> <var>new-title</var></li> -<li><code>clone</code> <var>bugnumber</var> <var>NewID</var> [ <var>new IDs</var> ... ]</li> -<li><code>merge</code> <var>bugnumber</var> <var>bugnumber</var> ...</li> -<li><code>unmerge</code> <var>bugnumber</var></li> -<li><code>forcemerge</code> <var>bugnumber</var> <var>bugnumber</var> ...</li> -<li><code>tags</code> <var>bugnumber</var> - [ <code>+</code> | <code>-</code> | <code>=</code> ] <var>tag</var> [ <var>tag</var> ... ]</li> -<li><code>block</code> <var>bugnumber</var> <code>by</code> <var>bug</var> ...</li> -<li><code>unblock</code> <var>bugnumber</var> <code>by</code> <var>bug</var> ...</li> -<li><code>close</code> <var>bugnumber</var> [ <var>fixed-version</var> ] - <strong>(deprecated — you must separately tell originator why, see -<q><a href="Developer#closing">Closing bug reports</a></q> -instead)</strong></li> -</ul> - -<p><code>reopen</code> with <code>=</code> or no originator address leaves -the originator as the original submitter; <code>!</code> sets it to -you, the person doing the reopen.</p> - -<p><a href="Developer#severities">Severities</a> are <bts_severities>.</p> - -<p><a href="Developer#tags">Tags</A> currently include <bts_tags>.</p> - -<h2>Synopsis of bug submission and followup addresses</h2> - -<ul> - <li><var>nnn</var>[ <code>-submit</code> | ]</li> - <li><var>nnn</var><code>-maintonly</code></li> - <li><var>nnn</var><code>-quiet</code></li> - <li><var>nnn</var><code>-forwarded</code></li> - <li><var>nnn</var><code>-request</code></li> - <li><var>nnn</var><code>-submitter</code></li> - <li><var>nnn</var><code>-done</code></li> - <li><var>nnn</var><code>-close</code></li> - <li><var>nnn</var><code>-subscribe</code></li> -</ul> - -<hr /> - -#use "otherpages.inc" - -#use "$(ENGLISHDIR)/Bugs/footer.inc" diff --git a/greek/Bugs/server-request.wml b/greek/Bugs/server-request.wml deleted file mode 100644 index 1499dd6372e..00000000000 --- a/greek/Bugs/server-request.wml +++ /dev/null @@ -1,297 +0,0 @@ -#use wml::debian::template title="Debian BTS - request server" NOHEADER=yes NOCOPYRIGHT=true -#use wml::debian::translation-check translation="ffe142fb8e27c6752fff483899ded27505b6364e" maintainer="galaxico" - -<h1><a name="introduction">Introduction to the bug system request server</a></h1> - -<p>There is a mailserver which can send the bug reports and -indices as plain text on request.</p> - -<p>To use it you send a mail message to -<a href="mailto:request@bugs.debian.org"><code>request@bugs.debian.org</code></a>. -The <code>Subject</code> of the message is ignored, except -for generating the <code>Subject</code> of the reply.</p> - -<p>The body you send should be a series of commands, one per line. -You'll receive a reply which looks like a transcript of your message -being interpreted, with a response to each command. No notifications -are sent to anyone for the commands listed here and the mail isn't -logged anywhere publicly available.</p> - -<p>Any text on a line starting with a hash sign <code>#</code> is -ignored; the server will stop processing when it finds a line with -a <a href="#stopprocessing">control terminator</a> ( -<code>quit</code>, <code>thank you</code>, or two -hyphens are common examples). It will also stop if it -encounters too many unrecognised or badly-formatted commands. If no -commands are successfully handled it will send the help text for the -server.</p> - -<h1>Commands available</h1> - -<dl> -<dt><code>send</code> <var>bugnumber</var></dt> -<dt><code>send-detail</code> <var>bugnumber</var></dt> -<dd> -Requests the transcript for the bug report in question. -<code>send-detail</code> sends all of the <q>boring</q> messages in the -transcript as well, such as the various auto-acks. -</dd> - -<dt><code>index</code> [<code>full</code>]</dt> -<dt><code>index-summary by-package</code></dt> -<dt><code>index-summary by-number</code></dt> -<dd> -Request the full index (with full details, and including done and -forwarded reports), or the summary sorted by package or by number, -respectively. -</dd> - -<dt><code>index-maint</code></dt> -<dd> -Requests the index page giving the list of maintainers with bugs (open -and recently-closed) in the tracking system. -</dd> - -<dt><code>index maint</code> <var>maintainer</var></dt> -<dd> -Requests the index pages of bugs in the system for the maintainer -<var>maintainer</var>. The search term is an exact match. -The bug index will be sent in a separate message. -</dd> - -<dt><code>index-packages</code></dt> -<dd> -Requests the index page giving the list of packages with bugs (open -and recently-closed) in the tracking system. -</dd> - -<dt><code>index packages</code> <var>package</var></dt> -<dd> -Requests the index pages of bugs in the system for the package -<var>package</var>. The search term is an exact match. -The bug index will be sent in a separate message. -</dd> - -<dt><code>send-unmatched</code> [<code>this</code>|<code>0</code>]</dt> -<dt><code>send-unmatched</code> <code>last</code>|<code>-1</code></dt> -<dt><code>send-unmatched</code> <code>old</code>|<code>-2</code></dt> -<dd> -Requests logs of messages not matched to a particular bug report, for -this week, last week and the week before. (Each week ends on a -Wednesday.) -</dd> - -<dt><code>getinfo</code> <var>filename</var></dt> -<dd> -<p> -Request a file containing information about package(s) and or -maintainer(s) - the files available are: -</p> - - <dl> - <dt><code>maintainers</code></dt> - <dd> - The unified list of packages' maintainers, as used by the tracking - system. - This is derived from information in the <code>Packages</code> - files, override files and pseudo-packages files. - </dd> - - <dt><code>override.</code><var>distribution</var></dt> - <dt><code>override.</code><var>distribution</var><code>.non-free</code></dt> - <dt><code>override.</code><var>distribution</var><code>.contrib</code></dt> - <dt><code>override.experimental</code></dt> - <dd> - Information about the priorities and sections of packages and - overriding values for the maintainers. This information is used by - the process which generates the <code>Packages</code> files in the FTP - archive. Information is available for each of the main distribution - trees available, by their codewords. - </dd> - - <dt><code>pseudo-packages.description</code></dt> - <dt><code>pseudo-packages.maintainers</code></dt> - <dd> - List of descriptions and maintainers respectively for pseudo-packages. - </dd> - </dl> -</dd> - -<dt><code>refcard</code></dt> -<dd> -Requests that the mailservers' reference card be sent in plain ASCII. -</dd> - -<dt><a name="user"><code>user</code> <var>address</var></a></dt> -<dd> -Sets <var>address</var> to be the <q>user</q> of all <code>usertag</code> -commands that follow. -</dd> - -<dt><a name="usertag"><code>usertag</code> <var>bugnumber</var> - [ <code>+</code> | <code>-</code> | <code>=</code> ] <var>tag</var> - [ <var>tag</var> ... ]</a></dt> -<dd> -Allows to define tags on a per-user basis. The <code>usertag</code> -command works just like the regular <code>tag</code> command, except -that you get to make up whatever tags you like. By default, the address -in the <code>From:</code> or <code>Reply-To:</code> header of your mail -will be used to set the user of the <code>usertag</code>. -</dd> - -<dt><a name="usercategory"><code>usercategory</code> - <var>category-name</var> [ <code>[hidden]</code> ]</a></dt> -<dd> -<p> -Adds, updates or removes a <code>usercategory</code>. By default the user -category is visible, if the optional argument <code>[hidden]</code> -is specified then it will not be visible, but still be available to be -referenced from other user category definitions. -</p> - -<p> -This command is somewhat special, as when adding or updating a user -category it requires a body following immediately after the command. If -the body is empty the user category will get removed instead. The body -is composed of lines starting with any number of spaces. Each category -should start with a line with <code>*</code>, and optionally it can be -followed by several selection lines starting with <code>+</code>. The -complete format is as follows: -</p> - -<div> -* <var>category-name-1</var><br /> -* <var>Category Title 2</var> - [ <code>[</code><var>selection-prefix</var><code>]</code> ]<br /> - + <var>Selection Title 1</var> <code>[</code> - [ <var>order</var><code>:</code> ] - <var>selection-1</var> <code>]</code><br /> - + <var>Selection Title 2</var> <code>[</code> - [ <var>order</var><code>:</code> ] - <var>selection-2</var> <code>]</code><br /> - + <var>Default Selection Title</var> <code>[</code> - [ <var>order</var>: ] <code>]</code><br /> -* <var>category-name-3</var><br /> -</div> - -<p> -The <var>category-names</var> appearing in the command and in the body -are used to make references between them, to avoid unnecessary inlining. -The <var>Category Titles</var> are used in the package report summary. -</p> - -<p> -The optional <var>selection-prefix</var> is prefixed to every -<var>selection</var> on each entry in the category section. The first -<var>selection</var> which matches gets the bug shown under it. The -optional <var>order</var> parameter specifies the position when showing -the selected entries, this is useful when using a match that selects a -superset of the previous ones but that needs to be shown before them. -</p> - -<p> -The <var>category-name</var> <code>normal</code> has the special meaning -of being the default view, so by replacing it with a different user category -for the <var>pkgname</var>@packages.debian.org user one can change the -default classification for a package. -</p> - -<p> -Example usage: -</p> - -<pre> - usercategory dpkg-program [hidden] - * Program - + dpkg-deb [tag=dpkg-deb] - + dpkg-query [tag=dpkg-query] - + dselect [package=dselect] - - usercategory new-status [hidden] - * Status [pending=] - + Outstanding with Patch Available [0:pending+tag=patch] - + Outstanding and Confirmed [1:pending+tag=confirmed] - + Outstanding and More Information Needed [pending+tag=moreinfo] - + Outstanding and Forwarded [pending+tag=forwarded] - + Outstanding but Will Not Fix [pending+tag=wontfix] - + Outstanding and Unclassified [2:pending] - + From other Branch [absent] - + Pending Upload [pending-fixed] - + Fixed in NMU [fixed] - + Resolved [done] - + Unknown Pending Status [] - - \# Change default view - usercategory normal - * new-status - * severity - - usercategory old-normal - * status - * severity - * classification -</pre> -</dd> - -<dt><code>help</code></dt> -<dd> -Requests that this help document be sent by email in plain ASCII. -</dd> - -<dt><a name="stopprocessing"></a><code>quit</code></dt> -<dt><code>stop</code></dt> -<dt><code>thank</code></dt> -<dt><code>thanks</code></dt> -<dt><code>thankyou</code></dt> -<dt><code>thank you</code></dt> -<dt><code>--</code></dt> -<!-- #366093, I blame you! --> -<!-- <dt><code>kthxbye</code></dt> --> -<!-- See... I documented it! --> -<dd> -Stops processing at this point of the message. After this you may -include any text you like, and it will be ignored. You can use this -to include longer comments than are suitable for <code>#</code>, for -example for the benefit of human readers of your message (reading it -via the tracking system logs or due to a <code>CC</code> or -<code>BCC</code>). -</dd> - -<dt><code>#</code>...</dt> -<dd> -One-line comment. The <code>#</code> must be at the start of the -line. -</dd> - -<dt><code>debug</code> <var>level</var></dt> -<dd> -Sets the debugging level to <var>level</var>, which should be a -nonnegative integer. 0 is no debugging; 1 is usually sufficient. The -debugging output appears in the transcript. It is not likely to be -useful to general users of the bug system. -</dd> - -</dl> - -<p>There is a <a href="server-refcard">reference card</a> for the -mailservers, available via the WWW, in -<code>bug-mailserver-refcard.txt</code> or by email using the -<code>refcard</code> command (see above).</p> - -<p>If you wish to manipulate bug reports you should use the -<code>control@bugs.debian.org</code> address, which understands a -<a href="server-control">superset of the commands listed -above</a>. This is described in another document, available on the -<a href="server-control">WWW</a>, -in the file <code>bug-maint-mailcontrol.txt</code>, or by -sending <code>help</code> to <code>control@bugs.debian.org</code>.</p> - -<p>In case you are reading this as a plain text file or via email: an -HTML version is available via the bug system main contents page -<code>https://www.debian.org/Bugs/</code>.</p> - -<hr /> - -#use "otherpages.inc" - -#use "$(ENGLISHDIR)/Bugs/footer.inc" diff --git a/greek/CD/artwork/Makefile b/greek/CD/artwork/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/CD/artwork/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/CD/artwork/index.wml b/greek/CD/artwork/index.wml deleted file mode 100644 index 361f02be937..00000000000 --- a/greek/CD/artwork/index.wml +++ /dev/null @@ -1,54 +0,0 @@ -#use wml::debian::cdimage title="Artwork for Debian CDs" BARETITLE=true -#use wml::debian::translation-check translation="76d302b75ce2d826fedb2802e2c449986414c089" maintainer="galaxico" - -<p>Official artwork for current and recent releases may be available on the -<a href="https://wiki.debian.org/DebianArt/Themes">themes</a> wiki page. - -<p>If you have made your own images for CD covers and want to share -them with us, <a -href="mailto:debian-cd@lists.debian.org" ->please tell us</a>! The Debian logo is also <a -href="$(HOME)/logos/">available in various forms</a>.</p> - -<p>Note that the thumbnails are just a selection of the graphics -on offer. Follow the links to see all graphics.</p> - -<ul> - - <li><a href="http://debian.semistable.com/cdcover.pl">\ - http://debian.semistable.com/cdcover.pl</a> - (editable, dynamically generated PostScript):<br /> - - <a href="http://debian.semistable.com/cdcover.pl"><img - src="semistable.com-cdcover.jpeg" alt="[Cover]"></a> - </li> - -# ============================================================ - - <li><a href="http://briscoe-smith.org.uk/charles/debian-cd-label.html">\ - http://briscoe-smith.org.uk/charles/debian-cd-label.html</a> - (editable PostScript file):<br /> - - <a href="http://briscoe-smith.org.uk/charles/cd-label.ps"><img - src="briscoe-smith.org.uk-cd-label.jpeg" alt="[Label]"></a> - </li> - - <li><url "http://www.nongnu.org/sdcdc/" /> - (editable shell and Gimp Scheme scripts):<br /> - - <a href="https://www.nongnu.org/sdcdc/"><img - src="autistici.org-cd-1-i386-en.jpeg" alt="[i386 covers]"></a> - - </li> - - <li><url "https://jonnyblair.co.uk/debian/" /><br /> - - <a href="https://jonnyblair.co.uk/img/illustrations/debian/woody_cover/disc01/woody01_front.jpg"><img - src="jonnyblair.co.uk-woody_front.jpeg" alt="[Front]"></a> - - <a href="https://jonnyblair.co.uk/img/illustrations/debian/woody_cover/disc01/woody01_tray.png"><img - src="jonnyblair.co.uk-woody_tray.jpeg" alt="[Tray]"></a> - </li> -# ============================================================ - -</ul> diff --git a/greek/CD/faq/Makefile b/greek/CD/faq/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/CD/faq/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/CD/faq/index.wml b/greek/CD/faq/index.wml deleted file mode 100644 index 9b25dd6dfa2..00000000000 --- a/greek/CD/faq/index.wml +++ /dev/null @@ -1,1003 +0,0 @@ -#use wml::debian::cdimage title="Frequently Asked Questions about Debian CD/DVD/USB images" NOHEADER=true BARETITLE=true -#use wml::debian::toc -#include "$(ENGLISHDIR)/releases/info" -#use wml::debian::translation-check translation="0b5d69c288d6d73850c91ea30fce27cb2b7fb379" maintainer="galaxico" - -<define-tag toc-title-formatting endtag="required" whitespace="delete"> -<p><strong>%body</strong></p> -</define-tag> - -<h1><a name="top">Frequently Asked Questions</a></h1> - -<toc-display/> - -<toc-add-entry name="what-is">What is a <q>CD image</q> anyway?</toc-add-entry> - -<p>A CD image is the exact representation of the data on a CD in a -normal computer file, that can e.g. be transmitted over the -Internet. CD burning programs can use the image files to make real -CDs.</p> - -<p>In Debian, we use the term <q>CD image</q> as a common way to -describe a range of things, many of which don't even fit on CD! The -name is old, but it has stuck. We regularly build multiple different -types of image:</p> - -<ul> - <li>Debian installer images in multiple sizes. These range from - small CD-sized <q>netinst</q> images for quick download up to - large complete sets of images designed for DVD, Blu-Ray (BD) or - Dual-Layer Blu-Ray (DLBD) media.</li> - - <li>Debian live images - live systems designed to be run directly - from CD/DVD/USB without needing - installation. See <a href="#live-cd">below</a> for more - details.</li> - -</ul> - -<p>In many cases, these installer and live images can often be written -directly to USB flash drives with no <b>CD</b> involved; -see <a href="#write-usb">below</a>. Don't be put off by the name <q>CD -image</q>!</p> - -<p>For a correctly written image, the <tt>.iso</tt> file must not -appear on the media when you access it! Instead, you should see a -number of files and directories - in the case of a Debian installer -image, this includes a -<q>dists</q> directory and a <q>README.html</q> file.</p> - -<p>The <tt>.iso</tt> format we use for our images is roughly -comparable to a <tt>.zip</tt> file: It contains other files and -directories, and only these will appear on the final CD/DVD/USB -medium. Some archive programs allow you to <q>unpack</q> -<tt>.iso</tt> files. Do not use this feature to create a CD from the -unpacked files! The resulting medium will fail to boot because the -<tt>.iso</tt> format includes special information related to booting -from the CD/DVD/USB, which is lost when you unpack the file. See below on how -to correctly write a CD/DVD image under <a href="#record-unix">Linux</a>, -<a href="#record-windows">Windows</a> or <a href="#record-mac">Mac -OS</a>, or how to write an image to a <a href="#write-usb">USB flash -drive</a>.</p> - -# ============================================================ - -# This text is basically the same as what's in the Debian wiki at -# https://wiki.debian.org/Firmware - -<toc-add-entry name="firmware">Debian installer tells me my hardware -needs extra firmware to work. Where do I get that?</toc-add-entry> - -<p>Many devices require firmware to operate. Historically, firmware -would be built into the device's ROM or Flash memory, but more and -more often, a firmware image has to be loaded into the device by a -device driver during device initialization.</p> - -<p>Some firmware images are free and open-source, and some of them are -non-free, which means that you would need to add the non-free and -contrib components to your APT sources.</p> - -<p>In some cases the installer detects the need for non-free firmware -and prompts the user to make the firmware available to the installer -to complete the installation. This can happen, for example, with -wireless network cards which often require non-free firmware to -function (see ipw2200 for an example).</p> - -<p>There are two ways to proceed here:</p> - -<ul> - - <li>An easy method is to use an installer image that includes all - non-free firmware packages directly. See - <a href="https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/">https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/</a> - for those.</li> - - <li>You can also download a firmware archive for your platform and - unpack it into a directory named <q>firmware</q> in the root of a - removable storage device (USB/CD drive). You can find firmware - downloads for your Debian version at - <a href="https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/">https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/</a>. When - the installer starts, it will automatically find the firmware - files in the directory on the removable storage and, if needed, - install the required firmware. This is documented in - the <a href="https://d-i.debian.org/doc/installation-guide/en.amd64/ch06s04.html">Debian - installer manual</a>.</li> - -</ul> - -# ============================================================ - -<toc-add-entry name="mailing-list">My question is not answered by this -FAQ!</toc-add-entry> - -<p>If you cannot find an answer to your question here, you can ask for -help on one of the Debian mailing lists. -In all cases, you should <a href="https://lists.debian.org/">search -the mailing list archives</a> before sending mail to the lists. -You can <a href="$(HOME)/MailingLists/subscribe">subscribe</a> -to and <a href="$(HOME)/MailingLists/unsubscribe">unsubscribe</a> -from the lists. However, you do not need to be subscribed in order -to send mail to the lists - if you are not subscribed, ask for -replies to be CC'd to you.</p> - -<p>Mailing lists relevant to problems with CD installation:</p> - -<ul> - - <li><a href="https://lists.debian.org/debian-cd/">debian-cd</a>: - Discussion about the CD image creation process, available CD - mirrors, problems when booting from CD, announcements of new - official images.</li> - - <li><a href="https://lists.debian.org/debian-boot/">debian-boot</a>: A - bit of a misnomer, this list actually covers the installation - process; any problems encountered after successfully booting - from CD may be more appropriate here than in debian-cd.</li> - - <li><a href="https://lists.debian.org/debian-live/">debian-live</a>: - A list for the Debian Live project, focused on development of the software - that is used to build Debian Live images, but also appropriate - for discussion particular to using those images.</li> - - <li><a href="https://lists.debian.org/debian-user/">debian-user</a>: - General support list for users of Debian. Focus is - more on problems encountered after a successful installation, - when using the system. There are also several lists for - non-English speakers, in <a href="https://lists.debian.org/debian-user-catalan/">Català</a>, - <a href="https://lists.debian.org/debian-chinese-big5/">Chinese</a>, - <a href="https://lists.debian.org/debian-user-danish/">Dansk</a>, - <a href="https://lists.debian.org/debian-esperanto/">Esperanto</a>, - <a href="https://lists.debian.org/debian-user-french/">Français</a>, - <a href="https://lists.debian.org/debian-user-german/">Deutsch</a>, - <a href="https://lists.debian.org/debian-user-hungarian/">Magyar</a>, - <a href="https://lists.debian.org/debian-user-indonesian/">Indonesian</a>, - <a href="https://lists.debian.org/debian-italian/">Italiano</a>, - <a href="https://lists.debian.org/debian-japanese/">日本語 (Nihongo)</a>, - <a href="https://lists.debian.org/debian-user-polish/">Polski</a>, - <a href="https://lists.debian.org/debian-user-portuguese/">Português</a>, - <a href="https://lists.debian.org/debian-russian/">Русский (Russkij)</a>, - <a href="https://lists.debian.org/debian-user-spanish/">Español</a>, - <a href="https://lists.debian.org/debian-user-swedish/">Svenska</a>, - <a href="https://lists.debian.org/debian-user-turkish/">Türkçe</a>, - and <a href="https://lists.debian.org/debian-user-ukrainian/">Ukrainian</a>. - </li> - -</ul> - -# ============================================================ - -<toc-add-entry name="why-jigdo">Why should I use this <q>jigdo</q> program? -I prefer a simple HTTP download!</toc-add-entry> - -<p>Today, there are nearly <a href="$(HOME)/mirror/list">300 Debian -mirrors</a> (which contain the complete Debian distribution as .deb files), -but <a href="../http-ftp/">far fewer</a> machines serving Debian CD images. -As a result, the CD image servers are constantly overloaded.</p> - -<p>Additionally, nobody is very enthusiastic about setting up more -CD servers because of the tremendous amounts of wasted bandwidth -(some people keep <em>restarting</em> failed downloads instead of -<em>resuming</em> from the point where the connection was closed) -and because a regular mirror is more attractive (it allows -continuous upgrades of Debian, or using the <q>testing</q>/<q>unstable</q> -distribution instead of the <q>stable</q> one).</p> - -<p>jigdo tries to make -the most out of this situation, by downloading the data for the CD -images from one of the 300 mirrors. However, these mirrors only -hold individual .deb files, not the CD image, so some additional -manipulation of the data is necessary to produce one big CD image -file from the many small .deb files.</p> - -<p>Do not be afraid to <a href="../jigdo-cd/">try out jigdo</a>! -The complex process of generating the CD image is completely -hidden from you - instead, you benefit from the fact that one of -the 300 Debian mirrors is bound to be nearer and faster than any -of the CD servers.</p> - -# ============================================================ - -<toc-add-entry name="which-cd">Which of the numerous images -should I download? Do I need all of them?</toc-add-entry> - -<p>No. First, of course you only need to download CD <em>or</em> DVD -<em>or</em> BD images - the three types of images contain the same -packages.</p> - -<p>Also, you only need the CD/DVD/BD images for your computer's -architecture. The architecture is the type of hardware your computer -uses. By far the most popular one is the 64-bit Intel/AMD PC -architecture, so most people will only want to get the images -for <q>amd64</q>. If your PC has an older 32-bit AMD or Intel -processor, you will most likely need the -<q><a href="../../ports/i386/">i386</a></q> images instead.</p> - -<p>Furthermore, in most cases it is not necessary to download all of -the images for your architecture. The packages are sorted by -popularity: The first CD/DVD/BD contains the installation system and -the most popular packages. The second one contains slightly less -popular ones, the third one even less popular ones, etc. You will -probably only need the first couple of DVDs (or the first BD, etc.) -unless you have very special requirements. (And in case you happen to -need a package later on which is not on one of the CDs/DVDs/BDs you -downloaded, you can always install that package directly from the -Internet.)</p> - -<p>Please also read the next paragraphs to determine whether you -want/need to download network install CDs, update CDs or source -CDs.</p> - -# ============================================================ - -<toc-add-entry name="netinst">What is a <q>netinst</q> or <q>network install</q> -CD?</toc-add-entry> - -<p>To quote the <a href="../netinst/">network install page</a>: A -<q>network install</q> or <q>netinst</q> CD is a single CD which enables you to -install the entire operating system. This single CD contains just the -minimal amount of software to start the installation and fetch the -remaining packages over the Internet.</p> - -<p>If you only want to install Debian on a single machine which has a -fast Internet connection, the network install may be the fastest and -easiest option for you: You only download the packages that you -selected for installation on your machine, which saves both time and -bandwidth.</p> - -# ============================================================ - -<toc-add-entry name="update-cd">What are the <q>update</q> -CDs/DVDs?</toc-add-entry> - -<p>Update CDs/DVDs are CDs/DVDs which contain all the packages that -changed between a major release version (e.g. 7.<strong>0</strong>, -8.<strong>0</strong>, etc.) and a later point release of that stable -distribution. For example, if you already have the full set of -<q>debian-8.0.0</q> CDs/DVDs, you can add the -<q>debian-update-8.2.0</q> disc set to turn this <q>debian-8.0.0</q> -set into a <q>debian-8.2.0</q> set.</p> - -<p>This type of CD/DVD is intended for vendors having large amounts of -pressed versions of CDs/DVDs (which makes them cheaper than -individually burned CDs/DVDs). If you order CDs/DVDs from such a -vendor, it is possible that you'll receive CDs/DVDs for a slightly -older point release, plus some update CDs/DVDs for the latest -revision. This is a perfectly acceptable way of distributing Debian on -CD/DVD.</p> - -<p>Of course, this type of CD/DVD can also be useful to you as an end user; -instead of creating the full set of CDs/DVDs for each new revision of a -release, you only need to download and burn update CDs/DVDs for -your architecture.</p> - -<p>Note that update CDs/DVDs are not meant to boot, they just contain the -packages needed to upgrade an existing installation. If you don't have -that existing installation, then you'll need to use the normal -installation CDs/DVDs. After the new system is booted, the updated CD/DVD can be added with -<code>apt-cdrom add</code>.</p> - -<p>Now, what if for some reason you do not want to download the update -CD/DVD even though you already have the full set of CDs/DVDs/BDs for -the previous revision? In this case, you should consider using <a -href="../jigdo-cd/">jigdo</a>'s <q>update</q> feature: jigdo can read -the contents of the old CDs/DVDs/BDs, download only those files that -have changed for the new CDs/DVDs, and create the full set of new -CDs/DVDs/BDs. Still, it will have done this by downloading only about -the same amount of data as for an update CD/DVD.</p> - -# ============================================================ - -<toc-add-entry name="source-cd">What are the <q>source</q> -CDs?</toc-add-entry> - -<p>There are two types of images, the <q>binary</q> CDs that contain -precompiled, ready-to-run programs, and the <q>source</q> CDs that -contain the source code for the programs. The vast majority of -people do not need the source CDs; you should not download them -unless you really have a good reason for it.</p> - -# ============================================================ - -<toc-add-entry name="nonfree">Where is the CD image with -non-free?</toc-add-entry> - -<p>Debian has a quite strict view with regard to the licenses of -software: Only software that is Free in the sense of the -<a href="$(HOME)/social_contract#guidelines">Debian Free Software -Guidelines</a> is allowed into the actual distribution. All the other, -<q>non-free</q> software (for example, software for which source code is not -available) is not supported officially.</p> - -<p>The official CDs may freely be used, copied and sold by anyone anywhere -in the world. Packages of the <q>non-free</q> category have restrictions that -conflict with this, so these packages are not placed on the official -CDs.</p> - -<p>Sometimes, someone is kind enough to create unofficial non-free -CDs. If you cannot find any links on this website, you can try -<a href="#mailing-list">asking on the debian-cd mailing list</a>.</p> - -# ============================================================ - -<toc-add-entry name="official">What's the difference between official -and unofficial images?</toc-add-entry> - -<p>Official images are built by a member of the Debian CD team and -have undergone some testing to ensure they work. Once they have been -released, the images never change - if they turn out to be broken, a -new set with a different version number is released.</p> - -<p>Unofficial images can be built by anyone - CD team members, other -Debian developers or even advanced Debian users. Typically, they are -more up-to-date, but have received less testing. Some have new -features (e.g. installation support for new hardware), or contain -additional software packages which are not part of the Debian archive.</p> - -# ============================================================ - -<toc-add-entry name="live-cd">Is a Debian <q>live image</q> -available?</toc-add-entry> - -<p>Yes. A so-called <q>live image</q> (<q>live CD</q>), or more -precisely, a <q>live system</q>, is a complete system prepared for a -DVD, USB key or other medium. You do not need to install anything on -the hard drive. Instead you boot from the medium (DVD or USB key) and -are able to start working on the machine right away. All programs run -directly from the medium.</p> - -<p>The <a href="$(HOME)/devel/debian-live/">Debian Live Project</a> produces -<a href="../live/">live image files</a> for a variety of system types and -media.</p> - -# ============================================================ - -<toc-add-entry name="bootable">The CD/DVD/BD fails to boot! / From -which disc should I boot?</toc-add-entry> - -<p>Only the first CD/DVD/BD in a set is bootable.</p> - -<p>If your Debian disc fails to boot, first ensure that you have -correctly written it to the medium - please <a href="#what-is">see the -explanation above</a>. Additionally, please check whether your BIOS is -set up to boot from your optical or USB drive.</p> - -# ============================================================ - -<toc-add-entry name="arch">Where are the images for M68K, Hurd or -other architectures?</toc-add-entry> - -<p>Depending on the state of support for a certain architecture, -CD/DVD images are available from different places:</p> - -<ul> - - <li>If the architecture you are looking for is officially - supported by the current <a href="$(HOME)/releases/stable/">stable - release</a>, see the <a href="../"><q>Debian on CD</q></a> page for - the available download options.</li> - - <li>If a Debian port for an architecture exists, but has not - yet been released officially, CD images may or may not be - available. Again, see the <a href="../"><q>Debian on CD</q></a> page - in - contrast to stable images, only one download option may be - supported, so have a look at both the <q>jigdo</q> and <q>HTTP</q> - sections.</li> - - <li>For the Debian port to the GNU/Hurd, see the - <a href="$(HOME)/ports/hurd/hurd-cd">page about unofficial Hurd CDs</a>. - - <li>Otherwise, check the <a href="$(HOME)/ports/">Debian port pages</a> - for the architecture you are interested in.</li> - -</ul> - -# ============================================================ - -<toc-add-entry name="unstable-images">Are images for the <q>unstable</q> -distribution available?</toc-add-entry> - -<p>There are no <q>unstable</q> full CD/DVD/BD images. Due to the fact -that the packages in <q>unstable</q> change so quickly, it is more -appropriate for people to download and install <q>unstable</q> using a -normal Debian HTTP mirror.</p> - -<p>If you are aware of the <a href="../../releases/unstable/">risks of -running unstable</a>, but still want to install it, you have a few -choices:</p> - -<ul> - - <li>Install <q>testing</q> using a <a href="../netinst/">netinst - image</a>, then upgrade to <q>unstable</q> by changing the entries in - your <tt>/etc/apt/sources.list</tt>. To avoid unnecessary downloads - and package upgrades, it is advisable to install a minimal - <q>testing</q> system first and only to install most of the software - (e.g. desktop environment) after the switch to <q>unstable</q>.</li> - - <li>Use the stable installer to install a minimal <q>stable</q> - system and then change your <tt>/etc/apt/sources.list</tt> file - to use <q>testing</q> and do an <tt>apt-get update</tt> and - <tt>apt-get dist-upgrade</tt>. Finally, install the packages you - desire. This method is the most likely to - work of those presented here.</li> - - <li>Be a tester of the <q>testing</q> installer and install - <q>testing</q> using a netinst image, then upgrade to - <q>unstable</q> by changing the entries in your - <tt>/etc/apt/sources.list</tt>. To avoid unnecessary downloads - and package upgrades, it is advisable to install a minimal - <q>testing</q> system first and only to install most of the - software (e.g. desktop environment) after the switch to - <q>unstable</q>. Then <tt>apt-get update</tt> and - <tt>apt-get -u dist-upgrade</tt> - - then you have a sid release.</li> - - <li>Use a netboot <q>mini.iso</q> image. You will find it on any of - the Debian mirrors under - debian/dists/unstable/main/installer-*/current/images/netboot/mini.iso. During - the installation choose <q>Advanced options</q> -> <q>Expert - install</q>. In the step <q>Choose a mirror of the Debian - archive</q> choose version <q>sid - unstable</q>.</li> - -</ul> - -# ============================================================ - -<toc-add-entry name="search-for-package">Which CD/DVD/BD image -contains package XYZ?</toc-add-entry> - -<p>To find out which image contains a certain file, use -the <a href="https://cdimage-search.debian.org">cdimage search -tool</a>. It has knowledge of just about all the Debian CDs/DVDs/BDs -produced by Debian since the 3.0 (Woody) release, covering all the -official releases (both older archived releases and the current stable -release) and the current sets of daily and weekly testing builds. </p> - -# ============================================================ - -<toc-add-entry name="list-image-contents">Can I have a list of all the -packages contained in an image?</toc-add-entry> - -<p> Yes. Look -on <a href="https://cdimage.debian.org/cdimage/">cdimage.debian.org</a> -for the corresponding <tt>.list.gz</tt> file - it will list all the -packages and source files included in the image. For Debian Live -images, you can find in the same directory as the image files some -similarly named files suffixed with <tt>.packages</tt>. Download these -and then search them for the desired package name.</p> - -# ============================================================ - -<toc-add-entry name="outdated">The software on the official CDs is -outdated - why don't you release a new version?</toc-add-entry> - -<p>We only make official releases of the <q>stable</q> distribution -when we think they truly deserve that name. Unfortunately, this means -that stable releases only happen about every 2 years...</p> - -<p>If you require more recent versions of some of the software in -Debian, you can install <q>stable</q> and then upgrade (via the net) -those parts you want to the versions from <q>testing</q> - it is -possible to mix software from the different releases.</p> - -<p>Alternatively, try out the images of <q>testing</q> that are -generated automatically every week. More information about <a -href="../../security/faq#testing"><q>testing</q> security support</a> -is available from the security FAQ.</p> - -<p>If you only need newer versions of specific packages, you can also -try the <q>backports</q> service, which takes packages from testing -and modifies them to work on stable. This option may be safer than -installing the same package directly from testing.</p> - -# ============================================================ - -<toc-add-entry name="newest">How do I know if I am downloading the -newest images?</toc-add-entry> - -<p>The note at the bottom of the <a href="../"><q>Debian on CD</q></a> page -always shows the version number of the latest -release.</p> - -# ============================================================ - -<toc-add-entry name="verify">How can I verify the downloaded ISO -images and written optical media?</toc-add-entry> - -<p>Detailed information on how to authenticate the signed checksum -files containing the checksums of the ISO image files is available on -the <a href="../verify">authenticity verification page</a>. After -cryptographically verifying the checksum files, we can check that: -</p> - -<ul> - <li>Checksums of the <em>downloaded ISO image files</em> match those - found in the checksum files. Computing the checksum of the ISO image - files is performed by tools such as <q>sha512sum</q> and <q>sha256sum</q>. - </li> - <li>Checksums of already <em>written optical media</em> match those - found in the checksum files. This is a slightly more difficult - operation to describe. </li> -</ul> - -<p>The problem with the verification of written optical media is that -some media types will possibly return more bytes than those found in -the ISO image. This trailing garbage is impossible to avoid with CD -written in TAO mode, incrementally recorded DVD-R[W], formatted -DVD-RW, DVD+RW, BD-RE, and also with USB keys. Therefore, we need to -read exactly the same number of sectors of data from the media as are -found in the ISO image itself; reading any more bytes from the media -will alter the checksum result.</p> - -<ul> - <li>The <q>isosize</q> program can be used to find out the appropriate - amount of bytes to be read from the optical media. It shows the - <q>sector count</q> and the <q>sector size</q> from the optical media, - where <q><device></q> is the device file of the loaded optical media. - <br/><tt>$ /sbin/isosize -x <device></tt> - <br/><tt>sector count: 25600, sector size: 2048 - </tt> - </li> - <li>Then <q>sector count</q> and <q>sector size</q> are passed to <q>dd</q> - to read the appropriate amount of bytes from the optical media and the byte - stream is then piped to the appropriate checksum tool (sha512sum, sha256sum, - etc). - <br/><tt>$ dd if=<device> count=<sector count> bs=<sector size> | sha512sum - </tt> - </li> - <li>The computed checksum is to be compared against the corresponding checksum found - in the appropriate checksum file (SHA512SUMS, SHA256SUMS, etc). - </li> -</ul> - -<p>Alternatively, there is a useful helper script called <a -href="https://people.debian.org/~danchev/debian-iso/check_debian_iso"> -check_debian_iso</a> which can verify <em>ISO image files</em> and -<em>optical media</em>, reading the appropriate amount of bytes from -media then computing the checksum and comparing it against the -checksum file.</p> - -<ul> - <li><em>ISO image file verification.</em> - This will compare the checksum of the debian-6.0.3-amd64-netinst.iso - image file against the corresponding checksum found in the SHA512SUMS - checksum file. - <br/><tt>$ ./check_debian_iso SHA512SUMS debian-6.0.3-amd64-netinst.iso</tt> - </li> - <li><em>Optical media verification.</em> - This will compare the checksum of the media accessible as /dev/dvd against the - checksum of debian-6.0.3-amd64-DVD-1.iso as found in the SHA512SUMS - checksum file. Note that the ISO image file itself is not needed, - its name is merely used to locate the corresponding checksum in - the checksum file. - <br/><tt>$ ./check_debian_iso SHA512SUMS debian-6.0.3-amd64-DVD-1.iso /dev/dvd</tt> - </li> -</ul> - -# ============================================================ - -<toc-add-entry name="small-dvd">Why is my downloaded DVD image smaller -than 1 GB when it should be larger than -4 GB?</toc-add-entry> - -<p><a id="wget-dvd"></a>Most likely, the tool you use for downloading -the image does not have large file support, i.e. it has problems -downloading files larger than 4 GBytes. The usual symptom for -this problem is that when you download the file, the file size -reported by your tool (and the amount of data that it downloads) is -too small by exactly 4 GB. For example, if the DVD image is -4.4 GB, your tool will report a size of 0.4 GB.</p> - -<p>Some old versions of <tt>wget</tt> also suffer from this problem - -either upgrade to a version of <tt>wget</tt> which does not have this -restriction or use the <tt>curl</tt> command line download tool: -<q><tt>curl -C - </tt><i>[URL]</i></q></p> - -# ============================================================ - -<toc-add-entry name="record-unix">How do I write an ISO image under -Linux/Unix?</toc-add-entry> - -<p>Note that Debian ISO images for i386, amd64 and arm64 are also -bootable from a USB key; see <a href="#write-usb">below</a>.</p> - -<p><a href="https://www.gnu.org/software/xorriso/xorriso.html">xorriso</a> -for all optical media types (also doable as non-root user): -<br/><tt>xorriso -as cdrecord -v dev=/dev/sr0 -eject debian-x.y.z-arch-MEDIUM-NN.iso</tt> -<br/>In order to get the full nominal speed when writing to BD-RE -(i.e. without the slowdown caused by the drive's internal defect -management), add the option <tt>stream_recording=on</tt>. - -<p><a href="http://fy.chalmers.se/~appro/linux/DVD+RW/">growisofs</a> -for DVD and BD optical media types: -<br/><tt>growisofs -dvd-compat -Z /dev/sr0=debian-x.y.z-arch-MEDIUM-NN.iso</tt> -</p> - -<p><a href="https://packages.debian.org/sid/wodim">wodim</a> -for CD optical media type: -<br/><tt>wodim -v dev=/dev/sr0 -eject -sao debian-x.y.z-arch-CD-NN.iso</tt> -</p> - -<p>For Linux, there are also the X programs -<a href="https://wiki.gnome.org/Apps/Brasero">Brasero</a>, -<a href="https://userbase.kde.org/K3b">K3B</a> and -<a href="http://www.xcdroast.org/">X-CD-Roast</a>, -to name a few. Note that they're all frontends to the previously -mentioned low-level burning applications.</p> - -<dl> - <dt><strong><a id="brasero" - href="https://wiki.gnome.org/Apps/Brasero">Brasero</a></strong></dt> - - <dd>Select the button <i>Burn Image</i>. Then click on - <i>Click here to select a disc image</i>, browse and select your - downloaded ISO file, check whether the settings under - <i>Properties</i> are correct and choose - <i>Create Image</i>.</dd> - - <dt><strong><a id="k3b" - href="https://userbase.kde.org/K3b">K3b</a></strong></dt> - - <dd>Select the menu entry <i>Tools - CD - Burn CD Image</i>. In the - dialog that opens, enter the path to the image in the <i>Image to - Burn</i> field, check whether the other settings are correct, then - click on <i>Start</i>.</dd> - - <dt><strong><a id="xcdroast" - href="http://www.xcdroast.org/">X-CD-Roast</a></strong></dt> - - <dd>After the program has started, click on -<i>Setup</i> and choose the <i>HD settings</i> tab. Copy the Debian CD -image to one of the directories that are displayed in the table. (If -the table is empty, enter the path of a directory you want to use for -temporary storage, and click on <i>Add</i>.) Click on <i>OK</i> to -exit the setup. Next, select <i>Create CD</i> and then <i>Write -Tracks</i>. Choose the <i>Layout tracks</i> tab, select the line -displaying the image filename and click on <i>Add</i>, then click on -<i>Accept track layout</i>. Finally, click on <i>Write tracks</i>.</dd> - -</dl> - -# ============================================================ - -<toc-add-entry name="record-windows">How do I write an ISO image under -Windows?</toc-add-entry> - -<p>On recent versions of Windows, this can be done natively by -right-clicking the ISO and selecting "Burn image to disk (or similar)"</p> - -<p>This might be a little problem on older versions of Windows, as -many Windows image-burning programs use their own formats for CD -images. To burn the <tt>.iso</tt> images you will most likely have to -use a <q>special</q> menu. Look for options like <q>ISO9660 file</q>, -<q>Raw ISO image</q> or <q>2048 bytes/sector</q>. (Note: other -bytes/sector values are fatal!) Some programs do not offer these -choices; use another burning program instead (ask a friend or -colleague). Here is some information about how to write CD images with -specific products:</p> - -<dl> - - <dt><strong><a name="imgburn" - href="https://www.imgburn.com/">ImgBurn</a></strong> - (Freeware)</dt> - - <dd>There are <a href="https://www.imgburn.com/index.php?act=screenshots#isowrite">screenshots</a> of how to write an image to CD/DVD</dd> - - <dt><strong><a name="cdburnerxp" - href="https://cdburnerxp.se/">CDBurnerXP Pro</a></strong> - (Freeware)</dt> - - <dd>The process of writing an <tt>.iso</tt> image is described - <a href="https://cdburnerxp.se">in the program's manual</a>.</dd> - - <dt><strong><a NAME="adaptec" href="https://www.roxio.com/">Roxio</a> Easy-CD Creator</strong></dt> - - <dd>From the <i>File</i> menu, choose <i>Create CD from - image...</i>. Then select the <q>.iso</q> file type, and the correct - image. This opens up the CD creation setup GUI, from there - ensure that all the information for your CD-R is correct. In the - <i>Create options</i> portion, choose <i>Create CD</i>; under - <i>Write method</i>, choose <i>Track at once</i> and <i>Close - CD</i>.</dd> - - <dt><strong><a NAME="nero">Nero</a> from - <a href="http://www.ahead.de/">Ahead Software</a></strong></dt> - - <dd>Disable the Wizard, then select <i>Burn Image</i> from the - <q>File</q> or <q>Recorder</q> menu. Select <i>All Files</i> in the file - selection window if necessary. Select the <tt>.iso</tt> file, click - OK in the <q>this is a foreign file</q> dialogue box, in case one is - displayed. In the - option box that opens, the defaults should be okay: <q><i>Data - Mode 1</i></q>, <q><i>Block Size 2048</i></q>, <q><i>Raw Data, Scrambled, - and Swapped</i></q> <strong>not</strong> selected, and <i>Image - Header</i> and <i>Image Trailer</i> left at 0. Click OK. Under - <i>Write CD</i> or <i>Burn</i>, use the default options, e.g. <i>Write</i> - and <i>Determine maximum speed</i>, plus check the <i>Finalize - CD</i> option.</dd> - - <dt><strong><a NAME="resource-kit-tools" - href="https://www.microsoft.com/en-us/download/details.aspx?id=17657">Microsoft - Resource Kit Tools</a></strong></dt> - - <dd>The command-line Resource Kit Tools are provided by Microsoft - free of charge, they work with Windows 2003 and XP. Two programs to - write images to CD and DVD are included, they are named - <tt>Cdburn.exe</tt> and <tt>Dvdburn.exe</tt>. Usage of the programs - is described in the accompanying help file - essentially, the - command to be executed is something like - <tt>cdburn drive: iso-file.iso /speed max</tt></dd> - -</dl> - -<p>If you can provide updated information or details for other -programs, please <a -href="mailto:debian-cd@lists.debian.org" ->let us know</a>. - -# ============================================================ - -<toc-add-entry name="record-mac">How do I write an ISO image under -Mac OS?</toc-add-entry> - -<p>The <strong>Toast</strong> program for Mac OS is reported to work fine with -<tt>.iso</tt> files. You can be extra-safe by giving it the -creator code <i>CDr3</i> (or possibly <i>CDr4</i>) and type code -<i>iImg</i> using e.g. FileTyper. Double-clicking on the file will -then open up Toast directly, without having to drag-and-drop or go -via the File-Open menu.</p> - -<p>Another option is <strong>Disk Utility</strong> (included with Mac OS -X 10.3 and higher): After opening the Disk Utility application (in -the <tt>/Applications/Utilities</tt> folder), select -<i>Burn...</i> in the <i>Image</i> menu and choose the CD -image to burn. Ensure that the settings are correct, then click on -<i>Burn</i>.</p> - -<p>Another option is <strong>Disk Copy</strong> (included with Mac OS -X 10.1 and higher): After opening the Disk Copy application (in -the <tt>/Applications/Utilities</tt> folder), select -<i>Burn Image...</i> in the <i>Image</i> menu and choose the CD -image to burn. Ensure that the settings are correct, then click on -<i>Burn</i>.</p> - - -# ============================================================ - -<toc-add-entry name="write-usb">How do I write a CD/DVD/BD image to a -USB flash drive?</toc-add-entry> - -<p>Several of the Debian and Debian Live images, notably all i386, -amd64 and arm64 images, are created using the <i>isohybrid</i> -technology, which means that they may be used in two different -ways:</p> - -<ul> - <li>They may be written to CD/DVD/BD and used as normal for CD/DVD/BD booting.</li> - <li>They may be written to USB flash drives, bootable directly from the BIOS / EFI firmware of most PCs.</li> -</ul> - -<p>On a Linux machine, simply use the <q>cp</q> command, to copy an -image to a USB flash drive:</p> - -<p><code>cp <file> <device></code></p> - -<p>Alternatively you can also use <q>dd</q>:</p> - -<p><code>dd if=<file> of=<device> bs=4M; sync</code></p> - -<p>where:</p> -<ul> - <li><file> is the name of the input image, e.g. <q>netinst.iso</q> - <li><device> is the device matching the USB flash drive, - e.g. /dev/sda, /dev/sdb. <em>Be careful to make sure you have the right - device name</em>, as this command is capable of writing over your hard - disk just as easily if you get the wrong one!</li> - <li><q>bs=4M</q> tells dd to read/write in 4 megabyte chunks for - better performance; the default is 512 bytes, which will be much - slower - <li>The <q>sync</q> is to make sure that all the writes are flushed out - before the command returns. -</ul> - -<p>Additionally to the method above for Linux systems, there is also - the <a NAME="win32diskimager" - href="https://sourceforge.net/projects/win32diskimager/">win32diskimager</a> - program available, which allows writing such bootable USB flash - drives under Windows. <b>Hint:</b> win32diskimager will apparently - only list input files named <i>*.img</i> by default, while the - Debian images are named <i>*.iso</i>. Change the filter to - <i>*.*</i> if you use this tool. -</p> - -<p>Please note, that Debian advises not using <q>unetbootin</q> for - this task. It can cause difficult-to-diagnose problems with booting - and installing, so is not recommended. -</p> - -# ============================================================ - -<toc-add-entry name="whatlabel">How should I label the -discs?</toc-add-entry> - -<p>There is no obligatory way of labeling. However, we suggest you -use the following scheme to ensure interchangeability:</p> - -<div class="cdflash"> - <p>Debian GNU/{Linux|Hurd|kFreeBSD} - <version>[<revision>]<br />Official - {<architecture>} {CD|DVD|BD}-<number></p> -</div> - -<p>For example:</p> - -<div class="cdflash"> - <p>Debian GNU/Linux 6.0.3<br />Official i386 - CD-1</p> -</div> - -<div class="cdflash"> - <p>Debian GNU/Linux 6.0.3<br />Official - amd64 DVD-2</p> -</div> - -<div class="cdflash"> - <p>Debian GNU/Linux 6.0.3<br />Official - source BD-1</p> -</div> - -<div class="cdflash"> - <p>Debian GNU/kFreeBSD 6.0.3<br />Official i386 - Netinst CD</p> -</div> - -<p>If you have enough space, you can also add the codename to the -first line, as in: <i>Debian GNU/Linux 6.0.3 <q>Squeeze</q></i>.</p> - -<p>Note that you are allowed to use the <em>Official</em> -designation <strong>only</strong> on CDs the image of which has a -checksum that matches the one from the -<a href="../jigdo-cd/#which">jigdo -files of official releases</a>. -Any CD that has no matching checksum (e.g. your own creations) must be -clearly labelled as <em>Unofficial</em>, for example:</p> - -<div class="cdflash"> - <p>Debian GNU/Linux 6.0.3<br />Unofficial - Non-free</p> -</div> - -<p>In the case of official weekly snapshots, version numbers like -<q>6.0.3</q> should not be used to avoid confusion with released -Debian versions. Instead, label the image with a codename like -<q>etch</q> or a distribution name like <q>testing</q>. Also add -<q>Snapshot</q> and the date of the snapshot to help identify it:</p> - -<div class="cdflash"> - <p>Debian GNU/Linux <q>etch</q><br /> - Official Snapshot alpha Binary-2<br /> - 2005-06-17</p> -</div> - -# ============================================================ - -<toc-add-entry name="artwork">Is there any artwork for discs and -covers?</toc-add-entry> - -<p>There is no official layout for the cover, back and label of a -Debian CD/DVD/BD, but a number of people have produced nice-looking -images. Please see the separate <a href="../artwork/">artwork -page</a>. - -# ============================================================ - -<toc-add-entry name="old">Are old CD/DVD/BD images still -available?</toc-add-entry> - -<p>Some older images are available from the <a -href="https://cdimage.debian.org/cdimage/archive/">archive -section on cdimage.debian.org</a>. For example, you might want to try -out older images if you need support for a certain (sub)architecture -which has been dropped for a newer release.</p> - -<p>Note that when you install using a really old CD/DVD (pre 4.0, -Etch), the contents of <tt>/etc/apt/sources.list</tt> will reference -the <em>current</em> stable Debian release by default. This means that -any upgrade over the net will upgrade to the current stable -release.</p> - -# ============================================================ - -<toc-add-entry name="lan-install">What is the best way of installing -Debian on many interconnected computers?</toc-add-entry> - -<p>If you want to install Debian on a large number of machines and -then keep all these installations up-to-date (e.g. security updates), -installing from optical media is not ideal, but then neither is -installing via the Internet, because the packages will have to be -downloaded again for each machine. In this case, you should set up a -local cache, the three options being:</p> - -<ul> - - <li><em>Make disc contents available via HTTP:</em> Download the - images, then make their contents available to your LAN on a local - mirror. The individual machines can use this mirror as if it - were a regular Debian server. For example, if the contents of a CD - are available under the URL <tt>http://10.0.0.1/cd1/</tt>, machines - in the local network can use the packages from the CD with the - following line in their <tt>/etc/apt/sources.list</tt>:<br /> - <tt>deb http://10.0.0.1/cd1/ stable main contrib</tt><br /> - A different URL and a separate entry in <tt>sources.list</tt> is - necessary for each CD.</li> - - <li><em>Instruct your HTTP proxy to cache .deb files:</em> - Configure the proxy to keep .deb files for a long time, then set - <tt>http_proxy</tt> in your environment on each machine to point - at the cache, and use apt's HTTP acquisition method.<br /> - This gives you most of the benefits of running a mirror, with - none of the admin hassle. Since you can set limits on the - proxy's disk usage, it works even for sites with limited disk - space, and it has the advantage over mirroring that you only - download those packages you install, which saves bandwidth. - Squid can be told to keep the files by adding a line to - <tt>/etc/squid/squid.conf</tt>:<br /><tt>refresh_pattern debian.org/.*.deb$ 129600 100% 129600</tt></li> - - <li><em>Set up a private Debian packages mirror:</em> Beware - that the Debian archive has grown to a tremendous size! Refer to - the <a href="$(HOME)/mirror/">mirroring page</a> for details.</li> - -</ul> - -<p>Installing on a large number of machines can be tricky. -<a href="https://fai-project.org/">Fully automatic -installation</a> (FAI), which is also available as a Debian -package, may help you with this task.</p> - -# ============================================================ - -<toc-add-entry name="diy">I have a local Debian mirror and want to -create my own CD/DVDs/BDs/. How do I do this?</toc-add-entry> - -<p>Apart from a <a href="$(HOME)/mirror/">local Debian mirror</a>, you -also need plenty of disc space. The image creation scripts are -packaged in the <em>debian-cd</em> package. However, it is usually a -better idea to use the latest code from git. (Still, you should have a -look at the package's dependencies to ensure you have all the -necessary tools.)</p> - -<p>To get the latest git version, make sure you have git -installed. From an empty directory, give the following command:</p> - -<div class="centerblock"> -<p> -<tt>git clone https://salsa.debian.org/images-team/debian-cd.git</tt> -</p> -</div> - -<p>Should you try to use the scripts, check the -<a href="https://lists.debian.org/debian-cd/">debian-cd mailing list -archive</a> for solutions to the questions that will inevitably -show up. :-)</p> - -# ============================================================ - -<toc-add-entry name="become-cd-mirror">How do I become a mirror for -Debian CD/DVD/BD images?</toc-add-entry> - -<p>The necessary steps to set up your debian-cd image mirror and keep -it up to date are <a href="../mirroring/">described on a separate -page</a>.</p> - -# ============================================================ - -<toc-add-entry name="not-all-images">Some Images are missing! -Only the first n images are available! Where is the rest?</toc-add-entry> - -<p>We don't store/serve the full set of ISO images for all architectures, -to reduce the amount of space taken up on the mirrors. You can -<a href="#why-jigdo">use the jigdo tool</a> to recreate the missing ISO -images instead.</p> - -# ============================================================ diff --git a/greek/CD/free-linux-cd.wml b/greek/CD/free-linux-cd.wml deleted file mode 100644 index 1680270cf37..00000000000 --- a/greek/CD/free-linux-cd.wml +++ /dev/null @@ -1,24 +0,0 @@ -#use wml::debian::cdimage title="Free Linux CD" NOHEADER=true BARETITLE=true -#use wml::debian::toc -#use wml::debian::translation-check translation="4dc6aa7c1925469f923a41d0b3ac63f8b2d27ee2" maintainer="galaxico" - -# Translators, I would not bother translating this file. Its sole -# purpose is to prevent stupid "Please send me a free Linux CD" mails -# to debian-cd. Apparently, this is another self-perpetuating Google -# flop: Whenever people from India (or somewhere from that part of the -# world) search for "Free Linux CD" with Google, the archived "free -# Linux CD" mails from lists.d.o turn up at the very top. Without -# bothering to read the replies to the archived mails, people copy the -# mail they found and send it to debian-cd. -# -- Richard Atterer, 2006-04-11 - -<h1>Free Linux CD</h1> - -<p>The Debian project does <em>not</em> send out free CDs. Please do -not send mail to the debian-cd mailing list about this.</p> - -<p>Instead, either <a href="./">download</a> the CD images yourself or -<a href="vendors/">buy</a> them from one of our CD -vendors. Alternatively, search for a Linux User Group (LUG) in your -area, you may be able to get a <em>free Linux CD</em> at a LUG -meeting.</p> diff --git a/greek/CD/http-ftp/Makefile b/greek/CD/http-ftp/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/CD/http-ftp/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/CD/http-ftp/index.wml b/greek/CD/http-ftp/index.wml deleted file mode 100644 index 2a83973c749..00000000000 --- a/greek/CD/http-ftp/index.wml +++ /dev/null @@ -1,161 +0,0 @@ -#use wml::debian::cdimage title="Downloading Debian CD/DVD images via HTTP/FTP" BARETITLE=true -#include "$(ENGLISHDIR)/releases/info" -#include "$(ENGLISHDIR)/releases/images.data" -#use wml::debian::translation-check translation="f4fe84f1063f34ac4bfb75eb963e6fa71ba0e642" maintainer="galaxico" - -<div class="tip"> -<p><strong>Please do not download CD or DVD images with your web browser the way -you download other files!</strong> The reason is that if your download -aborts, most browsers do not allow you to resume from the point where it -failed.</p> -</div> - -<p>Instead, please use a tool that supports resuming - typically -described as a <q>download manager</q>. There are many browser plugins -that do this job, or you might want to install a separate -program. Under Linux/Unix, you can use <a -href="http://aria2.sourceforge.net/">aria2</a>, <a -href="http://dfast.sourceforge.net/">wxDownload Fast</a> or (on the -command line) <q><tt>wget -c </tt><em>URL</em></q> or -<q><tt>curl -C - -L -O </tt><em>URL</em></q>. There -are many more options listed in a <a -href="https://en.wikipedia.org/wiki/Comparison_of_download_managers">comparison -of download managers</a>.</p> - -<p>The following Debian images are available for -download:</p> - -<ul> - - <li><a href="#stable">Official CD/DVD images of the <q>stable</q> release</a></li> - - <li><a href="#firmware"><b>Unofficial</b> CD/DVD images for <q>stable</q> with - <b>non-free</b> firmware included</a></li> - - <li><a href="https://cdimage.debian.org/cdimage/weekly-builds/">Official - CD/DVD images of the <q>testing</q> distribution (<em>regenerated - weekly</em>)</a></li> - -<comment> - <li>Unofficial CD/DVD images of the <q>testing</q> and <q>unstable</q> - distributions by fsn://HU — <a href="#unofficial">see below</a></li> -</comment> - -</ul> - -<p>See also:</p> -<ul> - - <li>A complete <a href="#mirrors">list of <tt>debian-cd/</tt> mirrors</a></li> - - <li>For <q>network install</q> (150-300 MB) images, - see the <a href="../netinst/">network install</a> page.</li> - - <li>For <q>netinst</q> images of the <q>testing</q> - release, both daily builds and known working snapshots, see the <a - href="$(DEVEL)/debian-installer/">Debian-Installer page</a>.</li> - -</ul> - -<hr /> - -<h2><a name="stable">Official CD/DVD images of the <q>stable</q> release</a></h2> - -<p>To install Debian on a machine without an Internet connection, -it's possible to use CD images (700 MB each) or DVD images (4.7 GB each). -Download the first CD or DVD image file, write it using a CD/DVD recorder (or a -USB stick on i386 and amd64 ports), and then reboot from that.</p> - -<p>The <strong>first</strong> CD/DVD disk contains all the files necessary -to install a standard Debian system.<br /> -To avoid needless downloads, please do <strong>not</strong> download -other CD or DVD image files unless you know that you need packages on -them.</p> - -<div class="line"> -<div class="item col50"> -<p><strong>CD</strong></p> - -<p>The following links point to image files which are up to 700 MB -in size, making them suitable for writing to normal CD-R(W) media:</p> - -<stable-full-cd-images /> -</div> -<div class="item col50 lastcol"> -<p><strong>DVD</strong></p> - -<p>The following links point to image files which are up to 4.7 GB -in size, making them suitable for writing to normal DVD-R/DVD+R and -similar media:</p> - -<stable-full-dvd-images /> -</div><div class="clear"></div> -</div> - -<p>Be sure to have a look at the documentation before you install. -<strong>If you read only one document</strong> before installing, read our -<a href="$(HOME)/releases/stable/i386/apa">Installation Howto</a>, a quick -walkthrough of the installation process. Other useful documentation includes: -</p> -<ul> -<li><a href="$(HOME)/releases/stable/installmanual">Installation Guide</a>, - the detailed installation instructions</li> -<li><a href="https://wiki.debian.org/DebianInstaller">Debian-Installer - Documentation</a>, including the FAQ with common questions and answers</li> -<li><a href="$(HOME)/releases/stable/debian-installer/#errata">Debian-Installer - Errata</a>, the list of known problems in the installer</li> -</ul> - -<hr /> - -# Translators: the following paragraph exists (in this or a similar form) several times in webwml, -# so please try to keep translations consistent. See: -# ./CD/http-ftp/index.wml -# ./CD/live/index.wml -# ./CD/netinst/index.wml -# ./CD/torrent-cd/index.wml -# ./distrib/index.wml -# ./distrib/netinst.wml -# ./releases/<release-codename>/debian-installer/index.wml -# ./devel/debian-installer/index.wml -# -<h2><a name="firmware">Unofficial CD/DVD images with non-free firmware included</a></h2> - -<div id="firmware_nonfree" class="important"> -<p> -If any of the hardware in your system <strong>requires non-free firmware to be -loaded</strong> with the device driver, you can use one of the -<a href="https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/stable/current/">\ -tarballs of common firmware packages</a> or download an <strong>unofficial</strong> image -including these <strong>non-free</strong> firmwares. Instructions how to use the tarballs -and general information about loading firmware during an installation can -be found in the <a href="../../releases/stable/amd64/ch06s04">Installation Guide</a>. -</p> -<p> -<a href="https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/">unofficial -installation images for <q>stable</q> with firmware included</a> -</p> -</div> - -<hr /> - -<h2><a name="mirrors">Registered mirrors of the <q>debian-cd</q> archive</a></h2> - -<p>Note that <strong>some mirrors are not up to date</strong> — -before downloading, check the version number of the images is the -same as the one listed <a href="../#latest">on this site</a>! -Additionally, note that many sites do not mirror the full set of -images (especially the DVD images) due to its size.</p> - -<p><strong>If in doubt, use the <a href="https://cdimage.debian.org/debian-cd/">primary -CD image server</a> in Sweden,</strong> or try -<a href="http://debian-cd.debian.net/">the experimental automatic -mirror selector</a> that will automatically redirect you to a nearby -mirror that is known to have the current version.</p> - -<p>Are you interested in offering the Debian CD images on your -mirror? If yes, see the <a href="../mirroring/">instructions on -how to set up a CD image mirror</a>.</p> - -#use wml::debian::countries -#include "$(ENGLISHDIR)/CD/http-ftp/cdimage_mirrors.list" diff --git a/greek/CD/jigdo-cd/Makefile b/greek/CD/jigdo-cd/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/CD/jigdo-cd/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/CD/jigdo-cd/index.wml b/greek/CD/jigdo-cd/index.wml deleted file mode 100644 index 56591965e36..00000000000 --- a/greek/CD/jigdo-cd/index.wml +++ /dev/null @@ -1,245 +0,0 @@ -#use wml::debian::cdimage title="Downloading Debian CD images with jigdo" BARETITLE=true -#use wml::debian::toc -#include "$(ENGLISHDIR)/releases/info" -#use wml::debian::installer -#include "$(ENGLISHDIR)/releases/images.data" -#include "$(ENGLISHDIR)/devel/debian-installer/images.data" -#use wml::debian::translation-check translation="8f4fd662362387b7d3aa9429a2b5b1ca8dbf2e97" maintainer="galaxico" - -<p>Jigsaw Download, or short <a -href="https://www.einval.com/~steve/software/jigdo/">jigdo</a>, is a -bandwidth-friendly way of distributing Debian CD/DVD images.</p> - -<toc-display/> - -<toc-add-entry name="why">Why jigdo is better than a direct -download</toc-add-entry> - -<p>Because it is faster! For various reasons, there are far fewer -mirrors for CD/DVD images than there are for the "normal" Debian -archive. Consequently, if you download from a CD image mirror, that -mirror will not only be further away from you, it will also be -overloaded, especially just after a release.</p> - -<p>Furthermore, some types of images are not available as full -<tt>.iso</tt> downloads because there is not enough space on our -servers to host them.</p> - -<p>Of course, a "normal" Debian mirror does not carry any CD/DVD -images, so how can jigdo download them there? jigdo achieves this by -downloading individually all the files that are on the CD/DVD. In the -next step, all these files are assembled in one big file which is an -exact copy of the CD/DVD image. However, all this happens behind the -scenes - all that <em>you</em> need to do is tell the download tool -the location of a "<tt>.jigdo</tt>" file to process.</p> - -<p>More information is available from the <a -href="https://www.einval.com/~steve/software/jigdo/">jigdo -homepage</a>. Volunteers willing to help with jigdo development are -always welcome!</p> - -<toc-add-entry name="how">How to download an image with jigdo</toc-add-entry> - -<ul> - - <li>Download a package containing <tt>jigdo-lite</tt>. This is - available directly for installation in the Debian and Ubuntu - distributions in the <tt>jigdo-file</tt> package. For FreeBSD, - install from /usr/ports/net-p2p/jigdo or grab the package - with <tt>pkg_add -r jigdo</tt>. For other installation options - (binaries for Windows, source), check the - the <a href="https://www.einval.com/~steve/software/jigdo/">jigdo - homepage</a>. </li> - - <li>Run the <tt>jigdo-lite</tt> script. It will ask for the URL - of a "<tt>.jigdo</tt>" file to process. (You can also supply - that URL on the command line if you like.)</li> - - <li>From one of the locations listed <a href="#which">below</a>, pick the - "<tt>.jigdo</tt>" files you want to download, and enter their URLs - at the <tt>jigdo-lite</tt> prompt. Each "<tt>.jigdo</tt>" file - corresponds to one "<tt>.iso</tt>" CD/DVD image.</li> - - <li>If you are a first-time user, just press Return at the "Files to - scan" prompt.</li> - - <li>At the prompt "Debian mirror", enter either - <kbd>http://deb.debian.org/debian/</kbd> or - <kbd>http://ftp.<strong><var>XY</var></strong>.debian.org/debian/</kbd>, where - <strong><var>XY</var></strong> is the two-letter code for your country - (for example, <tt>us</tt>, <tt>de</tt>, <tt>uk</tt>. See the current - list of <a href="$(HOME)/mirror/list">available - ftp.<var>XY</var>.debian.org locations</a>.) - - <li>Follow the instructions printed by the script. If all goes well, the - script finishes by calculating a checksum of the generated image and - telling you that the checksum matches that of the original image.</li> - -</ul> - -<p>For a detailed, step-by-step description of this process, have a -look at the <a href="https://tldp.org/HOWTO/Debian-Jigdo/">Debian -jigdo mini-HOWTO</a>. The HOWTO also explains jigdo's advanced -features, such as upgrading an older version of a CD/DVD image to the -current version (by downloading only what has changed, not the entire -new image).</p> - -<p>Once you have downloaded the images and written them to CD/DVD, be -sure to have a look at the <a -href="$(HOME)/releases/stable/installmanual">detailed information -about the installation process</a>.</p> - -<toc-add-entry name="which">Official images</toc-add-entry> - -<h3>Official jigdo files for the <q>stable</q> release</h3> - -<div class="line"> -<div class="item col50"> -<p><strong>CD</strong></p> - <stable-full-cd-jigdo /> -</div> -<div class="item col50 lastcol"> -<p><strong>DVD</strong></p> - <stable-full-dvd-jigdo /> -</div> -<div class="clear"></div> -</div> -<div class="line"> -<div class="item col50"> -<p><strong>Blu-ray</strong></p> - <stable-full-bluray-jigdo /> -</div> -</div> - -<p>Be sure to have a look at the documentation before you install. -<strong>If you read only one document</strong> before installing, read our -<a href="$(HOME)/releases/stable/i386/apa">Installation Howto</a>, a quick -walkthrough of the installation process. Other useful documentation includes: -</p> -<ul> -<li><a href="$(HOME)/releases/stable/installmanual">Installation Guide</a>, - the detailed installation instructions</li> -<li><a href="https://wiki.debian.org/DebianInstaller">Debian-Installer - Documentation</a>, including the FAQ with common questions and answers</li> -<li><a href="$(HOME)/releases/stable/debian-installer/#errata">Debian-Installer - Errata</a>, the list of known problems in the installer</li> -</ul> - -<h3>Official jigdo files for the <q>testing</q> distribution</h3> -<div class="line"> -<div class="item col50"> -<p><strong>CD</strong></p> - <devel-full-cd-jigdo /> -</div> -<div class="item col50 lastcol"> -<p><strong>DVD</strong></p> - <devel-full-dvd-jigdo /> -</div> -</div> - -<hr /> - -<toc-add-entry name="search">Search Contents of CD images</toc-add-entry> - -<p><strong>Which CD/DVD image contains a certain file?</strong> Below, -you can search the lists of files -contained in a wide variety of Debian CD/DVD images. You -can enter several words, each word must match a substring of the -filename. Add e.g. "_i386" to restrict the results to a certain -architecture. Add "_all" to see packages which are identical for all -architectures.</p> - -<form method="get" action="https://cdimage-search.debian.org/"><p> -<input type="hidden" name="search_area" value="release"> -<input type="hidden" name="type" value="simple"> -<input type="text" name="query" size="20" value=""> -# Translators: "Search" is translatable -<input type="submit" value="Search"></p></form> - -<p><strong>What files are contained in a certain image?</strong> If -you need a list of <em>all</em> files that a certain Debian CD/DVD -contains, just look in the image's corresponding <tt>list.gz</tt> file -on <a -href="https://cdimage.debian.org/cdimage/">cdimage.debian.org</a>.</p> - -<hr> - -<toc-add-entry name="faq">Frequently Asked/Answered Questions</toc-add-entry> - -<p><strong>How do I make jigdo use my proxy?</strong></p> - -<p>Load the file <tt>~/.jigdo-lite</tt> (or -<tt>jigdo-lite-settings.txt</tt> for the Windows version) into a text -editor and find the line that starts with "wgetOpts". The following -switches can be added to the line:</p> - -<p><tt>-e ftp_proxy=http://<i>LOCAL-PROXY</i>:<i>PORT</i>/</tt> -<br><tt>-e http_proxy=http://<i>LOCAL-PROXY</i>:<i>PORT</i>/</tt> -<br><tt>--proxy-user=<i>USER</i></tt> -<br><tt>--proxy-passwd=<i>PASSWORD</i></tt></p> - -<p>Of course, substitute the correct values for your proxy server. The -last two options are only necessary if your proxy uses password -authentication. The switches need to be added to the end of the -wgetOpts line <em>before</em> the final <tt>'</tt> character. All -options must be on one line.</p> - -<p>Alternatively, under Linux you can also set up the -<tt>ftp_proxy</tt> and <tt>http_proxy</tt> environment variables, for -example in the file <tt>/etc/environment</tt> or -<tt>~/.bashrc</tt>.</p> - -<p><strong>Aargh! The script fails with an error - have I downloaded all -those MBs in vain?!</strong></p> - -<p>Of course this Should Not Happen(tm), but for various reasons you -may end up in a state where a large "<tt>.iso.tmp</tt>" file has -already been generated and <tt>jigdo-lite</tt> appears to have -problems, telling you repeatedly to try restarting the download. There -are several possible things to try in this case:</p> - -<ul> - - <li>Simply restart the download by pressing Return. Maybe some of - the files could not be downloaded because of timeouts or other - transient errors - another attempt will be made to download any - missing files.</li> - - <li>Try a different mirror. Some Debian mirrors are slightly out of - sync - maybe a different mirror still holds files that were deleted - from the one you specified, or it has already been updated with - files that are not yet present on your mirror.</li> - - <li>Retrieve the missing parts of the image using <tt><a - href="https://rsync.samba.org/">rsync</a></tt>. First, you need to - find out the correct rsync URL of the image you are downloading: - Choose a server that offers rsync access to the <a - href="../mirroring/rsync-mirrors">stable</a> or <a - href="../http-ftp/#testing">testing</a> images, then determine the - correct path and filename. Directory listings can be obtained with - commands like - <tt>rsync rsync://cdimage.debian.org/debian-cd/</tt> - - <br>Next, remove the "<tt>.tmp</tt>" extension from - <tt>jigdo-lite</tt>'s temporary file by renaming it, and pass both - the remote URL and the local filename to rsync: - <tt>rsync rsync://server.org/path/binary-i386-1.iso - binary-i386-1.iso</tt> - - <br>You may want to use rsync's <tt>--verbose</tt> and - <tt>--progress</tt> switches to get status messages, and - <tt>--block-size=8192</tt> to increase its speed.</li> - - <li>If all else fails, your downloaded data is still not lost: Under - Linux, you can loop-mount the <tt>.tmp</tt> file to access the - packages that were already downloaded, and reuse them for generating - an image from a newer jigdo file (such as the latest weekly testing - snapshot if your failed download was also a testing snapshot). To do - this, first issue the following commands as root in the directory - with the broken download: <tt>mkdir mnt; - mount -t iso9660 -o loop *.tmp mnt</tt>. - Next, start a new download in a different directory, and enter the - path of the <tt>mnt</tt> directory at the "Files to scan" - prompt.</li> - -</ul> diff --git a/greek/CD/live/Makefile b/greek/CD/live/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/CD/live/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/CD/live/index.wml b/greek/CD/live/index.wml deleted file mode 100644 index 79ae9dc15a4..00000000000 --- a/greek/CD/live/index.wml +++ /dev/null @@ -1,103 +0,0 @@ -#use wml::debian::cdimage title="Live install images" -#use wml::debian::release_info -#use wml::debian::installer -#include "$(ENGLISHDIR)/releases/images.data" -#use wml::debian::translation-check translation="8c86ac02236495359e82eed0e3b9e29905514fd7" maintainer="galaxico" - -<p>A <q>live install</q> image contains a Debian system that can boot without -modifying any files on the hard drive and also allows installation of Debian -from the contents of the image. -</p> - -<p><a name="choose_live"><strong>Is a live image suitable for me?</strong></a> Here are some things -to consider that will help you decide. -<ul> -<li><b>Flavors:</b> The live images come in several "flavors" -providing a choice of desktop environments (GNOME, KDE, LXDE, Xfce, -Cinnamon and MATE). Many users will find these initial package -selections suitable, installing any additional packages they need from -the network afterwards. -<li><b>Architecture:</b> Only images for the two most popular architectures, -32-bit PC (i386) and 64-bit PC (amd64), are currently provided. -<li><b>Installer:</b> Starting from Debian 10 Buster, the live images contain -the end-user-friendly <a href="https://calamares.io">Calamares Installer</a>, a -distribution-independent installer framework, as alternative to our well known -<a href="$(HOME)/devel/debian-installer">Debian-Installer</a>. -<li><b>Size:</b> Each image is much smaller than the full set of -DVD images, but larger than the network install media. -<li><b>Languages:</b> The images do not contain a complete set of language -support packages. If you need input methods, fonts and supplemental language -packages for your language, you'll need to install these afterwards. -</ul> - -<p>The following live install images are available for download:</p> - -<ul> - - <li>Official <q>live install</q> images for the <q>stable</q> release — <a - href="#live-install-stable">see below</a></li> - -</ul> - - -<h2 id="live-install-stable">Official live install images for the <q>stable</q> release</h2> - -<p>Offered in different flavours, each differing in size as discussed above, these -images are suitable for trying a Debian system comprised of a selected default set of -packages and then install it from the same media.</p> - -<div class="line"> -<div class="item col50"> -<p><strong>DVD/USB (via <a -href="$(HOME)/CD/torrent-cd">BitTorrent</a>)</strong></p> -<p><q>Hybrid</q> ISO image files suitable for writing to DVD-R(W) -media, and also USB keys of the appropriate size. If you can use -BitTorrent, please do, as it reduces the load on our servers.</p> - <stable-live-install-bt-cd-images /> -</div> - -<div class="item col50 lastcol"> <p><strong>DVD/USB</strong></p> -<p><q>Hybrid</q> ISO image files suitable for writing to DVD-R(W) -media, and also USB keys of the appropriate size.</p> - <stable-live-install-iso-cd-images /> -</div> </div> - -<p>For information about what these files are and how to use them, please see -the <a href="../faq/">FAQ</a>.</p> - -<p>If you intend to install Debian from the downloaded live image, -be sure to have a look at the -<a href="$(HOME)/releases/stable/installmanual">detailed -information about the installation process</a>.</p> - -<p>See the <a href="$(HOME)/devel/debian-live">Debian Live Project page</a> for -more information about the Debian Live systems provided by these images.</p> - -# Translators: the following paragraph exists (in this or a similar form) several times in webwml, -# so please try to keep translations consistent. See: -# ./CD/http-ftp/index.wml -# ./CD/live/index.wml -# ./CD/netinst/index.wml -# ./CD/torrent-cd/index.wml -# ./distrib/index.wml -# ./distrib/netinst.wml -# ./releases/<release-codename>/debian-installer/index.wml -# ./devel/debian-installer/index.wml -# -<h2><a name="firmware">Unofficial live CD/DVD images with non-free firmware included</a></h2> - -<div id="firmware_nonfree" class="important"> -<p> -If any of the hardware in your system <strong>requires non-free firmware to be -loaded</strong> with the device driver, you can use one of the -<a href="https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/stable/current/">\ -tarballs of common firmware packages</a> or download an <strong>unofficial</strong> image -including these <strong>non-free</strong> firmwares. Instructions how to use the tarballs -and general information about loading firmware during an installation can -be found in the <a href="../../releases/stable/amd64/ch06s04">Installation Guide</a>. -</p> -<p> -<a href="https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current-live/">unofficial -live images for <q>stable</q> with firmware included</a> -</p> -</div> diff --git a/greek/CD/mirroring/Makefile b/greek/CD/mirroring/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/CD/mirroring/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/CD/mirroring/index.wml b/greek/CD/mirroring/index.wml deleted file mode 100644 index c8360252ee4..00000000000 --- a/greek/CD/mirroring/index.wml +++ /dev/null @@ -1,289 +0,0 @@ -#use wml::debian::cdimage title="Becoming a mirror for Debian CD images" BARETITLE=true -#use wml::debian::toc -#use wml::debian::translation-check translation="a2762a4686797f8bd714431c6bc466b37657847b" maintainer="galaxico" - -<p>To become a Debian CD Image mirror site, you need a Linux or -Unix-like machine with a permanent, reliable connection to the -Internet. Debian CD mirrors hold <tt>.iso</tt> images for CDs and DVDs -of various sizes, files for <a -href="https://www.einval.com/~steve/software/jigdo/">jigdo</a> (<tt>.jigdo</tt> and -<tt>.template</tt>), <a -href="https://en.wikipedia.org/wiki/BitTorrent">BitTorrent</a> files -(<tt>.torrent</tt>) and verification files for the images -(<tt>SHA512SUMS*</tt> and <tt>SHA256SUMS*</tt>).</p> - -<toc-display/> - -#______________________________________________________________________ - -<toc-add-entry name="master">Master site</toc-add-entry> - -<p><!-- There are two locations for mirroring, one for stable images and -one for beta/unstable/testing images. -->The URLs of the master site are -shown below - however, <strong>please</strong> consider mirroring from -another nearby mirror (mirror lists: <a -href="../http-ftp/">HTTP/FTP</a>, <a href="rsync-mirrors">rsync</a>) -if possible. Access to the master site may be restricted around -release time.</p> - -<p>Also be aware that a <strong>huge</strong> amount of data is stored -in these directories - read the <a href="#exclude">section below</a> -for details on how to cut down the size by excluding certain -files.</p> - -<ul> - - <li>Stable images (updated for each stable release):<br> - - <a href="https://cdimage.debian.org/debian-cd/" - ><tt>https://cdimage.debian.org/debian-cd/</tt></a><br> - - <tt>rsync://cdimage.debian.org/debian-cd/</tt> - - </li> - - <li>Weekly images:<br> - - <a href="https://cdimage.debian.org/cdimage/weekly-builds/" - ><tt>https://cdimage.debian.org/cdimage/weekly-builds/</tt></a><br> - - <tt>rsync://cdimage.debian.org/cdimage/weekly-builds/</tt> - - </li> - - <li>Daily images:<br> - - <a href="https://cdimage.debian.org/cdimage/daily-builds/" - ><tt>https://cdimage.debian.org/cdimage/daily-builds/</tt></a><br> - - <tt>rsync://cdimage.debian.org/cdimage/daily-builds/</tt> - - </li> - -</ul> -#______________________________________________________________________ - -<toc-add-entry name="httpftp">Mirroring using HTTP/FTP is -discouraged</toc-add-entry> - -<p>You should not use FTP or HTTP to update your mirror. These -transfer methods have a high failure probability because of the -enormous size of the files.</p> - -<p>Furthermore, HTTP and FTP do not include integrity checks of the -downloaded data, it is more likely that aborted downloads or data -corruption will go unnoticed.</p> -#______________________________________________________________________ - -<toc-add-entry name="rsync">Mirroring using rsync is -acceptable</toc-add-entry> - -<p>The <a href="https://rsync.samba.org/"><kbd>rsync</kbd></a> program -is a good solution for mirroring. It is less efficient than the other, -Debian-specific mirroring solution below, but may be easier to set -up. Furthermore, it ensures that all files are transferred correctly -and that the metadata (e.g. timestamps) is kept in sync just like the -file data.</p> - -<p>See the section <a href="#exclude">Excluding files from -mirroring</a> for examples of <kbd>--include</kbd> and -<kbd>--exclude</kbd> switches. The <a href="rsync-mirrors">list of -rsync mirrors</a> is available on a separate page.</p> - -<p>Use at least the options <strong><kbd>--times --links --hard-links --partial ---block-size=8192</kbd></strong>. This will preserve modification time, -symlinks and hardlinks, and use a block size of 8192 bytes (most efficient -for CD images). When modification time and size are the same, -<kbd>rsync</kbd> will just leave the file alone, so <kbd>--times</kbd> is -really obligatory.</p> -#______________________________________________________________________ - -<toc-add-entry name="jigdolite">Mirroring using jigdo-lite is -discouraged</toc-add-entry> - -<p>Recent versions of the <a -href="https://www.einval.com/~steve/software/jigdo/"><kbd>jigdo-lite</kbd></a> program -support batch downloading of multiple images. However, we do not -recommend to use <kbd>jigdo-lite</kbd> to create Debian CD mirrors - -use <kbd>jigdo-mirror</kbd> instead.</p> -#______________________________________________________________________ - -<toc-add-entry name="jigdomirror">Mirroring using jigdo-mirror is -recommended</toc-add-entry> - -<p>Actually, this means: Mirror the <tt>.iso</tt> files using <a -href="https://www.einval.com/~steve/software/jigdo/"><kbd>jigdo-mirror</kbd></a>, then (if -you also want to mirror other types of files, e.g. <tt>.jigdo</tt> and -<tt>.template</tt> files) run rsync over the directory to fetch the -rest. The scripts on <a -href="http://www.acc.umu.se/~maswan/debian-push/cdimage/">this -page</a> might help when setting this up.</p> - -<p>A lot of people maintain "regular" Debian mirrors -(<kbd>debian/</kbd>), or just have such a mirror nearby. This means -that they already have the <tt>.deb</tt>s that are included in the -CD/DVD images. The obvious question is -- why can't we use those same -files in the CD/DVD images?</p> - -<p><kbd>jigdo-mirror</kbd> is a program that enables one to generate a -set of Debian CD/DVD images using the files from a "normal" mirror, -plus a few extra jigdo template files.</p> - -<p>Firstly, you need the jigdo template files. See <a -href="../jigdo-cd">the jigdo information page</a> for links. Fetch the -files for each architecture you wish to build images for.</p> - -<p>Create <kbd>~/.jigdo-mirror</kbd> file to configure the program. -This is an example:</p> - -<pre> -jigdoDir="/where/you/keep/mirrors/debian-cd/current/jigdo" -imageDir="/where/you/keep/mirrors/debian-cd/current/images" -tmpDir="/where/you/keep/mirrors/debian-cd/current/images" -debianMirror="file:/where/you/keep/mirrors/debian" -include='i386/|sparc/|powerpc/|source/'; exclude='-1\.' -</pre> - -<p>The <i>include</i> and <i>exclude</i> variables contain the list of -architectures you wish to create images for (regular expressions, -rather). For more information, see the <kbd>jigdo-mirror</kbd> manual -page or the source itself (it's a shell script with a lot of comments).</p> - -<p>After you've configured it, simply run <kbd>jigdo-mirror</kbd> and it -will do everything on its own. It will make a lot of output and probably -take a while, so we suggest that you make steps to handle that (run it in -screen, redirect the output into a file etc).</p> -#______________________________________________________________________ - -<toc-add-entry name="pushmirror">How to become a push -mirror</toc-add-entry> - -<p>Whenever new images are available, the master site can send a -message to its mirrors and make them start updating immediately. This -way, the new data is "pushed" out rather than "pulled" by the mirrors -during their next daily update, which leads to faster propagation of -new image releases.</p> - -<p>If you want your mirror to be part of this update system, have a -look at <a href="http://www.acc.umu.se/~maswan/debian-push/cdimage/" ->this page</a>.</p> -#______________________________________________________________________ - -<toc-add-entry name="exclude">Excluding files from -mirroring</toc-add-entry> - -<p>To reduce the amount of storage required by your Debian CD mirror, -you can exclude certain files from being mirrored. The following -instructions include command line switches for <kbd>rsync</kbd>, but -might help you even if you use a different tool for mirroring. With -<kbd>rsync</kbd>, <kbd>--include</kbd> and <kbd>--exclude</kbd> -switches are considered in order of appearance, and the first switch -whose file pattern matches determines whether the file is excluded or -included.</p> - -<ul> - - <li><strong>Exclude source code:</strong> - <kbd>--exclude=source/</kbd><br> - - This will prevent images containing source code from being - mirrored. Note that some people consider it inappropriate to offer - binaries of GPL-licensed programs on a server without also offering - the programs' source code <em>on the same server</em>.</li> - - <li><strong>Exclude full images:</strong> - <kbd>--include='*netinst*.iso' - --exclude='*.iso'</kbd><br> - - Exclude all full CD/DVD image sets for all architectures, - <em>but</em> mirror the net-install - <tt>.iso</tt> images. We recommend always to mirror these small - images: Relative to their size, they are extremely useful!</li> - - <li><strong>Exclude full images for non-i386 architectures:</strong> - <kbd>--include='*netinst*.iso' - --include='i386/**.iso' --exclude='*.iso'</kbd><br> - - As above, but <em>do</em> include all CD/DVD images for the i386 - architecture.</li> - - <li><strong>Exclude full images, except for i386 CDs 1 to - 3:</strong> - <kbd>--include='*netinst*.iso' --include='i386/**-[1-3].iso' - --exclude='*.iso'</kbd><br> - - The full set of i386 images may still take too much space for you if - it includes DVD and dual-layer DVD images. This excludes all - <tt>.iso</tt> images except for the net-install images and the first - three i386 DVDs.</li> - - <li><strong>Exclude multiple architectures except i386:</strong> - <kbd>--exclude=alpha/ --exclude=arm/ --exclude=hppa/ --exclude=hurd/ - --exclude=ia64/ --exclude=m68k/ --exclude=mips/ --exclude=mipsel/ - --exclude=powerpc/ --exclude=s390/ --exclude=sh/ - --exclude=sparc/</kbd><br> - - Only include the full set of files for i386, do not include any - <tt>.jigdo</tt>, <tt>.iso</tt> etc files whatsoever for the other - architectures.<br> - - <strong>Check the architecture list before mirroring - the list - changes and these examples may be out of date!</strong></li> - -</ul> -#______________________________________________________________________ - -<toc-add-entry name="names">Naming conventions and size requirements -for <tt>.iso</tt> images</toc-add-entry> - -<p>The different variants of <tt>.iso</tt> images are distinguishable by -their names, allowing you to restrict the types of images you -mirror:</p> - -<ul> - - <li><strong><tt>*-netinst.iso</tt></strong>: One image for each - architecture, up to 500 MB</li> - - <li><strong><tt>*-dvd.iso</tt></strong> (single-layer DVDs): - Multiple images, each up to 4482 MB large. For buster, there - are up to <strong>16</strong> DVD images per architecture. Debian - servers provide only a small subset of DVD images in .iso form for - direct download: 3 for amd64, 3 for i386 and 1 each for other - architectures. The remaining images are only provided in jigdo - form.</li> - - <li><strong><tt>*-bd.iso</tt></strong> (single-layer Blu-Rays): As - above, except that individual images are up to 23 GB in - size. These images are only available as jigdo files for a limited - set of architectures (amd64 and i386) and source.</li> - - <li><strong><tt>*-dlbd.iso</tt></strong> (dual-layer Blu-Rays): As - above, except that individual images are up to 48 GB in - size. These images are only available as jigdo files for a limited - set of architectures (amd64 and i386) and source.</li> - - <li><strong><tt>*-STICK16GB*.iso</tt></strong> (16GB USB images): As - above, except that individual images are up to 16 GB in - size. These images are only available as jigdo files for a limited - set of architectures (amd64 and i386).</li> - -</ul> -#______________________________________________________________________ - -<toc-add-entry name="register">Registering the mirror</toc-add-entry> - -<p>To make your CD image mirror useful to a wider audience, -you can register it in our mirror list such as -<a href="../http-ftp/">this one</a> or <a href="rsync-mirrors">this one</a>. -However, since full images are large files, this might cause you -many gigabytes of network traffic per day.</p> - -<p>You can register your mirror either by filling out -<a href="$(HOME)/mirror/submit">the mirror submission form</a> -(note that the CDImage-* fields are the important ones), or by -sending an e-mail to -<a href="mailto:debian-cd@lists.debian.org">\ -debian-cd@lists.debian.org</a>.</p> - -<p>We appreciate all new CD image mirrors. Thanks in advance!</p> diff --git a/greek/CD/mirroring/rsync-mirrors.wml b/greek/CD/mirroring/rsync-mirrors.wml deleted file mode 100644 index 3add248c125..00000000000 --- a/greek/CD/mirroring/rsync-mirrors.wml +++ /dev/null @@ -1,21 +0,0 @@ -#use wml::debian::cdimage title="Λίστα καθρεφτών rsync των εικόνων CD του Debian" BARETITLE=true -#use wml::debian::translation-check translation="e8a790cd1b8ccef42905c4ac8504b62fc1052921" maintainer="galaxico" - -<p>These are the addresses of the Debian CD Image -<a href="http://rsync.samba.org/">rsync</a> mirrors. Note that some mirrors -may not be completely up to date. This list only contains sites that carry -<em>official</em> Debian images.</p> - -<p><strong>Note:</strong> These sites do <em>not</em> necessarily offer the -images via FTP or HTTP - no use in trying! Instead, they use the rsync -protocol, which is much more efficient for our purposes. If you are looking -for HTTP/FTP download links, see the <a href="../http-ftp/">list of HTTP/FTP -mirrors</a>.</p> - -<p>If you get "Access Denied" from a lot of sites, you are -probably behind a firewall that is blocking the rsync port (873). -Ask your system administrator to reconfigure the -firewall.</p> - -#use wml::debian::countries -#include "$(ENGLISHDIR)/CD/mirroring/cdimage_mirrors.list" diff --git a/greek/CD/misc.wml b/greek/CD/misc.wml deleted file mode 100644 index 2e4a5549db9..00000000000 --- a/greek/CD/misc.wml +++ /dev/null @@ -1,16 +0,0 @@ -#use wml::debian::cdimage title="Debian CD images - miscellaneous items" BARETITLE=true -#use wml::debian::translation-check translation="05e3a535fd42688838f38b58d986be8a81cde9c2" maintainer="galaxico" - -<p>The following pages are not directly accessible via the menu -bar at the top of each page:</p> - -<ul> - - <li><a href="artwork/">Artwork for covers of Debian CDs</a></li> - - <li><a href="mirroring/">Becoming a Debian CD mirror</a></li> - - <li><a href="mirroring/rsync-mirrors">List of rsync mirrors for - Debian CD images</a></li> - -</ul> diff --git a/greek/CD/netinst/Makefile b/greek/CD/netinst/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/CD/netinst/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/CD/netinst/index.wml b/greek/CD/netinst/index.wml deleted file mode 100644 index 44720647897..00000000000 --- a/greek/CD/netinst/index.wml +++ /dev/null @@ -1,94 +0,0 @@ -#use wml::debian::cdimage title="Network install from a minimal CD" -#use wml::debian::release_info -#use wml::debian::installer -#include "$(ENGLISHDIR)/releases/images.data" -#use wml::debian::translation-check translation="cf13aff27aee3763a70db6bb4c8d2087bea5716e" maintainer="galaxico" - -<p>A <q>network install</q> or <q>netinst</q> CD is a single CD which enables -you to install the entire operating system. This single CD contains -just the minimal amount of software to start the installation and -fetch the remaining packages over the Internet.</p> - -<p><strong>What's better for me — the minimal bootable CD-ROM or the -full CDs?</strong> It depends, but we think that in many cases the -minimal CD image is better — above all, you only download the packages -that you selected for installation on your machine, which saves both -time and bandwidth. On the other hand, the full CDs are more suitable -when installing on more than one machine, or on machines without a -free Internet connection.</p> - -<p><strong>What types of network connections are supported -during installation?</strong> -The network install assumes that you have a connection to the -Internet. Various different ways are supported for this, like -analogue PPP dial-up, Ethernet, WLAN (with some restrictions), but -ISDN is not — sorry!</p> - -<p>The following minimal bootable CD images are available for -download:</p> - -<ul> - - <li>Official <q>netinst</q> images for the <q>stable</q> release — <a - href="#netinst-stable">see below</a></li> - - <li>Images for the <q>testing</q> release, both daily builds and known - working snapshots, see the <a - href="$(DEVEL)/debian-installer/">Debian-Installer page</a>.</li> - -</ul> - - -<h2 id="netinst-stable">Official netinst images for the <q>stable</q> release</h2> - -<p>Up to 300 MB in size, this image contains the installer and a -small set of packages which allows the installation of a (very) basic -system.</p> - -<div class="line"> -<div class="item col50"> -<p><strong>netinst CD image (generally 150-300 MB, varies by architecture)</strong></p> - <stable-netinst-images /> -</div> -<div class="item col50 lastcol"> -<p><strong>netinst CD image (via <a href="$(HOME)/CD/torrent-cd">bittorrent</a>)</strong></p> - <stable-netinst-torrent /> -</div> -<div class="clear"></div> -</div> - -<p>For information what these files are and how to use them, please see -the <a href="../faq/">FAQ</a>.</p> - -<p>Once you have downloaded the images, be sure to have a look at the -<a href="$(HOME)/releases/stable/installmanual">detailed -information about the installation process</a>.</p> - -# Translators: the following paragraph exists (in this or a similar form) several times in webwml, -# so please try to keep translations consistent. See: -# ./CD/http-ftp/index.wml -# ./CD/live/index.wml -# ./CD/netinst/index.wml -# ./CD/torrent-cd/index.wml -# ./distrib/index.wml -# ./distrib/netinst.wml -# ./releases/<release-codename>/debian-installer/index.wml -# ./devel/debian-installer/index.wml -# -<h2><a name="firmware">Unofficial netinst images with non-free firmware included</a></h2> - -<div id="firmware_nonfree" class="important"> -<p> -If any of the hardware in your system <strong>requires non-free firmware to be -loaded</strong> with the device driver, you can use one of the -<a href="https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/stable/current/">\ -tarballs of common firmware packages</a> or download an <strong>unofficial</strong> image -including these <strong>non-free</strong> firmwares. Instructions how to use the tarballs -and general information about loading firmware during an installation can -be found in the <a href="../../releases/stable/amd64/ch06s04">Installation Guide</a>. -</p> -<p> -<a href="https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/">unofficial -installation images for <q>stable</q> with firmware included</a> -</p> -</div> diff --git a/greek/CD/torrent-cd/Makefile b/greek/CD/torrent-cd/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/CD/torrent-cd/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/CD/torrent-cd/index.wml b/greek/CD/torrent-cd/index.wml deleted file mode 100644 index 5782aecf5d4..00000000000 --- a/greek/CD/torrent-cd/index.wml +++ /dev/null @@ -1,104 +0,0 @@ -#use wml::debian::cdimage title="Downloading Debian CD images with BitTorrent" BARETITLE=true -#use wml::debian::toc -#include "$(ENGLISHDIR)/releases/info" -#use wml::debian::installer -#include "$(ENGLISHDIR)/releases/images.data" -#include "$(ENGLISHDIR)/devel/debian-installer/images.data" -#use wml::debian::translation-check translation="f917b9adf4a1c15cca8405e010043d380e4b1b83" maintainer="galaxico" - -<p><a href="https://en.wikipedia.org/wiki/BitTorrent">BitTorrent</a> -is a peer to peer download system optimised for large numbers of -downloaders. It puts minimal load on our servers because BitTorrent clients -upload pieces of files to others while downloading, thus spreading the load -across the network and making blazing fast downloads possible. -</p> -<div class="tip"> -<p>The <strong>first</strong> CD/DVD disk contains all the files necessary -to install a standard Debian system.<br /> -To avoid needless downloads, please do <strong>not</strong> download -other CD or DVD image files unless you know that you need packages on -them.</p> -</div> -<p> -You will need a BitTorrent client to download Debian CD/DVD images -this way. The Debian distribution includes -<a href="https://packages.debian.org/bittornado">BitTornado</a>, -<a href="https://packages.debian.org/ktorrent">KTorrent</a> and the original -<a href="https://packages.debian.org/bittorrent">BitTorrent</a> tools. -Other operating systems are supported by <a -href="http://www.bittornado.com/download.html">BitTornado</a> and <a -href="https://www.bittorrent.com/download">BitTorrent</a>. -</p> -<h3>Official torrents for the <q>stable</q> release</h3> - -<div class="line"> -<div class="item col50"> -<p><strong>CD</strong></p> - <stable-full-cd-torrent> -</div> -<div class="item col50 lastcol"> -<p><strong>DVD</strong></p> - <stable-full-dvd-torrent> -</div> -<div class="clear"></div> -</div> - -<p>Be sure to have a look at the documentation before you install. -<strong>If you read only one document</strong> before installing, read our -<a href="$(HOME)/releases/stable/i386/apa">Installation Howto</a>, a quick -walkthrough of the installation process. Other useful documentation includes: -</p> -<ul> -<li><a href="$(HOME)/releases/stable/installmanual">Installation Guide</a>, - the detailed installation instructions</li> -<li><a href="https://wiki.debian.org/DebianInstaller">Debian-Installer - Documentation</a>, including the FAQ with common questions and answers</li> -<li><a href="$(HOME)/releases/stable/debian-installer/#errata">Debian-Installer - Errata</a>, the list of known problems in the installer</li> -</ul> - -# <h3>Official torrents for the <q>testing</q> distribution</h3> -# -# <ul> -# -# <li><strong>CD</strong>:<br /> -# <full-cd-torrent> -# </li> -# -# <li><strong>DVD</strong>:<br /> -# <full-dvd-torrent> -# </li> -# -# </ul> - -<p> -If you can, please leave your client running after your download is complete, -to help others download images faster! -</p> - -# Translators: the following paragraph exists (in this or a similar form) several times in webwml, -# so please try to keep translations consistent. See: -# ./CD/http-ftp/index.wml -# ./CD/live/index.wml -# ./CD/netinst/index.wml -# ./CD/torrent-cd/index.wml -# ./distrib/index.wml -# ./distrib/netinst.wml -# ./releases/<release-codename>/debian-installer/index.wml -# ./devel/debian-installer/index.wml -# -<div id="firmware_nonfree" class="important"> -<p> -If any of the hardware in your system <strong>requires non-free firmware to be -loaded</strong> with the device driver, you can use one of the -<a href="https://cdimage.debian.org/cdimage/unofficial/non-free/firmware/stable/current/">\ -tarballs of common firmware packages</a> or download an <strong>unofficial</strong> image -including these <strong>non-free</strong> firmwares. Instructions how to use the tarballs -and general information about loading firmware during an installation can -be found in the <a href="../../releases/stable/amd64/ch06s04">Installation Guide</a>. -</p> -<p> -<a href="https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current/">unofficial -installation images for <q>stable</q> with firmware included</a> -</p> -</div> diff --git a/greek/CD/vendors/Makefile b/greek/CD/vendors/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/CD/vendors/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/CD/vendors/adding-form.wml b/greek/CD/vendors/adding-form.wml deleted file mode 100644 index b14b0a800c0..00000000000 --- a/greek/CD/vendors/adding-form.wml +++ /dev/null @@ -1,97 +0,0 @@ -#use wml::debian::template title="Submit CD vendor information" -#use wml::debian::countries -#use wml::debian::translation-check translation="8c7c1ae9759fa292ec185218b009c0dafb0002ea" maintainer="galaxico" - -<p>If you would like to submit information about a vendor of Debian CDs, -you can do so using the form below.</p> - -<p>If you are considering selling Debian CDs, you should make sure -you have examined our <a href="info">vendor information</a> page.</p> - -<p>Most information provided will be displayed in the vendor list. -In particular, the e-mail address will also be displayed in the list, -and will be available to all users.</p> - -<p>It is important that you keep this information up to date. We try to -check the vendor sites every now and then and if, for example, the web page -no longer exists or mail bounces, we delete that entry.</p> - -<form method=post action="https://cgi.debian.org/cgi-bin/submit_cdvendor.pl"> - -<h2>CD vendor information</h2> - -<p> -<input type="radio" name="submissiontype" value="new" checked> -New vendor listing submission - -<input type="radio" name="submissiontype" value="update"> -Update of an existing vendor listing -</p> - -<p>Vendor name: -<input type="text" name="vendor" size="50"></p> - -<p>URL of vendor: -<input type="text" name="url" size="50"></p> - -<p>Do you donate some of the sale price to Debian: -<input type="radio" name="donates" value="yes"> yes -<input type="radio" name="donates" value="no"> no -</p> - -<p>Type(s) of disks sold: <br /> -<label> <input type="checkbox" name="offerscd" value="yes">CD</label> <br /> -<label> <input type="checkbox" name="offersdvd" value="yes">DVD</label> <br /> -</p> - -<p>Country you are in: -<select name="country"> - <: country_list() :> -</select> -</p> - -<p>Do you ship orders overseas: -<select name="shipping"> - <option value="yes">yes</option> - <option value="no">no</option> - <option value="some">some areas</option> - <option value="europe">within Europe</option> -</select> -</p> - -<p>URL of a web page that has information about your Debian CDs: -<input type="text" name="urldebcd" size="50"></p> - -<p>Email address for sales enquiries: -<input type="text" name="email" size="50"></p> - -<p>What architectures your CDs are for:</p> -<table border="0"><tr><td> -<label><input type=checkbox name=architectures value="ALL"> <em>all of them</em></label><br /> -<label><input type=checkbox name=architectures value="multi-arch"> Multi-arch</label><br /> -#include "$(ENGLISHDIR)/releases/$(TESTING)/release.data" -#include "$(ENGLISHDIR)/releases/arches.data" -<: -my $na = scalar @arches; $na = int($na / 3 + .5); -foreach my $a (@arches) { - $i++; - my $aname = $arches{$a}; $aname =~ s, ,\ \;,g; - print "<br />\n" if ($i % $na == 0); - print "<label><input type=checkbox name=architectures value=".$a."> ".$aname." [".$a."]</label> \n"; -} -:> -</td></tr></table> - -<table><tr> -<td valign="top">Comment (optional, <em>in English</em>):</td> -<td><textarea name="comment" cols=40 rows=7></textarea></td> -</tr></table> - -# <p>Note: ...</p> - -<p><input type="submit" value="Submit"></p> -</form> - -<p>Your listing should appear on the list within a week, as soon as -a human operator verifies it and includes it. We might email you in -case of any problems with the submitted entry.</p> diff --git a/greek/CD/vendors/adding.wml b/greek/CD/vendors/adding.wml deleted file mode 100644 index b140dcb631c..00000000000 --- a/greek/CD/vendors/adding.wml +++ /dev/null @@ -1,30 +0,0 @@ -#use wml::debian::template title="Adding new vendors to the CD vendors list" -#use wml::debian::translation-check translation="36a5f3c2e6fc935d982de2a73e5e7bb1767f13ce" maintainer="galaxico" - -<p>If you are considering selling Debian CDs, you should look at the Debian -<a href="info">vendor information</a> page.</p> - -<p>If you would like to be added to the CD vendors page, send email, in English, to -<email "debian-www@lists.debian.org"> with the -following details:</p> - -<ul> - <li>Vendor Name</li> - <li>URL of Vendor</li> - <li>Whether or not you donate some of the sale price to Debian</li> - <li>Type of CDs sold (see at the <a href="./">top of the main page</a> for details)</li> - <li>Country you are in</li> - <li>Do you ship orders overseas ("yes", "no", "some areas" or "within Europe") - </li> - <li>URL of a web page that has information about your Debian CDs</li> - <li>Email address for sales enquiries</li> - <li>What architectures your CDs are for.</li> -</ul> - -<p>It is important that you keep this information up to date. We try to -check the vendor sites every now and then and if, for example, the web page -no longer exists or mail bounces, we delete that entry.</p> - -<p>You must have a web page (specified by the 'Debian URL' line) that -mentions the Debian CDs you sell. This entry is mandatory if you want to -be listed on our site.</p> diff --git a/greek/CD/vendors/index.wml b/greek/CD/vendors/index.wml deleted file mode 100644 index 80db4093494..00000000000 --- a/greek/CD/vendors/index.wml +++ /dev/null @@ -1,40 +0,0 @@ -#use wml::debian::cdimage title="Vendors of Debian installation media" BARETITLE=true GEN_TIME=true -#use wml::debian::countries -#use wml::debian::translation-check translation="765c2c97976e78cc11ae19d94b561f02334317d0" maintainer="galaxico" - -#include "$(ENGLISHDIR)/CD/vendors/vendors.inc" - -<p> -<country-list vendors <list_country>> -</p> - -<p>Debian creates and provides its entire distribution free of charge. -Debian does not manufacture its own CDs, DVDs, BDs, or USBs, but relies -on third-party vendors. To make it easier for vendors to provide a -high quality disk, we provide official images for them. This is the -only version that has been fully tested by our testing team and is by -far the most popular way to buy Debian.</p> - -<p> - Some vendors allow customers to pay extra money and donate this to - Debian. Others contribute a portion of sales of Debian disks back to - Debian. This is indicated under <q>Allows Contributions.</q> - We hope that you will consider making a donation to Debian. -</p> - -<p>If you are having trouble with a vendor (e.g. you paid for -installation media but never received them), you can inform us by -sending mail to <email "debian-www@lists.debian.org">.</p> - -<p> - If you want to buy a computer system that has Debian already installed - on it, go to the <a href="$(HOME)/distrib/pre-installed">Debian Pre-installed Page</a>. -</p> - -<p>If you are a Debian installation media vendor or you wish to -become one, please see <a href="info">the information for Debian CD -vendors</a>.</p> - -<hr /> - -#include "$(ENGLISHDIR)/CD/vendors/vendors.CD" diff --git a/greek/CD/vendors/info.wml b/greek/CD/vendors/info.wml deleted file mode 100644 index cf9b300a608..00000000000 --- a/greek/CD/vendors/info.wml +++ /dev/null @@ -1,84 +0,0 @@ -#use wml::debian::template title="Information for CD vendors" -#use wml::debian::translation-check translation="d377aef268f44033788f7d9e6266449cf10bf079" maintainer="galaxico" - -<p>If you want to sell CDs containing Debian, the most important ideas -you should understand are the following:</p> - -<ul> -<li>There are no restrictions on redistribution of the main Debian - distribution. - <br /> - We make sure that all of the software in the main distribution is - released under a license that complies with the - <a href="$(HOME)/social_contract#guidelines">Debian Free Software - Guidelines</a>.</li> -<li>Debian does not sell any products.</li> -<li>Debian is a volunteer organization.</li> -<li>If you decide to sell CDs containing any software from the non-free or non-US portions -of Debian, it is up to you, the vendor, to comply with any applicable laws. -In particular, you must negotiate any required licenses for material in non-free yourself.</li> -<li>Many of the programs on the CDs are distributed under the GNU -General Public License (GPL). Please read the <a href="legal">license -information</a> on how to comply with the GPL.</li> -<li>Debian is a <a href="$(HOME)/trademark">trademark</a>, only reasonable use of -this trademark is allowed.</li> -</ul> - -<p>There are three possibilities for those who want to sell Debian CDs:</p> - -<ul> -<li><strong>Become a reseller of an existing vendor.</strong> -<br /> -Use the list of known -<a href="./">vendors of Debian CDs</a> if you are looking for someone -to act as a supplier. It is important that Debian remain impartial so we -will not recommend suppliers.</li> - -<li><strong>Produce your own CDs using the <a href="../">Official Debian -CD Images</a>.</strong> -<br /> -Note that it is possible to sell the <q>Official Debian CD</q>, and add an extra disk -containing vendor additions and still use the term <q>Official Debian CD</q>. -<br /> -Note: if you just want to install Debian, then you do not -want these images, but want to do a <a href="$(HOME)/distrib/netinst">network -install</a> or <a href="./">buy a CD</a>.</li> - -<li><strong>Produce your own custom CDs.</strong> -<br /> -This requires you to have a local copy of -the Debian archive. Creating custom disks is not difficult, but it is the -vendors responsibility to test the disks before shipping. There have been -problems in the past with vendors selling customized CDs which are not up -to Debian's standards. For this reason, use of the term <q>Official Debian CD</q> -is reserved for those who sell disks made from the Official Debian CD Images.</li> -</ul> - -<h2>Requirements for being added to the vendor list</h2> - -<p>If you would like to be listed on the Debian vendors page, please use -<a href="adding-form">our CD vendor submission form</a>. -Your submission will only be accepted if it fulfills the following requirements:</p> - -<ul> - - <li><strong>Only one entry in the list is allowed for each company!</strong> If -your company operates web shops under several domains, you may only submit -one of them. Any attempt to submit more than one shop will cause <em>all</em> -of your shops to be removed <em>permanently</em>. This is because in our view, -in that case you would be trying to deceive us and our users. Please only -submit one entry!</li> - - <li>The website you submit should list exactly what version of Debian you are - offering, and the architectures for which it is offered.</li> - - <li>The website should offer the current stable Debian release (or a more recent - release like testing/unstable).</li> - - <li>Furthermore, your web pages need to include prices for the disks and for - shipping.</li> - - <li>Finally, there must be information on the page on how to contact you, - both electronically (email address or email form) and offline (postal address).</li> - -</ul> diff --git a/greek/CD/vendors/legal.wml b/greek/CD/vendors/legal.wml deleted file mode 100644 index 7442d89d7b2..00000000000 --- a/greek/CD/vendors/legal.wml +++ /dev/null @@ -1,164 +0,0 @@ -#use wml::debian::template title="License Information for CD vendors" -#use wml::debian::translation-check translation="4f31f115eea41bd4c733329d18c4bb1561ffdcc0" maintainer="galaxico" - -# Source thread: https://lists.debian.org/debian-legal-0207/msg00192.html - -<p>Since the Debian system consists of a lot software which is -licensed under the <a href="https://www.gnu.org/copyleft/gpl.html">GNU -General Public License</a> any distributor has to ensure the license -is not infringed. If you are distributing Debian or parts of it in -compiled (binary) form, please read the explanations and the advice -below.</p> - -<p><strong> Because copyright law varies around the world, the Debian -Project cannot provide legal advice. Contact a local attorney for -clarification about your legal obligations when you distribute Debian. -</strong></p> - -<p>Distributing software which is licensed under the GNU GPL in object -code or executable form, either as CD image through the Internet or as -pressed or burned CD, requires the distributor (commercial or -non-commercial) to - -inform the person, who receives the binary form, -how to obtain the source code of the software. The source code has to -be provided to the user for a period of at least three years. -Pointing them only to an FTP server from a third party (i.e. the -Debian project) is not sufficient!</p> - -<p>Quoting and interpreting the GPL:</p> - -<p>3. <em>You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following:</em></p> - - <p>a) <em>Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange;</em></p> - -<p>The distributor provides a copy of the complete and corresponding -source as well as the binary form. If customers are downloading the -binary from some archive on the Internet, then adding the source in -the same archive is good enough; the distributor doesn't have to force -the user to download it.</p> - - <div class="center">OR</div> - - <p>b) <em>Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange;</em></p> - -<p>The distributor has to give the customer a written offer to -provide the complete and corresponding source to anyone (not merely -ones own customers) at a later date for a period of at least three -years. The distributor may charge a regular fee for creating and -distributing the source CDs, though. Simply pointing to a third party -(e.g. another company that sells source CDs or the Debian archive) is -not sufficient. If there's no written offer, the source has to be -provided up front.</p> - - <div class="center">OR</div> - - <p>c) <em>Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.)</em></p> - -<p>If the distributor is a non-commercial organization, and if it has -received the binaries with an offer like in paragraph b) above, then the -distributor can merely pass on that offer.</p> - -<h3>Suggested Course of Action</h3> - -<p>Any entity that distributes binary Debian CDs or CD images (or even -binary packages through a different medium, through the Internet, for -example) has to provide the complete and corresponding source code to -all software packages that are released under the Terms of the GNU -GPL.</p> - -<p>If no source CDs are provided regularly, one way to fulfill -this requirement is to burn a CD containing the corresponding source -archives and store it in a shelf. In addition, the distributor -is required to add a written offer valid for at least three years to -the binary distribution, telling the customer that the -complete and corresponding source will be provided on demand.</p> - -<p>The easiest way, however, is to distribute both binary and source -CDs at the same time and at the same price. Since CDs are quite cheap -these days, this will only slightly increase the price. - -<h3>Additional Explanation</h3> - -<p>Pointing to a third party FTP server is not sufficient because of -two issues:</p> - -<ul> - -<li> The customer's claim for the complete and corresponding source is - against the distributor, not against any third party, simply - because the customer received the binary distribution from the - distributor and not from a third party. - -<li> When the third party that was pointed to updates or removes a - source package on their server or source CDs, the customer is not - able to receive the corresponding source package from there - anymore. - -</ul> - -<p>When a source package (released using the GNU GPL) is distributed -or modified and distributed afterwards, one should always place the -source code next to it or store it somewhere else at least. If a -customer or user is requesting the source code at any later time, it -should be possible to provide the corresponding source code.</p> - -<p>The <a href="https://www.fsf.org/">Free Software Foundation</a> -maintains a list of frequently asked questions and answers (FAQ) that -may be able to add further explanations the above:</p> - -<ol> -<li> <a href="https://www.gnu.org/licenses/gpl-faq#DoesTheGPLRequireAvailabilityToPublic">\ - If I distribute GPL'd software for a fee, am I required to also - make it available to the public without a charge?</a> - -<li> <a href="https://www.gnu.org/licenses/gpl-faq#GPLCommercially">\ - If I use a piece of software that has been obtained under the GNU - GPL, am I allowed to modify the original code into a new program, - then distribute and sell that new program commercially?</a> - -<li> <a href="https://www.gnu.org/licenses/gpl-faq#DistributeWithSourceOnInternet">\ - I want to distribute binaries without accompanying sources. Can I - provide source code by FTP instead of by mail order?</a> - -<li> <a href="https://www.gnu.org/licenses/gpl-faq#SourceAndBinaryOnDifferentSites">\ - Can I put the binaries on my Internet server and put the source - on a different Internet site?</a> - -<li> <a href="https://www.gnu.org/licenses/gpl-faq#DistributeExtendedBinary">\ - I want to distribute an extended version of a GPL-covered program - in binary form. Is it enough to distribute the source for the - original version?</a> - -<li> <a href="https://www.gnu.org/licenses/gpl-faq#DistributingSourceIsInconvenient">\ - I want to distribute binaries, but distributing complete source - is inconvenient. Is it ok if I give users the diffs from the - "standard" version along with the binaries?</a> - -<li> <a href="https://www.gnu.org/licenses/gpl-faq#AnonFTPAndSendSources">\ - I want to make binaries available for anonymous FTP, but send - sources only to people who order them.</a> - -<li> <a href="https://www.gnu.org/licenses/gpl-faq#HowCanIMakeSureEachDownloadGetsSource">\ - How can I make sure each user who downloads the binaries also - gets the source?</a> - -<li> <a href="https://www.gnu.org/licenses/gpl-faq#CompanyGPLCostsMoney">\ - I just found out that a company has a copy of a GPL'ed program, - and it costs money to get it. Aren't they violating the GPL by - not making it available on the Internet?</a> - -</ol> diff --git a/greek/MailingLists/HOWTO_start_list.wml b/greek/MailingLists/HOWTO_start_list.wml deleted file mode 100644 index 37cc3011e6b..00000000000 --- a/greek/MailingLists/HOWTO_start_list.wml +++ /dev/null @@ -1,137 +0,0 @@ -#use wml::debian::template title="HOWTO request a mailing list" -#use wml::debian::translation-check translation="881ca15fb120b2f30d9ab1613754ba77b339037e" maintainer="galaxico" - -<P>The scope of this document is to help people establish a mailing -list at <a href="https://lists.debian.org/">lists.debian.org</a>.</p> - -<p>All new mailing lists need to have these basic prerequisites:</p> - -<ul> - <li>Basic purpose. - <br> - This means that the topic the new mailing list would cover is appropriate - for discussion on a permanent mailing list on lists.debian.org. - <br> - Some discussions are better suited for simple mail aliases, and mailing - lists for simple package maintenance don't need lists here. - Needless to mention, vanity or offtopic lists will not be created.</li> - - <li>Interested audience. - <br> - This means that requests for new mailing lists need to be based on - a real need for a new, separate discussion forum, rather than on - the whim of the requester. A modicum of audience is also necessary - to avoid temporary or transient mailing list requests.</li> -</ul> - -<p>Once these two prerequisites have been obtained, a proper request -needs to be sent in as a <em>wishlist</em> -<a href="$(HOME)/Bugs/Reporting">bug report</a> against the -<code><a href="https://bugs.debian.org/lists.debian.org">lists.debian.org</a></code> -pseudo-package.</p> - -<p>The following information is required in the bug report:</p> - -<div class="centerblock"> -<dl> - - <dt><strong>Name</strong></dt> - <dd> - <p>Please choose a descriptive, short and unique name.</p> - - <p>Please note that every list name needs to be prefixed with a - unique string, most commonly <code>debian-</code> for lists related - to the Debian Project. - - <p>Lists for external projects don't need a prefix, as they will be - created as <code><var>listname</var>@other.debian.org</code>.</p> - - <p>Words are separated with a dash, "-", so for example a list about - "Foo bar" in relation to Debian would be called debian-foo-bar.</p> - </dd> - - <dt><strong>Rationale</strong></dt> - <dd> - <p>Full explanation on why do you want this list be created.</p> - - <p>The listmasters reserve the right to ask for consensus on - debian-devel and / or debian-project lists first. - If you are aware your request is questionable, you can speed up - the process by discussing the matter even before filing the bug.</p> - </dd> - - <dt><strong>Short description</strong></dt> - <dd> - <p>This is the one-line description, for display in list indices, - so make it short and straightforward.</p> - </dd> - - <dt><strong>Long description</strong></dt> - <dd> - <P>This description is meant for people who are looking for the - proper list to join, so make sure it's clear and informative. - - <P>See <A HREF="subscribe">the subscription page</A> for examples. - </p> - </dd> - - <dt><strong>Category</strong></dt> - <dd> - <p>This is needed to classify the list and to properly sort it on - <a href="subscribe">the subscription page</a> and elsewhere.</p> - <p> - The available categories can be found on <a - href="https://lists.debian.org">the homepage of lists.debian.org</a>. - </p> - </dd> - - <dt><strong>Subscription Policy</strong></dt> - <dd> - <P>open / closed - - <p>If closed, who may get subscribed, who can approve subscription - requests? We usually don't support closed lists, you need a very - good reasoning for requesting such a list.</p> - </dd> - - <dt><strong>Post Policy</strong></dt> - <dd> - <P>open / moderated - - <p>If moderated, who are the moderators? - We usually don't support moderated lists, you need a very - good reasoning for requesting such a list. There also doesn't exist - a webfrontend or something like that. Moderation is done by mail - only. - </p> - </dd> - - <dt><strong>Web Archive</strong></dt> - <dd> - <P>yes / no - - <p>At <a href="https://lists.debian.org/">our mailing list archives.</a>. - We do expect for list archives to be public, you do need a good reason - for not having a web archive. - </dd> - -</dl> -</div> - -<p>After filing the request, it would be very much appreciated if several -other people interested in the new list would send a mail to the bug, -in order to record their interest.</p> - -<p>Please follow the above rules, because improper requests will not be -implemented.</p> - -<h3>Moving existing mailing lists to lists.debian.org</h3> - -<p>An existing mailing list can be moved to lists.debian.org: the -administrator of the list has to submit a request as described above and -provide us with a list of subscribers (in plain text format, one address -per line). Archives of the existing list can also be imported from files -in mbox format (preferably split per month).</p> - -<p>In addition to that, they should set up redirections from -the old location to the new one, of course.</p> diff --git a/greek/MailingLists/Makefile b/greek/MailingLists/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/MailingLists/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/MailingLists/debian-announce.wml b/greek/MailingLists/debian-announce.wml deleted file mode 100644 index 457efff0069..00000000000 --- a/greek/MailingLists/debian-announce.wml +++ /dev/null @@ -1,28 +0,0 @@ -#use wml::debian::template title="debian-announce Mailing List Subscription" -#use wml::debian::translation-check translation="581109f2739fb8deca7c6d06962913ef78819761" maintainer="galaxico" - -<p>"debian-announce" is a moderated -<a href="https://foldoc.org/mailing+list">mailing -list</a> which is used to broadcast -announcements of general interest to the Debian community. - -<p>To subscribe to debian-announce you can follow the instructions at -<a href="./#subunsub">the mailing lists page</a> or you can simply use the -automatic subscription form below. - -<p>As part of the subscription process you will be sent mail to which you -must reply to finish subscribing. This is a security measure to keep people -from subscribing others to the lists without their permission. - -<p><strong>Your E-Mail address:</strong></p> -<form method="post" action="https://lists.debian.org/cgi-bin/subscribe.pl"> -<p> -<input type="hidden" name="subscribe" value="debian-announce"> -<input type="text" name="user_email" size="50"><br> -<input type="submit" value="Subscribe"> <input type="reset" value="Clear"> -</p> -</form> - -<p>Note that all the announcements sent to this list also go into the -<a href="$(HOME)/News/">News</a> section of our web pages, as well as the -<a href="https://lists.debian.org/debian-announce/">list archives</a>.</p> diff --git a/greek/MailingLists/disclaimer.wml b/greek/MailingLists/disclaimer.wml deleted file mode 100644 index 40e6009ff59..00000000000 --- a/greek/MailingLists/disclaimer.wml +++ /dev/null @@ -1,54 +0,0 @@ -#use wml::debian::template title="Disclaimer for the Debian mailing lists" BARETITLE=true -#use wml::debian::translation-check translation="b8114b588961778dbd04974c1464a2f388a90c28" maintainer="galaxico" - -<p><strong>Our mailing lists are public forums, and our mailing list -archives are public.</strong> - -<p>By sending an email to such a public forum, you agree to public -distribution of your article. All mails sent to any of our -<a href="subscribe">mailing lists</a> (and to the <a href="$(HOME)/Bugs/">bug -tracking system</a>) will be publicly distributed and archived in our -<a href="https://lists.debian.org/">mailing list archives</a>. - -<p>Any emails sent by any one person directly to the list, or replies by -others to those emails sent to the list, are considered published, in -accordance with the United States law. - -<p>Obviously the author still owns the copyright to the content of these -emails that they have written. However, that does <strong>not</strong> mean -that the Debian Project is under obligation to remove them from a list -archive once published. Several legal counsels have reviewed this stance and -confirmed it is correct. - -<p>The mailing list archives have been public well before you sent a message -to that mailing list address. You are responsible for determining who it is -you are sending your email to. You cannot send email to arbitrary -recipients and expect that they are automatically forced into accepting your -terms for receiving your email. - -<p>Debian accepts no responsibility for the opinions and information posted -on its mailing lists by others.</p> - -<p>Debian disclaims all warranties with regard to information posted on its -mailing lists, whether posted by Debian or others; this disclaimer includes -all implied warranties of merchantability and fitness. In no event shall -Debian be liable for any special, indirect or consequential damages, or -damages of any kind whatsoever, resulting from loss of use, data or profits, -arising out of or in connection with the use of any information posted on a -Debian mailing list.</p> - -<p>By posting material, the posting party warrants and represents that it -owns the copyright with respect to such material, has received permission -from the copyright owner, or that the material is in the public domain. -The posting party further warrants and represents that it otherwise has the -full and unencumbered right to post such material and that such posting will -not infringe any rights or interests of others.</p> - -<p>Debian does not generally monitor its mailing lists for inappropriate -postings, and does not undertake editorial control of postings. We do, -however, reserve the right to prevent posting to mailing lists in the event -of failure to comply with the mailing list code of conduct.</p> - -<p>Some spam and virus filtering is applied to every message that goes through -Debian lists. Roughly 1 in 400 messages that are sent to the list actually -make it through; the rest are discarded as spam.</p> diff --git a/greek/MailingLists/index.wml b/greek/MailingLists/index.wml deleted file mode 100644 index 2a9a392c4ab..00000000000 --- a/greek/MailingLists/index.wml +++ /dev/null @@ -1,277 +0,0 @@ -#use wml::debian::template title="Mailing Lists" -#use wml::debian::toc -#use wml::debian::translation-check translation="110bc4d4ee9d36736f60b27f71e4f404d9eb5a6a" maintainer="galaxico" - -<toc-display/> - -<toc-add-entry name="intro">Introduction</toc-add-entry> - -<p>Debian is developed through distributed development all around -the world. Therefore, e-mail is the preferred way to discuss various items. -Much of the conversation between Debian developers and users is managed -through several -<a href="https://foldoc.org/mailing+list">mailing -lists</a>.</p> - -<p>There are many world-open mailing lists, meaning anyone can read -everything that is posted, and participate in the discussions. Everyone is -encouraged to help development of Debian and to spread the word of free -software. There are also a few lists which are only open to official Debian -developers; please don't interpret this as closed development, it sometimes -doesn't make much sense discussing internal topics with non-developers.</p> - -<p>All original Debian mailing lists are run on a special server, using an -automatic mail processing software called SmartList. This server -is called <code><a href="https://lists.debian.org/">lists.debian.org</a></code>. -All submission, subscription and unsubscription messages have to be sent -to a particular address at this host.</p> - - -<toc-add-entry name="basics">Basic use</toc-add-entry> - -<p>Each Debian mailing list has a submission address in the form -<kbd><var>listname</var>@lists.debian.org</kbd>, a control request -address in the form <kbd><var>listname</var>-request@lists.debian.org</kbd>, -and a web page at <kbd>https://lists.debian.org/<var>listname</var>/</kbd>.</p> - -<p>To send an email to a list, simply send it to the submission address. -To subscribe to a list to be able to read incoming mails as they arrive, -or to unsubscribe from a list, use the control request -address (<a href="#subunsub">see below</a>).</p> - -<p>The current list of available mailing lists is at -<url "https://lists.debian.org/">, presented sorted by topic -and unsorted.</p> - -<p>We also maintain some <a href="https://lists.debian.org/stats/">usage -statistics</a> for the mailing lists: check the average number of posts -before subscribing to a list in order to avoid being flooded by mails.</p> - - -<toc-add-entry name="disclaimer">Disclaimer / Privacy policy / Legal information</toc-add-entry> - -<p>The mailing lists are <strong>public forums</strong>.</p> - -<p>All emails sent to the lists are distributed both to the list -subscribers and copied to the <a href="https://lists.debian.org/">public -archive</a>, for people to browse or -<a href="https://lists.debian.org/search.html">search</a> without the need -to be subscribed.</p> - -<p>Furthermore, you can browse our mailing lists as Usenet newsgroups. - -<p>There may be other places where lists are distributed — please make sure -you never send any confidential or unlicensed material to the lists. This -includes things like e-mail addresses. Of particular note is the fact that -spammers, viruses, worms etc have been known to abuse e-mail addresses -posted to our mailing lists.</p> - -<p>Debian maintains the mailing lists in good faith and will take steps to -curb all noticed abuse and maintain uninterrupted normal service. At the -same time, Debian is not responsible for all mailing list posts or anything -that may happen in relation to them.</p> - -<p>Please see our <a href="disclaimer">disclaimer of responsibility</a> for -more information.</p> - - -<toc-add-entry name="subunsub">Subscription / Unsubscription</toc-add-entry> - -<p>Anyone is able to subscribe/unsubscribe on their own to any mailing list, -presuming the subscription policy for a particular list is <q>open</q>.</p> - -<p>You can use simple web forms to subscribe or unsubscribe from -individual mailing lists, available at their respective web pages at -<url "https://lists.debian.org/">.</p> - -<p>To subscribe or unsubscribe from multiple mailing lists at once, -use the list <a href="subscribe">subscription</a> or -<a href="unsubscribe">unsubscription</a> web forms, respectively. -The former page also includes descriptions and the subscription policy -for each list.</p> - -<p>The requests for subscription or unsubscription can also be sent by -email, to a special control address, which is slightly different from the -lists address. <strong>Subscription or unsubscription messages should NOT be -sent to the address of the mailing list itself.</strong></p> - -<p>To subscribe to or unsubscribe from a mailing list, please send mail to</p> - -<p><var><listname></var>-REQUEST@lists.debian.org</p> - -<p>with the word <q>subscribe</q> or <q>unsubscribe</q> as subject.</p> - -<p><strong>Please remember the -REQUEST part of the address.</strong></p> - -<p>As part of the subscription process, the list software will send you an -email to which you must reply in order to finish subscribing. This is a -security measure to keep people from subscribing others to the lists without -their permission.</p> - -<h3><a name="subglitches">Common glitches in the (un)subscription process</a></h3> - -<p>Please remember that <strong>an unsubscription request should be sent from -the address that is subscribed</strong>. If that is not possible, the Subject: -header should be: <code>unsubscribe -<var>subscribedaddress@subscribed.domain</var></code>, or you can use the <a -href="unsubscribe">unsubscription</a> web form.</p> - -<p>If you're receiving mail from a mailing list but you can't find the -address through which you are subscribed, you can use the full headers -of the received messages which will include something like this:</p> - -<pre> - From bounce-debian-foo=quux=example.com@lists.debian.org Tue Apr 22 01:38:14 2003 -</pre> - -<p>This tells you reliably that the list in question is called -<code>debian-foo</code> and that the subscribed address is -<code>quux@example.com</code>. In this (fictional) case you would send e-mail -to <kbd>debian-foo-request@lists.debian.org</kbd> with <kbd>unsubscribe -quux@example.com</kbd> in the Subject field. The address you should send your -unsubscribe request to is also in the List-Unsubscribe-Header of every -mail.</p> - -<p>Unfortunately it's currently impossible to subscribe with a username that -matches procmail's check for mail coming from a daemon. This means that a -username may not have <q>mail</q>, <q>admin</q>, <q>root</q>, <q>master</q> or -similar strings in it (see <kbd>procmailrc(5)</kbd> for -<q>FROM_DAEMON</q>).</p> - -<p>Another known limitation in our mailing list software is that most -rejected e-mails get silently dropped, so the user has no real indication -on what went wrong. For example, it is common for people to try to subscribe -an address that is already subscribed: SmartList will simply ignore their -e-mail.</p> - -<p>If you are uncertain as to whether you are subscribed to a mailing -list of ours, send mail to <email majordomo@lists.debian.org> with -</p> -<p><kbd>which <var>your.email@address</var></kbd></p> -<p> -in the body. Further -information about this service (the so-called <q><a -href="https://www.infodrom.org/projects/majorsmart/">MajorSmart</a></q>) is -available by sending another mail to the same address with -</p> - -<p><kbd>help</kbd></p> - -<p>in the body.</p> - - -<toc-add-entry name="codeofconduct">Code of conduct</toc-add-entry> - -<p>When using the Debian mailing lists, please follow -<a href="../code_of_conduct">the Debian Code of Conduct</a> in addition to these rules:</p> - -<ul> - <li>The mailing lists exist to - foster the development and use of Debian. - Non-constructive or off-topic messages, - along with other abuses, are not welcome.</li> - <li>Do not send <em><a href="https://foldoc.org/spam"> - spam</a></em>; see the <a href="#ads">advertising policy</a> below.</li> - <li>Send all of your e-mails in English. Only use other languages on - mailing lists where that is explicitly allowed - (e.g. French on debian-user-french).</li> - <li>Make sure that you are using the proper list. In particular, don't - send user-related questions to developer-related mailing lists.</li> - <li>Wrap your lines at 80 characters or less for ordinary - discussion. Lines longer than 80 characters are acceptable - for computer-generated output (e.g., <kbd>ls -l</kbd>).</li> - <li>Do not send automated <q>out-of-office</q> or <q>vacation</q> messages.</li> - <li>Do not send <q>test</q> messages to determine whether your mail client - is working.</li> - <li>Do not send subscription or unsubscription requests to the list - address itself; use the respective <tt>-request</tt> address instead.</li> - <li>Please don't send your messages in HTML; use plain text instead.</li> - <li>Avoid sending large attachments.</li> - <li>Do not quote messages that were sent to you by other people - in private mail, unless agreed beforehand.</li> - <li>When replying to messages on the mailing list, do not send a carbon - copy (CC) to the original poster unless they explicitly request to be - copied.</li> - <li>If you want to complain to someone who sent you a carbon copy when - you did not ask for it, do it privately.</li> - <li>If you send messages to lists to which you are not subscribed, always - note that fact in the body of your message.</li> - <li>Do not use foul language; besides, some people receive the lists - via packet radio, where swearing is illegal.</li> - <li>Try not to <em><a href="https://foldoc.org/flame"> - flame</a></em>; it is not polite.</li> - <li>Use common sense all the time.</li> -</ul> - - -<toc-add-entry name="maintenance">List maintenance</toc-add-entry> - -<p>If you wish to request a new mailing list, please read the -<a href="HOWTO_start_list">HOWTO</a>.</p> - -<p>If you're having problems subscribing or unsubscribing, please -make sure you've <a href="#subunsub">followed the proper procedure</a> -<strong>before</strong> trying to contact us. Make sure that you have seen -<a href="#subglitches">the caveats regarding subscription/unsubscription</a>. -</p> - -<p>To contact the list maintainer, send e-mail <strong>in English</strong> -to <email "listmaster@lists.debian.org">. -<br /> -Alternatively, you can <a href="$(HOME)/Bugs/Reporting">file a bug report</a> -against the -<a href="https://bugs.debian.org/lists.debian.org">lists.debian.org</a> -pseudo-package.</p> - -<p>If you were unable to unsubscribe from a mailing list, please include a -copy of all the headers of an example message that you have received from -that list in your e-mail.</p> - - -<toc-add-entry name="ads">Debian mailing list advertising policy / Spam Fighting</toc-add-entry> - -<p>The sending of any kind of unsolicited bulk email (also known as <q>spam</q>) -to any of the Debian lists is prohibited. -Senders of such messages can get blocked from posting on lists -and/or reported to the relevant authorities.</p> - -<p>The Debian Listmasters do their best to stop as many such emails as possible -from reaching the lists. On a typical day, over 40,000 such messages are blocked.</p> - -<p>Many of the rules we use to block spammers and their messages have been reported -to us by subscribers. If you wish to help us reduce the amount of spam even more, your -help is very much appreciated. -<br/> -To report spam properly, you need to do the following:</p> - -<ul> - <li>Find a copy of the message at the - <a href="https://lists.debian.org">list archives</a>.</li> - <li>Find a SpamAssassin rule to catch this type of spam. Keep in mind - that this rule will be applied against all lists, and that we want - to keep the false positives to a minimum. (you can see our ruleset - at <url - "https://salsa.debian.org/debian-listmasters/spamassassin_config">)</li> - <li>Send email to <email "listmaster@lists.debian.org"> with - the exact URL of the message, and the said filter rule, - if possible.</li> -</ul> - -<p>You will get a reply when we act on your submission. -<br/> -Please bear in mind that we will only act on reported spam messages/patterns -that have been sent in the last few hours, because there is no point -in having out of date filtering rules. -<br/> -Also, please do not send any pre-packaged lists of rules you have found -somewhere. They very rarely provide good results on our lists, because they -receive some pretty unique traffic.</p> - -<p>Do not allow any emails that you receive from any Debian mailing lists -to be sent to an automated spam reporting system. Doing so is often harmful -to all users and will force us to block you from receiving traffic from -all Debian lists until you prove that you will not do so again.</p> - -<p>More efforts to reduce spam on the lists and in the archive -<url "https://lists.debian.org/"> can be found at -<url "https://wiki.debian.org/Teams/ListMaster/ListArchiveSpam"></p> diff --git a/greek/blends/gis/Makefile b/greek/blends/gis/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/blends/gis/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/blends/gis/about.wml b/greek/blends/gis/about.wml deleted file mode 100644 index 5341426a6e2..00000000000 --- a/greek/blends/gis/about.wml +++ /dev/null @@ -1,36 +0,0 @@ -#use wml::debian::blend title="About the Blend" -#use "navbar.inc" -#use wml::debian::translation-check translation="6d2e0afb56e760364713c2cca2c9f6407c9a744f" maintainer="galaxico" - -<p>The <b>Debian GIS Pure Blend</b> is a project of the <a -href="https://wiki.debian.org/Teams/DebianGis">Debian GIS Team</a> -who collaborate on maintenance of GIS related packages for Debian. -Every <a href="https://blends.debian.org/">Pure Blend</a> is a subset of Debian -that is configured to support a particular target group out-of-the-box. This -blend aims to support the needs of those working with map data, remote -sensing and earth observation.</p> - -<p>The Blend is built from a curated list of GIS software in Debian. -The two main outputs from the Blend are a collection of "metapackages" and live -images that can be put onto a DVD or a USB stick.</p> - -<h2>Metapackages</h2> - -<p>Metapackages in Debian are packages that can be installed just like other -packages but that do not contain any software themselves, instead instructing -the packaging system to install a group of other packages.</p> - -<p>See <a href="./get/metapackages">using the metapackages</a> for more -information on which metapackages are available and how to install the -metapackages on an existing Debian system.</p> - -<h2>Live Images</h2> - -<p>If you're new to Debian and you'd like to try the Debian GIS Pure Blend -without installing it on your computer, or if you'd like to perform a fresh -installation of Debian with all the GIS software ready-to-go, you -might find the live images useful. Images are produced that can be run from -DVDs or USB sticks on both 32-bit and 64-bit Intel architectures.</p> - -<p>See the <a href="./get/live">live images page</a> for more information.</p> - diff --git a/greek/blends/gis/contact.wml b/greek/blends/gis/contact.wml deleted file mode 100644 index 9b627ca1d8e..00000000000 --- a/greek/blends/gis/contact.wml +++ /dev/null @@ -1,15 +0,0 @@ -#use wml::debian::blend title="Contact" -#use "navbar.inc" -#use wml::debian::translation-check translation="119bc3a5217d95aec18b7362bcbdc917ec862ce8" maintainer="galaxico" - -<p>The primary point of contact for GIS related topics in Debian is the -Debian GIS Pure Blend team. You can contact the team by email or by -IRC. Note that if you contact the team by email, this email will be publicly -available <a href="https://lists.debian.org/debian-gis/">in the list -archives</a>.</p> - -<ul> -<li>E-Mail: <a href="mailto:debian-gis@lists.debian.org">debian-gis@lists.debian.org</a></li> -<li>IRC: <a href="irc://irc.debian.org/debian-gis">#debian-gis</a> on <a href="http://oftc.net/">OFTC</a></li> -</ul> - diff --git a/greek/blends/gis/deriv.wml b/greek/blends/gis/deriv.wml deleted file mode 100644 index 1829ea50777..00000000000 --- a/greek/blends/gis/deriv.wml +++ /dev/null @@ -1,46 +0,0 @@ -#use wml::debian::blend title="Derivatives" -#use "navbar.inc" -#use wml::debian::translation-check translation="a2385eca625b03cb7d545f28b511d14a5f12adbe" maintainer="galaxico" - -<p>The Debian source packages maintained by the Debian GIS team are also used -by efforts to support current GIS software on Debian derivatives. This page lists -some of the derivative efforts we are aware of.</p> - -<hr> - -<h2><img src="Pics/UbuntuGIS.png" alt="UbuntuGIS"></h2> - -<ul> -<li>Website: <a href="https://wiki.ubuntu.com/UbuntuGIS">https://wiki.ubuntu.com/UbuntuGIS</a></li> -</ul> - -<p>UbuntuGIS provides backports of GIS packages for Ubuntu. Your Ubuntu is -ready for daily, professional GIS work. Getting started it's just a matter of -minutes. After adding the UbuntuGIS repository corresponding to their -distribution (in sources.list), you can easily install on your machine each of -the GIS applications listed below (in brackets the package name), through the -Synaptic Package Manager or typing sudo apt-get install program-name from the -command line, just like any other package.</p> - -<hr> - -<h2><img src="Pics/OSGeo-Live.png" alt="OSGeo-Live"></h2> - -<ul> -<li>Website: <a href="http://live.osgeo.org/">http://live.osgeo.org/</a></li> -</ul> - -<p>OSGeo-Live is a self-contained bootable DVD, USB thumb drive or Virtual -Machine based on Lubuntu, that allows you to try a wide variety of open source -geospatial software without installing anything. It is composed entirely of -free software, allowing it to be freely distributed, duplicated and passed -around. It provides pre-configured applications for a range of geospatial use -cases, including storage, publishing, viewing, analysis and manipulation of -data. It also contains sample datasets and documentation.</p> - -<hr> - -<p>If you're aware of a derivative that is not listed on this page, please -<a href="mailto:debian-gis@lists.debian.org">send us an email</a> to have it -included.</p> - diff --git a/greek/blends/gis/get/Makefile b/greek/blends/gis/get/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/blends/gis/get/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/blends/gis/get/index.wml b/greek/blends/gis/get/index.wml deleted file mode 100644 index b5e4e99dbd1..00000000000 --- a/greek/blends/gis/get/index.wml +++ /dev/null @@ -1,48 +0,0 @@ -#use wml::debian::blend title="Getting the blend" -#use wml::debian::blends::gis -#use "../navbar.inc" -#use wml::debian::translation-check translation="289205d50f64d1fbef6272d8b76dbfdbd5b0af6f" maintainer="galaxico" - -<p>The Debian GIS Pure Blend is distributed <a href="../../../intro/free">freely</a> -over Internet.</p> -<p>If you want to use the Blend, these are your options:</p> -<div class="line"> - <div class="item col50"> - <h2><a href="./metapackages">Use the metapackages</a></h2> - <p>Depending on your needs, you can install one or more of the following metapackages on an existing Debian installation:</p> - <ul class="quicklist downlist"> - <li><a title="See information for gis-data" - href="https://packages.debian.org/unstable/gis-data">gis-data</a></li> - <li><a title="See information for gis-devel" - href="https://packages.debian.org/unstable/gis-devel">gis-devel</a></li> - <li><a title="See information for gis-gps" - href="https://packages.debian.org/unstable/gis-gps">gis-gps</a></li> - <li><a title="See information for gis-osm" - href="https://packages.debian.org/unstable/gis-osm">gis-osm</a></li> - <li><a title="See information for gis-remotesensing" - href="https://packages.debian.org/unstable/gis-remotesensing">gis-remotesensing</a></li> - <li><a title="See information for gis-statistics" - href="https://packages.debian.org/unstable/gis-statistics">gis-statistics</a></li> - <li><a title="See information for gis-web" - href="https://packages.debian.org/unstable/gis-web">gis-web</a></li> - <li><a title="See information for gis-workstation" - href="https://packages.debian.org/unstable/gis-workstation">gis-workstation</a></li> - </ul> - </div> - <div class="item col50 lastcol"> - <h2><a href="./live">Download a live image</a></h2> - <p> - You can try the Blend by booting a live system from a DVD or USB key - without installing any files to the computer. When you are ready, you can - run the included installer. - </p> - <ul class="quicklist downlist"> - <li><a title="Download live image for 64-bit Intel and AMD PC" - href="<stable-amd64-url/>">64-bit PC live</a></li> - <li><a title="Download live image 32-bit Intel and AMD PC" - href="<stable-i386-url/>">32-bit PC live</a></li> - </ul> - </div> -</div> -<div class="clr"></div> - diff --git a/greek/blends/gis/get/live.wml b/greek/blends/gis/get/live.wml deleted file mode 100644 index 36117f1c85e..00000000000 --- a/greek/blends/gis/get/live.wml +++ /dev/null @@ -1,56 +0,0 @@ -#use wml::debian::blend title="Download Live Images" -#use wml::debian::blends::gis -#use "../navbar.inc" -#use wml::debian::translation-check translation="a2a93c6af14d9de0d3c3aa2b2d7fa4d06a48ee43" maintainer="galaxico" - -<p>The Debian GIS Pure Blend produces <b>Live DVD images</b> that can -be used to try out the Debian GIS Pure Blend on a computer without -having to install it first. The images also contain an installer which can -be used to install Debian along with the packages from the blend.</p> - -<h2>Debian GIS Blend <em>stable</em></h2> - -<p>A preview release of the Debian GIS Blend Live DVD is available -for download.</p> - -<p>The latest stable release is: <strong><stable-version/></strong>.</p> - -<ul> - <li><a href="<stable-amd64-url/>">amd64 Live DVD image (ISO)</a> - <li><a href="<stable-i386-url/>">i386 Live DVD image (ISO)</a> - <li><a href="<stable-source-url/>">Live DVD image Source Archive (tar)</a> -</ul> - -<p>For webboot images, checksums and GPG signatures, see the <a -href="https://cdimage.debian.org/cdimage/blends-live/">full file -listing</a>.</p> - -<h2>Debian GIS Blend <em>testing</em></h2> - -<p>In the near future, live DVDs will be built for stretch (the current -Debian testing distribution) although these are not currently -available.</p> - -<h2>Getting Started</h2> - -<h3>Using a DVD</h3> - -<p>Most modern operating systems will have provisions for burning ISO images -to DVD media. The Debian CD FAQ provides instructions for burning ISO images -using <a href="https://www.debian.org/CD/faq/index#record-unix">Linux</a>, <a -href="https://www.debian.org/CD/faq/index#record-windows">Windows</a> and <a -href="https://www.debian.org/CD/faq/index#record-mac">Mac OS</a>. If you are -having difficulty, using a web search engine should provide the answers you -need.</p> - -<h3>Using a USB stick</h3> - -<p>The ISO images are built as hybrid images, so you can copy them directly to -a USB stick without using any special software like unetbootin. On a Linux -system, you can do this like so:</p> - -<pre>sudo dd if=/path/to/debian-gis-live-image.iso of=/dev/sd<b>X</b></pre> - -<p>The output of the dmesg command should let you know the device name of the -USB stick where you will need to change the <b>X</b> to the letter given.</p> - diff --git a/greek/blends/gis/get/metapackages.wml b/greek/blends/gis/get/metapackages.wml deleted file mode 100644 index 427db3887e5..00000000000 --- a/greek/blends/gis/get/metapackages.wml +++ /dev/null @@ -1,76 +0,0 @@ -#use wml::debian::blend title="Using the metapackages" -#use "../navbar.inc" -#use wml::debian::translation-check translation="7699c3698cd2627c6da0718bd3329188b02ad8c6" maintainer="galaxico" - -<p>Metapackages are used by the blend as a convinient way of collecting -together related software packages. Each metapackage when installed will cause -the package management system to install the packages related to the task.</p> - -<p>The following metapackages are currently maintained by the blend:</p> - -<table> - <tr><th>Task name</th><th>Metapackage</th><th>Description</th><th>Catalogue</th></tr> - <tr> - <td>gis-data</td> - <td><a href="https://packages.debian.org/unstable/gis-data"><code>gis-data</code></a></td> - <td>This task contains packages providing data that can be used - by different GIS applications.</td> - <td><a href="https://blends.debian.org/gis/tasks/data">Link</a></td> - </tr> - <tr> - <td>gis-devel</td> - <td><a href="https://packages.debian.org/unstable/gis-devel"><code>gis-devel</code></a></td> - <td>This task sets up your system for GIS development.</td> - <td><a href="https://blends.debian.org/gis/tasks/devel">Link</a></td> - </tr> - <tr> - <td>gis-gps</td> - <td><a href="https://packages.debian.org/unstable/gis-gps"><code>gis-gps</code></a></td> - <td>Set of Debian packages which are dealing with GPS devices and data.</td> - <td><a href="https://blends.debian.org/gis/tasks/gps">Link</a></td> - </tr> - <tr> - <td>gis-osm</td> - <td><a href="https://packages.debian.org/unstable/gis-osm"><code>gis-osm</code></a></td> - <td>Set of Debian packages which are dealing with OpenStreetMap data.</td> - <td><a href="https://blends.debian.org/gis/tasks/osm">Link</a></td> - </tr> - <tr> - <td>gis-remotesensing</td> - <td><a href="https://packages.debian.org/unstable/gis-remotesensing"><code>gis-remotesensing</code></a></td> - <td>Debian packages which are dealing with Remote Sensing (for - instance Synthetic Aperture Radar -- SAR) processing (interferometry, - polarimetry, data visualization, etc) and earth observation.</td> - <td><a href="https://blends.debian.org/gis/tasks/remotesensing">Link</a></td> - </tr> - <tr> - <td>gis-statistics</td> - <td><a href="https://packages.debian.org/unstable/gis-statistics"><code>gis-statistics</code></a></td> - <td>Set of Debian packages which are useful for doing statistics with geographical data.</td> - <td><a href="https://blends.debian.org/gis/tasks/statistics">Link</a></td> - </tr> - <tr> - <td>gis-web</td> - <td><a href="https://packages.debian.org/unstable/gis-web"><code>gis-web</code></a></td> - <td>Debian packages which are dealing with geographical information to be presented for the web on so called map tile servers. These are pretty useful when trying to setup an OpenStreetMap tile server but not restricted to OpenStreetMap data only.</td> - <td><a href="https://blends.debian.org/gis/tasks/web">Link</a></td> - </tr> - <tr> - <td>gis-workstation</td> - <td><a href="https://packages.debian.org/unstable/gis-workstation"><code>gis-workstation</code></a></td> - <td>This task sets up your system to be a GIS workstation to - process geographical information and make maps.</td> - <td><a href="https://blends.debian.org/gis/tasks/workstation">Link</a></td> - </tr> -</table> - -<p>To install any of the task metapackages, use your favourite package -management tool as you would with any other Debian package. For -<code>apt-get</code>:</p> - -<pre>apt-get install gis-<task></pre> - -<p>If you want to install the entire blend:</p> - -<pre>apt-get install gis-data gis-devel gis-gps gis-osm gis-remotesensing gis-statistics gis-web gis-workstation</pre> - diff --git a/greek/blends/gis/index.wml b/greek/blends/gis/index.wml deleted file mode 100644 index 6efc46a5e73..00000000000 --- a/greek/blends/gis/index.wml +++ /dev/null @@ -1,60 +0,0 @@ -#use wml::debian::blend title="Debian GIS Pure Blend" NOHEADER="true" BLENDHOME="true" BARETITLE="true" -#use wml::debian::recent_list -#use wml::debian::blends::gis -#use wml::debian::translation-check translation="c738dce70d430aa2486f7620f40ea3489aae4526" maintainer="galaxico" - -# translators: you need to translate the navbar.inc file so this page (when translated) is correctly built and shown - -<span class="download"><a href="<stable-amd64-url/>"> -Download Debian GIS <stable-version/><br/><em>(64-bit LiveDVD)</em></a> -</span> -<div id="splash"> - <h1 id="gis">Debian GIS Pure Blend</h1> -</div> - -<p>Debian GIS is a "<a href="../">Debian Pure Blend</a>" with the aim to -develop Debian into the best distribution for <strong>Geographical Information -System</strong> applications and users.</p> - -<p>A good deal of GIS related software and libraries (e.g. GRASS GIS, GDAL, and -PROJ.4) are already present in Debian.</p> - -<p>Thanks to efforts of the Debian GIS team, we currently have many exciting -GIS packages in Debian's main archives. Other programs are well along their way -to being included in the archive.</p> - -<p>The Debian source packages maintained by the Debian GIS team are also used -by efforts to support current GIS software on Debian derivatives such as -<a href="https://wiki.ubuntu.com/UbuntuGIS">UbuntuGIS</a>, which provides -backports of GIS packages for Ubuntu, and <a -href="http://live.osgeo.org/">OSGeo-Live</a> for their Ubuntu based -distribution.</p> - -<div id="hometoc"> -<ul id="hometoc-cola"> - <li><a href="./about">About the blend</a></li> - <li><a href="./contact">Contact us</a></li> -</ul> -<ul id="hometoc-colb"> - <li><a href="./get/">Getting the blend</a> - <ul> - <li><a href="./get/live">Download live images</a></li> - <li><a href="./get/metapackages">Using the metapackages</a></li> - </ul></li> -</ul> -<ul id="hometoc-colc"> - <li><a href="./deriv">Derivatives</a></li> -</ul> -<ul id="hometoc-cold"> - <li><a href="https://wiki.debian.org/DebianGis">Development</a> - <ul> - <li><a href="<gis-policy-html/>">GIS Team Policy</a></li> - </ul> - </li> -</ul> -<ul id="hometoc-cole"> - <li><a href="https://twitter.com/DebianGIS"><img src="Pics/twitter.gif" alt="Twitter" width="80" height="15" /></a></li> -</ul> -</div> - - diff --git a/greek/blends/gis/navbar.inc b/greek/blends/gis/navbar.inc deleted file mode 100644 index 6d686c4ba0c..00000000000 --- a/greek/blends/gis/navbar.inc +++ /dev/null @@ -1,25 +0,0 @@ -#use wml::debian::blends::gis - -{#alternate_navbar#: - <div id="second-nav"> - <p><a href="$(HOME)/blends/gis/">Debian GIS Blend</a></p> - <ul> - <li><a href="$(HOME)/blends/gis/about">About</a></li> - <li><a href="$(HOME)/blends/gis/contact">Contact</a></li> - <li><a href="$(HOME)/blends/gis/get/">Getting the Blend</a> - <ul> - <li><a href="$(HOME)/blends/gis/get/live">Download live images</a></li> - <li><a href="$(HOME)/blends/gis/get/metapackages">Using the metapackages</a></li> - </ul> - </li> - <li><a href="$(HOME)/blends/gis/support">Support</a></li> - <li><a href="$(HOME)/blends/gis/deriv">Derivatives</a></li> - <li><a href="https://wiki.debian.org/DebianGIS#Development">Development</a> - <ul> - <li><a href="<gis-policy-html/>">GIS Team Policy</a></li> - </ul> - </li> - <li><a href="https://twitter.com/DebianGIS"><img src="$(HOME)/blends/gis/Pics/twitter.gif" alt="Twitter" width="80" height="15"></a></li> - </ul> - </div> -:#alternate_navbar#} diff --git a/greek/blends/hamradio/Makefile b/greek/blends/hamradio/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/blends/hamradio/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/blends/hamradio/about.wml b/greek/blends/hamradio/about.wml deleted file mode 100644 index 81b05c3fe41..00000000000 --- a/greek/blends/hamradio/about.wml +++ /dev/null @@ -1,23 +0,0 @@ -#use wml::debian::blend title="About the Blend" -#use "navbar.inc" -#use wml::debian::translation-check translation="9bc4ecf1abce08efe4132833b3d0ba344ca3ff10" maintainer="galaxico" - -<p>The <b>Debian Hamradio Pure Blend</b> is a project of the <a -href="https://wiki.debian.org/DebianHams/">Debian Hamradio Maintainers Team</a> -who collaborate on maintenance of amateur-radio related packages for Debian. -Every <a href="https://blends.debian.org/">Pure Blend</a> is a subset of Debian -that is configured to support a particular target group out-of-the-box. This -blend aims to support the needs of radio amateurs.</p> - -<p>The Blend is built from a curated list of amateur radio software in Debian. -</p> - -<h2>Metapackages</h2> - -<p>Metapackages in Debian are packages that can be installed just like other -packages but that do not contain any software themselves, instead instructing -the packaging system to install a group of other packages.</p> - -<p>See <a href="./get/metapackages">using the metapackages</a> for more -information on which metapackages are available and how to install the -metapackages on an existing Debian system.</p> diff --git a/greek/blends/hamradio/contact.wml b/greek/blends/hamradio/contact.wml deleted file mode 100644 index db293e6613b..00000000000 --- a/greek/blends/hamradio/contact.wml +++ /dev/null @@ -1,15 +0,0 @@ -#use wml::debian::blend title="Contact" -#use "navbar.inc" -#use wml::debian::translation-check translation="6e56b4e2dbb6e975651897056c57191cdc6f00b4" maintainer="galaxico" - -<p>The primary point of contact for hamradio related topics in Debian is the -Debian Hamradio Maintainers team. You can contact the team by email or by -IRC. Note that if you contact the team by email, this email will be publicly -available <a href="https://lists.debian.org/debian-hams/">in the list -archives</a>.</p> - -<ul> -<li>E-Mail: <a href="mailto:debian-hams@lists.debian.org">debian-hams@lists.debian.org</a></li> -<li>IRC: <a href="irc://irc.debian.org/debian-hams">#debian-hams</a> on <a href="http://oftc.net/">OFTC</a></li> -</ul> - diff --git a/greek/blends/hamradio/dev.wml b/greek/blends/hamradio/dev.wml deleted file mode 100644 index 04db3fa3acf..00000000000 --- a/greek/blends/hamradio/dev.wml +++ /dev/null @@ -1,56 +0,0 @@ -#use wml::debian::blend title="Blend Development" -#use "navbar.inc" -#use wml::debian::translation-check translation="c3a3b8986d2ffef95ef7bb8f7d99f36678ff0e8f" maintainer="galaxico" - -<h2>Packaging</h2> - -<p>While packaging of hamradio software in Debian is the responsibility -of the <a href="https://pkg-hamradio.alioth.debian.org">Debian Hamradio Maintainers</a>, -the pure blend project does provide the following tools that may be useful -to packagers:</p> - -<ul> - <li><a href="https://blends.debian.org/hamradio/tasks/">Blend Tasks Index</a></li> - <li><a href="https://blends.debian.org/hamradio/bugs/">Blend Bugs Overview</a></li> - <li><a href="https://blends.debian.org/hamradio/thermometer/">Blend Thermometer</a></li> -</ul> - -<h2>Metapackages Source Code</h2> - -<ul> - <li><a href="https://salsa.debian.org/blends-team/hamradio">Web-based git browser</a></li> - <li><a href="https://salsa.debian.org/blends-team/hamradio.git">Anonymous git clone</a></li> -</ul> - -<pre>git clone https://salsa.debian.org/blends-team/hamradio -cd hamradio ; make dist -gbp buildpackage</pre> - -<p><i>Note: you will need <a -href="https://packages.debian.org/unstable/git-buildpackage">git-buildpackage</a> -and <a href="https://packages.debian.org/unstable/blends-dev">blends-dev</a> -installed to build the source.</i></p> - -<p>To learn more about how to work with blends metapackages, see <a href="https://blends.debian.org/blends/ch06.html#metapackages">§6.1</a> of the <a href="https://blends.debian.org/blends/">Debian Pure Blends Manual</a>.</p> - -<h2>Live DVD Source Code</h2> - -<ul> - <li><a href="https://salsa.debian.org/blends-team/blends-images">Web-based git browser</a></li> - <li><a href="https://salsa.debian.org/blends-team/blends-images.git">Anonymouse git clone</a></li> -</ul> - -<pre>git clone https://salsa.debian.org/blends-team/blends-images.git -cd blends-images/images/hamradio-amd64 -lb config -sudo lb build</pre> - -<p><i>Note: you will need <a - href="https://packages.debian.org/unstable/git-buildpackage">git-buildpackage</a> - and <a href="https://packages.debian.org/unstable/live-build">live build</a> - installed to build the source.</i></p> - -<p>To learn more about how to work with live-build sources, see the <a - href="http://live.debian.net/manual/unstable/html/live-manual/toc.en.html">Live - Systems Manual</a>.</p> - diff --git a/greek/blends/hamradio/docs/Makefile b/greek/blends/hamradio/docs/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/blends/hamradio/docs/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/blends/hamradio/docs/index.wml b/greek/blends/hamradio/docs/index.wml deleted file mode 100644 index a305902d54a..00000000000 --- a/greek/blends/hamradio/docs/index.wml +++ /dev/null @@ -1,35 +0,0 @@ -#use wml::debian::blend title="Documentation" -#use "../navbar.inc" -#use wml::debian::translation-check translation="27a7be18daa00f21db14cd22b5eeb82ca0902330" maintainer="galaxico" - -<p> -There are many sources of documentation available for using hamradio software -in Debian. All software packages will have man pages included and many also -include HTML or PDF-formatted documentation too. -</p> - -<p> -<em>A comprehensive guide for using amateur radio software in Debian is -currently in development but is not yet available. If you would like to -contribute to this effort, please see <a -href="https://wiki.debian.org/DebianHams/Handbook">the related wiki -page</a>.</em> -</p> - -<h2>man pages</h2> - -<p> -According to Debian policy, every application in Debian must contain a man -page and these can be very informative. They are typically more useful for -command-line driven applications although can also provide useful information -for GUI applications. To view the man page for an installed application, run: -</p> - -<pre>$ man <application></pre> - -<p> -If you'd like to view the man page for an application that you do not currently -have installed, you can search at <a -href="https://manpages.debian.org/">manpages.debian.org</a>. -</p> - diff --git a/greek/blends/hamradio/get/Makefile b/greek/blends/hamradio/get/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/blends/hamradio/get/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/blends/hamradio/get/index.wml b/greek/blends/hamradio/get/index.wml deleted file mode 100644 index bc969e3e709..00000000000 --- a/greek/blends/hamradio/get/index.wml +++ /dev/null @@ -1,43 +0,0 @@ -#use wml::debian::blend title="Getting the blend" -#use wml::debian::blends::hamradio -#use "../navbar.inc" -# This page is nowhere near done -#use wml::debian::translation-check translation="9bc4ecf1abce08efe4132833b3d0ba344ca3ff10" maintainer="galaxico" - -<p>The Debian Hamradio Pure Blend is distributed <a href="../../../intro/free">freely</a> -over Internet.</p> -<p>If you want to use the Blend, these are your options:</p> -<div class="line"> - <div class="item col50"> - <h2><a href="./metapackages">Use the metapackages</a></h2> - <p>Depending on your needs, you can install one or more of the following metapackages on an existing Debian installation:</p> - <ul class="quicklist downlist"> - <li><a title="See information for hamradio-antenna" - href="https://packages.debian.org/unstable/hamradio-antenna">hamradio-antenna</a></li> - <li><a title="See information for hamradio-datamodes" - href="https://packages.debian.org/unstable/hamradio-datamodes">hamradio-datamodes</a></li> - <li><a title="See information for hamradio-digitalvoice" - href="https://packages.debian.org/unstable/hamradio-digitalvoice">hamradio-digitalvoice</a></li> - <li><a title="See information for hamradio-logging" - href="https://packages.debian.org/unstable/hamradio-logging">hamradio-logging</a></li> - <li><a title="See information for hamradio-morse" - href="https://packages.debian.org/unstable/hamradio-morse">hamradio-morse</a></li> - <li><a title="See information for hamradio-nonamateur" - href="https://packages.debian.org/unstable/hamradio-nonamateur">hamradio-nonamateur</a></li> - <li><a title="See information for hamradio-packetmodes" - href="https://packages.debian.org/unstable/hamradio-packetmodes">hamradio-packetmodes</a></li> - <li><a title="See information for hamradio-rigcontrol" - href="https://packages.debian.org/unstable/hamradio-rigcontrol">hamradio-rigcontrol</a></li> - <li><a title="See information for hamradio-satellite" - href="https://packages.debian.org/unstable/hamradio-satellite">hamradio-satellite</a></li> - <li><a title="See information for hamradio-sdr" - href="https://packages.debian.org/unstable/hamradio-sdr">hamradio-sdr</a></li> - <li><a title="See information for hamradio-tools" - href="https://packages.debian.org/unstable/hamradio-tools">hamradio-tools</a></li> - <li><a title="See information for hamradio-training" - href="https://packages.debian.org/unstable/hamradio-training">hamradio-training</a></li> - </ul> - </div> -</div> -<div class="clr"></div> - diff --git a/greek/blends/hamradio/get/metapackages.wml b/greek/blends/hamradio/get/metapackages.wml deleted file mode 100644 index 4988dc98712..00000000000 --- a/greek/blends/hamradio/get/metapackages.wml +++ /dev/null @@ -1,108 +0,0 @@ -#use wml::debian::blend title="Using the metapackages" -#use "../navbar.inc" -#use wml::debian::translation-check translation="6d2e0afb56e760364713c2cca2c9f6407c9a744f" maintainer="galaxico" - -<p>Metapackages are used by the blend as a convinient way of collecting -together related software packages. Each metapackage when installed will cause -the package management system to install the packages related to the task.</p> - -<p>The following metapackages are currently maintained by the blend:</p> - -<table> - <tr><th>Task name</th><th>Metapackage</th><th>Description</th><th>Catalogue</th></tr> - <tr> - <td>Antennas</td> - <td><a href="https://packages.debian.org/unstable/hamradio-antenna"><code>hamradio-antenna</code></a></td> - <td>This task contains packages that are useful for antenna modelling.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/antenna">Link</a></td> - </tr> - <tr> - <td>Data Modes</td> - <td><a href="https://packages.debian.org/unstable/hamradio-datamodes"><code>hamradio-datamodes</code></a></td> - <td>This task contains packages that are useful for using data modes, such as - RTTY and SSTV, including weak signal modes, such as JT65.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/datamodes">Link</a></td> - </tr> - <tr> - <td>Digital Voice</td> - <td><a href="https://packages.debian.org/unstable/hamradio-digitalvoice"><code>hamradio-digitalvoice</code></a></td> - <td>This task contains packages that are useful for using - digital voice modes on RF and for Internet linking. - <td><a href="https://blends.debian.org/hamradio/tasks/digitalvoice">Link</a></td> - </tr> - <tr> - <td>Logging</td> - <td><a href="https://packages.debian.org/unstable/hamradio-logging"><code>hamradio-logging</code></a></td> - <td>This task contains packages that are useful for logging (including for - contests).</td> - <td><a href="https://blends.debian.org/hamradio/tasks/logging">Link</a></td> - </tr> - <tr> - <td>Morse</td> - <td><a href="https://packages.debian.org/unstable/hamradio-morse"><code>hamradio-morse</code></a></td> - <td>This task contains packages that are useful for CW operation and - for learning morse.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/morse">Link</a></td> - </tr> - <tr> - <td>Non-Amateur Modes</td> - <td><a href="https://packages.debian.org/unstable/hamradio-nonamateur"><code>hamradio-nonamateur</code></a></td> - <td>This task contains packages that are useful for listening to non-amateur - modes such as AIS and ADS-B.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/nonamateur">Link</a></td> - </tr> - <tr> - <td>Packet Modes</td> - <td><a href="https://packages.debian.org/unstable/hamradio-packetmodes"><code>hamradio-packetmodes</code></a></td> - <td>This task contains packages that are useful for using AX.25, including IPv4 - over AX.25 and APRS.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/packetmodes">Link</a></td> - </tr> - <tr> - <td>Rig Control</td> - <td><a href="https://packages.debian.org/unstable/hamradio-rigcontrol"><code>hamradio-rigcontrol</code></a></td> - <td>This task contains packages that are useful for rig control and - programming.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/rigcontrol">Link</a></td> - </tr> - <tr> - <td>Satellite operation</td> - <td><a href="https://packages.debian.org/unstable/hamradio-satellite"><code>hamradio-satellite</code></a></td> - <td>This task contains packages that are useful for amateur satellite operation.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/satellite">Link</a></td> - </tr> - <tr> - <td>Software-Defined Radio</td> - <td><a href="https://packages.debian.org/unstable/hamradio-sdr"><code>hamradio-sdr</code></a></td> - <td>This task contains packages that are useful for working with software-defined radio.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/sdr">Link</a></td> - </tr> - <tr> - <td>Tools</td> - <td><a href="https://packages.debian.org/unstable/hamradio-tools"><code>hamradio-tools</code></a></td> - <td>This task contains packages that provide useful hamradio related tools.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/tools">Link</a></td> - </tr> - <tr> - <td>Training</td> - <td><a href="https://packages.debian.org/unstable/hamradio-training"><code>hamradio-training</code></a></td> - <td>This task contains packages that are useful when training - for hamradio exams.</td> - <td><a href="https://blends.debian.org/hamradio/tasks/training">Link</a></td> - </tr> -</table> - -<p><i>Note: The metapackages have only recently been introduced to the -archives. These will only be available in Debian stretch (testing), and are not -available in Debian jessie (stable).</i></p> - -<p>To install any of the task metapackages, use your favourite package -management tool as you would with any other Debian package. For -<code>apt-get</code>:</p> - -<pre>apt-get install hamradio-<task></pre> - -<p>If you want to install the entire blend:</p> - -<pre>apt-get install hamradio-antenna hamradio-datamodes hamradio-digitalvoice hamradio-logging hamradio-morse hamradio-nonamateur hamradio-packetmodes hamradio-rigcontrol hamradio-satellite hamradio-sdr hamradio-tasks hamradio-tools hamradio-training</pre> - diff --git a/greek/blends/hamradio/index.wml b/greek/blends/hamradio/index.wml deleted file mode 100644 index 0e8d8570ce9..00000000000 --- a/greek/blends/hamradio/index.wml +++ /dev/null @@ -1,63 +0,0 @@ -#use wml::debian::blend title="Debian Hamradio Pure Blend" NOHEADER="true" BLENDHOME="true" -#use wml::debian::recent_list -#use wml::debian::blends::hamradio -#use wml::debian::translation-check translation="6d2e0afb56e760364713c2cca2c9f6407c9a744f" maintainer="galaxico" - -<div id="splash"> - <h1 id="hamradio">Debian Hamradio Pure Blend</h1> -</div> - -<p>The <b>Debian Hamradio Pure Blend</b> is a project of the <a -href="https://wiki.debian.org/DebianHams/">Debian Hamradio Maintainers Team</a> -who collaborate on maintenance of amateur-radio related packages for Debian. -Every <a href="https://blends.debian.org/">Pure Blend</a> is a subset of Debian -that is configured to support a particular target group out-of-the-box. This -blend aims to support the needs of radio amateurs.</p> - -<p><a href="./about">Read more…</a></p> - -<div id="hometoc"> -<ul id="hometoc-cola"> - <li><a href="./about">About the blend</a></li> - <li><a href="./News/">News archives</a></li> - <li><a href="./contact">Contact us</a></li> -</ul> -<ul id="hometoc-colb"> - <li><a href="./get/">Getting the blend</a> - <ul> - <li><a href="./get/metapackages">Using the metapackages</a></li> - </ul></li> -</ul> -<ul id="hometoc-colc"> - <li><a href="./docs">Documentation</a> - <ul> - <li><a href="<hamradio-handbook-html/>">Debian Hamradio Handbook</a></li> - </ul></li> - <li><a href="./support">Support</a></li> -</ul> -<ul id="hometoc-cold"> - <li><a href="./dev">Development</a> - <ul> - <li><a href="https://wiki.debian.org/DebianHams">Hamradio Maintainers Team</a></li> - <li><a href="<hamradio-maintguide-html/>">Hamradio Maintainers Guide</a></li> - </ul> - </li> -</ul> -<ul id="hometoc-cole"> - <li><a href="https://twitter.com/DebianHamradio"><img src="Pics/twitter.gif" alt="Twitter" width="80" height="15" /></a></li> -</ul> -</div> - -<h2>Getting Started</h2> - -<ul> -<li>If you've already got Debian installed, check out the <a href="./get/metapackages">list of metapackages</a> to discover amateur radio software you can install.</li> -<li>To get help in using amateur radio software in Debian, you can use one of our <a href="./support">support channels</a>.</li> -</ul> - -<h2>News</h2> - -<p><:= get_recent_list('News/$(CUR_YEAR)', '6', -'$(ENGLISHDIR)/blends/hamradio', '', '\d+\w*' ) :> -</p> - diff --git a/greek/blends/hamradio/navbar.inc b/greek/blends/hamradio/navbar.inc deleted file mode 100644 index 3fd3498d7a6..00000000000 --- a/greek/blends/hamradio/navbar.inc +++ /dev/null @@ -1,30 +0,0 @@ -#use wml::debian::blends::hamradio - -{#alternate_navbar#: - <div id="second-nav"> - <p><a href="$(HOME)/blends/hamradio/">Debian Hamradio Blend</a></p> - <ul> - <li><a href="$(HOME)/blends/hamradio/about">About</a></li> - <li><a href="$(HOME)/blends/hamradio/News/">News Archives</a></li> - <li><a href="$(HOME)/blends/hamradio/contact">Contact</a></li> - <li><a href="$(HOME)/blends/hamradio/get/">Getting the Blend</a> - <ul> - <li><a href="$(HOME)/blends/hamradio/get/metapackages">Using the metapackages</a></li> - </ul> - </li> - <li><a href="$(HOME)/blends/hamradio/docs/">Documentation</a> - <ul> - <li><a href="<hamradio-handbook-html/>">Debian Hamradio Handbook</a></li> - </ul> - </li> - <li><a href="$(HOME)/blends/hamradio/support">Support</a></li> - <li><a href="$(HOME)/blends/hamradio/dev">Development</a> - <ul> - <li><a href="https://wiki.debian.org/DebianHams">Hamradio Maintainers Team</a></li> - <li><a href="<hamradio-maintguide-html/>">Hamradio Maintainers Guide</a></li> - </ul> - </li> - <li><a href="https://twitter.com/DebianHamradio"><img src="$(HOME)/blends/hamradio/Pics/twitter.gif" alt="Twitter" width="80" height="15"></a></li> - </ul> - </div> -:#alternate_navbar#} diff --git a/greek/blends/hamradio/support.wml b/greek/blends/hamradio/support.wml deleted file mode 100644 index 33f6c3c0425..00000000000 --- a/greek/blends/hamradio/support.wml +++ /dev/null @@ -1,72 +0,0 @@ -#use wml::debian::blend title="Blend Support" -#use "navbar.inc" -#use wml::debian::translation-check translation="12c97b4a86d8b7e64c32dee1081bbf47b0bc84a1" maintainer="galaxico" - -<h2>Documentation</h2> - -<p>Before searching for support from someone else, it's usually good to try to -find an answer to your problem yourself. That way you will usually get the -answers you need, and even if you don't, the experience of reading the -documentation will likely be useful for you in the future.</p> - -<p>See the <a href="./docs">hamradio-specific documentation page</a> or the <a -href="../../doc/">Debian documentation page</a> for a list of documentation -available.</p> - -<h2>Mailing Lists</h2> - -<p>Debian is developed through distributed development all around the world. -Therefore e-mail is a preferred way to discuss various items. Much of the -conversation between Debian developers and users is managed through several -mailing lists.</p> - -# Translators: the first mailing list is English-only. I'll leave it up to you -# as to whether or not you remove reference to this list. - -<p>For support specifically relating to the use of hamradio software you can use -the <a -href="https://lists.alioth.debian.org/mailman/listinfo/pkg-hamradio-user">Debian -hamradio user's mailing list</a>.</p> - -# Translators: please swap this next one out for the local language's list. - -<p>For more general Debian support that is not specifically related to hamradio -software usage, you can use the <a -href="https://lists.debian.org/debian-user/">Debian user mailing list</a>.</p> - -<p>For user support in other languages, please check the <a -href="https://lists.debian.org/users.html">mailing lists index for -users</a>.</p> - -<h2>On-line Real Time Help Using IRC</h2> - -<p><a href="http://www.irchelp.org/">IRC (Internet Relay Chat)</a> is a way -to chat with people from all over the world in real time. -IRC channels dedicated to Debian can be found on -<a href="http://www.oftc.net/">OFTC</a>.</p> - -<p>To connect, you need an IRC client. Some of the most popular clients are -<a href="https://packages.debian.org/stable/net/hexchat">HexChat</a>, -<a href="https://packages.debian.org/stable/net/ircii">ircII</a>, -<a href="https://packages.debian.org/stable/net/irssi">irssi</a>, -<a href="https://packages.debian.org/stable/net/epic5">epic5</a> and -<a href="https://packages.debian.org/stable/net/kvirc">KVIrc</a>, -all of which have been packaged for -Debian. Once you have the client installed, you need to tell it to connect -to the server. In most clients, you can do that by typing:</p> - -<pre> -/server irc.debian.org -</pre> - -<p>Once you are connected, join channel <code>#debian-hamchat</code> by typing</p> - -<pre> -/join #debian-hamchat -</pre> - -<p>Note: clients like HexChat often have a different, graphical user interface -for joining servers/channels.</p> - -<p>There's a number of other IRC networks where you can chat about Debian, -too.</p> diff --git a/greek/consultants/Makefile b/greek/consultants/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/consultants/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/consultants/a_alves.wml b/greek/consultants/a_alves.wml deleted file mode 100644 index 11fb24dc553..00000000000 --- a/greek/consultants/a_alves.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Arthur Alves" -#use wml::debian::translation-check translation="0dae0c37317475be93c9c55a8c3417e0a6072cd8" maintainer="galaxico" - -<p> -Unix Systems Administrator and Linux/Shell/Perl/Python developer with 5 -years of experience, working with GNU/Debian for the past 4 years. Computer -Networking Associate's degree at Estácio de Sá University, Maceió - Brazil. -</p> diff --git a/greek/consultants/abadi_samir.wml b/greek/consultants/abadi_samir.wml deleted file mode 100644 index 7c23bf2eb92..00000000000 --- a/greek/consultants/abadi_samir.wml +++ /dev/null @@ -1,11 +0,0 @@ -#use wml::debian::consultant name="Abadi Samir" -#use wml::debian::translation-check translation="a7d4047d0db4f4cf961d326bffe8b2af15a9db58" original="french" -#use wml::debian::translation-check translation="c0816ff3dae7deb1cd48fb2f83fa934f5e5f3559" maintainer="galaxico" - -<ul> - <li>Specialized in Systems and Networks</li> - <li>B.Sc. in computer science in systems and software</li> - <li>B.Sc. in computer science in company management</li> - <li>M.Sc. in computer science in company management</li> - <li>Seminars and trainings about Linux and Unix</li> -</ul> diff --git a/greek/consultants/abaton.wml b/greek/consultants/abaton.wml deleted file mode 100644 index bab4b905275..00000000000 --- a/greek/consultants/abaton.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="abaton EDV GmbH" -#use wml::debian::translation-check translation="f592f8a79f40d759a1b7d6d56d97526a7e625b1b" original="german" -#use wml::debian::translation-check translation="c0816ff3dae7deb1cd48fb2f83fa934f5e5f3559" maintainer="galaxico" - -<p> - Specialized on web technology, Debian servers & and client services, - Linux clustering, Debian with <acronym lang="en" - title="Storage Attached Networks">SAN</acronym>, <acronym lang="en" - title="Network File System">NFS</acronym>. -</p> diff --git a/greek/consultants/aboo_technology.wml b/greek/consultants/aboo_technology.wml deleted file mode 100644 index cc0524dad85..00000000000 --- a/greek/consultants/aboo_technology.wml +++ /dev/null @@ -1,11 +0,0 @@ -#use wml::debian::consultant name="Aboo Technology" -#use wml::debian::translation-check translation="ecd1cec604366c40610c12a631884166ff48a27e" maintainer="galaxico" - -<ul> - <li>We provide support via: e-mail, phone, remote access or on-site - for customers located in Poland.</li> - <li>Debian GNU/Linux consulting & support: installation, update, - upgrade, securing: LAMP, DNS, DHCP, NFS, Postfix, Exim</li> - <li>Remote system administration</li> - <li>Other IT Consulting Services</li> -</ul> diff --git a/greek/consultants/acu.wml b/greek/consultants/acu.wml deleted file mode 100644 index b053c615934..00000000000 --- a/greek/consultants/acu.wml +++ /dev/null @@ -1,16 +0,0 @@ -#use wml::debian::consultant name="Acu Corporation" -# data updated on 26.11.2014 -#use wml::debian::translation-check translation="3cde1352bd20492e4dc9edd16e0d7714bb06ce51" maintainer="galaxico" - -<p> -We provide design, implementation and tech support for full stack -Linux Based Servers, File and Private Cloud Servers, Virtualization -(KVM) Servers, Web Servers, Course Management Servers (EDXcode and -Moodle), and Bioinformatics (e.g. Whole Genome Analysis). -Debian GNU/Linux is our mainline OS (since 10 years), however, we -provide support for other Linux distributions such as -RedHat Enterprise Linux, CentOS, Scientific Linux. -We have physical locations in Chicago Area and Minnesota, but -we do remote or fly anywhere in US or world to setup servers or for -tech support. -</p> diff --git a/greek/consultants/adamziaja.wml b/greek/consultants/adamziaja.wml deleted file mode 100644 index 52be739f4a4..00000000000 --- a/greek/consultants/adamziaja.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="adamziaja.com" -#use wml::debian::translation-check translation="8d9da31d66e8bcaea060af3d4862c9bce4e8b694" maintainer="galaxico" - -<p> -Debian Maintainer, Linux System Administrator (mainly Debian), IT -Security Specialist (i.a. Computer Forensics, Penetration Testing). -</p> diff --git a/greek/consultants/aerasec.wml b/greek/consultants/aerasec.wml deleted file mode 100644 index 359930ab93f..00000000000 --- a/greek/consultants/aerasec.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="AERAsec GmbH" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Security, complex network scenarios, server strategies. -</p> - -<p> -Also: Munich/Germany. -</p> diff --git a/greek/consultants/aikidev.wml b/greek/consultants/aikidev.wml deleted file mode 100644 index 8511d722fd8..00000000000 --- a/greek/consultants/aikidev.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="Aikidev, LLC" -#use wml::debian::translation-check translation="483bf8427652f4d2fbb66d06ff134a6e993074de" maintainer="galaxico" - -<p> -Aikidev provides consulting services for -thin client and network booted Debian systems, Debian-installer -customizations, and general Debian packaging work, with a focus on -changes that can be merged back into Debian for long-term -sustainability. -</p> diff --git a/greek/consultants/ainstainer.wml b/greek/consultants/ainstainer.wml deleted file mode 100644 index 1c4be47bfe3..00000000000 --- a/greek/consultants/ainstainer.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Ainstainer Software Development Teams" -#use wml::debian::translation-check translation="68a3e31427bf7ea0d24ad1ac289a7a932ab82c54" maintainer="galaxico" - -<p> -All specialists work out the projects remotely and perfectly bring into -effect all the solutions we can offer our customers. -</p> diff --git a/greek/consultants/all2all.wml b/greek/consultants/all2all.wml deleted file mode 100644 index ad85966dee3..00000000000 --- a/greek/consultants/all2all.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Moving Art Studio, all2all.org" -#use wml::debian::translation-check translation="5bde6b137b32232038fdfa566d09781fb7fed39f" maintainer="galaxico" - -<p> -Colocation facilities of dedicated Debian GNU/Linux servers -and Debian shared web hosting. -</p> diff --git a/greek/consultants/anderson.wml b/greek/consultants/anderson.wml deleted file mode 100644 index 91608fdbfab..00000000000 --- a/greek/consultants/anderson.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Anderson Carlos Daniel Sanches" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Development under GPL, server configuration and administration, training. -</p> diff --git a/greek/consultants/andrea_scarso.wml b/greek/consultants/andrea_scarso.wml deleted file mode 100644 index 5a98b145aa9..00000000000 --- a/greek/consultants/andrea_scarso.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Andrea Scarso" -#use wml::debian::translation-check translation="69384d8ce47f0e18730f463e2114618dd8f089ec" maintainer="galaxico" - -<p>Linux System Administrator, I currently work for an Internet Service -Provider. Mail, DNS, proxy, web, security, network configurations: -feel free to contact me for any request. I can suggest a solution and a -quotation you can freely value.</p> diff --git a/greek/consultants/angbert_enterprises.wml b/greek/consultants/angbert_enterprises.wml deleted file mode 100644 index 094f28215c9..00000000000 --- a/greek/consultants/angbert_enterprises.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Angbert Enterprises LLC" -#use wml::debian::translation-check translation="7865f3cdf13d284fa53b8d61017b28d6d2251e7e" maintainer="galaxico" - -<p> -We prefer to work Open Source, but can also work on closed source projects as well. -</p> diff --git a/greek/consultants/axxeo.wml b/greek/consultants/axxeo.wml deleted file mode 100644 index a66ca31a698..00000000000 --- a/greek/consultants/axxeo.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="axxeo GmbH" -#use wml::debian::translation-check translation="34f598bcfd1f8bce119e1f073176df5f80cdd1c8" maintainer="galaxico" - -<p> -Debian installations for customers since 1995, mainly -in the security and networking areas (WAN/LAN/Internet-Provider). -</p><p> -Support for Debian on embedded Systems. -</p> diff --git a/greek/consultants/b1-systems.wml b/greek/consultants/b1-systems.wml deleted file mode 100644 index 50c87fcfe61..00000000000 --- a/greek/consultants/b1-systems.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="B1 Systems GmbH" -#use wml::debian::translation-check translation="8a31ed4859f89eb55ef01046700e7a2897fab29b" maintainer="galaxico" - -<p> -B1 Systems GmbH is specialized in consulting and project work around Open Source -and employs more than 20 consultants in this field. We act internationally in -the topics of virtualization, clustering and performance optimization. We hand -the knowledge we gain in those projects and feasibility studies on in trainings, -workshops, books and presentations. -</p> diff --git a/greek/consultants/beeznest.wml b/greek/consultants/beeznest.wml deleted file mode 100644 index 94a7823e5e6..00000000000 --- a/greek/consultants/beeznest.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="BeezNest" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Can work anywhere in Europe between The Netherlands and Spain, -including Germany, and more if necessary. -</p> diff --git a/greek/consultants/ben_b.wml b/greek/consultants/ben_b.wml deleted file mode 100644 index 032232bf2b4..00000000000 --- a/greek/consultants/ben_b.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Ben Bell" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p>I specialise in design and implementation of infrastructure -- network, -server and software. I have a wide range of experience having worked in -positions ranging from network and systems architecture for an international -ISP through web-based application design and database design to systems -administration.</p> diff --git a/greek/consultants/boguslawski.wml b/greek/consultants/boguslawski.wml deleted file mode 100644 index d1965f7b14b..00000000000 --- a/greek/consultants/boguslawski.wml +++ /dev/null @@ -1,11 +0,0 @@ -#use wml::debian::consultant name="Informatyka Boguslawski" -#use wml::debian::translation-check translation="8ed019be1ea7875caee673ab54357f6a8545b7c4" maintainer="galaxico" - -<p>Informatyka Boguslawski sp. z o.o. sp.k. carries out business activity in the IT market. The Company's offer is addressed to individual clients, small and medium businesses, corporations and public-sector institutions. The Company's object of activity is above all the following:</p> - -<ul> - <li>software implementations, modifications and development,</li> - <li>IT consulting,</li> - <li>maintenance and outsourcing of IT systems,</li> - <li>professional support and popularization of Open Source solutions.</li> -</ul> diff --git a/greek/consultants/centrologic.wml b/greek/consultants/centrologic.wml deleted file mode 100644 index 4c6457b80c7..00000000000 --- a/greek/consultants/centrologic.wml +++ /dev/null @@ -1,20 +0,0 @@ -#use wml::debian::consultant name="Centrologic Computational Logistic Center" -#use wml::debian::translation-check translation="446d75268ef446fa58d5cee95f1dc50121da5dba" maintainer="galaxico" - -<p> -Linux specialists, high availability, clustering, -networking, long distance wireless networks, industrial programming, -remote management and administration, hosting, web -design, server installation, redundancy backups. -</p> -<p> -Languages: Spanish, English, Polish. -</p> -<p> -Centrologic is also available in Poland at phone number +48-609-56-53-41, -the price is 200-750 zlotys (this price is only available -in Poland). -For more information: -<a href="http://www.centrologic.pl">http://www.centrologic.pl</a> -</p> - diff --git a/greek/consultants/certcore.wml b/greek/consultants/certcore.wml deleted file mode 100644 index b55dcd1416b..00000000000 --- a/greek/consultants/certcore.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="CertCore" -#use wml::debian::translation-check translation="4e970d2fe87ee7b2ebee0e4473dc2b4a2f060994" maintainer="galaxico" - -<p> -We have an excellent track record as SysAdmin -services providers for customers in North America and Western Europe with -the most diverse needs. Managing IT security and IT infrastructure issues -of any complexity is one of our core competencies. -</p> diff --git a/greek/consultants/cesarsilva.wml b/greek/consultants/cesarsilva.wml deleted file mode 100644 index 3a052b717a4..00000000000 --- a/greek/consultants/cesarsilva.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="César Silva" -#use wml::debian::translation-check translation="8925980cd1fb629041fa7c3b0db8f946319139da" maintainer="galaxico" - -<p> -I provide consulting services for thin client -and network booted Debian systems, Debian-installer customizations, and -general Debian packaging work, with a focus on changes that can be merged -back into Debian for long-term sustainability. -</p> diff --git a/greek/consultants/cialdella.wml b/greek/consultants/cialdella.wml deleted file mode 100644 index cefe1096008..00000000000 --- a/greek/consultants/cialdella.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="Daniel Cialdella" -#use wml::debian::translation-check translation="14577b53b22e1b7f79a6fc59e89a53cc8f4a03aa" maintainer="galaxico" - -<ul> - <li>Complete Profile on - <a href="http://es.linkedin.com/in/dcialdella">http://es.linkedin.com/in/dcialdella</a></li> - <li>Experience on RDBMS, O.System, Teaching courses related to - LPIC, MySQL and Apache.</li> - <li>3 Years as DBA maintaining +400 Linux Servers.</li> -</ul>
\ No newline at end of file diff --git a/greek/consultants/cloud_bt.wml b/greek/consultants/cloud_bt.wml deleted file mode 100644 index d8a37afc7a7..00000000000 --- a/greek/consultants/cloud_bt.wml +++ /dev/null @@ -1,13 +0,0 @@ -#use wml::debian::consultant name="Cloud BT IT Support & IT Services" -#use wml::debian::translation-check translation="7da6c199929e7e586c8f87b8db8ab2bff0cb81ad" maintainer="galaxico" - -<p> -Cloud BT is a Sydney-based IT consulting firm with a diverse range of -expertise across many different environments and types of hardware. -Our core goal is to ensure the highest reliability for all systems -under our management, and to ensure that any projects we undertake are -conducted with the utmost of professionalism. Our central CBD location -means we are well-positioned to respond rapidly to clients who -require an onsite presence. -</p> - diff --git a/greek/consultants/coherent_light.wml b/greek/consultants/coherent_light.wml deleted file mode 100644 index 77fee79769e..00000000000 --- a/greek/consultants/coherent_light.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Coherent Light" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Specialist in web hosting, mail management and internet networking. -</p> diff --git a/greek/consultants/collabora.wml b/greek/consultants/collabora.wml deleted file mode 100644 index 2f87e7a2777..00000000000 --- a/greek/consultants/collabora.wml +++ /dev/null @@ -1,16 +0,0 @@ -#use wml::debian::consultant name="Collabora" -#use wml::debian::translation-check translation="9085a10db41388ef0539c960529b592903ee5d83" maintainer="galaxico" - -<p> -We also have an office in Canada: -</p> - <ul> - <li>Collabora (Canada)</li> - <li>440 rue Sainte-Hélène, Suite 200, Montréal, Québec, H2Y 2K7, Canada</li> - <li>Phone: +1 514 667 2499</li> - <li>Fax: +1 514 667 2499</li> - <li>Email: contact@collabora.com</li> - <li><url http://www.collabora.com/></li> - <li>Please contact for rates.</li> - </ul> - diff --git a/greek/consultants/compton_networks.wml b/greek/consultants/compton_networks.wml deleted file mode 100644 index f972e7e6284..00000000000 --- a/greek/consultants/compton_networks.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Compton Networks Organization" -#use wml::debian::translation-check translation="05ca90a106a3adb29bd7dce434098c26bcb74b05" maintainer="galaxico" - -<p> -Specializing in the needs of small businesses and home users. -Please see our website. -</p> diff --git a/greek/consultants/computer_problem.wml b/greek/consultants/computer_problem.wml deleted file mode 100644 index 585f495aeeb..00000000000 --- a/greek/consultants/computer_problem.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Computer Problem" -#use wml::debian::translation-check translation="ab44d17d91bb4d671fe7be6e9d0233d23af8abee" maintainer="galaxico" - -<p> -We do alot of work with Asterisks, Samba, Apache, FTP, Email, -Dedicated servers. We do Data recovery on desktop/server and even -offer system sales. -</p> diff --git a/greek/consultants/comware.wml b/greek/consultants/comware.wml deleted file mode 100644 index d860abc5f75..00000000000 --- a/greek/consultants/comware.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Comware International, Inc." -#use wml::debian::translation-check translation="9b8e07f9969a817da582687022adf550b9e90f9e" maintainer="galaxico" - -<p> -We also build <q>turn-key</q> servers (preloaded with the system, -configured, and documented). -</p> diff --git a/greek/consultants/con_z.wml b/greek/consultants/con_z.wml deleted file mode 100644 index 5b6ea5aa2db..00000000000 --- a/greek/consultants/con_z.wml +++ /dev/null @@ -1,14 +0,0 @@ -#use wml::debian::consultant name="Cyber IT Solutions Pty Ltd" -#use wml::debian::translation-check translation="869ced7b2e1d6175e7247c1a834e07191b6eb3d4" maintainer="galaxico" - -<p> -We are Australia's leading Linux and Free/Open Source solutions company, -in operation since 1991. -</p> - -<p> -Our team is available to help build, configure and maintain your IT -platforms and networks. We provide pro-active, on-site and remote -systems management, system administration and tuning, and support most -variants of Linux. -</p> diff --git a/greek/consultants/craftypenguins.wml b/greek/consultants/craftypenguins.wml deleted file mode 100644 index e1d78d87fc7..00000000000 --- a/greek/consultants/craftypenguins.wml +++ /dev/null @@ -1,12 +0,0 @@ -#use wml::debian::consultant name="Crafty Penguins, division of Kerkhoff Technologies Inc" -#use wml::debian::translation-check translation="7e86de5c5d6e6c34b67add82bc9bfc2dc78dcf09" maintainer="galaxico" - -<p> -We are full service IT consulting company providing Linux and Windows server -administration, network engineer, software development, VoIP PBX consulting, -hosting, and many other technical services. Mention that you found us through -Debian.org and we will donate back to the Debian Project. -</p><p> -We are located in Canada, and also service clients in the United States, -Australia, New Zealand, and the Netherlands. -</p>
\ No newline at end of file diff --git a/greek/consultants/credativ.wml b/greek/consultants/credativ.wml deleted file mode 100644 index 24bb3f9f3fa..00000000000 --- a/greek/consultants/credativ.wml +++ /dev/null @@ -1,25 +0,0 @@ -#use wml::debian::consultant name="credativ Group" -# Information updated by "Carsten Meskes" <carsten.meskes@credativ.com>, 21.12.2017 -#use wml::debian::translation-check translation="2942bacea03c9d0444f34633676b905c05e97664" maintainer="galaxico" - -<p> -credativ is an independent consulting and services company and since 1999 -been offering comprehensive services and technical support for the -implementation and operation of open source software in business -applications. Our Open Source Support Center is always available, 365 days a -year, around the clock. With our large team of open source specialists we -are one of the leading independent corporations for open source support; -many of our engineers are Debian developers and actively involved in -contributing to free software projects across the world. We have experience -in both, large scale projects as well as niche implementations. -</p> -<p> -We support all major projects and Linux distributions and offer a full range of -services including consultancy, operations takeover, qualified training and -personalized support. -</p> -<p> -For more information regarding our services and local subsidiaries in the US, Germany, -the Netherlands and India please visit <a href="https://www.credativ.com/"> -http://www.credativ.com</a>. -</p> diff --git a/greek/consultants/cubit.wml b/greek/consultants/cubit.wml deleted file mode 100644 index 6f73d152b31..00000000000 --- a/greek/consultants/cubit.wml +++ /dev/null @@ -1,14 +0,0 @@ -#use wml::debian::consultant name="CUBiT IT Solutions GmbH" -#use wml::debian::translation-check translation="1df31810be0396d287e92222bfd13f8f025b862f" maintainer="galaxico" - -<p> -CUBiT is focussed on: -</p> -<ul> - <li>High Availability Linux</li> - <li>Linux Monitoring and Management</li> - <li>Embedded Debian</li> - <li>Storage Attachment (Debian with SAN!, EMC, IBM, HP, NetApp)</li> - <li>NFS (and NetworkAppliance Systems)</li> - <li>Perl</li> -</ul> diff --git a/greek/consultants/cybertec.wml b/greek/consultants/cybertec.wml deleted file mode 100644 index 2f2e782752c..00000000000 --- a/greek/consultants/cybertec.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Cybertec Schönig & Schönig GmbH" -#use wml::debian::translation-check translation="aaf38fe6b628af51cfae312e79552cda3c86e4ff" maintainer="galaxico" - -<p> -Cybertec Schönig & Schönig GmbH is an IT-company with more than 10 years -of experience in the field of Open Source and offers comprehensive services -for PostgreSQL as well as for Linux. We are providing professional support -for PostgreSQL on / and Debian systems worldwide. -</p> diff --git a/greek/consultants/dan_ouellet.wml b/greek/consultants/dan_ouellet.wml deleted file mode 100644 index a6df1fd0d5a..00000000000 --- a/greek/consultants/dan_ouellet.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Dan Ouellet" -#use wml::debian::translation-check translation="eeb0364a9dea6b8e795816970be481cb1489c0e8" maintainer="galaxico" - -<p> -OCI specializes in infrastructure planning, layout, specification, and implementation, migration and contract administration, all at competitive rates. We support most Windows Operating Systems and Microsoft Application Platform Products as well as most UNIX, and Linux systems, including Debian, Ubuntu, Fedora, Red Hat, Mandriva, OpenBSD, NetBSD, FreeBSD, and many more. -</p> diff --git a/greek/consultants/defreitas.wml b/greek/consultants/defreitas.wml deleted file mode 100644 index 232ff7c1e0f..00000000000 --- a/greek/consultants/defreitas.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Greg DeFreitas" -#use wml::debian::translation-check translation="4f15ad77c29466aa0ca57089fb025215cb0ddc3e" maintainer="galaxico" - -<p> -Linux(0.99pl?) and Internet since 1992. -Will gladly donate a prearranged percentage of any fee to Debian. -Will gladly travel abroad if necessary (and expensed). -</p> diff --git a/greek/consultants/disch.wml b/greek/consultants/disch.wml deleted file mode 100644 index c6c84f4a0c8..00000000000 --- a/greek/consultants/disch.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Disch Services GmbH" -#use wml::debian::translation-check translation="5863803328c74dc80d4e6c07ecb2f6b7786ed43d" maintainer="galaxico" - -<p> -Linux experience since 1998. Support of Debian for our -customers since 2004. Competent knowledge in modification of Apache -HTTP Server modules and in qmail adoptions (IPv6, SSL, DKIM). -</p> diff --git a/greek/consultants/dompieri.wml b/greek/consultants/dompieri.wml deleted file mode 100644 index 5d5266967ef..00000000000 --- a/greek/consultants/dompieri.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Dompieri Tecnologia" -#use wml::debian::translation-check translation="aba9753ee5faf1d3d2a01e0a67b799bd0c289823" maintainer="galaxico" - -<p> -Dompieri Tecnologia is a State São Paulo and -Sergipe based information technology consultancy. -</p> diff --git a/greek/consultants/dotline_infotech.wml b/greek/consultants/dotline_infotech.wml deleted file mode 100644 index b5d0f03eb11..00000000000 --- a/greek/consultants/dotline_infotech.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Dotline Infotech Pty Ltd" -#use wml::debian::translation-check translation="0dd648e60719c42bce4ba77e06c2226bb8505565" maintainer="galaxico" - -<p> -Dotline Infotech is based in heart of Sydney CBD, providing IT Support and -Linux Support to various client Australia wide. We have dedicated Linux -team, which can help you with all support requirement or project of any -level. -</p> diff --git a/greek/consultants/emergya.wml b/greek/consultants/emergya.wml deleted file mode 100644 index 0e43766a4bf..00000000000 --- a/greek/consultants/emergya.wml +++ /dev/null @@ -1,19 +0,0 @@ -#use wml::debian::consultant name="Emergya" -#use wml::debian::translation-check translation="3fb699b4d8a234193849f04235af48b4521acfe3" maintainer="galaxico" - -<p> -We have been specialized in giving solutions out-of-the-box based -on Debian GNU/Linux. We have developed various distributions based on -Debian. Another goals of the company is the migration, services and -system integration. -</p> -<p> -We also have an office in Chile: -</p> -<ul> -<li>Name: Rafael Martín de Agar</li> -<li>Address: Antonio Varas, 175, Oficina 1208, Providencia, Santiago de Chile, Chile.</li> -<li>Phone: +56-2-4273900</li> -<li>E-Mail: debian@emergya.com</li> -<li>URL: <a href="http://www.emergya.com">http://www.emergya.com</a></li> -</ul> diff --git a/greek/consultants/ender_informatics.wml b/greek/consultants/ender_informatics.wml deleted file mode 100644 index 160b0ceaad0..00000000000 --- a/greek/consultants/ender_informatics.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="ender informatics gmbh" -#use wml::debian::translation-check translation="c17152092613e6eaf86c3a40f7e6ed5745fc860f" maintainer="galaxico" - -<p> -More than 17 years of experience in IT support, IT security, complex -networks, network monitoring, centralized -virus and spam filters. -</p> diff --git a/greek/consultants/enterux.wml b/greek/consultants/enterux.wml deleted file mode 100644 index 9f9cd58d2b6..00000000000 --- a/greek/consultants/enterux.wml +++ /dev/null @@ -1,94 +0,0 @@ -#use wml::debian::consultant name="Enterux Solutions" -#use wml::debian::translation-check translation="7101d0f39e02ee8088d173d7a10841df64c645ae" maintainer="galaxico" - -<p> -We can offer a full range of services listed on our website a few which I can -write here, -</p> - -<ul> -<li> -<a href="https://www.enterux.com/en/services/application-services/">\ -Applications Services</a> -</li> - -<li> -<a href="https://www.enterux.com/en/services/product-engineering-services/">\ -Product Engineering Services</a> -</li> - -<li> -<a href="https://www.enterux.com/en/services/web-services/">Web Services</a> -</li> - -<li> -<a href="https://www.enterux.com/en/services/infrastructure-services/">\ -Infrastructure Services</a> -</li> - -<li> -<a href="https://www.enterux.com/services/technology-consulting/">\ -Technology Consulting</a> -</li> -</ul> - -<p> -And the solutions which we can provide are: -</p> - -<ul> -<li> -<a href="https://www.enterux.com/en/solutions/enterprise-email-solutions/">\ -Enterprise Email Solutions</a> -</li> - -<li> -<a href="https://www.enterux.com/en/solutions/enterprise-instant-messaging-solutions/">\ -Enterprise Instant Messaging Solutions</a> -</li> - -<li> -<a href="https://www.enterux.com/en/solutions/enterprise-security-firewall-solutions/">\ -Enterprise Security / Firewall Solutions</a> -</li> - -<li> -<a href="https://www.enterux.com/en/solutions/network-optimization-solutions/">\ -Network Optimization Solutions</a> -</li> - -<li> -<a href="https://www.enterux.com/en/solutions/load-balancing-high-volume-solutions/">\ -Load Balancing / High Volume Solutions</a> -</li> - -<li> -<a href="https://www.enterux.com/en/solutions/high-availability-solutions/">\ -High Availability Solutions</a> -</li> - -<li> -<a href="https://www.enterux.com/en/solutions/embedded-gnu-linux-solutions/">\ -Embedded GNU/Linux Solutions</a> -</li> - -<li> -<a href="https://www.enterux.com/en/solutions/server-migration-solutions/">\ -Server Migration Solutions</a> -</li> - -<li> -<a href="https://www.enterux.com/en/solutions/thin-client-solutions/">\ -Thin Client Solutions</a> -</li> -</ul> - -<p> -We are also have this product named Resty: -What is Resty? -Resty is a Web Application Framework distributed under the terms of the GNU -General Public License by Enterux. Please check out the documentation to find -out more about Resty. -More relative information available from: -<a href="http://www.resty.org/">Resty Homepage</a> -</p> diff --git a/greek/consultants/f_mitha.wml b/greek/consultants/f_mitha.wml deleted file mode 100644 index 7d98b32889d..00000000000 --- a/greek/consultants/f_mitha.wml +++ /dev/null @@ -1,14 +0,0 @@ -#use wml::debian::consultant name="Faheem Mitha" -#use wml::debian::translation-check translation="42f408dca579e81a9022c8661d01bc0cfcfbf457" maintainer="galaxico" - -<p> -Long time Debian user (since 2001). PhD in Statistics from the -University of North Carolina. Extensive knowledge of Free and -Open Source Software, particularly scientific software. -Specialist in scientific computing. Good at troubleshooting. -</p><p> -See also my page on unix.stackexchange - -<url "http://unix.stackexchange.com/users/4671/faheem-mitha">. -</p><p> -You can also Google me. -</p> diff --git a/greek/consultants/fai-cluster.wml b/greek/consultants/fai-cluster.wml deleted file mode 100644 index c84ba3a1944..00000000000 --- a/greek/consultants/fai-cluster.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="fai-cluster.de" -#use wml::debian::translation-check translation="dd3d9ce420dc4e728d10b76c7a6ff715efa8a5e3" maintainer="galaxico" - -<p> -We only do support and service around FAI, the Fully -Automatic Installation (<a href="https://fai-project.org/">http://fai-project.org</a>). -</p> diff --git a/greek/consultants/falared.wml b/greek/consultants/falared.wml deleted file mode 100644 index e845312ebec..00000000000 --- a/greek/consultants/falared.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="FALARED" -#use wml::debian::translation-check translation="8ad522049fe011c0fd2d4c5edfa8bd91c4564131" maintainer="galaxico" - -<ul> -<li>IT consulting</li> -<li>15+ years of Debian experience</li> -<li>Multilingual (EN/FR/ES/PT/IT/DE)</li> -</ul> diff --git a/greek/consultants/fensterkitt.wml b/greek/consultants/fensterkitt.wml deleted file mode 100644 index f09230dca4d..00000000000 --- a/greek/consultants/fensterkitt.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Fensterkitt Computer Support" -#use wml::debian::translation-check translation="643c6f402f8d67364ceef5aad745b42f20e38ef8" maintainer="galaxico" - -<p> -Languages: German, French, English and a bit of Italian. -</p> diff --git a/greek/consultants/folinx.wml b/greek/consultants/folinx.wml deleted file mode 100644 index 0edb8f7fbc4..00000000000 --- a/greek/consultants/folinx.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="folinX EDV Service" -#use wml::debian::translation-check translation="5d3a461c058edb4c0b75684fcb2125e823128fc3" maintainer="galaxico" - -<p> -Migration, networks planning, facility organization, free software -in common use. -</p> diff --git a/greek/consultants/fortuitous.wml b/greek/consultants/fortuitous.wml deleted file mode 100644 index 548c25a0c8d..00000000000 --- a/greek/consultants/fortuitous.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Fortuitous Technologies" -#use wml::debian::translation-check translation="473d687521f9a2cfadc8522992e2dfc9399b56c2" maintainer="galaxico" - -<p> -Fortuitous provides expert design and support for Linux, Unix and FreeBSD. -We offer monitoring, maintenance and performance consulting -for Cloud, VPS, and networks. -</p> diff --git a/greek/consultants/gregory_duchatelet.wml b/greek/consultants/gregory_duchatelet.wml deleted file mode 100644 index 376cc1ed922..00000000000 --- a/greek/consultants/gregory_duchatelet.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Grégory Duchatelet" -#use wml::debian::translation-check translation="389433c9b4823ffc28eca06f0999baf094c34b52" maintainer="galaxico" - -<p> -Expert on high traffic and highly available web sites. -</p> diff --git a/greek/consultants/guhan_net.wml b/greek/consultants/guhan_net.wml deleted file mode 100644 index 08380273d7f..00000000000 --- a/greek/consultants/guhan_net.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Guhan.Net" -#use wml::debian::translation-check translation="a5810b3c39d2579433ff8b8cb31557827bbad674" maintainer="galaxico" - -<p> -Over 15 years experience with Linux, excellent communication, and -outstanding follow through. -</p> diff --git a/greek/consultants/gurunetwork.wml b/greek/consultants/gurunetwork.wml deleted file mode 100644 index 2a2c64bc6cf..00000000000 --- a/greek/consultants/gurunetwork.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="GuruNetwork di Massimo Martini" -#use wml::debian::translation-check translation="9332bacd1249f7f6177c9548f488135c984c5a9f" maintainer="galaxico" - -<p> -Enterprise Linux Systems, High-security Firewalls, Auditing, -Linux/*NIX consulting, IT project management. Sell/support Cisco product (Select Certified Partner), -WatchGuard (Certified System Professional) with network troubleshooting and planning Lan/Wan solutions. -</p> diff --git a/greek/consultants/h_loureiro.wml b/greek/consultants/h_loureiro.wml deleted file mode 100644 index 1f1812bbfda..00000000000 --- a/greek/consultants/h_loureiro.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Helio Loureiro" -#use wml::debian::translation-check translation="acc8ea1c79e79506a2be2c9f5cf245896d4a3dfd" maintainer="galaxico" - -<p> -Engineer with skills mostly on telecom area, including VoIP PBXs, -fault tolerant system and debian routers (quagga). -</p> diff --git a/greek/consultants/heureka.wml b/greek/consultants/heureka.wml deleted file mode 100644 index ad75e81a0c8..00000000000 --- a/greek/consultants/heureka.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Heureka GmbH" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -First contact free. -</p> diff --git a/greek/consultants/hypra.wml b/greek/consultants/hypra.wml deleted file mode 100644 index 05e2b776371..00000000000 --- a/greek/consultants/hypra.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="hypra" -#use wml::debian::translation-check translation="8ae9e5c6b6a241be161e3c7d6495818c9eeb8193" maintainer="galaxico" - -<p> -Help for Debian accessibility. -</p> diff --git a/greek/consultants/imagin.wml b/greek/consultants/imagin.wml deleted file mode 100644 index 6eca7e848d0..00000000000 --- a/greek/consultants/imagin.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="IMAGIN" -#use wml::debian::translation-check translation="8e2efdb07e30d5485f757f825aadb22193da831f" maintainer="galaxico" - -<p> -Projects outside Poland are accepted as well. -</p> diff --git a/greek/consultants/index.wml b/greek/consultants/index.wml deleted file mode 100644 index 5061cd9e2d8..00000000000 --- a/greek/consultants/index.wml +++ /dev/null @@ -1,50 +0,0 @@ -#use wml::debian::template title="Consultants" NOCOMMENTS="yes" GENTIME="yes" -#use wml::debian::translation-check translation="edbd4a65aeffde3b466134d488992d26b78b73eb" maintainer="galaxico" - -<p>Debian is free software and offers free help through -<a href="../MailingLists/">mailing lists</a>. Some people either don't -have the time or have specialized needs and are willing to hire someone to -either maintain or add additional functionality to their Debian system. The -following is a list of people who make at least part of their income from doing -<strong>paid</strong> support for Debian.</p> - -<p>Names are sorted by country, but within each country are simply listed in -the order received. If your country is not listed, please check any neighboring -countries, as some of the consultants will work internationally. Debian lists -the consultants simply as a courtesy to its users and does not endorse any of -the people or companies listed below. Please see the <a href="info">consultant -information page</a> for our policy of adding or updating a listing.</p> - -<p>Please note that some consultants donate a portion of their income (derived -from Debian) to supporting Debian. This is up to each consultant or company. -Of course, this is pointed out to you so that it will hopefully influence your -choice ...</p> - -<p><strong> -The list is provided as is, without any guarantee or endorsement by -the Debian Project. Entries are the sole responsibility of the corresponding -consultant. -</strong></p> - -<p>There are additional lists of consultants for specific uses of Debian:</p> -<ul> -<li><a href="https://wiki.debian.org/DebianEdu/Help/ProfessionalHelp">Debian Edu</a>: -for the use of Debian in schools, universities and other educational settings. -<li><a href="https://wiki.debian.org/LTS/Funding">Debian LTS</a>: -for long term security support of Debian. -</ul> - -<hrline> - -<h2>Countries in which there is a listed Debian consultant:</h2> - -#include "../../english/consultants/consultant.data" - -<hrline> - -# left for backwards compatibility - in case someone still links to #policy -# which is fairly unlikely, but hey -<h2><a name="policy"></a>Policy for Debian's consultants page</h2> -<p>Please see the <a href="info">page with information for consultants</a> -for our policy of adding or updating a listing. -</p> diff --git a/greek/consultants/indigo_solutions.wml b/greek/consultants/indigo_solutions.wml deleted file mode 100644 index f5a59465cb0..00000000000 --- a/greek/consultants/indigo_solutions.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="Indigo Solutions Europe Ltd." -#use wml::debian::translation-check translation="499ddd7cad22df735baa1a6f912f2b03d270e2ba" maintainer="galaxico" - -<p> -We are a systems integrator, providing both consultancy and engineering -specialising in core network services including DNS, DHCP, RADIUS, LDAP -and systems monitoring/reporting. We can provide both on and off site -support and training and SLA backed contracts for server -monitoring/management/maintenance are available. -</p> diff --git a/greek/consultants/info.wml b/greek/consultants/info.wml deleted file mode 100644 index f3db9702c3f..00000000000 --- a/greek/consultants/info.wml +++ /dev/null @@ -1,130 +0,0 @@ -#use wml::debian::template title="Information for Debian consultants" -#use wml::debian::translation-check translation="b27d50a764c00727d11d19b785f566eff3b2fa87" maintainer="galaxico" - -<h2>Policy for Debian's consultants page</h2> - -<p>If you want to be listed as a consultant at the Debian web site, -then please note the following rules:</p> - -<ul> - <li>Mandatory contact information<br /> - You must provide a working e-mail address and answer e-mails sent to you - within four weeks at most. In order to prevent abuse any requests (additions, - removals or changes) have to be sent from that same address. To avoid spam, - you can request to have your mail address scrambled (e.g. - <q>debian -dot- consulting -at- example -dot- com</q>). If you prefer - this, please note it explicitly in your submission. Alternatively you can - also request that your e-mail address should not be visible at all on the - web page (although we need a working e-mail address for list maintenance). - If you want your address to be hidden on the list, you can instead provide - the URL of a contact form on your web site for us to link to. - <q>Contact</q> is meant to be used for this. - </li> - <li>If you provide a link to a website, that website must have a - mention of your Debian consulting services. Providing the direct link - instead of just the homepage is not mandatory if the information is - reasonably accessible, but much appreciated. - </li> - <li>Multiple cities/regions/countries<br /> - You have to choose the country (only one) that you want to be - listed under. Additional cities, regions or countries should be - listed either as part of the additional info, or at your own website. - </li> - <li>Rules for Debian developers<br /> - You are not allowed to use your official @debian.org address - for the consultant listing.<br /> - If you'd like to provide a URL, you cannot use an official - *.debian.org domain.<br /> - This is required by the <a href="$(HOME)/devel/dmup">DMUP</a>. - </li> -</ul> - -<p>If the above criteria are no longer met at some future point, the -consultant should receive a warning message that they are about to be -removed from the list, unless they fulfill all criteria again. -There should be a grace period of four weeks.</p> - -<p>Some parts (or all) of the consultant's information can be removed -if they don't comply with this policy anymore, or at the discretion of -the list maintainers.</p> - -<h2>Additions, modifications, and removals of entries</h2> - -<p>If you wish to be added to the list of consultants, please - mail <a href="mailto:consultants@debian.org">consultants@debian.org</a>, - in English, providing any of the following pieces of information that you - would like to be listed (e-mail address is mandatory, everything else is - optional at your discretion):</p> - -<ul> - <li>Country for which you want to be listed</li> - <li>Name</li> - <li>Company</li> - <li>Address</li> - <li>Phone</li> - <li>Fax</li> - <li>Contact</li> - <li>E-mail</li> - <li>URL</li> - <li>Rates</li> - <li>Additional information, if any</li> -</ul> - -<p>A request for an update of the consultant's information should be sent -to <a href="mailto:consultants@debian.org">consultants@debian.org</a>. -Send e-mail preferably from the e-mail address mentioned on the -consultants page -(<a href="https://www.debian.org/consultants/">https://www.debian.org/consultants/</a>).</p> - -<p>Consultants can communicate with other Debian consultants via the -<a href="https://lists.debian.org/debian-consultants/">debian-consultants mailing list</a>.</p> - -# translators can, but don't have to, translate the rest - yet -# BEGIN future version -# fill out the following submission form:</p> -# -# <form method=post action="https://cgi.debian.org/cgi-bin/submit_consultant.pl"> -# -# <p> -# <input type="radio" name="submissiontype" value="new" checked> -# New consultant listing submission -# <br /> -# <input type="radio" name="submissiontype" value="update"> -# Update of an existing consultant listing -# <br /> -# <input type="radio" name="submissiontype" value="remove"> -# Removal of an existing consultant listing -# </p> -# -# <p>Name:<br /> -# <input type="text" name="name" size="50"></p> -# -# <p>Company:<br /> -# <input type="text" name="company" size="50"></p> -# -# <p>Address:<br /> -# <textarea name="comment" cols=35 rows=4></textarea></p> -# -# <p>Phone:<br /> -# <input type="text" name="phone" size="50"></p> -# -# <p>Fax:<br /> -# <input type="text" name="fax" size="50"></p> -# -# <p>E-mail:<br /> -# <input type="text" name="email" size="50"></p> -# -# <p>URL:<br /> -# <input type="text" name="url" size="50"></p> -# -# <p>Rates:<br /> -# <textarea name="comment" cols=35 rows=4></textarea></p> -# -# <p>Additional information, if any (<em>in English</em>):<br /> -# <textarea name="comment" cols=40 rows=7></textarea></p> -# -# </form> -# -# <p>If you are unable to submit the above for any reason whatsoever, -# please send it via e-mail <em>in English</em> to -# END future version diff --git a/greek/consultants/infranet.wml b/greek/consultants/infranet.wml deleted file mode 100644 index 228c9a39224..00000000000 --- a/greek/consultants/infranet.wml +++ /dev/null @@ -1,21 +0,0 @@ -#use wml::debian::consultant name="InfraNet AG" -#use wml::debian::translation-check translation="875bbf3198a11101dafc03445711fa7b288cac47" original="german" -#use wml::debian::translation-check translation="d8d7825eda328af69583367c1c7e4a2c4c28219c" maintainer="galaxico" - -<p> -For InfraNet AG security, flexibility and stability is in focus. That's why we -are convinced of Linux. You can rely on our Linux competence. You benefit -from individual solutions, maintain independence from certain manufacturers and -avoid licence costs. -</p> - -<p> -InfraNet relies primarily on Debian but also works with other distributions. If -you are looking for a competent contact person for all questions concerning -Linux, then you are right with us. -</p> - -<p> -Take advantage of our experience in the areas of Linux consulting, Linux -service and Linux administration. We look forward to a non-binding consultation. -</p> diff --git a/greek/consultants/inittab.wml b/greek/consultants/inittab.wml deleted file mode 100644 index 99bee779c66..00000000000 --- a/greek/consultants/inittab.wml +++ /dev/null @@ -1,14 +0,0 @@ -#use wml::debian::consultant name="Alberto Gonzalez Iniesta" -#use wml::debian::translation-check translation="46e4f0a2e629138908db7277aa7ee74ecf012c2e" maintainer="galaxico" - -<p> -Debian Developer offering Free Software training (GNU/Linux, -Apache, Mysql, Samba, security) and consulting. GNU/Linux -administration, web/mail/file & printing/firewall/HA servers -installation and maintenance. -<br /> -Web application development in LAMP environments. -</p> -<p> -Will travel through Spain and EU. -</p> diff --git a/greek/consultants/innova_computing.wml b/greek/consultants/innova_computing.wml deleted file mode 100644 index 2091743fd4f..00000000000 --- a/greek/consultants/innova_computing.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Innova Computing, L.L.C." -#use wml::debian::translation-check translation="24e0b269cf4ebf108d221dc90946253134c8838b" maintainer="galaxico" - -<p> -Innova Computing provides application -development, system administration, database administration, and web design services. -</p> diff --git a/greek/consultants/io_digital.wml b/greek/consultants/io_digital.wml deleted file mode 100644 index 312ce6d42d7..00000000000 --- a/greek/consultants/io_digital.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="IO Digital Sec" -#use wml::debian::translation-check translation="bcadbc7175e98ae1f947ff94090e20b52a9624b3" maintainer="galaxico" - -<p> -Available for one off projects, including programming and scripting. -Ongoing maintenance available. Emergency support available -including disaster recovery and breach remediation. -</p> diff --git a/greek/consultants/ipodion.wml b/greek/consultants/ipodion.wml deleted file mode 100644 index 94c18322a55..00000000000 --- a/greek/consultants/ipodion.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="iPodion GmbH" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -General Debian/Linux support, preconfigured server and workstation computers, -development of customized distributions for server and workstation use. -</p> diff --git a/greek/consultants/isvtec.wml b/greek/consultants/isvtec.wml deleted file mode 100644 index 4e77dac2b9f..00000000000 --- a/greek/consultants/isvtec.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="ISVTEC" -#use wml::debian::translation-check translation="7101d0f39e02ee8088d173d7a10841df64c645ae" maintainer="galaxico" - -<p> -ISVTEC is a managed services company, specializing in management of -large scale web and mail infrastructure using Debian as a platform. -Along our managed services offer, we are providing Debian related -services such as professional support, packaging and architecture. -</p><p> -More information at <a href="https://www.isvtec.com/">https://www.isvtec.com/</a>.</p> diff --git a/greek/consultants/it_service_drillich.wml b/greek/consultants/it_service_drillich.wml deleted file mode 100644 index 5270139c11a..00000000000 --- a/greek/consultants/it_service_drillich.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="IT-Service Drillich" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Configuration and administration of unix-systems, indiviual software, -it-consulting -</p> diff --git a/greek/consultants/janprunk.wml b/greek/consultants/janprunk.wml deleted file mode 100644 index 99534fdc466..00000000000 --- a/greek/consultants/janprunk.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Jan Prunk" -#use wml::debian::translation-check translation="3ee112f876966678ae6a220044d3587a14ed23af" maintainer="galaxico" - -<p> -I am available to telecommute for work. -</p> diff --git a/greek/consultants/jaume_t.wml b/greek/consultants/jaume_t.wml deleted file mode 100644 index d16b44c6771..00000000000 --- a/greek/consultants/jaume_t.wml +++ /dev/null @@ -1,11 +0,0 @@ -#use wml::debian::consultant name="Jaume Teixi" -#use wml::debian::translation-check translation="d7fc38d068090c888e5dc76f30ca6d75165b2fbf" maintainer="galaxico" - -<p> -Custom Amazon, Rackspace, Cloud Debian Servers. -High availability, HAProxy, Nginx, Apache, Lighttpd, Postfix, PostgreSQL, -Mysql, MariaDB. Galera Cluster. -More than 10 years of Debian Linux demonstrable -experience. -A portion of the profits will be donated to the Debian developers community. -</p> diff --git a/greek/consultants/jean_p.wml b/greek/consultants/jean_p.wml deleted file mode 100644 index 2948d3acbca..00000000000 --- a/greek/consultants/jean_p.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Linuz.it" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Enterprise Linux Systems, High-security Firewalls, Linux-based Antivirus -Systems, High-availability/reliability Linux Servers, Specialised -Linux/*BSD/Sun*/*NIX Consulting. -</p> - diff --git a/greek/consultants/jeremy_r.wml b/greek/consultants/jeremy_r.wml deleted file mode 100644 index 1a341aaca0b..00000000000 --- a/greek/consultants/jeremy_r.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Puget Sound Technology" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p>BSD <-> Linux migrations; on-site, customized training. -We do Apache, Postfix, Linux security, Unix shell essentials training for -example.</p> diff --git a/greek/consultants/jfranken.wml b/greek/consultants/jfranken.wml deleted file mode 100644 index 4f58a814642..00000000000 --- a/greek/consultants/jfranken.wml +++ /dev/null @@ -1,22 +0,0 @@ -#use wml::debian::consultant name="FRANKEN IT-CONCEPTS" -#use wml::debian::translation-check translation="7101d0f39e02ee8088d173d7a10841df64c645ae" maintainer="galaxico" - -<p> -Since 1992 we have been known for the realization of complex IT projects. -</p> -<p> -Our focus areas are: -</p> -<ul> -<li>IT-architecture and indivudual solution concepts for your IT -reqirements</li> -<li>Systems development in practically all languages and technologies -known today, for all environments and operating systems.</li> -<li>IT-seminars for system-administrators</li> -<li>Technical IT project management</li> -</ul> -<p> -For details, see -<a href="http://www.jfranken.de/en/">\ -http://www.jfranken.de/en/</a> -</p> diff --git a/greek/consultants/jh_networks.wml b/greek/consultants/jh_networks.wml deleted file mode 100644 index 9d57b0050d6..00000000000 --- a/greek/consultants/jh_networks.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="JH-Network Solutions" -#use wml::debian::translation-check translation="ae6ce9ea6a2185685bf55193b083486c882e4c1d" maintainer="galaxico" - -<p> -Privat customers, internet-cafes, firewalls, protection of minors, all -GNU/LINUX systems -</p> diff --git a/greek/consultants/jordan.wml b/greek/consultants/jordan.wml deleted file mode 100644 index 73e20f91d9f..00000000000 --- a/greek/consultants/jordan.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="JordanTeam Learning LLC" -#use wml::debian::translation-check translation="3804cc8dbffc45fa787aa58ba464af6ba98ace23" maintainer="galaxico" - -<p> -Linux Professional Institute, and Linux+ Certification Trainers. -</p> diff --git a/greek/consultants/juanmitaboada.wml b/greek/consultants/juanmitaboada.wml deleted file mode 100644 index 3f6b17634ea..00000000000 --- a/greek/consultants/juanmitaboada.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="Juanmi Taboada" -#use wml::debian::translation-check translation="0f6e52e972ea59613cb5e7d76d2af2a54ba82272" maintainer="galaxico" - -<p> -Linux Specialist, high availability servers, clusters, network, -long range wireless networks, industrial programming and acquisition, -remote server management, hosting, web design, erp/crm programming and -design, software analist, server install, backup and redundancy -systems. Languages: spanish-english. -</p> diff --git a/greek/consultants/keith_h.wml b/greek/consultants/keith_h.wml deleted file mode 100644 index 28d8e60a885..00000000000 --- a/greek/consultants/keith_h.wml +++ /dev/null @@ -1,46 +0,0 @@ -#use wml::debian::consultant name="Keith Herron" -#use wml::debian::translation-check translation="7101d0f39e02ee8088d173d7a10841df64c645ae" maintainer="galaxico" - -<p> -<a href="https://backdrift.org/aboutme">Keith Herron</a> is a Linux -consultant and open source systems engineer of over 10 years from the -greater Boston area. Available for work nationwide, his focal points -are Linux systems administration, Xen virtualization, Puppet configuration -management, automation, and cloud provisioning and management. -Keith builds and supports robust, affordable and scalable solutions using -open source software and cloud technologies. -</p><p> -Keith has extensive experience in the design, implementation and support -of many different aspects of IT systems infrastructure including... -</p> - -<ul> -<li>GNU/Linux Systems, Specifically Debian, Red Hat, CentOS and Ubuntu</li> -<li>Puppet Configuration Management</li> -<li>Xen Virtualization</li> -<li>Amazon EC2 and S3</li> -<li>Automated Provisioning</li> -<li>Monitoring and Log Analysis</li> -<li>Storage including RAID, DAS, SAN, NAS and Cloud Object Storage</li> -<li>Performance Optimization</li> -<li>Backup & Disaster Recovery</li> -<li>Apache, MySQL, PHP</li> -<li>Scalability</li> -<li>Subversion</li> -<li>Core Internet Protocols: IP, TCP, UDP, DNS, DHCP</li> -<li>and much more.</li> -</ul> - -<p>If you need a...</p> - -<ul> -<li>Xen Consultant</li> -<li>Linux Consultant</li> -<li>Puppet Consultant</li> -<li>Backup Consultant</li> -<li>LAMP Consultant</li> -<li>Cloud Consultant</li> -</ul> - -<p>...let's talk about how I can help you.</p> - diff --git a/greek/consultants/kiran_babu.wml b/greek/consultants/kiran_babu.wml deleted file mode 100644 index 847212b2f87..00000000000 --- a/greek/consultants/kiran_babu.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="V.Kiran Babu" -#use wml::debian::translation-check translation="4c64fffb96505613c92d32778873c2bb0d9c8f83" maintainer="galaxico" - -<p> -I am a post graduate in Electrical Power Engineering with 2 years -of Software experience in an MNC. I am training students in FOSS -and implementing in organizations since 2012. -</p> diff --git a/greek/consultants/kotarba.wml b/greek/consultants/kotarba.wml deleted file mode 100644 index 2276de20625..00000000000 --- a/greek/consultants/kotarba.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="SYSTEM7, University of Cambridge" -#use wml::debian::translation-check translation="8d2cbe90190b2038d14ea4f26e2ab4b92951e7e9" maintainer="galaxico" - -<p> -Also: London/UK. -</p> diff --git a/greek/consultants/legoutdulibre.wml b/greek/consultants/legoutdulibre.wml deleted file mode 100644 index cd118683af1..00000000000 --- a/greek/consultants/legoutdulibre.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Le Goût du Libre" -#use wml::debian::translation-check translation="7f097ae5ba22a7ebf5375ebfb69c1df4e1424fd0" maintainer="galaxico" - -<p> -Will travel to your location, services available in English, French -and Spanish. -</p> diff --git a/greek/consultants/liberobit.wml b/greek/consultants/liberobit.wml deleted file mode 100644 index a3495feb8de..00000000000 --- a/greek/consultants/liberobit.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Liberobit.net Srl" -#use wml::debian::translation-check translation="ce6254bc5f208bacd52551decef4341efabed5ce" maintainer="galaxico" - -<p> -We made and support only Debian servers, workstation -and lan managed by Debian box -</p> - diff --git a/greek/consultants/linux_ag.wml b/greek/consultants/linux_ag.wml deleted file mode 100644 index e54d29adb2f..00000000000 --- a/greek/consultants/linux_ag.wml +++ /dev/null @@ -1,42 +0,0 @@ -#use wml::debian::consultant name="Linux Information Systems AG" -#use wml::debian::translation-check translation="31222484a77c08496b404d86d418bc66a9c048ae" maintainer="galaxico" - -<p>The Linux Information Systems AG is specialized in working with -small and medium-sized businesses as well as authorities. Its focus -is the organization of IT for office and backoffice.</p> - -<p>After a previous consulting stage, we mainly help our customers -with the partial or full migration of their IT to Linux and Open Source. -Our aim is to integrate the different worlds of heterogeneous environments, -both technically and related to business.</p> - -<p>Below are some typical topics for which we have gathered -superiour competence:</p> - -<ul> - <li>Possibility and costs of migrations</li> - <li>Strategies for migration and implementation of projects</li> - <li>Fileserver for heterogeneous environments (Windows, Linux/Unix, Mac)</li> - <li>Groupware with multiple user interfaces (Web, Outlook, Linux, - Mac)</li> - <li>Individual and standardized solutions for mailservers replacing - Exchange</li> - <li>Integrated fax and SMS server</li> - <li>Solutions for the apache webserver</li> - <li>Office applications replacing Microsoft Office</li> - <li>Security (firewalls, virusscanner, VPNs)</li> - <li>Exchange and synchronization of data from company subsidiaries</li> - <li>Databases (commercial/Open Source)</li> - <li>Automatic distribution and installation of software in companies</li> - <li>Integration of Linux and Windows applications for mixed - mode</li> - <li>Migrations of Novell, Windows, and Unix servers to Linux</li> - <li>Migrations of Windows workstations to Linux with applications - running under Windows and Linux</li> - <li>Directory services with LDAP as an alternative to Microsoft Active - Directory Services</li> - <li>Backup solutions</li> - <li>Failover clusters (pacemaker, DRBD)</li> - <li>Integration of Zarafa groupware server</li> - <li>Virtualization (KVM)</li> -</ul> diff --git a/greek/consultants/linux_certified.wml b/greek/consultants/linux_certified.wml deleted file mode 100644 index 9c197c177c4..00000000000 --- a/greek/consultants/linux_certified.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="LinuxCertified, Inc." -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Debian consultants in various geographies. -</p> diff --git a/greek/consultants/linuxbox.wml b/greek/consultants/linuxbox.wml deleted file mode 100644 index d62dd404593..00000000000 --- a/greek/consultants/linuxbox.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Linuxbox" -#use wml::debian::translation-check translation="b418a58050acfa0c24a2d2f57fadd65ab35bbfa3" maintainer="galaxico" - -<p> -Available for one-off projects and regular work. Emergency support available. -</p> diff --git a/greek/consultants/linuxlabs.wml b/greek/consultants/linuxlabs.wml deleted file mode 100644 index e4f0d305e2a..00000000000 --- a/greek/consultants/linuxlabs.wml +++ /dev/null @@ -1,14 +0,0 @@ -#use wml::debian::consultant name="Linuxlabs" -#use wml::debian::translation-check translation="bd45142ee8152a7cabf4f7add4d67214246fd108" maintainer="galaxico" - -<p> -Services: -</p> -<ul> - <li>System installations</li> - <li>Software configurations</li> - <li>Maintenance</li> - <li>Monitoring 24x7</li> - <li>Backup & Disaster Recovery</li> - <li>Migration</li> -</ul> diff --git a/greek/consultants/linuxmagic.wml b/greek/consultants/linuxmagic.wml deleted file mode 100644 index 2bbb510f074..00000000000 --- a/greek/consultants/linuxmagic.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="LinuxMagic" -#use wml::debian::translation-check translation="927eb55e86cfa77bd11add4024391b1bfd59b228" maintainer="galaxico" - -<p> -Pacific Northwest's Premier Linux Support House since 1997, -serving the Enterprise, ISP and Telco markets. -</p> diff --git a/greek/consultants/logilab.wml b/greek/consultants/logilab.wml deleted file mode 100644 index 468224de662..00000000000 --- a/greek/consultants/logilab.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="LOGILAB" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -We have DD in our staff and publish all our free software as Debian -packages, see www.logilab.org. Furthermore, we have a course about -Debian administration and a course about packaging software for Debian. -Other courses will appear on our website once written. -</p> diff --git a/greek/consultants/m_bilow.wml b/greek/consultants/m_bilow.wml deleted file mode 100644 index c2320bbe4e5..00000000000 --- a/greek/consultants/m_bilow.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Bilow Computer Science, Inc." -#use wml::debian::translation-check translation="559ee8ebb660008e4ec2fb614486ad90fb92df4b" maintainer="galaxico" - -<p> -Established 1977, Linux since 1993. Service area covers RI, MA, CT, -southern NH, and eastern NY including the cities of Providence, Boston, -New York City, Hartford, New Haven, and Nashua. -</p> diff --git a/greek/consultants/m_bocquet.wml b/greek/consultants/m_bocquet.wml deleted file mode 100644 index 92a66dec85f..00000000000 --- a/greek/consultants/m_bocquet.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Mathias BOCQUET" -#use wml::debian::translation-check translation="c2c3d1ce6fcba51ae9cd150b28cc1f6fb82a4145" original="french" -#use wml::debian::translation-check translation="a35cadeab212400b98bc216c816f2c94c5ee8801" maintainer="galaxico" - -<p> -Possible remote interventions worldwide. -</p> diff --git a/greek/consultants/m_konzack.wml b/greek/consultants/m_konzack.wml deleted file mode 100644 index f60800a52dd..00000000000 --- a/greek/consultants/m_konzack.wml +++ /dev/null @@ -1,12 +0,0 @@ -#use wml::debian::consultant name="Michelle Konzack" -#use wml::debian::translation-check translation="dfcdae856174de2f76bd67fbafdfdb2d71f97abf" maintainer="galaxico" - -<ul> -<li>Services available for France (Strasbourg and 67xxx) and Germany</li> -<li>Website and Database Hosting under Debian GNU/Linux</li> -<li>Design and coding of Intranet Infrastructures -(based on Apache2, PHP, PostgreSQL, Courier, ...)</li> -<li>Cloud Storages</li> -<li>Embedded programming (ARM only) under EmDebian</li> -</ul> - diff --git a/greek/consultants/mare.wml b/greek/consultants/mare.wml deleted file mode 100644 index fa8b0374dba..00000000000 --- a/greek/consultants/mare.wml +++ /dev/null @@ -1,14 +0,0 @@ -#use wml::debian::consultant name="MARE system" -#use wml::debian::translation-check translation="59d581c9ce161f9c25646e0e8a8b23b6a10963be" maintainer="galaxico" - -<p> -We offer linux (mostly Debian) based hosting-services for -ecommerce and customized setups, including security, server-setup and -administration, monitoring (nagios), database and application-hosting and a lot -of other linux-based services. -</p> - -<p> -A complete list with our competences and some references can be found on our -website at <a href="http://www.mare-system.de/">http://www.mare-system.de/</a>. -</p> diff --git a/greek/consultants/miklos.wml b/greek/consultants/miklos.wml deleted file mode 100644 index be8fda1129a..00000000000 --- a/greek/consultants/miklos.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Miklos Consulting" -#use wml::debian::translation-check translation="f665ef905b9bbc44f2dfd48af67295b08c3d455c" maintainer="galaxico" - -<p> -Speaking Hungarian and English. -</p> diff --git a/greek/consultants/mirrlelabs.wml b/greek/consultants/mirrlelabs.wml deleted file mode 100644 index 9e9420746ff..00000000000 --- a/greek/consultants/mirrlelabs.wml +++ /dev/null @@ -1,41 +0,0 @@ -#use wml::debian::consultant name="mirrle labs" -#use wml::debian::translation-check translation="3d5527b246d5d451eaee0d8c2c0f2f642f3a3df3" original="german" -#use wml::debian::translation-check translation="c0816ff3dae7deb1cd48fb2f83fa934f5e5f3559" maintainer="galaxico" - -<p> - -Topics where we have gathered excellent specialization: -</p> - -<ul> -<li>Migration strategies and project implementation</li> -<li>Education and training</li> -<li>Error analysis and problem fixes</li> -<li>Security and post-mortem analysis, forensics, intrusion detection</li> -<li>Development of specially adapted or fully automated Linux systems</li> -<li>Project support - a second opinion</li> -<li>Integrated Fax- and SMS/GSM-Server</li> -<li>Messaging Services (like Jabber, XMPP, Telegram, ICQ, IRC)</li> -<li>Mail Server (Postfix, Dovecot)</li> -<li>Apache & Nginx Webserver-solutions</li> -<li>MySQL, PostgreSQL database solutions (Streaming Replication, Master/Master & Master/Slave)</li> -<li>Remote Hand - the helping hand</li> -<li>Security (Firewalls, WAFs, Proxys, Virus scanners, VPNs, HoneyPots, IDS Systems, Fail2Ban, Iptables)</li> -<li>Data- export/import, development of data converters</li> -<li>Automatic installation (unattended, PXE, TFTPd, Preseed, FAI)</li> -<li>System integration of Linux and Windows applications for mixed mode (Samba)</li> -<li>LDAP directory services</li> -<li>Backup solutions</li> -<li>Deployment solutions</li> -<li>Cluster file systems (Ceph, DRDB, GlusterFS)</li> -<li>Configuration management systems (Chef, Puppet, Ansible)</li> -<li>Software distribution</li> -<li>Version control systems / repositorys (Git, Mercurial, SVN)</li> -<li>Debian Packaging (APT Caching Proxy, Debian Mirroring, own and custom packages)</li> -<li>Failover Clustering (Pacemaker, DRBD, Veritas Cluster Server, Keepalived, LinuxHA)</li> -<li>Load Balancer (Keepalived, haproxy, Nginx)</li> -<li>Virtualization (KVM, Vserver, VMware vSphere, qemu, Xen)</li> -<li>Development (Bash, Python, dialog-based applications)</li> -<li>Kiosk- and Displaysystems</li> -<li>Sensors, Automation and Control systems</li> -</ul> diff --git a/greek/consultants/murat_demirten.wml b/greek/consultants/murat_demirten.wml deleted file mode 100644 index eea06a55943..00000000000 --- a/greek/consultants/murat_demirten.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="Murat Demirten" -#use wml::debian::translation-check translation="656a4f5f4952c1498a2d560996ba9156ff5cbdc6" maintainer="galaxico" - -<p> -We provide Debian GNU/Linux server installation and maintenance support to -customers. We have strong experience on creating customized Debian Live CD -environments and building customized (especially in thin client systems) -versions of Debian distribution. We have been preparing training sessions for -Debian Installation and Usage. -</p> diff --git a/greek/consultants/murphy_soft.wml b/greek/consultants/murphy_soft.wml deleted file mode 100644 index 5cd0113a745..00000000000 --- a/greek/consultants/murphy_soft.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Murphy Software BV" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -A portion of Debian-related revenues will be donated to the Debian project. -</p> - diff --git a/greek/consultants/netfs.wml b/greek/consultants/netfs.wml deleted file mode 100644 index 408c0003213..00000000000 --- a/greek/consultants/netfs.wml +++ /dev/null @@ -1,13 +0,0 @@ -#use wml::debian::consultant name="NetFS" -#use wml::debian::translation-check translation="1a4e5484cbca5ab19220349fe1262c3bfb523702" maintainer="galaxico" - -<p> -Our services: -</p> -<ul> -<li>Consulting IT and Constant Support</li> -<li>System installations and configurations</li> -<li>Software implementation and tests</li> -<li>Security Audits and backup systems</li> -<li>Monitoring servers and network</li> -</ul>
\ No newline at end of file diff --git a/greek/consultants/ondrej_sury.wml b/greek/consultants/ondrej_sury.wml deleted file mode 100644 index 2f692c096bc..00000000000 --- a/greek/consultants/ondrej_sury.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Ondřej Surý" -#use wml::debian::translation-check translation="2a4093449794059527ef6278d904260506503e22" maintainer="galaxico" - -<p> -Main expertise in domains, DNS and DNSSEC (Knot DNS, Bind9, NSD3, Unbound -& OpenDNSSEC) and routing (Bird). Experience in webhosting (apache2, -php, fastcgi) and mailhosting (postfix, cyrus-imap). Can help with redmine -installations. -</p> diff --git a/greek/consultants/open_solutions.wml b/greek/consultants/open_solutions.wml deleted file mode 100644 index c13f56b3571..00000000000 --- a/greek/consultants/open_solutions.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="OpenSolutionsMx" -#use wml::debian::translation-check translation="d6cee0b3091204fa8389a48ae8f02763d05009c1" maintainer="galaxico" - -<p> -Help Debian, a percentage of the money -raised will be donated to the foundation. -</p> diff --git a/greek/consultants/openit.wml b/greek/consultants/openit.wml deleted file mode 100644 index 280c28b610d..00000000000 --- a/greek/consultants/openit.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Open IT" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -I use linux from 1993 and I do always System Administration/Integration -with Debian, of course. -</p> diff --git a/greek/consultants/ozgur_yazilim.wml b/greek/consultants/ozgur_yazilim.wml deleted file mode 100644 index b0b6ce80f04..00000000000 --- a/greek/consultants/ozgur_yazilim.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Ozgur Yazilim AS" -#use wml::debian::translation-check translation="30f7dcf831e29439c28f258807f135c3b1bad3ed" maintainer="galaxico" - -<p> -Ozgur Yazilim AS creates products and -solutions by developing free software, by choosing and integrating -free software of highest quality, and by providing hosting and -support. -</p> diff --git a/greek/consultants/ozonomultimedia.wml b/greek/consultants/ozonomultimedia.wml deleted file mode 100644 index 210ed850de0..00000000000 --- a/greek/consultants/ozonomultimedia.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Ozono Multimedia s.l.l." -#use wml::debian::translation-check translation="aa0bb0d6120d0c1d519b5f281918764cacf19d89" maintainer="galaxico" - -<p> -Specialists in GNU/Linux Systems, Python and Advanced -Multimedia (mobile, TV, Internet) applications. Experts in Research & -Development Projects. -</p> diff --git a/greek/consultants/palazzini_francesco.wml b/greek/consultants/palazzini_francesco.wml deleted file mode 100644 index 57373c2c4da..00000000000 --- a/greek/consultants/palazzini_francesco.wml +++ /dev/null @@ -1,5 +0,0 @@ -#use wml::debian::consultant name="Palazzini Francesco" -#use wml::debian::translation-check translation="a10a97efaf7ccefe73c0897d57d59ef1fa1c044e" maintainer="galaxico" - -<p>IT consultant / Linux system administrator, specialised in computer -security and system reliability.</p> diff --git a/greek/consultants/peter_d.wml b/greek/consultants/peter_d.wml deleted file mode 100644 index af874686821..00000000000 --- a/greek/consultants/peter_d.wml +++ /dev/null @@ -1,11 +0,0 @@ -#use wml::debian::consultant name="Kangaroot Linux Solutions" -#use wml::debian::translation-check translation="e53be59d5458867ef3389f0933829872a2548842" maintainer="galaxico" - -<p> -Kangaroot is Belgium's top Linux & Open Source service partner. -We design, install and support Open Source infrastructure solutions for -multinationals, all levels of government, mid-size companies and -non-profit organisations. We deliver real added value by solving your -strategic business technology challenges. -</p> - diff --git a/greek/consultants/philiphands.wml b/greek/consultants/philiphands.wml deleted file mode 100644 index 4f9f94e58b7..00000000000 --- a/greek/consultants/philiphands.wml +++ /dev/null @@ -1,17 +0,0 @@ -#use wml::debian::consultant name="Philip Hands" -#use wml::debian::translation-check translation="1eefd8c88d2a04a0efc42f5f61f48c06155001c1" maintainer="galaxico" - -<p> -Hands.com Ltd has been providing support and consultancy related to -Free Software in general and Debian GNU/Linux in particular since -1993. It is owned and run by Philip Hands, who has been a Debian -developer since 1996, and has a wide knowledge of Free Software, -with particular specialisation in communications and interconnection of -systems, having been the Debian maintainer for packages including ssh, -rsync, ppp, and mgetty, and a member of the -Debian System Administration team. The server that hosts <a -href="ftp.uk.debian.org">ftp.uk.debian.org</a> is owned and -maintained by hands.com Ltd, and Philip Hands has been involved with -organising DebConf conference every year since 2007, as well as often -sponsoring the conference. -</p> diff --git a/greek/consultants/profelis.wml b/greek/consultants/profelis.wml deleted file mode 100644 index 67a809f4b09..00000000000 --- a/greek/consultants/profelis.wml +++ /dev/null @@ -1,5 +0,0 @@ -#use wml::debian::consultant name="Caglar Ulkuderner" -#use wml::debian::translation-check translation="05478afc591832a7d1081eb55ae3b87bcccac23e" maintainer="galaxico" - -<p>Profelis is leading and the only company in Turkey who has ISO 9001 and ISO 27001 -on Linux and Open Source Consultancy.</p> diff --git a/greek/consultants/prolibre.wml b/greek/consultants/prolibre.wml deleted file mode 100644 index 5ad8e54989e..00000000000 --- a/greek/consultants/prolibre.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="ProLibre" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Linux server installations of Debian, migration to Linux, development, support, -maintenance and training since 2000. -</p> diff --git a/greek/consultants/psychsoft.wml b/greek/consultants/psychsoft.wml deleted file mode 100644 index 0694340257c..00000000000 --- a/greek/consultants/psychsoft.wml +++ /dev/null @@ -1,4 +0,0 @@ -#use wml::debian::consultant name="psychsoft" -#use wml::debian::translation-check translation="ef6f2b690b0710ed78739ea081dcc5add5ba4957" maintainer="galaxico" - -<p>As former college professors, we have long been supporters of open source and Linux.</p> diff --git a/greek/consultants/puchalak.wml b/greek/consultants/puchalak.wml deleted file mode 100644 index ce266413e16..00000000000 --- a/greek/consultants/puchalak.wml +++ /dev/null @@ -1,11 +0,0 @@ -#use wml::debian::consultant name="Dariusz Puchalak" -#use wml::debian::translation-check translation="533989de621be0fa2e9a4602bba549cf85cd63b6" maintainer="galaxico" - -<p> -I have 20 years of Linux/Unix administration experience. -Current holder of Red Hat Certificate Architect, Novell Certified -Linux Engineer 11, SUSE CLE 11 Advanced Technical Specialist and -few more from <q>open/closed source</q> vendors. -</p><p> -Projects outside Poland are accepted as well. -</p> diff --git a/greek/consultants/quiarit.wml b/greek/consultants/quiarit.wml deleted file mode 100644 index 721a0857a92..00000000000 --- a/greek/consultants/quiarit.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="QuiAr IT" -#use wml::debian::translation-check translation="a90f8a32396513e4378a524002d6cb46f0012fbc" maintainer="galaxico" - -<p> -Linux and Open Source Services -</p> diff --git a/greek/consultants/r_coker.wml b/greek/consultants/r_coker.wml deleted file mode 100644 index c7565d49917..00000000000 --- a/greek/consultants/r_coker.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Russell Coker" -#use wml::debian::translation-check translation="dc9dbeecfd558a1f6c443fca8b234e413fb1b5f5" maintainer="galaxico" - -<p> -Expert on SE Linux, Postfix, and Linux storage. -</p> diff --git a/greek/consultants/radek_sima.wml b/greek/consultants/radek_sima.wml deleted file mode 100644 index 70ecf058a47..00000000000 --- a/greek/consultants/radek_sima.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="Radek Šíma" -#use wml::debian::translation-check translation="92f2e2a7cb0d7e69baf650df4f6eb4ce52c7e8e0" maintainer="galaxico" - -<ul> -<li>Support area: Prague or Central Bohemia, max 50 km.</li> -<li>I speak English fluently, additionally to Czech.</li> -<li>I have an official registration for computer support and training, -<q>Trade Certificate</q> (<q>Zivnostensky list</q> in Czech), so, everything -is legal, I can make legal invoicing for people or firms.</li> -</ul> diff --git a/greek/consultants/reconnix.wml b/greek/consultants/reconnix.wml deleted file mode 100644 index f911cbc66cb..00000000000 --- a/greek/consultants/reconnix.wml +++ /dev/null @@ -1,14 +0,0 @@ -#use wml::debian::consultant name="Reconnix" -# Translators: company "ForLinux" was renamed into "Reconnix" -#use wml::debian::translation-check translation="d693a75e14734c12b9db1ad86f682f8c04917952" maintainer="galaxico" - -<p> -Reconnix is a UK technology services company specialising in providing -Open Source Eco-Systems, Digital Delivery, Cloud and Managed Hosting -solutions to Public and Private sector Enterprises. Our consultancy, -development and management services are characterised by an inherent -drive to manage operational complexity for commercial competitive -advantage and service improvement. Open Source is at the heart of what -we do and we are passionate about delivering Enterprise class Open Source -solutions. -</p> diff --git a/greek/consultants/rei.wml b/greek/consultants/rei.wml deleted file mode 100644 index b5ced97848c..00000000000 --- a/greek/consultants/rei.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Reinaldo Gil Lima de Carvalho" -#use wml::debian::translation-check translation="f6d1c7d199ccda9d66e0c1de6eabcdb3ea8df38d" maintainer="galaxico" - -<p> -I am a Debian consultant for projects in Brazil, and I can optimize their -business processes and reduce the TCO with free software solutions provided -by the Debian project. Please see more (in Brazilian Portuguese) at -<url "https://reinaldoc.wordpress.com/about/debian-consultant/">. -</p> diff --git a/greek/consultants/rejas.wml b/greek/consultants/rejas.wml deleted file mode 100644 index 4a39d60e4a5..00000000000 --- a/greek/consultants/rejas.wml +++ /dev/null @@ -1,13 +0,0 @@ -#use wml::debian::consultant name="Rejås Datakonsult AB" -#use wml::debian::translation-check translation="aaa7f663f3185a2ffde73d4b2b18f8f7f436d3a1" maintainer="galaxico" - -<p> -Rejås Datakonsult AB is a small company with its office in Norrtälje close -to Stockholm, Sweden. Rejås Datakonsult is a modern company that, together -with established partners, can also take bigger assignments. We are -experts in maintenance of systems build on free software and are ready -to take care of your servers. -</p> -<p> -Rejås Datakonsult AB is a legally registered business in Sweden. -</p> diff --git a/greek/consultants/rvm.wml b/greek/consultants/rvm.wml deleted file mode 100644 index c1cc9f98da9..00000000000 --- a/greek/consultants/rvm.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="RVM S.r.l." -#use wml::debian::translation-check translation="adb9103d625d1ef0efbd12cc1cc24d7336e7e619" maintainer="galaxico" - -<p> -We have a strong knowledge of Debian/GNU Linux since woody release. -We started deploying Linux solutions in 1993. -</p> - diff --git a/greek/consultants/sange.wml b/greek/consultants/sange.wml deleted file mode 100644 index f8bc580deb2..00000000000 --- a/greek/consultants/sange.wml +++ /dev/null @@ -1,12 +0,0 @@ -#use wml::debian::consultant name="Seravo" -# Note: Sange was renamed into Seravo -#use wml::debian::translation-check translation="291d511f45658fc5c7ac3be06d0629b47b484d27" maintainer="galaxico" - -<p> -Seravo is a company with a strong commitment and expertise in Linux -and open source software. Our services include consulting, design, -development and administration. We have a long history of using and -developing (e.g. doing packaging) of Debian and its derivates (e.g. -Ubuntu). We work in Finnish, Swedish and English. Visit our website -for additional information. -</p> diff --git a/greek/consultants/scheeder.wml b/greek/consultants/scheeder.wml deleted file mode 100644 index c11b1b0be00..00000000000 --- a/greek/consultants/scheeder.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Scheeder & Partner GmbH" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -We support Debian servers in industry and health care since 1995, -we support the full Debian range, samba, freeswan, postgresql and -others. We are familiar with several open source applications. -Please feel free to ask us your questions! -</p> diff --git a/greek/consultants/science_resource_asia.wml b/greek/consultants/science_resource_asia.wml deleted file mode 100644 index 59a87f87b8c..00000000000 --- a/greek/consultants/science_resource_asia.wml +++ /dev/null @@ -1,81 +0,0 @@ -#use wml::debian::consultant name="Science Resource Asia" -#use wml::debian::translation-check translation="7101d0f39e02ee8088d173d7a10841df64c645ae" maintainer="galaxico" - -<strong>About Us: </strong> -Linux enthusiasts and consultants since 1995. Using Debian GNU/Linux within our firm since 2005 for: - -<div class="line"> -<div class="item col50"> - <ul> - <li>Administration</li> - <li>Accounting</li> - <li>Project Management</li> - <li>Document & report publication</li> - <li>Web, eMail, VOIP comms</li> - <li>Software development</li> - <li>Engineering & PCB design</li> - </ul> -</div> - -<div class="item col50 lastcol"> - <ul> - <li>Mathematical analysis</li> - <li>Numerical models of meteorological & oceanographic phenomena</li> - <li>Mapping & GIS</li> - <li>Environmental data acquisition & analysis</li> - <li>Environmental databases</li> - <li>High Availability, CRM, backup & security</li> - <li>Servers, desktops, laptops, & PDA's</li> - </ul> -</div> -</div> - -<ul> -<li>Experienced installing and configuring Debian on x86, x64, ARM, Ultrasparc, MIPS, & Alpha.</li> -<li>Supporting industry, government and private users in Singapore, Malaysia, and Indonesia.</li> -</ul> - -<hr> -<strong>Service Offerings:</strong> -<ul> -<li><p><strong>Migration to Debian GNU/Linux: </strong> We assist small-to-medium enterprises (SME's, typically 1-20+ staff) -to transition IT operations to Debian. Services include software and hardware advice; installation; configuration; commissioning; training; support and contract system-administration.</p></li> - -<li><p><strong>Diskless 'Thin Client' networks </strong> — talk to us to find out how these can -slash your IT hardware and administration costs. </p></li> - -<li><p><strong> Specialist skills </strong> in scientific, engineering and medical applications.</p></li> - -<li><strong>Community:</strong> We are keen to support NGO and Education -projects in any ASEAN country (Brunei, Cambodia, Thailand, -Philippines, Indonesia, Malaysia, Singapore, -Vietnam) with Debian solutions — reduced rates apply. </li> - -<li>Free phone consultation/guidance to proponents of ASEAN -IT projects for NGO and education sectors.</li> - -<li><p><strong>Inception studies:</strong> Workflow Analysis; Requirements Specification; recommendations.</p></li> - -<li><p><strong>Forensics:</strong> Data forensics and recovery from Windows or Linux crashed disks.</p></li> - -<li><p><strong>Publishing:</strong> Document preparation and publishing (LaTeX: <a href="https://www.latex-project.org">www.latex-project.org)</a></p></li> -<li><p><strong>Programming:</strong> C++; Fortran; Java; Octave; Mapscript, PHP, etc.</p></li> -<li><p><strong> Bespoke application development:</strong> applied physics; oceanography; geophysics and engineering.</p></li> -</ul> - -<hr> -<strong>Training Offerings:</strong> -<ul> -<li>Debian training tailored to customer needs.</li> -<li>Selected GNU/Linux applications.</li> -<li>LaTeX document processing tutorials.</li> -</ul> - -<hr> -<strong>Contact:</strong> -<br> -Phone: +65 96.15.86.61 -<br> -Email: -<a href="mailto:info@sciresource.com"> Email us!</a> - diff --git a/greek/consultants/scratchspace.wml b/greek/consultants/scratchspace.wml deleted file mode 100644 index ee3f8023878..00000000000 --- a/greek/consultants/scratchspace.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="ScratchSpace Inc." -#use wml::debian::translation-check translation="2f18a20929f522519e5ca7ec7114b945ebbae9fd" maintainer="galaxico" - -<p> -ScratchSpace Inc. is an IT Managed Services -Provider specializing in Linux and Open Source Software. We design, -build, monitor, and maintain public and private cloud infrastructure. We -provide services for a variety of customer types, including software -development companies, SaaS providers, and technology startups. -</p> diff --git a/greek/consultants/serverflow.wml b/greek/consultants/serverflow.wml deleted file mode 100644 index b7d10c1aee6..00000000000 --- a/greek/consultants/serverflow.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Serverflow consulting, d.o.o." -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Can telecomute for jobs elsewhere. -</p> diff --git a/greek/consultants/sghazi.wml b/greek/consultants/sghazi.wml deleted file mode 100644 index a125fbf1cc5..00000000000 --- a/greek/consultants/sghazi.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Shahryar Ghazi" -#use wml::debian::translation-check translation="0d37ef37ff1a62833591065e07acd8f1ff44a87b" maintainer="galaxico" - -<p> -System/Network admin, DBA/Developer, Designer, Programmer -</p><p> -I can help you setup web servers, database servers, -revision control systems and more. -</p> diff --git a/greek/consultants/shannon_d.wml b/greek/consultants/shannon_d.wml deleted file mode 100644 index d10bd443531..00000000000 --- a/greek/consultants/shannon_d.wml +++ /dev/null @@ -1,15 +0,0 @@ -#use wml::debian::consultant name="DeaTech Research Inc." -#use wml::debian::translation-check translation="755cf462403b2de3e2ce2945159966933d5ecacb" maintainer="galaxico" - -<p>Real-time, device driver, and embedded systems specialist. -Extensive experience in system administration, web development, and many -other areas. Twenty years Linux experience (mostly Debian), -BS Computer Science, BS Biochemistry and Biophysics, -25 years in business. Please visit -<a href="http://www.deatech.com/">www.deatech.com</a> -for more information. -</p> - -<p>Reference the Debian web site and five percent of the proceeds for labor -related charges on your project will be donated to Debian. -</p> diff --git a/greek/consultants/sicurezzarete.wml b/greek/consultants/sicurezzarete.wml deleted file mode 100644 index 7f7a95d109a..00000000000 --- a/greek/consultants/sicurezzarete.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Sicurezzarete" -#use wml::debian::translation-check translation="18d575df657bd8e2acf652e5671f859d1dd3b189" maintainer="galaxico" - -<p> -Provides administration and support of Linux servers, firewalls, routers, -VPN, email server, web server, DNS server, fax server at your company -and on remote servers. -</p> diff --git a/greek/consultants/simone_giustetti.wml b/greek/consultants/simone_giustetti.wml deleted file mode 100644 index 4399f00e200..00000000000 --- a/greek/consultants/simone_giustetti.wml +++ /dev/null @@ -1,23 +0,0 @@ -#use wml::debian::consultant name="Studio Simone Giustetti" -#use wml::debian::translation-check translation="007212c993e95b7d9497b8d8ad4322a97d7cbb0c" maintainer="galaxico" - -<p> -Studio Simone Giustetti is a company specialized in providing ICT -services with high added value. Its main asset consists of the -experience, skills, professionalism, and passion brought in by the -people it employs. StudioSg delivers solutions based on Open Source -products. It has been offering Debian Gnu/Linux based solutions since -2000 and gradually enriched its product expertise in order to meet -customer satisfaction and comply with technology evolution. -</p> -<p> -Offered services include: -</p> -<ul> -<li>Debian GNU/Linux system integration and administration.</li> -<li>Debian GNU/Linux installation, configuration and day by day administration.</li> -<li>Back-up configuration and management for both file systems and databases.</li> -<li>Customization and development of software packages for the Debian -GNU/Linux platform.</li> -<li>Deployment of Debian packages.</li> -</ul> diff --git a/greek/consultants/sine_nomine.wml b/greek/consultants/sine_nomine.wml deleted file mode 100644 index 370034582d2..00000000000 --- a/greek/consultants/sine_nomine.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Sine Nomine Associates" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Sine Nomine Associates is a research and development company focused -on bringing developing technology to practical business solutions. -</p> diff --git a/greek/consultants/sirius.wml b/greek/consultants/sirius.wml deleted file mode 100644 index 56e34d39403..00000000000 --- a/greek/consultants/sirius.wml +++ /dev/null @@ -1,11 +0,0 @@ -#use wml::debian::consultant name="Sirius Corporation" -#use wml::debian::translation-check translation="322e317492204e574fa7513ebdf8b79c8d10ed76" maintainer="galaxico" - -<p> -Sirius is the UK's leading Open Source services provider. -Genuine 24/7/365 operations and specialising in support, managed -services, outsourcing, consultancy, deployment and training. -Sirius designs, builds, supports and has managed systems since 1998 for -public, private and education sectors. -Some of Sirius' clients include Specsavers and the Cabinet Office. -</p> diff --git a/greek/consultants/small_business.wml b/greek/consultants/small_business.wml deleted file mode 100644 index 14bfa152653..00000000000 --- a/greek/consultants/small_business.wml +++ /dev/null @@ -1,30 +0,0 @@ -#use wml::debian::consultant name="Small Business Data Group" -#use wml::debian::translation-check translation="1adfd49fed1e37a0c45268def91e8cc46ca41fe6" maintainer="galaxico" - -<p> -SBDC is a Far North Queensland based information technology consultancy & -provider. We provide an extensive range of services and support to a large -variety of businesses and consumers. -Our focus is to provide cost effective services that suit your requirements. -</p><p> -Some of our specialties are: -</p> - -<ul> -<li>Linux consultancy</li> -<li>VoIP Consultancy and Provisioning</li> -<li>Remote Administration of servers and workstations</li> -<li>Automated offsite/remote backup</li> -<li>Managed Networks & firewalls</li> -<li>End User Support</li> -<li>Website design & development</li> -<li>Domain, web & e-mail hosting</li> -</ul> - -<p> -We use every day English to ensure that you understand the ins and outs of -every situation. -Our priority is to relieve you of technology stress, so you can get back -and utilise the systems how they were designed, to do what you do best. -We are a GLBT Friendly Business. -</p> diff --git a/greek/consultants/sol1.wml b/greek/consultants/sol1.wml deleted file mode 100644 index ab258431fed..00000000000 --- a/greek/consultants/sol1.wml +++ /dev/null @@ -1,24 +0,0 @@ -#use wml::debian::consultant name="Solutions First" -#use wml::debian::translation-check translation="b423ee95dacfbce73ecec75272ad4cf00de91b92" maintainer="galaxico" - -<p> -Solutions First is a Sydney based information technology consultancy. We -provide a wide range of services and support to a large variety of businesses, -spanning medium sized enterprise through to home offices. Our focus is to -provide prompt, cost effective services that suit your requirements. Some -examples of our specialties are: -</p> -<ul> -<li>Linux consultancy</li> -<li>Automated offsite/remote backup</li> -<li>Managed firewalls</li> -<li>Network support</li> -<li>Website design & development</li> -<li>Domain, web & email hosting</li> -</ul> -<p> -We are personable people and emphasize simplicity in the way we carry out our -services for clients. We make sure you understand the why, what, when and how -of every situation. Our job is to relieve you of technology problems so you can -get back to what you do best. -</p> diff --git a/greek/consultants/starnix.wml b/greek/consultants/starnix.wml deleted file mode 100644 index 20367c0b84c..00000000000 --- a/greek/consultants/starnix.wml +++ /dev/null @@ -1,26 +0,0 @@ -#use wml::debian::consultant name="Starnix Inc." -# Update from Kevin Glendenning, 28.02.2013 -#use wml::debian::translation-check translation="335e71e16d3bfd0b7acb202dede76ade947b78fe" maintainer="galaxico" - -<p> -Starnix is a technology firm founded in 1998, with a focus on Linux and -Open Source. From teaching revision control software courses at Research -in Motion to video card driver development for AMD/ATI, Starnix has a -proven track record of delivering exceptional service and cost savings -by leveraging Open Source technologies. -</p> -<p> -Such savings extend to their product line, a suite of Linux-based -servers including Firewall/VPN, database, network-attached storage, -backup and thin clients. These products are supported and maintained by -Starnix's managed services. -</p> -<p> -Starnix continues to significantly lower IT costs for businesses while -at the same time enhancing systems security and flexibility. Many of -North America’s industry leaders such as Clover Leaf Seafoods, Expedia, -Indigo Books and Konica Minolta have realized the benefits of Open -Source technologies by taking advantage of Starnix’s products and -services throughout the company’s 14-year history. -</p> - diff --git a/greek/consultants/steve_l.wml b/greek/consultants/steve_l.wml deleted file mode 100644 index 67360e690b0..00000000000 --- a/greek/consultants/steve_l.wml +++ /dev/null @@ -1,11 +0,0 @@ -#use wml::debian::consultant name="David Goodenough & Associates Limited (DGA)" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Additional Information: DGA specialise in connectivity, and have been -described as "Technical Glue manufacturers". We have experience with -Enterprise systems, and have worked extensively with Lotus Domino, -Websphere and Tomcat Web servers and Java programming. We also work with -corporate eMail systems, building bridges between legacy and SMTP systems -and doing migrations. -</p> diff --git a/greek/consultants/stin_priza.wml b/greek/consultants/stin_priza.wml deleted file mode 100644 index 9bf819a89f2..00000000000 --- a/greek/consultants/stin_priza.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Stin Priza Tech Collective" -#use wml::debian::translation-check translation="5fb26a76ae8b3eebe11e4cdfcb713ca4c0e60fdf" maintainer="galaxico" - -<p> -Stin Priza is a tech-workers collective mainly -focused on: Free Software, Reuse-Recycle, Open Standards, Freedom of -Speech & Privacy online, Social change. -</p> - diff --git a/greek/consultants/suhaibuddeen.wml b/greek/consultants/suhaibuddeen.wml deleted file mode 100644 index b536059702c..00000000000 --- a/greek/consultants/suhaibuddeen.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Mesiniaga Berhad" -#use wml::debian::translation-check translation="145a871f870a69c6d9661d153ca215f8db312999" maintainer="galaxico" - -<p> -Open Source Software Consultant with excellent track records in wide range -implementations on infrastructure and platform for both new setup as well -as migration from proprietary systems. -</p> diff --git a/greek/consultants/sysnove.wml b/greek/consultants/sysnove.wml deleted file mode 100644 index 7634e60e30f..00000000000 --- a/greek/consultants/sysnove.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="Sysnove" -#use wml::debian::translation-check translation="6dd59940c8d330024449393ca9e0e75f42114317" maintainer="galaxico" - -<p> -Sysnove's core business is the system administration -(upgrades, securisation, monitoring, backups, etc.) of -virtual private servers for web agencies and software -companies which does not have a sysadmin in their employees. -We also provide cloud storage services. -</p> diff --git a/greek/consultants/t_kurek.wml b/greek/consultants/t_kurek.wml deleted file mode 100644 index c2364be004a..00000000000 --- a/greek/consultants/t_kurek.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="Tytus Kurek" -#use wml::debian::translation-check translation="b1f6675d99db329da3b7b3344f9673861d2ae935" maintainer="galaxico" - -<p> -LPIC (Linux Professional Institute Certification) -Level 3 (Senior) certificate. -</p> diff --git a/greek/consultants/ted_j.wml b/greek/consultants/ted_j.wml deleted file mode 100644 index 5410f6a1cec..00000000000 --- a/greek/consultants/ted_j.wml +++ /dev/null @@ -1,14 +0,0 @@ -#use wml::debian::consultant name="JordanTeam IT Training" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p>Specialize in Unix, Linux, and Solaris Training. -Consulting includes Data Security, Disaster Recovery, -and Porting Applications to Unix/Linux.</p> - -<p>Over 15 years Unix administration, programming, and -training experience with General Motors, Ford, Sun, -SGI, Chrysler, and Tier 1 and 2 Auto Suppliers.</p> - -<p>MSE from U.C. Berkeley.</p> - -<p>Will travel worldwide.</p> diff --git a/greek/consultants/tegtmeier.wml b/greek/consultants/tegtmeier.wml deleted file mode 100644 index cb6c34d673f..00000000000 --- a/greek/consultants/tegtmeier.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Tegtmeier Internet Solutions e.K." -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Planning, realization, development and maintenance of internet projects -running on Debian. Focused on internet-security, performance/optimization -and high availability. Experience with Debian since several years. -Give us a call for reference projects and a free quote. -</p> diff --git a/greek/consultants/tiger_computing.wml b/greek/consultants/tiger_computing.wml deleted file mode 100644 index ad7fe5425b8..00000000000 --- a/greek/consultants/tiger_computing.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="Tiger Computing Ltd." -#use wml::debian::translation-check translation="a3e2f1c8bcdd4698998729d49581964009db62ea" maintainer="galaxico" - -<p> -We supply, monitor and support Debian servers throughout England and Wales. -We target our services at businesses that want the best possible -availability of their Debian systems. We provide a range of support -contracts and ad hoc consultancy services to ensure that you get the very -best value from your investment in Linux. -</p> diff --git a/greek/consultants/tina_pm.wml b/greek/consultants/tina_pm.wml deleted file mode 100644 index 259bd65df9c..00000000000 --- a/greek/consultants/tina_pm.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="tina.pm" -#use wml::debian::translation-check translation="88c24ef18a9ef56790eddc2526de2f246261220b" maintainer="galaxico" - -<p> -I'm often traveling around Europe, so if you are interested in meeting -me outside of Ireland, please get in touch. -</p> diff --git a/greek/consultants/togaware.wml b/greek/consultants/togaware.wml deleted file mode 100644 index c846a5326c3..00000000000 --- a/greek/consultants/togaware.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::consultant name="Togaware" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Togaware has over 10 years experience in installing Debian GNU/Linux -systems for both industry and government, as well as home users. Our -Debian GNU/Linux Desktop Survival Guide is widely referenced and -continually updated. We also make available the Debian package wajig -which simplifies system and package management for Debian. -</p> diff --git a/greek/consultants/toni_m.wml b/greek/consultants/toni_m.wml deleted file mode 100644 index 8fd69169033..00000000000 --- a/greek/consultants/toni_m.wml +++ /dev/null @@ -1,19 +0,0 @@ -#use wml::debian::consultant name="Oeko.neT" -#use wml::debian::translation-check translation="c3900379bc662d4577e74b4745668809a1142639" maintainer="galaxico" - -<p> -Toni holds a University degree in computer science (Dipl.-Inf.) -and has been active as a consultant since about 1985, and operated -an ISP since 1994. Customers as large as PLCs enjoy projects -that are functional, on time and on budget, too. -</p><p> -He tends to specify, design and implement in the direction of -a robust, scalable, and secure solution that can handle the -anticipated load if the client permits, maybe owing to his -ISP background there. -</p><p> -During all the work, he strongly emphasizes free software, if -somehow feasible. Available for tasks in other countries as well, -depending on the specifics. We offer Debian housing & hosting, both -managed and unmanaged. -</p> diff --git a/greek/consultants/trademaker.wml b/greek/consultants/trademaker.wml deleted file mode 100644 index 80b5a17e961..00000000000 --- a/greek/consultants/trademaker.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="TradeMaker.pl" -#use wml::debian::translation-check translation="edd506dd6e078156e9465754257df078880a0a3e" maintainer="galaxico" - -<p> -I offer networks design, implementation and administration, -virtualization and network solutions. -</p> diff --git a/greek/consultants/tribe29.wml b/greek/consultants/tribe29.wml deleted file mode 100644 index 441a2cea706..00000000000 --- a/greek/consultants/tribe29.wml +++ /dev/null @@ -1,7 +0,0 @@ -#use wml::debian::consultant name="tribe29 GmbH" -#use wml::debian::translation-check translation="46d5d9a72303c08e3c594ddf3d7910e1876e134a" maintainer="galaxico" - -<p> -large scale automated installation and software -distribution, experience in other high end projects -</p> diff --git a/greek/consultants/trustsec.wml b/greek/consultants/trustsec.wml deleted file mode 100644 index 2df0f9942c6..00000000000 --- a/greek/consultants/trustsec.wml +++ /dev/null @@ -1,11 +0,0 @@ -#use wml::debian::consultant name="trustsec IT solutions GmbH" -#use wml::debian::translation-check translation="02bb3ab210af6e5a828b06ac64246b5d067cc0cd" maintainer="galaxico" - -<p>trustsec is a Debian development partner and pays a Debian -developer to work on the S/390 port of Debian. -They also sponsored the free Debian CDs for LinuxTag -since 2001, both with money and work time.</p> - -<p>trustsec offers customer support, consulting and training for Debian -on the Intel PC architecture (i386), PowerPC and IBM zSeries (S/390) -and is specialized on network security and software development.</p> diff --git a/greek/consultants/tuxjob.wml b/greek/consultants/tuxjob.wml deleted file mode 100644 index fbea6df74da..00000000000 --- a/greek/consultants/tuxjob.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="TuxJob" -#use wml::debian::translation-check translation="defa84796e0b0f37164d73cc733ead8c76ba25cd" maintainer="galaxico" - -<p> -Consulting and training for Debian GNU/Linux workstations and desktops, especially in -GNOME environment. I give advices and recommandations for education (schools and academies) -and multimedia. -</p> diff --git a/greek/consultants/udyansh.wml b/greek/consultants/udyansh.wml deleted file mode 100644 index b98362ed296..00000000000 --- a/greek/consultants/udyansh.wml +++ /dev/null @@ -1,29 +0,0 @@ -#use wml::debian::consultant name="Udyansh" -#use wml::debian::translation-check translation="a2c7f6f764ff2f781aaeb7083fcf2dee5cbc7327" maintainer="galaxico" - -<p> -Udyansh provides consulting and training for Debian. Udyansh has more -than ten years of experience in setting up and maintaining of servers -running Debian. -</p><p> -We have done large installation of Debian (~3000 workstations + ~40 -servers) across India. -</p><p> -We have experience in implementing and supporting the following on Debian: -</p> - <ul> - <li>Database</li> - <li>DNS</li> - <li>Mail</li> - <li>NAS</li> - <li>Network Monitoring</li> - <li>PBX</li> - <li>Version Control</li> - <li>Virtualisation</li> - <li>Wiki</li> - </ul> -<p> -Please contact us at info(at)udyansh(dot)org. -</p><p> -<url http://www.udyansh.org> -</p> diff --git a/greek/consultants/ullrich-it-consult.wml b/greek/consultants/ullrich-it-consult.wml deleted file mode 100644 index 32a47dbe1c1..00000000000 --- a/greek/consultants/ullrich-it-consult.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Ullrich-IT-Consult" -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -For further information: please look at my homepage, send e-mail or phone -directly. -All solutions will be made exclusive with free software (according to GPL and -"Debian"-rules). -</p> diff --git a/greek/consultants/ultreia.wml b/greek/consultants/ultreia.wml deleted file mode 100644 index 8228e5f0ac1..00000000000 --- a/greek/consultants/ultreia.wml +++ /dev/null @@ -1,9 +0,0 @@ -#use wml::debian::consultant name="Ultreia Comunicaciones S.L." -#use wml::debian::translation-check translation="1dec5e3bbb4b0d98ac258ca55b7b0d4cf17dbbc3" maintainer="galaxico" - -<p> -Ultreia Comunicaciones is an engineering consultant devoted to the -development of Linux and other unices based projects. We do work with -Linux since 1995. Currently we are specialized in security and services -management. -</p> diff --git a/greek/consultants/uws-software-service.wml b/greek/consultants/uws-software-service.wml deleted file mode 100644 index 91965cfd649..00000000000 --- a/greek/consultants/uws-software-service.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="UWS Software Service Ltd." -#use wml::debian::translation-check translation="417c81e92bdb2fbc074ca39ba9893124b510ec27" maintainer="galaxico" - -<p> -Software Development Company, Debian Experts. -</p> diff --git a/greek/consultants/uxware.wml b/greek/consultants/uxware.wml deleted file mode 100644 index dc50683143e..00000000000 --- a/greek/consultants/uxware.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="UXWARE" -#use wml::debian::translation-check translation="d51bbdbd1f062101c6dcab27a9698c508cd9780f" maintainer="galaxico" - -<p> -We are used to working in English. -</p> diff --git a/greek/consultants/welters.wml b/greek/consultants/welters.wml deleted file mode 100644 index d850a53a839..00000000000 --- a/greek/consultants/welters.wml +++ /dev/null @@ -1,8 +0,0 @@ -#use wml::debian::consultant name="Welters Datentechnik" -#use wml::debian::translation-check translation="f59b4a8ee6b405533c03a820fd8ca309f5650f8a" maintainer="galaxico" - -<p> -Debian Linux as M$ Replacement. -Exim, Sendmail, Samba, DHCP, Bind, MySQL installation and operation, -small to medium networks, hosting and support. -</p> diff --git a/greek/consultants/xpile.wml b/greek/consultants/xpile.wml deleted file mode 100644 index e8b9551959b..00000000000 --- a/greek/consultants/xpile.wml +++ /dev/null @@ -1,16 +0,0 @@ -#use wml::debian::consultant name="Xpile Software Entwicklung" -#use wml::debian::translation-check translation="859e9d10a9b2d29d8f591dbb85811e506cb5c9e2" original="german" -#use wml::debian::translation-check translation="c0816ff3dae7deb1cd48fb2f83fa934f5e5f3559" maintainer="galaxico" - -<p> -Xpile Software Entwicklung provides support in the following areas: -</p> - -<ul> - <li>Consulting and project management</li> - <li>Software and release Management</li> - <li>System- and application programming</li> - <li>Development of web applications</li> - <li>Configuration and administration of unix servers</li> - <li>Network and firewall configuration</li> -</ul> diff --git a/greek/consultants/xuni_tech.wml b/greek/consultants/xuni_tech.wml deleted file mode 100644 index a13a27d1171..00000000000 --- a/greek/consultants/xuni_tech.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::consultant name="Xuni Technology" -#use wml::debian::translation-check translation="b89ae8236bbd0aecaf132f56653a9b2a031b3d5a" maintainer="galaxico" - -<p> -We are working mainly in the northern part of Italy. Visit our site for more informations. -</p> diff --git a/greek/derivatives/Makefile b/greek/derivatives/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/derivatives/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/derivatives/index.wml b/greek/derivatives/index.wml deleted file mode 100644 index 93b41aba5e1..00000000000 --- a/greek/derivatives/index.wml +++ /dev/null @@ -1,182 +0,0 @@ -#use wml::debian::template title="Debian derivatives" -#use wml::debian::translation-check translation="1b62dcf348569f7b3d0975c674a776e714dc31fc" maintainer="galaxico" - -<p> -There are a <a href="#list">number of distributions</a> based on Debian. -Some people might want to take a look at these distributions <em>in addition to</em> the official Debian releases. -</p> - -<p> -A Debian derivative is a distribution that -is based on the work done in Debian but -has its own identity, goals and audience and -is created by an entity that is independent from Debian. -Derivatives modify Debian to achieve the goals they set for themselves. -</p> - -<p> -Debian welcomes and encourages organisations that want to develop new distributions based on Debian. -In the spirit of Debian's <a href="$(HOME)/social_contract">social contract</a>, -we hope derivatives will contribute their work to Debian and upstream projects, -so that everyone can benefit from their improvements. -</p> - -<h2 id="list">Which derivatives are available?</h2> - -<p> -We would like to highlight the following Debian derivatives: -</p> - -## Please keep this list sorted alphabetically -## Please only add derivatives that meet the criteria below -<ul> - <li> - <a href="https://grml.org/">Grml</a>: - live system for system administrators. - <a href="https://wiki.debian.org/Derivatives/Census/Grml">More info</a>. - </li> - <li> - <a href="https://www.kali.org/">Kali Linux</a>: - security auditing and penetration testing. - <a href="https://wiki.debian.org/Derivatives/Census/Kali">More info</a>. - </li> - <li> - <a href="https://pureos.net/">Purism PureOS</a>: - <a href="https://www.fsf.org/news/fsf-adds-pureos-to-list-of-endorsed-gnu-linux-distributions-1">FSF-endorsed</a> - rolling release, focused on privacy, security and convenience. - <a href="https://wiki.debian.org/Derivatives/Census/Purism">More info</a>. - </li> - <li> - <a href="https://tails.boum.org/">Tails</a>: - preserve privacy and anonymity. - <a href="https://wiki.debian.org/Derivatives/Census/Tails">More info</a>. - </li> - <li> - <a href="https://www.ubuntu.com/">Ubuntu</a>: - popularising Linux around the world. - <a href="https://wiki.debian.org/Derivatives/Census/Ubuntu">More info</a>. - </li> -</ul> - -<p> -In addition, distributions based on Debian are listed in the -<a href="https://wiki.debian.org/Derivatives/Census">Debian derivatives census</a> -as well as in <a href="https://wiki.debian.org/Derivatives#Lists">other places</a>. -</p> - -<h2>Why use a derivative instead of Debian?</h2> - -<p> -If you have a specific need which is better served by a derivative, -you might prefer using it instead of Debian. -</p> - -<p> -If you are part of a specific community or group of people and -there is a derivative for that group of people, -you might prefer using it instead of Debian. -</p> - -<h2>Why is Debian interested in derivatives?</h2> - -<p> -Derivatives bring Debian to a larger number of people with more diverse -experiences and requirements than the audience we currently reach. -By developing relationships with derivatives, -<a href="https://wiki.debian.org/Derivatives/Integration">integrating</a> -information about them into Debian infrastructure and -merging changes they have made back into Debian, we -share our experience with our derivatives, -expand our understanding of our derivatives and their audiences, -potentially expand the Debian community, -improve Debian for our existing audience and -make Debian suitable for a more diverse audience. -</p> - -<h2>Which derivatives will Debian highlight?</h2> - -## Examples of these criteria are in the accompanying README.txt -<p> -The derivatives highlighted above have each met most of these criteria: -</p> - -<ul> - <li>actively cooperate with Debian</li> - <li>are actively maintained</li> - <li>have a team of people involved, including at least one Debian member</li> - <li>have joined the Debian derivatives census and included a sources.list in their census page</li> - <li>have a distinguishing feature or focus</li> - <li>are notable and established distributions</li> -</ul> - -<h2>Why derive from Debian?</h2> - -<p> -It can be faster to modify an existing distribution like Debian than starting from scratch since -a packaging format, repositories, base packages and other things are specified and usable. -A lot of software is packaged so there is no need to spend time packaging most things. -This allows derivatives to focus on the needs of a specific audience. -</p> - -<p> -Debian ensures that what we distribute is <a href="$(HOME)/intro/free">free</a> -for derivatives to modify and redistribute to their audience. -We do this by checking the licenses of software we distribute -against the <a href="$(HOME)/social_contract#guidelines">Debian Free Software Guidelines (DFSG)</a>. -</p> - -<p> -Debian has a number of different <a href="$(HOME)/releases/">release</a> cycles -available for derivatives to base their distribution on. -This allows derivatives to -try <a href="https://wiki.debian.org/DebianExperimental">experimental</a> software, -move really <a href="$(HOME)/releases/unstable/">fast</a>, -update <a href="$(HOME)/releases/testing/">often</a> with quality assurance, -have a <a href="$(HOME)/releases/stable/">solid base</a> for their work, -use <a href="https://backports.debian.org/">newer</a> -software on top of a solid base, -enjoy <a href="$(HOME)/security/">security</a> support and -<a href="https://wiki.debian.org/LTS">extend</a> that support. -</p> - -<p> -Debian supports a number of different <a href="$(HOME)/ports/">architectures</a> -and contributors are <a href="https://wiki.debian.org/DebianBootstrap">working</a> -on methods of automatically creating new ones for new processor types. -This allows derivatives to use the hardware of their choice -or to support new processor designs. -</p> - -<p> -The Debian community and people from existing derivatives are available -and willing to help guide new distributions in their work. -</p> - -<p> -Derivatives are created for a number of reasons, such as -translation to new languages, -specific hardware support, -different installation mechanisms or -supporting a particular community or group of people. -</p> - -<h2>How to derive from Debian?</h2> - -<p> -Derivatives can use parts of Debian's infrastructure if needed (like repositories). -Derivatives should change references to Debian (like the logo, name, etc.) -and to Debian services (like the website and BTS). -</p> - -<p> -If the goal is to define a set of packages to install, -creating a <a href="$(HOME)/blends/">Debian blend</a> -could be an interesting way to do that within Debian. -</p> - -<p> -Detailed development information is available in the -<a href="https://wiki.debian.org/Derivatives/Guidelines">guidelines</a> and -guidance is available from the -<a href="https://wiki.debian.org/DerivativesFrontDesk">front desk</a>. -</p> diff --git a/greek/devel/buildd/Makefile b/greek/devel/buildd/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/devel/buildd/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/devel/buildd/index.wml b/greek/devel/buildd/index.wml deleted file mode 100644 index 2bcfd527d3c..00000000000 --- a/greek/devel/buildd/index.wml +++ /dev/null @@ -1,168 +0,0 @@ -#use wml::debian::template title="Autobuilder network" -#use wml::debian::translation-check translation="63e5091d45458638e03a89dee1560f547b0cf0fc" maintainer="galaxico" - -<p>The autobuilder network is a Debian development that manages -package compilations for all the architectures <a -href="$(HOME)/ports/">Debian currently supports</a>. This -network is made up of several machines that use a specific software -package called <em>buildd</em> to pick up packages from the Debian -archive and rebuild them for the target architecture.</p> - -<h2>Why is the autobuilder network needed?</h2> - -<p>The Debian distribution supports <a href="$(HOME)/ports/">quite a -few architectures</a>, but the package maintainers usually only -compile binary versions for a single architecture they have access to -(usually i386 or amd64). The other builds are produced automatically, -ensuring that every package is only built once. Failures are tracked -in the autobuilder database.</p> - -<p> -As Debian/m68k (the first non-Intel port) started, developers for -it had to watch out for new versions of packages and recompile them -if they wanted to stay up-to-date with the Intel distribution. All -this was done manually: developers watched the upload mailing list for -new packages and took some of them for building. Coordination that no -package is built twice by different people was done by announcing on a -mailing list. It's obvious that this procedure is error-prone and -time-consuming. This was, however, the usual way for keeping non-i386 -distributions current for a long time. -</p> - -<p> -The build daemon system automates most of this process. It consists of -a set of scripts (written in Perl and Python) that have evolved over -time to help porters with various tasks. They have finally developed -into a system that is able to keep Debian distributions up-to-date nearly -automatically. The security updates are built on the same set of -machines to ensure their timely availability. -</p> - -<h2>How does buildd work?</h2> - -<p><em>Buildd</em> is the name usually given to the software used by the -autobuilder network, but it's really made of different parts:</p> - -<dl> - -<dt>wanna-build</dt> -<dd> -a tool that helps coordinate package (re)building through a database -that keeps a list of packages and their status. There is one central -database per architecture that stores package states, versions, and -some other information. It's fed with Sources and Packages files -retrieved from the various package archives Debian has (e.g. -ftp-master and security-master). -</dd> - -<dt><a href="https://packages.debian.org/buildd">buildd</a></dt> -<dd> -a daemon that periodically checks the database maintained by -<em>wanna-build</em> and calls <em>sbuild</em> to build the packages. -After the build log was acknowledged by the buildd administrator it -uploads the package to the appropriate archive. -</dd> - -<dt><a href="https://packages.debian.org/sbuild">sbuild</a></dt> -<dd> -is responsible for the actual compilation of packages in isolated chroots. -It ensured that all needed source dependencies are installed into the -chroot before building and then calls standard Debian tools to start -the build process. Build logs are submitted to the -<a href="https://buildd.debian.org">build log database</a>. -</dd> - -</dl> - -<p>All these parts <a href="operation">operate</a> -together in order to make the builder network work.</p> - -<h2>What does a Debian developer need to do?</h2> - -<p>Actually, an average Debian developer does not need to explicitly use -the buildd network. Whenever he uploads a package to the archive -(binary compiled to a given architecture) it will be added to the database -for all architectures (in state <em>Needs-Build</em>). -Build machines will query the build database for packages in this state, -and will routinely take packages from that list. The list -is prioritized by previous compilation state (either <em>out-of-date</em> -or <em>uncompiled</em>), priority, section and package name. Furthermore, -to prevent some packages from starving at the end of the queue, the priorities -are dynamically adjusted with increasing waiting time in the queue.</p> - -<p>If the build succeeds in all architectures, the maintainer will not -need to do anything. All those binary packages will be uploaded to the -corresponding archive. If the build does not succeed the package will -enter special states (<em>Build-Attempted</em> for build failures that -were not reviewed, <em>Failed</em> for reviewed and reported bugs in -the package or <em>Dep-Wait</em>, if they depend on specific build -dependencies which are not available). -The autobuilder administrators will review packages which fail to build -and will report back to the maintainer, usually, opening up a bug in the -Bug Tracking System.</p> - -<p>Sometimes a package takes a long time to build for a given architecture -and that holds the package from entering <a href="$(HOME)/devel/testing">\ -testing</a>. If a package holds up a transition build priorities are -usually adjusted upon request by the Release Team. Other requests will -not be accepted as the increased waiting time in the queue will lead to -a higher build priority automatically.</p> - -<p>You can check that status of the different buildds attempt -of the packages that belong to any given maintainer by checking the -<a href="https://buildd.debian.org/status/">buildd logs</a>. -These logs are also linked from the Packages' Maintainer Overview.</p> - -<p>For more information on the different states a package can be -please read <a href="wanna-build-states">wanna-build-states</a>.</p> - -<h2>Where can I find additional information?</h2> - -<p>Of course, both the documentation and the source code available for these -different tools are the best way to find out how the buildd network -works. Additionally, the -<a href="$(HOME)/doc/manuals/developers-reference/pkgs.html#porting">\ -Porting and being ported</a> section of the -<a href="$(HOME)/doc/manuals/developers-reference/">Debian Developers -Reference</a> provides complementary information on how does it work and -it also provides some information on -<a href="$(HOME)/doc/manuals/developers-reference/tools.html#tools-builders">\ -package builders</a> and -<a href="$(HOME)/doc/manuals/developers-reference/tools.html#tools-porting">\ -porting tools</a> which are involved in the process of both setting -up and maintaining the buildd network.</p> - -<p>There are some statistics available for the autobuilder network at -<a href="https://buildd.debian.org/stats/">the buildd stats page</a>.</p> - -<h2>How can I setup my own auto-builder node?</h2> - -<p>There are several reasons why a developer (or user) -might want to setup and run an autobuilder:</p> - -<ul> -<li>To help in developing a port to a given architecture (when autobuilders -are needed).</li> -<li>To assess the impact of a given compiler optimisation or patch -by recompiling a large subset of packages.</li> -<li>To run tools that analyse packages for known mistakes and need to -be run in compiled packages. This is even needed when doing source -code analysis, for example, as a work-around for packages -using <tt>dpatch</tt>.</li> -</ul> - -<p>You can read more information on how you can -<a href="https://wiki.debian.org/BuilddSetup">setup an autobuilder</a>.</p> - -<h2>Contacting the buildd admins</h2> - -<p>The admins responsible for buildd's for a particular arch can be reached -at <email arch@buildd.debian.org>, for example <email -i386@buildd.debian.org>.</p> - -<hrline /> -<p><small>This introduction to the autobuilder network was written -with bits and pieces provided by Roman Hodek, -Christian T. Steigies, Wouter Verhelst, Andreas Barth, -Francesco Paolo Lovergine, Javier Fernández-Sanguino and -Philipp Kern.</small></p> diff --git a/greek/devel/buildd/operation.wml b/greek/devel/buildd/operation.wml deleted file mode 100644 index c0d9555026c..00000000000 --- a/greek/devel/buildd/operation.wml +++ /dev/null @@ -1,77 +0,0 @@ -#use wml::debian::template title="Outline of operation of the autobuilder network" BARETITLE="true" -#use wml::debian::translation-check translation="4094875c3a7aafc988b5f218b0a629fab415552a" maintainer="galaxico" - -<P> -At the heart of the system is the <TT>wanna-build</TT> database, which -keeps track of package versions and states. <TT>quinn-diff</TT> -compares the package lists for the target architecture against the list -of source packages after every archive update and feeds a list of packages -that need re-compilation into the database where they enter state -<TT>Needs-Build</TT>. - -<P> -All the build daemons (there can be more than one) query the database -regularly for such packages and take some of them so that they go -into state <TT>Building</TT>. Of course, humans also can take -packages, e.g. in special cases where automatic compilation isn't -possible. Here we also see the second purpose of <TT>wanna-build</TT>: -It ensures that the same version of a package won't be built twice. - -<DIV class="center"><A name="autobuilder34"></A> -<IMG SRC="scheme.png" alt="Autobuilder scheme"> -<p><STRONG>Figure:</STRONG> -Package States and Transitions</p> -</DIV> - -<P> -If everything goes well, a finished package can be uploaded later, -which is another state <TT>Uploaded</TT>. After that it will -eventually be installed into the Debian archive so it appears in the -updated package list for the target architecture. This list will be -merged into the database, so the package will go to state -<TT>Installed</TT> and remains there until the next version of the source package. - -<P> -There are several other states; they include: <TT>Failed</TT> is for -packages that failed to build due to errors in the sources, and the -errors are expected to be fixed in a successor version (after -reporting the problem, of course). So a new version will directly -enter <TT>Needs-Build</TT>, but with a warning that something was -wrong with the previous version. Along with this state an error -description is stored. State <TT>Dep-Wait</TT> is used when a package -needs some other packages to be compiled but those aren't available -yet and must be built before. This state stores a list of required -packages and maybe versions, and if all of them are known to be -installed the state changes back to <TT>Needs-Build</TT>. - -<P> -As we have already seen, the build daemon takes packages from the -database for compiling them. Let's look a bit closer: If it has some -packages to build, it uses <TT>sbuild</TT> for the actual compilation -process, and for each build a log is mailed to the maintainer of the -daemon. He reviews the log and decides what to do with the package: -upload it, set it to <TT>Failed</TT> or <TT>Dep-Wait</TT> and retry it, -etc... If a positive acknowledgement (a signed <TT>.changes</TT> -file) is received, the daemon moves it to an upload directory, from where -all packages are uploaded by a cron job. - -<P> -Looking at the log files is the only human intervention in the whole -process if no errors happen. There are two good reasons for not -further automating this: First, sometimes builds end with an ``OK'' -result but the build nevertheless failed for reasons that are -invisible to the machine. And second, directly uploading would require -to automatically PGP-sign the resulting files with a key without -passphrase on the build machine. I considered this an unacceptable -security hole. - -<P> -The build script <TT>sbuild</TT> more or less just calls some standard -Debian tools to compile the sources. It also helps with some common -tasks and bookkeeping and with automatically installing the -build-dependencies as requested by the package being built. - -<hrline /> -<p><small>Content developed by Roman Hodek for the -6th International Linux-Kongress 1999; it was gently updated to reflect -the current reality a bit more by Philipp Kern in 2009</small></p> diff --git a/greek/devel/buildd/wanna-build-states.wml b/greek/devel/buildd/wanna-build-states.wml deleted file mode 100644 index 15079d0f8b2..00000000000 --- a/greek/devel/buildd/wanna-build-states.wml +++ /dev/null @@ -1,304 +0,0 @@ -#use wml::debian::template title="Wanna-build states: an explanation" BARETITLE="true" -#use wml::debian::translation-check translation="b8114b588961778dbd04974c1464a2f388a90c28" maintainer="galaxico" - - <p>This page tries to explain what every wanna-build state means - and what will happen to a package when it's in that state. Its - target audience are Debian package maintainers that try to - understand why their package has, or has not, been built for a - specific architecture. Also, an explanation of the different log - results is given.</p> - - <p>Finally, a flowchart version of the wanna-build states is - <a href="#graphlink">available</a>, but do note that it doesn't talk - about everything mentioned in this document.</p> - -<h2>The wanna-build states</h2> -<p>For every Debian-supported architecture, there's a wanna-build -database installed on buildd.debian.org, with all packages and their current -compilation state. There are 8 states: <em>needs-build</em>, -<em>building</em>, <em>uploaded</em>, <em>dep-wait</em>, -<em>BD-Uninstallable</em>, <em>failed</em>, <em>not-for-us</em>, and -<em>installed</em>.</p> - -<p>Their meaning is as follows:</p> - <dl> - <dt><a name="needs-build">needs-build</a></dt> - <dd>A package marked <em>needs-build</em> has seen an upload of - a new version by its maintainer, but for a different - architecture than the one this wanna-build database is for; as - such, it needs a rebuild. If the state is - <em>needs-build</em>, it has not been picked up by an - autobuilder yet, but it will be (once one is available at a - time the specific package is near the top of the list). People - commonly say <q>a package is queued for rebuild</q> when they are - talking about a package in the <em>needs-build</em> state.<br /> - It may be interesting to note that the <em>needs-build</em> - queue is not a FIFO queue; rather, the ordering used is based - on the following criteria: - <ol> - <li>Packages' previous compilation states; packages that - have been built previously are given priority over new - packages. - </li> - <li>priorities (packages with <em>required</em> priority are - built before packages with <em>extra</em> priority) - </li> - <li>The section a package is in. This ordering is based on what - packages are deemed more important; e.g., section <em>games</em> is - built after section <em>base</em>, and section <em>libs</em> is - built before <em>devel</em>. - </li> - <li>an asciibetical ordering on the package name.</li> - </ol> - Additionally, under certain conditions, it may happen that a buildd - will not take packages at the head of the queue; for instance, - when a buildd can't find the source of a given package, it will - put it back in the queue (where it will then again be put at its - previous position, i.e. the head of the queue), but it will - ignore the package for a few hours. Another example where this - might happen is when an architecture has multiple autobuilders; - in that case, the architecture's porters may choose to build - larger packages on their faster autobuilders, and leave the - smaller ones for the slower machines in the pool. A buildd can - theoretically also explicitly request a different section ordering, - but that is not usually done.<br /> - There could be other situations where the queue order seems to - be ignored; but note that they are all exceptions. - </dd> - <dt><a name="building">building</a></dt> - <dd>A package is marked <em>building</em> from the moment an - autobuilder picks it from the top of the wanna-build queue - until the moment the autobuilder admin replies to the log. As - packages are not picked one by one, this means a package can - be (and usually is) marked <em>building</em> before the build has - actually started; however, as buildd builds packages in its - local queue on a FIFO basis, it should not take too long - anymore. Also, note that the state of a package is - <strong>not</strong> modified once the build is complete; only - when the autobuilder admin comes around to replying to the - logs.</dd> - <dt><a name="uploaded">uploaded</a></dt> - <dd>When a build attempt was successful, a build log is sent to - the autobuilder admin and to buildd.debian.org. The - autobuilder maintainer will then sign the .changes file which - is embedded in the build log, and send it to the - autobuilder. In reaction, the autobuilder will upload the - package and set its state to <em>uploaded</em>. As such, a - package in this state can be found in the incoming queue - (somewhere).<br /> - An autobuilder will not touch a package anymore once it's - state is <em>uploaded</em>, at least not until the next upload - or until a porter manually modifies the state of a package. - </dd> - <dt><a name="dep-wait">dep-wait</a></dt> - <dd>When a package fails due to missing build-time dependencies, - the autobuilder maintainer will send a mail to the - autobuilder, instructing it to remove the package sources and - to mark the package as <em>dep-wait</em> on the missing - build-dependencies. A package in such a state will - automatically, without human intervention, be marked - needs-build once said dependencies are available.<br /> - Originally, a package had to see a build attempt before the - maintainer would manually place it in the <em>dep-wait</em> - state. However, in august 2005 some code was added to - wanna-build which will make a package move from the <em><a - href='#installed'>installed</a></em> state directly to the - <em>dep-wait</em> state, if that is appropriate.<br /> - There are two specific cases in which it may happen that a - package is marked dep-wait forever; these are when a typing - error happened by specifying the <em>dep-wait</em> dependencies - (so that the package is marked dep-wait on a package that does - not and will not ever exist) and when a build-time dependency is - declared on a package which is marked <em>not-for-us</em>, or - which is in the <em>packages-arch-specific</em> list.<br /> - As an example to the latter, consider three packages: a package - <tt>foo</tt>, which exists for <tt>i386</tt> only; a package - <tt>bar</tt>, which exists for <tt>m68k</tt> only (and which roughly - performs the same function); and a package <tt>baz</tt>, which can be - built with one of <tt>foo</tt> or <tt>bar</tt>. Should the maintainer - of the <tt>baz</tt> package forget to add <tt>bar</tt> to the - Build-Depends, and should he or she add it when it is noticed that - <tt>baz</tt> is <em>dep-wait</em>ing on a non-existing <tt>foo</tt> for - <tt>m68k</tt>, then the <em>dep-wait</em> state for <tt>m68k</tt> will - have to be manually lifted by the <tt>m68k</tt> porters. - </dd> - <dt><a name="bd-uninstallable">BD-Uninstallable</a></dt> - <dd>During debconf9, <a - href='https://lists.debian.org/debian-wb-team/2009/07/msg00089.html'>Joachim - Breitner had the idea</a> of using edos-debcheck to verify - build-dependency installability of packages that would otherwise - go into state Needs-Build. At that point, wanna-build already - had the ability to check the immediate availability of - build-dependencies; but if a package couldn't be installed - because it build-depends on a which depends on b which depends - on c (>=1.2.3) and c is still at version 1.2.2, this would - not be detected, and the build would fail early because of - unavailable build-dependencies. Figuring those out was a manual - process for the buildd admin, and, usually, a lengthy one at - that. With the BD-Uninstallable patch, this is no longer a - problem. When your package is in BD-Uninstallable, it means one - of the build-dependencies is not installable (either - immediately, or because part of its dependency tree is not - available). Unfortunately, the BD-Uninstallable patch does not - provide information about which package, exactly, is missing; - please use edos-debcheck to find out. This problem will, - however, solve itself once the missing dependencies are indeed - available, and at that point your package will automatically - move to Needs-Build again. - </dd> - <dt><a name="wanna-build-state-failed">failed</a></dt> - <dd>If a build attempt failed, and the autobuilder maintainer - decides it is really a failure that should not be retried, a - package is marked as <em>failed</em>. A package will not leave - this state until a porter decides it should do so, or until a - new version is available. However, when a new version of a - package is available which was marked as <em>failed</em> in - the previous version, the autobuilder will ask its admin - whether or not the package should be retried; this is so that - packages which will obviously fail again will not waste buildd - time. Although failing a package before trying a build is - hardly ever the right thing to do, the option is available to - the autobuilder admin.<br /> - Note that a package will <strong>never</strong> be marked - <em>failed</em> without human intervention. - </dd> - <dt><a name="not-for-us">not-for-us</a></dt> - <dd>Certain specific packages are architecture-specific; for - instance, <tt>lilo</tt>, an i386 boot loader, should not be - rebuilt on alpha, m68k, or s390. However, <em>wanna-build</em> - does not look at the control file of a package when creating its - database; only at the packages' name and section, the previous - build state, and its priority. As such, by the first upload of - an architecture-specific package which should not be built on - other architectures, a build attempt is tried none the less (but - fails even before the build-time dependencies are downloaded - and/or installed)<br /> - Since autobuilders should not waste time trying to build - packages that aren't required for their architecture, there's - need for a way to list packages for which even an attempt to - build isn't required. The first solution to this problem was - <em>not-for-us</em>; however, as that is difficult to - maintain, <em>not-for-us</em> is deprecated nowadays; - autobuilder maintainers should use - <em>packages-arch-specific</em> instead, which is a list of - packages specific to one or more architectures instead of a - wanna-build state.<br /> - A package in <em>not-for-us</em> or - <em>packages-arch-specific</em> will <strong>not</strong> - leave this state automatically; if your package specifically - excluded a given architecture in its control file previously, - but now includes more architectures, it must be - <strong>manually</strong> requeued.<br /> - If you ever find yourself in the position that you have to ask - for this to happen, you can do so by asking the relevant buildd - maintainer. They can be reached at $arch@buildd.debian.org. - </dd> - <dt><a name="installed">installed</a></dt> - <dd>As the name suggests, a package marked <em>installed</em> is - compiled for the architecture the wanna-build database is - for. Before Woody was released, a package's state changed from - <em>uploaded</em> to <em>installed</em> after the daily katie - runs. With the implementation of <a - href="https://lists.debian.org/debian-devel-announce/2002/debian-devel-announce-200206/msg00002.html">Accepted-autobuild</a>, - however, this is no longer true; nowadays, a package goes - from state <em>uploaded</em> to <em>installed</em> when it is - accepted into the archive. This means that a package is - usually marked <em>installed</em> after 15 minutes, on - average. - </dd> - </dl> - <p>In addition to these eight states, <em>wanna-build</em> also - knows two -removed states, which are really corner cases. These - two states are <em>dep-wait-removed</em> and - <em>failed-removed</em>. They relate to their respective <q>plain</q> - state as follows: when a package in state <em>failed</em> or - <em>dep-wait</em> doesn't appear in a new Packages file which is - fed to <em>wanna-build</em> – when it appears it has been - removed – the information about that package isn't thrown - away, as it could be that the package not appearing in the - Packages file is just a temporary glitch, or that the package is - temporarily removed for some reason (but that it will - reappear in the archive, given time). Instead, in such a case, a - package is moved to a <em>-removed</em> state, so that the - information on why it failed or what it's waiting for can be - retained. Should the package reappear in a following Packages file - which is fed to wanna-build, it will then be moved from - <em>failed-removed</em> back to <em>failed</em>, or from - <em>dep-wait-removed</em> back to <em>dep-wait</em> before further - processing.</p> - <p> - It is not possible to access the wanna-build database directly; - this database is installed on ftp-master.debian.org, which is a - restricted host, and only autobuilders have an SSH key which - allows them to access the wanna-build database of their - architecture. This has been the case even before ftp-master was - restricted; As wanna-build does a database-level lock when - accessing, even reading, the data, you had to be in the right - group (wb-<arch>) to be able to directly access a - wanna-build database. - </p> - <p>That said, you can see what state a package is in by - going to <a href="https://buildd.debian.org/stats/">the buildd - stats page</a>, except if it is in state <em>installed</em> - (well, not unless you don't mind digging through the - multi-megabytes "<arch>-all.txt" files...). - </p> - <h2>The build log results</h2> - <p> - When a package is built by sbuild (the buildd component which - does the actual building), a log with the build result is sent, - by mail, to the autobuilder admin and to logs@buildd.debian.org - (so that it can end up at https://buildd.debian.org). The build - log result can be one of <em>successful</em>, <em>attempted</em> (previously - known as <em>failed</em>), - <em>given-back</em>, or <em>skipped</em>. Note that, at <a - href="https://buildd.debian.org/">the buildd log overview - page</a>, the prefix <em>maybe-</em> is added, because among - other things, the fact that a build can be marked - <em>failed</em> there for things that aren't <em>really</em> a - failure has caused confusion in the past (or, the other way around, - sometimes a package which apparently built successful is really broken - and needs to be rebuilt).</p> - <p>The meaning of - the log results is as follows:</p> - <dl> - <dt><a name="successful">successful</a></dt> - <dd>The build was successful. When the autobuilder maintainer - receives this log, he will extract the embedded - <code>.changes</code> file, sign it, and send it back to the - autobuilder, which will cause the package to be uploaded.</dd> - <dt><a name="failed">attempted</a> (previously: failed)</dt> - <dd>The build exited with a non-zero exit state, indicating it probably - failed. As there can be a number of reasons why a build fails, - enumerating all them would be tedious, so no attempt is done here. If a - package of yours is marked <em>(maybe-)failed</em>, you will want to - read the above, and check its current wanna-build state. - </dd> - <dt><a name="given-back">given-back</a></dt> - <dd>The build failed due to a temporary problem with the - autobuilder; examples include network problems, the - unavailability of the packages' source with the current - sources.list, low disk space, and others.<br /> - A package which is <em>given-back</em> is marked as - <em><a href="#needs-build">needs-build</a></em> again; as - such, it will be automatically picked up by a different - autobuilder once one is ready. - </dd> - <dt><a name="skipped">skipped</a></dt> - <dd>In the time between the package was picked by the/an - autobuilder and marked <em><a - href="#building">building</a></em> and the build attempt, a new - version for this package was uploaded, or a porter manually - modified the wanna-build state for another reason. When that is - done, a mail is sent to the autobuilder, which will mark the - package as not to be built; sbuild sees this, and will skip the - build (although a build log with this result is sent, describing - the fact that this happened). - </dd> - </dl> - -<h2><a name="graphlink">The graphical version</a></h2> -<p>To illustrate the above, we have also provided a <a -href="wanna-build.png">flowchart-version</a> of this procedure. Again, note -that it does not contain everything mentioned in this document. -</p> diff --git a/greek/devel/constitution.1.0.wml b/greek/devel/constitution.1.0.wml deleted file mode 100644 index 3c8adc00d0d..00000000000 --- a/greek/devel/constitution.1.0.wml +++ /dev/null @@ -1,901 +0,0 @@ -#use wml::debian::template title="Historical Debian Constitution v 1.0" BARETITLE="true" -#use wml::debian::translation-check translation="ba01cfdc529712e3626bdf15fd37d39e94126794" maintainer="galaxico" - -<h1>Historical version of the Constitution for the Debian Project (v1.0)</h1> - -<p>Version 1.0 ratified on December 2nd, 1998. Superseded by -<a href="constitution.1.1">Version 1.1</a> ratified on June 21st, -2003, which is itself superseded by <a href="constitution.1.2">version 1.2</a>, -ratified on October 29th, 2003. Version 1.2 was again superseded by -<a href="constitution.1.3">version 1.3</a> ratified on September 24th, 2006. -Version 1.3 was again superseded by <a href="constitution.1.4">version 1.4</a> -ratified on October 7th, 2007. -That was superseded by the <a href="constitution.1.5">version 1.5</a> -ratified on January 9th, 2015, and again superseeded by the -<a href="constitution.1.6">version 1.6</a>, ratified on December 13th, 2015. -That was superseeded by the <a href="constitution">current version 1.7</a>, -ratified on August 14th, 2016. -</p> - - -<h2>1. Introduction</h2> - -<p><cite>The Debian Project is an association of individuals who have -made common cause to create a free operating system.</cite></p> - -<p>This document describes the organisational structure for formal -decision-making in the Project. It does not describe the goals of the -Project or how it achieves them, or contain any policies except those -directly related to the decision-making process.</p> - -<h2>2. Decision-making bodies and individuals</h2> - -<p>Each decision in the Project is made by one or more of the -following:</p> - -<ol> - <li>The Developers, by way of General Resolution or an election;</li> - - <li>The Project Leader;</li> - - <li>The Technical Committee and/or its Chairman;</li> - - <li>The individual Developer working on a particular task;</li> - - <li>Delegates appointed by the Project Leader for specific - tasks;</li> - - <li>The Project Secretary.</li> -</ol> - -<p>Most of the remainder of this document will outline the powers of -these bodies, their composition and appointment, and the procedure for -their decision-making. The powers of a person or body may be subject to -review and/or limitation by others; in this case the reviewing body or -person's entry will state this. <cite>In the list above, a person or -body is usually listed before any people or bodies whose decisions they -can overrule or who they (help) appoint - but not everyone listed -earlier can overrule everyone listed later.</cite></p> - -<h3>2.1. General rules</h3> - -<ol> - <li> - <p>Nothing in this constitution imposes an obligation on anyone to - do work for the Project. A person who does not want to do a task - which has been delegated or assigned to them does not need to do - it. However, they must not actively work against these rules and - decisions properly made under them.</p> - </li> - - <li> - <p>A person may hold several posts, except that the Project Leader, - Project Secretary and the Chairman of the Technical Committee must - be distinct, and that the Leader cannot appoint themselves as their - own Delegate.</p> - </li> - - <li> - <p>A person may leave the Project or resign from a particular post - they hold, at any time, by stating so publicly.</p> - </li> -</ol> - -<h2>3. Individual Developers</h2> - -<h3>3.1. Powers</h3> - -<p>An individual Developer may</p> - -<ol> - <li>make any technical or nontechnical decision with regard to their - own work;</li> - - <li>propose or sponsor draft General Resolutions;</li> - - <li>propose themselves as a Project Leader candidate in - elections;</li> - - <li>vote on General Resolutions and in Leadership elections.</li> -</ol> - -<h3>3.2. Composition and appointment</h3> - -<ol> - <li> - <p>Developers are volunteers who agree to further the aims of the - Project insofar as they participate in it, and who maintain - package(s) for the Project or do other work which the Project - Leader's Delegate(s) consider worthwhile.</p> - </li> - - <li> - <p>The Project Leader's Delegate(s) may choose not to admit new - Developers, or expel existing Developers. <cite>If the Developers - feel that the Delegates are abusing their authority they can of - course override the decision by way of General Resolution - see - §4.1(3), §4.2.</cite></p> - </li> -</ol> - -<h3>3.3. Procedure</h3> - -<p>Developers may make these decisions as they see fit.</p> - -<h2>4. The Developers by way of General Resolution or election</h2> - -<h3>4.1. Powers</h3> - -<p>Together, the Developers may:</p> - -<ol> - <li> - <p>Appoint or recall the Project Leader.</p> - </li> - - <li> - <p>Amend this constitution, provided they agree with a 3:1 - majority.</p> - </li> - - <li> - <p>Override any decision by the Project Leader or a Delegate.</p> - </li> - - <li> - <p>Override any decision by the Technical Committee, provided they - agree with a 2:1 majority.</p> - </li> - - <li> - <p>Issue nontechnical policy documents and statements.</p> - - <p>These include documents describing the goals of the project, - its relationship with other free software entities, and - nontechnical policies such as the free software licence terms that - Debian software must meet.</p> - - <p>They may also include position statements about issues of the - day.</p> - </li> - - <li> - <p>Together with the Project Leader and SPI, make decisions about - property held in trust for purposes related to Debian. (See - §9.1.)</p> - </li> -</ol> - -<h3>4.2. Procedure</h3> - -<ol> - <li> - <p>The Developers follow the Standard Resolution Procedure, below. - A resolution or amendment is introduced if proposed by any - Developer and sponsored by at least K other Developers, or if - proposed by the Project Leader or the Technical Committee.</p> - </li> - - <li> - <p>Delaying a decision by the Project Leader or their Delegate:</p> - - <ol> - <li>If the Project Leader or their Delegate, or the Technical - Committee, has made a decision, then Developers can override them - by passing a resolution to do so; see §4.1(3).</li> - - <li>If such a resolution is sponsored by at least 2K Developers, - or if it is proposed by the Technical Committee, the resolution - puts the decision immediately on hold (provided that resolution - itself says so).</li> - - <li>If the original decision was to change a discussion period or - a voting period, or the resolution is to override the Technical - Committee, then only K Developers need to sponsor the resolution - to be able to put the decision immediately on hold.</li> - - <li>If the decision is put on hold, an immediate vote is held to - determine whether the decision will stand until the full vote on - the decision is made or whether the implementation of the - original decision will be delayed until then. There is no - quorum for this immediate procedural vote.</li> - - <li>If the Project Leader (or the Delegate) withdraws the - original decision, the vote becomes moot, and is no longer - conducted.</li> - </ol> - </li> - - <li> - <p>Votes are taken by the Project Secretary. Votes and tallies - results are not be revealed during the voting period; after the - vote the Project Secretary lists all the votes cast. The voting - period is 2 weeks, but may be varied by up to 1 week by the Project - Leader, and may be ended by the Project Secretary when the outcome - of a vote is no longer in doubt.</p> - </li> - - <li> - <p>The minimum discussion period is 2 weeks, but may be varied by - up to 1 week by the Project Leader. The Project Leader has a - casting vote. There is a quorum of 3Q.</p> - </li> - - <li> - <p>Proposals, sponsors, amendments, calls for votes and other - formal actions are made by announcement on a publicly-readable - electronic mailing list designated by the Project Leader's - Delegate(s); any Developer may post there.</p> - </li> - - <li> - <p>Votes are cast by email in a manner suitable to the Secretary. - The Secretary determines for each poll whether voters can change - their votes.</p> - </li> - - <li> - <p>Q is half of the square root of the number of current - Developers. K is Q or 5, whichever is the smaller. Q and K need not - be integers and are not rounded.</p> - </li> -</ol> - -<h2>5. Project Leader</h2> - -<h3>5.1. Powers</h3> - -<p>The <a href="leader">Project Leader</a> may:</p> - -<ol> - <li> - <p>Appoint Delegates or delegate decisions to the Technical - Committee.</p> - - <p>The Leader may define an area of ongoing responsibility or a - specific decision and hand it over to another Developer or to the - Technical Committee.</p> - - <p>Once a particular decision has been delegated and made the - Project Leader may not withdraw that delegation; however, they may - withdraw an ongoing delegation of particular area of - responsibility.</p> - </li> - - <li> - <p>Lend authority to other Developers.</p> - - <p>The Project Leader may make statements of support for points of - view or for other members of the project, when asked or otherwise; - these statements have force if and only if the Leader would be - empowered to make the decision in question.</p> - </li> - - <li> - <p>Make any decision which requires urgent action.</p> - - <p>This does not apply to decisions which have only become - gradually urgent through lack of relevant action, unless there is a - fixed deadline.</p> - </li> - - <li> - <p>Make any decision for whom noone else has responsibility.</p> - </li> - - <li> - <p>Propose draft General Resolutions and amendments.</p> - </li> - - <li> - <p>Together with the Technical Committee, appoint new members to - the Committee. (See §6.2.)</p> - </li> - - <li> - <p>Use a casting vote when Developers vote.</p> - - <p>The Project Leader also has a normal vote in such ballots.</p> - </li> - - <li> - <p>Vary the discussion period for Developers' votes (as above).</p> - </li> - - <li> - <p>Lead discussions amongst Developers.</p> - - <p>The Project Leader should attempt to participate in discussions - amongst the Developers in a helpful way which seeks to bring the - discussion to bear on the key issues at hand. The Project Leader - should not use the Leadership position to promote their own - personal views.</p> - </li> - - <li> - <p>Together with SPI, make decisions affecting property held in - trust for purposes related to Debian. (See §9.1.)</p> - </li> -</ol> - -<h3>5.2. Appointment</h3> - -<ol> - <li>The Project Leader is elected by the Developers.</li> - - <li>The election begins nine weeks before the leadership post becomes - vacant, or (if it is too late already) immediately.</li> - - <li>For the following three weeks any Developer may nominate - themselves as a candidate Project Leader.</li> - - <li>For three weeks after that no more candidates may be nominated; - candidates should use this time for campaigning (to make their - identities and positions known). If there are no candidates at the - end of the nomination period then the nomination period is extended - for three further weeks, repeatedly if necessary.</li> - - <li>The next three weeks are the polling period during which - Developers may cast their votes. Votes in leadership elections are - kept secret, even after the election is finished.</li> - - <li>The options on the ballot will be those candidates who have - nominated themselves and have not yet withdrawn, plus None Of The - Above. If None Of The Above wins the election then the election - procedure is repeated, many times if necessary.</li> - - <li>The decision will be made using Concorde Vote Counting. The - quorum is the same as for a General Resolution (§4.2) and the - default option is None Of The Above.</li> - - <li>The Project Leader serves for one year from their election.</li> -</ol> - -<h3>5.3. Procedure</h3> - -<p>The Project Leader should attempt to make decisions which are -consistent with the consensus of the opinions of the Developers.</p> - -<p>Where practical the Project Leader should informally solicit the -views of the Developers.</p> - -<p>The Project Leader should avoid overemphasizing their own point of -view when making decisions in their capacity as Leader.</p> - -<h2>6. Technical committee</h2> - -<h3>6.1. Powers</h3> - -<p>The <a href="tech-ctte">Technical Committee</a> may:</p> - -<ol> - <li> - <p>Decide on any matter of technical policy.</p> - - <p>This includes the contents of the technical policy manuals, - developers' reference materials, example packages and the behaviour - of non-experimental package building tools. (In each case the usual - maintainer of the relevant software or documentation makes - decisions initially, however; see 6.3(5).)</p> - </li> - - <li> - <p>Decide any technical matter where Developers' jurisdictions - overlap.</p> - - <p>In cases where Developers need to implement compatible - technical policies or stances (for example, if they disagree about - the priorities of conflicting packages, or about ownership of a - command name, or about which package is responsible for a bug that - both maintainers agree is a bug, or about who should be the - maintainer for a package) the technical committee may decide the - matter.</p> - </li> - - <li> - <p>Make a decision when asked to do so.</p> - - <p>Any person or body may delegate a decision of their own to the - Technical Committee, or seek advice from it.</p> - </li> - - <li> - <p>Overrule a Developer (requires a 3:1 majority).</p> - - <p>The Technical Committee may ask a Developer to take a - particular technical course of action even if the Developer does - not wish to; this requires a 3:1 majority. For example, the - Committee may determine that a complaint made by the submitter of a - bug is justified and that the submitter's proposed solution should - be implemented.</p> - </li> - - <li> - <p>Offer advice.</p> - - <p>The Technical Committee may make formal announcements about its - views on any matter. <cite>Individual members may of course make - informal statements about their views and about the likely views of - the committee.</cite></p> - </li> - - <li> - <p>Together with the Project Leader, appoint new members to itself - or remove existing members. (See §6.2.)</p> - </li> - - <li> - <p>Appoint the Chairman of the Technical Committee.</p> - - <p>The Chairman is elected by the Committee from its members. All - members of the committee are automatically nominated; the committee - vote starting one week before the post will become vacant (or - immediately, if it is already too late). The members may vote by - public acclamation for any fellow committee member, including - themselves; there is no None Of The Above option. The vote finishes - when all the members have voted or when the outcome is no longer in - doubt. The result is determined according to Concorde Vote - Counting.</p> - </li> - - <li> - <p>The Chairman can stand in for the Leader, together with the - Secretary</p> - - <p>As detailed in §7.1(2), the Chairman of the Technical - Committee and the Project Secretary may together stand in for the - Leader if there is no Leader.</p> - </li> -</ol> - -<h3>6.2. Composition</h3> - -<ol> - <li> - <p>The Technical Committee consists of up to 8 Developers, and - should usually have at least 4 members.</p> - </li> - - <li> - <p>When there are fewer than 8 members the Technical Committee may - recommend new member(s) to the Project Leader, who may choose - (individually) to appoint them or not.</p> - </li> - - <li> - <p>When there are 5 members or fewer the Technical Committee may - appoint new member(s) until the number of members reaches 6.</p> - </li> - - <li> - <p>When there have been 5 members or fewer for at least one week - the Project Leader may appoint new member(s) until the number of - members reaches 6, at intervals of at least one week per - appointment.</p> - </li> - - <li> - <p>If the Technical Committee and the Project Leader agree they - may remove or replace an existing member of the Technical - Committee.</p> - </li> -</ol> - -<h3>6.3. Procedure</h3> - -<ol> - <li> - <p>The Technical Committee uses the Standard Resolution - Procedure.</p> - - <p>A draft resolution or amendment may be proposed by any member - of the Technical Committee. There is no minimum discussion period; - the voting period lasts for up to one week, or until the outcome is - no longer in doubt. Members may change their votes. There is a - quorum of two.</p> - </li> - - <li> - <p>Details regarding voting</p> - - <p>The Chairman has a casting vote. When the Technical Committee - votes whether to override a Developer who also happens to be a - member of the Committee, that member may not vote (unless they are - the Chairman, in which case they may use only their casting - vote).</p> - </li> - - <li> - <p>Public discussion and decision-making.</p> - - <p>Discussion, draft resolutions and amendments, and votes by - members of the committee, are made public on the Technical - Committee public discussion list. There is no separate secretary - for the Committee.</p> - </li> - - <li> - <p>Confidentiality of appointments.</p> - - <p>The Technical Committee may hold confidential discussions via - private email or a private mailing list or other means to discuss - appointments to the Committee. However, votes on appointments must - be public.</p> - </li> - - <li> - <p>No detailed design work.</p> - - <p>The Technical Committee does not engage in design of new - proposals and policies. Such design work should be carried out by - individuals privately or together and discussed in ordinary - technical policy and design forums.</p> - - <p>The Technical Committee restricts itself to choosing from or - adopting compromises between solutions and decisions which have - been proposed and reasonably thoroughly discussed elsewhere.</p> - - <p><cite>Individual members of the technical committee may of - course participate on their own behalf in any aspect of design and - policy work.</cite></p> - </li> - - <li> - <p>Technical Committee makes decisions only as last resort.</p> - - <p>The Technical Committee does not make a technical decision - until efforts to resolve it via consensus have been tried and - failed, unless it has been asked to make a decision by the person - or body who would normally be responsible for it.</p> - </li> -</ol> - -<h2>7. The Project Secretary</h2> - -<h3>7.1. Powers</h3> - -<p>The <a href="secretary">Secretary</a>:</p> - -<ol> - <li> - <p>Takes votes amongst the Developers, and determines the number - and identity of Developers, whenever this is required by the - constitution.</p> - </li> - - <li> - <p>Can stand in for the Leader, together with the Chairman of the - Technical Committee.</p> - - <p>If there is no Project Leader then the Chairman of the - Technical Committee and the Project Secretary may by joint - agreement make decisions if they consider it imperative to do - so.</p> - </li> - - <li> - <p>Adjudicates any disputes about interpretation of the - constitution.</p> - </li> - - <li> - <p>May delegate part or all of their authority to someone else, or - withdraw such a delegation at any time.</p> - </li> -</ol> - -<h3>7.2. Appointment</h3> - -<p>The Project Secretary is appointed by the Project Leader and the -current Project Secretary.</p> - -<p>If the Project Leader and the current Project Secretary cannot -agree on a new appointment they must ask the board of SPI (see §9.1.) -to appoint a Secretary.</p> - -<p>If there is no Project Secretary or the current Secretary is -unavailable and has not delegated authority for a decision then the -decision may be made or delegated by the Chairman of the Technical -Committee, as Acting Secretary.</p> - -<p>The Project Secretary's term of office is 1 year, at which point -they or another Secretary must be (re)appointed.</p> - -<h3>7.3. Procedure</h3> - -<p>The Project Secretary should make decisions which are fair and -reasonable, and preferably consistent with the consensus of the -Developers.</p> - -<p>When acting together to stand in for an absent Project Leader the -Chairman of the Technical Committee and the Project Secretary should -make decisions only when absolutely necessary and only when consistent -with the consensus of the Developers.</p> - -<h2>8. The Project Leader's Delegates</h2> - -<h3>8.1. Powers</h3> - -<p>The Project Leader's Delegates:</p> - -<ol> - <li>have powers delegated to them by the Project Leader;</li> - - <li>may make certain decisions which the Leader may not make - directly, including approving or expelling Developers or designating - people as Developers who do not maintain packages. <cite>This is to - avoid concentration of power, particularly over membership as a - Developer, in the hands of the Project Leader.</cite></li> -</ol> - -<h3>8.2. Appointment</h3> - -<p>The Delegates are appointed by the Project Leader and may be -replaced by the Leader at the Leader's discretion. The Project Leader -may not make the position as a Delegate conditional on particular -decisions by the Delegate, nor may they override a decision made by a -Delegate once made.</p> - -<h3>8.3. Procedure</h3> - -<p>Delegates may make decisions as they see fit, but should attempt to -implement good technical decisions and/or follow consensus opinion.</p> - -<h2>9. Software in the Public Interest</h2> - -<p><a href="https://www.spi-inc.org/">SPI</a> and Debian are separate -organisations who share some goals. Debian is grateful for the legal -support framework offered by SPI. <cite>Debian's Developers are -currently members of SPI by virtue of their status as -Developers.</cite></p> - -<h3>9.1. Authority</h3> - -<ol> - <li>SPI has no authority regarding Debian's technical or nontechnical - decisions, except that no decision by Debian with respect to any - property held by SPI shall require SPI to act outside its legal - authority, and that Debian's constitution may occasionally use SPI as - a decision body of last resort.</li> - - <li>Debian claims no authority over SPI other than that over the use - of certain of SPI's property, as described below, though Debian - Developers may be granted authority within SPI by SPI's rules.</li> - - <li>Debian Developers are not agents or employees of SPI, or of each - other or of persons in authority in the Debian Project. A person - acting as a Developer does so as an individual, on their own - behalf.</li> -</ol> - -<h3>9.2. Management of property for purposes related to Debian</h3> - -<p>Since Debian has no authority to hold money or property, any -donations for the Debian Project must be made to SPI, which manages such -affairs.</p> - -<p>SPI have made the following undertakings:</p> - -<ol> - <li>SPI will hold money, trademarks and other tangible and intangible - property and manage other affairs for purposes related to - Debian.</li> - - <li>Such property will be accounted for separately and held in trust - for those purposes, decided on by Debian and SPI according to this - section.</li> - - <li>SPI will not dispose of or use property held in trust for Debian - without approval from Debian, which may be granted by the Project - Leader or by General Resolution of the Developers.</li> - - <li>SPI will consider using or disposing of property held in trust - for Debian when asked to do so by the Project Leader.</li> - - <li>SPI will use or dispose of property held in trust for Debian when - asked to do so by a General Resolution of the Developers, provided - that this is compatible with SPI's legal authority.</li> - - <li>SPI will notify the Developers by electronic mail to a Debian - Project mailing list when it uses or disposes of property held in - trust for Debian.</li> -</ol> - -<h2>A. Standard Resolution Procedure</h2> - -<p>These rules apply to communal decision-making by committees and -plebiscites, where stated above.</p> - -<h3>A.1. Proposal</h3> - -<p>The formal procedure begins when a draft resolution is proposed and -sponsored, as required.</p> - -<h3>A.1. Discussion and Amendment</h3> - -<ol> - <li>Following the proposal, the resolution may be discussed. - Amendments may be made formal by being proposed and sponsored - according to the requirements for a new resolution, or directly by - the proposer of the original resolution.</li> - - <li>A formal amendment may be accepted by the resolution's proposer, - in which case the formal resolution draft is immediately changed to - match.</li> - - <li>If a formal amendment is not accepted, or one of the sponsors of - the resolution does not agree with the acceptance by the proposer of - a formal amendment, the amendment remains as an amendment and will be - voted on.</li> - - <li>If an amendment accepted by the original proposer is not to the - liking of others, they may propose another amendment to reverse the - earlier change (again, they must meet the requirements for proposer - and sponsor(s).)</li> - - <li>The proposer of a resolution may suggest changes to the wordings - of amendments; these take effect if the proposer of the amendment - agrees and none of the sponsors object. In this case the changed - amendments will be voted on instead of the originals.</li> - - <li>The proposer of a resolution may make changes to correct minor - errors (for example, typographical errors or inconsistencies) or - changes which do not alter the meaning, providing noone objects - within 24 hours. In this case the minimum discussion period is not - restarted.</li> -</ol> - -<h3>A.2. Calling for a vote</h3> - -<ol> - <li>The proposer or a sponsor of a motion or an amendment may call - for a vote, providing that the minimum discussion period (if any) has - elapsed.</li> - - <li>The proposer or a sponsor of a motion may call for a vote on any - or all of the amendments individually or together; the proposer or - sponsor of an amendment may call for a vote only on that amendment - and related amendments.</li> - - <li>The person who calls for a vote states what they believe the - wordings of the resolution and any relevant amendments are, and - consequently what form the ballot should take. However, the final - decision on the form of ballot(s) is the Secretary's - see 7.1(1), - 7.1(3) and A.3(6).</li> - - <li>The minimum discussion period is counted from the time the last - formal amendment was accepted, or the last related formal amendment - was accepted if an amendment is being voted on, or since the whole - resolution was proposed if no amendments have been proposed and - accepted.</li> -</ol> - -<h3>A.3. Voting procedure</h3> - -<ol> - <li>Each independent set of related amendments is voted on in a - separate ballot. Each such ballot has as options all the sensible - combinations of amendments and options, and an option Further - Discussion. If Further Discussion wins then the entire resolution - procedure is set back to the start of the discussion period. No - quorum is required for an amendment.</li> - - <li>When the final form of the resolution has been determined it is - voted on in a final ballot, in which the options are Yes, No and - Further Discussion. If Further Discussion wins then the entire - procedure is set back to the start of the discussion period.</li> - - <li>The vote taker (if there is one) or the voters (if voting is done - by public pronouncement) may arrange for these ballots to be held - simultaneously, even (for example) using a single voting message. If - amendment ballot(s) and the final ballot are combined in this way - then it must be possible for a voter to vote differently in the final - ballot for each of the possible forms of the final draft - resolution.</li> - - <li>Votes may be cast during the voting period, as specified - elsewhere. If the voting period can end if the outcome is no longer - in doubt, the possibility that voters may change their votes is not - considered.</li> - - <li>The votes are counted according to the Concorde Vote Counting. If - a quorum is required then the default option is Further - Discussion.</li> - - <li>In cases of doubt the Project Secretary shall decide on matters - of procedure (for example, whether particular amendments should be - considered independent or not).</li> -</ol> - -<h3>A.4. Withdrawing resolutions or unaccepted amendments</h3> - -<p>The proposer of a resolution or unaccepted amendment may withdraw -it. In this case new proposers may come forward keep it alive, in which -case the first person to do so becomes the new proposer and any others -become sponsors if they aren't sponsors already.</p> - -<p>A sponsor of a resolution or amendment (unless it has been -accepted) may withdraw.</p> - -<p>If the withdrawal of the proposer and/or sponsors means that a -resolution has no proposer or not enough sponsors it will not be voted -on unless this is rectified before the resolution expires.</p> - -<h3>A.5. Expiry</h3> - -<p>If a proposed resolution has not been discussed, amended, voted on -or otherwise dealt with for 4 weeks then it is considered to have been -withdrawn.</p> - -<h3>A.6. Concorde Vote Counting</h3> - -<ol> - <li>This is used to determine the winner amongst a list of options. - Each ballot paper gives a ranking of the voter's preferred options. - (The ranking need not be complete.)</li> - - <li>Option A is said to Dominate option B if strictly more ballots - prefer A to B than prefer B to A.</li> - - <li>All options which are Dominated by at least one other option are - discarded, and references to them in ballot papers will be - ignored.</li> - - <li>If there is any option which Dominates all others then that is - the winner.</li> - - <li> - If there is now more than one option remaining Single Transferrable - Vote will be applied to choose amongst those remaining: - - <ul> - <li>The number of first preferences for each option is counted, - and if any option has more than half it is the winner.</li> - - <li>Otherwise the option with the lowest number of first - preferences is eliminated and its votes redistributed according - to the second preferences.</li> - - <li>This elimination procedure is repeated, moving down ballot - papers to 2nd, 3rd, 4th, etc. preferences as required, until one - option gets more than half of the <q>first</q> preferences.</li> - </ul> - </li> - - <li>In the case of ties the elector with a casting vote will decide. - The casting vote does not count as a normal vote; however that - elector will usually also get a normal vote.</li> - - <li>If a supermajority is required the number of Yes votes in the - final ballot is reduced by an appropriate factor. Strictly speaking, - for a supermajority of F:A, the number of ballots which prefer Yes to - X (when considering whether Yes Dominates X or X Dominates Yes) or - the number of ballots whose first (remaining) preference is Yes (when - doing STV comparisons for winner and elimination purposes) is - multiplied by a factor A/F before the comparison is done. <cite>This - means that a 2:1 vote, for example, means twice as many people voted - for as against; abstentions are not counted.</cite></li> - - <li>If a quorum is required, there must be at least that many votes - which prefer the winning option to the default option. If there are - not then the default option wins after all. For votes requiring a - supermajority, the actual number of Yes votes is used when checking - whether the quorum has been reached.</li> -</ol> - -<p><cite>When the Standard Resolution Procedure is to be used, the text -which refers to it must specify what is sufficient to have a draft -resolution proposed and/or sponsored, what the minimum discussion -period is, and what the voting period is. It must also specify any -supermajority and/or the quorum (and default option) to be -used.</cite></p> - -<h2>B. Use of language and typography</h2> - -<p>The present indicative (<q>is</q>, for example) means that the statement -is a rule in this constitution. <q>May</q> or <q>can</q> indicates that the -person or body has discretion. <q>Should</q> means that it would be -considered a good thing if the sentence were obeyed, but it is not -binding. <cite>Text marked as a citation, such as this, is rationale -and does not form part of the constitution. It may be used only to aid -interpretation in cases of doubt.</cite></p> diff --git a/greek/devel/constitution.1.1.wml b/greek/devel/constitution.1.1.wml deleted file mode 100644 index 4b6e35c6bff..00000000000 --- a/greek/devel/constitution.1.1.wml +++ /dev/null @@ -1,937 +0,0 @@ -#use wml::debian::template title="Historical Debian Constitution v 1.1" BARETITLE="true" -#use wml::debian::translation-check translation="ba01cfdc529712e3626bdf15fd37d39e94126794" maintainer="galaxico" - -<h1>Historical version of the Constitution for the Debian Project (v1.1)</h1> - -<p>Version 1.1 ratified on June 21st, 2003. Supersedes -<a href="constitution.1.0">Version 1.0</a> ratified on December 2nd, -1998. Superseded by <a href="constitution.1.2">version 1.2</a>, ratified on October -29th, 2003, which was again superseded by <a href="constitution.1.3">version 1.3</a> -ratified on September 24th, 2006. -Version 1.3 was again superseded by <a href="constitution.1.4">version 1.4</a> -ratified on October 7th, 2007. -That was superseded by the <a href="constitution.1.5">version 1.5</a> -ratified on January 9th, 2015, and again superseeded by the -<a href="constitution.1.6">version 1.6</a>, ratified on December 13th, 2015. -That was superseeded by the <a href="constitution">current version 1.7</a>, -ratified on August 14th, 2016. -</p> - - -<h2>1. Introduction</h2> - -<p><cite>The Debian Project is an association of individuals who have -made common cause to create a free operating system.</cite></p> - -<p>This document describes the organisational structure for formal -decision-making in the Project. It does not describe the goals of the -Project or how it achieves them, or contain any policies except those -directly related to the decision-making process.</p> - -<h2>2. Decision-making bodies and individuals</h2> - -<p>Each decision in the Project is made by one or more of the -following:</p> - -<ol> - <li>The Developers, by way of General Resolution or an election;</li> - - <li>The Project Leader;</li> - - <li>The Technical Committee and/or its Chairman;</li> - - <li>The individual Developer working on a particular task;</li> - - <li>Delegates appointed by the Project Leader for specific - tasks;</li> - - <li>The Project Secretary.</li> -</ol> - -<p>Most of the remainder of this document will outline the powers of -these bodies, their composition and appointment, and the procedure for -their decision-making. The powers of a person or body may be subject to -review and/or limitation by others; in this case the reviewing body or -person's entry will state this. <cite>In the list above, a person or -body is usually listed before any people or bodies whose decisions they -can overrule or who they (help) appoint - but not everyone listed -earlier can overrule everyone listed later.</cite></p> - -<h3>2.1. General rules</h3> - -<ol> - <li> - <p>Nothing in this constitution imposes an obligation on anyone to - do work for the Project. A person who does not want to do a task - which has been delegated or assigned to them does not need to do - it. However, they must not actively work against these rules and - decisions properly made under them.</p> - </li> - - <li> - <p>A person may hold several posts, except that the Project Leader, - Project Secretary and the Chairman of the Technical Committee must - be distinct, and that the Leader cannot appoint themselves as their - own Delegate.</p> - </li> - - <li> - <p>A person may leave the Project or resign from a particular post - they hold, at any time, by stating so publicly.</p> - </li> -</ol> - -<h2>3. Individual Developers</h2> - -<h3>3.1. Powers</h3> - -<p>An individual Developer may</p> - -<ol> - <li>make any technical or nontechnical decision with regard to their - own work;</li> - - <li>propose or sponsor draft General Resolutions;</li> - - <li>propose themselves as a Project Leader candidate in - elections;</li> - - <li>vote on General Resolutions and in Leadership elections.</li> -</ol> - -<h3>3.2. Composition and appointment</h3> - -<ol> - <li> - <p>Developers are volunteers who agree to further the aims of the - Project insofar as they participate in it, and who maintain - package(s) for the Project or do other work which the Project - Leader's Delegate(s) consider worthwhile.</p> - </li> - - <li> - <p>The Project Leader's Delegate(s) may choose not to admit new - Developers, or expel existing Developers. <cite>If the Developers - feel that the Delegates are abusing their authority they can of - course override the decision by way of General Resolution - see - §4.1(3), §4.2.</cite></p> - </li> -</ol> - -<h3>3.3. Procedure</h3> - -<p>Developers may make these decisions as they see fit.</p> - -<h2>4. The Developers by way of General Resolution or election</h2> - -<h3>4.1. Powers</h3> - -<p>Together, the Developers may:</p> - -<ol> - <li> - <p>Appoint or recall the Project Leader.</p> - </li> - - <li> - <p>Amend this constitution, provided they agree with a 3:1 - majority.</p> - </li> - - <li> - <p>Override any decision by the Project Leader or a Delegate.</p> - </li> - - <li> - <p>Override any decision by the Technical Committee, provided they - agree with a 2:1 majority.</p> - </li> - - <li> - <p>Issue nontechnical policy documents and statements.</p> - - <p>These include documents describing the goals of the project, - its relationship with other free software entities, and - nontechnical policies such as the free software licence terms that - Debian software must meet.</p> - - <p>They may also include position statements about issues of the - day.</p> - </li> - - <li> - <p>Together with the Project Leader and SPI, make decisions about - property held in trust for purposes related to Debian. (See - §9.1.)</p> - </li> -</ol> - -<h3>4.2. Procedure</h3> - -<ol> - <li> - <p>The Developers follow the Standard Resolution Procedure, below. - A resolution or amendment is introduced if proposed by any - Developer and sponsored by at least K other Developers, or if - proposed by the Project Leader or the Technical Committee.</p> - </li> - - <li> - <p>Delaying a decision by the Project Leader or their Delegate:</p> - - <ol> - <li>If the Project Leader or their Delegate, or the Technical - Committee, has made a decision, then Developers can override them - by passing a resolution to do so; see §4.1(3).</li> - - <li>If such a resolution is sponsored by at least 2K Developers, - or if it is proposed by the Technical Committee, the resolution - puts the decision immediately on hold (provided that resolution - itself says so).</li> - - <li>If the original decision was to change a discussion period or - a voting period, or the resolution is to override the Technical - Committee, then only K Developers need to sponsor the resolution - to be able to put the decision immediately on hold.</li> - - <li>If the decision is put on hold, an immediate vote is held to - determine whether the decision will stand until the full vote on - the decision is made or whether the implementation of the - original decision will be delayed until then. There is no - quorum for this immediate procedural vote.</li> - - <li>If the Project Leader (or the Delegate) withdraws the - original decision, the vote becomes moot, and is no longer - conducted.</li> - </ol> - </li> - - <li> - <p> - Votes are taken by the Project Secretary. Votes, tallies, and - results are not revealed during the voting period; after the - vote the Project Secretary lists all the votes cast. The voting - period is 2 weeks, but may be varied by up to 1 week by the - Project Leader. - </p> - </li> - - <li> - <p>The minimum discussion period is 2 weeks, but may be varied by - up to 1 week by the Project Leader. The Project Leader has a - casting vote. There is a quorum of 3Q.</p> - </li> - - <li> - <p>Proposals, sponsors, amendments, calls for votes and other - formal actions are made by announcement on a publicly-readable - electronic mailing list designated by the Project Leader's - Delegate(s); any Developer may post there.</p> - </li> - - <li> - <p>Votes are cast by email in a manner suitable to the Secretary. - The Secretary determines for each poll whether voters can change - their votes.</p> - </li> - - <li> - <p>Q is half of the square root of the number of current - Developers. K is Q or 5, whichever is the smaller. Q and K need not - be integers and are not rounded.</p> - </li> -</ol> - -<h2>5. Project Leader</h2> - -<h3>5.1. Powers</h3> - -<p>The <a href="leader">Project Leader</a> may:</p> - -<ol> - <li> - <p>Appoint Delegates or delegate decisions to the Technical - Committee.</p> - - <p>The Leader may define an area of ongoing responsibility or a - specific decision and hand it over to another Developer or to the - Technical Committee.</p> - - <p>Once a particular decision has been delegated and made the - Project Leader may not withdraw that delegation; however, they may - withdraw an ongoing delegation of particular area of - responsibility.</p> - </li> - - <li> - <p>Lend authority to other Developers.</p> - - <p>The Project Leader may make statements of support for points of - view or for other members of the project, when asked or otherwise; - these statements have force if and only if the Leader would be - empowered to make the decision in question.</p> - </li> - - <li> - <p>Make any decision which requires urgent action.</p> - - <p>This does not apply to decisions which have only become - gradually urgent through lack of relevant action, unless there is a - fixed deadline.</p> - </li> - - <li> - <p>Make any decision for whom noone else has responsibility.</p> - </li> - - <li> - <p>Propose draft General Resolutions and amendments.</p> - </li> - - <li> - <p>Together with the Technical Committee, appoint new members to - the Committee. (See §6.2.)</p> - </li> - - <li> - <p>Use a casting vote when Developers vote.</p> - - <p>The Project Leader also has a normal vote in such ballots.</p> - </li> - - <li> - <p>Vary the discussion period for Developers' votes (as above).</p> - </li> - - <li> - <p>Lead discussions amongst Developers.</p> - - <p>The Project Leader should attempt to participate in discussions - amongst the Developers in a helpful way which seeks to bring the - discussion to bear on the key issues at hand. The Project Leader - should not use the Leadership position to promote their own - personal views.</p> - </li> - - <li> - <p>Together with SPI, make decisions affecting property held in - trust for purposes related to Debian. (See §9.1.)</p> - </li> -</ol> - -<h3>5.2. Appointment</h3> - -<ol> - <li>The Project Leader is elected by the Developers.</li> - - <li>The election begins nine weeks before the leadership post becomes - vacant, or (if it is too late already) immediately.</li> - - <li>For the following three weeks any Developer may nominate - themselves as a candidate Project Leader.</li> - - <li>For three weeks after that no more candidates may be nominated; - candidates should use this time for campaigning (to make their - identities and positions known). If there are no candidates at the - end of the nomination period then the nomination period is extended - for three further weeks, repeatedly if necessary.</li> - - <li>The next three weeks are the polling period during which - Developers may cast their votes. Votes in leadership elections are - kept secret, even after the election is finished.</li> - - <li>The options on the ballot will be those candidates who have - nominated themselves and have not yet withdrawn, plus None Of The - Above. If None Of The Above wins the election then the election - procedure is repeated, many times if necessary.</li> - - <li> - The decision will be made using the method specified in section - §A.6 of the Standard Resolution Procedure. The quorum is the - same as for a General Resolution (§4.2) and the default - option is <q>None Of The Above</q>. - </li> - - <li>The Project Leader serves for one year from their election.</li> -</ol> - -<h3>5.3. Procedure</h3> - -<p>The Project Leader should attempt to make decisions which are -consistent with the consensus of the opinions of the Developers.</p> - -<p>Where practical the Project Leader should informally solicit the -views of the Developers.</p> - -<p>The Project Leader should avoid overemphasizing their own point of -view when making decisions in their capacity as Leader.</p> - -<h2>6. Technical committee</h2> - -<h3>6.1. Powers</h3> - -<p>The <a href="tech-ctte">Technical Committee</a> may:</p> - -<ol> - <li> - <p>Decide on any matter of technical policy.</p> - - <p>This includes the contents of the technical policy manuals, - developers' reference materials, example packages and the behaviour - of non-experimental package building tools. (In each case the usual - maintainer of the relevant software or documentation makes - decisions initially, however; see 6.3(5).)</p> - </li> - - <li> - <p>Decide any technical matter where Developers' jurisdictions - overlap.</p> - - <p>In cases where Developers need to implement compatible - technical policies or stances (for example, if they disagree about - the priorities of conflicting packages, or about ownership of a - command name, or about which package is responsible for a bug that - both maintainers agree is a bug, or about who should be the - maintainer for a package) the technical committee may decide the - matter.</p> - </li> - - <li> - <p>Make a decision when asked to do so.</p> - - <p>Any person or body may delegate a decision of their own to the - Technical Committee, or seek advice from it.</p> - </li> - - <li> - <p>Overrule a Developer (requires a 3:1 majority).</p> - - <p>The Technical Committee may ask a Developer to take a - particular technical course of action even if the Developer does - not wish to; this requires a 3:1 majority. For example, the - Committee may determine that a complaint made by the submitter of a - bug is justified and that the submitter's proposed solution should - be implemented.</p> - </li> - - <li> - <p>Offer advice.</p> - - <p>The Technical Committee may make formal announcements about its - views on any matter. <cite>Individual members may of course make - informal statements about their views and about the likely views of - the committee.</cite></p> - </li> - - <li> - <p>Together with the Project Leader, appoint new members to itself - or remove existing members. (See §6.2.)</p> - </li> - - <li> - <p>Appoint the Chairman of the Technical Committee.</p> - - <p> - The Chairman is elected by the Committee from its members. All - members of the committee are automatically nominated; the - committee votes starting one week before the post will become - vacant (or immediately, if it is already too late). The members - may vote by public acclamation for any fellow committee member, - including themselves; there is no default option. The vote - finishes when all the members have voted, or when the voting - period has ended. The result is determined using the method - specified in section A.6 of the Standard Resolution Procedure. - </p> - </li> - - <li> - <p>The Chairman can stand in for the Leader, together with the - Secretary</p> - - <p>As detailed in §7.1(2), the Chairman of the Technical - Committee and the Project Secretary may together stand in for the - Leader if there is no Leader.</p> - </li> -</ol> - -<h3>6.2. Composition</h3> - -<ol> - <li> - <p>The Technical Committee consists of up to 8 Developers, and - should usually have at least 4 members.</p> - </li> - - <li> - <p>When there are fewer than 8 members the Technical Committee may - recommend new member(s) to the Project Leader, who may choose - (individually) to appoint them or not.</p> - </li> - - <li> - <p>When there are 5 members or fewer the Technical Committee may - appoint new member(s) until the number of members reaches 6.</p> - </li> - - <li> - <p>When there have been 5 members or fewer for at least one week - the Project Leader may appoint new member(s) until the number of - members reaches 6, at intervals of at least one week per - appointment.</p> - </li> - - <li> - <p>If the Technical Committee and the Project Leader agree they - may remove or replace an existing member of the Technical - Committee.</p> - </li> -</ol> - -<h3>6.3. Procedure</h3> - -<ol> - <li> - <p>The Technical Committee uses the Standard Resolution - Procedure.</p> - - <p>A draft resolution or amendment may be proposed by any member - of the Technical Committee. There is no minimum discussion period; - the voting period lasts for up to one week, or until the outcome is - no longer in doubt. Members may change their votes. There is a - quorum of two.</p> - </li> - - <li> - <p>Details regarding voting</p> - - <p>The Chairman has a casting vote. When the Technical Committee - votes whether to override a Developer who also happens to be a - member of the Committee, that member may not vote (unless they are - the Chairman, in which case they may use only their casting - vote).</p> - </li> - - <li> - <p>Public discussion and decision-making.</p> - - <p>Discussion, draft resolutions and amendments, and votes by - members of the committee, are made public on the Technical - Committee public discussion list. There is no separate secretary - for the Committee.</p> - </li> - - <li> - <p>Confidentiality of appointments.</p> - - <p>The Technical Committee may hold confidential discussions via - private email or a private mailing list or other means to discuss - appointments to the Committee. However, votes on appointments must - be public.</p> - </li> - - <li> - <p>No detailed design work.</p> - - <p>The Technical Committee does not engage in design of new - proposals and policies. Such design work should be carried out by - individuals privately or together and discussed in ordinary - technical policy and design forums.</p> - - <p>The Technical Committee restricts itself to choosing from or - adopting compromises between solutions and decisions which have - been proposed and reasonably thoroughly discussed elsewhere.</p> - - <p><cite>Individual members of the technical committee may of - course participate on their own behalf in any aspect of design and - policy work.</cite></p> - </li> - - <li> - <p>Technical Committee makes decisions only as last resort.</p> - - <p>The Technical Committee does not make a technical decision - until efforts to resolve it via consensus have been tried and - failed, unless it has been asked to make a decision by the person - or body who would normally be responsible for it.</p> - </li> -</ol> - -<h2>7. The Project Secretary</h2> - -<h3>7.1. Powers</h3> - -<p>The <a href="secretary">Secretary</a>:</p> - -<ol> - <li> - <p>Takes votes amongst the Developers, and determines the number - and identity of Developers, whenever this is required by the - constitution.</p> - </li> - - <li> - <p>Can stand in for the Leader, together with the Chairman of the - Technical Committee.</p> - - <p>If there is no Project Leader then the Chairman of the - Technical Committee and the Project Secretary may by joint - agreement make decisions if they consider it imperative to do - so.</p> - </li> - - <li> - <p>Adjudicates any disputes about interpretation of the - constitution.</p> - </li> - - <li> - <p>May delegate part or all of their authority to someone else, or - withdraw such a delegation at any time.</p> - </li> -</ol> - -<h3>7.2. Appointment</h3> - -<p>The Project Secretary is appointed by the Project Leader and the -current Project Secretary.</p> - -<p>If the Project Leader and the current Project Secretary cannot -agree on a new appointment they must ask the board of SPI (see §9.1.) -to appoint a Secretary.</p> - -<p>If there is no Project Secretary or the current Secretary is -unavailable and has not delegated authority for a decision then the -decision may be made or delegated by the Chairman of the Technical -Committee, as Acting Secretary.</p> - -<p>The Project Secretary's term of office is 1 year, at which point -they or another Secretary must be (re)appointed.</p> - -<h3>7.3. Procedure</h3> - -<p>The Project Secretary should make decisions which are fair and -reasonable, and preferably consistent with the consensus of the -Developers.</p> - -<p>When acting together to stand in for an absent Project Leader the -Chairman of the Technical Committee and the Project Secretary should -make decisions only when absolutely necessary and only when consistent -with the consensus of the Developers.</p> - -<h2>8. The Project Leader's Delegates</h2> - -<h3>8.1. Powers</h3> - -<p>The Project Leader's Delegates:</p> - -<ol> - <li>have powers delegated to them by the Project Leader;</li> - - <li>may make certain decisions which the Leader may not make - directly, including approving or expelling Developers or designating - people as Developers who do not maintain packages. <cite>This is to - avoid concentration of power, particularly over membership as a - Developer, in the hands of the Project Leader.</cite></li> -</ol> - -<h3>8.2. Appointment</h3> - -<p>The Delegates are appointed by the Project Leader and may be -replaced by the Leader at the Leader's discretion. The Project Leader -may not make the position as a Delegate conditional on particular -decisions by the Delegate, nor may they override a decision made by a -Delegate once made.</p> - -<h3>8.3. Procedure</h3> - -<p>Delegates may make decisions as they see fit, but should attempt to -implement good technical decisions and/or follow consensus opinion.</p> - -<h2>9. Software in the Public Interest</h2> - -<p><a href="https://www.spi-inc.org/">SPI</a> and Debian are separate -organisations who share some goals. -Debian is grateful for the legal support framework offered by SPI. -<cite>Debian's Developers are currently members of SPI by virtue of -their status as Developers.</cite></p> - -<h3>9.1. Authority</h3> - -<ol> - <li>SPI has no authority regarding Debian's technical or nontechnical - decisions, except that no decision by Debian with respect to any - property held by SPI shall require SPI to act outside its legal - authority, and that Debian's constitution may occasionally use SPI as - a decision body of last resort.</li> - - <li>Debian claims no authority over SPI other than that over the use - of certain of SPI's property, as described below, though Debian - Developers may be granted authority within SPI by SPI's rules.</li> - - <li>Debian Developers are not agents or employees of SPI, or of each - other or of persons in authority in the Debian Project. A person - acting as a Developer does so as an individual, on their own - behalf.</li> -</ol> - -<h3>9.2. Management of property for purposes related to Debian</h3> - -<p>Since Debian has no authority to hold money or property, any -donations for the Debian Project must be made to SPI, which manages such -affairs.</p> - -<p>SPI have made the following undertakings:</p> - -<ol> - <li>SPI will hold money, trademarks and other tangible and intangible - property and manage other affairs for purposes related to - Debian.</li> - - <li>Such property will be accounted for separately and held in trust - for those purposes, decided on by Debian and SPI according to this - section.</li> - - <li>SPI will not dispose of or use property held in trust for Debian - without approval from Debian, which may be granted by the Project - Leader or by General Resolution of the Developers.</li> - - <li>SPI will consider using or disposing of property held in trust - for Debian when asked to do so by the Project Leader.</li> - - <li>SPI will use or dispose of property held in trust for Debian when - asked to do so by a General Resolution of the Developers, provided - that this is compatible with SPI's legal authority.</li> - - <li>SPI will notify the Developers by electronic mail to a Debian - Project mailing list when it uses or disposes of property held in - trust for Debian.</li> -</ol> - -<h2>A. Standard Resolution Procedure</h2> - -<p>These rules apply to communal decision-making by committees and -plebiscites, where stated above.</p> - -<h3>A.1. Proposal</h3> - -<p>The formal procedure begins when a draft resolution is proposed and -sponsored, as required.</p> - -<h3>A.1. Discussion and Amendment</h3> - -<ol> - <li>Following the proposal, the resolution may be discussed. - Amendments may be made formal by being proposed and sponsored - according to the requirements for a new resolution, or directly by - the proposer of the original resolution.</li> - - <li>A formal amendment may be accepted by the resolution's proposer, - in which case the formal resolution draft is immediately changed to - match.</li> - - <li>If a formal amendment is not accepted, or one of the sponsors of - the resolution does not agree with the acceptance by the proposer of - a formal amendment, the amendment remains as an amendment and will be - voted on.</li> - - <li>If an amendment accepted by the original proposer is not to the - liking of others, they may propose another amendment to reverse the - earlier change (again, they must meet the requirements for proposer - and sponsor(s).)</li> - - <li>The proposer of a resolution may suggest changes to the wordings - of amendments; these take effect if the proposer of the amendment - agrees and none of the sponsors object. In this case the changed - amendments will be voted on instead of the originals.</li> - - <li>The proposer of a resolution may make changes to correct minor - errors (for example, typographical errors or inconsistencies) or - changes which do not alter the meaning, providing noone objects - within 24 hours. In this case the minimum discussion period is not - restarted.</li> -</ol> - -<h3>A.2. Calling for a vote</h3> - -<ol> - <li>The proposer or a sponsor of a motion or an amendment may call - for a vote, providing that the minimum discussion period (if any) has - elapsed.</li> - - <li> - The proposer or any sponsor of a resolution may call for a vote on that - resolution and all related amendments. - </li> - - <li>The person who calls for a vote states what they believe the - wordings of the resolution and any relevant amendments are, and - consequently what form the ballot should take. However, the final - decision on the form of ballot(s) is the Secretary's - see 7.1(1), - 7.1(3) and A.3(4).</li> - - <li> - The minimum discussion period is counted from the time the last - formal amendment was accepted, or since the whole resolution - was proposed if no amendments have been proposed and accepted. - </li> -</ol> - -<h3>A.3. Voting procedure</h3> - -<ol> - <li> - Each resolution and its related amendments is voted on in a - single ballot that includes an option for the original - resolution, each amendment, and the default option (where - applicable). - </li> - - <li> - The default option must not have any supermajority requirements. - Options which do not have an explicit supermajority requirement - have a 1:1 majority requirement. - </li> - - <li> - The votes are counted according to the rules in A.6. The - default option is <q>Further Discussion</q>, unless specified - otherwise. - </li> - - <li>In cases of doubt the Project Secretary shall decide on matters - of procedure.</li> -</ol> - -<h3>A.4. Withdrawing resolutions or unaccepted amendments</h3> - -<p>The proposer of a resolution or unaccepted amendment may withdraw -it. In this case new proposers may come forward keep it alive, in which -case the first person to do so becomes the new proposer and any others -become sponsors if they aren't sponsors already.</p> - -<p>A sponsor of a resolution or amendment (unless it has been -accepted) may withdraw.</p> - -<p>If the withdrawal of the proposer and/or sponsors means that a -resolution has no proposer or not enough sponsors it will not be voted -on unless this is rectified before the resolution expires.</p> - -<h3>A.5. Expiry</h3> - -<p> - If a proposed resolution has not been discussed, amended, voted on or - otherwise dealt with for 4 weeks the secretary may issue a statement - that the issue is being withdrawn. If none of the sponsors of any - of the proposals object within a week, the issue is withdrawn. -</p> - -<p> - The secretary may also include suggestions on how to proceed, - if appropriate. -</p> - -<h3>A.6. Vote Counting</h3> - -<ol> - <li> Each voter's ballot ranks the options being voted on. Not all - options need be ranked. Ranked options are considered - preferred to all unranked options. Voters may rank options - equally. Unranked options are considered to be ranked equally - with one another. Details of how ballots may be filled out - will be included in the Call For Votes. - </li> - <li> If the ballot has a quorum requirement R any options other - than the default option which do not receive at least R votes - ranking that option above the default option are dropped from - consideration. - </li> - <li> Any (non-default) option which does not defeat the default option - by its required majority ratio is dropped from consideration. - <ol> - <li> - Given two options A and B, V(A,B) is the number of voters - who prefer option A over option B. - </li> - <li> - An option A defeats the default option D by a majority - ratio N, if V(A,D) is strictly greater than N * V(D,A). - </li> - <li> - If a supermajority of S:1 is required for A, its majority ratio - is S; otherwise, its majority ratio is 1. - </li> - </ol> - </li> - <li> From the list of undropped options, we generate a list of - pairwise defeats. - <ol> - <li> - An option A defeats an option B, if V(A,B) is strictly greater - than V(B,A). - </li> - </ol> - </li> - <li> From the list of [undropped] pairwise defeats, we generate a - set of transitive defeats. - <ol> - <li> - An option A transitively defeats an option C if A defeats - C or if there is some other option B where A defeats B AND - B transitively defeats C. - </li> - </ol> - </li> - <li> We construct the Schwartz set from the set of transitive defeats. - <ol> - <li> - An option A is in the Schwartz set if for all options B, - either A transitively defeats B, or B does not transitively - defeat A. - </li> - </ol> - </li> - <li> If there are defeats between options in the Schwartz set, - we drop the weakest such defeats from the list of pairwise - defeats, and return to step 5. - <ol> - <li> - A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) - is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if - V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B). - </li> - <li> - A weakest defeat is a defeat that has no other defeat weaker - than it. There may be more than one such defeat. - </li> - </ol> - </li> - <li> If there are no defeats within the Schwartz set, then the winner - is chosen from the options in the Schwartz set. If there is - only one such option, it is the winner. If there are multiple - options, the elector with the casting vote chooses which of those - options wins. - </li> -</ol> - -<p> - <strong>Note:</strong> Options which the voters rank above the default option - are options they find acceptable. Options ranked below the default - options are options they find unacceptable. -</p> - -<p><cite>When the Standard Resolution Procedure is to be used, the text -which refers to it must specify what is sufficient to have a draft -resolution proposed and/or sponsored, what the minimum discussion -period is, and what the voting period is. It must also specify any -supermajority and/or the quorum (and default option) to be -used.</cite></p> - -<h2>B. Use of language and typography</h2> - -<p>The present indicative (<q>is</q>, for example) means that the statement -is a rule in this constitution. <q>May</q> or <q>can</q> indicates that the -person or body has discretion. <q>Should</q> means that it would be -considered a good thing if the sentence were obeyed, but it is not -binding. <cite>Text marked as a citation, such as this, is rationale -and does not form part of the constitution. It may be used only to aid -interpretation in cases of doubt.</cite></p> diff --git a/greek/devel/constitution.1.2.wml b/greek/devel/constitution.1.2.wml deleted file mode 100644 index d9d47138633..00000000000 --- a/greek/devel/constitution.1.2.wml +++ /dev/null @@ -1,950 +0,0 @@ -#use wml::debian::template title="Historical Debian Constitution v 1.2" BARETITLE="true" -#use wml::debian::translation-check translation="ba01cfdc529712e3626bdf15fd37d39e94126794" maintainer="galaxico" - -<h1>Historical version of the Constitution for the Debian Project (v1.2)</h1> - -<p>Version 1.2 ratified on October 29th, 2003. Supersedes -<a href="constitution.1.1">Version 1.1</a> ratified on June 21st, -2003, which itself supersedes <a href="constitution.1.0">Version 1.0</a> -ratified on December 2nd, 1998. -Superseded by <a href="constitution.1.3">version 1.3</a>, ratified on September -24th, 2006. -Version 1.3 was again superseded by <a href="constitution.1.4">version 1.4</a> -ratified on October 7th, 2007. -That was superseded by the <a href="constitution.1.5">version 1.5</a> -ratified on January 9th, 2015, and again superseeded by the -<a href="constitution.1.6">version 1.6</a>, ratified on December 13th, 2015. -That was superseeded by the <a href="constitution">current version 1.7</a>, -ratified on August 14th, 2016. -</p> - -<h2>1. Introduction</h2> - -<p><cite>The Debian Project is an association of individuals who have -made common cause to create a free operating system.</cite></p> - -<p>This document describes the organisational structure for formal -decision-making in the Project. It does not describe the goals of the -Project or how it achieves them, or contain any policies except those -directly related to the decision-making process.</p> - -<h2>2. Decision-making bodies and individuals</h2> - -<p>Each decision in the Project is made by one or more of the -following:</p> - -<ol> - <li>The Developers, by way of General Resolution or an election;</li> - - <li>The Project Leader;</li> - - <li>The Technical Committee and/or its Chairman;</li> - - <li>The individual Developer working on a particular task;</li> - - <li>Delegates appointed by the Project Leader for specific - tasks;</li> - - <li>The Project Secretary.</li> -</ol> - -<p>Most of the remainder of this document will outline the powers of -these bodies, their composition and appointment, and the procedure for -their decision-making. The powers of a person or body may be subject to -review and/or limitation by others; in this case the reviewing body or -person's entry will state this. <cite>In the list above, a person or -body is usually listed before any people or bodies whose decisions they -can overrule or who they (help) appoint - but not everyone listed -earlier can overrule everyone listed later.</cite></p> - -<h3>2.1. General rules</h3> - -<ol> - <li> - <p>Nothing in this constitution imposes an obligation on anyone to - do work for the Project. A person who does not want to do a task - which has been delegated or assigned to them does not need to do - it. However, they must not actively work against these rules and - decisions properly made under them.</p> - </li> - - <li> - <p>A person may hold several posts, except that the Project Leader, - Project Secretary and the Chairman of the Technical Committee must - be distinct, and that the Leader cannot appoint themselves as their - own Delegate.</p> - </li> - - <li> - <p>A person may leave the Project or resign from a particular post - they hold, at any time, by stating so publicly.</p> - </li> -</ol> - -<h2>3. Individual Developers</h2> - -<h3>3.1. Powers</h3> - -<p>An individual Developer may</p> - -<ol> - <li>make any technical or nontechnical decision with regard to their - own work;</li> - - <li>propose or sponsor draft General Resolutions;</li> - - <li>propose themselves as a Project Leader candidate in - elections;</li> - - <li>vote on General Resolutions and in Leadership elections.</li> -</ol> - -<h3>3.2. Composition and appointment</h3> - -<ol> - <li> - <p>Developers are volunteers who agree to further the aims of the - Project insofar as they participate in it, and who maintain - package(s) for the Project or do other work which the Project - Leader's Delegate(s) consider worthwhile.</p> - </li> - - <li> - <p>The Project Leader's Delegate(s) may choose not to admit new - Developers, or expel existing Developers. <cite>If the Developers - feel that the Delegates are abusing their authority they can of - course override the decision by way of General Resolution - see - §4.1(3), §4.2.</cite></p> - </li> -</ol> - -<h3>3.3. Procedure</h3> - -<p>Developers may make these decisions as they see fit.</p> - -<h2>4. The Developers by way of General Resolution or election</h2> - -<h3>4.1. Powers</h3> - -<p>Together, the Developers may:</p> - -<ol> - <li> - <p>Appoint or recall the Project Leader.</p> - </li> - - <li> - <p>Amend this constitution, provided they agree with a 3:1 - majority.</p> - </li> - - <li> - <p>Override any decision by the Project Leader or a Delegate.</p> - </li> - - <li> - <p>Override any decision by the Technical Committee, provided they - agree with a 2:1 majority.</p> - </li> - - <li> - <p>Issue, supersede and withdraw nontechnical policy documents and - statements.</p> - - <p>These include documents describing the goals of the project, its - relationship with other free software entities, and nontechnical - policies such as the free software licence terms that Debian - software must meet.</p> - - <p>They may also include position statements about issues of the - day.</p> - - <ol style="list-style: decimal;"> - <li>A Foundation Document is a document or statement regarded as - critical to the Project's mission and purposes.</li> - <li>The Foundation Documents are the works entitled <q>Debian - Social Contract</q> and <q>Debian Free Software Guidelines</q>.</li> - <li>A Foundation Document requires a 3:1 majority for its - supersession. New Foundation Documents are issued and - existing ones withdrawn by amending the list of Foundation - Documents in this constitution.</li> - </ol> - - </li> - - <li> - <p>Together with the Project Leader and SPI, make decisions about - property held in trust for purposes related to Debian. (See - §9.1.)</p> - </li> -</ol> - -<h3>4.2. Procedure</h3> - -<ol> - <li> - <p>The Developers follow the Standard Resolution Procedure, below. - A resolution or amendment is introduced if proposed by any - Developer and sponsored by at least K other Developers, or if - proposed by the Project Leader or the Technical Committee.</p> - </li> - - <li> - <p>Delaying a decision by the Project Leader or their Delegate:</p> - - <ol> - <li>If the Project Leader or their Delegate, or the Technical - Committee, has made a decision, then Developers can override them - by passing a resolution to do so; see §4.1(3).</li> - - <li>If such a resolution is sponsored by at least 2K Developers, - or if it is proposed by the Technical Committee, the resolution - puts the decision immediately on hold (provided that resolution - itself says so).</li> - - <li>If the original decision was to change a discussion period or - a voting period, or the resolution is to override the Technical - Committee, then only K Developers need to sponsor the resolution - to be able to put the decision immediately on hold.</li> - - <li>If the decision is put on hold, an immediate vote is held to - determine whether the decision will stand until the full vote on - the decision is made or whether the implementation of the - original decision will be delayed until then. There is no - quorum for this immediate procedural vote.</li> - - <li>If the Project Leader (or the Delegate) withdraws the - original decision, the vote becomes moot, and is no longer - conducted.</li> - </ol> - </li> - - <li> - <p> - Votes are taken by the Project Secretary. Votes, tallies, and - results are not revealed during the voting period; after the - vote the Project Secretary lists all the votes cast. The voting - period is 2 weeks, but may be varied by up to 1 week by the - Project Leader. - </p> - </li> - - <li> - <p>The minimum discussion period is 2 weeks, but may be varied by - up to 1 week by the Project Leader. The Project Leader has a - casting vote. There is a quorum of 3Q.</p> - </li> - - <li> - <p>Proposals, sponsors, amendments, calls for votes and other - formal actions are made by announcement on a publicly-readable - electronic mailing list designated by the Project Leader's - Delegate(s); any Developer may post there.</p> - </li> - - <li> - <p>Votes are cast by email in a manner suitable to the Secretary. - The Secretary determines for each poll whether voters can change - their votes.</p> - </li> - - <li> - <p>Q is half of the square root of the number of current - Developers. K is Q or 5, whichever is the smaller. Q and K need not - be integers and are not rounded.</p> - </li> -</ol> - -<h2>5. Project Leader</h2> - -<h3>5.1. Powers</h3> - -<p>The <a href="leader">Project Leader</a> may:</p> - -<ol> - <li> - <p>Appoint Delegates or delegate decisions to the Technical - Committee.</p> - - <p>The Leader may define an area of ongoing responsibility or a - specific decision and hand it over to another Developer or to the - Technical Committee.</p> - - <p>Once a particular decision has been delegated and made the - Project Leader may not withdraw that delegation; however, they may - withdraw an ongoing delegation of particular area of - responsibility.</p> - </li> - - <li> - <p>Lend authority to other Developers.</p> - - <p>The Project Leader may make statements of support for points of - view or for other members of the project, when asked or otherwise; - these statements have force if and only if the Leader would be - empowered to make the decision in question.</p> - </li> - - <li> - <p>Make any decision which requires urgent action.</p> - - <p>This does not apply to decisions which have only become - gradually urgent through lack of relevant action, unless there is a - fixed deadline.</p> - </li> - - <li> - <p>Make any decision for whom noone else has responsibility.</p> - </li> - - <li> - <p>Propose draft General Resolutions and amendments.</p> - </li> - - <li> - <p>Together with the Technical Committee, appoint new members to - the Committee. (See §6.2.)</p> - </li> - - <li> - <p>Use a casting vote when Developers vote.</p> - - <p>The Project Leader also has a normal vote in such ballots.</p> - </li> - - <li> - <p>Vary the discussion period for Developers' votes (as above).</p> - </li> - - <li> - <p>Lead discussions amongst Developers.</p> - - <p>The Project Leader should attempt to participate in discussions - amongst the Developers in a helpful way which seeks to bring the - discussion to bear on the key issues at hand. The Project Leader - should not use the Leadership position to promote their own - personal views.</p> - </li> - - <li> - <p>Together with SPI, make decisions affecting property held in - trust for purposes related to Debian. (See §9.1.)</p> - </li> -</ol> - -<h3>5.2. Appointment</h3> - -<ol> - <li>The Project Leader is elected by the Developers.</li> - - <li>The election begins nine weeks before the leadership post becomes - vacant, or (if it is too late already) immediately.</li> - - <li>For the following three weeks any Developer may nominate - themselves as a candidate Project Leader.</li> - - <li>For three weeks after that no more candidates may be nominated; - candidates should use this time for campaigning (to make their - identities and positions known). If there are no candidates at the - end of the nomination period then the nomination period is extended - for three further weeks, repeatedly if necessary.</li> - - <li>The next three weeks are the polling period during which - Developers may cast their votes. Votes in leadership elections are - kept secret, even after the election is finished.</li> - - <li>The options on the ballot will be those candidates who have - nominated themselves and have not yet withdrawn, plus None Of The - Above. If None Of The Above wins the election then the election - procedure is repeated, many times if necessary.</li> - - <li> - The decision will be made using the method specified in section - §A.6 of the Standard Resolution Procedure. The quorum is the - same as for a General Resolution (§4.2) and the default - option is <q>None Of The Above</q>. - </li> - - <li>The Project Leader serves for one year from their election.</li> -</ol> - -<h3>5.3. Procedure</h3> - -<p>The Project Leader should attempt to make decisions which are -consistent with the consensus of the opinions of the Developers.</p> - -<p>Where practical the Project Leader should informally solicit the -views of the Developers.</p> - -<p>The Project Leader should avoid overemphasizing their own point of -view when making decisions in their capacity as Leader.</p> - -<h2>6. Technical committee</h2> - -<h3>6.1. Powers</h3> - -<p>The <a href="tech-ctte">Technical Committee</a> may:</p> - -<ol> - <li> - <p>Decide on any matter of technical policy.</p> - - <p>This includes the contents of the technical policy manuals, - developers' reference materials, example packages and the behaviour - of non-experimental package building tools. (In each case the usual - maintainer of the relevant software or documentation makes - decisions initially, however; see 6.3(5).)</p> - </li> - - <li> - <p>Decide any technical matter where Developers' jurisdictions - overlap.</p> - - <p>In cases where Developers need to implement compatible - technical policies or stances (for example, if they disagree about - the priorities of conflicting packages, or about ownership of a - command name, or about which package is responsible for a bug that - both maintainers agree is a bug, or about who should be the - maintainer for a package) the technical committee may decide the - matter.</p> - </li> - - <li> - <p>Make a decision when asked to do so.</p> - - <p>Any person or body may delegate a decision of their own to the - Technical Committee, or seek advice from it.</p> - </li> - - <li> - <p>Overrule a Developer (requires a 3:1 majority).</p> - - <p>The Technical Committee may ask a Developer to take a - particular technical course of action even if the Developer does - not wish to; this requires a 3:1 majority. For example, the - Committee may determine that a complaint made by the submitter of a - bug is justified and that the submitter's proposed solution should - be implemented.</p> - </li> - - <li> - <p>Offer advice.</p> - - <p>The Technical Committee may make formal announcements about its - views on any matter. <cite>Individual members may of course make - informal statements about their views and about the likely views of - the committee.</cite></p> - </li> - - <li> - <p>Together with the Project Leader, appoint new members to itself - or remove existing members. (See §6.2.)</p> - </li> - - <li> - <p>Appoint the Chairman of the Technical Committee.</p> - - <p> - The Chairman is elected by the Committee from its members. All - members of the committee are automatically nominated; the - committee votes starting one week before the post will become - vacant (or immediately, if it is already too late). The members - may vote by public acclamation for any fellow committee member, - including themselves; there is no default option. The vote - finishes when all the members have voted, or when the voting - period has ended. The result is determined using the method - specified in section A.6 of the Standard Resolution Procedure. - </p> - </li> - - <li> - <p>The Chairman can stand in for the Leader, together with the - Secretary</p> - - <p>As detailed in §7.1(2), the Chairman of the Technical - Committee and the Project Secretary may together stand in for the - Leader if there is no Leader.</p> - </li> -</ol> - -<h3>6.2. Composition</h3> - -<ol> - <li> - <p>The Technical Committee consists of up to 8 Developers, and - should usually have at least 4 members.</p> - </li> - - <li> - <p>When there are fewer than 8 members the Technical Committee may - recommend new member(s) to the Project Leader, who may choose - (individually) to appoint them or not.</p> - </li> - - <li> - <p>When there are 5 members or fewer the Technical Committee may - appoint new member(s) until the number of members reaches 6.</p> - </li> - - <li> - <p>When there have been 5 members or fewer for at least one week - the Project Leader may appoint new member(s) until the number of - members reaches 6, at intervals of at least one week per - appointment.</p> - </li> - - <li> - <p>If the Technical Committee and the Project Leader agree they - may remove or replace an existing member of the Technical - Committee.</p> - </li> -</ol> - -<h3>6.3. Procedure</h3> - -<ol> - <li> - <p>The Technical Committee uses the Standard Resolution - Procedure.</p> - - <p>A draft resolution or amendment may be proposed by any member - of the Technical Committee. There is no minimum discussion period; - the voting period lasts for up to one week, or until the outcome is - no longer in doubt. Members may change their votes. There is a - quorum of two.</p> - </li> - - <li> - <p>Details regarding voting</p> - - <p>The Chairman has a casting vote. When the Technical Committee - votes whether to override a Developer who also happens to be a - member of the Committee, that member may not vote (unless they are - the Chairman, in which case they may use only their casting - vote).</p> - </li> - - <li> - <p>Public discussion and decision-making.</p> - - <p>Discussion, draft resolutions and amendments, and votes by - members of the committee, are made public on the Technical - Committee public discussion list. There is no separate secretary - for the Committee.</p> - </li> - - <li> - <p>Confidentiality of appointments.</p> - - <p>The Technical Committee may hold confidential discussions via - private email or a private mailing list or other means to discuss - appointments to the Committee. However, votes on appointments must - be public.</p> - </li> - - <li> - <p>No detailed design work.</p> - - <p>The Technical Committee does not engage in design of new - proposals and policies. Such design work should be carried out by - individuals privately or together and discussed in ordinary - technical policy and design forums.</p> - - <p>The Technical Committee restricts itself to choosing from or - adopting compromises between solutions and decisions which have - been proposed and reasonably thoroughly discussed elsewhere.</p> - - <p><cite>Individual members of the technical committee may of - course participate on their own behalf in any aspect of design and - policy work.</cite></p> - </li> - - <li> - <p>Technical Committee makes decisions only as last resort.</p> - - <p>The Technical Committee does not make a technical decision - until efforts to resolve it via consensus have been tried and - failed, unless it has been asked to make a decision by the person - or body who would normally be responsible for it.</p> - </li> -</ol> - -<h2>7. The Project Secretary</h2> - -<h3>7.1. Powers</h3> - -<p>The <a href="secretary">Secretary</a>:</p> - -<ol> - <li> - <p>Takes votes amongst the Developers, and determines the number - and identity of Developers, whenever this is required by the - constitution.</p> - </li> - - <li> - <p>Can stand in for the Leader, together with the Chairman of the - Technical Committee.</p> - - <p>If there is no Project Leader then the Chairman of the - Technical Committee and the Project Secretary may by joint - agreement make decisions if they consider it imperative to do - so.</p> - </li> - - <li> - <p>Adjudicates any disputes about interpretation of the - constitution.</p> - </li> - - <li> - <p>May delegate part or all of their authority to someone else, or - withdraw such a delegation at any time.</p> - </li> -</ol> - -<h3>7.2. Appointment</h3> - -<p>The Project Secretary is appointed by the Project Leader and the -current Project Secretary.</p> - -<p>If the Project Leader and the current Project Secretary cannot -agree on a new appointment they must ask the board of SPI (see §9.1.) -to appoint a Secretary.</p> - -<p>If there is no Project Secretary or the current Secretary is -unavailable and has not delegated authority for a decision then the -decision may be made or delegated by the Chairman of the Technical -Committee, as Acting Secretary.</p> - -<p>The Project Secretary's term of office is 1 year, at which point -they or another Secretary must be (re)appointed.</p> - -<h3>7.3. Procedure</h3> - -<p>The Project Secretary should make decisions which are fair and -reasonable, and preferably consistent with the consensus of the -Developers.</p> - -<p>When acting together to stand in for an absent Project Leader the -Chairman of the Technical Committee and the Project Secretary should -make decisions only when absolutely necessary and only when consistent -with the consensus of the Developers.</p> - -<h2>8. The Project Leader's Delegates</h2> - -<h3>8.1. Powers</h3> - -<p>The Project Leader's Delegates:</p> - -<ol> - <li>have powers delegated to them by the Project Leader;</li> - - <li>may make certain decisions which the Leader may not make - directly, including approving or expelling Developers or designating - people as Developers who do not maintain packages. <cite>This is to - avoid concentration of power, particularly over membership as a - Developer, in the hands of the Project Leader.</cite></li> -</ol> - -<h3>8.2. Appointment</h3> - -<p>The Delegates are appointed by the Project Leader and may be -replaced by the Leader at the Leader's discretion. The Project Leader -may not make the position as a Delegate conditional on particular -decisions by the Delegate, nor may they override a decision made by a -Delegate once made.</p> - -<h3>8.3. Procedure</h3> - -<p>Delegates may make decisions as they see fit, but should attempt to -implement good technical decisions and/or follow consensus opinion.</p> - -<h2>9. Software in the Public Interest</h2> - -<p><a href="https://www.spi-inc.org/">SPI</a> and Debian are separate -organisations who share some goals. -Debian is grateful for the legal support framework offered by SPI. -<cite>Debian's Developers are currently members of SPI by virtue of -their status as Developers.</cite></p> - -<h3>9.1. Authority</h3> - -<ol> - <li>SPI has no authority regarding Debian's technical or nontechnical - decisions, except that no decision by Debian with respect to any - property held by SPI shall require SPI to act outside its legal - authority, and that Debian's constitution may occasionally use SPI as - a decision body of last resort.</li> - - <li>Debian claims no authority over SPI other than that over the use - of certain of SPI's property, as described below, though Debian - Developers may be granted authority within SPI by SPI's rules.</li> - - <li>Debian Developers are not agents or employees of SPI, or of each - other or of persons in authority in the Debian Project. A person - acting as a Developer does so as an individual, on their own - behalf.</li> -</ol> - -<h3>9.2. Management of property for purposes related to Debian</h3> - -<p>Since Debian has no authority to hold money or property, any -donations for the Debian Project must be made to SPI, which manages such -affairs.</p> - -<p>SPI have made the following undertakings:</p> - -<ol> - <li>SPI will hold money, trademarks and other tangible and intangible - property and manage other affairs for purposes related to - Debian.</li> - - <li>Such property will be accounted for separately and held in trust - for those purposes, decided on by Debian and SPI according to this - section.</li> - - <li>SPI will not dispose of or use property held in trust for Debian - without approval from Debian, which may be granted by the Project - Leader or by General Resolution of the Developers.</li> - - <li>SPI will consider using or disposing of property held in trust - for Debian when asked to do so by the Project Leader.</li> - - <li>SPI will use or dispose of property held in trust for Debian when - asked to do so by a General Resolution of the Developers, provided - that this is compatible with SPI's legal authority.</li> - - <li>SPI will notify the Developers by electronic mail to a Debian - Project mailing list when it uses or disposes of property held in - trust for Debian.</li> -</ol> - -<h2>A. Standard Resolution Procedure</h2> - -<p>These rules apply to communal decision-making by committees and -plebiscites, where stated above.</p> - -<h3>A.1. Proposal</h3> - -<p>The formal procedure begins when a draft resolution is proposed and -sponsored, as required.</p> - -<h3>A.1. Discussion and Amendment</h3> - -<ol> - <li>Following the proposal, the resolution may be discussed. - Amendments may be made formal by being proposed and sponsored - according to the requirements for a new resolution, or directly by - the proposer of the original resolution.</li> - - <li>A formal amendment may be accepted by the resolution's proposer, - in which case the formal resolution draft is immediately changed to - match.</li> - - <li>If a formal amendment is not accepted, or one of the sponsors of - the resolution does not agree with the acceptance by the proposer of - a formal amendment, the amendment remains as an amendment and will be - voted on.</li> - - <li>If an amendment accepted by the original proposer is not to the - liking of others, they may propose another amendment to reverse the - earlier change (again, they must meet the requirements for proposer - and sponsor(s).)</li> - - <li>The proposer of a resolution may suggest changes to the wordings - of amendments; these take effect if the proposer of the amendment - agrees and none of the sponsors object. In this case the changed - amendments will be voted on instead of the originals.</li> - - <li>The proposer of a resolution may make changes to correct minor - errors (for example, typographical errors or inconsistencies) or - changes which do not alter the meaning, providing noone objects - within 24 hours. In this case the minimum discussion period is not - restarted.</li> -</ol> - -<h3>A.2. Calling for a vote</h3> - -<ol> - <li>The proposer or a sponsor of a motion or an amendment may call - for a vote, providing that the minimum discussion period (if any) has - elapsed.</li> - - <li> - The proposer or any sponsor of a resolution may call for a vote on that - resolution and all related amendments. - </li> - - <li>The person who calls for a vote states what they believe the - wordings of the resolution and any relevant amendments are, and - consequently what form the ballot should take. However, the final - decision on the form of ballot(s) is the Secretary's - see 7.1(1), - 7.1(3) and A.3(4).</li> - - <li> - The minimum discussion period is counted from the time the last - formal amendment was accepted, or since the whole resolution - was proposed if no amendments have been proposed and accepted. - </li> -</ol> - -<h3>A.3. Voting procedure</h3> - -<ol> - <li> - Each resolution and its related amendments is voted on in a - single ballot that includes an option for the original - resolution, each amendment, and the default option (where - applicable). - </li> - - <li> - The default option must not have any supermajority requirements. - Options which do not have an explicit supermajority requirement - have a 1:1 majority requirement. - </li> - - <li> - The votes are counted according to the rules in A.6. The - default option is <q>Further Discussion</q>, unless specified - otherwise. - </li> - - <li>In cases of doubt the Project Secretary shall decide on matters - of procedure.</li> -</ol> - -<h3>A.4. Withdrawing resolutions or unaccepted amendments</h3> - -<p>The proposer of a resolution or unaccepted amendment may withdraw -it. In this case new proposers may come forward keep it alive, in which -case the first person to do so becomes the new proposer and any others -become sponsors if they aren't sponsors already.</p> - -<p>A sponsor of a resolution or amendment (unless it has been -accepted) may withdraw.</p> - -<p>If the withdrawal of the proposer and/or sponsors means that a -resolution has no proposer or not enough sponsors it will not be voted -on unless this is rectified before the resolution expires.</p> - -<h3>A.5. Expiry</h3> - -<p> - If a proposed resolution has not been discussed, amended, voted on or - otherwise dealt with for 4 weeks the secretary may issue a statement - that the issue is being withdrawn. If none of the sponsors of any - of the proposals object within a week, the issue is withdrawn. -</p> - -<p> - The secretary may also include suggestions on how to proceed, - if appropriate. -</p> - -<h3>A.6. Vote Counting</h3> - -<ol> - <li> Each voter's ballot ranks the options being voted on. Not all - options need be ranked. Ranked options are considered - preferred to all unranked options. Voters may rank options - equally. Unranked options are considered to be ranked equally - with one another. Details of how ballots may be filled out - will be included in the Call For Votes. - </li> - <li> If the ballot has a quorum requirement R any options other - than the default option which do not receive at least R votes - ranking that option above the default option are dropped from - consideration. - </li> - <li> Any (non-default) option which does not defeat the default option - by its required majority ratio is dropped from consideration. - <ol> - <li> - Given two options A and B, V(A,B) is the number of voters - who prefer option A over option B. - </li> - <li> - An option A defeats the default option D by a majority - ratio N, if V(A,D) is strictly greater than N * V(D,A). - </li> - <li> - If a supermajority of S:1 is required for A, its majority ratio - is S; otherwise, its majority ratio is 1. - </li> - </ol> - </li> - <li> From the list of undropped options, we generate a list of - pairwise defeats. - <ol> - <li> - An option A defeats an option B, if V(A,B) is strictly greater - than V(B,A). - </li> - </ol> - </li> - <li> From the list of [undropped] pairwise defeats, we generate a - set of transitive defeats. - <ol> - <li> - An option A transitively defeats an option C if A defeats - C or if there is some other option B where A defeats B AND - B transitively defeats C. - </li> - </ol> - </li> - <li> We construct the Schwartz set from the set of transitive defeats. - <ol> - <li> - An option A is in the Schwartz set if for all options B, - either A transitively defeats B, or B does not transitively - defeat A. - </li> - </ol> - </li> - <li> If there are defeats between options in the Schwartz set, - we drop the weakest such defeats from the list of pairwise - defeats, and return to step 5. - <ol> - <li> - A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) - is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if - V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B). - </li> - <li> - A weakest defeat is a defeat that has no other defeat weaker - than it. There may be more than one such defeat. - </li> - </ol> - </li> - <li> If there are no defeats within the Schwartz set, then the winner - is chosen from the options in the Schwartz set. If there is - only one such option, it is the winner. If there are multiple - options, the elector with the casting vote chooses which of those - options wins. - </li> -</ol> - -<p> - <strong>Note:</strong> Options which the voters rank above the default option - are options they find acceptable. Options ranked below the default - options are options they find unacceptable. -</p> - -<p><cite>When the Standard Resolution Procedure is to be used, the text -which refers to it must specify what is sufficient to have a draft -resolution proposed and/or sponsored, what the minimum discussion -period is, and what the voting period is. It must also specify any -supermajority and/or the quorum (and default option) to be -used.</cite></p> - -<h2>B. Use of language and typography</h2> - -<p>The present indicative (<q>is</q>, for example) means that the statement -is a rule in this constitution. <q>May</q> or <q>can</q> indicates that the -person or body has discretion. <q>Should</q> means that it would be -considered a good thing if the sentence were obeyed, but it is not -binding. <cite>Text marked as a citation, such as this, is rationale -and does not form part of the constitution. It may be used only to aid -interpretation in cases of doubt.</cite></p> diff --git a/greek/devel/constitution.1.3.wml b/greek/devel/constitution.1.3.wml deleted file mode 100644 index 3cba8f50e85..00000000000 --- a/greek/devel/constitution.1.3.wml +++ /dev/null @@ -1,976 +0,0 @@ -#use wml::debian::template title="Historical Debian Constitution v 1.3" BARETITLE="true" -#use wml::debian::toc -#use wml::debian::translation-check translation="ba01cfdc529712e3626bdf15fd37d39e94126794" maintainer="galaxico" - -<h1>Historical version of the Constitution for the Debian Project (v1.3)</h1> - -<p>Version 1.3 ratified on September 24th, 2006. Supersedes -<a href="constitution.1.2">Version 1.2</a> ratified on October 29th, -2003 and -<a href="constitution.1.1">Version 1.1</a> ratified on June 21st, -2003, which itself supersedes <a href="constitution.1.0">Version 1.0</a> -ratified on December 2nd, 1998. -Version 1.3 was again superseded by <a href="constitution.1.4">version 1.4</a> -ratified on October 7th, 2007. -That was superseded by the <a href="constitution.1.5">version 1.5</a> -ratified on January 9th, 2015, and again superseeded by the -<a href="constitution.1.6">version 1.6</a>, ratified on December 13th, 2015. -That was superseeded by the <a href="constitution">current version 1.7</a>, -ratified on August 14th, 2016. -</p> - -<toc-display /> - -<toc-add-entry name="item-1">1. Introduction</toc-add-entry> - -<p><cite>The Debian Project is an association of individuals who have -made common cause to create a free operating system.</cite></p> - -<p>This document describes the organisational structure for formal -decision-making in the Project. It does not describe the goals of the -Project or how it achieves them, or contain any policies except those -directly related to the decision-making process.</p> - -<toc-add-entry name="item-2">2. Decision-making bodies and individuals</toc-add-entry> - -<p>Each decision in the Project is made by one or more of the -following:</p> - -<ol> - <li>The Developers, by way of General Resolution or an election;</li> - - <li>The Project Leader;</li> - - <li>The Technical Committee and/or its Chairman;</li> - - <li>The individual Developer working on a particular task;</li> - - <li>Delegates appointed by the Project Leader for specific - tasks;</li> - - <li>The Project Secretary.</li> -</ol> - -<p>Most of the remainder of this document will outline the powers of -these bodies, their composition and appointment, and the procedure for -their decision-making. The powers of a person or body may be subject to -review and/or limitation by others; in this case the reviewing body or -person's entry will state this. <cite>In the list above, a person or -body is usually listed before any people or bodies whose decisions they -can overrule or who they (help) appoint - but not everyone listed -earlier can overrule everyone listed later.</cite></p> - -<h3>2.1. General rules</h3> - -<ol> - <li> - <p>Nothing in this constitution imposes an obligation on anyone to - do work for the Project. A person who does not want to do a task - which has been delegated or assigned to them does not need to do - it. However, they must not actively work against these rules and - decisions properly made under them.</p> - </li> - - <li> - <p>A person may hold several posts, except that the Project Leader, - Project Secretary and the Chairman of the Technical Committee must - be distinct, and that the Leader cannot appoint themselves as their - own Delegate.</p> - </li> - - <li> - <p>A person may leave the Project or resign from a particular post - they hold, at any time, by stating so publicly.</p> - </li> -</ol> - -<toc-add-entry name="item-3">3. Individual Developers</toc-add-entry> - -<h3>3.1. Powers</h3> - -<p>An individual Developer may</p> - -<ol> - <li>make any technical or nontechnical decision with regard to their - own work;</li> - - <li>propose or sponsor draft General Resolutions;</li> - - <li>propose themselves as a Project Leader candidate in - elections;</li> - - <li>vote on General Resolutions and in Leadership elections.</li> -</ol> - -<h3>3.2. Composition and appointment</h3> - -<ol> - <li> - <p>Developers are volunteers who agree to further the aims of the - Project insofar as they participate in it, and who maintain - package(s) for the Project or do other work which the Project - Leader's Delegate(s) consider worthwhile.</p> - </li> - - <li> - <p>The Project Leader's Delegate(s) may choose not to admit new - Developers, or expel existing Developers. <cite>If the Developers - feel that the Delegates are abusing their authority they can of - course override the decision by way of General Resolution - see - §4.1(3), §4.2.</cite></p> - </li> -</ol> - -<h3>3.3. Procedure</h3> - -<p>Developers may make these decisions as they see fit.</p> - -<toc-add-entry name="item-4">4. The Developers by way of General Resolution or election</toc-add-entry> - -<h3>4.1. Powers</h3> - -<p>Together, the Developers may:</p> - -<ol> - <li> - <p>Appoint or recall the Project Leader.</p> - </li> - - <li> - <p>Amend this constitution, provided they agree with a 3:1 - majority.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Project - Leader or a Delegate.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Technical - Committee, provided they agree with a 2:1 majority.</p> - </li> - - <li> - <p>Issue, supersede and withdraw nontechnical policy documents and - statements.</p> - - <p>These include documents describing the goals of the project, its - relationship with other free software entities, and nontechnical - policies such as the free software licence terms that Debian - software must meet.</p> - - <p>They may also include position statements about issues of the - day.</p> - - <ol style="list-style: decimal;"> - <li>A Foundation Document is a document or statement regarded as - critical to the Project's mission and purposes.</li> - <li>The Foundation Documents are the works entitled <q>Debian - Social Contract</q> and <q>Debian Free Software Guidelines</q>.</li> - <li>A Foundation Document requires a 3:1 majority for its - supersession. New Foundation Documents are issued and - existing ones withdrawn by amending the list of Foundation - Documents in this constitution.</li> - </ol> - - </li> - - <li> - <p>Make decisions about property held in trust for purposes - related to Debian. (See §9.).</p> - </li> - - <li> - <p>In case of a disagreement between the project leader and - the incumbent secretary, appoint a new secretary.</p> - </li> -</ol> - -<h3>4.2. Procedure</h3> - -<ol> - <li> - <p>The Developers follow the Standard Resolution Procedure, below. - A resolution or amendment is introduced if proposed by any - Developer and sponsored by at least K other Developers, or if - proposed by the Project Leader or the Technical Committee.</p> - </li> - - <li> - <p>Delaying a decision by the Project Leader or their Delegate:</p> - - <ol> - <li>If the Project Leader or their Delegate, or the Technical - Committee, has made a decision, then Developers can override them - by passing a resolution to do so; see §4.1(3).</li> - - <li>If such a resolution is sponsored by at least 2K Developers, - or if it is proposed by the Technical Committee, the resolution - puts the decision immediately on hold (provided that resolution - itself says so).</li> - - <li>If the original decision was to change a discussion period or - a voting period, or the resolution is to override the Technical - Committee, then only K Developers need to sponsor the resolution - to be able to put the decision immediately on hold.</li> - - <li>If the decision is put on hold, an immediate vote is held to - determine whether the decision will stand until the full vote on - the decision is made or whether the implementation of the - original decision will be delayed until then. There is no - quorum for this immediate procedural vote.</li> - - <li>If the Project Leader (or the Delegate) withdraws the - original decision, the vote becomes moot, and is no longer - conducted.</li> - </ol> - </li> - - <li> - <p> - Votes are taken by the Project Secretary. Votes, tallies, and - results are not revealed during the voting period; after the - vote the Project Secretary lists all the votes cast. The voting - period is 2 weeks, but may be varied by up to 1 week by the - Project Leader. - </p> - </li> - - <li> - <p>The minimum discussion period is 2 weeks, but may be varied by - up to 1 week by the Project Leader. The Project Leader has a - casting vote. There is a quorum of 3Q.</p> - </li> - - <li> - <p>Proposals, sponsors, amendments, calls for votes and other - formal actions are made by announcement on a publicly-readable - electronic mailing list designated by the Project Leader's - Delegate(s); any Developer may post there.</p> - </li> - - <li> - <p>Votes are cast by email in a manner suitable to the Secretary. - The Secretary determines for each poll whether voters can change - their votes.</p> - </li> - - <li> - <p>Q is half of the square root of the number of current - Developers. K is Q or 5, whichever is the smaller. Q and K need not - be integers and are not rounded.</p> - </li> -</ol> - -<toc-add-entry name="item-5">5. Project Leader</toc-add-entry> - -<h3>5.1. Powers</h3> - -<p>The <a href="leader">Project Leader</a> may:</p> - -<ol> - <li> - <p>Appoint Delegates or delegate decisions to the Technical - Committee.</p> - - <p>The Leader may define an area of ongoing responsibility or a - specific decision and hand it over to another Developer or to the - Technical Committee.</p> - - <p>Once a particular decision has been delegated and made the - Project Leader may not withdraw that delegation; however, they may - withdraw an ongoing delegation of particular area of - responsibility.</p> - </li> - - <li> - <p>Lend authority to other Developers.</p> - - <p>The Project Leader may make statements of support for points of - view or for other members of the project, when asked or otherwise; - these statements have force if and only if the Leader would be - empowered to make the decision in question.</p> - </li> - - <li> - <p>Make any decision which requires urgent action.</p> - - <p>This does not apply to decisions which have only become - gradually urgent through lack of relevant action, unless there is a - fixed deadline.</p> - </li> - - <li> - <p>Make any decision for whom noone else has responsibility.</p> - </li> - - <li> - <p>Propose draft General Resolutions and amendments.</p> - </li> - - <li> - <p>Together with the Technical Committee, appoint new members to - the Committee. (See §6.2.)</p> - </li> - - <li> - <p>Use a casting vote when Developers vote.</p> - - <p>The Project Leader also has a normal vote in such ballots.</p> - </li> - - <li> - <p>Vary the discussion period for Developers' votes (as above).</p> - </li> - - <li> - <p>Lead discussions amongst Developers.</p> - - <p>The Project Leader should attempt to participate in discussions - amongst the Developers in a helpful way which seeks to bring the - discussion to bear on the key issues at hand. The Project Leader - should not use the Leadership position to promote their own - personal views.</p> - </li> - - <li> - <p>In consultation with the developers, make decisions affecting - property held in trust for purposes related to Debian. (See - §9.). Such decisions are communicated to the members by the - Project Leader or their Delegate(s). Major expenditures - should be proposed and debated on the mailing list before - funds are disbursed.</p> - </li> - <li> - <p>Add or remove organizations from the list of trusted - organizations (see §9.3) that are authorized to accept and - hold assets for Debian. The evaluation and discussion leading - up to such a decision occurs on an electronic mailing list - designated by the Project Leader or their Delegate(s), on - which any developer may post. There is a minimum discussion - period of two weeks before an organization may be added to - the list of trusted organizations.</p> - </li> -</ol> - -<h3>5.2. Appointment</h3> - -<ol> - <li>The Project Leader is elected by the Developers.</li> - - <li>The election begins nine weeks before the leadership post becomes - vacant, or (if it is too late already) immediately.</li> - - <li>For the following three weeks any Developer may nominate - themselves as a candidate Project Leader.</li> - - <li>For three weeks after that no more candidates may be nominated; - candidates should use this time for campaigning (to make their - identities and positions known). If there are no candidates at the - end of the nomination period then the nomination period is extended - for three further weeks, repeatedly if necessary.</li> - - <li>The next three weeks are the polling period during which - Developers may cast their votes. Votes in leadership elections are - kept secret, even after the election is finished.</li> - - <li>The options on the ballot will be those candidates who have - nominated themselves and have not yet withdrawn, plus None Of The - Above. If None Of The Above wins the election then the election - procedure is repeated, many times if necessary.</li> - - <li> - The decision will be made using the method specified in section - §A.6 of the Standard Resolution Procedure. The quorum is the - same as for a General Resolution (§4.2) and the default - option is <q>None Of The Above</q>. - </li> - - <li>The Project Leader serves for one year from their election.</li> -</ol> - -<h3>5.3. Procedure</h3> - -<p>The Project Leader should attempt to make decisions which are -consistent with the consensus of the opinions of the Developers.</p> - -<p>Where practical the Project Leader should informally solicit the -views of the Developers.</p> - -<p>The Project Leader should avoid overemphasizing their own point of -view when making decisions in their capacity as Leader.</p> - -<toc-add-entry name="item-6">6. Technical committee</toc-add-entry> - -<h3>6.1. Powers</h3> - -<p>The <a href="tech-ctte">Technical Committee</a> may:</p> - -<ol> - <li> - <p>Decide on any matter of technical policy.</p> - - <p>This includes the contents of the technical policy manuals, - developers' reference materials, example packages and the behaviour - of non-experimental package building tools. (In each case the usual - maintainer of the relevant software or documentation makes - decisions initially, however; see 6.3(5).)</p> - </li> - - <li> - <p>Decide any technical matter where Developers' jurisdictions - overlap.</p> - - <p>In cases where Developers need to implement compatible - technical policies or stances (for example, if they disagree about - the priorities of conflicting packages, or about ownership of a - command name, or about which package is responsible for a bug that - both maintainers agree is a bug, or about who should be the - maintainer for a package) the technical committee may decide the - matter.</p> - </li> - - <li> - <p>Make a decision when asked to do so.</p> - - <p>Any person or body may delegate a decision of their own to the - Technical Committee, or seek advice from it.</p> - </li> - - <li> - <p>Overrule a Developer (requires a 3:1 majority).</p> - - <p>The Technical Committee may ask a Developer to take a - particular technical course of action even if the Developer does - not wish to; this requires a 3:1 majority. For example, the - Committee may determine that a complaint made by the submitter of a - bug is justified and that the submitter's proposed solution should - be implemented.</p> - </li> - - <li> - <p>Offer advice.</p> - - <p>The Technical Committee may make formal announcements about its - views on any matter. <cite>Individual members may of course make - informal statements about their views and about the likely views of - the committee.</cite></p> - </li> - - <li> - <p>Together with the Project Leader, appoint new members to itself - or remove existing members. (See §6.2.)</p> - </li> - - <li> - <p>Appoint the Chairman of the Technical Committee.</p> - - <p> - The Chairman is elected by the Committee from its members. All - members of the committee are automatically nominated; the - committee votes starting one week before the post will become - vacant (or immediately, if it is already too late). The members - may vote by public acclamation for any fellow committee member, - including themselves; there is no default option. The vote - finishes when all the members have voted, or when the voting - period has ended. The result is determined using the method - specified in section A.6 of the Standard Resolution Procedure. - </p> - </li> - - <li> - <p>The Chairman can stand in for the Leader, together with the - Secretary</p> - - <p>As detailed in §7.1(2), the Chairman of the Technical - Committee and the Project Secretary may together stand in for the - Leader if there is no Leader.</p> - </li> -</ol> - -<h3>6.2. Composition</h3> - -<ol> - <li> - <p>The Technical Committee consists of up to 8 Developers, and - should usually have at least 4 members.</p> - </li> - - <li> - <p>When there are fewer than 8 members the Technical Committee may - recommend new member(s) to the Project Leader, who may choose - (individually) to appoint them or not.</p> - </li> - - <li> - <p>When there are 5 members or fewer the Technical Committee may - appoint new member(s) until the number of members reaches 6.</p> - </li> - - <li> - <p>When there have been 5 members or fewer for at least one week - the Project Leader may appoint new member(s) until the number of - members reaches 6, at intervals of at least one week per - appointment.</p> - </li> - - <li> - <p>If the Technical Committee and the Project Leader agree they - may remove or replace an existing member of the Technical - Committee.</p> - </li> -</ol> - -<h3>6.3. Procedure</h3> - -<ol> - <li> - <p>The Technical Committee uses the Standard Resolution - Procedure.</p> - - <p>A draft resolution or amendment may be proposed by any member - of the Technical Committee. There is no minimum discussion period; - the voting period lasts for up to one week, or until the outcome is - no longer in doubt. Members may change their votes. There is a - quorum of two.</p> - </li> - - <li> - <p>Details regarding voting</p> - - <p>The Chairman has a casting vote. When the Technical Committee - votes whether to override a Developer who also happens to be a - member of the Committee, that member may not vote (unless they are - the Chairman, in which case they may use only their casting - vote).</p> - </li> - - <li> - <p>Public discussion and decision-making.</p> - - <p>Discussion, draft resolutions and amendments, and votes by - members of the committee, are made public on the Technical - Committee public discussion list. There is no separate secretary - for the Committee.</p> - </li> - - <li> - <p>Confidentiality of appointments.</p> - - <p>The Technical Committee may hold confidential discussions via - private email or a private mailing list or other means to discuss - appointments to the Committee. However, votes on appointments must - be public.</p> - </li> - - <li> - <p>No detailed design work.</p> - - <p>The Technical Committee does not engage in design of new - proposals and policies. Such design work should be carried out by - individuals privately or together and discussed in ordinary - technical policy and design forums.</p> - - <p>The Technical Committee restricts itself to choosing from or - adopting compromises between solutions and decisions which have - been proposed and reasonably thoroughly discussed elsewhere.</p> - - <p><cite>Individual members of the technical committee may of - course participate on their own behalf in any aspect of design and - policy work.</cite></p> - </li> - - <li> - <p>Technical Committee makes decisions only as last resort.</p> - - <p>The Technical Committee does not make a technical decision - until efforts to resolve it via consensus have been tried and - failed, unless it has been asked to make a decision by the person - or body who would normally be responsible for it.</p> - </li> -</ol> - -<toc-add-entry name="item-7">7. The Project Secretary</toc-add-entry> - -<h3>7.1. Powers</h3> - -<p>The <a href="secretary">Secretary</a>:</p> - -<ol> - <li> - <p>Takes votes amongst the Developers, and determines the number - and identity of Developers, whenever this is required by the - constitution.</p> - </li> - - <li> - <p>Can stand in for the Leader, together with the Chairman of the - Technical Committee.</p> - - <p>If there is no Project Leader then the Chairman of the - Technical Committee and the Project Secretary may by joint - agreement make decisions if they consider it imperative to do - so.</p> - </li> - - <li> - <p>Adjudicates any disputes about interpretation of the - constitution.</p> - </li> - - <li> - <p>May delegate part or all of their authority to someone else, or - withdraw such a delegation at any time.</p> - </li> -</ol> - -<h3>7.2. Appointment</h3> - -<p>The Project Secretary is appointed by the Project Leader and the -current Project Secretary.</p> - -<p>If the Project Leader and the current Project Secretary cannot agree -on a new appointment, they must ask the Developers by way of -General Resolution to appoint a Secretary.</p> - -<p>If there is no Project Secretary or the current Secretary is -unavailable and has not delegated authority for a decision then the -decision may be made or delegated by the Chairman of the Technical -Committee, as Acting Secretary.</p> - -<p>The Project Secretary's term of office is 1 year, at which point -they or another Secretary must be (re)appointed.</p> - -<h3>7.3. Procedure</h3> - -<p>The Project Secretary should make decisions which are fair and -reasonable, and preferably consistent with the consensus of the -Developers.</p> - -<p>When acting together to stand in for an absent Project Leader the -Chairman of the Technical Committee and the Project Secretary should -make decisions only when absolutely necessary and only when consistent -with the consensus of the Developers.</p> - -<toc-add-entry name="item-8">8. The Project Leader's Delegates</toc-add-entry> - -<h3>8.1. Powers</h3> - -<p>The Project Leader's Delegates:</p> - -<ol> - <li>have powers delegated to them by the Project Leader;</li> - - <li>may make certain decisions which the Leader may not make - directly, including approving or expelling Developers or designating - people as Developers who do not maintain packages. <cite>This is to - avoid concentration of power, particularly over membership as a - Developer, in the hands of the Project Leader.</cite></li> -</ol> - -<h3>8.2. Appointment</h3> - -<p>The Delegates are appointed by the Project Leader and may be -replaced by the Leader at the Leader's discretion. The Project Leader -may not make the position as a Delegate conditional on particular -decisions by the Delegate, nor may they override a decision made by a -Delegate once made.</p> - -<h3>8.3. Procedure</h3> - -<p>Delegates may make decisions as they see fit, but should attempt to -implement good technical decisions and/or follow consensus opinion.</p> - -<toc-add-entry name="item-9">9. Assets held in trust for Debian</toc-add-entry> - -<p>In most jurisdictions around the world, the Debian project is not -in a position to directly hold funds or other property. Therefore, -property has to be owned by any of a number of organisations as -detailed in §9.2.</p> - -<p>Traditionally, SPI was the sole organisation authorized to hold -property and monies for the Debian Project. SPI was created in -the U.S. to hold money in trust there.</p> - -<p><a href="https://www.spi-inc.org/">SPI</a> and Debian are separate -organisations who share some goals. -Debian is grateful for the legal support framework offered by SPI.</p> - -<h3>9.1. Relationship with Associated Organizations</h3> - -<ol> - <li> - <p>Debian Developers do not become agents or employees of - organisations holding assets in trust for Debian, or of - each other, or of persons in authority in the Debian Project, - solely by the virtue of being Debian Developers. A person - acting as a Developer does so as an individual, on their own - behalf. Such organisations may, of their own accord, - establish relationships with individuals who are also Debian - developers.</p> - </li> -</ol> - -<h3>9.2. Authority</h3> - -<ol> - <li> - <p>An organisation holding assets for Debian has no authority - regarding Debian's technical or nontechnical decisions, except - that no decision by Debian with respect to any property held - by the organisation shall require it to act outside its legal - authority.</p> - </li> - <li> - <p>Debian claims no authority over an organisation that holds - assets for Debian other than that over the use of property - held in trust for Debian.</p> - </li> -</ol> - -<h3>9.3. Trusted organisations</h3> - -<p>Any donations for the Debian Project must be made to any one of a -set of organisations designated by the Project leader (or a -delegate) to be authorized to handle assets to be used for the -Debian Project.</p> - -<p>Organisations holding assets in trust for Debian should -undertake reasonable obligations for the handling of such -assets.</p> - -<p>Debian maintains a public List of Trusted Organisations that -accept donations and hold assets in trust for Debian -(including both tangible property and intellectual property) -that includes the commitments those organisations have made as -to how those assets will be handled.</p> - -<toc-add-entry name="item-A">A. Standard Resolution Procedure</toc-add-entry> - -<p>These rules apply to communal decision-making by committees and -plebiscites, where stated above.</p> - -<h3>A.1. Proposal</h3> - -<p>The formal procedure begins when a draft resolution is proposed and -sponsored, as required.</p> - -<h3>A.1. Discussion and Amendment</h3> - -<ol> - <li>Following the proposal, the resolution may be discussed. - Amendments may be made formal by being proposed and sponsored - according to the requirements for a new resolution, or directly by - the proposer of the original resolution.</li> - - <li>A formal amendment may be accepted by the resolution's proposer, - in which case the formal resolution draft is immediately changed to - match.</li> - - <li>If a formal amendment is not accepted, or one of the sponsors of - the resolution does not agree with the acceptance by the proposer of - a formal amendment, the amendment remains as an amendment and will be - voted on.</li> - - <li>If an amendment accepted by the original proposer is not to the - liking of others, they may propose another amendment to reverse the - earlier change (again, they must meet the requirements for proposer - and sponsor(s).)</li> - - <li>The proposer of a resolution may suggest changes to the wordings - of amendments; these take effect if the proposer of the amendment - agrees and none of the sponsors object. In this case the changed - amendments will be voted on instead of the originals.</li> - - <li>The proposer of a resolution may make changes to correct minor - errors (for example, typographical errors or inconsistencies) or - changes which do not alter the meaning, providing noone objects - within 24 hours. In this case the minimum discussion period is not - restarted.</li> -</ol> - -<h3>A.2. Calling for a vote</h3> - -<ol> - <li>The proposer or a sponsor of a motion or an amendment may call - for a vote, providing that the minimum discussion period (if any) has - elapsed.</li> - - <li> - The proposer or any sponsor of a resolution may call for a vote on that - resolution and all related amendments. - </li> - - <li>The person who calls for a vote states what they believe the - wordings of the resolution and any relevant amendments are, and - consequently what form the ballot should take. However, the final - decision on the form of ballot(s) is the Secretary's - see 7.1(1), - 7.1(3) and A.3(4).</li> - - <li> - The minimum discussion period is counted from the time the last - formal amendment was accepted, or since the whole resolution - was proposed if no amendments have been proposed and accepted. - </li> -</ol> - -<h3>A.3. Voting procedure</h3> - -<ol> - <li> - Each resolution and its related amendments is voted on in a - single ballot that includes an option for the original - resolution, each amendment, and the default option (where - applicable). - </li> - - <li> - The default option must not have any supermajority requirements. - Options which do not have an explicit supermajority requirement - have a 1:1 majority requirement. - </li> - - <li> - The votes are counted according to the rules in A.6. The - default option is <q>Further Discussion</q>, unless specified - otherwise. - </li> - - <li>In cases of doubt the Project Secretary shall decide on matters - of procedure.</li> -</ol> - -<h3>A.4. Withdrawing resolutions or unaccepted amendments</h3> - -<p>The proposer of a resolution or unaccepted amendment may withdraw -it. In this case new proposers may come forward keep it alive, in which -case the first person to do so becomes the new proposer and any others -become sponsors if they aren't sponsors already.</p> - -<p>A sponsor of a resolution or amendment (unless it has been -accepted) may withdraw.</p> - -<p>If the withdrawal of the proposer and/or sponsors means that a -resolution has no proposer or not enough sponsors it will not be voted -on unless this is rectified before the resolution expires.</p> - -<h3>A.5. Expiry</h3> - -<p> - If a proposed resolution has not been discussed, amended, voted on or - otherwise dealt with for 4 weeks the secretary may issue a statement - that the issue is being withdrawn. If none of the sponsors of any - of the proposals object within a week, the issue is withdrawn. -</p> - -<p> - The secretary may also include suggestions on how to proceed, - if appropriate. -</p> - -<h3>A.6. Vote Counting</h3> - -<ol> - <li> Each voter's ballot ranks the options being voted on. Not all - options need be ranked. Ranked options are considered - preferred to all unranked options. Voters may rank options - equally. Unranked options are considered to be ranked equally - with one another. Details of how ballots may be filled out - will be included in the Call For Votes. - </li> - <li> If the ballot has a quorum requirement R any options other - than the default option which do not receive at least R votes - ranking that option above the default option are dropped from - consideration. - </li> - <li> Any (non-default) option which does not defeat the default option - by its required majority ratio is dropped from consideration. - <ol> - <li> - Given two options A and B, V(A,B) is the number of voters - who prefer option A over option B. - </li> - <li> - An option A defeats the default option D by a majority - ratio N, if V(A,D) is strictly greater than N * V(D,A). - </li> - <li> - If a supermajority of S:1 is required for A, its majority ratio - is S; otherwise, its majority ratio is 1. - </li> - </ol> - </li> - <li> From the list of undropped options, we generate a list of - pairwise defeats. - <ol> - <li> - An option A defeats an option B, if V(A,B) is strictly greater - than V(B,A). - </li> - </ol> - </li> - <li> From the list of [undropped] pairwise defeats, we generate a - set of transitive defeats. - <ol> - <li> - An option A transitively defeats an option C if A defeats - C or if there is some other option B where A defeats B AND - B transitively defeats C. - </li> - </ol> - </li> - <li> We construct the Schwartz set from the set of transitive defeats. - <ol> - <li> - An option A is in the Schwartz set if for all options B, - either A transitively defeats B, or B does not transitively - defeat A. - </li> - </ol> - </li> - <li> If there are defeats between options in the Schwartz set, - we drop the weakest such defeats from the list of pairwise - defeats, and return to step 5. - <ol> - <li> - A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) - is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if - V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B). - </li> - <li> - A weakest defeat is a defeat that has no other defeat weaker - than it. There may be more than one such defeat. - </li> - </ol> - </li> - <li> If there are no defeats within the Schwartz set, then the winner - is chosen from the options in the Schwartz set. If there is - only one such option, it is the winner. If there are multiple - options, the elector with the casting vote chooses which of those - options wins. - </li> -</ol> - -<p> - <strong>Note:</strong> Options which the voters rank above the default option - are options they find acceptable. Options ranked below the default - options are options they find unacceptable. -</p> - -<p><cite>When the Standard Resolution Procedure is to be used, the text -which refers to it must specify what is sufficient to have a draft -resolution proposed and/or sponsored, what the minimum discussion -period is, and what the voting period is. It must also specify any -supermajority and/or the quorum (and default option) to be -used.</cite></p> - -<toc-add-entry name="item-B">B. Use of language and typography</toc-add-entry> - -<p>The present indicative (<q>is</q>, for example) means that the statement -is a rule in this constitution. <q>May</q> or <q>can</q> indicates that the -person or body has discretion. <q>Should</q> means that it would be -considered a good thing if the sentence were obeyed, but it is not -binding. <cite>Text marked as a citation, such as this, is rationale -and does not form part of the constitution. It may be used only to aid -interpretation in cases of doubt.</cite></p> diff --git a/greek/devel/constitution.1.4.wml b/greek/devel/constitution.1.4.wml deleted file mode 100644 index b40db870956..00000000000 --- a/greek/devel/constitution.1.4.wml +++ /dev/null @@ -1,976 +0,0 @@ -#use wml::debian::template title="Historical Debian Constitution v 1.4" BARETITLE="true" -#use wml::debian::toc -#use wml::debian::translation-check translation="ba01cfdc529712e3626bdf15fd37d39e94126794" maintainer="galaxico" - -<h1>Historical version of the Constitution for the Debian Project (v1.4)</h1> - -<p>Version 1.4 ratified on October 7th, 2007. Supersedes -<a href="constitution.1.3">Version 1.3</a> ratified on September 24th, -2006, -<a href="constitution.1.2">Version 1.2</a> ratified on October 29th, -2003 and -<a href="constitution.1.1">Version 1.1</a> ratified on June 21st, -2003, which itself supersedes <a href="constitution.1.0">Version 1.0</a> -ratified on December 2nd, 1998. -That was superseded by the <a href="constitution.1.5">version 1.5</a> -ratified on January 9th, 2015, and again superseded by the -<a href="constitution.1.6">version 1.6</a>, ratified on December 13th, 2015. -That was superseded by the <a href="constitution">current version 1.7</a>, -ratified on August 14th, 2016. -</p> - -<toc-display /> - -<toc-add-entry name="item-1">1. Introduction</toc-add-entry> - -<p><cite>The Debian Project is an association of individuals who have -made common cause to create a free operating system.</cite></p> - -<p>This document describes the organisational structure for formal -decision-making in the Project. It does not describe the goals of the -Project or how it achieves them, or contain any policies except those -directly related to the decision-making process.</p> - -<toc-add-entry name="item-2">2. Decision-making bodies and individuals</toc-add-entry> - -<p>Each decision in the Project is made by one or more of the -following:</p> - -<ol> - <li>The Developers, by way of General Resolution or an election;</li> - - <li>The Project Leader;</li> - - <li>The Technical Committee and/or its Chairman;</li> - - <li>The individual Developer working on a particular task;</li> - - <li>Delegates appointed by the Project Leader for specific - tasks;</li> - - <li>The Project Secretary.</li> -</ol> - -<p>Most of the remainder of this document will outline the powers of -these bodies, their composition and appointment, and the procedure for -their decision-making. The powers of a person or body may be subject to -review and/or limitation by others; in this case the reviewing body or -person's entry will state this. <cite>In the list above, a person or -body is usually listed before any people or bodies whose decisions they -can overrule or who they (help) appoint - but not everyone listed -earlier can overrule everyone listed later.</cite></p> - -<h3>2.1. General rules</h3> - -<ol> - <li> - <p>Nothing in this constitution imposes an obligation on anyone to - do work for the Project. A person who does not want to do a task - which has been delegated or assigned to them does not need to do - it. However, they must not actively work against these rules and - decisions properly made under them.</p> - </li> - - <li> - <p>A person may hold several posts, except that the Project Leader, - Project Secretary and the Chairman of the Technical Committee must - be distinct, and that the Leader cannot appoint themselves as their - own Delegate.</p> - </li> - - <li> - <p>A person may leave the Project or resign from a particular post - they hold, at any time, by stating so publicly.</p> - </li> -</ol> - -<toc-add-entry name="item-3">3. Individual Developers</toc-add-entry> - -<h3>3.1. Powers</h3> - -<p>An individual Developer may</p> - -<ol> - <li>make any technical or nontechnical decision with regard to their - own work;</li> - - <li>propose or sponsor draft General Resolutions;</li> - - <li>propose themselves as a Project Leader candidate in - elections;</li> - - <li>vote on General Resolutions and in Leadership elections.</li> -</ol> - -<h3>3.2. Composition and appointment</h3> - -<ol> - <li> - <p>Developers are volunteers who agree to further the aims of the - Project insofar as they participate in it, and who maintain - package(s) for the Project or do other work which the Project - Leader's Delegate(s) consider worthwhile.</p> - </li> - - <li> - <p>The Project Leader's Delegate(s) may choose not to admit new - Developers, or expel existing Developers. <cite>If the Developers - feel that the Delegates are abusing their authority they can of - course override the decision by way of General Resolution - see - §4.1(3), §4.2.</cite></p> - </li> -</ol> - -<h3>3.3. Procedure</h3> - -<p>Developers may make these decisions as they see fit.</p> - -<toc-add-entry name="item-4">4. The Developers by way of General Resolution or election</toc-add-entry> - -<h3>4.1. Powers</h3> - -<p>Together, the Developers may:</p> - -<ol> - <li> - <p>Appoint or recall the Project Leader.</p> - </li> - - <li> - <p>Amend this constitution, provided they agree with a 3:1 - majority.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Project - Leader or a Delegate.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Technical - Committee, provided they agree with a 2:1 majority.</p> - </li> - - <li> - <p>Issue, supersede and withdraw nontechnical policy documents and - statements.</p> - - <p>These include documents describing the goals of the project, its - relationship with other free software entities, and nontechnical - policies such as the free software licence terms that Debian - software must meet.</p> - - <p>They may also include position statements about issues of the - day.</p> - - <ol style="list-style: decimal;"> - <li>A Foundation Document is a document or statement regarded as - critical to the Project's mission and purposes.</li> - <li>The Foundation Documents are the works entitled <q>Debian - Social Contract</q> and <q>Debian Free Software Guidelines</q>.</li> - <li>A Foundation Document requires a 3:1 majority for its - supersession. New Foundation Documents are issued and - existing ones withdrawn by amending the list of Foundation - Documents in this constitution.</li> - </ol> - - </li> - - <li> - <p>Make decisions about property held in trust for purposes - related to Debian. (See §9.).</p> - </li> - - <li> - <p>In case of a disagreement between the project leader and - the incumbent secretary, appoint a new secretary.</p> - </li> -</ol> - -<h3>4.2. Procedure</h3> - -<ol> - <li> - <p>The Developers follow the Standard Resolution Procedure, below. - A resolution or amendment is introduced if proposed by any - Developer and sponsored by at least K other Developers, or if - proposed by the Project Leader or the Technical Committee.</p> - </li> - - <li> - <p>Delaying a decision by the Project Leader or their Delegate:</p> - - <ol> - <li>If the Project Leader or their Delegate, or the Technical - Committee, has made a decision, then Developers can override them - by passing a resolution to do so; see §4.1(3).</li> - - <li>If such a resolution is sponsored by at least 2K Developers, - or if it is proposed by the Technical Committee, the resolution - puts the decision immediately on hold (provided that resolution - itself says so).</li> - - <li>If the original decision was to change a discussion period or - a voting period, or the resolution is to override the Technical - Committee, then only K Developers need to sponsor the resolution - to be able to put the decision immediately on hold.</li> - - <li>If the decision is put on hold, an immediate vote is held to - determine whether the decision will stand until the full vote on - the decision is made or whether the implementation of the - original decision will be delayed until then. There is no - quorum for this immediate procedural vote.</li> - - <li>If the Project Leader (or the Delegate) withdraws the - original decision, the vote becomes moot, and is no longer - conducted.</li> - </ol> - </li> - - <li> - <p> - Votes are taken by the Project Secretary. Votes, tallies, and - results are not revealed during the voting period; after the - vote the Project Secretary lists all the votes cast. The voting - period is 2 weeks, but may be varied by up to 1 week by the - Project Leader. - </p> - </li> - - <li> - <p>The minimum discussion period is 2 weeks, but may be varied by - up to 1 week by the Project Leader. The Project Leader has a - casting vote. There is a quorum of 3Q.</p> - </li> - - <li> - <p>Proposals, sponsors, amendments, calls for votes and other - formal actions are made by announcement on a publicly-readable - electronic mailing list designated by the Project Leader's - Delegate(s); any Developer may post there.</p> - </li> - - <li> - <p>Votes are cast by email in a manner suitable to the Secretary. - The Secretary determines for each poll whether voters can change - their votes.</p> - </li> - - <li> - <p>Q is half of the square root of the number of current - Developers. K is Q or 5, whichever is the smaller. Q and K need not - be integers and are not rounded.</p> - </li> -</ol> - -<toc-add-entry name="item-5">5. Project Leader</toc-add-entry> - -<h3>5.1. Powers</h3> - -<p>The <a href="leader">Project Leader</a> may:</p> - -<ol> - <li> - <p>Appoint Delegates or delegate decisions to the Technical - Committee.</p> - - <p>The Leader may define an area of ongoing responsibility or a - specific decision and hand it over to another Developer or to the - Technical Committee.</p> - - <p>Once a particular decision has been delegated and made the - Project Leader may not withdraw that delegation; however, they may - withdraw an ongoing delegation of particular area of - responsibility.</p> - </li> - - <li> - <p>Lend authority to other Developers.</p> - - <p>The Project Leader may make statements of support for points of - view or for other members of the project, when asked or otherwise; - these statements have force if and only if the Leader would be - empowered to make the decision in question.</p> - </li> - - <li> - <p>Make any decision which requires urgent action.</p> - - <p>This does not apply to decisions which have only become - gradually urgent through lack of relevant action, unless there is a - fixed deadline.</p> - </li> - - <li> - <p>Make any decision for whom noone else has responsibility.</p> - </li> - - <li> - <p>Propose draft General Resolutions and amendments.</p> - </li> - - <li> - <p>Together with the Technical Committee, appoint new members to - the Committee. (See §6.2.)</p> - </li> - - <li> - <p>Use a casting vote when Developers vote.</p> - - <p>The Project Leader also has a normal vote in such ballots.</p> - </li> - - <li> - <p>Vary the discussion period for Developers' votes (as above).</p> - </li> - - <li> - <p>Lead discussions amongst Developers.</p> - - <p>The Project Leader should attempt to participate in discussions - amongst the Developers in a helpful way which seeks to bring the - discussion to bear on the key issues at hand. The Project Leader - should not use the Leadership position to promote their own - personal views.</p> - </li> - - <li> - <p>In consultation with the developers, make decisions affecting - property held in trust for purposes related to Debian. (See - §9.). Such decisions are communicated to the members by the - Project Leader or their Delegate(s). Major expenditures - should be proposed and debated on the mailing list before - funds are disbursed.</p> - </li> - <li> - <p>Add or remove organizations from the list of trusted - organizations (see §9.3) that are authorized to accept and - hold assets for Debian. The evaluation and discussion leading - up to such a decision occurs on an electronic mailing list - designated by the Project Leader or their Delegate(s), on - which any developer may post. There is a minimum discussion - period of two weeks before an organization may be added to - the list of trusted organizations.</p> - </li> -</ol> - -<h3>5.2. Appointment</h3> - -<ol> - <li>The Project Leader is elected by the Developers.</li> - - <li>The election begins six weeks before the leadership post becomes - vacant, or (if it is too late already) immediately.</li> - - <li>For the first week any Developer may nominate - themselves as a candidate Project Leader, and summarize their plans for their term.</li> - - <li>For three weeks after that no more candidates may be nominated; - candidates should use this time for campaigning and discussion. If - there are no candidates at the end of the nomination period then the - nomination period is extended for an additional week, repeatedly if - necessary.</li> - - <li>The next two weeks are the polling period during which - Developers may cast their votes. Votes in leadership elections are - kept secret, even after the election is finished.</li> - - <li>The options on the ballot will be those candidates who have - nominated themselves and have not yet withdrawn, plus None Of The - Above. If None Of The Above wins the election then the election - procedure is repeated, many times if necessary.</li> - - <li> - The decision will be made using the method specified in section - §A.6 of the Standard Resolution Procedure. The quorum is the - same as for a General Resolution (§4.2) and the default - option is <q>None Of The Above</q>. - </li> - - <li>The Project Leader serves for one year from their election.</li> -</ol> - -<h3>5.3. Procedure</h3> - -<p>The Project Leader should attempt to make decisions which are -consistent with the consensus of the opinions of the Developers.</p> - -<p>Where practical the Project Leader should informally solicit the -views of the Developers.</p> - -<p>The Project Leader should avoid overemphasizing their own point of -view when making decisions in their capacity as Leader.</p> - -<toc-add-entry name="item-6">6. Technical committee</toc-add-entry> - -<h3>6.1. Powers</h3> - -<p>The <a href="tech-ctte">Technical Committee</a> may:</p> - -<ol> - <li> - <p>Decide on any matter of technical policy.</p> - - <p>This includes the contents of the technical policy manuals, - developers' reference materials, example packages and the behaviour - of non-experimental package building tools. (In each case the usual - maintainer of the relevant software or documentation makes - decisions initially, however; see 6.3(5).)</p> - </li> - - <li> - <p>Decide any technical matter where Developers' jurisdictions - overlap.</p> - - <p>In cases where Developers need to implement compatible - technical policies or stances (for example, if they disagree about - the priorities of conflicting packages, or about ownership of a - command name, or about which package is responsible for a bug that - both maintainers agree is a bug, or about who should be the - maintainer for a package) the technical committee may decide the - matter.</p> - </li> - - <li> - <p>Make a decision when asked to do so.</p> - - <p>Any person or body may delegate a decision of their own to the - Technical Committee, or seek advice from it.</p> - </li> - - <li> - <p>Overrule a Developer (requires a 3:1 majority).</p> - - <p>The Technical Committee may ask a Developer to take a - particular technical course of action even if the Developer does - not wish to; this requires a 3:1 majority. For example, the - Committee may determine that a complaint made by the submitter of a - bug is justified and that the submitter's proposed solution should - be implemented.</p> - </li> - - <li> - <p>Offer advice.</p> - - <p>The Technical Committee may make formal announcements about its - views on any matter. <cite>Individual members may of course make - informal statements about their views and about the likely views of - the committee.</cite></p> - </li> - - <li> - <p>Together with the Project Leader, appoint new members to itself - or remove existing members. (See §6.2.)</p> - </li> - - <li> - <p>Appoint the Chairman of the Technical Committee.</p> - - <p> - The Chairman is elected by the Committee from its members. All - members of the committee are automatically nominated; the - committee votes starting one week before the post will become - vacant (or immediately, if it is already too late). The members - may vote by public acclamation for any fellow committee member, - including themselves; there is no default option. The vote - finishes when all the members have voted, or when the voting - period has ended. The result is determined using the method - specified in section A.6 of the Standard Resolution Procedure. - </p> - </li> - - <li> - <p>The Chairman can stand in for the Leader, together with the - Secretary</p> - - <p>As detailed in §7.1(2), the Chairman of the Technical - Committee and the Project Secretary may together stand in for the - Leader if there is no Leader.</p> - </li> -</ol> - -<h3>6.2. Composition</h3> - -<ol> - <li> - <p>The Technical Committee consists of up to 8 Developers, and - should usually have at least 4 members.</p> - </li> - - <li> - <p>When there are fewer than 8 members the Technical Committee may - recommend new member(s) to the Project Leader, who may choose - (individually) to appoint them or not.</p> - </li> - - <li> - <p>When there are 5 members or fewer the Technical Committee may - appoint new member(s) until the number of members reaches 6.</p> - </li> - - <li> - <p>When there have been 5 members or fewer for at least one week - the Project Leader may appoint new member(s) until the number of - members reaches 6, at intervals of at least one week per - appointment.</p> - </li> - - <li> - <p>If the Technical Committee and the Project Leader agree they - may remove or replace an existing member of the Technical - Committee.</p> - </li> -</ol> - -<h3>6.3. Procedure</h3> - -<ol> - <li> - <p>The Technical Committee uses the Standard Resolution - Procedure.</p> - - <p>A draft resolution or amendment may be proposed by any member - of the Technical Committee. There is no minimum discussion period; - the voting period lasts for up to one week, or until the outcome is - no longer in doubt. Members may change their votes. There is a - quorum of two.</p> - </li> - - <li> - <p>Details regarding voting</p> - - <p>The Chairman has a casting vote. When the Technical Committee - votes whether to override a Developer who also happens to be a - member of the Committee, that member may not vote (unless they are - the Chairman, in which case they may use only their casting - vote).</p> - </li> - - <li> - <p>Public discussion and decision-making.</p> - - <p>Discussion, draft resolutions and amendments, and votes by - members of the committee, are made public on the Technical - Committee public discussion list. There is no separate secretary - for the Committee.</p> - </li> - - <li> - <p>Confidentiality of appointments.</p> - - <p>The Technical Committee may hold confidential discussions via - private email or a private mailing list or other means to discuss - appointments to the Committee. However, votes on appointments must - be public.</p> - </li> - - <li> - <p>No detailed design work.</p> - - <p>The Technical Committee does not engage in design of new - proposals and policies. Such design work should be carried out by - individuals privately or together and discussed in ordinary - technical policy and design forums.</p> - - <p>The Technical Committee restricts itself to choosing from or - adopting compromises between solutions and decisions which have - been proposed and reasonably thoroughly discussed elsewhere.</p> - - <p><cite>Individual members of the technical committee may of - course participate on their own behalf in any aspect of design and - policy work.</cite></p> - </li> - - <li> - <p>Technical Committee makes decisions only as last resort.</p> - - <p>The Technical Committee does not make a technical decision - until efforts to resolve it via consensus have been tried and - failed, unless it has been asked to make a decision by the person - or body who would normally be responsible for it.</p> - </li> -</ol> - -<toc-add-entry name="item-7">7. The Project Secretary</toc-add-entry> - -<h3>7.1. Powers</h3> - -<p>The <a href="secretary">Secretary</a>:</p> - -<ol> - <li> - <p>Takes votes amongst the Developers, and determines the number - and identity of Developers, whenever this is required by the - constitution.</p> - </li> - - <li> - <p>Can stand in for the Leader, together with the Chairman of the - Technical Committee.</p> - - <p>If there is no Project Leader then the Chairman of the - Technical Committee and the Project Secretary may by joint - agreement make decisions if they consider it imperative to do - so.</p> - </li> - - <li> - <p>Adjudicates any disputes about interpretation of the - constitution.</p> - </li> - - <li> - <p>May delegate part or all of their authority to someone else, or - withdraw such a delegation at any time.</p> - </li> -</ol> - -<h3>7.2. Appointment</h3> - -<p>The Project Secretary is appointed by the Project Leader and the -current Project Secretary.</p> - -<p>If the Project Leader and the current Project Secretary cannot agree -on a new appointment, they must ask the Developers by way of -General Resolution to appoint a Secretary.</p> - -<p>If there is no Project Secretary or the current Secretary is -unavailable and has not delegated authority for a decision then the -decision may be made or delegated by the Chairman of the Technical -Committee, as Acting Secretary.</p> - -<p>The Project Secretary's term of office is 1 year, at which point -they or another Secretary must be (re)appointed.</p> - -<h3>7.3. Procedure</h3> - -<p>The Project Secretary should make decisions which are fair and -reasonable, and preferably consistent with the consensus of the -Developers.</p> - -<p>When acting together to stand in for an absent Project Leader the -Chairman of the Technical Committee and the Project Secretary should -make decisions only when absolutely necessary and only when consistent -with the consensus of the Developers.</p> - -<toc-add-entry name="item-8">8. The Project Leader's Delegates</toc-add-entry> - -<h3>8.1. Powers</h3> - -<p>The Project Leader's Delegates:</p> - -<ol> - <li>have powers delegated to them by the Project Leader;</li> - - <li>may make certain decisions which the Leader may not make - directly, including approving or expelling Developers or designating - people as Developers who do not maintain packages. <cite>This is to - avoid concentration of power, particularly over membership as a - Developer, in the hands of the Project Leader.</cite></li> -</ol> - -<h3>8.2. Appointment</h3> - -<p>The Delegates are appointed by the Project Leader and may be -replaced by the Leader at the Leader's discretion. The Project Leader -may not make the position as a Delegate conditional on particular -decisions by the Delegate, nor may they override a decision made by a -Delegate once made.</p> - -<h3>8.3. Procedure</h3> - -<p>Delegates may make decisions as they see fit, but should attempt to -implement good technical decisions and/or follow consensus opinion.</p> - -<toc-add-entry name="item-9">9. Assets held in trust for Debian</toc-add-entry> - -<p>In most jurisdictions around the world, the Debian project is not -in a position to directly hold funds or other property. Therefore, -property has to be owned by any of a number of organisations as -detailed in §9.2.</p> - -<p>Traditionally, SPI was the sole organisation authorized to hold -property and monies for the Debian Project. SPI was created in -the U.S. to hold money in trust there.</p> - -<p><a href="https://www.spi-inc.org/">SPI</a> and Debian are separate -organisations who share some goals. -Debian is grateful for the legal support framework offered by SPI.</p> - -<h3>9.1. Relationship with Associated Organizations</h3> - -<ol> - <li> - <p>Debian Developers do not become agents or employees of - organisations holding assets in trust for Debian, or of - each other, or of persons in authority in the Debian Project, - solely by the virtue of being Debian Developers. A person - acting as a Developer does so as an individual, on their own - behalf. Such organisations may, of their own accord, - establish relationships with individuals who are also Debian - developers.</p> - </li> -</ol> - -<h3>9.2. Authority</h3> - -<ol> - <li> - <p>An organisation holding assets for Debian has no authority - regarding Debian's technical or nontechnical decisions, except - that no decision by Debian with respect to any property held - by the organisation shall require it to act outside its legal - authority.</p> - </li> - <li> - <p>Debian claims no authority over an organisation that holds - assets for Debian other than that over the use of property - held in trust for Debian.</p> - </li> -</ol> - -<h3>9.3. Trusted organisations</h3> - -<p>Any donations for the Debian Project must be made to any one of a -set of organisations designated by the Project leader (or a -delegate) to be authorized to handle assets to be used for the -Debian Project.</p> - -<p>Organisations holding assets in trust for Debian should -undertake reasonable obligations for the handling of such -assets.</p> - -<p>Debian maintains a public List of Trusted Organisations that -accept donations and hold assets in trust for Debian -(including both tangible property and intellectual property) -that includes the commitments those organisations have made as -to how those assets will be handled.</p> - -<toc-add-entry name="item-A">A. Standard Resolution Procedure</toc-add-entry> - -<p>These rules apply to communal decision-making by committees and -plebiscites, where stated above.</p> - -<h3>A.1. Proposal</h3> - -<p>The formal procedure begins when a draft resolution is proposed and -sponsored, as required.</p> - -<h3>A.1. Discussion and Amendment</h3> - -<ol> - <li>Following the proposal, the resolution may be discussed. - Amendments may be made formal by being proposed and sponsored - according to the requirements for a new resolution, or directly by - the proposer of the original resolution.</li> - - <li>A formal amendment may be accepted by the resolution's proposer, - in which case the formal resolution draft is immediately changed to - match.</li> - - <li>If a formal amendment is not accepted, or one of the sponsors of - the resolution does not agree with the acceptance by the proposer of - a formal amendment, the amendment remains as an amendment and will be - voted on.</li> - - <li>If an amendment accepted by the original proposer is not to the - liking of others, they may propose another amendment to reverse the - earlier change (again, they must meet the requirements for proposer - and sponsor(s).)</li> - - <li>The proposer of a resolution may suggest changes to the wordings - of amendments; these take effect if the proposer of the amendment - agrees and none of the sponsors object. In this case the changed - amendments will be voted on instead of the originals.</li> - - <li>The proposer of a resolution may make changes to correct minor - errors (for example, typographical errors or inconsistencies) or - changes which do not alter the meaning, providing noone objects - within 24 hours. In this case the minimum discussion period is not - restarted.</li> -</ol> - -<h3>A.2. Calling for a vote</h3> - -<ol> - <li>The proposer or a sponsor of a motion or an amendment may call - for a vote, providing that the minimum discussion period (if any) has - elapsed.</li> - - <li> - The proposer or any sponsor of a resolution may call for a vote on that - resolution and all related amendments. - </li> - - <li>The person who calls for a vote states what they believe the - wordings of the resolution and any relevant amendments are, and - consequently what form the ballot should take. However, the final - decision on the form of ballot(s) is the Secretary's - see 7.1(1), - 7.1(3) and A.3(4).</li> - - <li> - The minimum discussion period is counted from the time the last - formal amendment was accepted, or since the whole resolution - was proposed if no amendments have been proposed and accepted. - </li> -</ol> - -<h3>A.3. Voting procedure</h3> - -<ol> - <li> - Each resolution and its related amendments is voted on in a - single ballot that includes an option for the original - resolution, each amendment, and the default option (where - applicable). - </li> - - <li> - The default option must not have any supermajority requirements. - Options which do not have an explicit supermajority requirement - have a 1:1 majority requirement. - </li> - - <li> - The votes are counted according to the rules in A.6. The - default option is <q>Further Discussion</q>, unless specified - otherwise. - </li> - - <li>In cases of doubt the Project Secretary shall decide on matters - of procedure.</li> -</ol> - -<h3>A.4. Withdrawing resolutions or unaccepted amendments</h3> - -<p>The proposer of a resolution or unaccepted amendment may withdraw -it. In this case new proposers may come forward keep it alive, in which -case the first person to do so becomes the new proposer and any others -become sponsors if they aren't sponsors already.</p> - -<p>A sponsor of a resolution or amendment (unless it has been -accepted) may withdraw.</p> - -<p>If the withdrawal of the proposer and/or sponsors means that a -resolution has no proposer or not enough sponsors it will not be voted -on unless this is rectified before the resolution expires.</p> - -<h3>A.5. Expiry</h3> - -<p> - If a proposed resolution has not been discussed, amended, voted on or - otherwise dealt with for 4 weeks the secretary may issue a statement - that the issue is being withdrawn. If none of the sponsors of any - of the proposals object within a week, the issue is withdrawn. -</p> - -<p> - The secretary may also include suggestions on how to proceed, - if appropriate. -</p> - -<h3>A.6. Vote Counting</h3> - -<ol> - <li> Each voter's ballot ranks the options being voted on. Not all - options need be ranked. Ranked options are considered - preferred to all unranked options. Voters may rank options - equally. Unranked options are considered to be ranked equally - with one another. Details of how ballots may be filled out - will be included in the Call For Votes. - </li> - <li> If the ballot has a quorum requirement R any options other - than the default option which do not receive at least R votes - ranking that option above the default option are dropped from - consideration. - </li> - <li> Any (non-default) option which does not defeat the default option - by its required majority ratio is dropped from consideration. - <ol> - <li> - Given two options A and B, V(A,B) is the number of voters - who prefer option A over option B. - </li> - <li> - An option A defeats the default option D by a majority - ratio N, if V(A,D) is strictly greater than N * V(D,A). - </li> - <li> - If a supermajority of S:1 is required for A, its majority ratio - is S; otherwise, its majority ratio is 1. - </li> - </ol> - </li> - <li> From the list of undropped options, we generate a list of - pairwise defeats. - <ol> - <li> - An option A defeats an option B, if V(A,B) is strictly greater - than V(B,A). - </li> - </ol> - </li> - <li> From the list of [undropped] pairwise defeats, we generate a - set of transitive defeats. - <ol> - <li> - An option A transitively defeats an option C if A defeats - C or if there is some other option B where A defeats B AND - B transitively defeats C. - </li> - </ol> - </li> - <li> We construct the Schwartz set from the set of transitive defeats. - <ol> - <li> - An option A is in the Schwartz set if for all options B, - either A transitively defeats B, or B does not transitively - defeat A. - </li> - </ol> - </li> - <li> If there are defeats between options in the Schwartz set, - we drop the weakest such defeats from the list of pairwise - defeats, and return to step 5. - <ol> - <li> - A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) - is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if - V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B). - </li> - <li> - A weakest defeat is a defeat that has no other defeat weaker - than it. There may be more than one such defeat. - </li> - </ol> - </li> - <li> If there are no defeats within the Schwartz set, then the winner - is chosen from the options in the Schwartz set. If there is - only one such option, it is the winner. If there are multiple - options, the elector with the casting vote chooses which of those - options wins. - </li> -</ol> - -<p> - <strong>Note:</strong> Options which the voters rank above the default option - are options they find acceptable. Options ranked below the default - options are options they find unacceptable. -</p> - -<p><cite>When the Standard Resolution Procedure is to be used, the text -which refers to it must specify what is sufficient to have a draft -resolution proposed and/or sponsored, what the minimum discussion -period is, and what the voting period is. It must also specify any -supermajority and/or the quorum (and default option) to be -used.</cite></p> - -<toc-add-entry name="item-B">B. Use of language and typography</toc-add-entry> - -<p>The present indicative (<q>is</q>, for example) means that the statement -is a rule in this constitution. <q>May</q> or <q>can</q> indicates that the -person or body has discretion. <q>Should</q> means that it would be -considered a good thing if the sentence were obeyed, but it is not -binding. <cite>Text marked as a citation, such as this, is rationale -and does not form part of the constitution. It may be used only to aid -interpretation in cases of doubt.</cite></p> diff --git a/greek/devel/constitution.1.5.wml b/greek/devel/constitution.1.5.wml deleted file mode 100644 index 407a7f9cdde..00000000000 --- a/greek/devel/constitution.1.5.wml +++ /dev/null @@ -1,1002 +0,0 @@ -#use wml::debian::template title="Historical Debian Constitution v 1.5" BARETITLE="true" -#use wml::debian::toc -#use wml::debian::translation-check translation="ba01cfdc529712e3626bdf15fd37d39e94126794" maintainer="galaxico" - -<h1>Historical version of the Constitution for the Debian Project (v1.5)</h1> - -<p>Version 1.5 ratified on January 9th, 2015. Supersedes -<a href="constitution.1.4">Version 1.4</a> ratified on October 7th, 2007, -<a href="constitution.1.3">Version 1.3</a> ratified on September 24th, -2006, -<a href="constitution.1.2">Version 1.2</a> ratified on October 29th, -2003 and -<a href="constitution.1.1">Version 1.1</a> ratified on June 21st, -2003, which itself supersedes <a href="constitution.1.0">Version 1.0</a> -ratified on December 2nd, 1998. -That was superseded by the -<a href="constitution.1.6">version 1.6</a>, ratified on December 13th, 2015. -That was superseded by the <a href="constitution">current version 1.7</a>, -ratified on August 14th, 2016. -</p> - -<toc-display /> - -<toc-add-entry name="item-1">1. Introduction</toc-add-entry> - -<p><cite>The Debian Project is an association of individuals who have -made common cause to create a free operating system.</cite></p> - -<p>This document describes the organisational structure for formal -decision-making in the Project. It does not describe the goals of the -Project or how it achieves them, or contain any policies except those -directly related to the decision-making process.</p> - -<toc-add-entry name="item-2">2. Decision-making bodies and individuals</toc-add-entry> - -<p>Each decision in the Project is made by one or more of the -following:</p> - -<ol> - <li>The Developers, by way of General Resolution or an election;</li> - - <li>The Project Leader;</li> - - <li>The Technical Committee and/or its Chairman;</li> - - <li>The individual Developer working on a particular task;</li> - - <li>Delegates appointed by the Project Leader for specific - tasks;</li> - - <li>The Project Secretary.</li> -</ol> - -<p>Most of the remainder of this document will outline the powers of -these bodies, their composition and appointment, and the procedure for -their decision-making. The powers of a person or body may be subject to -review and/or limitation by others; in this case the reviewing body or -person's entry will state this. <cite>In the list above, a person or -body is usually listed before any people or bodies whose decisions they -can overrule or who they (help) appoint - but not everyone listed -earlier can overrule everyone listed later.</cite></p> - -<h3>2.1. General rules</h3> - -<ol> - <li> - <p>Nothing in this constitution imposes an obligation on anyone to - do work for the Project. A person who does not want to do a task - which has been delegated or assigned to them does not need to do - it. However, they must not actively work against these rules and - decisions properly made under them.</p> - </li> - - <li> - <p>A person may hold several posts, except that the Project Leader, - Project Secretary and the Chairman of the Technical Committee must - be distinct, and that the Leader cannot appoint themselves as their - own Delegate.</p> - </li> - - <li> - <p>A person may leave the Project or resign from a particular post - they hold, at any time, by stating so publicly.</p> - </li> -</ol> - -<toc-add-entry name="item-3">3. Individual Developers</toc-add-entry> - -<h3>3.1. Powers</h3> - -<p>An individual Developer may</p> - -<ol> - <li>make any technical or nontechnical decision with regard to their - own work;</li> - - <li>propose or sponsor draft General Resolutions;</li> - - <li>propose themselves as a Project Leader candidate in - elections;</li> - - <li>vote on General Resolutions and in Leadership elections.</li> -</ol> - -<h3>3.2. Composition and appointment</h3> - -<ol> - <li> - <p>Developers are volunteers who agree to further the aims of the - Project insofar as they participate in it, and who maintain - package(s) for the Project or do other work which the Project - Leader's Delegate(s) consider worthwhile.</p> - </li> - - <li> - <p>The Project Leader's Delegate(s) may choose not to admit new - Developers, or expel existing Developers. <cite>If the Developers - feel that the Delegates are abusing their authority they can of - course override the decision by way of General Resolution - see - §4.1(3), §4.2.</cite></p> - </li> -</ol> - -<h3>3.3. Procedure</h3> - -<p>Developers may make these decisions as they see fit.</p> - -<toc-add-entry name="item-4">4. The Developers by way of General Resolution or election</toc-add-entry> - -<h3>4.1. Powers</h3> - -<p>Together, the Developers may:</p> - -<ol> - <li> - <p>Appoint or recall the Project Leader.</p> - </li> - - <li> - <p>Amend this constitution, provided they agree with a 3:1 - majority.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Project - Leader or a Delegate.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Technical - Committee, provided they agree with a 2:1 majority.</p> - </li> - - <li> - <p>Issue, supersede and withdraw nontechnical policy documents and - statements.</p> - - <p>These include documents describing the goals of the project, its - relationship with other free software entities, and nontechnical - policies such as the free software licence terms that Debian - software must meet.</p> - - <p>They may also include position statements about issues of the - day.</p> - - <ol style="list-style: decimal;"> - <li>A Foundation Document is a document or statement regarded as - critical to the Project's mission and purposes.</li> - <li>The Foundation Documents are the works entitled <q>Debian - Social Contract</q> and <q>Debian Free Software Guidelines</q>.</li> - <li>A Foundation Document requires a 3:1 majority for its - supersession. New Foundation Documents are issued and - existing ones withdrawn by amending the list of Foundation - Documents in this constitution.</li> - </ol> - - </li> - - <li> - <p>Make decisions about property held in trust for purposes - related to Debian. (See §9.).</p> - </li> - - <li> - <p>In case of a disagreement between the project leader and - the incumbent secretary, appoint a new secretary.</p> - </li> -</ol> - -<h3>4.2. Procedure</h3> - -<ol> - <li> - <p>The Developers follow the Standard Resolution Procedure, below. - A resolution or amendment is introduced if proposed by any - Developer and sponsored by at least K other Developers, or if - proposed by the Project Leader or the Technical Committee.</p> - </li> - - <li> - <p>Delaying a decision by the Project Leader or their Delegate:</p> - - <ol> - <li>If the Project Leader or their Delegate, or the Technical - Committee, has made a decision, then Developers can override them - by passing a resolution to do so; see §4.1(3).</li> - - <li>If such a resolution is sponsored by at least 2K Developers, - or if it is proposed by the Technical Committee, the resolution - puts the decision immediately on hold (provided that resolution - itself says so).</li> - - <li>If the original decision was to change a discussion period or - a voting period, or the resolution is to override the Technical - Committee, then only K Developers need to sponsor the resolution - to be able to put the decision immediately on hold.</li> - - <li>If the decision is put on hold, an immediate vote is held to - determine whether the decision will stand until the full vote on - the decision is made or whether the implementation of the - original decision will be delayed until then. There is no - quorum for this immediate procedural vote.</li> - - <li>If the Project Leader (or the Delegate) withdraws the - original decision, the vote becomes moot, and is no longer - conducted.</li> - </ol> - </li> - - <li> - <p> - Votes are taken by the Project Secretary. Votes, tallies, and - results are not revealed during the voting period; after the - vote the Project Secretary lists all the votes cast. The voting - period is 2 weeks, but may be varied by up to 1 week by the - Project Leader. - </p> - </li> - - <li> - <p>The minimum discussion period is 2 weeks, but may be varied by - up to 1 week by the Project Leader. The Project Leader has a - casting vote. There is a quorum of 3Q.</p> - </li> - - <li> - <p>Proposals, sponsors, amendments, calls for votes and other - formal actions are made by announcement on a publicly-readable - electronic mailing list designated by the Project Leader's - Delegate(s); any Developer may post there.</p> - </li> - - <li> - <p>Votes are cast by email in a manner suitable to the Secretary. - The Secretary determines for each poll whether voters can change - their votes.</p> - </li> - - <li> - <p>Q is half of the square root of the number of current - Developers. K is Q or 5, whichever is the smaller. Q and K need not - be integers and are not rounded.</p> - </li> -</ol> - -<toc-add-entry name="item-5">5. Project Leader</toc-add-entry> - -<h3>5.1. Powers</h3> - -<p>The <a href="leader">Project Leader</a> may:</p> - -<ol> - <li> - <p>Appoint Delegates or delegate decisions to the Technical - Committee.</p> - - <p>The Leader may define an area of ongoing responsibility or a - specific decision and hand it over to another Developer or to the - Technical Committee.</p> - - <p>Once a particular decision has been delegated and made the - Project Leader may not withdraw that delegation; however, they may - withdraw an ongoing delegation of particular area of - responsibility.</p> - </li> - - <li> - <p>Lend authority to other Developers.</p> - - <p>The Project Leader may make statements of support for points of - view or for other members of the project, when asked or otherwise; - these statements have force if and only if the Leader would be - empowered to make the decision in question.</p> - </li> - - <li> - <p>Make any decision which requires urgent action.</p> - - <p>This does not apply to decisions which have only become - gradually urgent through lack of relevant action, unless there is a - fixed deadline.</p> - </li> - - <li> - <p>Make any decision for whom noone else has responsibility.</p> - </li> - - <li> - <p>Propose draft General Resolutions and amendments.</p> - </li> - - <li> - <p>Together with the Technical Committee, appoint new members to - the Committee. (See §6.2.)</p> - </li> - - <li> - <p>Use a casting vote when Developers vote.</p> - - <p>The Project Leader also has a normal vote in such ballots.</p> - </li> - - <li> - <p>Vary the discussion period for Developers' votes (as above).</p> - </li> - - <li> - <p>Lead discussions amongst Developers.</p> - - <p>The Project Leader should attempt to participate in discussions - amongst the Developers in a helpful way which seeks to bring the - discussion to bear on the key issues at hand. The Project Leader - should not use the Leadership position to promote their own - personal views.</p> - </li> - - <li> - <p>In consultation with the developers, make decisions affecting - property held in trust for purposes related to Debian. (See - §9.). Such decisions are communicated to the members by the - Project Leader or their Delegate(s). Major expenditures - should be proposed and debated on the mailing list before - funds are disbursed.</p> - </li> - <li> - <p>Add or remove organizations from the list of trusted - organizations (see §9.3) that are authorized to accept and - hold assets for Debian. The evaluation and discussion leading - up to such a decision occurs on an electronic mailing list - designated by the Project Leader or their Delegate(s), on - which any developer may post. There is a minimum discussion - period of two weeks before an organization may be added to - the list of trusted organizations.</p> - </li> -</ol> - -<h3>5.2. Appointment</h3> - -<ol> - <li>The Project Leader is elected by the Developers.</li> - - <li>The election begins six weeks before the leadership post becomes - vacant, or (if it is too late already) immediately.</li> - - <li>For the first week any Developer may nominate - themselves as a candidate Project Leader, and summarize their plans for their term.</li> - - <li>For three weeks after that no more candidates may be nominated; - candidates should use this time for campaigning and discussion. If - there are no candidates at the end of the nomination period then the - nomination period is extended for an additional week, repeatedly if - necessary.</li> - - <li>The next two weeks are the polling period during which - Developers may cast their votes. Votes in leadership elections are - kept secret, even after the election is finished.</li> - - <li>The options on the ballot will be those candidates who have - nominated themselves and have not yet withdrawn, plus None Of The - Above. If None Of The Above wins the election then the election - procedure is repeated, many times if necessary.</li> - - <li> - The decision will be made using the method specified in section - §A.6 of the Standard Resolution Procedure. The quorum is the - same as for a General Resolution (§4.2) and the default - option is <q>None Of The Above</q>. - </li> - - <li>The Project Leader serves for one year from their election.</li> -</ol> - -<h3>5.3. Procedure</h3> - -<p>The Project Leader should attempt to make decisions which are -consistent with the consensus of the opinions of the Developers.</p> - -<p>Where practical the Project Leader should informally solicit the -views of the Developers.</p> - -<p>The Project Leader should avoid overemphasizing their own point of -view when making decisions in their capacity as Leader.</p> - -<toc-add-entry name="item-6">6. Technical committee</toc-add-entry> - -<h3>6.1. Powers</h3> - -<p>The <a href="tech-ctte">Technical Committee</a> may:</p> - -<ol> - <li> - <p>Decide on any matter of technical policy.</p> - - <p>This includes the contents of the technical policy manuals, - developers' reference materials, example packages and the behaviour - of non-experimental package building tools. (In each case the usual - maintainer of the relevant software or documentation makes - decisions initially, however; see 6.3(5).)</p> - </li> - - <li> - <p>Decide any technical matter where Developers' jurisdictions - overlap.</p> - - <p>In cases where Developers need to implement compatible - technical policies or stances (for example, if they disagree about - the priorities of conflicting packages, or about ownership of a - command name, or about which package is responsible for a bug that - both maintainers agree is a bug, or about who should be the - maintainer for a package) the technical committee may decide the - matter.</p> - </li> - - <li> - <p>Make a decision when asked to do so.</p> - - <p>Any person or body may delegate a decision of their own to the - Technical Committee, or seek advice from it.</p> - </li> - - <li> - <p>Overrule a Developer (requires a 3:1 majority).</p> - - <p>The Technical Committee may ask a Developer to take a - particular technical course of action even if the Developer does - not wish to; this requires a 3:1 majority. For example, the - Committee may determine that a complaint made by the submitter of a - bug is justified and that the submitter's proposed solution should - be implemented.</p> - </li> - - <li> - <p>Offer advice.</p> - - <p>The Technical Committee may make formal announcements about its - views on any matter. <cite>Individual members may of course make - informal statements about their views and about the likely views of - the committee.</cite></p> - </li> - - <li> - <p>Together with the Project Leader, appoint new members to itself - or remove existing members. (See §6.2.)</p> - </li> - - <li> - <p>Appoint the Chairman of the Technical Committee.</p> - - <p> - The Chairman is elected by the Committee from its members. All - members of the committee are automatically nominated; the - committee votes starting one week before the post will become - vacant (or immediately, if it is already too late). The members - may vote by public acclamation for any fellow committee member, - including themselves; there is no default option. The vote - finishes when all the members have voted, or when the voting - period has ended. The result is determined using the method - specified in section A.6 of the Standard Resolution Procedure. - </p> - </li> - - <li> - <p>The Chairman can stand in for the Leader, together with the - Secretary</p> - - <p>As detailed in §7.1(2), the Chairman of the Technical - Committee and the Project Secretary may together stand in for the - Leader if there is no Leader.</p> - </li> -</ol> - -<h3>6.2. Composition</h3> - -<ol> - <li> - <p>The Technical Committee consists of up to 8 Developers, and - should usually have at least 4 members.</p> - </li> - - <li> - <p>When there are fewer than 8 members the Technical Committee may - recommend new member(s) to the Project Leader, who may choose - (individually) to appoint them or not.</p> - </li> - - <li> - <p>When there are 5 members or fewer the Technical Committee may - appoint new member(s) until the number of members reaches 6.</p> - </li> - - <li> - <p>When there have been 5 members or fewer for at least one week - the Project Leader may appoint new member(s) until the number of - members reaches 6, at intervals of at least one week per - appointment.</p> - </li> - - <li> - <p>A Developer is not eligible to be (re)appointed to the Technical - Committee if they have been a member within the previous 12 - months.</p> - </li> - - <li> - <p>If the Technical Committee and the Project Leader agree they - may remove or replace an existing member of the Technical - Committee.</p> - </li> - - <li> - <p>Term limit:</p> - <ol> - <li> - <p>On January 1st of each year the term of any Committee member - who has served more than 42 months (3.5 years) and who is one - of the two most senior members is set to expire on December - 31st of that year.</p> - </li> - <li> - <p>A member of the Technical Committee is said to be more - senior than another if they were appointed earlier, or were - appointed at the same time and have been a member of the - Debian Project longer. In the event that a member has been - appointed more than once, only the most recent appointment is - relevant.</p> - </li> - </ol> - </li> -</ol> - -<h3>6.3. Procedure</h3> - -<ol> - <li> - <p>The Technical Committee uses the Standard Resolution - Procedure.</p> - - <p>A draft resolution or amendment may be proposed by any member - of the Technical Committee. There is no minimum discussion period; - the voting period lasts for up to one week, or until the outcome is - no longer in doubt. Members may change their votes. There is a - quorum of two.</p> - </li> - - <li> - <p>Details regarding voting</p> - - <p>The Chairman has a casting vote. When the Technical Committee - votes whether to override a Developer who also happens to be a - member of the Committee, that member may not vote (unless they are - the Chairman, in which case they may use only their casting - vote).</p> - </li> - - <li> - <p>Public discussion and decision-making.</p> - - <p>Discussion, draft resolutions and amendments, and votes by - members of the committee, are made public on the Technical - Committee public discussion list. There is no separate secretary - for the Committee.</p> - </li> - - <li> - <p>Confidentiality of appointments.</p> - - <p>The Technical Committee may hold confidential discussions via - private email or a private mailing list or other means to discuss - appointments to the Committee. However, votes on appointments must - be public.</p> - </li> - - <li> - <p>No detailed design work.</p> - - <p>The Technical Committee does not engage in design of new - proposals and policies. Such design work should be carried out by - individuals privately or together and discussed in ordinary - technical policy and design forums.</p> - - <p>The Technical Committee restricts itself to choosing from or - adopting compromises between solutions and decisions which have - been proposed and reasonably thoroughly discussed elsewhere.</p> - - <p><cite>Individual members of the technical committee may of - course participate on their own behalf in any aspect of design and - policy work.</cite></p> - </li> - - <li> - <p>Technical Committee makes decisions only as last resort.</p> - - <p>The Technical Committee does not make a technical decision - until efforts to resolve it via consensus have been tried and - failed, unless it has been asked to make a decision by the person - or body who would normally be responsible for it.</p> - </li> -</ol> - -<toc-add-entry name="item-7">7. The Project Secretary</toc-add-entry> - -<h3>7.1. Powers</h3> - -<p>The <a href="secretary">Secretary</a>:</p> - -<ol> - <li> - <p>Takes votes amongst the Developers, and determines the number - and identity of Developers, whenever this is required by the - constitution.</p> - </li> - - <li> - <p>Can stand in for the Leader, together with the Chairman of the - Technical Committee.</p> - - <p>If there is no Project Leader then the Chairman of the - Technical Committee and the Project Secretary may by joint - agreement make decisions if they consider it imperative to do - so.</p> - </li> - - <li> - <p>Adjudicates any disputes about interpretation of the - constitution.</p> - </li> - - <li> - <p>May delegate part or all of their authority to someone else, or - withdraw such a delegation at any time.</p> - </li> -</ol> - -<h3>7.2. Appointment</h3> - -<p>The Project Secretary is appointed by the Project Leader and the -current Project Secretary.</p> - -<p>If the Project Leader and the current Project Secretary cannot agree -on a new appointment, they must ask the Developers by way of -General Resolution to appoint a Secretary.</p> - -<p>If there is no Project Secretary or the current Secretary is -unavailable and has not delegated authority for a decision then the -decision may be made or delegated by the Chairman of the Technical -Committee, as Acting Secretary.</p> - -<p>The Project Secretary's term of office is 1 year, at which point -they or another Secretary must be (re)appointed.</p> - -<h3>7.3. Procedure</h3> - -<p>The Project Secretary should make decisions which are fair and -reasonable, and preferably consistent with the consensus of the -Developers.</p> - -<p>When acting together to stand in for an absent Project Leader the -Chairman of the Technical Committee and the Project Secretary should -make decisions only when absolutely necessary and only when consistent -with the consensus of the Developers.</p> - -<toc-add-entry name="item-8">8. The Project Leader's Delegates</toc-add-entry> - -<h3>8.1. Powers</h3> - -<p>The Project Leader's Delegates:</p> - -<ol> - <li>have powers delegated to them by the Project Leader;</li> - - <li>may make certain decisions which the Leader may not make - directly, including approving or expelling Developers or designating - people as Developers who do not maintain packages. <cite>This is to - avoid concentration of power, particularly over membership as a - Developer, in the hands of the Project Leader.</cite></li> -</ol> - -<h3>8.2. Appointment</h3> - -<p>The Delegates are appointed by the Project Leader and may be -replaced by the Leader at the Leader's discretion. The Project Leader -may not make the position as a Delegate conditional on particular -decisions by the Delegate, nor may they override a decision made by a -Delegate once made.</p> - -<h3>8.3. Procedure</h3> - -<p>Delegates may make decisions as they see fit, but should attempt to -implement good technical decisions and/or follow consensus opinion.</p> - -<toc-add-entry name="item-9">9. Assets held in trust for Debian</toc-add-entry> - -<p>In most jurisdictions around the world, the Debian project is not -in a position to directly hold funds or other property. Therefore, -property has to be owned by any of a number of organisations as -detailed in §9.2.</p> - -<p>Traditionally, SPI was the sole organisation authorized to hold -property and monies for the Debian Project. SPI was created in -the U.S. to hold money in trust there.</p> - -<p><a href="https://www.spi-inc.org/">SPI</a> and Debian are separate -organisations who share some goals. -Debian is grateful for the legal support framework offered by SPI.</p> - -<h3>9.1. Relationship with Associated Organizations</h3> - -<ol> - <li> - <p>Debian Developers do not become agents or employees of - organisations holding assets in trust for Debian, or of - each other, or of persons in authority in the Debian Project, - solely by the virtue of being Debian Developers. A person - acting as a Developer does so as an individual, on their own - behalf. Such organisations may, of their own accord, - establish relationships with individuals who are also Debian - developers.</p> - </li> -</ol> - -<h3>9.2. Authority</h3> - -<ol> - <li> - <p>An organisation holding assets for Debian has no authority - regarding Debian's technical or nontechnical decisions, except - that no decision by Debian with respect to any property held - by the organisation shall require it to act outside its legal - authority.</p> - </li> - <li> - <p>Debian claims no authority over an organisation that holds - assets for Debian other than that over the use of property - held in trust for Debian.</p> - </li> -</ol> - -<h3>9.3. Trusted organisations</h3> - -<p>Any donations for the Debian Project must be made to any one of a -set of organisations designated by the Project leader (or a -delegate) to be authorized to handle assets to be used for the -Debian Project.</p> - -<p>Organisations holding assets in trust for Debian should -undertake reasonable obligations for the handling of such -assets.</p> - -<p>Debian maintains a public List of Trusted Organisations that -accept donations and hold assets in trust for Debian -(including both tangible property and intellectual property) -that includes the commitments those organisations have made as -to how those assets will be handled.</p> - -<toc-add-entry name="item-A">A. Standard Resolution Procedure</toc-add-entry> - -<p>These rules apply to communal decision-making by committees and -plebiscites, where stated above.</p> - -<h3>A.1. Proposal</h3> - -<p>The formal procedure begins when a draft resolution is proposed and -sponsored, as required.</p> - -<h3>A.1. Discussion and Amendment</h3> - -<ol> - <li>Following the proposal, the resolution may be discussed. - Amendments may be made formal by being proposed and sponsored - according to the requirements for a new resolution, or directly by - the proposer of the original resolution.</li> - - <li>A formal amendment may be accepted by the resolution's proposer, - in which case the formal resolution draft is immediately changed to - match.</li> - - <li>If a formal amendment is not accepted, or one of the sponsors of - the resolution does not agree with the acceptance by the proposer of - a formal amendment, the amendment remains as an amendment and will be - voted on.</li> - - <li>If an amendment accepted by the original proposer is not to the - liking of others, they may propose another amendment to reverse the - earlier change (again, they must meet the requirements for proposer - and sponsor(s).)</li> - - <li>The proposer of a resolution may suggest changes to the wordings - of amendments; these take effect if the proposer of the amendment - agrees and none of the sponsors object. In this case the changed - amendments will be voted on instead of the originals.</li> - - <li>The proposer of a resolution may make changes to correct minor - errors (for example, typographical errors or inconsistencies) or - changes which do not alter the meaning, providing noone objects - within 24 hours. In this case the minimum discussion period is not - restarted.</li> -</ol> - -<h3>A.2. Calling for a vote</h3> - -<ol> - <li>The proposer or a sponsor of a motion or an amendment may call - for a vote, providing that the minimum discussion period (if any) has - elapsed.</li> - - <li> - The proposer or any sponsor of a resolution may call for a vote on that - resolution and all related amendments. - </li> - - <li>The person who calls for a vote states what they believe the - wordings of the resolution and any relevant amendments are, and - consequently what form the ballot should take. However, the final - decision on the form of ballot(s) is the Secretary's - see 7.1(1), - 7.1(3) and A.3(4).</li> - - <li> - The minimum discussion period is counted from the time the last - formal amendment was accepted, or since the whole resolution - was proposed if no amendments have been proposed and accepted. - </li> -</ol> - -<h3>A.3. Voting procedure</h3> - -<ol> - <li> - Each resolution and its related amendments is voted on in a - single ballot that includes an option for the original - resolution, each amendment, and the default option (where - applicable). - </li> - - <li> - The default option must not have any supermajority requirements. - Options which do not have an explicit supermajority requirement - have a 1:1 majority requirement. - </li> - - <li> - The votes are counted according to the rules in A.6. The - default option is <q>Further Discussion</q>, unless specified - otherwise. - </li> - - <li>In cases of doubt the Project Secretary shall decide on matters - of procedure.</li> -</ol> - -<h3>A.4. Withdrawing resolutions or unaccepted amendments</h3> - -<p>The proposer of a resolution or unaccepted amendment may withdraw -it. In this case new proposers may come forward keep it alive, in which -case the first person to do so becomes the new proposer and any others -become sponsors if they aren't sponsors already.</p> - -<p>A sponsor of a resolution or amendment (unless it has been -accepted) may withdraw.</p> - -<p>If the withdrawal of the proposer and/or sponsors means that a -resolution has no proposer or not enough sponsors it will not be voted -on unless this is rectified before the resolution expires.</p> - -<h3>A.5. Expiry</h3> - -<p> - If a proposed resolution has not been discussed, amended, voted on or - otherwise dealt with for 4 weeks the secretary may issue a statement - that the issue is being withdrawn. If none of the sponsors of any - of the proposals object within a week, the issue is withdrawn. -</p> - -<p> - The secretary may also include suggestions on how to proceed, - if appropriate. -</p> - -<h3>A.6. Vote Counting</h3> - -<ol> - <li> Each voter's ballot ranks the options being voted on. Not all - options need be ranked. Ranked options are considered - preferred to all unranked options. Voters may rank options - equally. Unranked options are considered to be ranked equally - with one another. Details of how ballots may be filled out - will be included in the Call For Votes. - </li> - <li> If the ballot has a quorum requirement R any options other - than the default option which do not receive at least R votes - ranking that option above the default option are dropped from - consideration. - </li> - <li> Any (non-default) option which does not defeat the default option - by its required majority ratio is dropped from consideration. - <ol> - <li> - Given two options A and B, V(A,B) is the number of voters - who prefer option A over option B. - </li> - <li> - An option A defeats the default option D by a majority - ratio N, if V(A,D) is strictly greater than N * V(D,A). - </li> - <li> - If a supermajority of S:1 is required for A, its majority ratio - is S; otherwise, its majority ratio is 1. - </li> - </ol> - </li> - <li> From the list of undropped options, we generate a list of - pairwise defeats. - <ol> - <li> - An option A defeats an option B, if V(A,B) is strictly greater - than V(B,A). - </li> - </ol> - </li> - <li> From the list of [undropped] pairwise defeats, we generate a - set of transitive defeats. - <ol> - <li> - An option A transitively defeats an option C if A defeats - C or if there is some other option B where A defeats B AND - B transitively defeats C. - </li> - </ol> - </li> - <li> We construct the Schwartz set from the set of transitive defeats. - <ol> - <li> - An option A is in the Schwartz set if for all options B, - either A transitively defeats B, or B does not transitively - defeat A. - </li> - </ol> - </li> - <li> If there are defeats between options in the Schwartz set, - we drop the weakest such defeats from the list of pairwise - defeats, and return to step 5. - <ol> - <li> - A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) - is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if - V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B). - </li> - <li> - A weakest defeat is a defeat that has no other defeat weaker - than it. There may be more than one such defeat. - </li> - </ol> - </li> - <li> If there are no defeats within the Schwartz set, then the winner - is chosen from the options in the Schwartz set. If there is - only one such option, it is the winner. If there are multiple - options, the elector with the casting vote chooses which of those - options wins. - </li> -</ol> - -<p> - <strong>Note:</strong> Options which the voters rank above the default option - are options they find acceptable. Options ranked below the default - options are options they find unacceptable. -</p> - -<p><cite>When the Standard Resolution Procedure is to be used, the text -which refers to it must specify what is sufficient to have a draft -resolution proposed and/or sponsored, what the minimum discussion -period is, and what the voting period is. It must also specify any -supermajority and/or the quorum (and default option) to be -used.</cite></p> - -<toc-add-entry name="item-B">B. Use of language and typography</toc-add-entry> - -<p>The present indicative (<q>is</q>, for example) means that the statement -is a rule in this constitution. <q>May</q> or <q>can</q> indicates that the -person or body has discretion. <q>Should</q> means that it would be -considered a good thing if the sentence were obeyed, but it is not -binding. <cite>Text marked as a citation, such as this, is rationale -and does not form part of the constitution. It may be used only to aid -interpretation in cases of doubt.</cite></p> diff --git a/greek/devel/constitution.1.6.wml b/greek/devel/constitution.1.6.wml deleted file mode 100644 index 8c5bcc9f9e4..00000000000 --- a/greek/devel/constitution.1.6.wml +++ /dev/null @@ -1,1001 +0,0 @@ -#use wml::debian::template title="Historical Debian Constitution v 1.6" BARETITLE="true" -#use wml::debian::toc -#use wml::debian::translation-check translation="e3d525d9f092f9014e00417cc847900ac5a99649" maintainer="galaxico" - -<h1>Historical version of the Constitution for the Debian Project (v1.6)</h1> - -<p>Version 1.6 ratified on December 13th, 2015. Supersedes -<a href="constitution.1.5">Version 1.5</a> ratified on January 9th, 2015, -<a href="constitution.1.4">Version 1.4</a> ratified on October 7th, 2007, -<a href="constitution.1.3">Version 1.3</a> ratified on September 24th, -2006, -<a href="constitution.1.2">Version 1.2</a> ratified on October 29th, -2003 and -<a href="constitution.1.1">Version 1.1</a> ratified on June 21st, -2003, which itself supersedes <a href="constitution.1.0">Version 1.0</a> -ratified on December 2nd, 1998. -Superseded by the <a href="constitution">current version 1.7</a>, -ratified on August 14th, 2016. -</p> - -<toc-display /> - -<toc-add-entry name="item-1">1. Introduction</toc-add-entry> - -<p><cite>The Debian Project is an association of individuals who have -made common cause to create a free operating system.</cite></p> - -<p>This document describes the organisational structure for formal -decision-making in the Project. It does not describe the goals of the -Project or how it achieves them, or contain any policies except those -directly related to the decision-making process.</p> - -<toc-add-entry name="item-2">2. Decision-making bodies and individuals</toc-add-entry> - -<p>Each decision in the Project is made by one or more of the -following:</p> - -<ol> - <li>The Developers, by way of General Resolution or an election;</li> - - <li>The Project Leader;</li> - - <li>The Technical Committee and/or its Chairman;</li> - - <li>The individual Developer working on a particular task;</li> - - <li>Delegates appointed by the Project Leader for specific - tasks;</li> - - <li>The Project Secretary.</li> -</ol> - -<p>Most of the remainder of this document will outline the powers of -these bodies, their composition and appointment, and the procedure for -their decision-making. The powers of a person or body may be subject to -review and/or limitation by others; in this case the reviewing body or -person's entry will state this. <cite>In the list above, a person or -body is usually listed before any people or bodies whose decisions they -can overrule or who they (help) appoint - but not everyone listed -earlier can overrule everyone listed later.</cite></p> - -<h3>2.1. General rules</h3> - -<ol> - <li> - <p>Nothing in this constitution imposes an obligation on anyone to - do work for the Project. A person who does not want to do a task - which has been delegated or assigned to them does not need to do - it. However, they must not actively work against these rules and - decisions properly made under them.</p> - </li> - - <li> - <p>A person may hold several posts, except that the Project Leader, - Project Secretary and the Chairman of the Technical Committee must - be distinct, and that the Leader cannot appoint themselves as their - own Delegate.</p> - </li> - - <li> - <p>A person may leave the Project or resign from a particular post - they hold, at any time, by stating so publicly.</p> - </li> -</ol> - -<toc-add-entry name="item-3">3. Individual Developers</toc-add-entry> - -<h3>3.1. Powers</h3> - -<p>An individual Developer may</p> - -<ol> - <li>make any technical or nontechnical decision with regard to their - own work;</li> - - <li>propose or sponsor draft General Resolutions;</li> - - <li>propose themselves as a Project Leader candidate in - elections;</li> - - <li>vote on General Resolutions and in Leadership elections.</li> -</ol> - -<h3>3.2. Composition and appointment</h3> - -<ol> - <li> - <p>Developers are volunteers who agree to further the aims of the - Project insofar as they participate in it, and who maintain - package(s) for the Project or do other work which the Project - Leader's Delegate(s) consider worthwhile.</p> - </li> - - <li> - <p>The Project Leader's Delegate(s) may choose not to admit new - Developers, or expel existing Developers. <cite>If the Developers - feel that the Delegates are abusing their authority they can of - course override the decision by way of General Resolution - see - §4.1(3), §4.2.</cite></p> - </li> -</ol> - -<h3>3.3. Procedure</h3> - -<p>Developers may make these decisions as they see fit.</p> - -<toc-add-entry name="item-4">4. The Developers by way of General Resolution or election</toc-add-entry> - -<h3>4.1. Powers</h3> - -<p>Together, the Developers may:</p> - -<ol> - <li> - <p>Appoint or recall the Project Leader.</p> - </li> - - <li> - <p>Amend this constitution, provided they agree with a 3:1 - majority.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Project - Leader or a Delegate.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Technical - Committee, provided they agree with a 2:1 majority.</p> - </li> - - <li> - <p>Issue, supersede and withdraw nontechnical policy documents and - statements.</p> - - <p>These include documents describing the goals of the project, its - relationship with other free software entities, and nontechnical - policies such as the free software licence terms that Debian - software must meet.</p> - - <p>They may also include position statements about issues of the - day.</p> - - <ol style="list-style: decimal;"> - <li>A Foundation Document is a document or statement regarded as - critical to the Project's mission and purposes.</li> - <li>The Foundation Documents are the works entitled <q>Debian - Social Contract</q> and <q>Debian Free Software Guidelines</q>.</li> - <li>A Foundation Document requires a 3:1 majority for its - supersession. New Foundation Documents are issued and - existing ones withdrawn by amending the list of Foundation - Documents in this constitution.</li> - </ol> - - </li> - - <li> - <p>Make decisions about property held in trust for purposes - related to Debian. (See §9.).</p> - </li> - - <li> - <p>In case of a disagreement between the project leader and - the incumbent secretary, appoint a new secretary.</p> - </li> -</ol> - -<h3>4.2. Procedure</h3> - -<ol> - <li> - <p>The Developers follow the Standard Resolution Procedure, below. - A resolution or amendment is introduced if proposed by any - Developer and sponsored by at least K other Developers, or if - proposed by the Project Leader or the Technical Committee.</p> - </li> - - <li> - <p>Delaying a decision by the Project Leader or their Delegate:</p> - - <ol> - <li>If the Project Leader or their Delegate, or the Technical - Committee, has made a decision, then Developers can override them - by passing a resolution to do so; see §4.1(3).</li> - - <li>If such a resolution is sponsored by at least 2K Developers, - or if it is proposed by the Technical Committee, the resolution - puts the decision immediately on hold (provided that resolution - itself says so).</li> - - <li>If the original decision was to change a discussion period or - a voting period, or the resolution is to override the Technical - Committee, then only K Developers need to sponsor the resolution - to be able to put the decision immediately on hold.</li> - - <li>If the decision is put on hold, an immediate vote is held to - determine whether the decision will stand until the full vote on - the decision is made or whether the implementation of the - original decision will be delayed until then. There is no - quorum for this immediate procedural vote.</li> - - <li>If the Project Leader (or the Delegate) withdraws the - original decision, the vote becomes moot, and is no longer - conducted.</li> - </ol> - </li> - - <li> - <p> - Votes are taken by the Project Secretary. Votes, tallies, and - results are not revealed during the voting period; after the - vote the Project Secretary lists all the votes cast. The voting - period is 2 weeks, but may be varied by up to 1 week by the - Project Leader. - </p> - </li> - - <li> - <p>The minimum discussion period is 2 weeks, but may be varied by - up to 1 week by the Project Leader. The Project Leader has a - casting vote. There is a quorum of 3Q.</p> - </li> - - <li> - <p>Proposals, sponsors, amendments, calls for votes and other - formal actions are made by announcement on a publicly-readable - electronic mailing list designated by the Project Leader's - Delegate(s); any Developer may post there.</p> - </li> - - <li> - <p>Votes are cast by email in a manner suitable to the Secretary. - The Secretary determines for each poll whether voters can change - their votes.</p> - </li> - - <li> - <p>Q is half of the square root of the number of current - Developers. K is Q or 5, whichever is the smaller. Q and K need not - be integers and are not rounded.</p> - </li> -</ol> - -<toc-add-entry name="item-5">5. Project Leader</toc-add-entry> - -<h3>5.1. Powers</h3> - -<p>The <a href="leader">Project Leader</a> may:</p> - -<ol> - <li> - <p>Appoint Delegates or delegate decisions to the Technical - Committee.</p> - - <p>The Leader may define an area of ongoing responsibility or a - specific decision and hand it over to another Developer or to the - Technical Committee.</p> - - <p>Once a particular decision has been delegated and made the - Project Leader may not withdraw that delegation; however, they may - withdraw an ongoing delegation of particular area of - responsibility.</p> - </li> - - <li> - <p>Lend authority to other Developers.</p> - - <p>The Project Leader may make statements of support for points of - view or for other members of the project, when asked or otherwise; - these statements have force if and only if the Leader would be - empowered to make the decision in question.</p> - </li> - - <li> - <p>Make any decision which requires urgent action.</p> - - <p>This does not apply to decisions which have only become - gradually urgent through lack of relevant action, unless there is a - fixed deadline.</p> - </li> - - <li> - <p>Make any decision for whom noone else has responsibility.</p> - </li> - - <li> - <p>Propose draft General Resolutions and amendments.</p> - </li> - - <li> - <p>Together with the Technical Committee, appoint new members to - the Committee. (See §6.2.)</p> - </li> - - <li> - <p>Use a casting vote when Developers vote.</p> - - <p>The Project Leader also has a normal vote in such ballots.</p> - </li> - - <li> - <p>Vary the discussion period for Developers' votes (as above).</p> - </li> - - <li> - <p>Lead discussions amongst Developers.</p> - - <p>The Project Leader should attempt to participate in discussions - amongst the Developers in a helpful way which seeks to bring the - discussion to bear on the key issues at hand. The Project Leader - should not use the Leadership position to promote their own - personal views.</p> - </li> - - <li> - <p>In consultation with the developers, make decisions affecting - property held in trust for purposes related to Debian. (See - §9.). Such decisions are communicated to the members by the - Project Leader or their Delegate(s). Major expenditures - should be proposed and debated on the mailing list before - funds are disbursed.</p> - </li> - <li> - <p>Add or remove organizations from the list of trusted - organizations (see §9.3) that are authorized to accept and - hold assets for Debian. The evaluation and discussion leading - up to such a decision occurs on an electronic mailing list - designated by the Project Leader or their Delegate(s), on - which any developer may post. There is a minimum discussion - period of two weeks before an organization may be added to - the list of trusted organizations.</p> - </li> -</ol> - -<h3>5.2. Appointment</h3> - -<ol> - <li>The Project Leader is elected by the Developers.</li> - - <li>The election begins six weeks before the leadership post becomes - vacant, or (if it is too late already) immediately.</li> - - <li>For the first week any Developer may nominate - themselves as a candidate Project Leader, and summarize their plans for their term.</li> - - <li>For three weeks after that no more candidates may be nominated; - candidates should use this time for campaigning and discussion. If - there are no candidates at the end of the nomination period then the - nomination period is extended for an additional week, repeatedly if - necessary.</li> - - <li>The next two weeks are the polling period during which - Developers may cast their votes. Votes in leadership elections are - kept secret, even after the election is finished.</li> - - <li>The options on the ballot will be those candidates who have - nominated themselves and have not yet withdrawn, plus None Of The - Above. If None Of The Above wins the election then the election - procedure is repeated, many times if necessary.</li> - - <li> - The decision will be made using the method specified in section - §A.6 of the Standard Resolution Procedure. The quorum is the - same as for a General Resolution (§4.2) and the default - option is <q>None Of The Above</q>. - </li> - - <li>The Project Leader serves for one year from their election.</li> -</ol> - -<h3>5.3. Procedure</h3> - -<p>The Project Leader should attempt to make decisions which are -consistent with the consensus of the opinions of the Developers.</p> - -<p>Where practical the Project Leader should informally solicit the -views of the Developers.</p> - -<p>The Project Leader should avoid overemphasizing their own point of -view when making decisions in their capacity as Leader.</p> - -<toc-add-entry name="item-6">6. Technical committee</toc-add-entry> - -<h3>6.1. Powers</h3> - -<p>The <a href="tech-ctte">Technical Committee</a> may:</p> - -<ol> - <li> - <p>Decide on any matter of technical policy.</p> - - <p>This includes the contents of the technical policy manuals, - developers' reference materials, example packages and the behaviour - of non-experimental package building tools. (In each case the usual - maintainer of the relevant software or documentation makes - decisions initially, however; see 6.3(5).)</p> - </li> - - <li> - <p>Decide any technical matter where Developers' jurisdictions - overlap.</p> - - <p>In cases where Developers need to implement compatible - technical policies or stances (for example, if they disagree about - the priorities of conflicting packages, or about ownership of a - command name, or about which package is responsible for a bug that - both maintainers agree is a bug, or about who should be the - maintainer for a package) the technical committee may decide the - matter.</p> - </li> - - <li> - <p>Make a decision when asked to do so.</p> - - <p>Any person or body may delegate a decision of their own to the - Technical Committee, or seek advice from it.</p> - </li> - - <li> - <p>Overrule a Developer (requires a 3:1 majority).</p> - - <p>The Technical Committee may ask a Developer to take a - particular technical course of action even if the Developer does - not wish to; this requires a 3:1 majority. For example, the - Committee may determine that a complaint made by the submitter of a - bug is justified and that the submitter's proposed solution should - be implemented.</p> - </li> - - <li> - <p>Offer advice.</p> - - <p>The Technical Committee may make formal announcements about its - views on any matter. <cite>Individual members may of course make - informal statements about their views and about the likely views of - the committee.</cite></p> - </li> - - <li> - <p>Together with the Project Leader, appoint new members to itself - or remove existing members. (See §6.2.)</p> - </li> - - <li> - <p>Appoint the Chairman of the Technical Committee.</p> - - <p> - The Chairman is elected by the Committee from its members. All - members of the committee are automatically nominated; the - committee votes starting one week before the post will become - vacant (or immediately, if it is already too late). The members - may vote by public acclamation for any fellow committee member, - including themselves; there is no default option. The vote - finishes when all the members have voted, or when the voting - period has ended. The result is determined using the method - specified in section A.6 of the Standard Resolution Procedure. - </p> - </li> - - <li> - <p>The Chairman can stand in for the Leader, together with the - Secretary</p> - - <p>As detailed in §7.1(2), the Chairman of the Technical - Committee and the Project Secretary may together stand in for the - Leader if there is no Leader.</p> - </li> -</ol> - -<h3>6.2. Composition</h3> - -<ol> - <li> - <p>The Technical Committee consists of up to 8 Developers, and - should usually have at least 4 members.</p> - </li> - - <li> - <p>When there are fewer than 8 members the Technical Committee may - recommend new member(s) to the Project Leader, who may choose - (individually) to appoint them or not.</p> - </li> - - <li> - <p>When there are 5 members or fewer the Technical Committee may - appoint new member(s) until the number of members reaches 6.</p> - </li> - - <li> - <p>When there have been 5 members or fewer for at least one week - the Project Leader may appoint new member(s) until the number of - members reaches 6, at intervals of at least one week per - appointment.</p> - </li> - - <li> - <p>A Developer is not eligible to be (re)appointed to the Technical - Committee if they have been a member within the previous 12 - months.</p> - </li> - - <li> - <p>If the Technical Committee and the Project Leader agree they - may remove or replace an existing member of the Technical - Committee.</p> - </li> - - <li> - <p>Term limit:</p> - <ol> - <li> - <p>On January 1st of each year the term of any Committee member - who has served more than 42 months (3.5 years) and who is one - of the two most senior members is set to expire on December - 31st of that year.</p> - </li> - <li> - <p>A member of the Technical Committee is said to be more - senior than another if they were appointed earlier, or were - appointed at the same time and have been a member of the - Debian Project longer. In the event that a member has been - appointed more than once, only the most recent appointment is - relevant.</p> - </li> - </ol> - </li> -</ol> - -<h3>6.3. Procedure</h3> - -<ol> - <li> - <p>The Technical Committee uses the Standard Resolution - Procedure.</p> - - <p>A draft resolution or amendment may be proposed by any member - of the Technical Committee. There is no minimum discussion period; - the voting period lasts for up to one week, or until the outcome is - no longer in doubt. Members may change their votes. There is a - quorum of two.</p> - </li> - - <li> - <p>Details regarding voting</p> - - <p>The Chairman has a casting vote. When the Technical Committee - votes whether to override a Developer who also happens to be a - member of the Committee, that member may not vote (unless they are - the Chairman, in which case they may use only their casting - vote).</p> - </li> - - <li> - <p>Public discussion and decision-making.</p> - - <p>Discussion, draft resolutions and amendments, and votes by - members of the committee, are made public on the Technical - Committee public discussion list. There is no separate secretary - for the Committee.</p> - </li> - - <li> - <p>Confidentiality of appointments.</p> - - <p>The Technical Committee may hold confidential discussions via - private email or a private mailing list or other means to discuss - appointments to the Committee. However, votes on appointments must - be public.</p> - </li> - - <li> - <p>No detailed design work.</p> - - <p>The Technical Committee does not engage in design of new - proposals and policies. Such design work should be carried out by - individuals privately or together and discussed in ordinary - technical policy and design forums.</p> - - <p>The Technical Committee restricts itself to choosing from or - adopting compromises between solutions and decisions which have - been proposed and reasonably thoroughly discussed elsewhere.</p> - - <p><cite>Individual members of the technical committee may of - course participate on their own behalf in any aspect of design and - policy work.</cite></p> - </li> - - <li> - <p>Technical Committee makes decisions only as last resort.</p> - - <p>The Technical Committee does not make a technical decision - until efforts to resolve it via consensus have been tried and - failed, unless it has been asked to make a decision by the person - or body who would normally be responsible for it.</p> - </li> -</ol> - -<toc-add-entry name="item-7">7. The Project Secretary</toc-add-entry> - -<h3>7.1. Powers</h3> - -<p>The <a href="secretary">Secretary</a>:</p> - -<ol> - <li> - <p>Takes votes amongst the Developers, and determines the number - and identity of Developers, whenever this is required by the - constitution.</p> - </li> - - <li> - <p>Can stand in for the Leader, together with the Chairman of the - Technical Committee.</p> - - <p>If there is no Project Leader then the Chairman of the - Technical Committee and the Project Secretary may by joint - agreement make decisions if they consider it imperative to do - so.</p> - </li> - - <li> - <p>Adjudicates any disputes about interpretation of the - constitution.</p> - </li> - - <li> - <p>May delegate part or all of their authority to someone else, or - withdraw such a delegation at any time.</p> - </li> -</ol> - -<h3>7.2. Appointment</h3> - -<p>The Project Secretary is appointed by the Project Leader and the -current Project Secretary.</p> - -<p>If the Project Leader and the current Project Secretary cannot agree -on a new appointment, they must ask the Developers by way of -General Resolution to appoint a Secretary.</p> - -<p>If there is no Project Secretary or the current Secretary is -unavailable and has not delegated authority for a decision then the -decision may be made or delegated by the Chairman of the Technical -Committee, as Acting Secretary.</p> - -<p>The Project Secretary's term of office is 1 year, at which point -they or another Secretary must be (re)appointed.</p> - -<h3>7.3. Procedure</h3> - -<p>The Project Secretary should make decisions which are fair and -reasonable, and preferably consistent with the consensus of the -Developers.</p> - -<p>When acting together to stand in for an absent Project Leader the -Chairman of the Technical Committee and the Project Secretary should -make decisions only when absolutely necessary and only when consistent -with the consensus of the Developers.</p> - -<toc-add-entry name="item-8">8. The Project Leader's Delegates</toc-add-entry> - -<h3>8.1. Powers</h3> - -<p>The Project Leader's Delegates:</p> - -<ol> - <li>have powers delegated to them by the Project Leader;</li> - - <li>may make certain decisions which the Leader may not make - directly, including approving or expelling Developers or designating - people as Developers who do not maintain packages. <cite>This is to - avoid concentration of power, particularly over membership as a - Developer, in the hands of the Project Leader.</cite></li> -</ol> - -<h3>8.2. Appointment</h3> - -<p>The Delegates are appointed by the Project Leader and may be -replaced by the Leader at the Leader's discretion. The Project Leader -may not make the position as a Delegate conditional on particular -decisions by the Delegate, nor may they override a decision made by a -Delegate once made.</p> - -<h3>8.3. Procedure</h3> - -<p>Delegates may make decisions as they see fit, but should attempt to -implement good technical decisions and/or follow consensus opinion.</p> - -<toc-add-entry name="item-9">9. Assets held in trust for Debian</toc-add-entry> - -<p>In most jurisdictions around the world, the Debian project is not -in a position to directly hold funds or other property. Therefore, -property has to be owned by any of a number of organisations as -detailed in §9.2.</p> - -<p>Traditionally, SPI was the sole organisation authorized to hold -property and monies for the Debian Project. SPI was created in -the U.S. to hold money in trust there.</p> - -<p><a href="https://www.spi-inc.org/">SPI</a> and Debian are separate -organisations who share some goals. -Debian is grateful for the legal support framework offered by SPI.</p> - -<h3>9.1. Relationship with Associated Organizations</h3> - -<ol> - <li> - <p>Debian Developers do not become agents or employees of - organisations holding assets in trust for Debian, or of - each other, or of persons in authority in the Debian Project, - solely by the virtue of being Debian Developers. A person - acting as a Developer does so as an individual, on their own - behalf. Such organisations may, of their own accord, - establish relationships with individuals who are also Debian - developers.</p> - </li> -</ol> - -<h3>9.2. Authority</h3> - -<ol> - <li> - <p>An organisation holding assets for Debian has no authority - regarding Debian's technical or nontechnical decisions, except - that no decision by Debian with respect to any property held - by the organisation shall require it to act outside its legal - authority.</p> - </li> - <li> - <p>Debian claims no authority over an organisation that holds - assets for Debian other than that over the use of property - held in trust for Debian.</p> - </li> -</ol> - -<h3>9.3. Trusted organisations</h3> - -<p>Any donations for the Debian Project must be made to any one of a -set of organisations designated by the Project leader (or a -delegate) to be authorized to handle assets to be used for the -Debian Project.</p> - -<p>Organisations holding assets in trust for Debian should -undertake reasonable obligations for the handling of such -assets.</p> - -<p>Debian maintains a public List of Trusted Organisations that -accept donations and hold assets in trust for Debian -(including both tangible property and intellectual property) -that includes the commitments those organisations have made as -to how those assets will be handled.</p> - -<toc-add-entry name="item-A">A. Standard Resolution Procedure</toc-add-entry> - -<p>These rules apply to communal decision-making by committees and -plebiscites, where stated above.</p> - -<h3>A.0. Proposal</h3> - -<p>The formal procedure begins when a draft resolution is proposed and -sponsored, as required.</p> - -<h3>A.1. Discussion and Amendment</h3> - -<ol> - <li>Following the proposal, the resolution may be discussed. - Amendments may be made formal by being proposed and sponsored - according to the requirements for a new resolution, or directly by - the proposer of the original resolution.</li> - - <li>A formal amendment may be accepted by the resolution's proposer, - in which case the formal resolution draft is immediately changed to - match.</li> - - <li>If a formal amendment is not accepted, or one of the sponsors of - the resolution does not agree with the acceptance by the proposer of - a formal amendment, the amendment remains as an amendment and will be - voted on.</li> - - <li>If an amendment accepted by the original proposer is not to the - liking of others, they may propose another amendment to reverse the - earlier change (again, they must meet the requirements for proposer - and sponsor(s).)</li> - - <li>The proposer of a resolution may suggest changes to the wordings - of amendments; these take effect if the proposer of the amendment - agrees and none of the sponsors object. In this case the changed - amendments will be voted on instead of the originals.</li> - - <li>The proposer of a resolution may make changes to correct minor - errors (for example, typographical errors or inconsistencies) or - changes which do not alter the meaning, providing noone objects - within 24 hours. In this case the minimum discussion period is not - restarted.</li> -</ol> - -<h3>A.2. Calling for a vote</h3> - -<ol> - <li>The proposer or a sponsor of a motion or an amendment may call - for a vote, providing that the minimum discussion period (if any) has - elapsed.</li> - - <li> - The proposer or any sponsor of a resolution may call for a vote on that - resolution and all related amendments. - </li> - - <li>The person who calls for a vote states what they believe the - wordings of the resolution and any relevant amendments are, and - consequently what form the ballot should take. However, the final - decision on the form of ballot(s) is the Secretary's - see 7.1(1), - 7.1(3) and A.3(4).</li> - - <li> - The minimum discussion period is counted from the time the last - formal amendment was accepted, or since the whole resolution - was proposed if no amendments have been proposed and accepted. - </li> -</ol> - -<h3>A.3. Voting procedure</h3> - -<ol> - <li> - Each resolution and its related amendments is voted on in a - single ballot that includes an option for the original - resolution, each amendment, and the default option (where - applicable). - </li> - - <li> - The default option must not have any supermajority requirements. - Options which do not have an explicit supermajority requirement - have a 1:1 majority requirement. - </li> - - <li> - The votes are counted according to the rules in A.6. The - default option is <q>Further Discussion</q>, unless specified - otherwise. - </li> - - <li>In cases of doubt the Project Secretary shall decide on matters - of procedure.</li> -</ol> - -<h3>A.4. Withdrawing resolutions or unaccepted amendments</h3> - -<p>The proposer of a resolution or unaccepted amendment may withdraw -it. In this case new proposers may come forward keep it alive, in which -case the first person to do so becomes the new proposer and any others -become sponsors if they aren't sponsors already.</p> - -<p>A sponsor of a resolution or amendment (unless it has been -accepted) may withdraw.</p> - -<p>If the withdrawal of the proposer and/or sponsors means that a -resolution has no proposer or not enough sponsors it will not be voted -on unless this is rectified before the resolution expires.</p> - -<h3>A.5. Expiry</h3> - -<p> - If a proposed resolution has not been discussed, amended, voted on or - otherwise dealt with for 4 weeks the secretary may issue a statement - that the issue is being withdrawn. If none of the sponsors of any - of the proposals object within a week, the issue is withdrawn. -</p> - -<p> - The secretary may also include suggestions on how to proceed, - if appropriate. -</p> - -<h3>A.6. Vote Counting</h3> - -<ol> - <li> Each voter's ballot ranks the options being voted on. Not all - options need be ranked. Ranked options are considered - preferred to all unranked options. Voters may rank options - equally. Unranked options are considered to be ranked equally - with one another. Details of how ballots may be filled out - will be included in the Call For Votes. - </li> - <li> If the ballot has a quorum requirement R any options other - than the default option which do not receive at least R votes - ranking that option above the default option are dropped from - consideration. - </li> - <li> Any (non-default) option which does not defeat the default option - by its required majority ratio is dropped from consideration. - <ol> - <li> - Given two options A and B, V(A,B) is the number of voters - who prefer option A over option B. - </li> - <li> - An option A defeats the default option D by a majority - ratio N, if V(A,D) is greater or equal to N * V(D,A) and V(A,D) is strictly greater than V(D,A). - </li> - <li> - If a supermajority of S:1 is required for A, its majority ratio - is S; otherwise, its majority ratio is 1. - </li> - </ol> - </li> - <li> From the list of undropped options, we generate a list of - pairwise defeats. - <ol> - <li> - An option A defeats an option B, if V(A,B) is strictly greater - than V(B,A). - </li> - </ol> - </li> - <li> From the list of [undropped] pairwise defeats, we generate a - set of transitive defeats. - <ol> - <li> - An option A transitively defeats an option C if A defeats - C or if there is some other option B where A defeats B AND - B transitively defeats C. - </li> - </ol> - </li> - <li> We construct the Schwartz set from the set of transitive defeats. - <ol> - <li> - An option A is in the Schwartz set if for all options B, - either A transitively defeats B, or B does not transitively - defeat A. - </li> - </ol> - </li> - <li> If there are defeats between options in the Schwartz set, - we drop the weakest such defeats from the list of pairwise - defeats, and return to step 5. - <ol> - <li> - A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) - is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if - V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B). - </li> - <li> - A weakest defeat is a defeat that has no other defeat weaker - than it. There may be more than one such defeat. - </li> - </ol> - </li> - <li> If there are no defeats within the Schwartz set, then the winner - is chosen from the options in the Schwartz set. If there is - only one such option, it is the winner. If there are multiple - options, the elector with the casting vote chooses which of those - options wins. - </li> -</ol> - -<p> - <strong>Note:</strong> Options which the voters rank above the default option - are options they find acceptable. Options ranked below the default - options are options they find unacceptable. -</p> - -<p><cite>When the Standard Resolution Procedure is to be used, the text -which refers to it must specify what is sufficient to have a draft -resolution proposed and/or sponsored, what the minimum discussion -period is, and what the voting period is. It must also specify any -supermajority and/or the quorum (and default option) to be -used.</cite></p> - -<toc-add-entry name="item-B">B. Use of language and typography</toc-add-entry> - -<p>The present indicative (<q>is</q>, for example) means that the statement -is a rule in this constitution. <q>May</q> or <q>can</q> indicates that the -person or body has discretion. <q>Should</q> means that it would be -considered a good thing if the sentence were obeyed, but it is not -binding. <cite>Text marked as a citation, such as this, is rationale -and does not form part of the constitution. It may be used only to aid -interpretation in cases of doubt.</cite></p> diff --git a/greek/devel/constitution.wml b/greek/devel/constitution.wml deleted file mode 100644 index 3b2c15b6b6f..00000000000 --- a/greek/devel/constitution.wml +++ /dev/null @@ -1,997 +0,0 @@ -#use wml::debian::template title="Καταστατικό του Debian" BARETITLE="true" -#use wml::debian::toc -#use wml::debian::translation-check translation="e3d525d9f092f9014e00417cc847900ac5a99649" maintainer="galaxico" mindelta="-1" maxdelta="1" - -<h1>Καταστατικό για το Σχέδιο Debian (v1.7)</h1> - -<p>η έκδοση 1.7 επικυρώθηκε στις 15 Αυγούστου 2016. Αντικαθιστά τις: -<a href="constitution.1.6">έκδοση 1.6</a> που επικυρώθηκε στις 13 Δεκεμβρίου 2015, -<a href="constitution.1.5">έκδοση 1.5</a> που επικυρώθηκε στις 9 Ιανουαρίου 2015, -<a href="constitution.1.4">έκδοση 1.4</a> που επικυρώθηκε στις 7 Οκτωβρίου 2007, -<a href="constitution.1.3">έκδοση 1.3</a> που επικυρώθηκε στις 24 Σεπτεμβρίου 2006, -<a href="constitution.1.2">έκδοση 1.2</a> που επικυρώθηκε στις 29 Οκτωβρίου 2003 και -<a href="constitution.1.1">έκδοση 1.1</a> που επικυρώθηκε στις 21 Ιουνίου 2003, -που αντικαθιστά η ίδια την <a href="constitution.1.0">έκδοση 1.0</a> -που επικυρώθηκε στις 2 Δεκεμβρίου 1998.</p> - -<toc-display /> - -<toc-add-entry name="item-1">1. Εισαγωγή</toc-add-entry> - -<p><cite>Το Σχέδιο Debian είναι μια ένωση ατόμων που έχουν θέσει σαν κοινό -στόχο την δημιουργία ενός ελεύθερου λειτουργικού συστήματος.</cite></p> - -<p>Το παρόν κείμενο περιγράφει την οργανωτική δομή για την τυπική διαδικασία λήψης αποφάσεων του Σχεδίου. -Δεν περιγράφει τους στόχους του Σχεδίου ή πώς τους επιτυγχάνει ούτε περιέχει οποιεσδήποτε -πολιτικές εκτός από αυτές που σχετίζονται άμεσα με τη διαδικασία λήψης αποφάσεων.</p> - -<toc-add-entry name="item-2">2. Σώματα και άτομα λήψης αποφάσεων</toc-add-entry> - -<p>Οποιαδήποτε απόφαση του Σχεδίου λαμβάνεται από ένα ή περισσότερα -από τα ακόλουθα:</p> - -<ol> - <li>Τους/Τις προγραμματιστές/προγραμματίστριες, μέσω μιας Γενικής Συνέλευσης ή μιας εκλογής·</li> - - <li>Τον/Την Επικεφαλής του Σχεδίου·</li> - - <li>Την Τεχνική Επιτροπή και/ή τον/την Πρόεδρό της·</li> - - <li>Τον μεμονωμένο προγραμματιστή/την μεμονωμένη προγραμματίστρια που - δουλεύει πάνω σε ένα συγκεκριμένο καθήκον·</li> - - <li>Εκπροσώπους που έχουν οριστεί από τον/την Επικεφαλής του Σχεδίου για - συγκεκριμένα καθήκοντα·</li> - - <li>The Project Secretary.</li> -</ol> - -<p>Most of the remainder of this document will outline the powers of -these bodies, their composition and appointment, and the procedure for -their decision-making. The powers of a person or body may be subject to -review and/or limitation by others; in this case the reviewing body or -person's entry will state this. <cite>In the list above, a person or -body is usually listed before any people or bodies whose decisions they -can overrule or who they (help) appoint - but not everyone listed -earlier can overrule everyone listed later.</cite></p> - -<h3>2.1. General rules</h3> - -<ol> - <li> - <p>Nothing in this constitution imposes an obligation on anyone to - do work for the Project. A person who does not want to do a task - which has been delegated or assigned to them does not need to do - it. However, they must not actively work against these rules and - decisions properly made under them.</p> - </li> - - <li> - <p>A person may hold several posts, except that the Project Leader, - Project Secretary and the Chair of the Technical Committee must - be distinct, and that the Leader cannot appoint themselves as their - own Delegate.</p> - </li> - - <li> - <p>A person may leave the Project or resign from a particular post - they hold, at any time, by stating so publicly.</p> - </li> -</ol> - -<toc-add-entry name="item-3">3. Individual Developers</toc-add-entry> - -<h3>3.1. Powers</h3> - -<p>An individual Developer may</p> - -<ol> - <li>make any technical or nontechnical decision with regard to their - own work;</li> - - <li>propose or sponsor draft General Resolutions;</li> - - <li>propose themselves as a Project Leader candidate in - elections;</li> - - <li>vote on General Resolutions and in Leadership elections.</li> -</ol> - -<h3>3.2. Composition and appointment</h3> - -<ol> - <li> - <p>Developers are volunteers who agree to further the aims of the - Project insofar as they participate in it, and who maintain - package(s) for the Project or do other work which the Project - Leader's Delegate(s) consider worthwhile.</p> - </li> - - <li> - <p>The Project Leader's Delegate(s) may choose not to admit new - Developers, or expel existing Developers. <cite>If the Developers - feel that the Delegates are abusing their authority they can of - course override the decision by way of General Resolution - see - §4.1(3), §4.2.</cite></p> - </li> -</ol> - -<h3>3.3. Procedure</h3> - -<p>Developers may make these decisions as they see fit.</p> - -<toc-add-entry name="item-4">4. The Developers by way of General Resolution or election</toc-add-entry> - -<h3>4.1. Powers</h3> - -<p>Together, the Developers may:</p> - -<ol> - <li> - <p>Appoint or recall the Project Leader.</p> - </li> - - <li> - <p>Amend this constitution, provided they agree with a 3:1 - majority.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Project - Leader or a Delegate.</p> - </li> - - <li> - <p>Make or override any decision authorised by the powers of the Technical - Committee, provided they agree with a 2:1 majority.</p> - </li> - - <li> - <p>Issue, supersede and withdraw nontechnical policy documents and - statements.</p> - - <p>These include documents describing the goals of the project, its - relationship with other free software entities, and nontechnical - policies such as the free software licence terms that Debian - software must meet.</p> - - <p>They may also include position statements about issues of the - day.</p> - - <ol style="list-style: decimal;"> - <li>A Foundation Document is a document or statement regarded as - critical to the Project's mission and purposes.</li> - <li>The Foundation Documents are the works entitled <q>Debian - Social Contract</q> and <q>Debian Free Software Guidelines</q>.</li> - <li>A Foundation Document requires a 3:1 majority for its - supersession. New Foundation Documents are issued and - existing ones withdrawn by amending the list of Foundation - Documents in this constitution.</li> - </ol> - - </li> - - <li> - <p>Make decisions about property held in trust for purposes - related to Debian. (See §9.).</p> - </li> - - <li> - <p>In case of a disagreement between the project leader and - the incumbent secretary, appoint a new secretary.</p> - </li> -</ol> - -<h3>4.2. Procedure</h3> - -<ol> - <li> - <p>The Developers follow the Standard Resolution Procedure, below. - A resolution or amendment is introduced if proposed by any - Developer and sponsored by at least K other Developers, or if - proposed by the Project Leader or the Technical Committee.</p> - </li> - - <li> - <p>Delaying a decision by the Project Leader or their Delegate:</p> - - <ol> - <li>If the Project Leader or their Delegate, or the Technical - Committee, has made a decision, then Developers can override them - by passing a resolution to do so; see §4.1(3).</li> - - <li>If such a resolution is sponsored by at least 2K Developers, - or if it is proposed by the Technical Committee, the resolution - puts the decision immediately on hold (provided that resolution - itself says so).</li> - - <li>If the original decision was to change a discussion period or - a voting period, or the resolution is to override the Technical - Committee, then only K Developers need to sponsor the resolution - to be able to put the decision immediately on hold.</li> - - <li>If the decision is put on hold, an immediate vote is held to - determine whether the decision will stand until the full vote on - the decision is made or whether the implementation of the - original decision will be delayed until then. There is no - quorum for this immediate procedural vote.</li> - - <li>If the Project Leader (or the Delegate) withdraws the - original decision, the vote becomes moot, and is no longer - conducted.</li> - </ol> - </li> - - <li> - <p> - Votes are taken by the Project Secretary. Votes, tallies, and - results are not revealed during the voting period; after the - vote the Project Secretary lists all the votes cast. The voting - period is 2 weeks, but may be varied by up to 1 week by the - Project Leader. - </p> - </li> - - <li> - <p>The minimum discussion period is 2 weeks, but may be varied by - up to 1 week by the Project Leader. The Project Leader has a - casting vote. There is a quorum of 3Q.</p> - </li> - - <li> - <p>Proposals, sponsors, amendments, calls for votes and other - formal actions are made by announcement on a publicly-readable - electronic mailing list designated by the Project Leader's - Delegate(s); any Developer may post there.</p> - </li> - - <li> - <p>Votes are cast by email in a manner suitable to the Secretary. - The Secretary determines for each poll whether voters can change - their votes.</p> - </li> - - <li> - <p>Q is half of the square root of the number of current - Developers. K is Q or 5, whichever is the smaller. Q and K need not - be integers and are not rounded.</p> - </li> -</ol> - -<toc-add-entry name="item-5">5. Project Leader</toc-add-entry> - -<h3>5.1. Powers</h3> - -<p>The <a href="leader">Project Leader</a> may:</p> - -<ol> - <li> - <p>Appoint Delegates or delegate decisions to the Technical - Committee.</p> - - <p>The Leader may define an area of ongoing responsibility or a - specific decision and hand it over to another Developer or to the - Technical Committee.</p> - - <p>Once a particular decision has been delegated and made the - Project Leader may not withdraw that delegation; however, they may - withdraw an ongoing delegation of particular area of - responsibility.</p> - </li> - - <li> - <p>Lend authority to other Developers.</p> - - <p>The Project Leader may make statements of support for points of - view or for other members of the project, when asked or otherwise; - these statements have force if and only if the Leader would be - empowered to make the decision in question.</p> - </li> - - <li> - <p>Make any decision which requires urgent action.</p> - - <p>This does not apply to decisions which have only become - gradually urgent through lack of relevant action, unless there is a - fixed deadline.</p> - </li> - - <li> - <p>Make any decision for whom noone else has responsibility.</p> - </li> - - <li> - <p>Propose draft General Resolutions and amendments.</p> - </li> - - <li> - <p>Together with the Technical Committee, appoint new members to - the Committee. (See §6.2.)</p> - </li> - - <li> - <p>Use a casting vote when Developers vote.</p> - - <p>The Project Leader also has a normal vote in such ballots.</p> - </li> - - <li> - <p>Vary the discussion period for Developers' votes (as above).</p> - </li> - - <li> - <p>Lead discussions amongst Developers.</p> - - <p>The Project Leader should attempt to participate in discussions - amongst the Developers in a helpful way which seeks to bring the - discussion to bear on the key issues at hand. The Project Leader - should not use the Leadership position to promote their own - personal views.</p> - </li> - - <li> - <p>In consultation with the developers, make decisions affecting - property held in trust for purposes related to Debian. (See - §9.). Such decisions are communicated to the members by the - Project Leader or their Delegate(s). Major expenditures - should be proposed and debated on the mailing list before - funds are disbursed.</p> - </li> - <li> - <p>Add or remove organizations from the list of trusted - organizations (see §9.3) that are authorized to accept and - hold assets for Debian. The evaluation and discussion leading - up to such a decision occurs on an electronic mailing list - designated by the Project Leader or their Delegate(s), on - which any developer may post. There is a minimum discussion - period of two weeks before an organization may be added to - the list of trusted organizations.</p> - </li> -</ol> - -<h3>5.2. Appointment</h3> - -<ol> - <li>The Project Leader is elected by the Developers.</li> - - <li>The election begins six weeks before the leadership post becomes - vacant, or (if it is too late already) immediately.</li> - - <li>For the first week any Developer may nominate - themselves as a candidate Project Leader, and summarize their plans for their term.</li> - - <li>For three weeks after that no more candidates may be nominated; - candidates should use this time for campaigning and discussion. If - there are no candidates at the end of the nomination period then the - nomination period is extended for an additional week, repeatedly if - necessary.</li> - - <li>The next two weeks are the polling period during which - Developers may cast their votes. Votes in leadership elections are - kept secret, even after the election is finished.</li> - - <li>The options on the ballot will be those candidates who have - nominated themselves and have not yet withdrawn, plus None Of The - Above. If None Of The Above wins the election then the election - procedure is repeated, many times if necessary.</li> - - <li> - The decision will be made using the method specified in section - §A.6 of the Standard Resolution Procedure. The quorum is the - same as for a General Resolution (§4.2) and the default - option is <q>None Of The Above</q>. - </li> - - <li>The Project Leader serves for one year from their election.</li> -</ol> - -<h3>5.3. Procedure</h3> - -<p>The Project Leader should attempt to make decisions which are -consistent with the consensus of the opinions of the Developers.</p> - -<p>Where practical the Project Leader should informally solicit the -views of the Developers.</p> - -<p>The Project Leader should avoid overemphasizing their own point of -view when making decisions in their capacity as Leader.</p> - -<toc-add-entry name="item-6">6. Technical committee</toc-add-entry> - -<h3>6.1. Powers</h3> - -<p>The <a href="tech-ctte">Technical Committee</a> may:</p> - -<ol> - <li> - <p>Decide on any matter of technical policy.</p> - - <p>This includes the contents of the technical policy manuals, - developers' reference materials, example packages and the behaviour - of non-experimental package building tools. (In each case the usual - maintainer of the relevant software or documentation makes - decisions initially, however; see 6.3(5).)</p> - </li> - - <li> - <p>Decide any technical matter where Developers' jurisdictions - overlap.</p> - - <p>In cases where Developers need to implement compatible - technical policies or stances (for example, if they disagree about - the priorities of conflicting packages, or about ownership of a - command name, or about which package is responsible for a bug that - both maintainers agree is a bug, or about who should be the - maintainer for a package) the technical committee may decide the - matter.</p> - </li> - - <li> - <p>Make a decision when asked to do so.</p> - - <p>Any person or body may delegate a decision of their own to the - Technical Committee, or seek advice from it.</p> - </li> - - <li> - <p>Overrule a Developer (requires a 3:1 majority).</p> - - <p>The Technical Committee may ask a Developer to take a - particular technical course of action even if the Developer does - not wish to; this requires a 3:1 majority. For example, the - Committee may determine that a complaint made by the submitter of a - bug is justified and that the submitter's proposed solution should - be implemented.</p> - </li> - - <li> - <p>Offer advice.</p> - - <p>The Technical Committee may make formal announcements about its - views on any matter. <cite>Individual members may of course make - informal statements about their views and about the likely views of - the committee.</cite></p> - </li> - - <li> - <p>Together with the Project Leader, appoint new members to itself - or remove existing members. (See §6.2.)</p> - </li> - - <li> - <p>Appoint the Chair of the Technical Committee.</p> - - <p> - The Chair is elected by the Committee from its members. All - members of the committee are automatically nominated; the - committee votes starting one week before the post will become - vacant (or immediately, if it is already too late). The members - may vote by public acclamation for any fellow committee member, - including themselves; there is no default option. The vote - finishes when all the members have voted, or when the voting - period has ended. The result is determined using the method - specified in section A.6 of the Standard Resolution Procedure. - </p> - </li> - - <li> - <p>The Chair can stand in for the Leader, together with the - Secretary</p> - - <p>As detailed in §7.1(2), the Chair of the Technical - Committee and the Project Secretary may together stand in for the - Leader if there is no Leader.</p> - </li> -</ol> - -<h3>6.2. Composition</h3> - -<ol> - <li> - <p>The Technical Committee consists of up to 8 Developers, and - should usually have at least 4 members.</p> - </li> - - <li> - <p>When there are fewer than 8 members the Technical Committee may - recommend new member(s) to the Project Leader, who may choose - (individually) to appoint them or not.</p> - </li> - - <li> - <p>When there are 5 members or fewer the Technical Committee may - appoint new member(s) until the number of members reaches 6.</p> - </li> - - <li> - <p>When there have been 5 members or fewer for at least one week - the Project Leader may appoint new member(s) until the number of - members reaches 6, at intervals of at least one week per - appointment.</p> - </li> - - <li> - <p>A Developer is not eligible to be (re)appointed to the Technical - Committee if they have been a member within the previous 12 - months.</p> - </li> - - <li> - <p>If the Technical Committee and the Project Leader agree they - may remove or replace an existing member of the Technical - Committee.</p> - </li> - - <li> - <p>Term limit:</p> - <ol> - <li> - <p>On January 1st of each year the term of any Committee member - who has served more than 42 months (3.5 years) and who is one - of the two most senior members is set to expire on December - 31st of that year.</p> - </li> - <li> - <p>A member of the Technical Committee is said to be more - senior than another if they were appointed earlier, or were - appointed at the same time and have been a member of the - Debian Project longer. In the event that a member has been - appointed more than once, only the most recent appointment is - relevant.</p> - </li> - </ol> - </li> -</ol> - -<h3>6.3. Procedure</h3> - -<ol> - <li> - <p>The Technical Committee uses the Standard Resolution - Procedure.</p> - - <p>A draft resolution or amendment may be proposed by any member - of the Technical Committee. There is no minimum discussion period; - the voting period lasts for up to one week, or until the outcome is - no longer in doubt. Members may change their votes. There is a - quorum of two.</p> - </li> - - <li> - <p>Details regarding voting</p> - - <p>The Chair has a casting vote. When the Technical Committee - votes whether to override a Developer who also happens to be a - member of the Committee, that member may not vote (unless they are - the Chair, in which case they may use only their casting - vote).</p> - </li> - - <li> - <p>Public discussion and decision-making.</p> - - <p>Discussion, draft resolutions and amendments, and votes by - members of the committee, are made public on the Technical - Committee public discussion list. There is no separate secretary - for the Committee.</p> - </li> - - <li> - <p>Confidentiality of appointments.</p> - - <p>The Technical Committee may hold confidential discussions via - private email or a private mailing list or other means to discuss - appointments to the Committee. However, votes on appointments must - be public.</p> - </li> - - <li> - <p>No detailed design work.</p> - - <p>The Technical Committee does not engage in design of new - proposals and policies. Such design work should be carried out by - individuals privately or together and discussed in ordinary - technical policy and design forums.</p> - - <p>The Technical Committee restricts itself to choosing from or - adopting compromises between solutions and decisions which have - been proposed and reasonably thoroughly discussed elsewhere.</p> - - <p><cite>Individual members of the technical committee may of - course participate on their own behalf in any aspect of design and - policy work.</cite></p> - </li> - - <li> - <p>Technical Committee makes decisions only as last resort.</p> - - <p>The Technical Committee does not make a technical decision - until efforts to resolve it via consensus have been tried and - failed, unless it has been asked to make a decision by the person - or body who would normally be responsible for it.</p> - </li> -</ol> - -<toc-add-entry name="item-7">7. The Project Secretary</toc-add-entry> - -<h3>7.1. Powers</h3> - -<p>The <a href="secretary">Secretary</a>:</p> - -<ol> - <li> - <p>Takes votes amongst the Developers, and determines the number - and identity of Developers, whenever this is required by the - constitution.</p> - </li> - - <li> - <p>Can stand in for the Leader, together with the Chair of the - Technical Committee.</p> - - <p>If there is no Project Leader then the Chair of the - Technical Committee and the Project Secretary may by joint - agreement make decisions if they consider it imperative to do - so.</p> - </li> - - <li> - <p>Adjudicates any disputes about interpretation of the - constitution.</p> - </li> - - <li> - <p>May delegate part or all of their authority to someone else, or - withdraw such a delegation at any time.</p> - </li> -</ol> - -<h3>7.2. Appointment</h3> - -<p>The Project Secretary is appointed by the Project Leader and the -current Project Secretary.</p> - -<p>If the Project Leader and the current Project Secretary cannot agree -on a new appointment, they must ask the Developers by way of -General Resolution to appoint a Secretary.</p> - -<p>If there is no Project Secretary or the current Secretary is -unavailable and has not delegated authority for a decision then the -decision may be made or delegated by the Chair of the Technical -Committee, as Acting Secretary.</p> - -<p>The Project Secretary's term of office is 1 year, at which point -they or another Secretary must be (re)appointed.</p> - -<h3>7.3. Procedure</h3> - -<p>The Project Secretary should make decisions which are fair and -reasonable, and preferably consistent with the consensus of the -Developers.</p> - -<p>When acting together to stand in for an absent Project Leader the -Chair of the Technical Committee and the Project Secretary should -make decisions only when absolutely necessary and only when consistent -with the consensus of the Developers.</p> - -<toc-add-entry name="item-8">8. The Project Leader's Delegates</toc-add-entry> - -<h3>8.1. Powers</h3> - -<p>The Project Leader's Delegates:</p> - -<ol> - <li>have powers delegated to them by the Project Leader;</li> - - <li>may make certain decisions which the Leader may not make - directly, including approving or expelling Developers or designating - people as Developers who do not maintain packages. <cite>This is to - avoid concentration of power, particularly over membership as a - Developer, in the hands of the Project Leader.</cite></li> -</ol> - -<h3>8.2. Appointment</h3> - -<p>The Delegates are appointed by the Project Leader and may be -replaced by the Leader at the Leader's discretion. The Project Leader -may not make the position as a Delegate conditional on particular -decisions by the Delegate, nor may they override a decision made by a -Delegate once made.</p> - -<h3>8.3. Procedure</h3> - -<p>Delegates may make decisions as they see fit, but should attempt to -implement good technical decisions and/or follow consensus opinion.</p> - -<toc-add-entry name="item-9">9. Assets held in trust for Debian</toc-add-entry> - -<p>In most jurisdictions around the world, the Debian project is not -in a position to directly hold funds or other property. Therefore, -property has to be owned by any of a number of organisations as -detailed in §9.2.</p> - -<p>Traditionally, SPI was the sole organisation authorized to hold -property and monies for the Debian Project. SPI was created in -the U.S. to hold money in trust there.</p> - -<p><a href="https://www.spi-inc.org/">SPI</a> and Debian are separate -organisations who share some goals. -Debian is grateful for the legal support framework offered by SPI.</p> - -<h3>9.1. Relationship with Associated Organizations</h3> - -<ol> - <li> - <p>Debian Developers do not become agents or employees of - organisations holding assets in trust for Debian, or of - each other, or of persons in authority in the Debian Project, - solely by the virtue of being Debian Developers. A person - acting as a Developer does so as an individual, on their own - behalf. Such organisations may, of their own accord, - establish relationships with individuals who are also Debian - developers.</p> - </li> -</ol> - -<h3>9.2. Authority</h3> - -<ol> - <li> - <p>An organisation holding assets for Debian has no authority - regarding Debian's technical or nontechnical decisions, except - that no decision by Debian with respect to any property held - by the organisation shall require it to act outside its legal - authority.</p> - </li> - <li> - <p>Debian claims no authority over an organisation that holds - assets for Debian other than that over the use of property - held in trust for Debian.</p> - </li> -</ol> - -<h3>9.3. Trusted organisations</h3> - -<p>Any donations for the Debian Project must be made to any one of a -set of organisations designated by the Project leader (or a -delegate) to be authorized to handle assets to be used for the -Debian Project.</p> - -<p>Organisations holding assets in trust for Debian should -undertake reasonable obligations for the handling of such -assets.</p> - -<p>Debian maintains a public List of Trusted Organisations that -accept donations and hold assets in trust for Debian -(including both tangible property and intellectual property) -that includes the commitments those organisations have made as -to how those assets will be handled.</p> - -<toc-add-entry name="item-A">A. Standard Resolution Procedure</toc-add-entry> - -<p>These rules apply to communal decision-making by committees and -plebiscites, where stated above.</p> - -<h3>A.0. Proposal</h3> - -<p>The formal procedure begins when a draft resolution is proposed and -sponsored, as required.</p> - -<h3>A.1. Discussion and Amendment</h3> - -<ol> - <li>Following the proposal, the resolution may be discussed. - Amendments may be made formal by being proposed and sponsored - according to the requirements for a new resolution, or directly by - the proposer of the original resolution.</li> - - <li>A formal amendment may be accepted by the resolution's proposer, - in which case the formal resolution draft is immediately changed to - match.</li> - - <li>If a formal amendment is not accepted, or one of the sponsors of - the resolution does not agree with the acceptance by the proposer of - a formal amendment, the amendment remains as an amendment and will be - voted on.</li> - - <li>If an amendment accepted by the original proposer is not to the - liking of others, they may propose another amendment to reverse the - earlier change (again, they must meet the requirements for proposer - and sponsor(s).)</li> - - <li>The proposer of a resolution may suggest changes to the wordings - of amendments; these take effect if the proposer of the amendment - agrees and none of the sponsors object. In this case the changed - amendments will be voted on instead of the originals.</li> - - <li>The proposer of a resolution may make changes to correct minor - errors (for example, typographical errors or inconsistencies) or - changes which do not alter the meaning, providing noone objects - within 24 hours. In this case the minimum discussion period is not - restarted.</li> -</ol> - -<h3>A.2. Calling for a vote</h3> - -<ol> - <li>The proposer or a sponsor of a motion or an amendment may call - for a vote, providing that the minimum discussion period (if any) has - elapsed.</li> - - <li> - The proposer or any sponsor of a resolution may call for a vote on that - resolution and all related amendments. - </li> - - <li>The person who calls for a vote states what they believe the - wordings of the resolution and any relevant amendments are, and - consequently what form the ballot should take. However, the final - decision on the form of ballot(s) is the Secretary's - see 7.1(1), - 7.1(3) and A.3(4).</li> - - <li> - The minimum discussion period is counted from the time the last - formal amendment was accepted, or since the whole resolution - was proposed if no amendments have been proposed and accepted. - </li> -</ol> - -<h3>A.3. Voting procedure</h3> - -<ol> - <li> - Each resolution and its related amendments is voted on in a - single ballot that includes an option for the original - resolution, each amendment, and the default option (where - applicable). - </li> - - <li> - The default option must not have any supermajority requirements. - Options which do not have an explicit supermajority requirement - have a 1:1 majority requirement. - </li> - - <li> - The votes are counted according to the rules in A.6. The - default option is <q>Further Discussion</q>, unless specified - otherwise. - </li> - - <li>In cases of doubt the Project Secretary shall decide on matters - of procedure.</li> -</ol> - -<h3>A.4. Withdrawing resolutions or unaccepted amendments</h3> - -<p>The proposer of a resolution or unaccepted amendment may withdraw -it. In this case new proposers may come forward keep it alive, in which -case the first person to do so becomes the new proposer and any others -become sponsors if they aren't sponsors already.</p> - -<p>A sponsor of a resolution or amendment (unless it has been -accepted) may withdraw.</p> - -<p>If the withdrawal of the proposer and/or sponsors means that a -resolution has no proposer or not enough sponsors it will not be voted -on unless this is rectified before the resolution expires.</p> - -<h3>A.5. Expiry</h3> - -<p> - If a proposed resolution has not been discussed, amended, voted on or - otherwise dealt with for 4 weeks the secretary may issue a statement - that the issue is being withdrawn. If none of the sponsors of any - of the proposals object within a week, the issue is withdrawn. -</p> - -<p> - The secretary may also include suggestions on how to proceed, - if appropriate. -</p> - -<h3>A.6. Vote Counting</h3> - -<ol> - <li> Each voter's ballot ranks the options being voted on. Not all - options need be ranked. Ranked options are considered - preferred to all unranked options. Voters may rank options - equally. Unranked options are considered to be ranked equally - with one another. Details of how ballots may be filled out - will be included in the Call For Votes. - </li> - <li> If the ballot has a quorum requirement R any options other - than the default option which do not receive at least R votes - ranking that option above the default option are dropped from - consideration. - </li> - <li> Any (non-default) option which does not defeat the default option - by its required majority ratio is dropped from consideration. - <ol> - <li> - Given two options A and B, V(A,B) is the number of voters - who prefer option A over option B. - </li> - <li> - An option A defeats the default option D by a majority - ratio N, if V(A,D) is greater or equal to N * V(D,A) and V(A,D) is strictly greater than V(D,A). - </li> - <li> - If a supermajority of S:1 is required for A, its majority ratio - is S; otherwise, its majority ratio is 1. - </li> - </ol> - </li> - <li> From the list of undropped options, we generate a list of - pairwise defeats. - <ol> - <li> - An option A defeats an option B, if V(A,B) is strictly greater - than V(B,A). - </li> - </ol> - </li> - <li> From the list of [undropped] pairwise defeats, we generate a - set of transitive defeats. - <ol> - <li> - An option A transitively defeats an option C if A defeats - C or if there is some other option B where A defeats B AND - B transitively defeats C. - </li> - </ol> - </li> - <li> We construct the Schwartz set from the set of transitive defeats. - <ol> - <li> - An option A is in the Schwartz set if for all options B, - either A transitively defeats B, or B does not transitively - defeat A. - </li> - </ol> - </li> - <li> If there are defeats between options in the Schwartz set, - we drop the weakest such defeats from the list of pairwise - defeats, and return to step 5. - <ol> - <li> - A defeat (A,X) is weaker than a defeat (B,Y) if V(A,X) - is less than V(B,Y). Also, (A,X) is weaker than (B,Y) if - V(A,X) is equal to V(B,Y) and V(X,A) is greater than V(Y,B). - </li> - <li> - A weakest defeat is a defeat that has no other defeat weaker - than it. There may be more than one such defeat. - </li> - </ol> - </li> - <li> If there are no defeats within the Schwartz set, then the winner - is chosen from the options in the Schwartz set. If there is - only one such option, it is the winner. If there are multiple - options, the elector with the casting vote chooses which of those - options wins. - </li> -</ol> - -<p> - <strong>Note:</strong> Options which the voters rank above the default option - are options they find acceptable. Options ranked below the default - options are options they find unacceptable. -</p> - -<p><cite>When the Standard Resolution Procedure is to be used, the text -which refers to it must specify what is sufficient to have a draft -resolution proposed and/or sponsored, what the minimum discussion -period is, and what the voting period is. It must also specify any -supermajority and/or the quorum (and default option) to be -used.</cite></p> - -<toc-add-entry name="item-B">B. Use of language and typography</toc-add-entry> - -<p>The present indicative (<q>is</q>, for example) means that the statement -is a rule in this constitution. <q>May</q> or <q>can</q> indicates that the -person or body has discretion. <q>Should</q> means that it would be -considered a good thing if the sentence were obeyed, but it is not -binding. <cite>Text marked as a citation, such as this, is rationale -and does not form part of the constitution. It may be used only to aid -interpretation in cases of doubt.</cite></p> diff --git a/greek/devel/debian-accessibility/Makefile b/greek/devel/debian-accessibility/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/devel/debian-accessibility/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/devel/debian-accessibility/index.wml b/greek/devel/debian-accessibility/index.wml deleted file mode 100644 index b06755c1e72..00000000000 --- a/greek/devel/debian-accessibility/index.wml +++ /dev/null @@ -1,114 +0,0 @@ -#use wml::debian::template title="Debian-Accessibility" -#use wml::debian::translation-check translation="82f3d1721149ec88f5974028ed2c2d8d454b4071" maintainer="galaxico" -{#style#:<link rel="stylesheet" href="style.css" type="text/css" />:#style#} - -<h2>Project description</h2> - -<p>Debian-Accessibility is an internal project to develop Debian into an - operating system that is particularly well fit for the requirements of - people with disabilities. - The goal of Debian-Accessibility is a completely accessible system - which offers users with disabilities the highest possible amount - of independence, built completely on free software. -</p> -<p>We envisage that Debian-Accessibility will add value to existing - packages by providing patches to fix problems very specific - to certain user groups or conducting Accessibility validation tests and - providing modification suggestions based on the results. -</p> - -<h2><a id="email-list" name="email-list">Email List</a></h2> - -<p>The Debian-Accessibility mailing list is the central point of communication - for Debian-Accessibility. It serves as a forum for potential, as - well as current, users of the Debian system who do have special needs. - Additionally, it is used to coordinate development efforts around the various - topics of Accessibility. You can subscribe to and unsubscribe from it using - <a href="https://lists.debian.org/debian-accessibility/">the list web - page</a>, and also read the - <a href="https://lists.debian.org/debian-accessibility/">list archives</a>. -</p> - -<h2><a id="projects" name="projects">Relevant Software</a></h2> - -<p>The first attempt to put the software into categories might be not the - best. Send any suggestions for improvements to <a href="#email-list">the - mailing list</a>, or to <a href="mailto:sthibault@debian.org">Samuel Thibault</a>. -</p> -<ul> - <li><a href="software#speech-synthesis">Speech synthesis and related - APIs</a></li> - <li><a href="software#console">Console (text-mode) screen - readers</a></li> - <li><a href="software#emacs">Screen review extensions for - Emacs</a></li> - <li><a href="software#gui">Graphical User Interfaces</a>: - <ul> - <li><a href="software#gnome">GNOME Accessibility</a></li> - <li><a href="software#input">Non-standard input - methods</a></li> - </ul></li> -</ul> - -<h2><a id="goals" name="goals">Project goals</a></h2> - -<ul> - <li>Provide information and documentation of Accessibility.</li> - <li>Ensure that Accessibility software like drivers for specialized - peripheral devices can be loaded if necessary as early as possible in the - system startup phase, including the Debian installation process. This is - to ensure that people with special needs retain a high level of - independence during maintenance of their own systems.</li> - <li>Verify and ensure that Debian core infrastructure like our Web site does - comply with Accessibility Guidelines.</li> - <li>Bring authors of different projects with similar goals together.</li> - <li>Help upstream authors to get their products packaged for Debian.</li> - <li>Show commercial assistive technology vendors the strengths of Free - Software based systems and make them consider to port their software to - Linux or even to switch to Open Source.</li> -</ul> - -<h2><a id="help" name="help">What can I do to help?</a></h2> - -<ul> - <li>Work on enhancing and translating these web pages.</li> - <li>Create a logo.</li> - <li>Documentation and translation.</li> - <li>Internationalization (which is more than just translating, see - <a href="software#i18nspeech">internationalized speech - synthesis</a> for some ideas).</li> - <li>Verify that the debian.org web site is Accessible according to - established Accessibility Guidelines and submit enhancement suggestions - based on your findings. It could eventually be desirable to apply for - something like Bobby Approval at some point.</li> -</ul> - -<h2><a id="links" name="links">Links</a></h2> - -<ul> - <li>The <a href="https://wiki.debian.org/accessibility">Debian Accessibility Wiki</a>.</li> - <li>The <a href="https://wiki.debian.org/accessibility-maint">Debian Accessibility Wiki for all Debian maintainers</a>.</li> - <li>The <a href="https://wiki.debian.org/accessibility-devel">Debian Accessibility Developer Wiki</a>.</li> - <li>The <a href="https://wiki.linuxfoundation.org/accessibility/start">Free Standards Group Accessibility - Workgroup</a>.</li> - <li>The <a href="https://wiki.gnome.org/Accessibility">GNOME - Accessibility Project</a>.</li> - <li>The <a href="https://community.kde.org/Accessibility">KDE Accessibility - Project</a>.</li> - <li><a href="https://wiki.ubuntu.com/Accessibility">Ubuntu Accessibility</a></li> - <li><a href="http://leb.net/blinux/">BLINUX</a>: Improve usability of the - GNU/Linux operating system for the user who is blind.</li> - <li><a href="http://www.linux-speakup.org/">The Linux Speakup - Project</a>.</li> - <li><a href="http://www.w3.org/WAI/">W3C's Web Accessibility Initiative - (WAI)</a>: - <ul> - <li>The <a href="http://www.w3.org/TR/WCAG10/">Web Content - Accessibility Guidelines</a> explain in detail how to make a Web - site accessible for people with a variety of disabilities.</li> - <li>The <a href="http://www.w3.org/TR/ATAG10/">Authoring Tool - Accessibility Guidelines</a> explain how to make a variety of - authoring tools support the production of accessible Web - content, and also how to make the software itself accessible.</li> - </ul></li> -</ul> diff --git a/greek/devel/debian-accessibility/software.wml b/greek/devel/debian-accessibility/software.wml deleted file mode 100644 index 61dbb6e1863..00000000000 --- a/greek/devel/debian-accessibility/software.wml +++ /dev/null @@ -1,401 +0,0 @@ -#use wml::debian::template title="Debian-Accessibility - Software" -#use wml::debian::translation-check translation="82f3d1721149ec88f5974028ed2c2d8d454b4071" maintainer="galaxico" -{#style#:<link rel="stylesheet" href="style.css" type="text/css" />:#style#} - -<define-tag a11y-pkg endtag=required> -<preserve name tag url/> -<set-var %attributes> -<h3><if "<get-var url>" - <a href="<get-var url>" name="<get-var tag>"><get-var name></a> - <a href="https://packages.debian.org/<get-var tag>" name="<get-var tag>"><get-var name></a>></h3> - %body -<restore name tag url/> -</define-tag> - -<h2><a id="speech-synthesis" name="speech-synthesis">Speech Synthesis and related APIs</a></h2> - -<p> - A thorough list is available on the - <a href="https://blends.debian.org/accessibility/tasks/speechsynthesis">speechsynthesis task page</a> -</p> - -<a11y-pkg name="EFlite" tag=eflite url="http://eflite.sourceforge.net/"> -<p> - A speech server for <a href="#emacspeak">Emacspeak</a> and - <a href="#yasr">yasr</a> (or other screen readers) that allows them to - interface with <a href="#flite">Festival Lite</a>, a free text-to-speech - engine developed at the CMU Speech Center as an off-shoot of - <a href="#festival">Festival</a>. -</p> -<p> - Due to limitations inherited from its backend, EFlite does only provide - support for the English language at the moment. -</p> -</a11y-pkg> -<a11y-pkg name="eSpeak" tag=espeak> -<p> -eSpeak/eSpeak-NG is a software speech synthesizer for English, and some other -languages. -</p> -<p> -eSpeak produces good quality English speech. It uses a different synthesis -method from other open source text to speech (TTS) engines (no concatenative -speech synthesis, therefore it also has a very small footprint), and sounds -quite different. It's perhaps not as natural or <q>smooth</q>, but some find the -articulation clearer and easier to listen to for long periods. -</p> -<p> -It can run as a command line program to speak text from a file or from stdin. -It also works well as a <q>Talker</q> with the KDE text to speech system (KTTS), -as an alternative to <a href="#festival">Festival</a> for example. As such, it -can speak text which has been selected into the clipboard, or directly from the -Konqueror browser or the Kate editor. -</p> - <ul> - <li>Includes different Voices, whose characteristics can be altered.</li> - <li>Can produce speech output as a WAV file.</li> - <li>Can translate text to phoneme codes, so it could be adapted as a front end - for another speech synthesis engine.</li> - <li>Potential for other languages. Rudimentary (and probably humourous) - attempts at German and Esperanto are included.</li> - <li>Compact size. The program and its data total about 350 kbytes.</li> - <li>Written in C++.</li> - </ul> -<p> -eSpeak can also be used with <a href="#speech-dispatcher">Speech Dispatcher</a>. -</p> -</a11y-pkg> -<a11y-pkg name="Festival Lite" tag=flite> -<p> - A small fast run-time speech synthesis engine. It is the latest - addition to the suite of free software synthesis tools including - University of Edinburgh's Festival Speech Synthesis System and - Carnegie Mellon University's FestVox project, tools, scripts and - documentation for building synthetic voices. However, flite itself - does not require either of these systems to run. -</p> -<p> - It currently only supports the English language. -</p> -</a11y-pkg> -<a11y-pkg name="Festival" tag="festival" - url="http://www.cstr.ed.ac.uk/projects/festival/"> -<p> - A general multi-lingual speech synthesis system developed - at the <a href="http://www.cstr.ed.ac.uk/">CSTR</a> [<i>C</i>entre for - <i>S</i>peech <i>T</i>echnology <i>R</i>esearch] of - <a href="http://www.ed.ac.uk/text.html">University of Edinburgh</a>. -</p> -<p> - Festival offers a full text to speech system with various APIs, as well an - environment for development and research of speech synthesis techniques. - It is written in C++ with a Scheme-based command interpreter for general - control. -</p> -<p> - Besides research into speech synthesis, festival is useful as a stand-alone - speech synthesis program. It is capable of producing clearly understandable - speech from text. -</p> -</a11y-pkg> -<a11y-pkg name="Speech Dispatcher" tag="speech-dispatcher" - url="http://www.freebsoft.org/speechd"> -<p> - Provides a device independent layer for speech synthesis. - It supports various software and hardware speech synthesizers as - backends and provides a generic layer for synthesizing speech and - playing back PCM data via those different backends to applications. -</p> -<p> - Various high level concepts like enqueueing vs. interrupting speech - and application specific user configurations are implemented in a device - independent way, therefore freeing the application programmer from having - to yet again reinvent the wheel. -</p> -</a11y-pkg> - - -<h2><a name="i18nspeech">Internationalised Speech Synthesis</a></h2> -<p> -All the currently available free solutions for software based speech -synthesis seem to share one common deficiency: They are mostly limited to -English, providing only very marginal support for other languages, or in -most cases none at all. -Among all the free software speech synthesizers for Linux, only CMU -Festival supports more than one natural language. CMU Festival can -synthesize English, Spanish and Welsh. German is not -supported. French is not supported. Russian is not supported. When -internationalization and localization are the trends in software and -web services, is it reasonable to require blind people interested in -Linux to learn English just to understand their computer's output and to -conduct all their correspondence in a foreign tongue? -</p> -<p> -Unfortunately, speech synthesis is not really Jane Hacker's favourite -homebrew project. Creating an intelligible software speech -synthesizer involves time-consuming tasks. -Concatenative speech synthesis requires the careful creation of a -phoneme database containing all the possible combinations of sounds -for the target language. -Rules that determine the transformation of the text representation -into individual phonemes also need to be developed and fine-tuned, -usually requiring the division of the stream of characters into -logical groups such as sentences, phrases and words. Such lexical -analysis requires a language-specific lexicon seldom released under a -free license. -</p> -<p> -One of the most promising speech synthesis systems is Mbrola, with -phoneme databases for over several dozen different languages. The synthesis -itself is free software. Unfortunately the phoneme databases are for -non-military and non-commercial use only. We are lacking free phoneme -databases in order to be used in the Debian Operating System. -</p> -<p> -Without a broadly multi-lingual software speech synthesizer, Linux -cannot be accepted by assistive technology providers and people with -visual disabilities. What can we do to improve this? -</p> -<p> -There are basically two approaches possible: -</p> -<ol> -<li>Organize a group of people willing to help in this regard, and -try to actively improve the situation. This might get a bit complicated, -since a lot of specific knowledge about speech synthesis will be required, -which isn't that easy if done via an autodidactic approach. However, this -should not discourage you. If you think you can motivate a group of -people large enough to achieve some improvements, it would be worthwhile -to do.</li> -<li>Obtain funding and hire some institute which already has the -know how to create the necessary phoneme databases, lexica and transformation -rules. This approach has the advantage that it has a better probability -of generating quality results, and it should also achieve some improvements -much earlier than the first approach. Of course, the license under which all -resulting work would be released should be agreed on in advance, and it should -pass the DFSG requirements. The ideal solution would of course -be to convince some university to undergo such a project on their own -dime, and contribute the results to the Free Software community.</li> -</ol> -<p> -Last but not least, it seems most of the commercially successful -speech synthesis products nowadays do no longer use concatenative speech -synthesis, mainly because the sound databases -consume a lot of diskspace. This is not really desireable -for small embedded products, like for instance speech -on a mobile phone. Recently released Free software like <a href="#espeak">eSpeak</a> -seem to try this approach, which might be very worthwhile -to look at. -</p> - - -<h2><a id="emacs" name="emacs">Screen review extensions for Emacs</a></h2> -<a11y-pkg name="Emacspeak" tag="emacspeak" - url="http://emacspeak.sourceforge.net/"> -<p> - A speech output system that will allow someone who cannot see - to work directly on a UNIX system. Once you start Emacs with - Emacspeak loaded, you get spoken feedback for everything you do. Your - mileage will vary depending on how well you can use Emacs. There is nothing - that you cannot do inside Emacs :-). This package includes speech servers - written in tcl to support the DECtalk Express and DECtalk MultiVoice - speech synthesizers. For other synthesizers, look for separate - speech server packages such as Emacspeak-ss or <a href="#eflite">eflite</a>. -</p> -</a11y-pkg> -<a11y-pkg name="speechd-el" tag="speechd-el" - url="http://www.freebsoft.org/speechd-el"> -<p> - Emacs client to speech synthesizers, Braille displays - and other alternative output interfaces. It provides full speech and - Braille output environment for Emacs. It is aimed primarily at - visually impaired users who need non-visual communication with Emacs, - but it can be used by anybody who needs sophisticated speech or other - kind of alternative output from Emacs. -</p> -</a11y-pkg> - - -<h2><a id="console" name="console">Console (text-mode) screen readers</a></h2> - -<p> - A thorough list is available on the - <a href="https://blends.debian.org/accessibility/tasks/console">console screen readers task page</a> -</p> - -<a11y-pkg name="BRLTTY" tag="brltty" url="https://brltty.app/"> -<p> - A daemon which provides access to the Linux console for a blind - person using a soft braille display. - It drives the braille terminal and provides complete screen review - functionality. -</p> -<p> - The Braille devices supported by BRLTTY are listed on the - <a href="https://brltty.app/doc/KeyBindings/#braille-device-bindings"> - BRLTTY device documentation</a> -</p> -<p> - BRLTTY also provides a client/server based infrastructure for applications - wishing to utilize a Braille display. The daemon process listens for - incoming TCP/IP connections on a certain port. A shared object library - for clients is provided in the package - <a href="https://packages.debian.org/libbrlapi">libbrlapi</a>. A static - library, header files and documentation is provided in package - <a href="https://packages.debian.org/libbrlapi-dev">libbrlapi-dev</a>. This - functionality is for instance used by <a href="#gnome-orca">Orca</a> - to provide support for display types which are not yet support by Gnopernicus - directly. -</p> -</a11y-pkg> -<a11y-pkg name="Yasr" tag="yasr" url="http://yasr.sourceforge.net/"> -<p> - A general-purpose console screen reader for GNU/Linux and - other UNIX-like operating systems. The name <q>yasr</q> is an acronym that - can stand for either <q>Yet Another Screen Reader</q> or <q>Your All-purpose - Screen Reader</q>. -</p> -<p> - Currently, yasr attempts to support the Speak-out, DEC-talk, BNS, Apollo, - and DoubleTalk hardware synthesizers. It is also able to communicate with - Emacspeak speech servers and can thus be used with synthesizers not directly - supported, such as <a href="#flite">Festival Lite</a> (via - <a href="#eflite">eflite</a>) or FreeTTS. -</p> -<p> - Yasr works by opening a pseudo-terminal and running a shell, intercepting - all input and output. It looks at the escape sequences being sent and - maintains a virtual <q>window</q> containing what it believes to be on the - screen. It thus does not use any features specific to Linux and can be - ported to other UNIX-like operating systems without too much trouble. -</p> -</a11y-pkg> - - -<h2><a id="gui" name="gui">Graphical User Interfaces</a></h2> -<p> -Accessibility of graphical user interfaces on UNIX platforms has only recently -received a significant upswing with the various development efforts around the -<a href="http://www.gnome.org/">GNOME Desktop</a>, especially the -<a href="https://wiki.gnome.org/Accessibility">GNOME Accessibility Project</a>. -</p> - - -<h2><a id="gnome" name="gnome">GNOME Accessibility Software</a></h2> - -<p> - A thorough list is available on the - <a href="https://blends.debian.org/accessibility/tasks/gnome">Gnome accessibility task page</a> -</p> - -<a11y-pkg name="Assistive Technology Service Provider Interface" tag="at-spi"> -<p> - This package contains the core components of GNOME Accessibility. - It allows Assistive technology providers like screen readers to - query all applications running on the desktop for accessibility - related information as well as provides bridging mechanisms to support - other toolkits than GTK. -</p> -<p> - Bindings to the Python language are provided in package - <a href="https://packages.debian.org/python-at-spi">python-at-spi</a>. -</p> -</a11y-pkg> -<a11y-pkg name="The ATK accessibility toolkit" tag="atk"> -<p> - ATK is a toolkit providing accessibility interfaces for applications or - other toolkits. By implementing these interfaces, those other toolkits or - applications can be used with tools such as screen readers, magnifiers, and - other alternative input devices. -</p> -<p> - The runtime part of ATK, needed to run applications built with it is available - in package <a href="https://packages.debian.org/libatk1.0-0">libatk1.0-0</a>. - Development files for ATK, needed for compilation of programs or toolkits - which use it are provided by package <a href="https://packages.debian.org/libatk1.0-dev">libatk1.0-dev</a>. - Ruby language bindings are provided by package - <a href="https://packages.debian.org/ruby-atk">ruby-atk</a>. -</p> -</a11y-pkg> -<a11y-pkg name="gnome-accessibility-themes" tag="gnome-accessibility-themes"> -<p> - The gnome-accessibility-themes package contains some high accessibility themes - for the GNOME desktop environment, designed for the visually impaired. -</p> -<p> - A total of 7 themes are provided, providing combinations of high, low - or inversed contrast, as well as enlarged text and icons. -</p> -</a11y-pkg> -<a11y-pkg name="gnome-orca" tag="gnome-orca" - url="http://live.gnome.org/Orca"> -<p> - Orca is a flexible and extensible screen reader - that provides access to the graphical desktop via user-customizable - combinations of speech, braille, and/or magnification. Under - development by the Sun Microsystems, Inc., Accessibility Program - Office since 2004, Orca has been created with early input from and - continued engagement with its end users. -</p> -<p> - Orca can use <a href="#speech-dispatcher">Speech Dispatcher</a> for delivering speech - output to the user. <a href="#brltty">BRLTTY</a> is used for braille display - support (and for seamless console and GUI braille review integration). -</p> -</a11y-pkg> - - -<h2><a id="kde" name="kde">KDE Accessibility Software</a></h2> - -<p> - A thorough list is available on the - <a href="https://blends.debian.org/accessibility/tasks/kde">KDE accessibility task page</a> -</p> - -<a11y-pkg name="kmag" tag="kmag"> -<p> - Magnify a part of the screen just as you would use a lens to magnify a - newspaper fine-print or a photograph. This application is useful for - a variety of people: from researchers to artists to web-designers - to people with low vision. -</p> -</a11y-pkg> - - -<h2><a id="input" name="input">Non-standard input methods</a></h2> - -<p> - A thorough list is available on the - <a href="https://blends.debian.org/accessibility/tasks/input">Input methods task page</a> -</p> - -<a11y-pkg name="Dasher" tag="dasher" url="http://www.inference.phy.cam.ac.uk/dasher/"> -<p> - Dasher is an information-efficient text-entry interface, driven by natural - continuous pointing gestures. Dasher is a competitive text-entry system - wherever a full-size keyboard cannot be used - for example, -</p> - <ul> - <li>on a palmtop computer</li> - <li>on a wearable computer</li> - <li>when operating a computer one-handed, by joystick, touchscreen, - trackball, or mouse</li> - <li>when operating a computer with zero hands (i.e., by head-mouse or by - eyetracker).</li> - </ul> -<p> - The eyetracking version of Dasher allows an experienced user to write text - as fast as normal handwriting - 25 words per minute; using a mouse, - experienced users can write at 39 words per minute. -</p> -<p> - Dasher uses a more advanced prediction algorithm than the T9(tm) system - often used in mobile phones, making it sensitive to surrounding context. -</p> -</a11y-pkg> -<a11y-pkg name="Caribou" tag="caribou" url="https://wiki.gnome.org/Projects/Caribou"> -<p> - Caribou is an input assistive technology intended for switch and pointer -users. It provides a configurable on-screen keyboard with scanning mode. -</p> -</a11y-pkg> diff --git a/greek/devel/debian-desktop/Makefile b/greek/devel/debian-desktop/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/devel/debian-desktop/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/devel/debian-desktop/index.wml b/greek/devel/debian-desktop/index.wml deleted file mode 100644 index fbc325f5f37..00000000000 --- a/greek/devel/debian-desktop/index.wml +++ /dev/null @@ -1,70 +0,0 @@ -#use wml::debian::template title="Debian on the Desktop" MAINPAGE="true" -#use wml::debian::recent_list -#use wml::debian::translation-check translation="21849af3149d448e7ee39af170c93bee402c4d3a" maintainer="galaxico" - -<link href="$(HOME)/font-awesome.css" rel="stylesheet" type="text/css"> - -<ul class="toc"> -<li><a href="#philosophy">Our Philosophy</a></li> -<li><a href="#help">How you can help</a></li> -<li><a href="#join">Join us</a></li> -</ul> - -<aside> -<p><span class="fas fa-caret-right fa-3x"></span> Debian Desktop is a group of volunteers who want to create the best possible operating system for home and corporate workstation use. Our motto: <q>Software that just works.</q> Our goal: bringing Debian, GNU, and Linux to the mainstream world.</p> -</aside> - -<h2><a id="philosophy">Our Philosophy</a></h2> - -<p> -We recognize that many -<a href="https://wiki.debian.org/DesktopEnvironment">Desktop -Environments</a> exist and will support the use of them – this includes -making sure they work well on Debian. Our goal is to make the graphical -interfaces easy to use for beginners while allowing advanced users and -experts to tweak things if they like. -</p> - -<p> -We will try to ensure that software is configured for the most common -desktop use. For example, the regular user account created during the -installation should have permission to play audio and video, print, -and manage the system through sudo. Also, we would like to keep -<a href="https://wiki.debian.org/debconf">debconf</a> (the Debian -configuration management system) questions to the absolute minimum. -There is no need to present difficult technical details during the -installation. Instead, we will try to ensure that debconf questions -make sense to the users. A novice may not even understand what these -questions are about. An expert, however, is perfectly happy to configure -the dekstop environment after the installation is complete. -</p> - -<h2><a id="help">How you can help</a></h2> - -<p> -We're looking for motivated people who make things happen. You don't have -to be a Debian Developer (DD) to submit patches or make packages. The -core Debian Desktop team will ensure that your work is integrated. So, -here are some things you can do to help: -</p> - -<ul> - <li>Test the default desktop environment (or any of the other desktops) for the upcoming release. Get one of the <a href="$(DEVEL)/debian-installer/">testing images</a> and send feedback to the <a href="https://lists.debian.org/debian-desktop/">debian-desktop mailing list</a>.</li> - <li>Join the <a href="https://wiki.debian.org/DebianInstaller/Team">Debian Installer Team</a> and help to improve the <a href="$(DEVEL)/debian-installer/">debian-installer</a> – the GTK+ frontend needs you.</li> - <li>You can help the <a href="https://wiki.debian.org/Teams/DebianGnome">Debian GNOME Team</a>, the <a href="https://qt-kde-team.pages.debian.net/"> Debian Qt/KDE Maintainers and Debian KDE Extras Team</a>, or the <a href="https://salsa.debian.org/xfce-team/">Debian Xfce Group</a> with packaging, bug fixing, documentation, tests and more.</li> - <li>Help to improve <a href="https://packages.debian.org/debconf">debconf</a> by lowering the priority of questions or removing unnecessary ones from packages. Make the necessary deconf questions easier to understand.</li> - <li>Got some designer skills? Then why not work on the <a href="https://wiki.debian.org/DebianDesktop/Artwork">Debian Desktop Artwork</a>.</li> -</ul> - -<h2><a id="join">Join us</a></h2> - -<aside class="light"> - <span class="fa fa-users fa-4x"></span> -</aside> - -<ul> - <li><strong>Wiki:</strong> Visit our <a href="https://wiki.debian.org/DebianDesktop">DebianDesktop</a> Wiki (some articles may be outdated).</li> - <li><strong>Mailing List:</strong> Discuss with us on the <a href="https://lists.debian.org/debian-desktop/">debian-desktop</a> mailing list.</li> - <li><strong>IRC Channel:</strong> Chat with us on IRC. Join the #debian-desktop channel on <a href="http://oftc.net/">OFTC IRC</a> (irc.debian.org)</li> -</ul> - diff --git a/greek/devel/debian-installer/builds.wml b/greek/devel/debian-installer/builds.wml deleted file mode 100644 index a91f4e1677a..00000000000 --- a/greek/devel/debian-installer/builds.wml +++ /dev/null @@ -1,89 +0,0 @@ -#use wml::debian::template title="Debian-Installer builds" -#use wml::debian::translation-check translation="c1221b640653be886b43ce18e8e72c5516aa770f" maintainer="galaxico" - -<h2>CD builds</h2> - -<p> -There are a number of different builds of the Debian-Installer CD images -that serve different purposes. -</p> -<p> -The most important build is <a href="index">the current official release</a>, currently -included in Debian 6.0. These images are static and unchanging, and are -the ones mostly likely to work for most people. While testing of these -images is still useful, most problems with them are well known by the -team within a few weeks of their release. See the <a href="errata">errata -page</a> for the worst of the known issues. -</p> -<p> -The other most commonly used builds are the daily builds. -These are newer images that need testing in the hopes -of one day becoming an official release. They are just a link to one of the -two types of images described below; which one is linked to depends on -where we are in our release cycle. -<a href="$(HOME)/releases/stable/i386/ch05s04#submit-bug">Installation reports</a> using these images are -very valuable to us. -</p> -<p> -<a href="https://cdimage.debian.org/cdimage/daily-builds/sid_d-i/">The sid_d-i -images</a> are new CD images produced each day. These images -use the version of the installer from the unstable distribution, although -they still install the testing distribution. Typically the daily CD build links point -at these images. -</p> -<p> -<a href="https://cdimage.debian.org/cdimage/daily-builds/jessie_d-i/">The -jessie_d-i images</a> are also produced each day. They use the version of -the installer from testing, and install testing. At release time, one -of these images is picked and becomes the official release image. Near a -release the links to daily CD builds will be switched to point to these -images, so that they can get testing. -</p> -<p> -<a href="https://cdimage.debian.org/cdimage/weekly-builds/i386/iso-cd/">The weekly full CD</a> -and <a href="https://cdimage.debian.org/cdimage/weekly-builds/i386/iso-dvd/">DVD</a> -builds take several days to build, so are -only regenerated once per week. The version of the installer on these -varies, but is generally the version we want to get tested at the current -time. -</p> - -<h2>initrd builds</h2> - -<p> -All the other Debian-Installer images, including netboot, -are collectively known as the <q>initrd images</q>. Again several different -builds are used. -</p> -<p> -As with the CD images, the most important initrd build is -<a href="index">the current official release</a>. -</p> -<p> -The other most commonly used initrd builds are the daily builds. -These images are built approximately once each day by -some Debian-Installer developers, typically on their own personal machines. -They always include the latest version of the installer, from the unstable -distribution. -</p> -<p> -From time to time an official Debian-Installer initrd build will be done, -as part of a release of the <tt>debian-installer</tt> package. These images -are built on the Debian autobuilder network like any other package, and are -placed in the <tt>dists/unstable/main/binary-<arch>/current</tt> -subdirectory. -</p> -<p> -When Debian-Installer is released, one of these official builds is copied -to the <tt>dists/testing/main/binary-<arch>/current</tt> -subdirectory. -</p> - -<h2>Build status page</h2> - -<p> -The status of all of the periodically built images is tracked and collected -on <a href="https://d-i.debian.org/daily-images/build-logs.html">the build -status page</a>. This page can't tell if the images work, only if it was -successfully built. -</p> diff --git a/greek/devel/debian-installer/errata.wml b/greek/devel/debian-installer/errata.wml deleted file mode 100644 index 438897268e4..00000000000 --- a/greek/devel/debian-installer/errata.wml +++ /dev/null @@ -1,66 +0,0 @@ -#use wml::debian::template title="Debian-Installer errata" -#use wml::debian::recent_list -#include "$(ENGLISHDIR)/devel/debian-installer/images.data" -#use wml::debian::translation-check translation="50ddc8fab8f8142c1e8266a7c0c741f9bfe1b23a" maintainer="galaxico" - -<h1>Errata for <humanversion /></h1> - -<p> -This is a list of known problems in the <humanversion /> release of the Debian -Installer. If you do not see your problem listed here, please send us an -<a href="$(HOME)/releases/stable/amd64/ch05s04#submit-bug">installation -report</a> describing the problem. -</p> - -<dl class="gloss"> - <dt>Broken rescue mode with the graphical installer</dt> - <dd>It was discovered during Bullseye RC 1 image testing that - the rescue mode seems broken (<a href="https://bugs.debian.org/987377">#987377</a>). - Additionally, the “Rescue” label in the banner needs to be - adjusted for the Bullseye theme. - <br /> - <b>Status:</b> Fixed in Bullseye RC 2.</dd> - - <dt>amdgpu firmware required for many AMD graphic cards</dt> - <dd>There seems to be a growing need to install amdgpu firmware - (through the non-free <code>firmware-amd-graphics</code> package) - to avoid a black screen when booting the installed system. As of - Bullseye RC 1, even when using an installation image that includes - all firmware packages, the installer doesn't detect the need for - that specific component. See the - <a href="https://bugs.debian.org/989863">umbrella bug report</a> - to keep track of our efforts. - <br /> - <b>Status:</b> Fixed in Bullseye RC 3.</dd> - - <dt>Firmwares required for some sound cards</dt> - <dd>There seems to be a number of sound cards that require loading a - firmware to be able to emit sound. As of Bullseye, the installer is - not able to load them early, which means that speech synthesis during - installation is not possible with such cards. A possible workaround is to - plug another sound card which does not need such firmware. - See the <a href="https://bugs.debian.org/992699">umbrella bug report</a> - to keep track of our efforts.</dd> - - <dt>Desktop installations may not work using CD#1 alone</dt> - <dd>Due to space constraints on the first CD, not all of the - expected GNOME desktop packages fit on CD#1. For a successful - installation, use extra package sources (e.g. a second CD or a - network mirror) or use a DVD instead. <br /> <b>Status:</b> It is - unlikely more efforts can be made to fit more packages on - CD#1. </dd> - - <dt>LUKS2 is incompatible with GRUB's cryptodisk support</dt> - <dd>It was only lately discovered that GRUB has no support for - LUKS2. This means that users who want to use - <tt>GRUB_ENABLE_CRYPTODISK</tt> and avoid a separate, - unencrypted <tt>/boot</tt>, won't be able to do so - (<a href="https://bugs.debian.org/927165">#927165</a>). This - setup isn't supported in the installer anyway, but it would - make sense to at least document this limitation more - prominently, and to have at least the possibility to opt for - LUKS1 during the installation process. - <br /> - <b>Status:</b> Some ideas have been expressed on the bug; cryptsetup maintainers have written <a href="https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html">some specific documentation</a>.</dd> - -</dl> diff --git a/greek/devel/debian-live/Makefile b/greek/devel/debian-live/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/devel/debian-live/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/devel/debian-live/index.wml b/greek/devel/debian-live/index.wml deleted file mode 100644 index f9573e9f9c3..00000000000 --- a/greek/devel/debian-live/index.wml +++ /dev/null @@ -1,29 +0,0 @@ -#use wml::debian::template title="Debian Live" NOHEADER="true" -#use wml::debian::translation-check translation="8377a51d59273f2581a58118cb3505bcdc6fce1c" maintainer="galaxico" - -<h1>The Debian Live Project</h1> - -<p>The Debian Live project produces the framework used to build live -systems based on Debian and the <a href="$(HOME)/CD/live/">official Debian Live -images</a> themselves.</p> - -<p>More information can be found at the <a -href="https://wiki.debian.org/DebianLive">Debian Live project wiki -pages</a>.</p> - -<h2>Contacting the team</h2> - -<p>You can reach the Debian Live team in one of the following ways:</p> -<ul> -<li>Bugs should be reported in the <a href="https://bugs.debian.org/">\ -Debian Bug Tracking System</a> against the appropriate package (e.g. -<a href="https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=live-wrapper">live-wrapper</a> or -one of the other -<a href="https://qa.debian.org/developer.php?login=debian-live%40lists.debian.org&comaint=yes">\ -packages maintained by the Debian Live Project</a>). -<li>You can send an email to the <a href="https://lists.debian.org/debian-live/">debian-live mailing list</a> -and use the archives to learn more about our activities. -<li>Team members and users are at times available on our -<a href="irc://irc.debian.org/debian-live">IRC channel</a>. -If you don't get a useful response, try our mailing list instead. -</ul> diff --git a/greek/devel/debian-med/Makefile b/greek/devel/debian-med/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/devel/debian-med/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/devel/debian-med/index.wml b/greek/devel/debian-med/index.wml deleted file mode 100644 index c00576bd355..00000000000 --- a/greek/devel/debian-med/index.wml +++ /dev/null @@ -1,110 +0,0 @@ -#use wml::debian::template title="Debian Med" -#use wml::debian::recent_list -#use wml::debian::translation-check translation="b9967d1f4d930716e9646a92bda776ced3c44cce" maintainer="galaxico" - -<h2>Project description</h2> - -<p>Debian Med is a - "<a href="https://blends.debian.org/blends/">Debian Pure Blend</a>" - with the aim to - develop Debian into an operating - system that is particularly well fit for the requirements for medical - practice and biomedical research. - The goal of Debian Med is a complete free and open system for all tasks in medical - care and research. To achieve this goal Debian Med integrates related - free and open source software for medical imaging, bioinformatics, - clinic IT infrastructure, and others within Debian OS. -</p> - - -<p>Debian Med contains a set of metapackages that declare dependencies on - other Debian packages, and that way the complete system is prepared for - solving particular tasks. - The best overview about Debian Med is given - at the <a href="https://blends.debian.org/med/tasks/">tasks page</a>. -</p> - -<p>For a more in-depth discussion, - <a href="https://people.debian.org/~tille/talks/">several talks about - Debian Med and Debian Pure Blends in general</a> - are available as slides, partly with video recording. -</p> - - -<h2>Contact and developer information</h2> - -<p> -The <a href="mailto:debian-med@lists.debian.org">Debian Med mailing -list</a> is the central point of communication -for Debian Med. It serves as a forum for potential, as well as current, -users of the Debian system who want to use their computer for -medical tasks. Additionally, it is used to coordinate development -efforts around the various topics of Medicine. You can subscribe to -and unsubscribe from it using the -<a href="https://lists.debian.org/debian-med/">list web page</a>. -You will also find the list archives on that page. -</p> -<p> -Important places for developer information: -</p> -<ol> - <li><a href="https://wiki.debian.org/DebianMed">The Wiki page</a></li> - <li><a href="https://blends.debian.org/med/">The Blends page</a></li> - <li>The <a href="https://med-team.pages.debian.net/policy/">Debian Med policy</a> which explains packaging rules in the team</li> - <li><a href="https://salsa.debian.org/med-team/">Git repositories of Debian Med packages on Salsa</a></li> -</ol> - -<h2>Included software projects</h2> - -The <a href="https://blends.debian.org/blends">Debian Pure Blends</a> system -provides an autogenerated overview of all included software of a Blend. -Just have a look at the so called -<b><a href="https://blends.debian.org/med/tasks/">tasks pages of -Debian Med</a></b> to learn about all included software and projects which -are on our todo list for inclusion into Debian. - - -<h2>Project goals</h2> - -<ul> - <li>Build a solid software base for medical health care with emphasis on easy - installation, easy maintenance and security.</li> - <li>Encourage the co-operation of authors of different software projects - with similar goals.</li> - <li>Test suite for easy evaluation of the quality of medical software.</li> - <li>Provide information and documentation of medical software.</li> - <li>Help upstream authors to get their products packaged for - Debian.</li> - <li>Show commercial software companies the strengths of a solid base - system and make them consider to port their software to Linux or - even to switch to Open Source.</li> -</ul> - - -<h2>What can I do to help?</h2> - -<p> - There is a <a href="https://wiki.debian.org/DebianMedTodo">Wiki page containing - a list of things</a> which can be done to help the project. -</p> - -<h2>Marketing & PR</h2> - -<p>Once we have something to show for this project, and indeed even in - the formative stages of this project, we are being watched by the - eyes of the world. We will necessarily want to work with - press@debian.org to get the word out and to help give Debian and - this project the kind of exposure we want. For this purpose we will - build a collection of slides of talks about Debian Med. -</p> - - -<h2>Links</h2> - -<ul> - <li>Debian Med is working closely together with - <a href="http://nebc.nerc.ac.uk/tools/bio-linux/bio-linux-6.0">Bio-Linux</a>. - While Bio-Linux is based on Ubuntu LTS releases the packages of biologic - scope are maintained inside Debian by the Debian Med team. - </li> -</ul> diff --git a/greek/devel/developers.loc.wml b/greek/devel/developers.loc.wml deleted file mode 100644 index fa113ad1be9..00000000000 --- a/greek/devel/developers.loc.wml +++ /dev/null @@ -1,58 +0,0 @@ -#use wml::debian::template title="Developer Locations" MAINPAGE="true" -#use wml::debian::recent_list -#use wml::debian::translation-check translation="bd2e76d96db915ccd0dee367a373417db7422565" maintainer="galaxico" - -<link href="$(HOME)/font-awesome.css" rel="stylesheet" type="text/css"> - -<aside> -<p><span class="fas fa-caret-right fa-3x"></span> Where are the Debian Developers (DD) located? If a DD has specified the home coordinates in the developer database, it's visible in our World Map.</p> -</aside> - -<p> -The map below was generated from an anonymized <a -href="developers.coords">list of developer coordinates</a> using the -program <a href="https://packages.debian.org/stable/graphics/xplanet"> -xplanet</a>. -</p> - -<img src="developers.map.jpeg" alt="World Map"> - -<h2>How to add your Coordinates</h2> - -<p> -If you would like to add your coordinates to your database entry, log in -to the <a href="https://db.debian.org">Debian Developers' Database</a> -and modify your entry. If you don't know the coordinates of your home -town, you can use <a href="https://www.openstreetmap.org">OpenStreetMap</a> to look -them up. Search for your city and select the direction arrows next to the -search field. Drag the green marker to the OSM map, and the coordinates -will appear in the <em>From</em> field. -</p> - -<p>The format for coordinates is one of the following:</p> - -<dl> - <dt>Decimal Degrees</dt> - <dd>The format is <code>+-DDD.DDDDDDDDDDDDDDD</code>. Programs like - Xearth and many other positioning web sites use it. The precision is - limited to 4 or 5 decimals.</dd> - <dt>Degrees Minutes (DGM)</dt> - <dd>The format is <code>+-DDDMM.MMMMMMMMMMMMM</code>. It's not - arithmetic, but a packed representation of two separate units: degrees - and minutes. This output is common with some types of handheld GPS - devices and NMEA format GPS messages.</dd> - <dt>Degrees Minutes Seconds (DGMS)</dt> - <dd>The format is <code>+-DDDMMSS.SSSSSSSSSSS</code>. Like DGM, it's - not arithmetic, but a packed representation of three separate units: - degrees, minutes, and seconds. This output is typically derived - from web sites which give 3 values for each position. For example, - <code>34:50:12.24523 North</code> might be the given position, and in - DGMS it would be <code>+0345012.24523</code>.</dd> -</dl> - -<p> -<strong>Please note:</strong> <code>+</code> is North for latitude, -<code>+</code> is East for longitude. It's important to specify enough -leading zeros to dis-ambiguate the format being used if your position -is less than 2 degrees from a zero point. -</p> diff --git a/greek/devel/dmup.1.1.1.wml b/greek/devel/dmup.1.1.1.wml deleted file mode 100644 index d3ecf5a5126..00000000000 --- a/greek/devel/dmup.1.1.1.wml +++ /dev/null @@ -1,337 +0,0 @@ -#use wml::debian::template title="Debian Machine Usage Policies" NOHEADER=yes -#use wml::debian::translation-check translation="b8114b588961778dbd04974c1464a2f388a90c28" maintainer="galaxico" - -<h2>Debian Machine Usage Policies</h2> - -<p>This is the historical version 1.1.1 of the <i>Debian Machine Usage -Policies</i>, which was superseded by the <a href="dmup">current -version 1.1.2</a>, as announced <a -href="https://lists.debian.org/debian-devel-announce/2010/05/msg00001.html">May -9th, 2010</a>.</p> - -<ol> -<li><strong>Introduction</strong><br> - -This document describes the policies for using -<a href="https://db.debian.org/machines.cgi">Debian machines</a> and -all rules surrounding those. - -<p>In short: -<ul> -<li>Don't by any wilful, deliberate, reckless or unlawful act interfere - with the work of another developer or jeopardize the integrity of data - networks, computing equipment, systems programs, or other stored - information. - -<li>Don't use Debian Facilities for private financial gain or for - commercial purposes, including consultancy or any other work outside - the scope of official duties or functions for the time being, without - specific authorization to do so. - -<li>Don't use Debian Facilities for unlawful activities, including, but - not limited to, software piracy. -</ul> - -<p>This document contains two parts: policies and guidelines. The rules -in the policies are binding and may not be violated. The guidelines -specify rules that may be violated if necessary but we would rather -one did not. - - -<li><strong>General statements</strong><br> - -<ol> -<li> Privilege<br> -Access to Debian Facilities is a privilege, not a right or a -commercial service, and we reserve the right to revoke this privilege -at any time, without prior notice. An explanation will be given within -48 hours. - -<li> Guarantees<br> -There is no guarantee of service. Although we will do our best to assure -that everything functions perfectly, we can't give any guarantees. - -<li> Privacy<br> -If necessary to keep machines working properly the DSA is allowed to edit -user files. (for example modifying .forward files to break mail loops.) - -<li> Used abbreviations<br> - <ul> - <li>DSA - Debian Systems Administration - <li>DMUP - Debian Machine Usage Policy (this document) - <li>DPL - Debian Project Leader - </ul> -</ol> - -<li><strong>Penalties</strong><br> - -If someone violates the rules set in this document they will be subjected -to a penalty. The penalty depends on the number of previous violations -and the offense involved. - -<ol> -<li> First offense<br> - -<ol> -<li>The accounts of the offender will be suspended and access will - not be available. - -<li>The offender will be required to contact the Debian Systems Administration - and convince us that there will be no further breaches of the DMUP by the - offender. - -<li>If the offender fails to contact the DSA within 14 days, the account will - be terminated and the offender expelled from the Debian project. If the - offender has announced they will be on vacation in this time frame this - period will be extended with the announced duration of the vacation. - -<li>If the offender is expelled from the project they can register to become - a maintainer again after a period of a month. The offense will remain - on record. -</ol> - - -<li> Second offense<br> - -<ol> -<li>The offender's accounts will be suspended immediately and the - offender expelled from the project. -<li>If the offender does not file for an appeal within the designated - time frame the account is terminated. - -<li>The offender is prohibited from registering as a Debian maintainer - again. -</ol> - - -<li> Publication<br> - -<ol> -<li>The offense and the penalty will be announced to Debian developers only. - -<li>Should it, in the sole opinion of the Debian project leader, be considered - necessary, then a public announcement will be made. This can include - the offender's identity. -</ol> - - -<li> Appeal<br> - -<ol> -<li>If the offender does not agree with the decision made by the DSA they can - appeal to the developers. This is only possible in the 14 days directly - following the day the offender was informed of the sentence. This is - done using the procedure as detailed in section 4.2 of the Debian - constitution. - -<li>During the time the appeal is processed the account will remain suspended. -</ol> -</ol> - - -<li><strong>The policies</strong><br> - -This section lists the policies. This list is not and cannot be comprehensive. - - -<dl> -<dt>Disk usage: - -<dd>All machines run a /tmp cleanup daemon and expire files after a week. -Some machines have /scratch partitions specifically for storing large -data sets without fear of them being erased. If you receive an email -notification that your homedir is large and that we need more space then -please promptly take action. The DSA's may find it necessary to clean up -exceptionally large space users without warning. - -<dt>Shell: - -<dd>Please use ssh/scp if at all possible rather than less secure alternatives -(rsh, telnet or FTP). - -<p>Idle connections are killed after an hour; this is easy to bypass, -but please don't do so without good cause. - -<p>Mirroring via any private means any portion of the public archives from -the private servers is strictly forbidden without the prior consent of the -residing Mirror Master. Developers are free to use any publicly available -forms of access. - -<dt>Processes: - -<dd>Do not run any long running process without the permission of the DSA's. -Running servers of any sort (this includes IRC bots) without prior permission -from the DSA's is also forbidden. Avoid running processes that are abusive in -CPU or memory. If necessary the DSA's will reap up such processes without -warning. - - -<dt>WWW pages: - -<dd>In general, web space on Debian machines is provided for the purpose of -communicating ideas and files related to the project, or to the Free -Software community in general. Private 'vanity' pages on Debian machines -are discouraged. - -<p>Commercial web pages are not permitted. - -<p>You are responsible for the content of your WWW pages, including -obtaining the legal permission for any works they include and ensuring -that the contents of these pages do not violate the laws that apply to -the location of the server. - -<p>You are responsible for and accept responsibility for any defamatory, -confidential, secret or other proprietary material available via your -WWW pages. - -<p>You may not advertise your WWW pages, or cause another person to -advertise it, by techniques that would be classified as abuse if they -were carried out from a Debian Account. This includes, but is not -limited to, bulk emailing and excessive news posting. Such action may -be treated under the appropriate DMUP as if it had been done from the -Account, or as a violation of this DMUP or both. - -<dt>Mail/News: - -<dd>Using Debian machines for reading mail is OK, please choose a lightly -loaded machine [ie not master]. We do not support the use of mail download -methods such as POP or IMAP, use your ISP's mail server and forwarding. As -with web pages incoming mail is generally encouraged to be of a Free -Software nature or related to the project somehow. The DSA's may find it -necessary to compress, relocate or erase mail without warning. -</dl> - -<p>If a Developer becomes unreachable for a prolonged time their accounts, -data and mail forwarding/filtering/etc may be disabled until they -reappear. - - -<p>Don't use Debian facilities in a manner which constitutes net abuse. -Debian does not have any Usenet news servers. It may be that some of the -Debian machines have access to such a news server, but their use through -Debian machines is strictly forbidden. - -<p>Examples of what we consider net abuse: - -<ul> -<li><em>Chain Letters and Ponzi Pyramid-Selling Schemes</em><br> - - Such messages work (or rather, don't work) in much the same - way as their paper-based cousins. The most common example of - this in email is MAKE-MONEY-FAST. In addition to being a - waste of resources, such messages are illegal in certain - countries. - -<li><em>Unsolicited Commercial Email (UCE)</em><br> - - Unsolicited Commercial Email is advertising material - received by email without the recipient either requesting - such information or otherwise expressing an interest in the - material advertised. - - <p>Since many Internet users use a dial-up connection and pay - for their online time, it costs them money to receive - email. Receipt of unsolicited commercial advertising - therefore costs them money and is particularly unwelcome. - - <p>It should be noted that a user has not expressed an interest - by the mere act of posting a news article in any particular - newsgroup, unless of course they have made a specific - request for information to be emailed to them. - -<li><em>Unsolicited Bulk Email (UBE)</em><br> - - Similar to the above UCE but not attempting to sell - anything. Its sole purpose is usually to annoy. - -<li><em>Forged headers and / or Addresses</em><br> - - Forging headers or messages means sending mail such that its - origin appears to be another user or machine, or a - non-existent machine. - - <p>It is also forgery to arrange for any replies to the mail to - be sent to some other user or machine. - - <p>However, in either case, if prior permission has been - granted to you by the other user or the administrators of - the other machine, then there is no problem, and of course - "null" reverse paths can be used as defined in the relevant - RFCs. - -<li><em>Mail Bombing</em><br> - - Mail bombing is the sending of multiple emails, or one large - email, with the sole intent of annoying and / or seeking - revenge on a fellow Internet user. It is wasteful of shared - Internet resource as well as serving no value to the - recipient. - - <p>Due to the time taken to download it, sending long email to - sites without prior agreement can amount to denial of - service, or access to email at the receiving site. Note that - if binary attachments are added to mail this may increase - the size considerably. If prior arrangement has not been - made, the mail will be extremely unwelcome. - -<li><em>Denial of Service attacks</em><br> - - Denial of Service is any activity designed to prevent a - specific host on the Internet making full and effective use - of their facilities. This includes, but is not limited to: - - <ul> - <li>Mail bombing an address in such a way to make their - Internet access impossible, difficult, or costly. - <li>Opening an excessive number of mail connections to the - same host. - <li>Intentionally sending email designed to damage the - receiver's systems when interpreted; for example, sending - malicious programs or viruses attached to an email. - <li>Using a smarthost or SMTP relay without authorization to do so. - </ul> - -<li><em>Mailing List Subscriptions</em><br> - - You must not subscribe anyone, other than a user on your own - host, to a mail list or similar service without their - permission. - -<li><em>Illegal Content</em><br> - - You must not send via email any item which it is illegal to - send or possess. - -<li><em>Breach of Copyright or Intellectual Property</em><br> - - You must not send (via email) or post Copyright material or - Intellectual Property unless you have permission to do so. - -<li><em>Binary Postings to non-Binary Groups</em><br> - - Outside of the alt.binaries... and alt.pictures... newsgroup - hierarchies, the posting of encoded binary data is - considered most unwelcome. The majority of Usenet sites and - readers do not have the capability for selective - transmission of articles (kill-filing) and such posts can - result in a significant amount of resources being tied up - and wasted in the transmission process, and as such can be - considered as a denial of service attack on multiple - recipients. [Example] - -<li><em>Excessive Cross-Posting</em><br> - - Simply put, this form of unacceptable behavior occurs when - the same article is cross-posted to a large number of - unrelated newsgroups. - -<li><em>Excessive Multi-Posting</em><br> - - Simply put, this form of unacceptable behavior occurs when - a substantively similar (perhaps differing only in Subject - header) article is posted to a large number of unrelated - newsgroups. -</ul> - - -</ol> diff --git a/greek/devel/dmup.wml b/greek/devel/dmup.wml deleted file mode 100644 index 50d3264bb63..00000000000 --- a/greek/devel/dmup.wml +++ /dev/null @@ -1,341 +0,0 @@ -#use wml::debian::template title="Debian Machine Usage Policies" NOHEADER=yes -#use wml::debian::translation-check translation="b8114b588961778dbd04974c1464a2f388a90c28" maintainer="galaxico" - -<h2>Debian Machine Usage Policies</h2> -<p> -Version 1.1.2<br> -This version of the Debian Machine Usage Policies becomes effective on -July 4th, 2010 and supersedes all previous <a -href="dmup.1.1.1">versions</a>. It was <a -href="https://lists.debian.org/debian-devel-announce/2010/05/msg00001.html">announced -on May 9th, 2010</a>.</p> - -<ol> -<li><strong>Introduction</strong><br> - -This document describes the policies for using -<a href="https://db.debian.org/machines.cgi">Debian machines</a> and -all rules surrounding those. - -<p>In short: -<ul> -<li>The Debian Systems Administration Team will do whatever is necessary - to keep all machines and services working and running in a secure - fashion. - -<li>Don't by any wilful, deliberate, reckless or unlawful act interfere - with the work of another developer or jeopardize the integrity of data - networks, computing equipment, systems programs, or other stored - information. - -<li>Don't use Debian Facilities for private financial gain or for - commercial purposes, including consultancy or any other work outside - the scope of official duties or functions for the time being, without - specific authorization to do so. - -<li>Don't use Debian Facilities for unlawful activities, including, but - not limited to, software piracy. -</ul> - -<p>This document contains two parts: policies and guidelines. The rules -in the policies are binding and may not be violated. The guidelines -specify rules that may be violated if necessary but we would rather -one did not. - - -<li><strong>General statements</strong><br> - -<ol> -<li> Used abbreviations<br> - <ul> - <li>DSA - Debian Systems Administration - <li>DMUP - Debian Machine Usage Policy (this document) - <li>DPL - Debian Project Leader - <li>DAM - Debian Account Managers - </ul> - -<li> Privilege<br> -Access to Debian Facilities is a privilege, not a right or a -commercial service, and DSA reserves the right to revoke this privilege -at any time, without prior notice. An explanation will be given within -48 hours. - -<li> Guarantees<br> -There is no guarantee of service. Although DSA will do its best to assure -that everything functions perfectly, they can't give any guarantees. - -<li> Privacy<br> -If necessary to keep machines working properly the DSA is allowed to edit -user files. (for example modifying .forward files to break mail loops.) -</ol> - -<li><strong>Penalties</strong><br> - -If someone violates the rules set in this document they will be subjected -to a penalty. The penalty depends on the number of previous violations -and the offense involved. - -<ol> -<li> First offense<br> - -<ol> -<li>The accounts of the offender will be suspended and access will - not be available. - -<li>The offender will be required to contact DSA and convince them - that there will be no further breaches of the DMUP by the offender. - -<li>If the offender fails to contact DSA within 14 days, DSA - will suspend the corresponding account and propose to DAM the - expulsion of the offender from the Debian project. If the offender - has announced they will be on vacation in this time frame, - this period will be extended with the announced duration of - the vacation. -<li>If the offender is expelled from the project they can register to become - a maintainer again after a period of a month. The offense will remain - on record. -</ol> - - -<li> Second offense<br> - -<ol> -<li>The offender's accounts will be suspended immediately and - DSA will propose to DAM the expulsion of the offender from - the Debian project. -<li>If the offender does not file for an appeal within the designated - time frame the account is terminated. - -</ol> - - -<li> Publication<br> - -<ol> -<li>The offense and the penalty will be announced to Debian developers only. - -<li>Should it, in the sole opinion of the Debian project leader, be considered - necessary, then a public announcement will be made. This can include - the offender's identity. -</ol> - - -<li> Appeal<br> - -<ol> -<li>If the offender does not agree with the decision made by DSA they - can appeal to the developers. This is only possible in the 14 days directly - following the day the offender was informed of the sentence. This is - done using the procedure as detailed in section 4.2 of the Debian - constitution. - -<li>During the time the appeal is processed the account will remain suspended. -</ol> -</ol> - - -<li><strong>The policies</strong><br> - -This section lists the policies. This list is not and cannot be comprehensive. - - -<dl> -<dt>Disk usage: - -<dd>All machines run a /tmp cleanup daemon and expire files after a week. -Some machines have /scratch partitions specifically for storing large -data sets without fear of them being erased. If you receive an email -notification that your homedir is large and that more free space is -needed then please promptly take action. DSA may find it necessary to -clean up without warning. - -<dt>Shell: - -<dd>Please use ssh/scp if at all possible rather than less secure alternatives -(rsh, telnet or FTP). - -<p>Idle connections are killed after an hour; this is easy to bypass, -but please don't do so without good cause. - -<p>Mirroring via any private means any portion of the public archives from -the private servers is strictly forbidden without the prior consent of the -residing Mirror Master. Developers are free to use any publicly available -forms of access. - -<dt>Processes: - -<dd>Do not run any long running process without the permission of DSA. -Running servers of any sort (this includes IRC bots) without prior -permission from DSA is also forbidden. Avoid running processes that are -abusive in CPU or memory. If necessary DSA will clean up such processes -without warning. - -<dt>WWW pages: - -<dd>In general, web space on Debian machines is provided for the purpose of -communicating ideas and files related to the project, or to the Free -Software community in general. Private 'vanity' pages on Debian machines -are discouraged. - -<p>Commercial web pages are not permitted. - -<p>You are responsible for the content of your WWW pages, including -obtaining the legal permission for any works they include and ensuring -that the contents of these pages do not violate the laws that apply to -the location of the server. - -<p>You are responsible for and accept responsibility for any defamatory, -confidential, secret or other proprietary material available via your -WWW pages. - -<p>You may not advertise your WWW pages, or cause another person to -advertise it, by techniques that would be classified as abuse if they -were carried out from a Debian Account. This includes, but is not -limited to, bulk emailing and excessive news posting. Such action may -be treated under the appropriate DMUP as if it had been done from the -Account, or as a violation of this DMUP or both. - -<dt>Mail/News: - -<dd>Using Debian machines for reading mail is OK, please choose a -lightly loaded machine. We do not support the use of mail download -methods such as POP or IMAP, use your ISP's mail server and forwarding. -As with web pages incoming mail is generally encouraged to be of a Free -Software nature or related to the project somehow. DSA may find it -necessary to compress, relocate or erase mail without warning. -</dl> - -<p>If a Developer becomes unreachable for a prolonged time, their -accounts, data and mail forwarding/filtering/etc may be disabled until -they reappear. - - -<p>Don't use Debian facilities in a manner which constitutes net abuse. -Debian does not have any Usenet news servers. It may be that some of the -Debian machines have access to such a news server, but their use through -Debian machines is strictly forbidden. - -<p>Examples of what DSA considers net abuse: - -<ul> -<li><em>Chain Letters and Ponzi Pyramid-Selling Schemes</em><br> - - Such messages work (or rather, don't work) in much the same - way as their paper-based cousins. The most common example of - this in email is MAKE-MONEY-FAST. In addition to being a - waste of resources, such messages are illegal in certain - countries. - -<li><em>Unsolicited Commercial Email (UCE)</em><br> - - Unsolicited Commercial Email is advertising material - received by email without the recipient either requesting - such information or otherwise expressing an interest in the - material advertised. - - <p>Since many Internet users use a dial-up connection and pay - for their online time, it costs them money to receive - email. Receipt of unsolicited commercial advertising - therefore costs them money and is particularly unwelcome. - - <p>It should be noted that a user has not expressed an interest - by the mere act of posting a news article in any particular - newsgroup, unless of course they have made a specific - request for information to be emailed to them. - -<li><em>Unsolicited Bulk Email (UBE)</em><br> - - Similar to the above UCE but not attempting to sell - anything. Its sole purpose is usually to annoy. - -<li><em>Forged headers and / or Addresses</em><br> - - Forging headers or messages means sending mail such that its - origin appears to be another user or machine, or a - non-existent machine. - - <p>It is also forgery to arrange for any replies to the mail to - be sent to some other user or machine. - - <p>However, in either case, if prior permission has been - granted to you by the other user or the administrators of - the other machine, then there is no problem, and of course - "null" reverse paths can be used as defined in the relevant - RFCs. - -<li><em>Mail Bombing</em><br> - - Mail bombing is the sending of multiple emails, or one large - email, with the sole intent of annoying and / or seeking - revenge on a fellow Internet user. It is wasteful of shared - Internet resource as well as serving no value to the - recipient. - - <p>Due to the time taken to download it, sending long email to - sites without prior agreement can amount to denial of - service, or access to email at the receiving site. Note that - if binary attachments are added to mail this may increase - the size considerably. If prior arrangement has not been - made, the mail will be extremely unwelcome. - -<li><em>Denial of Service attacks</em><br> - - Denial of Service is any activity designed to prevent a - specific host on the Internet making full and effective use - of their facilities. This includes, but is not limited to: - - <ul> - <li>Mail bombing an address in such a way to make their - Internet access impossible, difficult, or costly. - <li>Opening an excessive number of mail connections to the - same host. - <li>Intentionally sending email designed to damage the - receiver's systems when interpreted; for example, sending - malicious programs or viruses attached to an email. - <li>Using a smarthost or SMTP relay without authorization to do so. - </ul> - -<li><em>Mailing List Subscriptions</em><br> - - You must not subscribe anyone, other than a user on your own - host, to a mail list or similar service without their - permission. - -<li><em>Illegal Content</em><br> - - You must not send via email any item which it is illegal to - send or possess. - -<li><em>Breach of Copyright or Intellectual Property</em><br> - - You must not send (via email) or post Copyright material or - Intellectual Property unless you have permission to do so. - -<li><em>Binary Postings to non-Binary Groups</em><br> - - Outside of the alt.binaries... and alt.pictures... newsgroup - hierarchies, the posting of encoded binary data is - considered most unwelcome. The majority of Usenet sites and - readers do not have the capability for selective - transmission of articles (kill-filing) and such posts can - result in a significant amount of resources being tied up - and wasted in the transmission process, and as such can be - considered as a denial of service attack on multiple - recipients. [Example] - -<li><em>Excessive Cross-Posting</em><br> - - Simply put, this form of unacceptable behavior occurs when - the same article is cross-posted to a large number of - unrelated newsgroups. - -<li><em>Excessive Multi-Posting</em><br> - - Simply put, this form of unacceptable behavior occurs when - a substantively similar (perhaps differing only in Subject - header) article is posted to a large number of unrelated - newsgroups. -</ul> - - -</ol> diff --git a/greek/devel/extract_key.wml b/greek/devel/extract_key.wml deleted file mode 100644 index 6ad24ba72ef..00000000000 --- a/greek/devel/extract_key.wml +++ /dev/null @@ -1,6 +0,0 @@ -#use wml::debian::template title="Extracting a developer's PGP/GPG Key" -#use wml::debian::translation-check translation="e0e8489e695219a95c1630c9211978a2eaee0637" maintainer="galaxico" - -<p>Search for the developer in the -<a href="https://db.debian.org/">Developers' Database</a> and then click -on the “PGP/GPG fingerprint” link(s) once you have found them. diff --git a/greek/devel/index.wml b/greek/devel/index.wml deleted file mode 100644 index 3286702c182..00000000000 --- a/greek/devel/index.wml +++ /dev/null @@ -1,255 +0,0 @@ -#use wml::debian::template title="Debian Developers' Corner" MAINPAGE="true" -#use wml::debian::recent_list -#use wml::debian::translation-check translation="9a3deb4236c92e083ea1e494362dc1ff242f6a8c" maintainer="galaxico" - -<link href="$(HOME)/font-awesome.css" rel="stylesheet" type="text/css"> - -<aside> -<p><span class="fas fa-caret-right fa-3x"></span> Though all information on this page and all links to other pages are publicly available, this site is primarily aimed at Debian developers.</p> -</aside> - -<ul class="toc"> -<li><a href="#basic">Basic</a></li> -<li><a href="#packaging">Packaging</a></li> -<li><a href="#workinprogress">Work in Progress</a></li> -<li><a href="#projects">Projects</a></li> -<li><a href="#miscellaneous">Miscellaneous</a></li> -</ul> - -<div class="row"> - - <!-- left column --> - <div class="column column-left" id="basic"> - <div style="text-align: center"> - <span class="fa fa-users fa-3x" style="float:left;margin-right:5px;margin-bottom:5px;"></span> - <h2><a id="basic">General Information</a></h2> - <p>A list of current developers and maintainers, how to join the project, and links to the developers' database, the constitution, the voting process, releases, and architectures.</p> - </div> - - <div style="text-align: left"> - <dl> - <dt><a href="$(HOME)/intro/organization">Debian Organization</a></dt> - <dd>Over one thousand volunteers are part of the Debian project. This page explains Debian's organizational structure, lists teams and their members as well as contact addresses.</dd> - <dt><a href="$(HOME)/intro/people">People behind Debian</a></dt> - <dd><a href="https://wiki.debian.org/DebianDeveloper">Debian Developers (DD)</a> (full members of the Debian project) and <a href="https://wiki.debian.org/DebianMaintainer">Debian Maintainers (DM)</a>, contribute to the project. Please have a look at the <a href="https://nm.debian.org/public/people/dd_all/">list of Debian Developers</a> and the <a href="https://nm.debian.org/public/people/dm_all/">list of Debian Maintainers</a> to find out more about the people involved. We also have a <a href="developers.loc">world map of Debian developers</a>.</dd> - <dt><a href="join/">How to join Debian</a></dt> - <dd>Would you like to contribute and join the project? We're always looking for new developers or free software enthusiasts with technical and non-technical skills. For more information, please visit this page.</dd> - <dt><a href="https://db.debian.org/">Developer Database</a></dt> - <dd>Some information in this database is accessible to everybody, some information only to developers who have logged in. The database contains information such as <a href="https://db.debian.org/machines.cgi">project machines</a> and developers' GnuPG keys. - To extract a developer's key click on the “PGP/GPG fingerprint” link(s) once you have found them. - Developers can <a href="https://db.debian.org/password.html">change their password</a> and set up <a href="https://db.debian.org/forward.html">mail forwarding</a> for their Debian account. If you're planning to use one of the Debian machines, please make sure to read the <a href="dmup">Debian Machine Usage Policies</a>.</dd> - <dt><a href="constitution">The Constitution</a></dt> - <dd>This document describes the organizational structure for formal decision-making in the project. - </dd> - <dt><a href="$(HOME)/vote/">Voting Information</a></dt> - <dd>How we elect our leaders, choose our logos and how we vote in general.</dd> - <dt><a href="$(HOME)/releases/">Releases</a></dt> - <dd>This page lists current releases (<a href="$(HOME)/releases/stable/">stable</a>, <a href="$(HOME)/releases/testing/">testing</a>, and <a href="$(HOME)/releases/unstable/">unstable</a>) and contains an index of old releases and their codenames.</dd> - <dt><a href="$(HOME)/ports/">Different Architectures</a></dt> - <dd>Debian runs on many different architectures. This page collects information about various Debian ports, some based on the Linux kernel, others based on the FreeBSD, NetBSD and Hurd kernels.</dd> - - </dl> - </div> - - </div> - - <!-- right column --> - <div class="column column-right" id="software"> - <div style="text-align: center"> - <span class="fa fa-code fa-3x" style="float:left;margin-right:5px;margin-bottom:5px;"></span> - <h2><a id="packaging">Packaging</a></h2> - <p>Links to our policy manual and other documents related to the Debian policy, procedures and other resources for Debian developers, and the new maintainers' guide.</p> - </div> - - <div style="text-align: left"> - <dl> - <dt><a href="$(DOC)/debian-policy/">Debian Policy Manual</a></dt> - <dd>This manual describes the policy requirements for the Debian distribution. This includes the structure and contents of the Debian archive, several design issues of the operating system as well as technical requirements which each package must satisfy to be included in the distribution. - - <p>In short, you <strong>need</strong> to read it.</p> - </dd> - </dl> - - <p>There are several other documents related to the policy that you might be - interested in:</p> - - <ul> - <li><a href="https://wiki.linuxfoundation.org/lsb/fhs/">Filesystem Hierarchy Standard</a> (FHS) - <br />The FHS defines the directory structure - and directory contents (location of files); - compliance with version 3.0 is mandatory (see <a - href="https://www.debian.org/doc/debian-policy/ch-opersys.html#file-system-hierarchy">chapter - 9</a> of the Debian Policy Manual).</li> - <li>List of <a href="$(DOC)/packaging-manuals/build-essential">build-essential packages</a> - <br />You are expected to have these packages if you want to - compile software, build a package or a set of packages. You don't - have to include them in <code>Build-Depends</code> line when <a - href="https://www.debian.org/doc/debian-policy/ch-relationships.html">declaring - relationships</a> between packages.</li> - <li><a href="$(DOC)/packaging-manuals/menu-policy/">Menu system</a> - <br />Debian's structure of menu entries; please check the - <a href="$(DOC)/packaging-manuals/menu.html/">menu system</a> - documentation as well.</li> - <li><a href="$(DOC)/packaging-manuals/debian-emacs-policy">Emacs Policy</a></li> - <li><a href="$(DOC)/packaging-manuals/java-policy/">Java Policy</a></li> - <li><a href="$(DOC)/packaging-manuals/perl-policy/">Perl Policy</a></li> - <li><a href="$(DOC)/packaging-manuals/python-policy/">Python Policy</a></li> - <li><a href="$(DOC)/packaging-manuals/debconf_specification.html">Debconf Specification</a></li> - <li><a href="https://www.debian.org/doc/manuals/dbapp-policy/">Database Application Policy</a> (draft)</li> - <li><a href="https://tcltk-team.pages.debian.net/policy-html/tcltk-policy.html/">Tcl/Tk Policy</a> (draft)</li> - <li><a href="https://people.debian.org/~lbrenta/debian-ada-policy.html">Debian Policy for Ada</a></li> - </ul> - - <p>Please take a look at <a - href="https://bugs.debian.org/debian-policy">proposed updates to - Debian Policy</a>, too.</p> - - <dl> - <dt><a href="$(DOC)/manuals/developers-reference/">Developers' Reference</a></dt> - - <dd> - Overview of the recommended procedures and the available resources - for Debian developers -- another <strong>must-read</strong>. - </dd> - - <dt><a href="$(DOC)/manuals/debmake-doc/">Guide for Debian Maintainers</a></dt> - - <dd> - How to build a Debian package (in common language), including - lots of examples. If you're planning to become a Debian developer - or maintainer, this is a good starting point. - </dd> - </dl> - - - </div> - - </div> - -</div> - - -<h2><a id="workinprogress">Work in Progress: Links for active Debian developers and maintainers</a></h2> - -<aside class="light"> - <span class="fas fa-wrench fa-5x"></span> -</aside> - -<dl> - <dt><a href="testing">Debian ‘Testing’</a></dt> - <dd> - Automatically generated from the ‘unstable’ distribution: - this is where you need to get your packages in order for them to be - considered for the next Debian release. - </dd> - - <dt><a href="https://bugs.debian.org/release-critical/">Release Critical Bugs</a></dt> - <dd> - A list of bugs which may cause a package to be removed from the - ‘testing’ distribution or may cause a delay for the - next release. Bug reports with a severity higher than or equal to - ‘serious’ qualify for the list, so please make sure to - fix those bugs against your packages as soon as you can. - </dd> - - <dt><a href="$(HOME)/Bugs/">Debian Bug Tracking System (BTS)</a></dt> - <dd> - For reporting, discussing, and fixing bugs. The BTS is useful - for both users and developers. - </dd> - - <dt>Information about Debian Packages</dt> - <dd> - The <a href="https://qa.debian.org/developer.php">package - information</a> and <a href="https://tracker.debian.org/">package - tracker</a> web pages provide collections of valuable - information to maintainers. Developers who want to keep - track of other packages, can subscribe (through email) - to a service which sends out copies of BTS mails and - notifications for uploads and installations. Please see the <a - href="$(DOC)/manuals/developers-reference/resources.html#pkg-tracker">package - tracker manual</a> for further information. - </dd> - - <dt><a href="wnpp/">Packages that need Help</a></dt> - <dd> - Work-Needing and Prospective Packages, WNPP for short, is a list - of Debian packages in need of new maintainers and packages that - have yet to be included in Debian. - </dd> - - <dt><a href="$(DOC)/manuals/developers-reference/resources.html#incoming-system">Incoming System</a></dt> - <dd> - Internal archive servers: this is where new packages are uploaded - to. Accepted packages are almost immediately available via a web - browser and propagated to <a href="$(HOME)/mirror/">mirrors</a> - four times a day. - <br /> - <strong>Note:</strong> Due to the nature of ‘incoming’, - we do not recommend mirroring it. - </dd> - - <dt><a href="https://lintian.debian.org/">Lintian Reports</a></dt> - <dd> - <a href="https://packages.debian.org/unstable/devel/lintian">Lintian</a> - is a program which checks whether a package conforms to the - policy. Developers should use it before every upload. - </dd> - - <dt><a href="$(DOC)/manuals/developers-reference/resources.html#experimental">Debian ‘Experimental’</a></dt> - <dd> - The ‘experimental’ distribution is used as a temporary - staging area for highly experimental software. Please install the - <a href="https://packages.debian.org/experimental/">experimental - packages</a> only if you already know how to use - ‘unstable’. - </dd> - - <dt><a href="https://wiki.debian.org/HelpDebian">Debian Wiki</a></dt> - <dd> - The Debian Wiki with advice for developers and other contributors. - </dd> -</dl> - -<h2><a id="projects">Projects: Internal Groups and Projects</a></h2> - -<aside class="light"> - <span class="fas fa-folder-open fa-5x"></span> -</aside> - -<ul> -<li><a href="website/">Debian Web Pages</a></li> -<li><a href="https://ftp-master.debian.org/">Debian Archive</a></li> -<li><a href="$(DOC)/ddp">Debian Documentation Project (DDP)</a></li> -<li><a href="https://qa.debian.org/">Debian Quality Assurance (QA) Team</a></li> -<li><a href="$(HOME)/CD/">CD/DVD Images</a></li> -<li><a href="https://wiki.debian.org/Keysigning">Keysigning</a></li> -<li><a href="https://wiki.debian.org/Keysigning/Coordination">Keysigning Coordination</a></li> -<li><a href="https://wiki.debian.org/DebianIPv6">Debian IPv6 Project</a></li> -<li><a href="buildd/">Autobuilder Network</a> and their <a href="https://buildd.debian.org/">Build Logs</a></li> -<li><a href="$(HOME)/international/l10n/ddtp">Debian Description Translation Project (DDTP)</a></li> -<li><a href="debian-installer/">The Debian Installer</a></li> -<li><a href="debian-live/">Debian Live</a></li> -<li><a href="$(HOME)/women/">Debian Women</a></li> -<li><a href="$(HOME)/blends/">Debian Pure Blends</a></li> - -</ul> - - -<h2><a id="miscellaneous">Miscellaneous Links</a></h2> - -<aside class="light"> - <span class="fas fa-bookmark fa-5x"></span> -</aside> - -<ul> -<li><a href="https://peertube.debian.social/home">Recordings</a> of our Conference Talks on PeerTube or using a - <a href="https://debconf-video-team.pages.debian.net/videoplayer/">different user interface</a></li> -<li><a href="passwordlessssh">Setting up SSH</a> so it doesn't ask you for a password</li> -<li>How to <a href="$(HOME)/MailingLists/HOWTO_start_list">request a new Mailing List</a></li> -<li>Information on <a href="$(HOME)/mirror/">Mirroring Debian</a></li> -<li>The <a href="https://qa.debian.org/data/bts/graphs/all.png">Graph of all Bugs</a></li> -<li><a href="https://ftp-master.debian.org/new.html">New Packages</a> waiting to be included in Debian (NEW Queue)</li> -<li><a href="https://packages.debian.org/unstable/main/newpkg">New Debian Packages</a> from the last 7 Days</li> -<li><a href="https://ftp-master.debian.org/removals.txt">Packages removed from Debian</a></li> -</ul> diff --git a/greek/devel/join/newmaint.wml b/greek/devel/join/newmaint.wml deleted file mode 100644 index c7e559c324b..00000000000 --- a/greek/devel/join/newmaint.wml +++ /dev/null @@ -1,156 +0,0 @@ -#use wml::debian::template title="Debian New Members Corner" BARETITLE="true" -#use wml::debian::translation-check translation="e75c4ef4f01457261f11a81e80de9862be35be30" maintainer="galaxico" - -<p>The Debian New Member process is the process of becoming an official -Debian Developer (DD). These webpages are the place where prospective Debian -Developers can find all the details on applying to become a DD, the -different steps of the process, and how to track the process of their ongoing -application.</p> - -<p>The first important point to make is that you do <em>not</em> need -to be an official Debian Developer in order to help improving -Debian. In fact, you should already have a track record of earlier -contributions to Debian before you apply for the New Member process.</p> - -<p><a name="non-maintainer-contributions"></a>Debian is an open community and -welcomes everyone who wants to use or help improve our distribution. As a -non-developer you can:</p> - -<ul> - <li>maintain packages through a <a href="#Sponsor">sponsor</a></li> - <li>create and/or review translations</li> - <li>create or improve documentation</li> - <li><a href="../website">help maintain the website</a></li> - <li>help with handling bugs (by providing patches, filing good bugs, - confirming the existence of the bug, finding ways to reproduce the - problem, ...)</li> - <li>be an active member of a packaging team (e.g. debian-qt-kde or debian-gnome)</li> - <li>be an active member of a subproject (e.g. debian-installer or debian-desktop)</li> - <li>etc</li> -</ul> - -<p>The <a href="$(DOC)/developers-reference/new-maintainer.html">Debian -Developer's Reference</a> contains several concrete suggestions on how -to do several of these tasks (in particular, how to find willing -sponsors).</p> - -<p>The Debian New Member process is the process of becoming an official -Debian Developer (DD). This is the traditional full membership role in -Debian. A DD can participate in Debian elections. Uploading DDs can upload -any package to the archive. Before applying as an uploading DD you should -have a track record of maintaining packages for at least six months. For -example uploading packages as a <a -href="https://wiki.debian.org/DebianMaintainer">Debian Maintainer -(DM)</a>, working inside a team or maintaining packages uploaded by -sponsors. Non-uploading DDs have the same permissions in the archive as -Debian Maintainers. Before -applying as non-uploading DD, you should have a visible and significant -track record of work inside the project.</p> - -<p>It is important to understand that the New Member process is part of -Debian's Quality Assurance efforts. It is hard to find developers who can spend -enough time on their Debian tasks, so we find it important to checking that -applicants are able to sustain their work, and do it well. Therefore we require -that prospective members have been actively involved in Debian for some time -already.</p> - -<p><a name="developer-priveleges"></a>Every Debian Developer:</p> -<ul> - <li>is member of the Debian project;</li> - <li>is allowed to vote about issues regarding the whole project;</li> - <li>can log in on most systems that keep Debian running;</li> - <li>has upload permissions for <em>all</em> packages - (except non-uploading Developers, who have the upload rights of a DM);</li> - <li>has access to the debian-private mailing list.</li> -</ul> - -<p>In other words, becoming a Debian Developer grants you several important -privileges regarding the project's infrastructure. Obviously this requires a -great deal of trust in and commitment by the applicant.</p> - -<p>Consequently the whole NM process is very strict and thorough. This is not -meant to discourage people interested in becoming a registered developer, but -it does explain why the New Member process takes so much time.</p> - -<p>Please read the <a href="#Glossary">glossary definitions</a> before -reading the rest of the pages.</p> - -<p>The following pages will be of interest to Applicants:</p> - -<ul> - <li><a href="nm-checklist">Checklist - required steps for Applicants</a> - <ul> - <li><a href="nm-step1">Step 1: Application</a></li> - <li><a href="nm-step2">Step 2: Identification</a></li> - <li><a href="nm-step3">Step 3: Philosophy and Procedures</a></li> - <li><a href="nm-step4">Step 4: Tasks and Skills</a></li> - <li><a href="nm-step5">Step 5: Recommendation</a></li> - <li><a href="nm-step6">Step 6: Front Desk Check</a></li> - <li><a href="nm-step7">Step 7: Debian Account Manager check and account creation</a></li> - </ul></li> - <li><a href="https://nm.debian.org/public/newnm">Entry Form</a></li> -</ul> - -<p>If you are a Debian Developer, and are interested in participating in the -New Member process, please visit these pages:</p> -<ul> - <li><a href="nm-amchecklist">Checklist for Application Managers</a></li> - <li><a href="nm-advocate">Advocating a prospective member</a></li> - <li><a href="nm-amhowto">Mini-HOWTO for Application Managers</a></li> - <li><a href="$(HOME)/events/keysigning">Mini-HOWTO for Keysigning</a></li> -</ul> - -<p>Miscellaneous:</p> -<ul> - <li><a href="https://nm.debian.org/">Status database for the New Member - process</a></li> - <li><a href="https://nm.debian.org/process/">List of current applicants</a></li> - <li><a href="https://nm.debian.org/public/managers">List of current application - managers</a></li> -</ul> - -<define-tag email><<a href="mailto:%0">%0</a>></define-tag> - -<h2><a name="Glossary">Glossary Definitions</a></h2> -<dl> - <dt><a name="Advocate">Advocate</a>:</dt> - <dd>A <a href="#Member">Debian Member</a> that advocates an application. They - should know the <a href="#Applicant">Applicant</a> fairly well and should be - able to give an overview of the Applicant's work, interests and plans. - Advocates are often the <a href="#Sponsor">Sponsors</a> of an Applicant. - </dd> - - <dt><a name="Applicant">Applicant</a>, New Member, historically also New Maintainer (NM):</dt> - <dd>A person requesting Debian membership as Debian Developer.</dd> - - <dt><a name="AppMan">Application Manager</a> (AM):</dt> - <dd>A <a href="#Member">Debian Member</a> who is assigned to an <a - href="#Applicant">Applicant</a> to collect the information needed by - the <a href="#DAM">Debian Account Managers</a> to decide about an - application. One Application Manager can be assigned to more than - one Applicant.</dd> - - <dt><a name="DAM">Debian Account Manager</a> (DAM): <email da-manager@debian.org></dt> - <dd>A <a href="#Member">Debian Member</a> that was delegated to manage - the Debian Account creation and removal by the Debian Project Leader (DPL). - The DAMs have the final decision over an application.</dd> - - <dt><a name="FrontDesk">Front Desk</a>: <email nm@debian.org></dt> - <dd>The Front Desk members do the infrastructural work for the NM process like - receiving the initial applications, advocation messages and final application - reports, and assigning AMs to NMs. They are the point of contact if problems - with the application arise.</dd> - - <dt><a name="Member">Member, Developer</a>:</dt> - <dd>A Debian member, who has gone - through the New Member process and had their application accepted.</dd> - - <dt><a name="Sponsor">Sponsor</a>:</dt> - <dd>A <a href="#Member">Debian Member</a> who acts as the mentor of - an Applicant: They check packages provided by the Applicant and help - to find problems and to improve the packaging. When the sponsor is - satisfied with the package, they upload it on behalf of the Applicant - to the Debian archive. The Applicant is recorded as the maintainer of - such a package, despite the fact Applicants do not upload - packages themselves.</dd> -</dl> diff --git a/greek/devel/join/nm-advocate.wml b/greek/devel/join/nm-advocate.wml deleted file mode 100644 index a3df5c2bba2..00000000000 --- a/greek/devel/join/nm-advocate.wml +++ /dev/null @@ -1,58 +0,0 @@ -#use wml::debian::template title="Advocating a prospective member" -#use wml::debian::translation-check translation="a0723d79bbfc5ed2266ada5ffd402b2d3ab47405" maintainer="galaxico" - -<p>Before advocating a prospective member, you should check that they -satisfy all things listed on the <a href="./nm-checklist">NM checklist</a>. -</p> - -<p>You should <em>only</em> advocate someone if you think that they are -ready to be a project member. This means that you should have known them for -some time and can judge their work. It is important that prospective -members have been working in the project for some time. Some ways -prospective members might be contributing include:</p> - -<ul> -<li>maintaining a package (or several),</li> -<li>helping users,</li> -<li>publicity work,</li> -<li>translations,</li> -<li>organizing work for debconf,</li> -<li>sending patches,</li> -<li>contributing bug reports,</li> -<li>... and much more!</li> -</ul> - -<p>These ways of helping are not mutually exclusive, of course! Many -prospective members will have done work in several areas of the -project, and not everyone must be a packager. Remember, <a -href="https://www.debian.org/vote/2010/vote_002">Debian welcomes -non-packaging contributors as project members</a>. For a wider -overview of a given contributor, you may be interested in <a -href="http://ddportfolio.debian.net/">tools which aggregate some -publicly-visible parts of the project</a>. Your personal knowledge of -the applicant is also important here. -</p> - -<p>The prospective member should be familiar with Debian's special -ways of doing things and should have already contributed actively and -effectively to the project. Most importantly, they should be -committed to the ideals and structure of the Debian project. Ask -yourself if you want to see them in Debian – if you think they -should be a Debian Developer then go ahead and encourage them to apply. -</p> - -<p>Next carry out the following steps: Agree with the prospective member -to recommend them and let them <a href="https://nm.debian.org/public/newnm">sign -up</a>. After that, you have to click on their name in the <a -href="https://nm.debian.org/process/">listing of Applicants</a> -and go the <q>Advocate this application</q> page. Enter your Debian login -and press the <q>Advocate</q> button. You then will receive an e-mail with an -auth key which you have to return PGP/GPG signed. After this, the -Applicant is added to the queue for an Application Manager with whom -they will go through all steps of the New Member checks. -</p> - -<p> -See also the <a href="https://wiki.debian.org/FrontDesk/AdvocacyTips">Advocacy Tips</a> -wiki page. -</p> diff --git a/greek/devel/join/nm-amchecklist.wml b/greek/devel/join/nm-amchecklist.wml deleted file mode 100644 index 9dd3ab6ae95..00000000000 --- a/greek/devel/join/nm-amchecklist.wml +++ /dev/null @@ -1,148 +0,0 @@ -#use wml::debian::template title="Checklist for Application Managers" -#use wml::debian::translation-check translation="5011f532637dc7820b79b151eecfda4ab65aa22f" maintainer="galaxico" - -<p> -<b>Note:</b> The <a href="https://wiki.debian.org/FrontDesk/AMTutorial">AM -Tutorial</a> wiki page is more up to date than this page. -</p> - -<p>This checklist only covers the most important areas of the NM checks. -Depending on the <a href="./newmaint#Applicant">Applicant's</a> -background and plans in the project, an <a href="./newmaint#AppMan">\ -Application Manager</a> may choose to ignore some of the things -listed here or to add others.</p> - -<p>Also see the <a href="nm-amhowto">Mini-HOWTO for Application -Managers</a>.</p> - -<h3><a name="identification">Identification Check</a></h3> -<p>The <a href="./newmaint#Applicant">Applicant</a> has to have - an OpenPGP public key signed by at least one <a href="./newmaint#Member">\ - Debian member</a>. If possible, at least one other signature - from a well-connected OpenPGP key is also required. Always - use <tt>gpg --check-sigs</tt>, not <tt>gpg --list-sigs</tt> to verify - an Applicant's identity.</p> - -<p>The OpenPGP key that will go to the Debian Keyring needs to be - a version 4 key. To check this, get the fingerprint of the key - and check if it's either 32 or 40 hexadecimal digits long. Version 3 - keys have only 32 digits, version 4 have 40 digits. This key - doesn't have to be the same as the one that is used to verify the - Applicant's identity.</p> - -<p>Applicants <em>must</em> have an encryption key. Check this by - running <tt>gpg --list-keys <var><KeyID></var></tt>. -If the output doesn't contain a line with either -<tt><var><Number></var>E/<var><KeyID></var></tt> or -<tt><var><Number></var>g/<var><KeyID></var></tt>, the -Applicant needs to add an encryption subkey.</p> - -<p>If the <a href="./newmaint#Applicant">Applicant</a> can't - provide a signed key, a government-issued photo ID can be used for - identification. Please contact the <a href="./newmaint#FrontDesk">\ - Front Desk</a> in such cases.</p> - -<p>Additional verification options can be used if there is some - doubt about the identity of the Applicant:</p> - -<ul> - <li>If the Applicant is a student, someone at their university can - confirm their identify. This person should also be listed on the - webpages of the university staff.</li> - - <li>If the Applicant works in a bigger company, their employer should - be able to confirm their identity.</li> - - <li>There are websites that can do reverse lookups for telephone - numbers, though this normally doesn't work for mobile phones. - The number the Applicant provides should either resolve to their - own name or the person answering the phone should be able to - confirm the Applicant's identity.</li> -</ul> - -<h3><a name="pandp">Philosophy and Procedures</a></h3> -<p>There are no fixed rules for this part, but some areas should - always be covered (and it is recommended to discuss the - others):</p> -<ul> - <li>Applicants have to agree to uphold the <a - href="$(DOC)/debian-policy/">Debian Policy</a> and the <a - href="$(DEVEL)/dmup">Debian Machine Usage Policy (DMUP)</a>.</li> - - <li>Applicants need to agree to the <a href="$(HOME)/social_contract">\ - Social Contract</a> and must be able to explain how Debian - relates to the Free Software Community.</li> - - <li>Applicants must have a good understanding of the <a - href="$(HOME)/social_contract#guidelines">Debian Free Software - Guidelines</a>. They need to be able to decide if a license is free - or not and should have a strong opinion about Free Software.</li> - - <li>Applicants have to understand how the Debian Bug Tracking - System works, what information Debian keeps in there (pseudo-packages, - wnpp, ...) and how they can manipulate it.</li> - - <li>Applicants should know about Debian QA processes (orphaning, - removing, NMUing and QA uploads).</li> - - <li>Applicants should understand the Debian release process.</li> - - <li>Applicants should know Debian's l10n and i18n efforts and what - they can do to help them.</li> -</ul> - -<h3><a name="tands">Tasks and Skills</a></h3> -<p>What needs to be covered by the T&S checks depends on the - area the Applicant wishes to work in:</p> - -<ul> - <li>Applicants aiming to work as packager <em>must</em> have at least - one package in the archive. The package should have enough users - to provide a basis for documentation of the Applicant's packaging - skills and their way of dealing with users, bug submitters and bugs. - <br /> - Further questions should also cover some basic aspects of Debian - packaging (conffiles, menus, init scripts, sub-policies, porting, - complex dependencies).</li> - - <li>Applicants planning to write documentation must have already - provided examples of their work. They should also have a clear vision - on what kind of documents they want to work on in the future.</li> -</ul> - -<h3><a name="finalreport">Final Application Report to the Debian -Account Manager</a></h3> -<p>After all checks are finished and the AM is satisfied with the - Applicant's performance, a report should be submitted to the Debian - Account Manager and the New Member Front Desk. It should - document what was done to satisfy the different parts of the New - Member checks and also contain all information collected - about the Applicant.</p> - -<p>The email should be directed at <da-manager@debian.org> and - <nm@debian.org> and contain the following - things:</p> - -<ul> - <li>A short overview about the application, containing some basic - information about the Applicant.</li> - - <li>The account name the Applicant requested. It should be at least - 3 characters long.</li> - - <li>The email address to which all mail directed at - <var><account></var>@debian.org should be forwarded.</li> - - <li>The fingerprint of the Applicant's OpenPGP public key that should be incorporated - into the Debian Keyring.</li> - - <li>An gzipped mbox with logs of all discussion between the Application Manager - and the Applicant about the application.</li> -</ul> - -<p>This completes the Application Manager's responsibilities in the - application process. The New Member Front Desk and the Account - Manager will check and judge the application report.</p> - -<hr /> -<a href="newmaint">Back to the New Members Corner</a> diff --git a/greek/devel/join/nm-amhowto.wml b/greek/devel/join/nm-amhowto.wml deleted file mode 100644 index fab5a29343f..00000000000 --- a/greek/devel/join/nm-amhowto.wml +++ /dev/null @@ -1,120 +0,0 @@ -#use wml::debian::template title="Mini-HOWTO for Debian New Members Application Managers" -#use wml::debian::translation-check translation="c3a3b8986d2ffef95ef7bb8f7d99f36678ff0e8f" maintainer="galaxico" - -<p> -<b>Note:</b> The <a href="https://wiki.debian.org/FrontDesk/AMTutorial">AM -Tutorial</a> wiki page is more up to date than this page. -</p> - -<h2>Documentation and Infrastructure for Application Managers</h2> - -<p>The basic information needed by Application Manager is provided -here, in the <a href="newmaint">New Members Corner</a>. Start -to look around until you're familiar with the process and all -requirements for Applicants.</p> - -<p>There are three important mail addresses for Application Managers:</p> - -<dl> - <dt>The New Member mailing list: <a href="https://lists.debian.org/debian-newmaint"> - debian-newmaint@lists.debian.org</a></dt> - <dd>This mailing list covers all aspects of the New Member process - and is used by the New Member group (Front Desk, Application - Managers, Debian Account Manager) and others to discuss - administrative issues and the New Member process. - If you have any questions regarding the NM process, you can ask - for help there. Please note that the list is archived publicly, so - questions of a highly personal nature shouldn't be discussed there. - Instead, you can ask the Front Desk privately.</dd> - - <dt>New Member Front Desk: nm@debian.org</dt> - <dd>This is where the initial applications, advocation messages and final - application reports get sent. Any personal questions about individual - applications which are inappropriate for a public forum should be - directed here as well.</dd> - - <dt>Debian Account Managers (DAMs): da-manager@debian.org</dt> - <dd>Normally, this address is only important to submit the final - application report. The DAMs are responsible for creating new accounts - on the Debian machines and adding New Members' OpenPGP keys to - the keyring. They also get to make the final decision on each - application, as the official New Member delegates of the Debian - Project Leader.</dd> -</dl> - -<p>The coordination of the NM process happens on <url -"https://nm.debian.org/"/>, where a website provides an interface to a -database containing all important information about NM applications. -Applicants can use the site to track their application status and -Application Managers can use it to organize their work.</p> - -<p>As Application Manager, you can log in over a secure https connection, -but please note that the password used on nm.debian.org is <em>not</em> the -one used for your normal Debian account (unless you change them to -match, but that's your business). You can record what you have done -with an Applicant and how many applicants you want to process at the -same time.</p> - -<p>To put someone on hold, you need to go to the applicant's status -page after you logged in and mark the "No" radio button for "AM approves -and submits report". You should also put a line into the AM comment field -to document why you did this.</p> - -<p>The rest of the pages is fairly self-explanatory. Some statistics -about all Application Managers are available, you can see an unsorted -list of all Applicants and change your AM profile.</p> - -<h2>Notes about the NM checks</h2> - -<p>As the NM-oriented documentation already provides enough information -about the requirements of the checks, nothing of that will be repeated -here. If you're unsure how to manage an applicant, use the excellent -templates provided by Joerg Jaspert's <a -href="https://salsa.debian.org/nm-team/nm-templates">nm-templates</a> -project. Questions should be asked on debian-newmaint@l.d.o or sent -to the Front Desk.</p> - -<h3>Putting an application on hold</h3> - -<p>Applicants that are either not able or not willing to invest enough -time into the New Member checks to finish them in a reasonable time -span (∼ 6 to 9 months) should be put on hold. That's not a problem or an -assessment of the Applicant's skills, but a simple reaction to the lack -of time. Many people want to join Debian, so Applicants shouldn't block -AM spots.</p> - -<p>You should discuss the possibility of setting an application on hold -when you get the feeling that it isn't moving forward, either because -the Applicant doesn't answer or because their only answer is "Yeah, will -do it soon". Emphasize the fact that getting off hold when they have -more time is no problem.</p> - -<h3>Other important notes</h3> - -<ul> - <li>Applicants should provide a short biography which can be sent to - debian-project@lists.debian.org in the regular "New Members" - email. That's very useful to introduce new members to the project. - Please note that the Applicant <em>has</em> to agree to the - publishing of this biography.</li> - - <li>Get some background information about the Applicant and put it - into the report — use your favourite search engine, private mail - archives, the BTS and all other means that come to your mind. - Sometimes the application process is too short to get a proper - impression of the Applicant's personality, so try to find out what - they did in the past.</li> - - <li>Ask sponsors and other people who worked closely together with - the Applicant to provide short statements about them. As more and - more packages are team-maintained, you can almost always find someone - who's able to tell you more about an Applicant. Include these - statements in the report.</li> - - <li>When checking the performance of a packaging Applicant, you should - be aware that one tiny package in the archive is not enough to - satisfy the Skills part of the T&S checks. The package should - have had more than one upload, some users (check popcon) and some - (closed, if possible) bug reports. This is important to see how an - Applicant interacts with users.</li> -</ul> diff --git a/greek/devel/join/nm-checklist.wml b/greek/devel/join/nm-checklist.wml deleted file mode 100644 index a5be6fe1149..00000000000 --- a/greek/devel/join/nm-checklist.wml +++ /dev/null @@ -1,105 +0,0 @@ -#use wml::debian::template title="Applicant's Checklist" -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" -#use wml::debian::translation-check translation="517d7a4f999561b8f28e207214a40990fdc3da49" maintainer="galaxico" - -<p>The information on this page, while public, will primarily -be of interest to future Debian Developers.</p> - -<h3>0. Contributing</h3> - -Before you decide to apply, you should already be contributing to Debian by -providing packages, translations, documentation, or any other activity. Usually -you are already registered as a <a -href="https://wiki.debian.org/DebianMaintainer">Debian Maintainer</a>, and have -been uploading your packages for six months. - -<p>The current registration process of New Members is divided -into 4 parts:</p> - -<h3>1. Application and Advocation</h3> -<p>Normally, the process is started with an application through the -<a href="https://nm.debian.org/public/newnm">New Member Application -web interface</a>. -<br> -After this step, the Applicant is known to the system and the Debian -New Member Front Desk is the primary contact for questions -concerning the Application. The Front Desk manages or supervises -all other steps and will try to help with all upcoming issues. -</p> - -<p>After the application is submitted to the system, an official Debian -Developer who has worked with the Applicant advocates them. This is -done with a signed email, containing a short text about the Applicant. -Normally, this mail covers topics like the background of the Applicant, -what they have done for Debian and a few bits about future plans.</p> - -<p>Then the Front Desk has a look to what the Applicant has already done -in the project. For the NM process to be the most efficient, Applicants -should have already contributed significantly to Debian. This can be done -through packaging, documentation, Quality Assurance, ...</p> - -<p><a href="./nm-step1">More ...</a></p> - -<h3>2. AM checks</h3> -<p>As soon as an Application Manager is available, the Front Desk -assigns one to the Applicant. The Application Manager's task is to -collect the information needed as a foundation for the decision -of the Debian Account Manager. This is divided into 4 parts:</p> - -<h4>ID check</h4> -<p>To maintain the strong Web of Trust that connects all Debian -Developers, Applicants need to identify themselves by providing an -OpenPGP key that is signed by at least two official Developers. To -further ensure their identity, signatures by other people (who do not -need to be DDs, but should be well connected in the overall Web of -Trust) are strongly recommended.</p> - -<p><a href="./nm-step2">More ...</a></p> - -<h4>Philosophy and Procedures checks</h4> -<p>As Debian is known for its strong ethical and philosophical -background, Applicants have to explain their own view about the -topic of Free Software. Debian has also evolved quite complicated -standard procedures to handle the problems of working in a large -group, so Applicants need to show that they know them and are -able to apply them to concrete situations.</p> - -<p><a href="./nm-step3">More ...</a></p> - -<h4>Tasks and Skills checks</h4> -<p>To ensure the overall quality of the Debian distribution, -Applicants need to show that they know their tasks in the area -they plan to work on (either documentation and internationalisation -or package maintenance). -#We have more areas, I'm sure of that - but I can't remember them now: FIXME -They also have to show their skills by submitting examples of their -work and answering some questions about it.</p> - -<p><a href="./nm-step4">More ...</a></p> - -<h4>Recommendation</h4> -<p>If the Application Manager is satisfied with the performance -of the Applicant, an Application Report is prepared and submitted -to the Front Desk and Debian Account Managers.</p> - -<p><a href="./nm-step5">More ...</a></p> - -<h3>3. Front Desk check</h3> -<p>The Application Report is checked by a member of the Debian Front Desk -for formal problems. If these are grave, the report is rejected and -the Application Manager has to correct the issue. If there are only minor -errors, these are reported to the Applicant and Application Manager.</p> - -<p><a href="./nm-step6">More ...</a></p> - -<h3>4. Debian Account Manager check and Account creation</h3> -<p>At this last stage of the process, the Application Report is judged. -If needed, further checks are either done by the Account Manager or -an Application Manager is asked to carry out a recheck. Sometimes -a Phone Call is required to finish the application.</p> - -<p>If all possible problems are resolved, the Debian Account Managers -assign an account to the Applicant and add their OpenPGP key to the -Debian keyring.</p> - -<p><a href="./nm-step7">More ...</a></p> diff --git a/greek/devel/join/nm-step1.wml b/greek/devel/join/nm-step1.wml deleted file mode 100644 index 4a9398de0fd..00000000000 --- a/greek/devel/join/nm-step1.wml +++ /dev/null @@ -1,89 +0,0 @@ -#use wml::debian::template title="Step 1: Application" NOHEADER="true" -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" -#use wml::debian::translation-check translation="0f3581ea8ff22d12b1665c2fb885ea6ccfe11f1c" maintainer="galaxico" - -<p>The information on this page, while public, will primarily -be of interest to future Debian Developers.</p> - -<h2>Step 1: Application</h2> - -<p>Before applying, prospective Developers should check that they are -prepared for all parts of the checks. To make this as easy as possible, -the most important prerequisites are listed below:</p> - -<ul> - <li><h4>The Applicant needs to agree with Debian's Philosophy</h4> - <p>It is needed that Applicants have read the - <a href="$(HOME)/social_contract">Social Contract</a> and the - <a href="$(HOME)/social_contract#guidelines">Debian Free Software - Guidelines</a> and agree to abide by them in their Debian-related work. - </p> - </li> - - <li><h4>The Applicant's identity needs to be verified</h4> - <p>This is done by having at least two signatures on the Applicant's - OpenPGP key from Debian Developers. It is also strongly recommended to have - more signatures from people who are well connected in the web of trust. - </p> - - <p>If the Applicant's location makes it <em>impossible</em> to get a key - signed by another Debian Developer, a scanned photo of their drivers license - or passport signed with their GPG key can be accepted as an alternative - method of identification. - </p> - </li> - - <li><h4>The Applicant needs to be able to perform their duties as a - developer</h4> - <p>This means that the Applicant should have experience of packaging and - package maintenance or experience of documenting or translating, depending - on the area they want to work in. - </p> - - <p>It's recommended that Applicants get a <a href="newmaint#Sponsor">sponsor</a> - to help them achieve this.</p> - </li> - - <li><h4>The Applicant needs to have read the developer documentation</h4> - <p>Later on in the process, the <a href="newmaint#AppMan">Application - Manager</a> will test the Applicant's knowledge of concepts described in - <a href="$(DOC)/debian-policy/">Debian Policy</a>, - <a href="$(DOC)/developers-reference/">Developers' Reference</a>, - <a href="$(DOC)/maint-guide/">New Maintainers' Guide</a> etc. - </p> - </li> - - <li><h4>The Applicant needs to have enough free time</h4> - <p>Finishing the New Member checks and being a Debian Developer - requires to invest time on a regular basis. Maintaining packages - in the main archive is a big commitment and can require quite - a lot of time.</p> - </li> - - <li><h4>The Applicant needs to have an <a href="newmaint#Advocate">\ - Advocate</a></h4> - <p>In order to persuade a developer to be your advocate, an Applicant should - get involved in Debian development – help tackle open bugs - against existing packages, adopt an orphaned package, work on the - installer, package useful new software, write or update documentation - etc. - </p> - </li> -</ul> - -<p>Once the Applicant has satisfied the above standards, they -can submit their <a href="https://nm.debian.org/public/newnm">New Member -Application</a>.</p> - -<p>After receiving the application, the <a href="./newmaint#FrontDesk"> -Front Desk</a> manages the application. As soon as someone is available -(this can take some weeks), it will assign them as the <a -href="./newmaint#AppMan">Application Manager</a> (AM) for the <a -href="./newmaint#Applicant">Applicant</a> (i.e. you).</p> - -<p>All further communication should happen between the Applicant and their -Application Manager, but if problems arise, the Front Desk is your primary -contact point.</p> - -<hr> -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" diff --git a/greek/devel/join/nm-step2.wml b/greek/devel/join/nm-step2.wml deleted file mode 100644 index 33e068f5343..00000000000 --- a/greek/devel/join/nm-step2.wml +++ /dev/null @@ -1,97 +0,0 @@ -#use wml::debian::template title="Step 2: Identification" NOHEADER="true" -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" -#use wml::debian::translation-check translation="b59849318da01faabdbc1d5bb5e05f99c4f7a61a" maintainer="galaxico" - -<p>The information on this page, while public, will primarily -be of interest to future Debian developers.</p> - - -<h2>Step 2: Identification</h2> - -<h3>Why OpenPGP?</h3> - -<p>Debian makes extensive use of OpenPGP because <a -href="newmaint#Member">Debian members</a> are located all over the world -(see the <a href="$(DEVEL)/developers.loc">developer locations</a>) and rarely -meet each other in person. This means trust cannot be built up by -personal contact and other means are necessary. All Debian developers -are identified by their <a href="http://www.gnupg.org/">OpenPGP</a> -key. These keys make it possible to authenticate messages and -other data by signing it. For more information on OpenPGP keys -see the README file in the <code>debian-keyring</code> package.</p> - -<h3>Providing a key</h3> - -<p>Each <a href="newmaint#Applicant">Applicant</a> must provide an -OpenPGP version 4 public key with encryption capabilities. The -preferred way to do this is to export it to one of the public key -servers, such as <tt>subkeys.pgp.net</tt>. -Public keys can be exported using:</p> -<pre> -gpg --send-key --keyserver <server address> <yourkeyid> -</pre> - -<p>If your key has no encryption capability, you can simply add -an encryption subkey.</p> - -<p>See <a href="https://keyring.debian.org/">keyring.debian.org</a> -for more information on key formats and properties.</p> - - -<h3>Verification</h3> - -<p>Since anyone can upload a public key to the servers it needs -to be verified that the key belongs to the Applicant.</p> - -<p>To accomplish this the public key itself must be signed by two other -<a href="newmaint#Member">Debian members</a>. Therefore the -Applicant must meet this Debian member in person and must -identify himself (by providing a passport, a driver's license -or some other ID).</p> - - -<h4><a name="key_signature">How to get your OpenPGP key signed</a></h4> - -<p>There are several ways to find a Debian member for a key -exchange. You should try them in the order listed below:</p> - -<ol> - -<li>Announcements of key signing parties are usually posted on the -<code>debian-devel</code> mailing list, so check there first.</li> - -<li><p>You can look for developers in specific areas through the <a -href="https://wiki.debian.org/Keysigning">key signing coordination page</a>:</p> - -<ul> - <li>First you should check the list of key signing offers for a Debian - member near you.</li> - <li>If you cannot find a Debian member among the key signing offers, - you can register your key signing request.</li> -</ul> -</li> - -<li>If no one has reacted to your request for several weeks, send an -e-mail to <email debian-private@lists.debian.org> telling them exactly -where you live (plus naming some big cities close to you), -then they can check in the developer database for developers who are -near you.</li> - -</ol> - -<p>Once you find someone to sign your key, you should follow the steps -in the <a href="$(HOME)/events/keysigning">Keysigning Mini-HOWTO</a>.</p> - -<p>It is recommended that you also sign the Debian Developer's -key. This is not necessary for your ID check but it strengthens the -web of trust.</p> - - -<h4>When you can't get your key signed</h4> - -<p>If all of the steps above fail, please contact the -<a href="newmaint#FrontDesk">Front Desk</a> and ask for help. They may -offer you an alternate way of identification.</p> - -<hr> -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" diff --git a/greek/devel/join/nm-step3.wml b/greek/devel/join/nm-step3.wml deleted file mode 100644 index 71e913cc044..00000000000 --- a/greek/devel/join/nm-step3.wml +++ /dev/null @@ -1,167 +0,0 @@ -#use wml::debian::template title="Step 3: Philosophy and Procedures" NOHEADER="true" -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" -#use wml::debian::translation-check translation="517d7a4f999561b8f28e207214a40990fdc3da49" maintainer="galaxico" - -<p>The information on this page, while public, will primarily -be of interest to future Debian Developers.</p> - -<h2>Step 3: Philosophy and Procedures</h2> - -<h3>Philosophy</h3> -<p> -The <a href="./newmaint#Applicant">Applicant</a> is expected to fit -into the Debian community, which is built around the philosophy of -Free Software. What Debian understands as "free" and how this is -applied is explained in the <a href="$(HOME)/social_contract">Social -Contract</a> and the <a href="$(HOME)/social_contract#guidelines">Debian -Free Software Guidelines</a>. -<br /> -Prospective Developers need to understand these documents well enough to -express the ideas and ideals described there in their own words. Just -exactly how this understanding is accomplished and communicated is left -up to the Applicant and their manager to determine. The following methods -are only intended as a suggestion, not as a requirement, but they are -examples of ways to complete this step of the process. Several -opportunities will be provided for the Applicant to show understanding in -these areas. -</p> - -<p>Note: Though we require Applicants to agree with the Debian philosophy, -this is limited to work done for Debian. We understand that people need -to earn their living and are sometimes required to work on non-free -projects for their employer or customer.</p> - -<p>Debian makes no attempt to control what the Applicant thinks about these -subjects, but it is important to the stability of such a large and amorphous -project that all participants work within the same set of basic principles -and beliefs.</p> - -<p>The <a href="./newmaint#AppMan">Application Manager</a> (AM) will -decide when the criteria for each step have been satisfied. The following -guidelines only try to provide useful examples. In most cases, a mix -of all of them will be used. -<br> -The AM and the <a href="./newmaint#Applicant">Applicant</a> may decide -on other tasks than the ones specified here. Those tasks must be -documented clearly in the final report to the <a href="./newmaint#DAM">\ -Debian Account Manager</a>.</p> - -<dl> - <dt>1. The <a href="$(HOME)/social_contract">Social Contract</a></dt> - <dd><p> - The Social Contract declares Debian's goals and aspirations. It - also tries to express our self-imposed responsibilities to the rest - of the community. - <br /> - A proper understanding of the priorities we give to these various - responsibilities and agreement with them is essential for any - Applicant. - </p> - - <p>The understanding can be documented in various ways:</p> - - <ul> - <li>A discussion with the AM about the various terms in the Social - Contract, expressing how they relate to each other and Debian's - organization.</li> - - <li>A discussion about the Applicant's personal goals for Debian, - how they fit in with the Social Contract can in some cases - be enough.</li> - - <li>The Applicant can put the Social Contract in their own words, - explaining some of the more complex parts and how Debian - strives to comply to them.<br /> - Note: This is the usually chosen way. - </li> - </ul> - <br> - </dd> - - <dt>2. The <a href="$(HOME)/social_contract#guidelines">Debian Free - Software Guidelines</a></dt> - <dd> - <p>These principles act as guidelines for determining the freedom - delivered by a particular license.</p> - - <p>Although most Applicants aren't lawyers, every one should be - able to express and use the understanding of the basic principles - set forth in these guidelines.</p> - - <p>The understanding can be documented in various ways:</p> - - <ul> - <li>The Applicant discusses several licenses and tries to show - if they're free or not. In this process, the AM can point out - special cases and ask further questions regarding the DFSG.<br> - Note: This is the usually chosen way. - </li> - - <li>The Applicant compares the Debian Free Software Guidelines -#FIXME: "statements" is so wrong, but I already used guidelines... - to other statements about Free Software and points out - similarities and differences. - </li> - </ul> - </dd> -</dl> - -<p>Whatever method is used, the Applicant must agree with these -principles, as well as show an understanding of their meaning and -content.</p> - -<p> -Failure to agree with these terms will terminate the application process. -</p> - -<h3>Procedures</h3> - -<p>The standard procedures and policies that have evolved in the creation -of the Debian system are very important to manage the distributed work -of volunteers. They ensure the overall quality of Debian and often help -to prevent problems between Developers by providing a set of guidelines -for the interaction in special cases.</p> - -<p>How the <a href="./newmaint#Applicant">Applicant</a> has to show -their understanding is up to the <a href="./newmaint#AppMan">Application -Manager</a>, but there are some essentials that should always be covered. -The following list documents what is a must for the Procedures checks:</p> - -<ul> - <li><h4>Working with the Bug Tracking System</h4> - Debian uses the <a href="https://bugs.debian.org/">Bug Tracking System</a> - (BTS) not only to keep track of bugs in packages, but also to gather - requests about the infrastructure and manage the work-needing and - prospective packages. - <br /> - Prospective Developers need to be able to control the BTS and explain - how it can be used to represent all available data about problems. - </li> - - <li><h4>The Debian release process</h4> - Debian's release process is the base for its stability and security, - so prospective Developers need to understand how it works, why it - is structured as it is and what exceptions are possible. - </li> - - <li><h4>Debian's internationalisation and localisation efforts</h4> - Considering that only a small part of the world speaks English - natively, Developers and Translators invest a significant amount - of time to make Debian useable for everybody. There are a lot of - specific tools and rules and prospective Developers should be aware - of them. - </li> -</ul> - -<p>There are of course many other topics that can be covered by -the New Member checks, but the AM should only choose those -that are relevant for the area the Applicants wants to work in. -The most important quality is that prospective Developers know -where to look for information concerning them.</p> - -<p><a href="./newmaint#Applicant">Applicants</a> should also read -<a href="$(DEVEL)/dmup">the Debian Machine Usage Policy (DMUP)</a> -and agree to abide by it.</p> - -<hr /> -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" diff --git a/greek/devel/join/nm-step4.wml b/greek/devel/join/nm-step4.wml deleted file mode 100644 index 81b412eb537..00000000000 --- a/greek/devel/join/nm-step4.wml +++ /dev/null @@ -1,56 +0,0 @@ -#use wml::debian::template title="Step 4: Tasks and Skills" NOHEADER="true" -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" -#use wml::debian::translation-check translation="517d7a4f999561b8f28e207214a40990fdc3da49" maintainer="galaxico" - -<p>The information on this page, while public, will primarily be of -interest to future Debian Developers.</p> - -<h2>Step 4: Tasks and Skills</h2> - -<p>Most of the current members of the <a href="./newmaint#DebianProject"> -Debian Project</a> maintain one or more packages for the distribution. -However there are many other jobs that need to be done that do not -involve package management.</p> - -<p>The <a href="./newmaint#AppMan">Application Manager</a> will -work out with the <a href="./newmaint#Applicant">Applicant</a> -which tasks the Applicant volunteers to perform. After that, the -Applicant will need to demonstrate their skills in this area.</p> - -<p>The following tasks are obvious examples of the various jobs available -to the Applicant, but they don't necessarily include everything an -Applicant may find interesting and productive for the group. Additional -tasks may be defined by the AM and the Applicant.</p> - -<p>Some example tasks are:</p> - -<ul> - <li><h4>Package Management</h4> - By maintaining a package, a prospective Developer can show their - understanding of the <a href="$(DOC)/debian-policy/">Debian Policy</a> - and how they work with Debian users and bug submitters. - </li> - - <li><h4>Documentation</h4> - The Applicant can demonstrate their skills in this area by writing - man pages for executables that don't have one, by updating an outdated - document and by creating new documentation that is required by - users, but still missing from the distribution. - </li> - - <li><h4>Debugging, Testing and Patching</h4> - The Applicant can show skills in this area either by working on - fixing bugs with the QA team, or by testing installation process or - individual packages working with the testing team. The Applicant - can fix bugs in existing Debian packages or file bug reports in - the Debian BTS describing problems and enclosing patches. - </li> -</ul> - -<p>Alternative demonstration tasks can be worked out between the -Applicant and the Application Manager. Such alternative tasks need to -be coordinated with the <a href="./newmaint#FrontDesk">Front Desk</a> -and the <a href="./newmaint#DAM">Debian Account Manager</a>.</p> - -<hr> -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" diff --git a/greek/devel/join/nm-step5.wml b/greek/devel/join/nm-step5.wml deleted file mode 100644 index fcb0912a163..00000000000 --- a/greek/devel/join/nm-step5.wml +++ /dev/null @@ -1,30 +0,0 @@ -#use wml::debian::template title="Step 5: Recommendation" NOHEADER="true" -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" -#use wml::debian::translation-check translation="7606615ccc824d084b77b8389bc4b0de77974b15" maintainer="galaxico" - -<p>The information on this page, while public, will primarily be of -interest to future Debian Developers.</p> - -<h2>Step 5: Recommendation</h2> - -<p>When the <a href="./newmaint#Applicant">Applicant</a> has completed -the tasks and skills tests, expressed an understanding of the <a -href="$(HOME)/social_contract">Social Contract</a>, the -<a href="$(HOME)/social_contract#guidelines">Debian Free Software -Guidelines</a> and Debian Policies and Procedures and been properly -identified, it is time for the <a href="./newmaint#AppMan">Application -Manager</a> to make <a href="./nm-amchecklist#finalreport">a final -report</a> to the <a href="./newmaint#FrontDesk">Front Desk</a> and -the <a href="./newmaint#DAM">Debian Account Manager</a>.</p> - -<p>This report includes statements from the <a href="./newmaint#Advocate"> -Advocate</a> and other people who have worked with the Applicant, -the completed identification information, all discussions between the -Application Manager and the Applicant and details about the Skill checks, -as well a comment from the Application Manager.</p> - -<p>The <a href="./newmaint#AppMan">Application Manager</a> will include a -recommendation to either accept or reject the Applicant.</p> - -<hr> -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" diff --git a/greek/devel/join/nm-step6.wml b/greek/devel/join/nm-step6.wml deleted file mode 100644 index 29def819121..00000000000 --- a/greek/devel/join/nm-step6.wml +++ /dev/null @@ -1,24 +0,0 @@ -#use wml::debian::template title="Step 6: Front Desk Check" NOHEADER="true" -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" -#use wml::debian::translation-check translation="7606615ccc824d084b77b8389bc4b0de77974b15" maintainer="galaxico" - -<p>The information on this page, while public, will primarily be of -interest to future Debian Developers.</p> - -<h2>Step 6: Front Desk Check</h2> - -<p>After the <a href="./newmaint#AppMan">Application Manager</a> has -prepared the final report about the <a href="./newmaint#Applicant"> -Applicant</a>, the <a href="./newmaint#FrontDesk">Front Desk</a> -checks the report. If it covers all needed areas and documents all -parts of the NM checks, it is approved. Little problems and errors -are pointed out to the <a href="./newmaint#AppMan">Application -Manager</a> and <a href="./newmaint#Applicant">Applicant</a>.</p> - -<p>If the report is incomplete, the <a href="./newmaint#FrontDesk">Front -Desk</a> either decides to send it back to <a href="./newmaint#AppMan"> -Application Manager</a> to complete it or asks another <a -href="./newmaint#AppMan">Application Manager</a> to finish it.</p> - -<hr> -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" diff --git a/greek/devel/join/nm-step7.wml b/greek/devel/join/nm-step7.wml deleted file mode 100644 index 52e303b8945..00000000000 --- a/greek/devel/join/nm-step7.wml +++ /dev/null @@ -1,35 +0,0 @@ -#use wml::debian::template title="Step 7: Debian Account Manager check and account creation" NOHEADER="true" -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" -#use wml::debian::translation-check translation="7606615ccc824d084b77b8389bc4b0de77974b15" maintainer="galaxico" - -<p>The information on this page, while public, will primarily be of -interest to future Debian Developers.</p> - -<h2>Step 7: Debian Account Manager check and account creation</h2> - -<p>The <a href="./newmaint#DAM">Debian Account Manager</a> has to make -the final decision about the account creation. If any major problems -in the application are found, it is either directly rejected or given -back to the <a href="./newmaint#FrontDesk">Front Desk</a>, which decides -how to complete the application.</p> - -<p>There are some problems that always lead to a rejection:</p> -<ul> - <li>Failure to provide adequate identification.</li> - <li>Failure to agree to our principles and procedures.</li> - <li>Failure to complete the tasks the Applicant agreed to do with - their Application Manager.</li> -</ul> - -<p>When the <a href="./newmaint#DAM">Debian Account Managers</a> are -satisfied with the complete application, they ask the Debian Keyring maintainers -to add the Applicant's key, and the Debian System Administrators to create the -necessary accounts for the Applicant and subscribe the Applicant to -the debian-private mailing list.</p> - -<p>Once all the final details of membership have been completed by the -<a href="./newmaint#DAM">Debian Account Managers</a>, the Applicant, -their AM and the debian-project mailing list will be informed.</p> - -<hr> -#include "$(ENGLISHDIR)/devel/join/nm-steps.inc" diff --git a/greek/devel/leader.wml b/greek/devel/leader.wml deleted file mode 100644 index 46c68bf7b10..00000000000 --- a/greek/devel/leader.wml +++ /dev/null @@ -1,74 +0,0 @@ -#use wml::debian::template title="Debian Project Leader" BARETITLE="true" -#use wml::debian::translation-check translation="9f2c3e2f64ffd99731f45de697c0b4c733e68ced" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/leader.data" - -<p>The Debian Project Leader (DPL) is the official -representative of the Debian Project. They have two main functions, -one internal and one external.</p> - -<p>In the external function, the Project Leader represents the Debian -Project to others. This involves giving talks and presentations about -Debian and attending trade shows, as well as building good relationships -with other organizations and companies.</p> - -<p>Internally, the Project Leader manages the project and defines its -vision. They should talk to other Debian developers, especially to the -delegates, to see how they can assist their work. A main task of the -Project Leader therefore involves coordination and communication.</p> - - -<h2>Appointment</h2> - -<p>The Project Leader is chosen in an election in which all Debian -Developers are eligible to vote. The Project Leader's term of office is -one year. Six weeks before the leadership post becomes vacant, the -<a href="secretary">Project Secretary</a> initiates a new election. During -the first week, any Debian Developer can become a candidate for this -post by nominating themselves. The next three weeks are used for -campaigning. Each candidate posts their platforms and everyone can direct -questions to one or all candidates. The last two weeks consist of the -polling period during which developers may cast their votes.</p> - -<p>More information about the leader elections are available at -<a href="../vote/">the voting pages</a>.</p> - - -<h2>Tasks performed by the Project Leader</h2> - -<h3>Appoint Delegates or delegate decisions to the - <a href="tech-ctte">Technical Committee</a></h3> - -<p>The Project Leader may define a specific area of responsibility and -delegate it to a Debian developer.</p> - -<h3>Lend authority to other Developers</h3> - -<p>The Project Leader may make statements of support for points of -view or for other members of the project.</p> - -<h3>Make any decision which requires urgent action</h3> - -<h3>Make any decision for whom nobody else has responsibility</h3> - -<h3>In consultation with the developers, make decisions affecting property held -in trust for purposes related to Debian</h3> - -<p>The Project Leader may make decisions about how money owned by Debian is -to be used.</p> - - -<h2>Contact information</h2> - -<p>Contact the Debian Project Leader by sending e-mail in English -to <email "leader@debian.org">.</p> - -<h1>About Our Current Leader</h1> - -<p>The current Debian Project Leader is <current_leader>.</p> - -<h2>Past leaders</h2> - -<p>A complete list of past leaders can be found in the -<a href="$(DOC)/manuals/project-history/leaders">Debian Project -History</a>.</p> diff --git a/greek/devel/passwordlessssh.wml b/greek/devel/passwordlessssh.wml deleted file mode 100644 index 4b7b77841d4..00000000000 --- a/greek/devel/passwordlessssh.wml +++ /dev/null @@ -1,53 +0,0 @@ -#use wml::debian::template title="How to set up ssh so you aren't asked for a password" BARETITLE=true -#use wml::debian::translation-check translation="87a9a20b860797210702af5b17db09a362a220e7" maintainer="galaxico" - -<p>You can create a RSA authentication key to be able to log into a remote -site from your account, without having to type your password.</p> - -<p>Note that once you've set this up, if an intruder breaks into your -account/site, they are given access to the site you are allowed in without a -password, too! For this reason, this should <strong>never</strong> be -done from root.</p> - -<ul> - <li>Run <code>ssh-keygen(1)</code> on your machine, and just hit - enter when asked for a password. - <br> - This will generate both a private and a public key. With older - SSH versions, they will be stored in - <code>~/.ssh/identity</code> and - <code>~/.ssh/identity.pub</code>; with newer ones, they - will be stored in <code>~/.ssh/id_rsa</code> and - <code>~/.ssh/id_rsa.pub</code>.</li> - <li>Next, add the contents of the public key file into - <code>~/.ssh/authorized_keys</code> on the remote site (the file - should be mode 600). - <br> - If you are a developer and you want to access debian.org systems with - such a key, it's possible to have the developer database propagate - your key to all of the debian.org machines. See the - <a href="https://db.debian.org/doc-mail.html">LDAP gateway - documentation</a>.</li> -</ul> - -<p>You should then be able to use ssh to log in to the remote server -without being asked for a password.</p> - -<p><strong>Important:</strong> Note that everyone that has read access -to the private key file can use it to have the same passwordless -access to the remote site. This includes any person that has root -access to your local machine. Therefore it's strongly recommended -that you use a passphrase for your private key if you are not the only -root on your machine. You can use <code>ssh-agent(1)</code> and -<code>ssh-add(1)</code> to type your passphrase only once for all uses -of a specific key in a session. You can automatically load all your -keys in the agent by adding the following lines to your -<code>~/.xsession</code> file:</p> -<pre> - \# if use-ssh-agent is specified in /etc/X11/Xsession.options - \# (this is the default) then you need only the second line - \# eval ssh-agent - ssh-add <filename-of-ssh-key> -</pre> -<p>The <code>ssh-askpass</code> package must be installed in order to -run <code>ssh-add</code> without a terminal.</p> diff --git a/greek/devel/secretary.wml b/greek/devel/secretary.wml deleted file mode 100644 index 1f9a1ec35fc..00000000000 --- a/greek/devel/secretary.wml +++ /dev/null @@ -1,127 +0,0 @@ -#use wml::debian::template title="Debian Project Secretary" BARETITLE="true" NOHEADER="true" -#use wml::debian::translation-check translation="965001d7d8f032b9d41bfa609f0cca3bc3c927d3" maintainer="galaxico" - - <h1 class="title">The Debian Project Secretary</h1> - - <p class="initial"> - As the <a href="$(HOME)/">Debian project</a> grew, - it became apparent that there needed to be a set of semi-formal - rules to help in conflict resolution, and as a result the - constitution was written. The Debian - <a href="constitution">constitution</a> - describes the organisational structure for formal decision - making in the Project. The constitution delineates who makes - decisions, and what powers are attached to each such decision - making individual or body. The office of the Project Secretary - is one of the six entities enumerated in the Debian constitution - as a decision making entity. - </p> - - <p> - Any Debian developer is eligible to be considered for the post - of the Debian Project Secretary. Any person may hold several - posts, except that the Project Secretary may not also be the - <a href="leader">Debian Project Leader</a>, or the Chair of the - <a href="tech-ctte">Technical Committee</a>. - </p> - - <h2>Appointment</h2> - - <p> - Unlike other delegates, who are appointed by the - <a href="leader">Project Leader</a>, - the next Project Secretary is appointed by the Project Leader - and the current Project Secretary. In case the current secretary - and the project leader disagree, they must ask the Developers by - way of general resolution to appoint a Secretary. - </p> - - <p> - The Project Secretary's term of office is 1 year, at which point - they or another Secretary must be (re)appointed. - </p> - - <h2>Tasks performed by the Project Secretary</h2> - - - <h3>Conducting votes</h3> - <p> - The most visible task performed by the secretary is conducting - <a href="$(HOME)/vote/">votes</a> for the project - -- notably the Project Leader elections, but also any other - votes that are run (General Resolutions, for example). Running a - vote also entails determining the number and identity of the - people eligible to vote, for the purpose of calculating quorum. - </p> - - <h3>Standing in for other Officers</h3> - - <p> - The Project Secretary can stand in for the Leader, together with - the Chair of the Technical Committee. In this situation, they - may jointly make decisions if they consider it imperative to do - so -- but only when absolutely necessary and only when - consistent with the consensus of the Developers. - </p> - - <p> - If there is no Project Secretary or the current Secretary is - unavailable and has not delegated authority for a decision then - the decision may be made or delegated by the Chair of the - Technical Committee, as Acting Secretary. - </p> - - <h3>Interpreting the Constitution</h3> - - <p> - The secretary is also responsible for adjudicating any disputes - about interpretation of the constitution. - </p> - - - <h2>Contact information</h2> - - <p>Contact the Debian Project Secretary by sending e-mail in English to - <email "secretary@debian.org">.</p> - - - <h1 class="center">About Our Current Secretary</h1> - - <p> - The current Project Secretary is Kurt Roeckx - <<email "kroeckx@debian.org">>. - Kurt has been involved with free software and linux since 1995, and has - been a Debian Developer since - <a href='https://lists.debian.org/debian-project/2005/08/msg00283.html'>August 2005</a>.<br /> - Kurt has a Masters degree in Electronics and ICT, awarded by Hogeschool - voor Wetenschap & Kunst. - </p> - - <p> - Kurt has been Project Secretary since February 2009; he took up the - position after the previous secretary, Manoj Srivastava, resigned from - the position. Apart from being Project Secretary, Kurt is an AMD64 porter - and maintains - <a href="https://qa.debian.org/developer.php?login=kurt@roeckx.be">12 packages</a> - including libtool, ntp and openssl. - </p> - - <h2>The assistant secretary post</h2> - - <p> - Due to the increasing amount of work (i.e.: votes) that the secretary was - starting to need to handle, the DPL (at the time, Steve McIntyre) and the - previous secretary (Manoj) decided that it would be a good idea to - appoint an assistant in cases of unavailability.<br /> - Currently, Neil McGovern <<email "neilm@debian.org">> serves in - this position. - </p> - - <hrline> - <address> - <a href="mailto:secretary@debian.org">The Debian Project Secretary</a> - </address> - -## Local variables: -## sgml-default-doctype-name: "HTML" -## End: diff --git a/greek/devel/tech-ctte.wml b/greek/devel/tech-ctte.wml deleted file mode 100644 index 73883c2fb80..00000000000 --- a/greek/devel/tech-ctte.wml +++ /dev/null @@ -1,370 +0,0 @@ -#use wml::debian::template title="Debian Technical Committee" BARETITLE="true" -#use wml::debian::toc -#use wml::debian::translation-check translation="c64de4f08b1bd899f017c8059cc6622fd4cd5910" maintainer="galaxico" - -<p>The Technical Committee is established by the -<a href="constitution">Debian Constitution</a>, section 6. It is the body -which makes the final decision on technical disputes in the Debian project. -</p> - -<toc-display/> - -<toc-add-entry name="referquestions">How to refer a question to the committee</toc-add-entry> - -<ol> - -<li>Before referring a decision to the Technical Committee, you should try - to resolve it yourself. Engage in a constructive discussion and try - to understand the other person's point of view. If, after discussion, - you've identified a technical question which you can't agree on, you - can put it to the committee: -</li> - -<li>Write up a summary of the disagreement, preferably agreeing it with - your opponent, and send it to the bug tracking system - <em>as a new bug</em>, against the pseudo-package <tt>tech-ctte</tt>. - In your summary mention any relevant existing bug numbers and mailing - list archive urls. -</li> - -<li>Send an email to all relevant parties inviting them to subscribe to the - bug. If there are existing bug(s) open about the - issue, set the new tech-ctte bug to block them (but if you don't know - how to do this, don't worry - we will do it for you.) - -<li>The committee will discuss your question in the tech-ctte bug. - We will generally not CC discussion to individual participants, - unless we invite them into the conversation to ask them a specific - question. Everyone who is interested in the issue should subscribe - to the bug using the BTS. - -<li>The committee will aim to make a decision as soon as possible. In - practice this process is likely to take many weeks, or perhaps - longer. If the question is particularly urgent please say so. -</li> - -<li>Sometimes, one side or other is convinced, during the committee's - deliberations, by the merit of the other side's arguments. This is a - good thing! If it happens, the committee need not make a formal - decision, and the bug report can be closed, or reassigned, as appropriate. -</li> - -</ol> - -<h3>Some caveats about contacting the committee</h3> - -<ul> - -<li>A sound and vigorous debate is important to ensure that all the - aspects of an issue are fully explored. When discussing technical - questions with other developers you should be ready to be challenged. - You should also be prepared to be convinced! There is no shame in - seeing the merit of good arguments. -</li> - -<li>Please conduct your technical discussions with other maintainers - in a calm and civilised way; do not use insults, or question their - competence. Instead, address yourself to your opponents' arguments. -</li> - -<li>The committee is only empowered to make technical decisions. If - you feel that someone has been misbehaving, the committee probably - can't help you much. You may wish to talk to the Project Leader, - <tt>leader@debian.org</tt>. -</li> - -<li>The bug traffic will also appear on the committee mailing list, - <a href="https://lists.debian.org/debian-ctte/">debian-ctte@lists.debian.org</a>. Anyone else who wishes to do so may subscribe to - the debian-ctte mailing list and see our deliberations. But please - do not send messages relating to specific issues directly to the - list. -</li> - -<li>To post to the committee mailing list you must either be - subscribed to the list from your posting address, or PGP-sign your - message. This is an anti-spam measure. We apologise for the - inconvenience, but this setup makes it possible for committee - members to pay proper attention to the committee list mails. -</li> - -</ul> - -<toc-add-entry name="membership">Membership</toc-add-entry> - -<p>The current membership of the committee is documented on the -<a href="$(HOME)/intro/organization#tech-ctte">\ -Debian Organizational Structure</a> page. -</p> - -<toc-add-entry name="status">Archives and status</toc-add-entry> - -<p>The <a href="https://lists.debian.org/debian-ctte/">committee mailing list -is archived</a>.</p> - -<p><a href="https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=tech-ctte">Questions pending decision</a> -can be reviewed in the bug tracking system.</p> - -<toc-add-entry name="repository">VCS repository</toc-add-entry> - -<p>The TC sometimes uses its -<a href="https://salsa.debian.org/debian/tech-ctte">\ -shared git repository</a> -for collaboration.</p> - -<h3>Formal technical decisions, including recommendations and advice</h3> - -<p> The decision history sections are not necessarily up to date. - (<a href="https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=tech-ctte;archive=yes">Older - questions and decisions</a> can be viewed in the bug tracking - system.)</p> - -<ul> - <li><a href="https://lists.debian.org/debian-devel-announce/2019/03/msg00001.html">2019-03-05</a> - <a href="https://bugs.debian.org/914897">Bug #914897:</a>The - technical committee decided to decline to override the <a - href="https://wiki.debian.org/Debootstrap">debootstrap</a> - maintainer's decision on enabling "merged /usr" by default on newly - installed systems. The decision also clarified the desirable - solution on "merged /usr" status at the time of Debian - Bullseye's release.</li> - <li> - <a href="https://lists.debian.org/debian-devel-announce/2018/11/msg00004.html">2018-11-13</a> - <a href="https://bugs.debian.org/904302">Bug #904302:</a>The - technical committee decided that any use of dpkg's vendor-specific - patch series feature is a bug for packages in the Debian archive - and such feature will be forbidden in the Debian archive after the - release of Debian Buster.</li> - <li> - <a href="https://lists.debian.org/debian-devel-announce/2018/02/msg00004.html">2018-02-16</a> - <a href="https://bugs.debian.org/883573">Bug #883573:</a>The - technical committee repeals the decision made on 2014-11-15 in - <a href="https://bugs.debian.org/746578">Bug #746578</a> and - set the libpam-systemd package's dependencies free from - specific ordering constraints.</li> - <li> - <a href="https://lists.debian.org/debian-devel-announce/2017/07/msg00006.html">2017-07-31</a> - <a href="https://bugs.debian.org/862051">Bug #862051:</a>The - technical committee repeals the decision made on 2012-07-12 in - <a href="https://bugs.debian.org/614907">Bug #614907</a> and - allows nodejs package to provide /usr/bin/node in - backwards-compatibility arrangements.</li> - <li>2015-09-04 - <a href="https://bugs.debian.org/741573">Bug #741573:</a>The - technical committee adopts the changes to policy regarding menu - entries proposed by Charles Plessy, and additionally resolves that - packages providing desktop files shall not also provide a menu - file.</li> -<li>2015-06-19 - <a href="https://bugs.debian.org/750135">Bug #750135:</a>The - technical committee encourages Christian Perrier to implement his - proposal for maintenance of the Aptitude project.</li> -<li>2014-11-15 - <a href="https://bugs.debian.org/746578">Bug #746578:</a>The -committee decided that systemd-shim should be the first listed -alternative dependency of libpam-systemd instead of systemd-sysv.</li> -<li>2014-08-01 - <a href="https://bugs.debian.org/746715">Bug #746715</a>: The -technical committee expects maintainers to continue to support the -multiple available init systems.</li> -<li>2014-08-01 - <a href="https://bugs.debian.org/717076">Bug #717076</a>: The -committee decided that the default libjpeg implementation should be -libjpeg-turbo.</li> -<li>2014-02-11 - <a href="https://bugs.debian.org/727708">Bug #727708</a>: The -committee decided that the default init system for Linux architectures -in jessie should be systemd.</li> -<li>2013-03-06 - <a href="https://bugs.debian.org/698556">Bug #698556</a>: The -committee overrules the maintainer of isdnutils to require the -inclusion of code to create isdn devices by isdnutils.</li> -<li>2012-12-21 - <a href="https://bugs.debian.org/688772">Bug #688772</a>: - The committee overrules the dependency of meta-gnome - on network-manager while concerns raised in <a - href="https://bugs.debian.org/681834#273">§4 of the - decision in #681834</a> remain unaddressed.</li> -<li>2012-10-05 - <a href="https://bugs.debian.org/573745">Bug #573745</a>: - The committee declines to change the maintainer - of python packages in Debian.</li> -<li>2012-09-14 - <a href="https://bugs.debian.org/681834">Bug #681834</a>: gnome-core - should Recommends: network-manager; override maintainer.</li> -<li>2012-08-24 - <a href="https://bugs.debian.org/681783">Bug #681783</a>: Policy on - Recommends is correct; Recommends is fine in metapackages.</li> -<li>2012-08-14 - <a href="https://bugs.debian.org/681687">Bug #681687</a>: - evince's lack of mime type entry for PDF is RC bug - (decline to overrule release team).</li> -<li>2012-07-12 - <a href="https://bugs.debian.org/614907">Bug #614907</a>: - nodejs must use /usr/bin/nodejs, node must change - to ax25-node and provide /usr/sbin/ax25-node, and - transition packages and legacy packages defined.</li> -<li>2012-04-05 - <a href="https://bugs.debian.org/640874">Bug #640874</a>: decline to - override policy maintainers. debian/rules must be a Makefile.</li> -<li>2012-03-21 - <a href="https://bugs.debian.org/629385">Bug #629385</a>: - dpkg-buildpackage will implement build-arch testing using make -qn.</li> -<li>2012-02-27 - <a href="https://bugs.debian.org/607368">Bug #607368</a>: decline to - override the kernel maintainer team's ABI numbering policy.</li> -<li>2012-02-05 - <a href="https://bugs.debian.org/658341">Bug #658341</a>: multi-arch - enabled dpkg may be uploaded to experimental and unstable by Raphaël - Hertzog without waiting for primary maintainer code review.</li> -<li>2010-12-01 - <a href="https://bugs.debian.org/587886">Bug #587886</a>: - lilo should remain in unstable. Matt Arnold and Joachim - Wiedorn are to be joint maintainers of lilo.</li> -<li>2009-09-04 - <a href="https://bugs.debian.org/535645">Bug #535645</a>: - decline to override ftp team's removal of ia32-libs-tools; - reaffirm ftp team's ability to remove packages; - recommend clarification of reasons for removal, - and mechanism of reintroduction to the archive.</li> -<li>2009-08-27 - <a href="https://bugs.debian.org/510415">Bug #510415</a>: - allow Qmail into Debian after fixing delayed-bounce - issue with RC bug to block transition for one month</li> -<li>2009-07-30 - <a href="https://bugs.debian.org/539158">Bug #539158</a>: refuse to - override udev maintainer; printf suggested to be documented as a - required builtin in policy.</li> -<li>2009-07-25 - <a href="https://bugs.debian.org/484841">Bug #484841</a>: by - default, /usr/local is not writable by group staff; change can be - implemented after transition plan which enables administrators to - keep the current behavoir.</li> -<li>2007-12-10 - <a href="https://bugs.debian.org/412976">Bug #412976</a>: - keep current behavior and existing policy regarding mixmaster's use of /etc/default.</li> - -<li>2007-06-22 - <a href="https://bugs.debian.org/367709">Bug #367709</a>: - a libstdc++ udeb should not be created.</li> - -<li>2007-06-19 - <a href="https://bugs.debian.org/341839">Bug #341839</a>: - the output of <code>md5sum</code> should not change.</li> - -<li>2007-04-09 - <a href="https://bugs.debian.org/385665">Bug #385665</a>: - <code>fluidsynth</code> remains in main.</li> - -<li>2007-04-09 - <a href="https://bugs.debian.org/353277">Bug #353277</a>, - <a href="https://bugs.debian.org/353278">Bug #353278</a>: - <code>ndiswrapper</code> remains in main.</li> - -<li>2007-03-27 - <a href="https://bugs.debian.org/413926">Bug #413926</a>: - <code>wordpress</code> should be included in etch.</li> - -<li>2004-06-24 - <a href="https://bugs.debian.org/254598">Bug #254598</a>: - <code>amd64</code> is a fine name for that architecture. - <a href="https://lists.debian.org/debian-ctte/2004/debian-ctte-200406/msg00115.html">Full text</a>. - In favour: Wichert, Raul, Guy, Manoj, Ian. - Voting period ended early; no other votes.</li> -<li>2004-06-05 - <a href="https://bugs.debian.org/164591">Bug #164591</a>, - <a href="https://bugs.debian.org/164889">Bug #164889</a>: - <code>md5sum </dev/null</code> should produce the bare md5sum value. - <a href="https://lists.debian.org/debian-ctte/2004/debian-ctte-200406/msg00032.html">Full text</a>. - In favour: Guy, Ian, Manoj, Raul. - No other votes.</li> -<li>2002-10-06 - <a href="https://bugs.debian.org/104101">Bug #104101</a>, - <a href="https://bugs.debian.org/123987">Bug #123987</a>, - <a href="https://bugs.debian.org/134220">Bug #134220</a>, - <a href="https://bugs.debian.org/161931">Bug #161931</a>: - The default kernel should have VESA framebuffer support included. - <a href="https://lists.debian.org/debian-ctte/2002/debian-ctte-200211/msg00043.html">Full text</a>. - In favour: Ian, Jason, Raul; against: Manoj. - No other votes.</li> -<li>2002-07-19 <a href="https://bugs.debian.org/119517">Bug #119517</a>: - Packages may sometimes contain binaries whose libraries are only - referred to in Suggests. - <a href="https://lists.debian.org/debian-ctte/2002/debian-ctte-200207/msg00017.html">Full - text</a>. In favour: Ian, Wichert; against: Bdale, - Manoj; no-one else voted and Ian used his casting vote.</li> -</ul> - -<p>NB that decisions from before the 1st of April 2002 are not yet -recorded here.</p> - -<h3>Formal nontechnical and procedural decisions</h3> - -<ul> -<li>2015-03-05 Approved Sam Hartman, Tollef Fog Heen and Didier Raboud as - candidates for the committee. - (<a href="https://lists.debian.org/debian-ctte/2015/03/msg00023.html">Full - text</a>. In favour: Don, Bdale, Andreas, Colin, Steve, Keith. - Appointment approved by the DPL 2015-03-08; - <a href="https://lists.debian.org/debian-devel-announce/2015/03/msg00003.html">Full - text</a>).</li> -<li>2013-11-07 Approved Keith Packard as member of the technical committee (<a href="https://lists.debian.org/debian-ctte/2013/11/msg00041.html">resolution</a>)</li> -<li>2011-08-24 Approved Colin Watson as member of the technical committee (<a href="https://lists.debian.org/debian-devel-announce/2011/08/msg00004.html">for appointment</a>)</li> -<li>2009-01-11 Approved Russ Allbery and Don Armstrong as members of the technical committee (<a href="https://lists.debian.org/debian-ctte/2009/01/msg00053.html">summary</a>)</li> -<li>2006-04-11 Elected Bdale as chair (<a href=https://lists.debian.org/debian-ctte/2006/04/msg00042.html>for vote</a>)</li> -<li>2006-02-27 Elected Steve as chair (<a href=https://lists.debian.org/debian-ctte/2006/02/msg00085.html>for summary</a>)</li> -<li>2005-12-20 Approved Steve Langasek, Anthony Towns and Andreas Barth - as candidates for the committee. - (<a href="https://lists.debian.org/debian-ctte/2005/12/msg00042.html">Full - text</a>. In favour: Bdale, Manoj. Expressions of support, - with apologies, after end of the voting period: Ian, Raul. - None against or abstaining; Appointment approved by the DPL 2006-01-05; - <a href="https://lists.debian.org/debian-project/2006/01/msg00013.html">Full - text</a>).</li> -<li>2005-12-20 Proposed the removal of Wichert, Guy, and Jason - from the committee. - (<a href="https://lists.debian.org/debian-ctte/2005/12/msg00000.html">Motion text</a>; <a href="https://lists.debian.org/debian-ctte/2005/12/msg00028.html">results</a>. In favour: Manoj, Raul. Guy: in favour of his own removal; no opinion otherwise. Ian: in favour of removal of Jason; against otherwise. - Removal approved by the DPL 2006-01-05; - <a href="https://lists.debian.org/debian-project/2006/01/msg00013.html">Full - text</a>.)</li> -<li>2002-07-05 Passed the question of proper use of bug system - severities (<a href="https://bugs.debian.org/97671">Bug #97671</a>) - on to the BTS admins and project leader. - (<a href="https://lists.debian.org/debian-ctte/2002/debian-ctte-200207/msg00002.html">Full - text</a>. In favour: Ian, Jason, Bdale; none against or abstaining.)</li> - -<li>2002-01-31 Appointed Ian Jackson as chairman, following Raul's - resignation from the post. (In favour: Dale, Ian, Manoj, Raul, Wichert; - none against or abstaining.)</li> - -</ul> - -<p>NB that decisions from before the 31st of January 2002 are not yet -recorded here.</p> - -<toc-add-entry name="retiredmembers">Retired members</toc-add-entry> - -Thanks to the following people who have served on the committee: - -<ul> -<li>Phil Hands (2016-04-16 - 2020-12-31)</li> -<li>Tollef Fog Heen (2015-03-05 - 2019-12-31)</li> -<li>Didier Raboud (2015-03-05 - 2019-12-31)</li> -<li>Keith Packard (2013-11-29 - 2017-12-31)</li> -<li>Sam Hartman (2015-03-08 - 2017-11-09)</li> -<li>Don Armstrong (2009-09-11 - 2016-12-31)</li> -<li>Andreas Barth (2006-01-04 - 2016-12-31)</li> -<li>Steve Langasek (2006-01-04 - 2015-12-31)</li> -<li>Bdale Garbee (2001-04-17 - 2015-12-31)</li> -<li>Colin Watson (2011-08-24 - 2015-03-05)</li> -<li>Ian Jackson (to 2014-11-19)</li> -<li>Russ Allbery (2009-01-11 - 2014-11-16)</li> -<li>Manoj Srivasta (to 2012-08-12)</li> -<li>Anthony Towns (2006-01-04 - 2009-01-05)</li> -<li>Raul Miller (to 2007-04-30)</li> -<li>Wichert Akkerman (to 2006-01-05)</li> -<li>Jason Gunthorpe (to 2006-01-05)</li> -<li>Guy Maor (to 2006-01-05)</li> -<li>Dale Scheetz (to 2002-09-02)</li> -<li>Klee Dienes (to 2001-05-21)</li> - -</ul> diff --git a/greek/devel/testing.wml b/greek/devel/testing.wml deleted file mode 100644 index 64176b6f9ee..00000000000 --- a/greek/devel/testing.wml +++ /dev/null @@ -1,320 +0,0 @@ -#use wml::debian::template title="Debian “testing” distribution" BARETITLE=true -#include "$(ENGLISHDIR)/releases/info" -#use wml::debian::translation-check translation="8900568ad5473cc15ea75f71f489b4f2b7ae659e" maintainer="galaxico" - -<p>For basic, user-oriented information about the testing distribution, -please see <a href="$(DOC)/manuals/debian-faq/ftparchives#testing">the Debian FAQ</a>.</p> - -<p>An important thing to note, both for regular users and the developers of -testing, is that security updates for testing are <strong>not managed by -the security team</strong>. For more information please see the -<a href="../security/faq#testing">Security Team's FAQ</a>.</p> - -<p>This page primarily covers the aspects of <q>testing</q> important to Debian -developers.</p> - -<h2>How <q>testing</q> works</h2> - -<p>The <q>testing</q> distribution is an automatically generated distribution. -It is generated from the <q>unstable</q> distribution by a set of scripts which -attempt to move over packages which are reasonably likely to lack release-critical -bugs. They do so in a way that ensures that dependencies of other packages -in testing are always satisfiable.</p> - -<p>A (particular version of a) package will move into testing when it -satisfies all of the following criteria:</p> - -<ol> - <li>It must have been in unstable for 10, 5 or 2 days, depending on the - urgency of the upload;</li> - - <li>It must be compiled and up to date on all architectures it has - previously been compiled for in unstable;</li> - - <li>It must not have release-critical bugs which do not also apply to - the version currently in <q>testing</q> (see below for - <a href="#faq">more information</a>);</li> - - <li>All of its dependencies must <em>either</em> be satisfiable by - packages already in <q>testing</q>, <em>or</em> be satisfiable by the group - of packages which are going to be installed at the same time;</li> - - <li>The operation of installing the package into <q>testing</q> must not break - any packages currently in <q>testing</q>. (See below for - <a href="#faq">more information</a>.)</li> -</ol> - -<p>A package which satisfies the first three of the above is said to be a -<q>Valid Candidate</q>.</p> - -<p>The update script shows when each package might move from <q>unstable</q> into -<q>testing</q>. The output is twofold:</p> - -<ul> - <li>The <a href="https://release.debian.org/britney/update_excuses.html">\ - update excuses</a> - [<a href="https://release.debian.org/britney/update_excuses.html.gz">\ - gzipped</a>]: - list of all candidate package versions and the basic status of their - propagation into <q>testing</q>; this is somewhat shorter and nicer than - </li> - <li>The <a href="https://release.debian.org/britney/update_output.txt">\ - update output</a> - [<a href="https://release.debian.org/britney/update_output.txt.gz">\ - gzipped</a>]: - the complete, rather crude output of the <q>testing</q> scripts as they - recurse through the candidates - </li> -</ul> - -<h2><a name="faq">Frequently Asked/Answered Questions</a></h2> - -# Note to translators: these two first items are almost the same as -# https://www.debian.org/doc/manuals/developers-reference/pkgs.html#faq - -<h3><q>What are release-critical bugs, and how do they get counted?</q></h3> - -<p>All bugs of some higher severities are by default considered -<em><a href="https://bugs.debian.org/release-critical/">release-critical</a></em>; -currently, these are <strong>critical</strong>, <strong>grave</strong> and -<strong>serious</strong> bugs.</p> - -<p>Such bugs are presumed to have an impact on the chances that the package -will be released with the stable release of Debian: in general, if a package -has open release-critical bugs filed on it, it won't get into <q>testing</q>, and -consequently won't be released in <q>stable</q>.</p> - -<p> -The <q>testing</q> bug count are all release-critical bugs which -are marked to apply to <tt>package/version</tt> combinations -that are available in <q>testing</q>for a release architecture. -</p> - - -<h3><q>How could installing a package into <q>testing</q> possibly break other -packages?</q></h3> - -<p>The structure of the distribution archives is such that they can only -contain one version of a package; a package is defined by its name. So, when -the source package <tt>acmefoo</tt> is installed into <q>testing</q>, along with -its binary packages <tt>acme-foo-bin</tt>, <tt>acme-bar-bin</tt>, -<tt>libacme-foo1</tt> and <tt>libacme-foo-dev</tt>, the old version is -removed.</p> - -<p>However, the old version may have provided a binary package with an old -soname of a library, such as <tt>libacme-foo0</tt>. Removing the old -<tt>acmefoo</tt> will remove <tt>libacme-foo0</tt>, which will break any -packages which depend on it.</p> - -<p>Evidently, this mainly affects packages which provide changing sets of -binary packages in different versions (in turn, mainly libraries). However, -it will also affect packages upon which versioned dependencies have been -declared of the ==, <= or << varieties.</p> - -<p>When the set of binary packages provided by a source package change in -this way, all the packages that depended on the old binaries will have to be -updated to depend on the new binaries instead. Because installing such a -source package into <q>testing</q> breaks all the packages that depended on it in -<q>testing</q>, some care now has to be taken: all the depending packages must be -updated and ready to be installed themselves so that they won't be broken, -and, once everything is ready, manual intervention by the release manager or -an assistant is normally required.</p> - -<p>If you are having problems with complicated groups of packages like this, -contact debian-devel or debian-release for help.</p> - -<h3><q>I still don't understand! The <q>testing</q> scripts say that this -package is a valid candidate, but it still hasn't gone into -<q>testing</q>.</q></h3> - -<p>This tends to happen when in some way, directly or indirectly, installing -the package will break some other package.</p> - -<p>Remember to consider your package's dependencies. Suppose your package -depends on libtool, or libltdl<var>X</var>. Your package won't go into -<q>testing</q> until the right version of libtool is ready to go in with it.</p> - -<p>In turn, that won't happen until installing libtool doesn't break things -already in <q>testing</q>. In other words, until all other packages which depend -on libltdl<var>Y</var> (where <var>Y</var> is the earlier version) have been -recompiled, and all their release critical bugs are gone, etc, none of these -packages will enter <q>testing</q>.</p> - -<p>This is where the <a href="https://release.debian.org/britney/update_output.txt">\ -textual output</a> -[<a href="https://release.debian.org/britney/update_output.txt.gz">gzipped</a>] -is useful: it gives hints (albeit very terse ones) as to which packages -break when a valid candidate is added to <q>testing</q> (see the <a -href="$(DOC)/manuals/developers-reference/pkgs.html#details">\ -Developer's Reference for more details</a>). -</p> - -<h3><q>Why is it sometimes hard to get <kbd>Architecture: all</kbd> packages -into <q>testing</q>?</q></h3> - -<p>If the <kbd>Architecture: all</kbd> package is to be installed, it must -be possible to satisfy its dependencies on <strong>all</strong> -architectures. If it depends on certain packages which only compile on a -limited set of Debian's architectures, then it can't do that.</p> - -<p>However, for the time being, <q>testing</q> will ignore <kbd>Architecture: -all</kbd> packages' installability on non-i386 architectures. (<q>It's a -gross hack and I'm not really happy to have made it, but there you go.</q> -—aj)</p> - -<h3><q>My package is stalled because it's out of date on some architecture. -What do I do?</q></h3> - -<p>Check the status of your package in the -<a href="https://buildd.debian.org/build.php">build log database</a>. -If the package doesn't build, it will be marked as <em>failed</em>; -investigate the build logs and fix any of the problems that are caused -by your package's sources.</p> - -<p>If you happen to notice that some architectures have built the new -version of your package, but it isn't showing up in <q>testing</q> scripts output, -then you just have to be a bit more patient until the respective buildd -maintainer uploads the files to the Debian archive.</p> - -<p>If you notice that some architectures haven't built your new version of -the package at all, despite the fact you uploaded a fix for an earlier -failure, the reason is probably that it's marked as waiting for dependencies -(Dep-Wait). You can also see the list of these so-called -<a href="https://buildd.debian.org/stats/">wanna-build states</a> to make -sure.</p> - -<p>These problems usually get fixed eventually, but if you've been waiting -for a longer period of time (say, two weeks or more), notify the respective -port buildd maintainer if such an address is documented on the -<a href="$(HOME)/ports/">port web page</a>, or the mailing list of the -port.</p> - -<p>If you have explicitly dropped the architecture from the Architecture list -in the control file, and the package has been built for that architecture -before, you will need to request that the old binary package for this -architecture be removed from the archive before your package can transition to -testing. You need to file a bug against <q>ftp.debian.org</q> requesting removal of -the dropped architecture's packages from the unstable archive. Generally the -relevant porting list should be informed as a matter of courtesy.</p> - -<h3><q>Are there any exceptions? I'm sure <tt>acmefoo</tt> has just made -it into <q>testing</q> despite not satisfying all of the requirements.</q></h3> - -<p>The release manager can override the rules in two ways:</p> - -<ul> - <li>They can decide that the breakage caused by the installation of a new - library will make things better rather than worse, and let it go in - along with its flotilla of dependents.</li> - <li>They can also manually remove packages from <q>testing</q> that would be - broken, so that new stuff can be installed.</li> -</ul> - -<h3><q>Can you provide a real, non-trivial example?</q></h3> - -<p>Here's one: when the source package <tt>apache</tt> is installed into -<q>testing</q>, along with its binary packages <tt>apache</tt>, -<tt>apache-common</tt>, <tt>apache-dev</tt> and <tt>apache-doc</tt>, the -old version is removed.</p> - -<p>However, all Apache module packages depend on <code>apache-common (>= -<var>something</var>), apache-common (<< <var>something</var>)</code>, -so this change breaks all of those dependencies. Consequently, all Apache -modules need to be recompiled against the new version of Apache in order -for <q>testing</q> to be updated.</p> - -<p>Let's elaborate on this a bit further: after all of the modules have been -updated in unstable to work with a new Apache, the <q>testing</q> scripts try -<tt>apache-common</tt> and find out that it breaks all the Apache modules -because they have <code>Depends: apache-common (<< <var>the current -version</var>)</code>, and then try <tt>libapache-<var>foo</var></tt> to find -out that it doesn't install because it has <code>Depends: apache-common (>= -<var>the new version</var>)</code>.</p> - -<p>However, later they'll apply a different logic (sometimes prompted by a -manual intervention): they'll ignore the fact <tt>apache-common</tt> breaks -stuff, and keep going with things that work; if it still doesn't work after -we've done everything we can, too bad, but maybe it <strong>will</strong> -work. Later they'll try all the random <tt>libapache-<var>foo</var></tt> -packages and see that they indeed work.</p> - -<p>After everything's been tried, they check how many packages have been -broken, work out if that's better or worse than what there was originally -and either accept everything or forget about it. You'll see this in -<tt>update_output.txt</tt> on <q><code>recur:</code></q> lines.</p> - -<p>For example:</p> - -<pre> - recur: [<var>foo</var> <var>bar</var>] <var>baz</var> -</pre> - -<p>basically says <q>having already found that <var>foo</var> and -<var>bar</var> make things better, I'm now trying <var>baz</var> to -see what happens, even though that breaks things</q>. The lines of -<tt>update_output.txt</tt> that start with <q><code>accepted</code></q> indicate -things that appear to make things better, and <q><code>skipped</code></q> lines make -things worse.</p> - -<h3><q>The <tt>update_output.txt</tt> file is completely unreadable!</q></h3> - -<p>That is not a question. ;-)</p> - -<p>Let's take an example:</p> - -<pre> - skipped: cln (0) (150+4) - got: 167+0: a-40:a-33:h-49:i-45 - * i386: ginac-cint, libginac-dev -</pre> - -<p>This means that if <tt>cln</tt> goes into <q>testing</q>, <tt>ginac-cint</tt> -and <tt>libginac-dev</tt> become uninstallable in <q>testing</q> on i386. -Note that the architectures are checked in alphabetical order and only the -problems on the first architecture with problems are shown — that's why -the alpha architecture is shown so often.</p> - -<p>The <q>got</q> line includes the number of problems in <q>testing</q> on the -different architectures (until the first architecture where a problem is -found — see above). The <q>i-45</q> means that if <tt>cln</tt> would go into -<q>testing</q>, there would be 45 uninstallable packages on i386. Some of the -entries above and below <tt>cln</tt> show there were 43 uninstallable -packages in <q>testing</q> on i386 at the time.</p> - -<p>The <q>skipped: cln (0) (150+4)</q> line means that there are still 150 -packages to go through after this package until this check of all packages -is completed, and that 4 packages have been found already that won't be -planned to be upgraded because they would break dependencies. The <q>(0)</q> is -irrelevant, you can safely ignore it.</p> - -<p>Note that there are several checks of all packages in one <q>testing</q> -script run.</p> - -<p><em>Jules Bean initially assembled the frequently asked questions and -answers.</em></p> -# Created: Sat Dec 8 12:44:29 GMT 2001 - -<h2>Additional information</h2> - -<p>The following pages provide additional information about the current state -of testing and the migration of packages from unstable to testing:</p> - -<ul> -<li>Statistics on binary packages that are out of date for -<a href="https://release.debian.org/britney/testing_outdate.txt">testing</a>, -<a href="https://release.debian.org/britney/stable_outdate.txt">stable</a> -<li>Dependency problems in -<a href="https://qa.debian.org/debcheck.php?list=INDEX&dist=testing">testing</a>, -<a href="https://qa.debian.org/debcheck.php?list=INDEX&dist=stable">stable</a> -</ul> - -<p>You might be interested in reading an older -<a href="https://lists.debian.org/debian-devel-0008/msg00906.html">explanation -email</a>. Its only major flaw is that it doesn't take the package pool -into account, because that was implemented by James Troup after it was -written.</p> - -<p>The testing code is available from -<a href="https://release.debian.org/britney/update_out_code/">ftp-master</a>.</p> - -<p><em>Anthony Towns takes credit for the implementation of testing.</em></p> diff --git a/greek/devel/website/content_negotiation.wml b/greek/devel/website/content_negotiation.wml deleted file mode 100644 index 0ff8203631f..00000000000 --- a/greek/devel/website/content_negotiation.wml +++ /dev/null @@ -1,31 +0,0 @@ -#use wml::debian::template title="Content Negotiation" -#use wml::debian::translation-check translation="c646e774c01abc2ee3d32c65d6920ea4f03159dc" maintainer="galaxico" - -<H3>How Does the Server Know Which File to Serve</H3> -<P>You will notice that internal links don't end in .html. This -is because the server is using content negotiation to decide -which version of the document to deliver. When there is more -than one choice, the server will make a list of all possible -files to serve, e.g. if the request is for 'about', then the list -of completions might be about.en.html and about.de.html. -The default for Debian servers will be to serve the English -document, but it is configurable. - -<P>If a client has the proper variable set, for example to serve German, -then in the example above about.de.html would be served. The -nice thing about this setup is that if the desired language is -not available, a different language will be delivered instead -(which hopefully is better than nothing). The decision on which -document is served is a bit confusing so instead of describing -it here, you should get the definitive answer from -<a href="https://httpd.apache.org/docs/current/content-negotiation.html">https://httpd.apache.org/docs/current/content-negotiation.html</a> -if you are interested. - -<P>Because many users will not even know of the existence of content-negotiation, -there are links at the bottom of every page pointing directly -to the version of that page in every other language available. -This is computed using a perl script called by wml when the -page is generated. - -<P>There is also an option to override the browser language preferences -using a cookie that prioritises a single language over the browser preferences. diff --git a/greek/devel/website/desc.wml b/greek/devel/website/desc.wml deleted file mode 100644 index 42f731e7468..00000000000 --- a/greek/devel/website/desc.wml +++ /dev/null @@ -1,176 +0,0 @@ -#use wml::debian::template title="How is www.debian.org made" -#use wml::debian::toc -#use wml::debian::translation-check translation="6d9ec7201dcfa229e0cdf7f93c34b3d4a8509ebe" maintainer="galaxico" - -<p>The Debian <em>“webtree”</em>, collection of directories and files -that comprise our web site, is located in the <tt>/org/www.debian.org/www</tt> -directory on www-master.debian.org. The bulk of the pages are normal static -HTML files (i.e. not produced with something dynamic such as a CGI or a PHP -script), because the web site is mirrored. - -<p>The site is generated in one of three ways: -<ul> - <li>the bulk of it is generated using WML, from the - <a href="$(DEVEL)/website/using_git"><q>webwml</q> git repository</a> - <li>the documentation is generated either using DocBook XML (use of DebianDoc - SGML is being phased out), from the - <a href="$(DOC)/vcs"><q>ddp</q> git repository</a>; or - using <a href="#scripts">cron scripts</a>, from the corresponding - Debian packages - <li>parts of the site are generated using scripts using other sources, - e.g. the mailing list (un)subscription pages -</ul> - -<p>An automatic update (from the git repository and other sources to the -webtree) is being run six times a day. - -<p>If you'd like to contribute to the site, do <strong>not</strong> simply -add to or edit items in the <code>www/</code> directory. Contact -<a href="mailto:webmaster@debian.org">the webmasters</a> first. - -<p>All the files and directories are owned by group debwww and writable -by that group, so the web team can modify files in the web directory. The -2775 mode on directories means that any files created under that directory -will inherit the group - debwww in this case. Anyone in group debwww is -expected to set '<code>umask 002</code>' so that the files are created with -group write permissions. - -<toc-display /> - -<hrline /> - - -<toc-add-entry name="look">Look & feel</toc-add-entry> - -<p>We give the pages the same look and feel by having -<a href="https://packages.debian.org/unstable/web/wml">WML</a> do all -the detail work of adding headers and footers to pages. Although a .wml page -may look like HTML at first glance, HTML is only one of the types of extra -information that can be used in .wml. After WML is finished running its various -filters over a file, the final product is true HTML. To give you an idea of -the power of WML, you can include Perl code into a page to allow you to do, -well, almost anything. - -<p>Note however that WML checks (and sometimes automagically corrects) only -the very basic validity of your HTML code. You should install -<a href="https://packages.debian.org/unstable/web/weblint">weblint</a> -and/or -<a href="https://packages.debian.org/unstable/web/tidy">tidy</a> -to validate your HTML code. - -<p>Our web pages currently comply to the -<a href="http://www.w3.org/TR/html4/">HTML 4.01 Strict</a> standard. - -<p>Anyone who is working on a lot of pages should install WML so they can -test to make sure the result is what they want. If you are running Debian, -you can easily install the <code>wml</code> package. Read the pages on -<a href="using_wml">using WML</a> for more information. - - -<toc-add-entry name="sources">Sources</toc-add-entry> - -<p>The source for the web pages is stored under git. git is a version -control system, which allows us to keep a log of which, who, when, and why changes -occurred, etc. It is a safe way to control the concurrent editing of source -files among multiple authors, which is crucial for us because the Debian web -team is rather large in size. - -<p>If you are unfamiliar with this program, you will want to read the pages -on <a href="using_git">using git</a>. - -<p>The topmost webwml directory in the git repository contains directories -named after the languages the web site is in, two makefiles and several -scripts. The translation directory names should be in English and lowercase -(e.g. "german", not "Deutsch"). - -<p>The more important of the two makefiles is Makefile.common, which, as its -name says, contains some common rules which are applied by including this -file in the other makefiles. - -<p>Each of the language directories contains makefiles, WML source files and -subdirectories. The file and directory names do not differ in order to keep -the links correct for all languages. The directories may also contain .wmlrc -files which contain some information useful to WML. - -<p>The webwml/english/template directory contains special WML files that we -call templates, because they can be referenced from all other files using the -<code>#use</code> command. - -<p>In order for changes in the templates to propagate to the files which use -them, the files have makefile dependencies on them. Since a vast majority of -the files use the "template" template, by having a -"<code>#use wml::debian::template</code>" line at the top, the generic -dependency (the one for all files) is that very template. There are -exceptions to this rule, of course. - - -<toc-add-entry name="scripts">Scripts</toc-add-entry> - -<p>The scripts are mostly written in shell or Perl. Some of them are -standalone, and some of them are integrated into WML source files.</p> - -<p>The sources for the main www-master rebuild scripts are in the -<a href="https://salsa.debian.org/webmaster-team/cron.git">webmaster-team/cron -Git repository</a>. -</p> - -<p>The sources for the packages.debian.org rebuild scripts are in the -<a href="https://salsa.debian.org/webmaster-team/packages">webmaster-team/packages -Git repository</a>.</p> - - -<toc-add-entry name="help">How to help</toc-add-entry> - -<p>We invite everyone interested to help us make the Debian site as good as -it can be. If you have valuable information related to Debian that you think -our pages are missing, <a href="mailto:debian-www@lists.debian.org">share it -with us</a> and we'll see that it gets included. - -<p>We could always use help with designing pages (regarding graphics and -layouts), and keeping our HTML clean, too. We regularly run the following -checks on the whole web site:</p> - -<ul> - <li><a href="https://www-master.debian.org/build-logs/urlcheck/">URL check</a> - <li><a href="https://www-master.debian.org/build-logs/validate/">wdg-html-validator</a> - <li><a href="https://www-master.debian.org/build-logs/tidy/">tidy</a> -</ul> - -<p>Help is always welcome in reading the above logs and fixing the problems.</p> - -<p>The current build logs for the web site can be found at -<url "https://www-master.debian.org/build-logs/">.</p> - -<p>If you're a fluent English speaker, we'd like you to proof-read our pages -and report all errors to <a href="mailto:debian-www@lists.debian.org">us</a>. - -<p>If you speak another language, you may want to help us translate the -pages to your language. If a translation has already been made, but has -problems, take a look at the list of <a href="translation_coordinators">\ -translation coordinators</a> and talk to the leader for your language -about fixing it. If you'd like to translate pages yourself, see the page on -<a href="translating">that topic</a> for more information. - -<p>There's also a <a href="todo">TODO file</a>, check it out.</p> - - -<toc-add-entry name="nohelp">How <strong>not</strong> to help</toc-add-entry> - -<p><em>[Q] I want to put <var>fancy web feature</var> into www.debian.org, -may I?</em> - -<p>[A] No. We want www.debian.org to be as accessible as possible, so -<ul> - <li>no browser specific "extensions". - <li>no relying on images only. Images may be used to clarify, but the - information on www.debian.org must remain accessible via a text-only - web browser, like lynx. -</ul> - -<p><em>[Q] I have this nice idea. Can you enable FOO in www.debian.org's -HTTPD, please?</em> - -<p>[A] No. We want to make life easy for administrators to mirror -www.debian.org, so no special HTTPD features please. No, not even SSI. -An exception has been made for content negotiation. This is because it -is the only robust way to serve multiple languages. diff --git a/greek/devel/website/errors/404.wml b/greek/devel/website/errors/404.wml deleted file mode 100644 index 7a19f95d611..00000000000 --- a/greek/devel/website/errors/404.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::template title="Page not found" -#use wml::debian::translation-check translation="1fed65f277a53d12839ebbf4454d9f7ea9fca5ed" maintainer="galaxico" - -<p>We are sorry, the page you were looking for can't be found on this site. -Please inform the site owner that referred you to this page about the broken -link. You can go to the <a href="$(HOME)">home page of the Debian project</a> in the -meantime or use the <a href="$(SEARCH)">search engine</a> to crawl the website for the -information you are looking for.</p> - - diff --git a/greek/devel/website/errors/Makefile b/greek/devel/website/errors/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/devel/website/errors/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/devel/website/htmlediting.wml b/greek/devel/website/htmlediting.wml deleted file mode 100644 index 1a4673df9ef..00000000000 --- a/greek/devel/website/htmlediting.wml +++ /dev/null @@ -1,141 +0,0 @@ -#use wml::debian::template title="Debian Web Pages HTML Usage" BARETITLE=true -#use wml::debian::common_tags -#use wml::debian::acronyms -#use wml::debian::toc -#use wml::debian::translation-check translation="648de6ad5bea60540e41a5733da0b761a34c7927" maintainer="galaxico" - -<p> -This page is still a draft. -</p> - -<toc-display/> - -<toc-add-entry name="preface">Preface</toc-add-entry> - -<p>This page is built to help editors and translators to form well-tagged pages. -It contains hints about tag usage and how to create new pages and make them -more easy to translate.</p> - - -<toc-add-entry name="general">Some general hints</toc-add-entry> -<p>For new pages or translations here's a list of general advice</p> -<dl> -<dt>do not use long lines</dt> -<dd> -The wml files and other files should have lines fitting in a normal -terminal window. This is easier to edit in vi, better searchable and -easier to translate. It's also important because -it's harder to resolve conflicts in long lines. -</dd> -<dt>keep tags in separate lines if possible</dt> -<dd> -Most HTML tags can be kept in separate lines. Some of them are <div>, -<p>, <table>, <ul>. To make things easier for translators, -you should keep all tags that can be used this way in separate lines. Otherwise -translators may delete tags accidentally and forget to restore -them after translating. -</dd> -<dt>do not use spaces or line breaks in inline tags</dt> -<dd>Some tags produce a space, if they are kept in separate lines. One of those -is the <q>tag for small citations or quotes. You may only separate them -as a whole with content in one line. Else there might be a space between content -and tag in the HTML page afterwards. Between words in these tags you may -have as many line breaks or spaces as you want. -</dd> -</dl> - -<toc-add-entry name="abbreviations">Abbreviations and Acronyms</toc-add-entry> -<p> -For abbreviations and acronyms the HTML tag <acronym> should be used. -There are two reasons why the use of the <abbr> tag is not recommended: -First not all -browsers do support it and second there are inconsistent definitions about what -is an acronym and what is an abbreviation. -</p> -<p> -An acronym is added to the page in the following syntax: -<code><acronym lang="language code" title="Full definition of -acronym">ACRONYM</acronym></code>. The title contains the full spoken -words. If the acronym is built from initial letters of words, those letters -should be upper case in the title. The lang attribute is only needed if the -acronym or abbreviation is in a foreign language. -</p> -<p> -There is already a set of common acronyms in the wml templates -included to use it in your page, you have to add a line to use -<code>acronyms</code> in the wml file. For example the wml tag for DD is -<acronym_DD />. -</p> - -<toc-add-entry name="citations">Citations and Quotes</toc-add-entry> -<p> -There are several different rules what a citation or quote is for different -languages. If you have a short inline citation you have to use the <q> -tag. -The rendering of the content is handled by language CSS. <q> tags must -not have a space or line break between the opening and closing tag and the -content. -</p> -<p> -For longer citations the tag <blockquote> is used. A <blockquote> -encloses one or more paragraphs of text, which are marked with <p>. -Please do not use the <blockquote> tags for centering any block of text -which is not a citation. Blockquotes are exclusively for citations and will -be rendered by language specific CSS code in the future. -</p> -<p> -There is also a <cite> tag in HTML. The <cite> tag is not used for -the citation text itself. It is used for the source of a citation. This can be -the name of the person the citation is from and is added as attribute -to a <blockquote> as URL. -</p> - -<toc-add-entry name="code">Program Names and Code</toc-add-entry> -<p> -For program names and computer code there is a tag named <code>. Browsers -normally know about displaying code and program names, but rendering -can also be changed by CSS. It is not a good idea to use <tt> -instead as this does not say anything about the content. -</p> - -<toc-add-entry name="samp">Samples of Computer Output</toc-add-entry> -<p> -For computer output on the screen there is a special tag named <samp>. If -you have a larger block of computer output, you should also have -a look into the CSS file, if there is a special class for it. -</p> - -<toc-add-entry name="kbd">Keyboard Input</toc-add-entry> -<p>If there are examples where the user has to type something on the -keyboard, the <kbd> tag is used for the user input. See also the chapter -about <a href="#var">variables</a> for how to tag the variable input. -</p> - -<toc-add-entry name="var">Variables</toc-add-entry> -<p> -Sometimes it is necessary to emphasize a variable input such as -a special IP address or the users name which has to be -given in a program call on command line. For these variable inputs the <var> -tag is used. -</p> - -<toc-add-entry name="pre">Preformatted Content</toc-add-entry> -<p> -The <pre> tag is use for preformatted text only. Line length, spaces and -other things will be preserved. Naturally this tag cannot contain most -of the other HTML tags. -</p> - -<toc-add-entry name="img">Images</toc-add-entry> -<p> -If there are images added in the page, there is no need to add an invalid -border=0 as attribute. But if possible the image size and an <code>alt</code> attribute -should -be added. The size is added by wml if not present, but that needs compile -time. The <code>alt</code> attribute should contain something that tells users browsing -with lynx and blind people what is in the image. -</p> - - -# <toc-add-entry name=""></toc-add-entry> - diff --git a/greek/devel/website/todo.wml b/greek/devel/website/todo.wml deleted file mode 100644 index f9ced53d611..00000000000 --- a/greek/devel/website/todo.wml +++ /dev/null @@ -1,292 +0,0 @@ -#use wml::debian::template title="Debian Web Pages TODO List" BARETITLE=true -#use wml::debian::common_tags -#use wml::debian::toc -#use wml::debian::translation-check translation="4c1a7bf103f9b1ba7228b8356649c7dcb99f1cb2" maintainer="galaxico" - -# Note to translators: there should be no need to translate this file, -# unless you're some sort of masochistic psycho :) - -<toc-display/> - -<toc-add-entry name="important">Fairly important items</toc-add-entry> - -<h3>/donations and /partners/</h3> - - <P>Make a page for old donations, we don't want to forget the past ones, - but they'd clutter up the page of current donations. Same for partners. - - <p>Separate huge chunks of non-translatable data from the donations page. - See /mirror/sponsors for a start. - -<h3>/ports/</h3> - - <p>All port specific information should be in the port pages. - (More of a long-standing wishlist that can't ever be fixed. :) - - <p>Review the ports listed as unmaintained in the port.maintainers file - and fix them. - - <p>Import the sh port pages. - -<h3>/intro/about</h3> - - <P>This page should be shortened and have the more detailed information in - links. There has been a suggestion that we create an advocacy page with - links to other free projects that Debian supports. - - <P>One example is licenses. I [treacy?] wrote a bit about them, but it - really should be moved to its own page (see <tt>intro/license_disc.wml</tt>). - We need to convince people that some licenses are better than others. Hmmm - sounds like this should be linked from the advocacy page too. - - <P>Writing an intro to something like Debian is not an easy job. You - really need to give some thought into how you split up all the - (interconnected) issues involved. - -<h3>/intro/advocacy</h3> - - <P>A new page as mentioned above. The LPF needs to be linked from here - (this is what started the idea of an advocacy page). - - <P>This should probably be created only when someone has time to redo all - the intro documents. I [treacy?] have a lot of ideas on this and will do - it myself if I get enough time. - -<h3>/CD/vendors/</h3> - - <P>All the vendors web sites need to be checked to see that they actually - contribute. They should also be checked after each major release of Debian. - - <P>Another solution would be to move it to a database-driven system. - There's already some sort of an internal database that only Craig knows - about. - - <P><I>This page is being maintained by Craig Small (csmall@debian.org)</I> - -<h3>/consultants/index</h3> - - <p>This needs to be split up. (by continent, perhaps by country too) - -<h3>/events/*/</h3> - - <p>Too much redundant stuff is left in the files translators touch; the - same thing with .data files that we (treacy with some help from joy) did - to security/ should be done here. Plus, this would make a single location - where we change whether an event is past or current, which is a major - hassle. - -<h3>/doc/books</h3> - - <p>The tags for title, author, language, url, and available should be - separated from the translatable portion of the page. - -<h3>/vote/*/</h3> - - <p>Get the secretary to (help) maintain these pages. - - <p>Figure out if we should keep basic+votebar templates, instead of just - one template ("votepage" or something). - -<h3>packages.debian.org</h3> - - <p>You can find a current <a - href="https://salsa.debian.org/webmaster-team/packages/blob/master/TODO">TODO - list</a> in the <a - href="https://salsa.debian.org/webmaster-team/packages/">Git - repository</a>.</p> - - <p><i>The scripts are currently maintained by Frank 'djpig' Lichtenheld and - Martin 'Joey' Schulze.</i></p> - -<h3>/ports/hurd</h3> - - <p>Move this out of ports because they is not a Linux port (beowulf already removed). (Rename - /ports/, too?) - -<h3>/sitemap</h3> - - <p>Maybe we should emphasize some major pages by making them - <strong> or <em>. - -<h3>lists.debian.org</h3> - - <p>"We might want to put a note on lists.debian.org, pointing out that - Debian reserves the right to archive any mail that comes into Debian." - -- David Starner - - <p>There's now a note to that effect in /MailingLists/. - -<h3>/security/*/</h3> - - <p>Find the <moreinfo> entries for older years that contain mentions - of lists-archives instead of including text from it or even linking to it, - and correct it. - - <p>There are many advisories in 1997 and early 1998 that lack even the - basic extra information -- find it and document it. Somehow. :) - - <p>Change the pages to have 'fixed in' info in a tag instead of page body, - so that we can check for that tag in the template and not display 'Fixed - in:' if it's empty. - -<h3>/ports/i386/</h3> - - <p>Make the x86 port pages more useful... somehow :) - -<h3>/MailingLists/{,un}subscribe</h3> - - <p>Split it up by section? Perhaps, if it grows too much... - - <p>This is already partially remedied by having various - https://lists.debian.org/foo pages include a sub/unsub form. - - <p>Make a note about the anti-abuse check. - -<h3>/intro/organization</h3> - - <p>Collect remaining missing representatives of Debian in other places, - verify/maintain the current ones. - -<h3>/devel/website/*</h3> - - <p>Code all the remaining best current practices. - -<toc-add-entry name="cn">Content negotiation issues</toc-add-entry> - - <p>The content negotiation system has several flaws that might make some - people give up on our site. However, we can't do much about this. Most of - it is caused by clients sending non-RFC strings in the Accept-Language - header, which makes Apache go bezerk and apply some of its illogical - methods of serving smallest available files. - - <p>When given "*" in the Accept-Language header, the first available page - will be served, and that's most likely not English, rather Arabic or - Chinese. This is especially problematic when the user's language - preference is a two-part language code (like "en-ca" or "nl-BE") followed - by a "*". - - <p>Apache 1.3 sticks with the RFC here. Apache 2.0's code will imply a - en or nl respectively, but it will be low priority so it probably won't - help with e.g. "en-ca, fr-ca, *". - - <p>Also, when there exists a file of unknown language, i.e. an unrecognized - foo.*.html file with no AddLanguage or LanguagePriority setting, and when - the client sends an Accept-Language which contains only unavailable - languages, the former file will be served. - - <p>This happened most often with the /releases/potato/i386/install page, - because there's a Slovak variant of it and we didn't have that language - set up in Apache because there's no web site translation in Slovak. - We've alleviated the problem by including sk in the Apache config files, - but as usual, changes don't propagate to all of the mirrors fast. - -<toc-add-entry name="mirroring">Mirroring issues</toc-add-entry> - - <p>Sites are supposed to create the file mirror/timestamps/<host>. - Jay has made scripts that check the date in this file for each mirror so - we can know when a mirror is out of date, see mirror/timestamps/*.py. - - <p>We should reduce the number of web mirrors in Europe and increase the - number of mirrors on other, less connected continents. - - <p>Making all mirrors pushed (from www-master if possible) is also a goal. - - <p>Making sure whether each mirror has correct Apache configuration is a - pain, but there doesn't seem to be a way around that. Phil Hands suggested - that the "AddLanguage" stuff is put into a wgettable file and that we make - a Perl script that would automatically update people's Apache config - files. - - <P>All links into the archive should allow the user to select the download - site. The master mirror list could be used to keep the list of mirrors up - to date (maybe even using a script). See - <code>webwml/english/mirror/Mirrors.masterlist</code> and - <code>webwml/english/mirror/mirror_list.pl</code> files. - - <P><em>The mirror list is maintained by the people at mirrors@debian.org.</em> - -<toc-add-entry name="wrongurls">Wrong URLs</toc-add-entry> - - <p>Links to external pages have to be checked if they are still - correct. James Treacy has written a small Python script for this - purpose. Frank Lichtenheld is currently - maintaining the script, the (daily updated) results can be found at - <url "https://www-master.debian.org/build-logs/urlcheck/" />. - Broken links have to be removed. This is more of a permanent task.</p> - -<toc-add-entry name="misc">Miscellaneous requests</toc-add-entry> - - <p><strong>Deal with these as you wish.</strong></p> - - <P>If we had cgi.debian.org on a less used and faster host, we could have - more dynamic content on the web pages. - - <p>Javier suggested making DDP pages account for translations, - automatically. - - <p>Joey said: -<blockquote> -<p>I'd rather like to see a note on the security pages like:</p> - -<p> - Please note that we cannot guarantee that an intruder gets access to - our servers since they are connected to the internet. In such a - case an evil third party could potential modify uploads to - security.debian.org and modify web pages containing MD5 sums. We - are, however, trying our best to prohibit this. Please be advised - that there is no 100% security, only improvements to the current - situation. -</p> -</blockquote> - -<p>Joey should rephrase it probably. :)</p> - - <p>Should be added to /security/faq.</p> - - <p>"Vernon Balbert" <vbalbert@mediaone.net> suggested we make it - clear which kernel version is used in the latest version of Debian. - - <p>Matti Airas <mairas@iki.fi> suggested "doing language selection - with Apache mod_rewrite. Instead of having to explicitly go to - https://www.debian.org/intro/about.en.html (or some mirror), I could go to - https://www.debian.org/en/intro/about, which mod_rewrite then could replace - with the correct url." Note that this would require additional hacks in - order not to break relative links.</p> - - - <p>Chris Tillman suggested:</p> - -<blockquote> -<p>There is often confusion about which machines -Debian supports and which we don't, yet. There is a bewildering array of -machines, not to mention network cards, displays, mice, video cards, sound -cards, port types, and so forth which an individual system might -mix-and-match. Many of the Ports pages are out of date. - -<p>Debian supports a *lot* of systems. I think it would make sense to start -trying to list which ones, specifically. Also, it would be really nice to -know which ones aren't supported, both for new would-be users and for -developers as a todo list. - -<p>I think the easiest way to achieve this, would be to provide a web page -where people could enter in their system components, preferably chosen from -a list of known components with an 'other' capability. Then, they could also -enter a thumbs-up or thumbs-down, on Debian on that architecture. Also any -specific problems. - -<p>Then after submission of the user's hardware specs, the system can show a -(dated) list of previous user's experiences with those components. - -<p>We should also need to sprinkle pointers to this page into the install -documentation, FAQs, probably even put a link on the front Debian page. -</blockquote> - -<toc-add-entry name="bugs">Bug reports</toc-add-entry> - -<p><a href="https://bugs.debian.org/www.debian.org">The list of our bug -reports</a>. - -<hr> - -<p>Please submit anything else to -<a href="mailto:debian-www@lists.debian.org">our mailing list</a>. diff --git a/greek/devel/website/translating.wml b/greek/devel/website/translating.wml deleted file mode 100644 index 227e9c8caca..00000000000 --- a/greek/devel/website/translating.wml +++ /dev/null @@ -1,312 +0,0 @@ -#use wml::debian::template title="Translating Debian web pages" BARETITLE=true -#use wml::fmt::verbatim -#use wml::debian::translation-check translation="8627b3f6f68ecae195c89923923955f8e32ea092" maintainer="galaxico" - -<p>To make the job of the translators as easy as possible the pages are -generated a bit differently than many of you will be used to. The web pages -are actually generated using source that is marked up with -<a href="https://www.shlomifish.org/open-source/projects/website-meta-language/"><tt>wml</tt></a>. -There are separate directories for each language. -</p> - -<p>If you plan to start an entirely new translation of the Debian web site, -please see the <a href="#completenew">section on starting a new -translation</a>. -</p> - -<h2><a name="singlepages">Translating individual pages</a></h2> - -<p>We use WML to separate the specific content of a page from the elements -common to multiple pages. This means that one needs to edit certain WML -source files instead of HTML files. Please <a href="using_git">use Git</a> -to acquire the current sources. You'll need to check out at least two -directories: <tt>webwml/english/</tt> and <tt>webwml/<var><language></var>/</tt>.</p> - -<p>To translate a single page from English into your language, the original -.wml file needs to be translated and placed within the other language's -directory. The relative path and name need to be the same as in the English -directory in order for the links to continue to work.</p> - -<h3>Translation headers</h3> -<p>It is strongly -recommended that the translator adds an additional line to the headers -after the last <code>#use</code> statement to record the exact commit of -the original file that was translated, so that <a href="uptodate">updating is -easier</a>. The line looks like this: -<kbd>#use wml::debian::translation-check translation="<var><git_commit_hash></var>"</kbd> -Please note that if you generate the translatable file using <tt>copypage.pl</tt> -tool (which is highly recommended), the git commit hash will be generated -automatically. The usage of <tt>copypage.pl</tt> will be explained in the -following texts. -</p> - -<p>Some translation teams also use this line to mark the official -translator of each web page. Doing so, you will get automatic mails -when the pages you maintain are updated in English, and need your -attention to update the translation. For that, simply add your name as -maintainer at the end of the <code>#use</code> line to make it look -like this: -<kbd>#use wml::debian::translation-check translation="<var>git_commit_hash</var>" maintainer="<var>your name</var>"</kbd>. -The <tt>copypage.pl</tt> will do this automatically -if you set the <tt>DWWW_MAINT</tt> environment variable -or use the <tt>-m</tt> command-line switch. -</p> - -# I Removed cvs specific descriptions from here because of cvs to git transition. -# Help to update instruction if possible. -# -#<p>You also need to explain to the robot who you are, how often you -#want to get automatic mails and their content. For that, edit (or let -#your coordinator edit) the file -#webwml/<var>language</var>/international/<var>language</var>/translator.db.pl -#in the repository. The syntax should be quite understandable, and you can -##use the file of the French team as template if it does not exist for -#your language yet. The robot can send several kinds of information, and -#for each of them, you can choose the frequency at which it will be -#sent to you. The different kinds of information are: -#</p> - -#<ul> -# <li><b>summary</b>: a summary of which documents are outdated</li> -# <li><b>logs</b>: the "cvs log" between the translated and current versions</li> -# <li><b>diff</b>: "cvs diff"</li> -# <li><b>tdiff</b>: the script will try to find the part of the translated text modified by the English patch</li> -# <li><b>file</b>: add the current version of the file to translate</li> -#</ul> - -#<p>Then, for each of them, the value should be one of: 0 (never), 1 (monthly), 2 (weekly) or 3 (daily).</p> - -#<p>An example could be: -#</p> - -#<verbatim> -# 'Martin Quinson' => { -# email => 'martin.quinson@tuxfamily.org', -# summary => 3, -# logs => 3, -# diff => 3, -# tdiff => 0, -# file => 0 -# }, -#</verbatim> - -<p>The header of the web page can be easily produced by using the -<tt>copypage.pl</tt> script in the webwml root directory. The script -will copy the page to the right place, create directories and -makefiles if necessary, and add the required header automatically. -You will be warned if a page to be copied exists in the repository, whether -because the page was removed from the repository (due to it being -too out of date) or because somebody already committed a translation -and your local repository copy is not up to date. -</p> - -<p>In order to start using the <tt>copypage.pl</tt> you should first -configure the file <tt>language.conf</tt> in the <tt>webwml</tt> root directory, -which it will use to -determine the language you are translating to. That file needs up to -two lines: the first line gets the language name (like <tt>german</tt>) and -the second can optionally get the name of the maintaining translator. You can also -set the language through the use of the <tt>DWWW_LANG</tt> environment -variable and use the <tt>DWWW_MAINT</tt> environment variable to -put your name so that it will be added to the header of the wml -files generated as the maintainer for the translation. Or as a third possibility, -you can give language and (optionally) maintainer on the commandline via -<tt>-l german -m "Donald Duck"</tt> and not use the language.conf file at all. -There are other features -available in the script, just run it without any arguments to get the help. -</p> - -<p>After you have run e.g. <kbd>./copypage.pl <var>file</var>.wml</kbd>, -translate the original text within the file. Comments in files will indicate -if there are items that should not be translated; respect them. Don't do any -unnecessary changes to the formatting; if something needs to be fixed, it -should likely be done in the original file.</p> - -<h3>Page building and publishing</h3> - -<p>Since we use <a href="content_negotiation">content negotiation</a>, -HTML files are not named <tt><var>file</var>.html</tt> but -<tt><var>file</var>.<var><lang></var>.html</tt>, where <var><lang></var> -is the two letter code of the language, according to -<a href="https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes">ISO 639</a> -(e.g. <tt>fr</tt> for French).</p> - -<p>You can build HTML from WML by running -<kbd>make <var>file</var>.<var><lang></var>.html</kbd>. -If that works, check if the syntax is fully valid with -<kbd>weblint <var>file</var>.<var><lang></var>.html</kbd>.</p> - -<p>NOTE: The web pages are regularly rebuilt automatically on the -www-master server, based on the wml source in git. This process is for -the most part impervious to errors. However, if you commit a broken -file in the top level of your translation (e.g. the top-level -index.wml file), it will break the build process and stall all the -other updates to the web site. Please pay special attention to these -files.</p> - -<p>Once the page is good to go, you can commit it into Git. If you -have the permissions to do this yourself, please push the commits to -the <a href="https://salsa.debian.org/webmaster-team/webwml">webwml -git repository</a>; if not, send it to <a -href="translation_coordinators"> somebody with write access to the -repository</a>.</p> - -<h2><a name="completenew">Starting a new translation</a></h2> - -<p>If you would like to start translation of the Debian web pages into -a new language, send us e-mail (in English) at -<a href="mailto:webmaster@debian.org">webmaster@debian.org</a>. - -<p>First of all, clone our source tree, as described <a -href="using_git">on our Git introduction page</a>.</p> - -<p>After you have a git checkout, start by creating a new top level -directory for your translation, next to english/ and others. The name -of the translation directory must be in English and entirely lowercase -(e.g. "german", not "Deutsch").</p> - -<p>Copy the <tt>Make.lang</tt> and <tt>.wmlrc</tt> files from the english/ -directory to the new translation directory. These files are essential for -building your translation from WML files. They have been designed so that -after you copy them to the new language directory, you only have to change -these things:</p> - -<ol> - <li>The variable LANGUAGE must be changed in the file <tt>Make.lang</tt>. - - <li>The variables CUR_LANG, CUR_ISO_LANG and CHARSET must be changed in - the <tt>.wmlrc</tt> file. Add CUR_LOCALE to that, if you need it for - sorting. - - <li>Some languages may need extra processing to handle the charset. This - can be done using the --prolog and --epilog options to wml. Use the - WMLPROLOG and WMLEPILOG variables in <tt>Make.lang</tt> to do this. - - <li>The variable LANGUAGES must be changed in top-level - <tt>webwml/Makefile</tt> file so that your language will get built - along with the other ones, on www.debian.org. We would prefer if you - left this particular change up to the webmasters, because you may not - be aware that your translation is broken when checked out of VCS - afresh, which could break the building process of the rest of our web - site. -</ol> - -<p>After that is done, put the following line in a new file called -"Makefile" in that directory: - -<pre> -<protect>include $(subst webwml/<var>yourlanguagedir</var>,webwml/english,$(CURDIR))/Makefile</protect> -</pre> - -<p>(Replace <var>yourlanguagedir</var> with the name of your language's -directory, of course.)</p> - -<p>Now create a subdirectory inside your language's directory called "po", -and copy the same Makefile to that subdirectory (<kbd>cp ../Makefile .</kbd>). -</p> - -<p>In the po/ directory, run <kbd>make init-po</kbd> to generate the initial -set of *.po files.</p> - -<p>Now that you have the skeleton set up, you can start -adding your translations in our shared WML tags used in templates. -The first templates that you should translate are those that appear -on all of the web pages, like the header keywords, the entries in the -navigation bar, and the footer.</p> - -# The page on <a href="using_wml">using WML</a> has more information on this. - -<p>Start translating in the <code>po/templates.<var>xy</var>.po</code> file -(where <var>xy</var> is your language's two-letter code). For every -<code>msgid "<var>something</var>"</code> there is initially a -<code>msgstr ""</code> where you should fill in the translation of -<var>something</var> in the double quotes after <code>msgstr</code>.</p> - -<p>You don't have to translate all of the strings in all of the .po files, -just those that your currently translated pages actually need. To see if you -need to translate a string, see the comments in the .po file just above each -<code>msgid</code> statement. If the referenced file is in -<tt>english/template/debian</tt>, then you should most likely translate it. -If not, you can postpone it for later, when you actually translate the -relevant section of the web pages that require it.</p> - -<p>The point of po/ files is to make things easier for translators, so that -they (almost) never have to edit anything in the -<tt>english/template/debian</tt> directory itself. -If you find anything to be wrong with the way something -is set up in the template directory, please make sure that the problem is -fixed in a general manner (feel free to ask someone else to do it for you), -rather than commiting actual translations into the templates, which would -(usually) be a major problem.</p> - -<p>If you aren't sure if you did something properly, ask on the debian-www -mailing list before committing.</p> - -<p>Note: if you find you need to make any other changes, send mail to -debian-www saying what you changed and why, so the problem can be corrected. - -<p>After the template skeleton is done, you can start with translating the -front page and the other *.wml files. For a list of files that -should be translated first, check <a href="translation_hints">the hints -page</a>. Translate *.wml pages as described <a href="#singlepages">at -the top of this page</a>.</p> - -<h3>Reviving outdated translations</h3> - -<p>As described in <a href="uptodate">how to keep translations up to date</a>, -outdated translations of the website might be removed automatically when a -long period of time has gone by without an update.</p> - -<p>If you find that some files got removed sometime in the past and you would -like to checkout the file again for further editing, you may search through -the commit history using git's standard commands.</p> - -<p>For example, if the delete file is "deleted.wml", you may search the history -by running:</p> - -<verbatim> - git log --all --full-history -- <path/to/file/deleted.wml> -</verbatim> - -<p>You may find out the exact commit that removed the file you want, together -with the commit's hash string. To display the detail information about the -modification made to the file in this commit, you may -use <code>git show</code> subcommand:</p> - -<verbatim> - git show <COMMIT_HASH_STRING> -- <path/to/file/deleted.wml> -</verbatim> - -<p>If the commit is exactly the one that deleted the file, you may restore -the file to the workspace using <code>git checkout</code>:</p> - -<verbatim> - git checkout <COMMIT_HASH_STRING>^ -- <path/to/file/deleted.wml> -</verbatim> - -<p>Once you do this you have to, of course, update the document before -you check it in again. Or it might be otherwise removed.</p> - - -<h3>The rest of the story</h3> - -<p>The description above will probably be enough to get you started. -Afterwards, you will want to refer to the following documents which provide -more detailed explanations and additional useful information.</p> - -<ul> -<li>A number of <a href="examples">examples</a> are provided to give you - a clearer idea of how to get started. -<li>A number of common questions are answered and helpful hints provided in - the <a href="translation_hints">translation hints</a> page. -<li>We have mechanisms in place to aid in <a href="uptodate">keeping the - translations up to date</a>. -<li>To see the status of your translation and how it compares to others, - check the <a href="stats/">statistics</a>. -</ul> - -<P>We hope you find the work we've done will make translating -the pages as easy as possible. As has already been mentioned, if -you have any questions, you can ask them on the <a -href="mailto:debian-www@lists.debian.org">debian-www</a> mailing -list. diff --git a/greek/devel/website/translation_hints.wml b/greek/devel/website/translation_hints.wml deleted file mode 100644 index eb9edff683e..00000000000 --- a/greek/devel/website/translation_hints.wml +++ /dev/null @@ -1,174 +0,0 @@ -#use wml::debian::template title="Useful Translation Suggestions" -#include "$(ENGLISHDIR)/releases/info" -#use wml::debian::translation-check translation="d49333f670c2639f601fd741d3dd5f060de97e2b" maintainer="galaxico" - -<p>Please see the pages about <a href="working">working on the web pages</a> -which describe some general things to observe, not strictly limited to -translations. - -<h2>What to translate?</h2> - -<p>See the <a href="translating#completenew">instructions for starting a new -translation</a> for an introduction.</p> - -<p>Once you start translating pages, we recommend you start with pages -that users are most likely to visit. Here are some guidelines; also -note that the lists of pages in the <a href="stats/">translation -statistics</a> are ordered by popularity.</p> - -<dl> -<dt><strong>Most important:</strong></dt> - <dd> - <ul> - <li>the main directory: index.wml, contact.wml, donations.wml, - social_contract.wml, support.wml</li> - <li>the intro/ directory: about.wml, cn.wml, free.wml, why_debian.wml</li> - <li>the releases/ directory: index.wml</li> - <li>the releases/<current_release_name>/ directory: index.wml, - installmanual.wml, releasenotes.wml</li> - <li>the distrib/ directory: index.wml, packages.wml, netinst.wml, ftplist.wml</li> - <li>the mirror/ directory: list.wml</li> - <li>the CD/ directory: index.wml</li> - <li>the doc/ directory: index.wml</li> - <li>the MailingLists/ directory: index.wml</li> - <li>the security/ directory: index.wml</li> - </ul> - </dd> -<dt><strong>Standard:</strong></dt> - <dd>The remaining files in the aforementioned directories, and these: - <ul> - <li>Bugs/index.wml, Bugs/Reporting.wml</li> - <li>banners/index.wml</li> - <li>blends/index.wml</li> - <li>consultants/index.wml</li> - <li>doc/ddp.wml</li> - <li>events/index.wml</li> - <li>international/index.wml, and create a page (or directory) for your - language</li> - <li>logos/index.wml</li> - <li>mirror/index.wml</li> - <li>misc/index.wml</li> - <li>News/index.wml</li> - <li>News/weekly/index.wml</li> - <li>ports/index.wml</li> - <li>partners/index.wml</li> - </ul> - </dd> -<dt><strong>Optional:</strong></dt> - <dd>All the other files in the previously mentioned directories. - This includes the following directories which include subdirectories that - are modified frequently, so are harder to keep up to date: - <ul> - <li>MailingLists/desc/</li> - <li>News/</li> - <li>doc/books.wml</li> - <li>events/</li> - <li>security/</li> - </ul> - </dd> -<dt><strong>Least Important:</strong></dt> - <dd>Files in the devel/ and vote/ directories. Since they are mostly - for developers, and the primary language of developers is English, it - is only when you have a strong translation team should you attempt to - tackle these.</dd> -</dl> - -<p> -<strong>It is important that you only translate files that you have -the time to maintain. A few well maintained pages is much more useful -than a lot of out of date ones.</strong> - -<h2>How closely should translations follow the original?</h2> - -<p>There are times when you may want to make a change to the content when -you are translating. One example is on the support page; you will probably -want to include an example on subscribing to the language specific mailing -list, e.g. debian-user-french on the French version of the pages. - -<p>If you make more significant changes, please notify -<a href="mailto:debian-www@lists.debian.org">debian-www list</a> -as it is desired to keep the content as similar as possible -between the different versions. - -<p>The pages are meant to be useful. If you have information that -will help the users of your language, feel free to add it. You can use -international/<Language>.wml for all the stuff interesting to -Language-speaking visitors. - -<p>If you know of information that would be useful to all users, -bring it up on debian-www. - -<h2>How do translators know when files need to be updated?</h2> - -<P>There is a mechanism that translators can use to <a href="uptodate"> -keeping web site translations up-to-date</a>. - -<h2>How do we keep the gettext template translations up to date?</h2> - -<p>After the English files have been updated, run <kbd>make update-po</kbd> -in the <code>po/</code> subdirectory of your translation to update your .po -files with the originals. Watching the log messages on the -<a href="https://lists.debian.org/debian-www-cvs/">debian-www-cvs mailing -list</a> can be helpful to find out when this should be done; or you can -simply run it at regular intervals.</p> - -<p>Use the <kbd>make stats</kbd> command to see an overview of the changes. -Gettext will mark the tags whose value it had to guess with -"<code>#, fuzzy</code>", and newly introduced tags will simply have an empty -string after <code>msgstr</code>.</p> - -<h2>How do users know if a translated page is out of date?</h2> - -<P>The <code>translation-check</code> template which is used to -<a href="uptodate">keep translations up-to-date</a> will make a note in -translations which are outdated. - -<h2>Things to observe when translating</h2> - -<p>The following is a list of pages and directories that may require special -attention when translating: - -<dl> -<dt><tt>News/</tt> - <dd>You can translate as many or as few pieces of news as you wish. The - indices are created automatically from the titles of the items. If an - item has been translated, then the translated title will be used in the - index.</dd> - -<dt><tt>security/</tt> - <dd>This is set up similar to the News/ directory. There's one - difference, there are .data files that you should <em>not</em> translate.</dd> - -<dt><tt>CD/vendors/</tt> - <dd>Only the *.wml files in CD/vendors/ should be translated. - Translations for tags are added via gettext in the - po/vendors.<var>xy</var>.po file.</dd> - -<dt><tt>intro/organization.wml</tt> - <dd>Tags are translated via gettext in the - po/organization.<var>xy</var>.po file.</dd> - -<dt><tt>MailingLists/{un,}subscribe.wml</tt> - <dd>These two files are generated by the <tt>mklist</tt> script, so you - can't edit them directly. You can translate the files in the desc/ - subdirectory, they contain the descriptions of mailing lists. - Tags are translated via gettext in the po/mailinglists.<var>xy</var>.po - file. - </dd> - -<dt><tt>consultants/index.wml</tt> - <dd>Tags are translated via gettext in the po/consultants.<var>xy</var>.po - file.</dd> - -<dt><tt>releases/*/{installmanual,releasenotes}.wml</tt> - <dd>Translate everything but the Perl code (stuff enclosed in <: :>), - except for the <strong>second</strong> argument of permute_as_list.</dd> - -<dt><tt>ports/</tt> - <dd>Port pages may be volatile. You should only translate these if - you are willing to spend the time keeping them up to date.</dd> - -<dt><tt>devel/website/</tt> - <dd>This is for people editing or translating web pages, so it is - probably very low priority.</dd> -</dl> diff --git a/greek/devel/website/uptodate.wml b/greek/devel/website/uptodate.wml deleted file mode 100644 index f3eb75b01b5..00000000000 --- a/greek/devel/website/uptodate.wml +++ /dev/null @@ -1,103 +0,0 @@ -#use wml::debian::template title="Keeping web site translations up-to-date" -#use wml::debian::translation-check translation="8f2dd37edbf6287df4029e3f234798efbcce2862" maintainer="galaxico" - -<P>Since web pages aren't static, it is a good idea to keep track of which -version of the original a certain translation refers to, and to use this -information to check which pages have changed since the last translation. -This information should be embedded at the top of the document (though -below any other "use" headers) in this form: - -<pre> -\#use wml::debian::translation-check translation="git_commit_hash" -</pre> - -<p>where <var>git_commit_hash</var> is the git commit hash that refers -to the commit of the original (English) file that the translated file -was translated against. You can get the detail of that specific commit -using the <code>git show</code> tool: <code>git show -<git_commit_hash></code> . If you use the <kbd>copypage.pl</kbd> -script in the webwml directory, the <code>translation-check</code> -line is added automatically in the first version of your translated -page, pointing to the version of the original file that exists at that -point. </p> - -<p>Some translations may not get updated for quite some time, even -though the original language (English) has changed. Due to content -negotiation, the reader of the translated page may not be aware of -this and might miss important information, introduced in new versions -of the original. The <code>translation-check</code> template contains -code to check if your translation is outdated, and output an -appropriate message warning the user about it. </p> - -<P>There are more parameters that you can use on the -<code>translation-check</code> line: - -<dl> - <dt><code>original="<var>language</var>"</code> - <dd>where <var>language</var> is the name of the language you are translating - from, if not english. - The name must correspond to the top-level subdirectory in the VCS, and to - the name in <code>languages.wml</code> template. - - <dt><code>mindelta="<var>number</var>"</code> - <dd>which defines the maximum difference in git revisions before the - translation is considered to be <strong>aged</strong>. The default - value is <var>1</var>. For less important pages, set it to - <var>2</var>, meaning that two changes need to be made before the - translation will be considered aged. - - <dt><code>maxdelta="<var>number</var>"</code> - <dd>which defines the maximum differenc in git revisions before the - translation is considered to be <strong>outdated</strong>. The - default value is <var>5</var>. For very important pages, set it to a - smaller number. A value of <var>1</var> means that every change will - cause the translation to be marked as outdated. -</dl> - -<p>Tracking the age of translations also enables us to have <a -href="stats/">translation statistics</a>, a report of outdated -translations (together with helpful links to the differences between -files), along with a list of pages that haven't been translated at -all. This is intended to help translators and to attract new people to -help. </p> - -<p> -To avoid presenting our users with information that is too outdated, -translations that have not been updated within six months from when the -original page was changed will be purged automatically. -Please see the -<a href="https://www.debian.org/devel/website/stats/">list of outdated -translations</a> to find which pages are in danger of being purged. -</p> - -<P>Additionally, the script <kbd>check_trans.pl</kbd> is available in the -webwml/ directory, which will show you a report on pages needing updates: - -<pre> -check_trans.pl <var>language</var> -</pre> - -<P>where <var>language</var> is the directory name that contains your -translation, e.g. "swedish". - -<P>Pages that lack translation will be shown as -"<code>Missing <var>filename</var></code>", and pages that are not up to -date with the original will be shown as -"<code>NeedToUpdate <var>filename</var> to version <var>XXXXXXX</var></code>". - -<P>If you want to see what the exact changes are, you can get the -differences by adding <kbd>-d</kbd> command line option to the above -command.</p> - -<P>If you want to ignore warnings about missing translations (for -instance for old news items), you can create a file called -<code>.transignore</code> in the directory where you want to suppress -the warnings, listing each file that you are not going to translate, -with one name per line. - -<p> -A similar script for keeping track of the translations of the mailing lists -descriptions is also available. -Please read the comments in the <code>check_desc_trans.pl</code> script for -documentation. -</p> diff --git a/greek/devel/website/using_git.wml b/greek/devel/website/using_git.wml deleted file mode 100644 index aaa809a9316..00000000000 --- a/greek/devel/website/using_git.wml +++ /dev/null @@ -1,311 +0,0 @@ -#use wml::debian::template title="Using git to manipulate website source code" -#use wml::debian::translation-check translation="74a4415fa07f5810685f1d0568bf4b695cc931b3" maintainer="galaxico" - -<h2>Introduction</h2> - -<p>Git is a <a href="https://en.wikipedia.org/wiki/Version_control">version -control system</a> that helps to manage having multiple people work on -the same material simultaneously. Every user can hold a local copy of a main -repository. The local copies can be on the same machine, or across the world. -Users can then modify the local copy as they wish and when the modified -material is ready, commit the changes and push them back to the main -repository.</p> - -<p>Git will not let you push a commit directly if the remote repository has -any newer commits (modifications) than your local copy on the same branch. -In such case where conflict takes place, please fetch and update your local -copy first and <code>rebase</code> your new modifications on top of the latest -commit as needed. -</p> - -<h3><a name="write-access">Git repository write access</a></h3> - -<p> -The whole Debian website source code is managed under Git. It is located -at <url https://salsa.debian.org/webmaster-team/webwml/>. By default, -guests are not allowed to push commits onto the source code repository. -You will need some kind of permission to gain write access to the -repository. -</p> - -<h4><a name="write-access-unlimited">Unlimited write access</a></h4> -<p> -If you need unlimited write access to the repository (e.g., You are about to -become a frequent contributor), please consider requesting write access via -the <url https://salsa.debian.org/webmaster-team/webwml/> web interface after -logging in to Debian's Salsa platform. -</p> - -<p> -If you are new to Debian's website development and have no previous experience, -please also send a mail to <a href="mailto:debian-www@lists.debian.org"> -debian-www@lists.debian.org</a> with your self introduction before requesting -unlimited write access. Please provide with something useful in your -introduction, like which language or which part of the website you plan to -work on, and who would vouch for you. -</p> - -<h4><a name="write-access-via-merge-request">Write into repository via Merge Requests</a></h4> -<p> -If you do not intend to get unlimited write access to the repository or -is unable to do so, you can always submit a Merge Request and let other -developers to review and accept your work. Please submit Merge Requests -using the standard procedure as provided by the Salsa GitLab platform via -its web interface (read -<a href="https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html">Project forking workflow</a> -and -<a href="https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html#when-you-work-in-a-fork">When you work in a fork</a> -for details). -</p> - -<p> -The Merge Requests are not monitored by all website developers thus it may -not always be processed in time. If you are not sure whether your contribution -would be accepted, please send a email to the -<a href="https://lists.debian.org/debian-www/">debian-www</a> -mailing list and request for a review. -</p> - -<h2><a name="work-on-repository">Working on the repository</a></h2> - -<h3><a name="get-local-repo-copy">Get a local copy of the repository</a></h3> - -<p>First, you need to install git to work with the repository. Next, -configure your user and e-mail details on your computer (please refer -to general git documentation to learn how to do this). Then, you can -clone the repository (in other words, make a local copy of it) -in one of two ways.</p> - -<p>The recommended way to work on webwml is to first register an -account on salsa.debian.org and enable git SSH access by uploading an -SSH public key into your salsa account. See the <a -href="https://salsa.debian.org/help/user/ssh.md">salsa help -pages</a> for more details on how to do that. Then you can clone the -webwml repository using the following command:</p> - -<pre> - git clone git@salsa.debian.org:webmaster-team/webwml.git -</pre> - -<p>If you don't have a salsa account, an alternative method is to -clone the repository using the HTTPS protocol:</p> - -<pre> - git clone https://salsa.debian.org/webmaster-team/webwml.git -</pre> - -<p>This will give you the same repository copy locally, but you will -not be able to directly push changes back directly this way.</p> - -<p>Cloning the whole webwml repository will require downloading about -500MB of data, thus it may be difficult for those with slow or -unstable Internet connections. You may try shallow cloning with -a minimum depth first for a smaller initial download:</p> - -<pre> - git clone git@salsa.debian.org:webmaster-team/webwml.git --depth 1 -</pre> - -<p>After obtaining a usable (shallow) repository, you can deepen the -local shallow copy and eventually convert it to a full local -repository: </p> - -<pre> - git fetch --deepen=1000 # deepen the repo for another 1000 commits - git fetch --unshallow # fetch all missing commits, convert the repo to a complete one -</pre> - -<h4><a name="partial-content-checkout">Partial content checkout</a></h4> - -<p>You can create a checkout for only a subset of the pages like this:</p> - -<pre> - $ git clone --no-checkout git@salsa.debian.org:webmaster-team/webwml.git - $ cd webwml - $ git config core.sparseCheckout true - In webwml: Create the file .git/info/sparse-checkout with content like this - (if you only want the base files, English, Catalan and Spanish translations): - /* - !/[a-z]*/ - /english/ - /catalan/ - /spanish/ - Then: - $ git checkout -- -</pre> - -<h3><a name="submit-changes">Submitting local changes</a></h3> - -<h4><a name="keep-local-repo-up-to-date">Keep your local repo up-to-date</a></h4> - -<p>Every few days (and definitely before starting some editing work!) -you should do a</p> - -<pre> - git pull -</pre> - -<p>to retrieve any files from the repository which have changed.</p> - -<p> -It is strongly recommended to keep your local git working directory clean -before performing "git pull" and following editing work. If you have -uncommitted changes or local commits that are not present in the remote -repository on the current branch, doing "git pull" will automatically create -merge commits or even fail due to conflicts. Please consider keeping your -unfinished work in another branch or using commands like "git stash". -</p> - -<p>Note: git is a distributed (not centralised) version control -system. This means that when you commit changes they will only be -stored in your local repository. To share them with others, you will -also need to push your changes to the central repository on salsa.</p> - -<h4><a name="example-edit-english-file">Example on editing English files</a></h4> - -<p> -An example on how to edit English files within the website source code -repository is provided here. After obtaining a local copy of the repo -using "git clone" and before starting the editing work, run the following -command: -</p> - -<pre> - $ git pull -</pre> - -<p>Now make changes to files. When you are done, commit your changes -to your local repository using:</p> - -<pre> - $ git add path/to/file(s) - $ git commit -m "Your commit message" -</pre> - -<p>If you have unlimited write access to the remote webwml repository, you -may now push your changes directly onto the Salsa repo:</p> - -<pre> - $ git push -</pre> - -<p>If you do not have direct write access to the webwml repository, please -consider submitting your changes using the Merge Request function as provided -by Salsa GitLab platform or asking other developers for help. -</p> - -<p>That's a very basic summary of how to use git to manipulate the -Debian website's source code. For more information on git, please read -git's documentation.</p> - -<h4><a name="closing-debian-bug-in-git-commits">Closing Debian bugs in git commits</a></h4> - -<p> -If you include <code>Closes: #</code><var>nnnnnn</var> in your commit log -entry, then bug number <code>#</code><var>nnnnnn</var> will be closed -automatically when you push your changes. The precise form of this is the same as -<a href="$(DOC)/debian-policy/ch-source.html#id24">in Debian policy</a>.</p> - -<h4><a name="links-using-http-https">Linking using HTTP/HTTPS</a></h4> - -<p>Many Debian websites support SSL/TLS, so please use HTTPS links where -possible and sensible. <strong>However</strong>, some -Debian/DebConf/SPI/etc websites either don't have have HTTPS support -or only use the SPI CA (and not an SSL CA trusted by all browsers). To -avoid causing error messages for non-Debian users, please do not link -to such sites using HTTPS.</p> - -<p>The git repository will reject commits containing plain HTTP links -for Debian websites that support HTTPS or containing HTTPS links for -the Debian/DebConf/SPI websites that are known to either not support -HTTPS or use certificates signed only by SPI.</p> - -<h3><a name="translation-work">Working on translations</a></h3> - -<p>Translations should always be kept to be up-to-date with its -corresponding English file. The "translation-check" header in translation -files is used to track which version of English file the current -translation was based on. If you change translated files, you need to update the -translation-check header to match the git commit hash of the -corresponding change in the English file. You can find that hash -with</p> - -<pre> -$ git log path/to/english/file -</pre> - -<p>If you do a new translation of a file, please use the <q>copypage.pl</q> script -and it will create a template for your language, including the correct -translation header.</p> - -<h4><a name="translation-smart-change">Translation changes with smart_change.pl</a></h4> - -<p><code>smart_change.pl</code> is a script designed to make it easier -to update original files and their translations together. There are -two ways to use it, depending on what changes you are making.</p> - -<p>To use <code>smart_change</code> to just update the translation-check -headers when you're working on files manually:</p> - -<ol> - <li>Make the changes to the original file(s), and commit</li> - <li>Update translations</li> - <li>Run smart_change.pl - it will pick up the changes and update - headers in the translated files</li> - <li>Review the changes (e.g. with "git diff")</li> - <li>Commit the translation changes</li> -</ol> - -<p>Or, if you're using smart_change with a regular expression to make -multiple changes across files in one pass:</p> - -<ol> - <li>Run <code>smart_change.pl -s s/FOO/BAR/ origfile1 origfile2 ...</code></li> - <li>Review the changes (e.g. with <code>git diff</code>) - <li>Commit the original file(s)</li> - <li>Run <code>smart_change.pl origfile1 origfile2</code> - (i.e. <strong>without the regexp</strong> this time);it will now - just update headers in the translated files</li> - <li>Finally, commit the translation changes</li> -</ol> - -<p>This is more involved than the previous one (needing two commits), but -unavoidable due to the way git commit hashes work.</p> - -<h2><a name="notifications">Getting notifications</a></h2> - -<h3><a name="commit-notifications">Receiving commit notifications</a></h3> - -<p>We have configured the webwml project in Salsa so that commits are -shown in the IRC channel #debian-www.</p> - -<p>If you want to receive notifications via e-mail when there are -commits in the webwml repo, please subscribe to the <q>www.debian.org</q> -pseudopackage via tracker.debian.org and activate the <q>vcs</q> keyword -there, following these steps (only once):</p> - -<ul> - <li>Open a web browser and go to <url https://tracker.debian.org/pkg/www.debian.org></li> - <li>Subscribe to the <q>www.debian.org</q> pseudopackage. (You can authenticate - via SSO or register an email and password, if you were not using - tracker.debian.org already for other purposes).</li> - <li>Go to <url https://tracker.debian.org/accounts/subscriptions/>, then to <q>modify - keywords</q>, check <q>vcs</q> (if it's not checked) and save.</li> - <li>From now on you will get e-mails when somebody commits to the - webwml repo. We will add the other webmaster-team repositories soon.</li> -</ul> - -<h3><a name="merge-request-notifications">Receiving Merge Request notifications</a></h3> - -<p> -If you wish to receive notification emails whenever there are new Merge -Requests submitted on the webwml repository web interface on Salsa GitLab -platform, you may configure your notification settings for the webwml -repository on the web interface, following these steps: -</p> - -<ul> - <li>Log in to your Salsa account and go to the project page;</li> - <li>Click the bell icon on the top of the project homepage;</li> - <li>Select the notification level you prefer.</li> -</ul> diff --git a/greek/devel/website/using_wml.wml b/greek/devel/website/using_wml.wml deleted file mode 100644 index 469285f4338..00000000000 --- a/greek/devel/website/using_wml.wml +++ /dev/null @@ -1,68 +0,0 @@ -#use wml::debian::template title="Using WML" -#use wml::debian::translation-check translation="24a8bbc5bf2fd2fbe025f0baa536bf1126f83723" maintainer="galaxico" - -<p>WML stands for web site meta language. This means that WML takes input -.wml files, processes whatever is inside them (it can be anything from basic -HTML to Perl code!), and outputs whatever you want it to output, for example -.html or .php.</p> - -<p>The documentation for WML is not easy to learn from. It is actually quite -complete, but until you begin to understand how it works (and it is quite -powerful) it is easiest to learn from examples. You may find template files -used for the Debian site useful. They can be found in -<code><a href="https://salsa.debian.org/webmaster-team/webwml/tree/master/english/template/debian">\ -webwml/english/template/debian/</a></code>.</p> - -<p>This assumes that you have WML installed on your machine. -WML is available as a -<a href="https://packages.debian.org/wml">Debian package</a>. - - -<h2>Editing WML sources</h2> - -<p>One thing all .wml files will have is one or more opening <code>#use</code> -lines. You must not change or translate their syntax, only the quoted -strings such as those after <code>title=</code>, which would change the -<title> element in the output files.</p> - -<p>Other than the header lines, most of our .wml pages contain simple HTML. -If you encounter tags such as <define-tag> or <: ... :>, be -careful, because those delimit code that's processed by one of WML's special -passes. See below for more information.</p> - - -<h2>Building Debian web pages</h2> - -<p>Simply type <kbd>make</kbd> in webwml/<lang>. We have set up -makefiles that call <kbd>wml</kbd> with all the right arguments.</p> - -<p>If you do a <kbd>make install</kbd> then the HTML files will be built and -placed in the directory <kbd>../../www/</kbd>.</p> - - -<h2>Extra WML features we use</h2> - -<p>One of the features of WML that we make extensive use of is the use of Perl. -Remember, these are not dynamic pages. Perl is used at the time the HTML -pages are generated to do, well, whatever you like. Two good examples of how -we are using Perl in the pages is to create the list of most recent news items for -the main page and to generate the links to translations at the end of the page. - -# TODO: add the basic stuff from webwml/english/po/README here - -<p>To rebuild the templates of our web site, wml version >= 2.0.6 is -needed. To rebuild the gettext templates for non-English translations, -mp4h >= 1.3.0 is necessary.</p> - - -<h2>Specific issues with WML</h2> - -<p>Multi-byte languages may need special pre- or post-processing of the .wml -files in order to handle the character set properly. This can be done by -changing the variables <kbd>WMLPROLOG</kbd> and <kbd>WMLEPILOG</kbd> in -<kbd>webwml/<lang>/Make.lang</kbd> appropriately. Depending on how -your <kbd>WMLEPILOG</kbd> program works, you may need to change the value of -<kbd>WMLOUTFILE</kbd>. -<br> -See the Japanese or Chinese translations for an example. -</p> diff --git a/greek/devel/website/working.wml b/greek/devel/website/working.wml deleted file mode 100644 index 3375273338b..00000000000 --- a/greek/devel/website/working.wml +++ /dev/null @@ -1,253 +0,0 @@ -#use wml::debian::template title="How to work on the Debian web pages" BARETITLE=true -#use wml::debian::toc -#use wml::debian::translation-check translation="b5c35a479efa1910b978df5114fd87e4142e3892" maintainer="galaxico" - -<toc-display/> - - - -<toc-add-entry name="general">General information</toc-add-entry> - -<h3>Resource requirements</h3> - -<p>If you want to work on our web site, please be prepared to store at least -740 MB of data on your disk. This reflects the current size of the source -archive. If you (accidentally) rebuild all of the pages, you will need at -least three times as much space.</p> - -<h3><q>What are these lines beginning with `#'?</q></h3> - -<p>In WML, a line beginning with a `#' is a comment. These are preferred to -normal HTML comments as they don't show up on the final page.</p> - -<p>Please read the page on <a href="using_wml">using WML</a> for more -information on WML.</p> - -<toc-add-entry name="etiquette">Etiquette for editors</toc-add-entry> - -<h3><q>Can I modify this page?</q></h3> - -<p>That depends. If you see a small mistake, like a typo, just fix it.</p> - -<p>If you notice that some bit of information is missing, feel free to fix -it, too.</p> - -<p>If you feel that something is awful and needs to be rewritten, bring it -up on debian-www so it can be discussed. We'll probably agree with you.</p> - -<p>If you notice there's a problem in a template (i.e. a file in -webwml/english/template/debian directory), please think about the change -before committing it, because changes to templates often cause large portions -of the site to get rebuilt.</p> - -<h3>When adding new directories, also add the Makefile!</h3> - -<p>Some care should be taken when adding a new directory to git. If the -current directory is listed in ../Makefile then you <b>must</b> create a -Makefile in it — otherwise <tt>make</tt> will give an error message.</p> - -<h3>Use clear and simple English</h3> - -<p>Since the Debian web pages are read by non-native speakers of English -and are translated into other languages, it is best to write in clear and -simple English and avoid the use of slang, emoticons and obscure idioms. -</p> - -<p>If you do use any of this, add a comment to the file explaining the -meaning.</p> - -<p> -If any doubt, or in order to proofread your proposal, please contact the <a -href="mailto:debian-l10n-english@lists.debian.org">English localization team</a>. -</p> - -<h3>Look for READMEs</h3> - -<p>Some of the directories contain a README to help you understand -how that directory is organized. These should provide any special -information needed when working in that area.</p> - -<h3>Separate the changes in content from the changes in formatting</h3> - -<p>Always make separate patches or commits for content changes and for -changes in formatting. When they are combined, it's much harder for -translators to find the differences. If you run <kbd>git diff -u</kbd> with -such mixed changes, you can see the mess for yourself.</p> - -<p>In general, avoid random formatting changes. Making older parts of pages -XHTML/XML-compliant shouldn't be done in the same commit with other changes. -(New stuff can and should be done properly from the start, of course.)</p> - - -<h3>Update translations, too, if possible</h3> - -<p>Some changes are independent of the language used in a WML file, like -changes to URLs or embedded Perl code. Fixing typos also falls in the same -category, because translators have usually ignored them while translating. -With such language-independent changes, you can do the same change in -all the translated files without actually knowing the other languages, -and safely increase the version in the translation-check headers.</p> - -<p>It's not terribly hard for translators to do the same work themselves, -and it can be inconvenient for English-speaking editors to have a full -checkout in which to operate. However, we still encourage people to do this -in order to avoid bothering two dozen people for something that can be done -quickly by a single person.</p> - -<p>In addition, to make such changes easier to apply, you can use the -<a href="using_git#translation-smart-change"><code>smart_change.pl</code></a> -script from the top-level directory in the webwml git module.</p> - -<toc-add-entry name="links">Links</toc-add-entry> - -<h3><q>This link doesn't look right. Should I change it?</q></h3> - -<p>Because of the way the web servers are set up (using -<a href="content_negotiation">content negotiation</a>), -you should not have to change any of the internal links. -In fact we suggest you don't. Write to debian-www -if you feel a link is incorrect before changing it.</p> - -<h3>Fixing links</h3> - -<p>If you notice a link to an external web site results in a redirection -(301, 302, a <meta> redirect, or a page saying <q>This page has moved.</q>) -please tell debian-www about it.</p> - -<p>If you find a broken link (404, 403, or a page that's not what the link -says it is), please fix it and tell debian-www about it so translators are -aware. Even better, fix the link in all the other translations, and update -translation-check headers if possible.</p> - -<toc-add-entry name="special">Separation of text from data</toc-add-entry> - -<h3><q>What are these foo.def and foo.data files?</q></h3> - -<p>To make it easier to keep the translations up to date, we separate the -generic parts (data) from the textual parts (text) of some pages. The -translators only need to copy and translate the textual parts of those, the -generic parts will be added automatically.</p> - -<p>An example may help in understanding this. It takes several files to -generate the page of vendor listings in <code>CD/vendors</code>:</p> - -<dl> - <dt><code>index.wml</code>:</dt> - <dd>The text at the top of the vendors page is in this file. - A translated copy of this should be placed in each language directory.</dd> - <dt><code>vendors.CD.def</code>:</dt> - <dd>This contains all the pieces of text which are needed for each - vendor entry. Translations are added via - <code><<var>language</var>>/po/vendors.<var>xy</var>.po</code>.</dd> - <dt><code>vendors.CD</code>:</dt> - <dd>This file contains the actual vendor entries which are independent - on the language, so a translator doesn't need to touch this file.</dd> -</dl> - -<p>When one of the people behind <email "cdvendors@debian.org"> adds a -new vendor, they add it to <code>debiancd.db</code>, convert it into WML -format as <code>vendors.CD</code> (using <code>getvendors.pl</code>), -and then let WML and the makefiles do their magic. All the translations -get rebuilt using the existing translated text but with the new vendor -data. (An updated translation for free!)</p> - -<toc-add-entry name="newpage">Adding a new page</toc-add-entry> - -<p>Adding new pages to Debian is quite easy. All the work of getting the -header and footer right are done using WML. All you need to do is to include -a line such as the following at the top of the new file:</p> - -<pre><protect> -#use wml::debian::template title="TITLE OF PAGE" -</protect></pre> - -<p>followed by the body. All pages should use the -<code>wml::debian::template</code> template file unless they are using -a special one created just for that section, e.g. the News or security items.</p> - -<p>The templates we have allow you to define certain variables which will -affect the pages created. This should avoid having to create different -templates for every situation and allow improvements to be easier to -implement. The variables currently available and their purpose are:</p> - -<dl> -<dt>BARETITLE="true"</dt> - <dd>Removes the "Debian --" part that is usually prepended - to all the <title> tags.</dd> -<dt>NOHEADER="true"</dt> - <dd>Removes the initial header from the page. A custom header - can, of course, be included in the body.</dd> -<dt>NOMIRRORS="true"</dt> - <dd>Removes the mirror dropdown list from the page. It is generally - not recommended to be used, except for a handful of pages.</dd> -<dt>NOHOMELINK="true"</dt> - <dd>Removes the link back to the main Debian page, which is normally - added to the bottom of the page.</dd> -<dt>NOLANGUAGES="true"</dt> - <dd>Removes the links to versions in other languages, which are - normally added to the bottom of the page.</dd> -<dt>GEN_TIME="true"</dt> - <dd>Sets the date on the resulting files to the timestamp of the - generated files, instead of the timestamp of the source file.</dd> -<dt>NOCOPYRIGHT="true"</dt> - <dd>Removes the copyright notice at the bottom of the page.</dd> -</dl> - -<p>Note that you can use any string as the value of these variables, -<q>true</q>, <q>yes</q>, <q>foo</q>, it doesn't matter.</p> - -<p>An example of the use of this is in the ports pages which have -their own headers. <code>ports/arm/index.wml</code> uses:</p> - -<pre><protect> -#use wml::debian::template title="ARM Port" NOHEADER="yes" -</protect></pre> - -<p>If you want to do something that can't be done using the existing -templates, first consider extending one of them. If it isn't -possible to extend one in a backward compatible way, try to make -the new template a superset of an existing one so the pages can -be converted to it at the next major upgrade (hopefully never more -than every 6 months).</p> - -<p>If you are creating a page that is generated by a script or has -little prose, consider using the <gettext> tags to ease -the task of keeping translations up to date.</p> - -# think of a good example for <gettext> in new pages - -<toc-add-entry name="inclusion">Including other files</toc-add-entry> - -<p>If you want to separate some parts of your page into a distinct file - (which is then included by your main file) use - the extension <code>.src</code> if your file contains content which should - be translated because then your included file is tracked for changes as - any ordinary <code>.wml</code> file. If you use any other extension, like - <code>.inc</code>, translators will not notice your updates and different - languages might ship different content.</p> - -<toc-add-entry name="newdir">Adding a new directory</toc-add-entry> - -<p>Note: do <strong>not</strong> create a directory with the name -<code>install</code>. This confuses make and the pages in that directory -will not be updated automatically.</p> - -<p>Below is an annotated example of adding a new directory to the web site. -</p> -<pre> - mkdir foo - git add foo - cd foo - cp ../intro/Makefile . - git add Makefile -</pre> - -<p>Edit the Makefile in the parent directory and add the directory you just -created to the <code>SUBS</code> variable. This will add the directory to -the build for when make is run.</p> - -<p>Finally, commit all the changes just made to the repository with -</p> -<pre> - git commit Makefile foo -</pre> diff --git a/greek/devel/wnpp/Makefile b/greek/devel/wnpp/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/devel/wnpp/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/devel/wnpp/being_adopted.wml b/greek/devel/wnpp/being_adopted.wml deleted file mode 100644 index 0cc0dd3bca7..00000000000 --- a/greek/devel/wnpp/being_adopted.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages currently being adopted" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="being_adopted_byage">by age</a> or -<a href="being_adopted_byactivity">by activity</a>. -</p> - -<being_adopted /> - -<p> -This list is also available organized -<a href="being_adopted_byage">by age</a> or -<a href="being_adopted_byactivity">by activity</a>. -</p> diff --git a/greek/devel/wnpp/being_adopted_byactivity.wml b/greek/devel/wnpp/being_adopted_byactivity.wml deleted file mode 100644 index 5fab1cd913e..00000000000 --- a/greek/devel/wnpp/being_adopted_byactivity.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages currently being adopted, organized by activity" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="being_adopted">by package name</a> or -<a href="being_adopted_byage">by age</a>. -</p> - -<being_adopted_byactivity /> - -<p> -This list is also available organized -<a href="being_adopted">by package name</a> or -<a href="being_adopted_byage">by age</a>. -</p> diff --git a/greek/devel/wnpp/being_adopted_byage.wml b/greek/devel/wnpp/being_adopted_byage.wml deleted file mode 100644 index 46c24790ed6..00000000000 --- a/greek/devel/wnpp/being_adopted_byage.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages currently being adopted, organized by age" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="being_adopted">by package name</a> or -<a href="being_adopted_byactivity">by activity</a>. -</p> - -<being_adopted_byage /> - -<p> -This list is also available organized -<a href="being_adopted">by package name</a> or -<a href="being_adopted_byactivity">by activity</a>. -</p> diff --git a/greek/devel/wnpp/being_packaged.wml b/greek/devel/wnpp/being_packaged.wml deleted file mode 100644 index 045f950378d..00000000000 --- a/greek/devel/wnpp/being_packaged.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages being worked on" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="being_packaged_byage">by age</a> or -<a href="being_packaged_byactivity">by activity</a>. -</p> - -<being_packaged /> - -<p> -This list is also available organized -<a href="being_packaged_byage">by age</a> or -<a href="being_packaged_byactivity">by activity</a>. -</p> diff --git a/greek/devel/wnpp/being_packaged_byactivity.wml b/greek/devel/wnpp/being_packaged_byactivity.wml deleted file mode 100644 index 9b0a1d58531..00000000000 --- a/greek/devel/wnpp/being_packaged_byactivity.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages being worked on, organized by activity" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="being_packaged">by package name</a> or -<a href="being_packaged_byage">by age</a>. -</p> - -<being_packaged_byactivity /> - -<p> -This list is also available organized -<a href="being_packaged">by package name</a> or -<a href="being_packaged_byage">by age</a>. -</p> diff --git a/greek/devel/wnpp/being_packaged_byage.wml b/greek/devel/wnpp/being_packaged_byage.wml deleted file mode 100644 index 5eb4c22c5d2..00000000000 --- a/greek/devel/wnpp/being_packaged_byage.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages being worked on, organized by age" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="being_packaged">by package name</a> or -<a href="being_packaged_byactivity">by activity</a>. -</p> - -<being_packaged_byage /> - -<p> -This list is also available organized -<a href="being_packaged">by package name</a> or -<a href="being_packaged_byactivity">by activity</a>. -</p> diff --git a/greek/devel/wnpp/help_requested.wml b/greek/devel/wnpp/help_requested.wml deleted file mode 100644 index 3cb8788c953..00000000000 --- a/greek/devel/wnpp/help_requested.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages for which help was requested" GEN_TIME="true" -#use wml::debian::translation-check translation="2e1044712299f75aac55782c35ffe2ebce9eb3e5" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="help_requested_byage">by age</a> or -<a href="help_requested_bypop">by popularity</a>. -</p> - -<help_req /> - -<p> -This list is also available organized -<a href="help_requested_byage">by age</a> or -<a href="help_requested_bypop">by popularity</a>. -</p> diff --git a/greek/devel/wnpp/help_requested_byage.wml b/greek/devel/wnpp/help_requested_byage.wml deleted file mode 100644 index 17a800b8661..00000000000 --- a/greek/devel/wnpp/help_requested_byage.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages for which help was requested, organized by age" GEN_TIME="true" -#use wml::debian::translation-check translation="2e1044712299f75aac55782c35ffe2ebce9eb3e5" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="help_requested">by package name</a> or -<a href="help_requested_bypop">by popularity</a>. -</p> - -<help_req_byage /> - -<p> -This list is also available organized -<a href="help_requested">by package name</a> or -<a href="help_requested_bypop">by popularity</a>. -</p> diff --git a/greek/devel/wnpp/help_requested_bypop.wml b/greek/devel/wnpp/help_requested_bypop.wml deleted file mode 100644 index f5f97cfe720..00000000000 --- a/greek/devel/wnpp/help_requested_bypop.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages for which help was requested, organized by popularity" GEN_TIME="true" -#use wml::debian::translation-check translation="2e1044712299f75aac55782c35ffe2ebce9eb3e5" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="help_requested">by package name</a> or -<a href="help_requested_byage">by age</a>. -</p> - -<help_req_bypop /> - -<p> -This list is also available organized -<a href="help_requested">by package name</a> or -<a href="help_requested_byage">by age</a>. -</p> diff --git a/greek/devel/wnpp/index.wml b/greek/devel/wnpp/index.wml deleted file mode 100644 index 495834a1949..00000000000 --- a/greek/devel/wnpp/index.wml +++ /dev/null @@ -1,384 +0,0 @@ -#use wml::debian::template title="Work-Needing and Prospective Packages" -#use wml::debian::toc -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" -#use wml::debian::translation-check translation="ff76decf22b833c8b721fc40392935030d5f2a2b" maintainer="galaxico" - -<define-tag toc-title-formatting endtag=required><h3>%body</h3></define-tag> - -<p>Work-Needing and Prospective Packages, WNPP for short, is a list -of packages in need of new maintainers and prospective packages in Debian. -In order to closely track the real status of such things, WNPP is currently -operated as a pseudo-package in the <a href="https://bugs.debian.org/">Debian -Bug Tracking System (BTS)</a>.</p> - -<hrline /> - -<p><a href="work_needing">Packages in need of a new maintainer</a>: -</p> -<ul> - <li> - <a href="rfa_bypackage"><rfa_number> packages up for adoption</a>, - organized <a href="rfa_bymaint">by maintainer</a> - or <a href="rfa_byage">by age</a> - </li> - <li> - <a href="orphaned"><orphaned_number> orphaned packages</a>, - organized <a href="orphaned_byage">by age</a> - </li> - <li> - <a href="being_adopted"><adopted_number> packages currently being adopted</a>, - organized <a href="being_adopted_byage">by age</a> - or <a href="being_adopted_byactivity">by activity</a> - </li> -</ul> - -<p> -<a href="help_requested"><help_number> packages in need of help</a>, -organized <a href="help_requested_byage">by age</a> -or <a href="help_requested_bypop">by popularity</a> -</p> - -<p><a href="prospective">Prospective packages</a>:</p> -<ul> - <li> - <a href="being_packaged"><packaged_number> packages being worked on</a>, - organized <a href="being_packaged_byage">by age</a> - or <a href="being_packaged_byactivity">by activity</a> - </li> - <li> - <a href="requested"><requested_number> requested packages</a>, - organized <a href="requested_byage">by age</a> - </li> -</ul> - - -<p>Note: these lists are updated six times a day; for more up-to-date information -please check the <a href="https://bugs.debian.org/wnpp">wnpp pseudo package</a> -entry in the BTS.</p> - -<p>You can search the above information by package, description or type -on the <a href="https://wnpp.debian.net">WNPP search</a> website.</p> - -<p>You can browse the above information broken down into various categories -(based on <a href="https://debtags.debian.org/">debtags</a>) on the -<a href="https://wnpp-by-tags.debian.net">WNPP-by-tags</a> website.</p> - -<hrline /> - -<h2>Using WNPP</h2> - -<toc-display /> - -<p>Since it uses the BTS, every developer is already familiar with the -technical details, such as submission of new information, modification of -information or closing of pending requests. On the other hand, in order to -achieve the highest level of automatization, some procedures have to be -observed.</p> - -<p>In order to submit new information, a bug has to be filed against the -<a href="https://bugs.debian.org/wnpp">wnpp pseudo package</a> for each -(prospective) package that is affected. Please note that you should -only submit one bug per source package rather than one bug for each -binary package built from a source package.</p> - - -<toc-add-entry>Adding new entries with <q>reportbug</q></toc-add-entry> - -<p>You can use <a href="https://packages.debian.org/reportbug">reportbug</a> -(<kbd>apt-get install reportbug</kbd>):</p> - -<samp> - $ reportbug --email <var>username@domain.tld</var> wnpp<br /> - Using '<var>Your Name <username@domain.tld></var>' as your from address.<br /> - Getting status for wnpp...<br /> - Querying Debian bug tracking system for reports on wnpp<br /> - (Use ? for help at prompts.)<br /> - ...<br /> -</samp> - -<p>You will see a list of reported bugs against WNPP which you -should read to prevent a second report for the same package.</p> -<p>After the buglist you are asked for the request type:</p> - -<samp> -What sort of request is this?<br /> -<br /> -1 ITP This is an <q>Intent To Package</q>. Please submit a package description<br /> - along with copyright and URL in such a report.<br /> -<br /> -2 O The package has been <q>Orphaned</q>. It needs a new maintainer as soon<br /> - as possible.<br /> -<br /> -3 RFA This is a <q>Request for Adoption</q>. Due to lack of time, resources,<br /> - interest or something similar, the current maintainer is asking for<br /> - someone else to maintain this package. They will maintain it in<br /> - the meantime, but perhaps not in the best possible way. In short:<br /> - the package needs a new maintainer.<br /> -<br /> -4 RFH This is a <q>Request For Help</q>. The current maintainer wants to continue<br /> - to maintain this package, but he/she needs some help to do this, because<br /> - his/her time is limited or the package is quite big and needs several<br /> - maintainers.<br /> -<br /> -5 RFP This is a <q>Request For Package</q>. You have found an interesting piece<br /> - of software and would like someone else to maintain it for Debian.<br /> - Please submit a package description along with copyright and URL in<br /> - such a report.<br /> -<br /> -Choose the request type: <br /> -</samp> - -<p>After your selection you will be asked for the package name:</p> - -<samp> -Choose the request type: <var>x</var><br /> -Please enter the proposed package name: <var>PACKAGENAME</var><br /> -Checking status database...<br /> -</samp> - -<ul> -<li><p>If your request type is ITP (1) or RFP (5) you are asked for a short - description and then for some information about the package:</p> - -<samp> -Please briefly describe this package; this should be an appropriate short -description for the eventual package:<br /> -> <var>A DESCRIPTION</var><br /> -<br /> -Subject: ITP: <var>PACKAGENAME -- A DESCRIPTION</var><br /> -Package: wnpp<br /> -Version: N/A; reported 2002-01-30<br /> -Severity: wishlist<br /> -<br /> -* Package name : <var>PACKAGENAME</var><br /> - Version : <var>x.y.z</var><br /> - Upstream Author : <var>Name <somebody@some.org></var><br /> -* URL : <var>http://www.some.org/</var><br /> -* License : <var>(GPL, LGPL, BSD, MIT/X, etc.)</var><br /> - Description : <var>A DESCRIPTION</var><br /> -<br /> -<br /> --- System Information<br /> -...<br /> -</samp> - -<p>Below the <q>Description</q> line you should give more information -about the package.</p></li> - -<li><p>If your request type is O (2) or RFA (3) you have to enter the name -of the package.</p> - -<samp> -Choose the request type: <var>x</var><br /> -Please enter the name of the package: <var>PACKAGENAME</var><br /> -Checking status database...<br /> -<br /> -Subject: O: <var>PACKAGENAME -- SHORT DESCRIPTION</var><br /> -Package: wnpp<br /> -Version: N/A; reported 2002-01-30<br /> -Severity: normal<br /> -<br /> -<br /> -<br /> --- System Information<br /> -...<br /> -</samp> - -<p>You should add some information about maintaining the package, the upstream -situation and maybe a reason why you want to give the package away.</p></li> - -</ul> - -<p>Then you are asked if you want to send your request:</p> - -<samp> -Report will be sent to Debian Bug Tracking System <submit@bugs.debian.org><br /> -Submit this bug report (e to edit) [Y|n|i|e|?]? <br /> -</samp> - - -<toc-add-entry>Adding new entries via email</toc-add-entry> - -<p>It is also possible to report reports/bugs against the WNPP via email. -The format of the submission should be like this:</p> - -<samp> - To: submit@bugs.debian.org<br /> - Subject: <var>TAG</var>: <var>package name</var> -- <var>short package description</var><br /> - <br /> - Package: wnpp<br /> - Severity: <var>see below</var><br /> - <br /> - <var>Some information about the package.</var> (If this is an ITP or RFP a URL - where the package (either the .deb or the original source) can be downloaded - from is required, as well as - information concerning its license.) -</samp> - -<p>The tags to be used and their corresponding severities are:</p> - -<table> -<colgroup span="3"> -<col width="10%"> -<col width="10%"> -<col width="80%"> -</colgroup> -<tr> - <th valign="top"><a name="tag-o">O</a></th> - <td valign="top"><em>normal</em></td> - <td>The package has been <q>Orphaned</q>. It needs a new maintainer - as soon as possible. If the package has a Priority higher or equal to - standard, the severity should be set to important. - </td> -</tr> -<tr> - <th valign="top"><a name="tag-rfa">RFA</a></th> - <td valign="top"><em>normal</em></td> - <td>This is a <q>Request for Adoption</q>. Due to lack of time, - resources, interest or something similar, the current maintainer is - asking for someone else to maintain this package. They will maintain - it in the meantime, but perhaps not in the best possible way. - In short: the package needs a new maintainer. - </td> -</tr> -<tr> - <th valign="top"><a name="tag-rfh">RFH</a></th> - <td valign="top"><em>normal</em></td> - <td>This is a <q>Request For Help</q>. The - current maintainer wants to continue to maintain this package, - but they need some help to do this, because their time is limited - or the package is quite big and needs several maintainers. - </td> -</tr> -<tr> - <th valign="top"><a name="tag-itp">ITP</a></th> - <td valign="top"><em>wishlist</em></td> - <td>This is an <q>Intent To Package</q>. Please submit a package - description along with copyright and URL in such a report. - </td> -</tr> -<tr> - <th valign="top"><a name="tag-rfp">RFP</a></th> - <td valign="top"><em>wishlist</em></td> - <td>This is a <q>Request For Package</q>. Someone has found an - interesting piece of software and would like someone else to maintain - it for Debian. Please submit a package description along with - copyright and URL in such a report. - </td> -</tr> -</table> - - -<toc-add-entry>Removing entries</toc-add-entry> - -<p>The procedures for closing these bugs are as follows: -</p> - -<table> -<colgroup span="2"> -<col width="10%"> -<col width="90%"> -</colgroup> -<tr> - <th valign="top"><a name="howto-o">O</a></th> - <td>If you are going to adopt a package, retitle its bug - to replace <q>O</q> with <q>ITA</q>, in order for other people to know the - package is being adopted and to prevent its automatic removal from the - archive, and set yourself as the owner of the bug. - To actually adopt the package, upload it with your name in - its Maintainer: field, and put something like - <code> - * New maintainer (Closes: #<var>bugnumber</var>) - </code> - in the changelog of the package in order to automatically close this - bug once the package has been installed; where <var>bugnumber</var> - has to be replaced with the corresponding bugreport number. - Furthermore, before you - actually upload a new package with you as the maintainer, you should - check if there is a new upstream release and you should try to fix the - outstanding bugs. - </td> -</tr> -<tr> - <th valign="top"><a name="howto-rfa">RFA</a></th> - <td><p>If you are going to adopt a package, retitle its bug - to replace <q>RFA</q> with <q>ITA</q>, in order for other people to know the - package is being adopted and to prevent its automatic removal from the - archive, and set yourself as the owner of the bug. - To actually adopt the package, upload it with your name in - its Maintainer: field, and close this bug once the package has been - installed. - </p> - - <p>If you as the package maintainer decide to orphan the package you - marked with <q>RFA</q>, please retitle the bug report and replace <q>RFA</q> - with <q>O</q>. If you withdraw your request, please close the bug.</p> - </td> -</tr> -<tr> - <th valign="top"><a name="howto-rfh">RFH</a></th> - <td><p>Normally this bug should only closed by the - submitter, i.e. the package maintainer, if they consider it - obsolete, either because one or more people have offered - (and provided) their support or because they now think that - they can handle the package for themself. - </p> - - <p>If you as the package maintainer decides to change the RFH to - a request for adoption (<q>RFA</q>) or if you want to - orphan the package (<q>O</q>), please retitle the bug - instead of closing it and filing a new one.</p> - </td> -</tr> -<tr> - <th valign="top"><a name="howto-itp">ITP</a></th> - <td><p>package the software, upload it and close this bug once - the package has been installed. - </p> - - <p>If you change your mind, and no longer want to package this, either - close the bug or retitle and reclassify it as RFP, as you see fit.</p> - - <p>If you encounter problems with packaging the program (for example it - depends on another, not-yet-packaged program which you don't have - time to package), you might want to record these problems - as additional information in the ITP, so that it is clear what's going on with - your packaging efforts.</p> - </td> -</tr> -<tr> - <th valign="top"><a name="howto-rfp">RFP</a></th> - <td>If you are going to package this, retitle the bug report - to replace <q>RFP</q> with <q>ITP</q>, in order for other people to know the - program is already being packaged, and set yourself as the owner of - the bug. Then package the software, upload it and close this bug once - the package has been installed. - </td> -</tr> -</table> - -<p>If you feel that the developers' mailing list should know about your ITP, -RFA or anything else, add the header</p> -<pre>X-Debbugs-CC: debian-devel@lists.debian.org</pre> -<p>to the message.</p> - -<p>Of course, the easiest way of closing these bugs is to include an entry -in the package changelog saying what you've done and append -<tt>(closes: bug#nnnnn)</tt> to it. This way the bug will be closed -automatically after the new package gets installed into the archive.</p> - -<p> -<strong>Attention:</strong> if you need to reassign, retitle, or set the -owner of bug reports, you must do so by emailing the BTS control bot -<a href="$(HOME)/Bugs/server-control">directly</a> or by emailing the report -number @bugs.debian.org and using -<a href="$(HOME)/Bugs/Reporting#control">Control pseudo-headers</a>, -but <strong>not</strong> by filing new reports. -</p> - -<p>Note: if a package remains orphaned for a very long time, we will examine -the situation to determine if the package is needed anymore — if not, -the FTP maintainers will be asked to remove the package from unstable.</p> - -<p>If for some reason you need to contact the WNPP maintainers, they can be -reached at <email wnpp@debian.org>.</p> diff --git a/greek/devel/wnpp/orphaned.wml b/greek/devel/wnpp/orphaned.wml deleted file mode 100644 index 222c6150ddc..00000000000 --- a/greek/devel/wnpp/orphaned.wml +++ /dev/null @@ -1,16 +0,0 @@ -#use wml::debian::template title="Orphaned packages" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="orphaned_byage">by age</a>. -</p> - -<orphaned /> - -<p> -This list is also available organized -<a href="orphaned_byage">by age</a>. -</p> diff --git a/greek/devel/wnpp/orphaned_byage.wml b/greek/devel/wnpp/orphaned_byage.wml deleted file mode 100644 index 36632902bd3..00000000000 --- a/greek/devel/wnpp/orphaned_byage.wml +++ /dev/null @@ -1,16 +0,0 @@ -#use wml::debian::template title="Orphaned packages, by age" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="orphaned">by package name</a>. -</p> - -<orphaned_byage /> - -<p> -This list is also available organized -<a href="orphaned">by package name</a>. -</p> diff --git a/greek/devel/wnpp/prospective.wml b/greek/devel/wnpp/prospective.wml deleted file mode 100644 index b5c5029e162..00000000000 --- a/greek/devel/wnpp/prospective.wml +++ /dev/null @@ -1,10 +0,0 @@ -#use wml::debian::template title="Prospective packages" GEN_TIME="true" -#use wml::debian::translation-check translation="f49611cb55aa09fd5351490070f08bc13071863c" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<h3>Packages being worked on</h3> -<being_packaged /> - -<h3>Requested packages</h3> -<requested /> diff --git a/greek/devel/wnpp/requested.wml b/greek/devel/wnpp/requested.wml deleted file mode 100644 index 8803a594dc5..00000000000 --- a/greek/devel/wnpp/requested.wml +++ /dev/null @@ -1,16 +0,0 @@ -#use wml::debian::template title="Requested packages" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="requested_byage">by age</a>. -</p> - -<requested /> - -<p> -This list is also available organized -<a href="requested_byage">by age</a>. -</p> diff --git a/greek/devel/wnpp/requested_byage.wml b/greek/devel/wnpp/requested_byage.wml deleted file mode 100644 index 55920baf1b1..00000000000 --- a/greek/devel/wnpp/requested_byage.wml +++ /dev/null @@ -1,16 +0,0 @@ -#use wml::debian::template title="Requested packages, organized by age" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="requested">by package name</a>. -</p> - -<requested_byage /> - -<p> -This list is also available organized -<a href="requested">by package name</a>. -</p> diff --git a/greek/devel/wnpp/rfa_byage.wml b/greek/devel/wnpp/rfa_byage.wml deleted file mode 100644 index 2e985b77d80..00000000000 --- a/greek/devel/wnpp/rfa_byage.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages up for adoption, organized by age" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="rfa_bypackage">by package name</a> or -<a href="rfa_bymaint">by maintainer</a>. -</p> - -<rfa_byage /> - -<p> -This list is also available organized -<a href="rfa_bypackage">by package name</a> or -<a href="rfa_bymaint">by maintainer</a>. -</p> diff --git a/greek/devel/wnpp/rfa_bymaint.wml b/greek/devel/wnpp/rfa_bymaint.wml deleted file mode 100644 index 0fd14f83da7..00000000000 --- a/greek/devel/wnpp/rfa_bymaint.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages up for adoption, organized by maintainer" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="rfa_bypackage">by package name</a> or -<a href="rfa_byage">by age</a>. -</p> - -<rfa_bymaint /> - -<p> -This list is also available organized -<a href="rfa_bypackage">by package name</a> or -<a href="rfa_byage">by age</a>. -</p> diff --git a/greek/devel/wnpp/rfa_bypackage.wml b/greek/devel/wnpp/rfa_bypackage.wml deleted file mode 100644 index 41a2478ee7d..00000000000 --- a/greek/devel/wnpp/rfa_bypackage.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Packages up for adoption" GEN_TIME="true" -#use wml::debian::translation-check translation="9c91dafe36ecc3ea323c52c9c21d02f91dca4751" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<p> -This list is also available organized -<a href="rfa_bymaint">by maintainer</a> or -<a href="rfa_byage">by age</a>. -</p> - -<rfa_bypackage /> - -<p> -This list is also available organized -<a href="rfa_bymaint">by maintainer</a> or -<a href="rfa_byage">by age</a>. -</p> diff --git a/greek/devel/wnpp/unable-hdate.wml b/greek/devel/wnpp/unable-hdate.wml deleted file mode 100644 index 898f35651be..00000000000 --- a/greek/devel/wnpp/unable-hdate.wml +++ /dev/null @@ -1,28 +0,0 @@ -#use wml::debian::template title="Unable to be packaged: hdate" -#use wml::debian::translation-check translation="6f3adf6374f35194686f89dec2ba66b1ecf3bb5f" maintainer="galaxico" - -<h3>hdate — Prints Hijra (Islamic lunar) dates, calendar, Islamic prayer times</h3> - -<p>This package contains more than one licence -and they stand in conflict with each other.</p> - -<p>The source archive contains file licensed under the <a -href="https://www.gnu.org/copyleft/gpl.html">GNU General Public -License</a> (GPL) but some source files also contain the following -note:</p> - -<pre> - * Permission for nonprofit use and redistribution of this software and - * its documentation is hereby granted without fee, provided that the - * above copyright notice appear in all copies and that both that - * copyright - * notice and this permission notice appear in supporting - * documentation. -</pre> - -<p>The author says that he is not prepared to re-release the entire -software under the GPL and explicitly asserts that the software is -available for use without charge for non-profit use only.</p> - -<p>This problem has been discussed in <a -href="https://bugs.debian.org/225537">Bug#225537</a>.</p> diff --git a/greek/devel/wnpp/work_needing.wml b/greek/devel/wnpp/work_needing.wml deleted file mode 100644 index 25153bf5fa0..00000000000 --- a/greek/devel/wnpp/work_needing.wml +++ /dev/null @@ -1,13 +0,0 @@ -#use wml::debian::template title="Packages in need of a new maintainer" GEN_TIME="true" -#use wml::debian::translation-check translation="f49611cb55aa09fd5351490070f08bc13071863c" maintainer="galaxico" - -#include "$(ENGLISHDIR)/devel/wnpp/wnpp.data" - -<h3>Packages up for adoption</h3> -<rfa_bypackage /> - -<h3>Packages up for adoption, by maintainer</h3> -<rfa_bymaint /> - -<h3>Orphaned packages</h3> -<orphaned /> diff --git a/greek/doc/cvs.wml b/greek/doc/cvs.wml deleted file mode 100644 index 2cd21dcf44e..00000000000 --- a/greek/doc/cvs.wml +++ /dev/null @@ -1,2 +0,0 @@ -#use wml::debian::redirect newpage="vcs" -#use wml::debian::translation-check translation="63b253e9f683a3e51632a8be03911a02d53a936e" maintainer="galaxico" diff --git a/greek/doc/ddp.wml b/greek/doc/ddp.wml deleted file mode 100644 index 9a75834a3f0..00000000000 --- a/greek/doc/ddp.wml +++ /dev/null @@ -1,40 +0,0 @@ -#use wml::debian::ddp title="Debian Documentation Project" -#use wml::debian::translation-check translation="60eea6916091f1a3a9240f472ebea1904c32d0bd" maintainer="galaxico" - -<p>The Debian Documentation Project was formed to coordinate and unify all -efforts to write more and better documentation for the Debian system.</p> - - <h2>DDP Work</h2> -<div class="line"> - <div class="item col50"> - - <h3>Manuals</h3> - <ul> - <li><strong><a href="user-manuals">Users' manuals</a></strong></li> - <li><strong><a href="devel-manuals">Developers' manuals</a></strong></li> - <li><strong><a href="misc-manuals">Miscellaneous manuals</a></strong></li> - </ul> - - </div> - - <div class="item col50 lastcol"> - - <h3>Documentation Policy</h3> - <ul> - <li>Manual licenses comply with DFSG.</li> - <li>We use Docbook XML for our documents.</li> - <li>The sources should be at <a href="https://salsa.debian.org/ddp-team">https://salsa.debian.org/ddp-team</a></li> - <li><tt>www.debian.org/doc/<manual-name></tt> will be the official URL</li> - <li>Every document should be actively maintained.</li> - <li>Please ask on <a href="https://lists.debian.org/debian-doc/">debian-doc</a> if you like to write a new document</li> - </ul> - - <h3>Git Access</h3> - <ul> - <li><a href="vcs">How to access</a> the git repositories of the DDP</li> - </ul> - - </div> - - -</div> diff --git a/greek/doc/devel-manuals.wml b/greek/doc/devel-manuals.wml deleted file mode 100644 index 6843855eebf..00000000000 --- a/greek/doc/devel-manuals.wml +++ /dev/null @@ -1,263 +0,0 @@ -#use wml::debian::ddp title="Debian Developers' Manuals" -#include "$(ENGLISHDIR)/doc/manuals.defs" -#include "$(ENGLISHDIR)/doc/devel-manuals.defs" -#use wml::debian::translation-check translation="78f856f0bff4125a68adb590b66952d97f183227" maintainer="galaxico" - -<document "Debian Policy Manual" "policy"> - -<div class="centerblock"> -<p> - This manual describes the policy requirements for the Debian GNU/Linux - distribution. This includes the structure and contents of the Debian - archive, several design issues of the operating system, as well as - technical requirements that each package must satisfy to be included - in the distribution. - -<doctable> - <authors "Ian Jackson, Christian Schwarz, David A. Morris"> - <maintainer "The Debian Policy group"> - <status> - ready - </status> - <availability> - <inpackage "debian-policy"> - <inddpvcs-debian-policy> - <p><a href="https://bugs.debian.org/debian-policy">Proposed amendments</a> to Policy - - <p>Supplemental Policy documentation:</p> - <ul> - <li><a href="packaging-manuals/fhs/fhs-3.0.html">Filesystem Hierarchy Standard</a> - [<a href="packaging-manuals/fhs/fhs-3.0.pdf">PDF</a>] - [<a href="packaging-manuals/fhs/fhs-3.0.txt">plain text</a>] - <li><a href="debian-policy/upgrading-checklist.html">Upgrading checklist</a> - <li><a href="packaging-manuals/virtual-package-names-list.yaml">Virtual package names list</a> - <li><a href="packaging-manuals/menu-policy/">Menu policy</a> - [<a href="packaging-manuals/menu-policy/menu-policy.txt.gz">plain text</a>] - <li><a href="packaging-manuals/perl-policy/">Perl policy</a> - [<a href="packaging-manuals/perl-policy/perl-policy.txt.gz">plain text</a>] - <li><a href="packaging-manuals/debconf_specification.html">debconf specification</a> - <li><a href="packaging-manuals/debian-emacs-policy">Emacsen policy</a> - <li><a href="packaging-manuals/java-policy/">Java policy</a> - <li><a href="packaging-manuals/python-policy/">Python policy</a> - <li><a href="packaging-manuals/copyright-format/1.0/">copyright-format specification</a> - </ul> - </availability> -</doctable> -</div> - -<hr> - -<document "Debian Developer's Reference" "devref"> - -<div class="centerblock"> -<p> - This manual describes procedures and resources for Debian maintainers. - It describes how to become a new developer, the upload procedure, how - to handle our bug tracking system, the mailing lists, Internet - servers, etc. - - <p>This manual is thought as a <em>reference manual</em> for all Debian - developers (newbies and old pros). - -<doctable> - <authors "Ian Jackson, Christian Schwarz, Lucas Nussbaum, Raphaël Hertzog, Adam Di Carlo, Andreas Barth"> - <maintainer "Lucas Nussbaum, Hideki Yamane, Holger Levsen"> - <status> - ready - </status> - <availability> - <inpackage "developers-reference"> - <inddpvcs-developers-reference> - </availability> -</doctable> -</div> - -<hr> - -<document "Guide for Debian Maintainers" "debmake-doc"> - -<div class="centerblock"> -<p> -This tutorial document describes the building of the Debian package to ordinary -Debian users and prospective developers using the <code>debmake</code> command. -</p> -<p> -It is focused on the modern packaging style and comes with many simple examples. -</p> -<ul> -<li>POSIX shell script packaging</li> -<li>Python3 script packaging</li> -<li>C with Makefile/Autotools/CMake</li> -<li>multiple binary packages with shared library etc.</li> -</ul> -<p> -This “Guide for Debian Maintainers” can be considered as the successor to the -“Debian New Maintainers’ Guide”. -</p> - -<doctable> - <authors "Osamu Aoki"> - <maintainer "Osamu Aoki"> - <status> - ready - </status> - <availability> - <inpackage "debmake-doc"> - <inddpvcs-debmake-doc> - </availability> -</doctable> -</div> - -<hr> - -<document "Debian New Maintainers' Guide" "maint-guide"> - -<div class="centerblock"> -<p> - This document will try to describe building of a Debian GNU/Linux package - to the common Debian user (and wannabe developer) in common language, and - well covered with working examples. - - <p>Unlike previous attempts, this one is based on <code>debhelper</code> - and the new tools available to maintainers. The author is making every - attempt to incorporate and unify previous efforts. - -<doctable> - <authors "Josip Rodin, Osamu Aoki"> - <maintainer "Osamu Aoki"> - <status> - to be replaced by “Guide for Debian Maintainers” (debmake-doc) - </status> - <availability> - <inpackage "maint-guide"> - <inddpvcs-maint-guide> - </availability> -</doctable> -</div> - -<hr> - -<document "Introduction to Debian packaging" "packaging-tutorial"> - -<div class="centerblock"> -<p> -This tutorial is an introduction to Debian packaging. -It teaches prospective -developers how to modify existing packages, how to create their own packages, -and how to interact with the Debian community. -In addition to the main -tutorial, it includes three practical sessions on modifying the <code>grep</code> -package, and packaging the <code>gnujump</code> game and a Java library. -</p> - -<doctable> - <authors "Lucas Nussbaum"> - <maintainer "Lucas Nussbaum"> - <status> - ready - </status> - <availability> - <inpackage "packaging-tutorial"> - <inddpvcs-packaging-tutorial> - </availability> -</doctable> -</div> - -<hr> - -<document "Debian Menu System" "menu"> - -<div class="centerblock"> -<p> - This manual describes the Debian Menu System and the <strong>menu</strong> - package. - - <p>The menu package was inspired by the install-fvwm2-menu program from - the old fvwm2 package. However, menu tries to provide a more general - interface for menu building. With the update-menus command from this - package, no package needs to be modified for every X window manager again, - and it provides a unified interface for both text- and X-oriented - programs. - -<doctable> - <authors "Joost Witteveen, Joey Hess, Christian Schwarz"> - <maintainer "Joost Witteveen"> - <status> - ready - </status> - <availability> - <inpackage "menu"> - <a href="packaging-manuals/menu.html/">HTML online</a> - </availability> -</doctable> -</div> - -<hr> - -<document "Debian Installer internals" "d-i-internals"> - -<div class="centerblock"> -<p> - This document is intended to make Debian Installer more accessible to new - developers and as a central location to document technical information. - -<doctable> - <authors "Frans Pop"> - <maintainer "Debian Installer team"> - <status> - ready - </status> - <availability> - <p><a href="https://d-i.debian.org/doc/internals/">HTML online</a></p> - <p><a href="https://salsa.debian.org/installer-team/debian-installer/tree/master/doc/devel/internals">DocBook XML source online</a></p> - </availability> -</doctable> -</div> - -<hr> - -<document "dbconfig-common documentation" "dbconfig-common"> - -<div class="centerblock"> -<p> - This document is intended for package maintainers who maintain packages that - require a working database. Instead of implementing the required logic - themselves they can rely on dbconfig-common to ask the right questions during - install, upgrade, reconfigure and deinstall for them and create and fill the - database. - -<doctable> - <authors "Sean Finney and Paul Gevers"> - <maintainer "Paul Gevers"> - <status> - ready - </status> - <availability> - <inpackage "dbconfig-common"> - <inddpvcs-dbconfig-common> - Additional also the <a href="/doc/manuals/dbconfig-common/dbconfig-common-design.html">design document</a> is available. - </availability> -</doctable> -</div> - -<hr> - -<document "dbapp-policy" "dbapp-policy"> - -<div class="centerblock"> -<p> - A proposed policy for packages that depend on a working database. - -<doctable> - <authors "Sean Finney"> - <maintainer "Paul Gevers"> - <status> - draft - </status> - <availability> - <inpackage "dbconfig-common"> - <inddpvcs-dbapp-policy> - </availability> -</doctable> -</div> - diff --git a/greek/doc/misc-manuals.wml b/greek/doc/misc-manuals.wml deleted file mode 100644 index 2fe2caaf3bd..00000000000 --- a/greek/doc/misc-manuals.wml +++ /dev/null @@ -1,26 +0,0 @@ -#use wml::debian::ddp title="Debian Miscellaneous Manuals" -#include "$(ENGLISHDIR)/doc/manuals.defs" -#include "$(ENGLISHDIR)/doc/misc-manuals.defs" -#use wml::debian::translation-check translation="def8c6b64adbe3506617995c16f029216a068763" maintainer="galaxico" - -<document "Debian Project History" "history"> - -<div class="centerblock"> -<p> - This manual explains the history, the goals and related issues - about the Debian Project. - -<doctable> - <authors "Will Lowe, Martin Schulze, Bdale Garbee"> - <maintainer "Bdale Garbee, Javier Fernández-Sanguino Peña"> - <status> - ready, updated on demand - </status> - <availability> - <inpackage "debian-history"> - <inddpvcs-debian-history> - </availability> -</doctable> -</div> - - diff --git a/greek/doc/user-manuals.wml b/greek/doc/user-manuals.wml deleted file mode 100644 index 5e460b7fe31..00000000000 --- a/greek/doc/user-manuals.wml +++ /dev/null @@ -1,325 +0,0 @@ -#use wml::debian::ddp title="Debian Users' Manuals" -#include "$(ENGLISHDIR)/doc/manuals.defs" -#include "$(ENGLISHDIR)/doc/user-manuals.defs" -#use wml::debian::translation-check translation="35678d9c62667396da87b15a2475b03c7169ba26" maintainer="galaxico" - -<document "Debian GNU/Linux FAQ" "faq"> - -<div class="centerblock"> -<p> - Users' Frequently Asked Questions. - -<doctable> - <authors "Susan G. Kleinmann, Sven Rudolph, Santiago Vila, Josip Rodin, Javier Fernández-Sanguino Peña"> - <maintainer "Javier Fernández-Sanguino Peña"> - <status> - ready - </status> - <availability> - <inpackage "debian-faq"><br> - <inddpvcs-debian-faq> - </availability> -</doctable> -</div> - -<hr /> - -<document "Debian Installation Guide" "install"> - -<div class="centerblock"> -<p> - Installation instructions for the Debian GNU/Linux distribution. - The manual describes the installation process using the Debian Installer, - the installation system for Debian that was first released with - <a href="$(HOME)/releases/sarge/">Sarge</a> (Debian GNU/Linux 3.1).<br> - Additional information related to the installation can be found in the - <a href="https://wiki.debian.org/DebianInstaller/FAQ">Debian Installer FAQ</a> - and the - <a href="https://wiki.debian.org/DebianInstaller">Debian Installer wiki pages</a>. - -<doctable> - <authors "Debian Installer team"> - - <maintainer "Debian Installer team"> - <status> - The manual is not yet perfect. Active work is being done for the current - and future Debian releases. Help is welcome, especially with non-x86 - installation and translations. - Contact - <a href="mailto:debian-boot@lists.debian.org?subject=Install%20Manual">debian-boot@lists.debian.org</a> - for more information. - </status> - <availability> - <insrcpackage "installation-guide"> - <br><br> - <a href="$(HOME)/releases/stable/installmanual">Published version - for the stable release</a> - <br> - Available on the <a href="$(HOME)/CD/">official full CDs and DVDs</a> - in the <tt>/doc/manual/</tt> directory. - <br><br> - <a href="$(HOME)/releases/testing/installmanual">Version being prepared - for the next stable (in testing)</a> - <br><br> - <a href="https://d-i.debian.org/manual/">Development version</a> - <br> - <inddpvcs-installation-guide> - </availability> -</doctable> - -<p> -Versions of the installation guide for previous releases (and possibly the -next release) of Debian are linked from the <a href="$(HOME)/releases/">release -page</a> for those releases. - -</div> - -<hr /> - -<document "Debian Release Notes" "relnotes"> - -<div class="centerblock"> -<p> - This document contains information on what's new in the current Debian - GNU/Linux distribution and complete upgrading information for users of - older Debian releases. - -<doctable> - <authors "Adam Di Carlo, Bob Hilliard, Josip Rodin, Anne Bezemer, Rob Bradford, Frans Pop, Andreas Barth, Javier Fernández-Sanguino Peña, Steve Langasek"> - <status> - Actively worked upon for Debian releases. - Contact - <a href="mailto:debian-doc@lists.debian.org?subject=Release%20Notes">debian-doc@lists.debian.org</a> - for more information. Problems and patches should be reported as - <a href="https://bugs.debian.org/release-notes">bugs against the - release-notes pseudo-package</a>. - </status> - <availability> - <a href="$(HOME)/releases/stable/releasenotes">Released version</a> - <br> - Available on the <a href="$(HOME)/CD/">official full CDs and DVDs</a> - in the <tt>/doc/release-notes/</tt> directory. -# <br> -# Also available at <a href="$(HOME)/mirror/list">ftp.debian.org and all mirrors</a> -# in the <tt>/debian/doc/release-notes/</tt> directory. -# <br> -# <a href="$(HOME)/releases/testing/releasenotes">Version being prepared -# for the next stable (in testing)</a> - - <inddpvcs-release-notes> - </availability> -</doctable> -</div> - -<hr /> - -<document "Debian Reference Card" "refcard"> - -<div class="centerblock"> -<p> - This card provides new users of Debian GNU/Linux with the most - important commands in a single page to be used as a reference - when working with Debian GNU/Linux systems. Basic (or better) - knowledge of computers, files, directories and the command line is - required. - -<doctable> - <authors "W. Martin Borgert"> - <maintainer "W. Martin Borgert"> - <status> - published; in active development - </status> - <availability> - <inpackage "debian-refcard"><br> - <inddpvcs-refcard> - </availability> -</doctable> -</div> - -<hr /> - -<document "The Debian Administrator's Handbook" "debian-handbook"> - -<div class="centerblock"> -<p> - The Debian Administrator's Handbook teaches the - essentials to anyone who wants to become an effective and independent Debian - GNU/Linux administrator. - -<doctable> - <authors "Raphaël Hertzog, Roland Mas"> - <status> - Published; in active development - </status> - <availability> - <inpackage "debian-handbook"><br> - <inddpvcs-debian-handbook> - </availability> -</doctable> -</div> - -<hr /> - -<document "Debian Reference" "quick-reference"> - -<div class="centerblock"> -<p> - This Debian GNU/Linux reference covers many aspects of system - administration through shell-command examples. Basic tutorials, tips, and - other information are provided for topics including system installation, - Debian package management, the Linux kernel under Debian, system tuning, - building a gateway, text editors, VCS, programming, and GnuPG. - - <p>Previously known as "Quick Reference". - -<doctable> - <authors "Osamu Aoki (青木 修)"> - <maintainer "Osamu Aoki (青木 修)"> - <status> - Published; in active development - </status> - <availability> - <inpackage "debian-reference"><br> - <inddpvcs-debian-reference> - </availability> -</doctable> -</div> - -<hr /> - -<document "Securing Debian Manual" "securing"> - -<div class="centerblock"> -<p> - This manual describes the security of the Debian GNU/Linux - operating system and within the Debian project. It starts - with the process of securing and hardening the default Debian GNU/Linux - installation (both manually and automatically), covers some of the - common tasks involved in setting up a secure user and network environment, - gives information on the security tools available, steps to take - before and after a compromise and also describes how security is - enforced in Debian by the security team. The document includes - a step by step hardening guide and within the appendix there - is detailed information on how to setup an intrusion detection - system and a bridge firewall with Debian GNU/Linux. - -<doctable> - <authors "Alexander Reelsen, Javier Fernández-Sanguino Peña"> - <maintainer "Javier Fernández-Sanguino Peña"> - <status> - Published; under development with few changes. Some of its content might not be fully up-to-date. - </status> - <availability> - <inpackage "harden-doc"><br> - <inddpvcs-securing-debian-manual> - </availability> -</doctable> -</div> - -<hr /> - -<document "aptitude user's manual" "aptitude"> - -<div class="centerblock"> -<p> - An introductory guide to the aptitude package manager with the - complete command reference. - - -<doctable> - <authors "Daniel Burrows"> - <status> - Published; in active development - </status> - <availability> - <inpackage "aptitude-doc"><br> - <inddpvcs-aptitude> - </availability> -</doctable> -</div> - -<hr /> - -<document "APT User's Guide" "apt-guide"> - -<div class="centerblock"> -<p> - This document provides an overview of how to use the APT package manager. - - -<doctable> - <authors "Jason Gunthorpe"> - <status> - Published; somewhat stale - </status> - <availability> - <inpackage "apt-doc"><br> - <inddpvcs-apt-guide> - </availability> -</doctable> -</div> - -<hr /> - -<document "Using APT Offline" "apt-offline"> - -<div class="centerblock"> -<p> - This document describes how to use APT in a non-networked environment, - specifically a 'sneaker-net' approach for performing upgrades. - -<doctable> - <authors "Jason Gunthorpe"> - <status> - Published; somewhat stale - </status> - <availability> - <inpackage "apt-doc"><br> - <inddpvcs-apt-offline> - </availability> -</doctable> -</div> - -<hr /> - -<document "Debian Java FAQ" "java-faq"> - -<div class="centerblock"> -<p> -The purpose of this FAQ is to be a place to look for all kind of -questions a developer or user might have regarding Java as far as Debian -is concerned, it includes license issues, development packages available, -and programs related to building a Free Software Java environment. - -<doctable> - <authors "Javier Fernández-Sanguino Peña, Torsten Werner, Niels Thykier, Sylvestre Ledru"> - <status> - Published; in active development although some of its content might not be current. - </status> - <availability> - <inpackage "java-common"><br> - <inddpvcs-debian-java-faq> - </availability> -</doctable> -</div> - -<hr /> - -<document "Debian Hamradio Maintainer’s Guide" "hamradio-maintguide"> - -<div class="centerblock"> -<p> -The Debian Hamradio Maintainers Guide is a document that outlines team policy and best -current practice for the Deian Hamradio Maintainers packaging team. - -<doctable> - <authors "Iain R. Learmonth"> - <status> - Published; in active development. - </status> - <availability> - <inpackage "hamradio-maintguide"><br> - <inddpvcs-hamradio-maintguide> - </availability> -</doctable> -</div> diff --git a/greek/doc/vcs.wml b/greek/doc/vcs.wml deleted file mode 100644 index c0f3f61c520..00000000000 --- a/greek/doc/vcs.wml +++ /dev/null @@ -1,102 +0,0 @@ -#use wml::debian::ddp title="Debian Documentation Project VCS" -#use wml::debian::toc -#use wml::debian::translation-check translation="bf1a0486dfbf35e11a7ff98a29d9e2e4f2eda3f3" maintainer="galaxico" - -<p>The Debian Documentation Project stores its web pages and much of the -manual text on the Debian Salsa service at -<strong>salsa.debian.org</strong>, which is Debian's GitLab instance. -Please read the <a href="https://wiki.debian.org/Salsa">Salsa documentation</a> -for more information about how this service works. -</p> - -<p>Everybody can download the sources from the Salsa service. Only members of -the Debian Documentation Project can update files.</p> - -<toc-display /> - -<toc-add-entry name="access">Accessing the sources in git</toc-add-entry> - -<p>You can use a web interface to access the files individually and -see changes on each project at -<url "https://salsa.debian.org/ddp-team/" /></p> - -<p>For downloading an entire manual, direct access to the git server -is often a better option. You need the -<tt><a href="https://packages.debian.org/git">git</a></tt> package on your -own machine.</p> - -<h3>Cloning a git repository anonymously (read-only)</h3> - -<p>Use this command to download all the files for one project:</p> - -<p style="margin-left: 2em"> - <code>git clone https://salsa.debian.org/ddp-team/release-notes.git</code> -</p> - -<p>Do the same for every project you want to clone locally.</p> - -<h3>Cloning a git repository with push privileges (read-write)</h3> - -<p>Before accessing the git server using this method you have to be -granted write access to it first. Please read how to <a -href="#obtaining">request</a> push permission first.</p> - -<p>Use this command to download all the files for one project:</p> - -<p style="margin-left: 2em"> - <code>git clone git@salsa.debian.org:ddp-team/release-notes.git</code> -</p> - -<p>Do the same for every project you want to clone locally.</p> - -<h3>Fetching changes from the remote git repository</h3> - -<p>To update your local copy with any changes made by other people, enter -the <strong>manuals</strong> directory and run the command:</p> - -<p style="margin-left: 2em"> - <code>git pull</code> -</p> - -<toc-add-entry name="obtaining">Obtaining push privileges</toc-add-entry> - -<p>Push privileges are available to anyone who wishes to participate in -writing the manuals. We generally request that you have submitted -a couple of useful patches first.</p> - -<p>After creating your account on <a href="https://salsa.debian.org/">Salsa</a>, -please request push privileges by clicking <q>Request to join</q> on the -group or any of the specific projects under -<url "https://salsa.debian.org/ddp-team/" />. -Please follow it up with an email to debian-doc@lists.debian.org explaining -the track record of your work on Debian.</p> - -<p>Once your request is approved, you'll be part of either the <a -href="https://salsa.debian.org/ddp-team/"><q>ddp-team</q> group</a> or -one of its projects. -</p> - -<hr /> - -<toc-add-entry name="updates">Automatic update mechanism</toc-add-entry> - -<p>The published web pages of the manual text are generated on -www-master.debian.org as part of the regular web site rebuilding process, -which happens every four hours.</p> - -<p>The process is set up to download the latest package versions from the -archive, rebuild each manual, and install the files -in <code>doc/manuals/</code> subdirectory of the web site.</p> - -<p>The documentation files generated by the update script can be found at -<a href="manuals/">https://www.debian.org/doc/manuals/</a>.</p> - -<p>The log files generated by the update process can be found at -<url "https://www-master.debian.org/build-logs/webwml/" /> -(the script is named <code>7doc</code> and is running as part of the -<code>often</code> cron job).</p> - -# <p>Note that this process regenerates the <code>/doc/manuals/</code> -# directory. The contents of the <code>/doc/</code> directory is generated -# either from <a href="/devel/website/desc">webwml</a> or from other scripts, -# such as those which extract certain manuals from their packages.</p> diff --git a/greek/legal/anssi.wml b/greek/legal/anssi.wml deleted file mode 100644 index 6f4291bd0d7..00000000000 --- a/greek/legal/anssi.wml +++ /dev/null @@ -1,90 +0,0 @@ -#use wml::debian::template title="Cryptographic export/import attestation" -#use wml::debian::translation-check original="french" translation="bb3439fa8a9568782acebb5b5b50d732ec55014a" -#use wml::debian::translation-check translation="c0816ff3dae7deb1cd48fb2f83fa934f5e5f3559" maintainer="galaxico" - -<p> -Following the <a -href="debian-lenny-crypto-declaration.pdf">\ -declaration related to cryptology equipment</a>, the <a -href="http://www.ssi.gouv.fr/site_rubrique88.html">\ -FNISA (ANSSI)</a> assigned the <a -href="debian-lenny-crypto-attestation.pdf">\ -file number 1101027</a> to the request. -</p> - -<p> -Here is the translation of the <a -href="debian-lenny-crypto-attestation-export.pdf">\ -cryptographic export/import attestation</a> received; please use the <a -href="anssi.fr.html">original version</a> for legal purposes. -</p> - -<hr/> - -<p> -Paris, 20 January 2011 -</p> - -<p> -General Secretariat for Defence and National Security -<br/> -<em>French Network and Information Security Agency</em> -<br/> -<em>Regulatory Oversight Office</em> -</p> - -<p style="class:center"><strong> -The Chief Executive of the French Network and Information Security Agency -<br/> -to -<br/> -Mr Yves-Alexis Perez -</strong></p> - -<table border=0 width="100%" summary="mail headers"> -<colgroup span="2"> -<col width="10%"><col> -<tr><td> -Subject: -</td><td> -Classification of a cryptology equipment -</td></tr> -<tr><td> -Reference: -</td><td> -Your cryptology equipment declaration for <strong>Debian version 5.0 -(Lenny)</strong>, registered under the file number <strong>1101027</strong>. -</td></tr> -</table> - - -<p> -Sir, -</p> - -<p> -I hereby certify that the cryptology equipment indicated -in the above declaration comes under Category 3 -of Schedule 2 of decree No. 2007-663, 2 May 2007. -</p> - -<p> -I consequently inform you that you may freely engage in -transfer operations to a member state of the European Union and -export to a third-party state with this cryptology equipment. -</p> - -<p> -This declaration does not in any way constitute a statement about -the quality of this cryptology equipment or a recommendation -from the French Network and Information Security Agency. -</p> - -<p> -Yours Sincerely -</p> - -<p> -Ivan Maximoff, policy officer responsible for cryptography controls -</p> - diff --git a/greek/legal/cryptoinmain.wml b/greek/legal/cryptoinmain.wml deleted file mode 100644 index ec40e7adff6..00000000000 --- a/greek/legal/cryptoinmain.wml +++ /dev/null @@ -1,750 +0,0 @@ -#use wml::debian::template title="Exploring Cryptographic Software in Debian's Main Archive" BARETITLE=true -#use wml::debian::translation-check translation="ba01cfdc529712e3626bdf15fd37d39e94126794" maintainer="galaxico" - -# Nota bene! This is basically draft text from the lawyers, and it must -# _not_ be modified for spelling errors and such. Formatting changes are -# fine (I think). -- Joy - -<table width="100%" summary="mail headers"> -<colgroup span="2"> -<col width="10%"> -<col> -</colgroup> -<tr><td>To:</td> - <td><a href="https://www.spi-inc.org/">Software in the Public Interest</a>, <a href="https://www.debian.org/">Debian Project</a></td></tr> -<tr><td>From:</td> - <td>Roszel C. Thomsen II, Partner, <a href="http://www.t-b.com/">Thomsen & Burke LLP</a></td></tr> -<tr><td>Date:</td> - <td>July 31, 2001</td></tr> -<tr><td>Re:</td> - <td>Exploring Cryptographic Software in Debian's Main Archive</td></tr> -</table> - -<p>Thank you for this opportunity to comment on Sam Hartman's white paper -entitled <q>Exploring Cryptographic Software in Debian's Main Archive</q>.</p> - -<p>We are providing this information as a general guideline to you. BXA -requires that each entity exporting products be familiar with and comply -with their affirmative obligations set forth in the Export Administration -Regulations. Please note that the regulations are subject to change. We -recommend that you obtain your own legal advice when attempting to -export. In addition some countries may restrict certain levels of -encryption imported into their country. We recommend consulting legal -counsel in the appropriate country or the applicable governmental -agencies in the particular country.</p> - -<p>By way of background, the export of cryptographic software from the -United States is governed under the United States Export Administration -Regulations (<q>EAR</q>, 15 CFR Part 730 et seq.) administered by the -Commerce Department's Bureau of Export Administration (<q>BXA</q>). BXA -revised the provisions of the EAR governing cryptographic software most -recently on October 19, 2000. I refer to these as the <q>new US -Regulations</q> in order to distinguish them from prior regulations that -were more restrictive.</p> - -<p>When the Clinton Administration came to Washington, encryption items -were controlled for export from the United States as <q>munitions</q> under -the Arms Export Control Act and the International Traffic in Arms -Regulations. Most applications for licenses to export strong encryption -items were denied. Industry and public interest groups lobbied for -liberalization, and the Clinton Administration reformed the outdated -U.S. export controls on encryption items in a series of graduated steps, -culminating the new US Regulations. The new Bush Administration is -considering further liberalizations that may be published later this -year.</p> - -<p>Despite these liberalizations, the U.S. export controls on commercial -encryption items remain complex and onerous. American companies must -submit encryption items for technical reviews by the intelligence -authorities prior to export. Exports to some agencies of foreign -governments require licenses, as do exports to telecommunications and -Internet service providers wishing to provide services to some -government agencies. Finally, post-export reporting requirements apply -to many exports from the United States. Thus, U.S. encryption export -controls continue to impose a significant regulatory burden on American -companies, retarding the worldwide deployment of strong cryptography in -commercial software programs.</p> - -<p>Not all software programs with encryption are commercial products, -however. For purposes of the EAR, cryptographic source code controls -fall into three categories: (a) open source, (b) community source, and -(c) proprietary source. The rules governing exports of each type of -source code are different, and they have been amended in important -respects in the new US Regulations.</p> - -<p>Open source refers to software that is available to the public without -restriction free of charge, under a GNU-style license agreement. Debian -would appear to fall into this category. The old regulations allowed -the export of open source to any end-user without a technical review, -provided that the person making the open source available filed a -contemporaneous notification with BXA and the National Security Agency -(<q>NSA</q>). However, the old regulations were silent with respect to -restrictions (if any) on the export of compiled executable software -derived from open source.</p> - -<p>Under the new US Regulations, not only the open source, but also the -compiled executable software derived from open source, is eligible for -export under the same conditions as the open source itself, provided -that the compiled executable is available without restriction and free -of charge. Unfortunately, if you include the compiled executable -software into a product that you distribute for a fee, then the -resulting product is subject to all of the rules that apply to -commercial software programs. For example, they must be submitted to -BXA and NSA for a one-time technical review, described above.</p> - -<p>Community source refers to software that is available to the public free -of charge for non-commercial use but that contains further restrictions -on commercial use. Community source may be exported under essentially -the same conditions as open source, but community source remains subject -to more detailed reporting requirements.</p> - -<p>Proprietary source refers to all source code that is neither <q>open</q> -nor <q>community</q> source. Exporters may provide proprietary source code -to any end-user in the EU and its partners, and to any non-government -end-user in other countries, promptly upon filing of a technical review -with BXA and NSA. The same reporting requirements applicable to -community source also apply to proprietary source.</p> - -<p>Please keep in mind that persons in the US who may post to sites outside -the US are governed by US law, even if they do so in their individual -capacity. Therefore, you may want to warn persons in the US that their -posting to the current crypto server outside the US are still subject to -US regulations.</p> - -<p>Finally, you should be aware that a core set of US export controls apply -to all exports of open source cryptographic software from the United -States. In essence, these controls prohibit the export of open source -cryptographic software under License Exception TSU to (1) prohibited -parties (listed at <a href="http://www.bxa.doc.gov/DPL/Default.shtm">http://www.bxa.doc.gov/DPL/Default.shtm</a>), -(2) prohibited countries (currently Cuba, Iran, Iraq, Libya, North -Korea, Sudan, Syria and Taliban Occupied Afghanistan) and (3) design, -development, stockpiling, production or use of nuclear, chemical or -biological weapons or missiles.</p> - -<p>With this background, your specific questions with respect to Debian are -address in the order that they appear in Sam Hartman's white paper, -below in italics.</p> - -<hr /> - -<h2><i>Exploring Cryptographic Software in Debian's Main Archive</i></h2> - -<p><i>Sam Hartman</i></p> - -<p><i>Debian Project</i></p> - -<hrline /> - -<p style="margin-left: 2em"> - <i>Debian is a free operating system. Currently for US export reasons, Debian - splits cryptographic software off into a separate archive located outside - the US. This document summarizes the questions we would need to answer from - a legal standpoint in order to merge these two archives.</i> -</p> - -<hrline /> - -<h3><i>About Debian</i></h3> - -<p><i>Debian is a group of individuals working to produce a free operating system. -These individuals are responsible for decisions they make while working on -Debian; there is no legal Debian organization that developers work for or that -decisions are made on behalf of. There is a registered non-profit, Software in -the Public Interest (SPI), that holds money and resources for Debian. So -decisions developers make may impact resources owned by SPI and thus impact -SPI. Other Debian resources are owned by various sponsors. Debian generally -depends on sponsors for network connectivity. There are also third-party groups -that copy the Debian software onto mirrors so that people around the world can -download and use it. Others make and sell CDs of Debian. All these groups might -be accountable to a greater or lesser extent for the decisions Debian makes. We -want to conduct ourselves in a manner that minimizes the liability for all -parties and, within that constraint, maximizes the value of our efforts.</i></p> - -<p><i>As with all operating system vendors, Debian needs to include cryptographic -software. This software provides security, allows users to engage in Internet -commerce, and accomplishes other tasks requiring cryptography. Today, this -software is stored on a server outside the United States, known as the <q>non-US -server</q>. Currently Debian takes no measures to assist US developers in -following export control regulations if they upload software to the non-US -archive or to prevent them from uploading software. We would like to move -cryptographic software from the non-US server onto our main server in the US.</i></p> - -<p><i>With the increasing networked nature of the work, and the fact that more and -more critical functions are being placed on computing platforms, and the -unfortunate growth of mischief and deliberate malice, security is going to be -increasingly important. Cryptography is an important corner stone of a number -of security processes. Any OS that does not make an effort to seamlessly -integrate cryptography is unlikely to be competitive.</i></p> - -<p><i>Putting all software on a single source, and the corresponding ability to -create a single set of CD's that have integrated cryptographic support makes it -easier for the users, makes it easier for CD vendors, simplifies the task of -developers uploading software to these sites, and simplifies the task of -replicating the software repositories on the internet.</i></p> - -<p><i>The rest of this document will focus on the main server within the US and on -its mirrors and copies around the world. It's important to realize that there -is currently a parallel structure set up to deal with the non-US server.</i></p> - -<p><i>Every few months Debian developers release a new official version of Debian. -This software is made available on the main (and for cryptographic software, -the non-US) server to a group of primary mirrors around the world. These -mirrors copy the software off the main server and make it available to users -and secondary mirrors. The users can use HTTP, FTP, or a variety of other -methods to retrieve the software. CD images are made available to users and -resellers. These images can be burned onto physical CDs by individuals or by -those wanting to sell/give away Debian.</i></p> - -<p><i>In addition, there are two constantly evolving releases of Debian: the testing -and unstable releases. These releases are updated on a daily basis by -developers around the world. Like the official releases, these releases are -made available on the main and non-US servers to primary mirrors. The primary -mirrors make software available via HTTP, FTP and other methods both to end -users and to secondary mirrors. CD images are sometimes made from these -releases. The important difference between these evolving releases and the -official release is that they are constantly changing.</i></p> - -<p><i>Often, developers upload binaries and source code at the same time. However, we -support many different types of computers each of which requires different -binaries for the same source code. Most developers make binaries only for one -of the computer architectures we support when they upload a changed program. -Automated processes go and use the source code they have uploaded to make -binaries for the other architectures. As such, some binaries for a particular -source code program will likely be uploaded at a later time than that source -code.</i></p> - -<p><i>Some Debian developers also use Debian resources to work on as-yet-unreleased -software. The primary resource that is useful for this task is the Debian CVS -server. Source code to projects on this server is almost always available to -the public, but may change many times in a day. The CVS server is in the US.</i></p> - -<p><i>However most Debian software is not developed directly by Debian developers. -Instead, the software is released to the public by some third party. Some -software is made available to the public on sites within the US, while other -original authors release their software on sites outside the US. Debian -developers are responsible for integrating the software into Debian. As part of -this job, many Debian developers end up working closely with the original -software author, often contributing code back to the original release.</i></p> - -<p><i>The software in Debian complies with the Debian Free Software Guidelines; the -DFSG. We believe this software has publicly available source code in the sense -of section 740.13(e) of the EAR. The guidelines require that the source code be -redistributable. The DFSG indirectly requires that one be able to distribute a -product based on the source code without paying a fee. We distribute all the -source code in Debian as part of our releases. Other software is distributed in -our non-free archive, but our focus in this document is on the DFSG-free -software. We would be interested in knowing to what extent we could move -non-DFSG-free software for which we can distribute source code into the US, but -we want to make sure advice in this area does not get confused with advice on -how to handle DFSG-free software.</i></p> - -<p><i>Debian developers live around the world and are citizens of many countries. -Obviously some are US citizens, but many others are not. Some may be citizens -of the seven forbidden countries in EAR section 740.13(e).</i></p> - -<p><i>As mentioned, we have mirrors all around the world. We do not have any official -mirrors (mirrors with which the project is connected) in any of the seven -countries listed in EAR section 740.13(e), although since our software is -publicly available, it might be copied into these countries. Most mirrors -within the US currently only mirror the main server (the one without -cryptography), although some mirror both the main and non-US portions of the -archive. Debian takes no responsibility for mirrors within the US that mirror -the non-US portion of the archive.</i></p> - -<hrline /> - -<h3><i>Our Goal</i></h3> - -<p><i>We want to include cryptographic software in our main archive. We want to -understand the risks to developers, users, SPI, mirror maintainers, CD -resellers, sponsors and any other parties that are connected with Debian so -that we can make an informed decision. We want to be able to document and -publicize these risks so that these parties do not commit a crime through -ignorance. Obviously, we also want to avoid taking unnecessary risks.</i></p> - -<p><i>In particular we would like to consider the following activities:</i></p> - -<ul> -<li><i>On a daily basis, adding and modifying DFSG-free software to our releases. - In practice only the testing and unstable releases are modified on a daily - basis, but the other releases are modified from time to time.</i></li> - -<li><i>Distributing cryptographic software as part of our releases over the - Internet and on CDs.</i></li> - -<li><i>Adding and changing DFSG-free cryptographic software on our CVS server.</i></li> - -<li><i>Any reactions we'd have to have to any changes in cryptographic regulations - (or laws).</i></li> -</ul> - -<hrline /> - -<p><em>END Debian Document Preamble</em></p> - -<p>I will try to reflect these goals in my answers to your questions. By -way of summary, I think that an initial notification should suffice for -the current archive and updates thereto. A new notification would be -required only if a new program with encryption should be added to the -archive. Additional distribution of freeware does not require further -notification. However, commercial versions would be subject to the -technical review, licensing and reporting requirements that apply to -other commercial products. Predicting the future of changes to laws or -regulations is difficult, but if the law changes, you would either have -to take down the site or modify it in order to remain in compliance. -You have no obligation to inform other constituencies of their legal -obligations, but if you have a list of frequently asked questions, I -would be pleased to suggest appropriate responses that you might wish to -offer.</p> - -<p>Questions (Note, each question by Debian is marked with "D:")</p> - -<blockquote class="question"> -<p> -<span>D:</span> - Do we need to notify the Bureau of Export Administration (BXA) - about software we add to releases? -</p> -</blockquote> - -<p>If the notification is drafted properly, and the archive remains on the -site identified in the notification, then you only have to file a single -notification with BXA for the initial archive. Only one notification -for one U.S. site is required; no separate notification is required for -mirror sites inside or outside the U.S. This notification would only -have to be updated if you added a new program implementing encryption.</p> - -<pre> - Department of Commerce - Bureau of Export Administration - Office of Strategic Trade and Foreign Policy Controls - 14th Street and Pennsylvania Ave., N.W. - Room 2705 - Washington, DC 20230 - - Re: Unrestricted Encryption Source Code Notification - Commodity: Debian Source Code - - Dear Sir/Madam: - Pursuant to paragraph (e)(1) of Part 740.13 of the U.S. Export - Administration Regulations ("EAR", 15 CFR Part 730 et seq.), we are - providing this written notification of the Internet location of the - unrestricted, publicly available Debian Source Code. Debian Source Code - is a free operating system developed by a group of individuals, - coordinated by the non-profit Software in the Public Interest. This - archive is updated from time to time, but its location is constant. - Therefore, and this notification serves as a one-time notification for - subsequent updates that may occur in the future. New programs will be - the subject of a separate notification. The Internet location for the - Debian Source Code is: https://www.debian.org. - - This site is mirrored to a number of other sites located - outside the United States. - - A duplicate copy of this notification has been sent to the ENC - Encryption Request Coordinator, P.O. Box 246, Annapolis Junction, MD - 20701-0246. - - If you have any questions, please call me at (xxx) xxx-xxxx. - - Sincerely, - Name - Title -</pre> - - -<blockquote class="question"> -<p> -<span>D:</span> - What information do we need to include in the notifications? -</p> -</blockquote> - -<p>The draft language above includes the information that you need to -include in the notification</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - How often do we need to notify? We want to notify as little as - possible as it creates more work for us and for the government, - but we want to notify as often as necessary to follow the - regulations. -</p> -</blockquote> - -<p>As drafted above, and assuming that the archive remains on the Internet -site identified in the notification, you should not have to file a -subsequent notification for subsequent updates. You would only file -another notification if you added a new program implementing -cryptography.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - If we move our cryptographic software into this country, - and the laws or regulations change to be more restrictive, what - are we likely to lose? Would we have to destroy any software, - or CDs? Would we have to remove it from our master or secondary - sites? If we use the increased availability of cryptographic - software to improve the security of the rest of the system, and - the cryptographic legal climate worsens, would be likely to have - to discard all copies of such software in the U.S.? -</p> -</blockquote> - -<p>The trend has been toward increased liberalization of the export -controls on cryptography in the United States, rather than increased -restrictions. This trend has been constant over the past decade and has -accelerated in the past year. We cannot advise you with respect to what -you might lose unless and until new regulations are published. However, -we believe that you would retain copyrights to the software and some, -albeit perhaps more limited, rights to export.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - In order of decreasing preference, we would like to notify: - </p> - <ul> - <li>Once for the entire Debian archive</li> - - <li>Once for each official release (keeping in mind that - testing/unstable change between releases)</li> - - <li>Once when a new program containing cryptography is added to - the archive</li> - - <li>Once when a new version of a program containing cryptography - is added to the archive.</li> - </ul> - -</blockquote> - -<p>I think that you only have to file a new notification if you add a new -program that incorporates cryptography. Updates to existing programs -should be covered by the broad language of the notification we -suggested, above.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - New packages enter the debian archive through the following sequence - of steps. At what point must the notification happen? -</p> - <ol> - <li>Upstream developer releases a package as open-source. - This step gets skipped in the case of a native-Debian package.</li> - <li>A Debian developer packages the source and binary for Debian, - frequently with source changes.</li> - <li>The package is uploaded to ftp-master, incoming.</li> - <li>The new package fails to install, because it's new.</li> - <li>Ftp admins add the needed records for the package.</li> - <li>The package installs into the archive, within a few days.</li> - <li>The package gets copied to the mirror sites.</li> - </ol> -</blockquote> - -<p>The regulations are pretty clear that the notification has to occur -prior to or contemporaneous with public availability. Exports prior to -public availability require an export license. Therefore, if the archive -in step 3 is not publicly available, then either the package must be made -publicly available prior to step 3 (and notifications sent), or export -licenses will be needed for Debian developers. If the archive in step 3 -is publicly available, then notification at that point would eliminate the -need to have export licenses for Debian developers.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - If the upstream author has notified BXA, is the notification needed? - (Packaging for debian can involve modifications to the source - involving file locations, and occasionally functional differences, - although the general goal is to make the upstream code work in - Debian with minimal modification.) -</p> -</blockquote> - -<p>If the upstream author has notified BXA, that is sufficient.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - Do we need to notify when new binaries (object code) are added if - we have already notified for the source code? -</p> -</blockquote> - -<p>I do not think that you have to file a new notification for object code, -provided that a notification for the source code has been filed.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - Is notification required for programs that do not contain crypto - algorithms, but are linked against crypto libraries? What about - programs that launch other programs in order to do cryptographic - functions? -</p> -</blockquote> - -<p>As long as the program is open source, it may include an open crypto API -and still qualify under License Exception TSU.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - New programs can be checked easily prior to their release (and - notification done at that time), but when an update is performed, - there isn't a manual step at which to do the notification. Would - it be acceptable to notify BXA for each addition of software, with - an indication that future updates may include the addition of - crypto functionality? -</p> -</blockquote> - -<p>Yes. Overreporting should probably be avoided where reasonable, but -underreporting must be avoided. Future updates of an existing program -do not require separate notification. Only new programs require separate -notification.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - Can we automate the process of sending in notifications? -</p> -</blockquote> - -<p>You may automate the process of sending notifications. This in an -internal procedural matter. BXA and NSA do not care how you handle the -filing of notifications internally.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - What form should the notification take? -</p> -</blockquote> - -<p>The BXA notification may be in either electronic or paper form; -however, the NSA notification must be in paper form.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - Who can send in the notifications? For example, do they need to - be a US citizen? -</p> -</blockquote> - -<p>Any person may send in the notification; citizenship is not relevant.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - Are there any other concerns we should be aware of? What steps - other than notification do we need to take? -</p> -</blockquote> - -<p>Other than notification, you might consider implementing a reverse IP -lookup that identifies the computer requesting the download, and that -blocks downloads of the cryptographic archive to countries embargoed by -the United States: Cuba, Iran, Iraq, Libya, North Korea, Syria, Sudan -and Taliban Occupied Afghanistan. In addition, you might consider -having a provision in your license agreement, or a separate screen prior -to download, that advises the person downloading the software as -follows:</p> - -<p>This software is subject to U.S. export controls applicable to open source -software that includes encryption. Debian has filed the notification with -the Bureau of Export Administration and the National Security Agency that -is required prior to export under the provisions of License Exception TSU -of the U.S. Export Administration Regulations. Consistent with the -requirements of License Exception TSU, you represent and warrant that you -are eligible to receive this software, that you are not located in a country -subject to embargo by the United States, and that you will not use the -software directly or indirectly in the design, development, stockpiling -or use of nuclear, chemical or biological weapons or missiles. Compiled -binary code that is given away free of charge may be re-exported under the -provisions of License Exception TSU. However, additional technical review -and other requirements may apply to commercial products incorporating this -code, prior to export from the United States. For additional information, -please refer to www.bxa.doc.gov.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - Currently, users around the world can access and potentially - download software that is awaiting integration into our archive. - Likely, we would do any necessary notifications as software is - processed into the archive, so software in this state would be - awaiting notification. Would this be a problem? If so, would it - be acceptable to set up an alternate queue of cryptographic - software awaiting integration into the archive available only to - our developers? In order to process software into our distribution, - developers who are often outside the US need to examine the - software and make sure it meets certain guidelines. How should we - accomplish this access? Are there any other solutions to this - pre-notification area of the archive we should consider? - </p> - <p>One issue we often run into is software patents. Clearly the - integration of cryptography into software doesn't remove any of the - patent concerns we would normally have to think about. However, are - there any new issues we need to consider when patents interact with - cryptography export regulations? It seems that at least for exemption - TSU (section 740.13 of the EAR), patents do not influence whether the - source code is public. - -</p> -</blockquote> - -<p>It is important to differentiate between the archive that has been a -subject of notification, and new programs. You can update the archive -that has been a subject of notification without further notification, as -described above. Only new programs need to be subject of a separate -notification, prior to posting. If new programs must be reviewed by -developers prior to posting, and such software is not both publicly -available and already notified to the U.S. government, then I recommend -that you consider obtaining an export license authorizing this limited, -pre-notification review. You are correct that patents do not disqualify -software from eligibility for export under License Exception TSU.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - Distribution, Mirroring and CDs</p> - - <p>Do our mirrors within the US need to notify the BXA if we add - cryptography to our archive? How often do they need to notify BXA? - We would like to avoid a situation where mirrors have to notify for - each new program Debian adds to the archive, even if our master - server must send in such notifications. We need to keep operations - simple for mirror operators. What, if anything, would mirrors - outside the US need to do?</p> - - <p>If we send an update to a mirror rather than waiting for it to - download software, do we need to take any special steps? What if we - send a mirror a request to download new/changed software? - -</p> -</blockquote> - -<p>Once the notification has been filed for the central server, no further -notification is required for mirror sites.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - Which of the following vendors (if any) would be able to ship - unmodified Debian binaries (and source) with only notification? - Which would require review and approval? Could the review be - concurrent with shipment, or must approval predate shipment? -</p> - <p> - A) mail-order shipment of CD's for the cost of the media?<br /> - B) mail-order shipment of CD's for profit?<br /> - C) off-the-shelf sales of CD's for the cost of the media?<br /> - D) off-the-shelf sales of CD's for profit?<br /> - E) vendor providing CD's from A or C above, along with hardware. HW - sold at a profit, but with no preinstall?<br /> - F) E, but with software pre-installed?<br /> - G) any of the above, selling support for the software? - </p> - - <p>If it's easier, another way to look at this is: what conditions must - be met for the vendor to ship binaries under License Exception TSU, - and what expenses is the vendor allowed to recover costs and/or sell - at a profit?</p> -</blockquote> - -<p>Reasonable and customary fees for reproduction and distribution are -allowed, but not license fees or royalties. Support also is allowed, -subject to the above limitation.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - If the one-time review is required for unmodified binaries shipped - for-profit, can that approval be used by other vendors which are - shipping unmodified binaries? -</p> -</blockquote> - -<p>A one time review is for the product, and is vendor-independent.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - Would it be acceptable to set up an official mirror in a country - forbidden in EAR section 740.13(e)? -</p> -</blockquote> - -<p>You would have to apply for a license to set up an official mirror in an -embargoed country.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - If it is technically infeasible to block access from the T7 countries - to a web (or ftp, etc) server, does due diligence require extreme - measures? Does the defacto standard of (US) industry common-practice - meet due diligence? -</p> -</blockquote> - -<p>The de facto industry standard should suffice. I hope that the government -will recognize that any system devised by man can be defeated, with enough -effort.</p> - - -<blockquote class="question"> -<p> -<span>D:</span> - What steps should we take if we become aware of someone downloading - software into one of these countries from a mirror within the US? - What if we become aware of downloads into one of these countries - from a mirror outside the US? -</p> - <p>Some of our developers may live in or be citizens of the seven - countries forbidden for exemption TSU. Would it be a problem for - these developers to have access to cryptographic software on our - machines? Would we need to ask them not to download such software? - What steps should we take if we become aware of them downloading - cryptographic software?</p> -</blockquote> - -<p>Simply posting cryptographic software on a server that may be accessible -from an embargoed country does not constitute <q>knowledge</q> that the -software has been exported there. Therefore, criminal liability would -not apply to the act of posting. We recommend that you perform IP -checking and deny downloads to known embargoed countries. This due -diligence also would provide a defense to a claim of civil liability. -If you find out that your software has been downloaded to a prohibited -destination, then I recommend that you block future downloads to that -specific site unless and until you obtain a license from BXA.</p> - -<hr /> - -<p>Debian thanks the <a href="http://www.hp.com/">Hewlett-Packard</a> -<a href="http://www.hp.com/products1/linux/">Linux Systems Operation</a> -for their support in obtaining this legal opinion.</p> diff --git a/greek/legal/licenses/Makefile b/greek/legal/licenses/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/legal/licenses/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/legal/licenses/gpl2.wml b/greek/legal/licenses/gpl2.wml deleted file mode 100644 index 1f40c928950..00000000000 --- a/greek/legal/licenses/gpl2.wml +++ /dev/null @@ -1,482 +0,0 @@ -#use wml::debian::template title="GNU GENERAL PUBLIC LICENSE" NOCOPYRIGHT="true" -#use wml::debian::translation-check translation="d109ac4197d816202547b41d15ccf7b9e9e35b8e" maintainer="galaxico" - -<p><strong> -Version 2, June 1991 -</strong></p> - -<pre> -Copyright (C) 1989, 1991 Free Software Foundation, Inc. -51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA - -Everyone is permitted to copy and distribute verbatim copies -of this license document, but changing it is not allowed. - -</pre> - -<h3><a name="preamble"></a><a name="SEC2">Preamble</a></h3> - -<p> - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Lesser General Public License instead.) You can apply it to -your programs, too. -</p> - -<p> - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. -</p> - -<p> - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - -</p> - -<p> - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. -</p> - -<p> - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. -</p> - -<p> - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. -</p> - -<p> - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. -</p> - -<p> - The precise terms and conditions for copying, distribution and -modification follow. -</p> - - -<h3><a name="terms"></a><a name="SEC3">TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION</a></h3> - - -<a name="section0"></a><p> -<strong>0.</strong> - - This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". -</p> - -<p> -Activities other than copying, distribution and modification are not -covered by this License; they are outside its scope. The act of -running the Program is not restricted, and the output from the Program -is covered only if its contents constitute a work based on the -Program (independent of having been made by running the Program). -Whether that is true depends on what the Program does. -</p> - -<a name="section1"></a><p> -<strong>1.</strong> - You may copy and distribute verbatim copies of the Program's -source code as you receive it, in any medium, provided that you -conspicuously and appropriately publish on each copy an appropriate -copyright notice and disclaimer of warranty; keep intact all the -notices that refer to this License and to the absence of any warranty; -and give any other recipients of the Program a copy of this License -along with the Program. -</p> - -<p> -You may charge a fee for the physical act of transferring a copy, and -you may at your option offer warranty protection in exchange for a fee. - -</p> - -<a name="section2"></a><p> -<strong>2.</strong> - You may modify your copy or copies of the Program or any portion -of it, thus forming a work based on the Program, and copy and -distribute such modifications or work under the terms of Section 1 -above, provided that you also meet all of these conditions: -</p> - -<dl> - <dt> </dt> - <dd> - <strong>a)</strong> - - You must cause the modified files to carry prominent notices - stating that you changed the files and the date of any change. - </dd> - <dt> </dt> - <dd> - <strong>b)</strong> - You must cause any work that you distribute or publish, that in - whole or in part contains or is derived from the Program or any - part thereof, to be licensed as a whole at no charge to all third - parties under the terms of this License. - </dd> - <dt> </dt> - <dd> - - <strong>c)</strong> - If the modified program normally reads commands interactively - when run, you must cause it, when started running for such - interactive use in the most ordinary way, to print or display an - announcement including an appropriate copyright notice and a - notice that there is no warranty (or else, saying that you provide - a warranty) and that users may redistribute the program under - these conditions, and telling the user how to view a copy of this - License. (Exception: if the Program itself is interactive but - does not normally print such an announcement, your work based on - the Program is not required to print an announcement.) - </dd> -</dl> - -<p> -These requirements apply to the modified work as a whole. If -identifiable sections of that work are not derived from the Program, -and can be reasonably considered independent and separate works in -themselves, then this License, and its terms, do not apply to those -sections when you distribute them as separate works. But when you -distribute the same sections as part of a whole which is a work based -on the Program, the distribution of the whole must be on the terms of -this License, whose permissions for other licensees extend to the -entire whole, and thus to each and every part regardless of who wrote it. -</p> - -<p> -Thus, it is not the intent of this section to claim rights or contest -your rights to work written entirely by you; rather, the intent is to -exercise the right to control the distribution of derivative or -collective works based on the Program. -</p> - -<p> - -In addition, mere aggregation of another work not based on the Program -with the Program (or with a work based on the Program) on a volume of -a storage or distribution medium does not bring the other work under -the scope of this License. -</p> - -<a name="section3"></a><p> -<strong>3.</strong> - You may copy and distribute the Program (or a work based on it, -under Section 2) in object code or executable form under the terms of -Sections 1 and 2 above provided that you also do one of the following: -</p> - -<!-- we use this doubled UL to get the sub-sections indented, --> -<!-- while making the bullets as unobvious as possible. --> - -<dl> - <dt> </dt> - <dd> - - <strong>a)</strong> - Accompany it with the complete corresponding machine-readable - source code, which must be distributed under the terms of Sections - 1 and 2 above on a medium customarily used for software interchange; or, - </dd> - <dt> </dt> - <dd> - <strong>b)</strong> - Accompany it with a written offer, valid for at least three - years, to give any third party, for a charge no more than your - cost of physically performing source distribution, a complete - machine-readable copy of the corresponding source code, to be - distributed under the terms of Sections 1 and 2 above on a medium - customarily used for software interchange; or, - </dd> - <dt> </dt> - - <dd> - <strong>c)</strong> - Accompany it with the information you received as to the offer - to distribute corresponding source code. (This alternative is - allowed only for noncommercial distribution and only if you - received the program in object code or executable form with such - an offer, in accord with Subsection b above.) - </dd> -</dl> - -<p> -The source code for a work means the preferred form of the work for -making modifications to it. For an executable work, complete source -code means all the source code for all modules it contains, plus any -associated interface definition files, plus the scripts used to -control compilation and installation of the executable. However, as a -special exception, the source code distributed need not include -anything that is normally distributed (in either source or binary -form) with the major components (compiler, kernel, and so on) of the -operating system on which the executable runs, unless that component -itself accompanies the executable. -</p> - -<p> -If distribution of executable or object code is made by offering -access to copy from a designated place, then offering equivalent -access to copy the source code from the same place counts as -distribution of the source code, even though third parties are not -compelled to copy the source along with the object code. -</p> - -<a name="section4"></a><p> -<strong>4.</strong> - You may not copy, modify, sublicense, or distribute the Program -except as expressly provided under this License. Any attempt -otherwise to copy, modify, sublicense or distribute the Program is -void, and will automatically terminate your rights under this License. -However, parties who have received copies, or rights, from you under -this License will not have their licenses terminated so long as such -parties remain in full compliance. -</p> - -<a name="section5"></a><p> -<strong>5.</strong> - You are not required to accept this License, since you have not -signed it. However, nothing else grants you permission to modify or -distribute the Program or its derivative works. These actions are -prohibited by law if you do not accept this License. Therefore, by -modifying or distributing the Program (or any work based on the -Program), you indicate your acceptance of this License to do so, and -all its terms and conditions for copying, distributing or modifying -the Program or works based on it. -</p> - -<a name="section6"></a><p> -<strong>6.</strong> - - Each time you redistribute the Program (or any work based on the -Program), the recipient automatically receives a license from the -original licensor to copy, distribute or modify the Program subject to -these terms and conditions. You may not impose any further -restrictions on the recipients' exercise of the rights granted herein. -You are not responsible for enforcing compliance by third parties to -this License. -</p> - -<a name="section7"></a><p> -<strong>7.</strong> - If, as a consequence of a court judgment or allegation of patent -infringement or for any other reason (not limited to patent issues), -conditions are imposed on you (whether by court order, agreement or -otherwise) that contradict the conditions of this License, they do not -excuse you from the conditions of this License. If you cannot -distribute so as to satisfy simultaneously your obligations under this -License and any other pertinent obligations, then as a consequence you -may not distribute the Program at all. For example, if a patent -license would not permit royalty-free redistribution of the Program by -all those who receive copies directly or indirectly through you, then -the only way you could satisfy both it and this License would be to -refrain entirely from distribution of the Program. -</p> - -<p> -If any portion of this section is held invalid or unenforceable under -any particular circumstance, the balance of the section is intended to -apply and the section as a whole is intended to apply in other -circumstances. -</p> - -<p> -It is not the purpose of this section to induce you to infringe any -patents or other property right claims or to contest validity of any -such claims; this section has the sole purpose of protecting the -integrity of the free software distribution system, which is -implemented by public license practices. Many people have made -generous contributions to the wide range of software distributed -through that system in reliance on consistent application of that -system; it is up to the author/donor to decide if he or she is willing -to distribute software through any other system and a licensee cannot -impose that choice. - -</p> - -<p> -This section is intended to make thoroughly clear what is believed to -be a consequence of the rest of this License. -</p> - -<a name="section8"></a><p> -<strong>8.</strong> - If the distribution and/or use of the Program is restricted in -certain countries either by patents or by copyrighted interfaces, the -original copyright holder who places the Program under this License -may add an explicit geographical distribution limitation excluding -those countries, so that distribution is permitted only in or among -countries not thus excluded. In such case, this License incorporates -the limitation as if written in the body of this License. -</p> - -<a name="section9"></a><p> -<strong>9.</strong> - The Free Software Foundation may publish revised and/or new versions -of the General Public License from time to time. Such new versions will -be similar in spirit to the present version, but may differ in detail to -address new problems or concerns. - -</p> - -<p> -Each version is given a distinguishing version number. If the Program -specifies a version number of this License which applies to it and "any -later version", you have the option of following the terms and conditions -either of that version or of any later version published by the Free -Software Foundation. If the Program does not specify a version number of -this License, you may choose any version ever published by the Free Software -Foundation. -</p> - -<a name="section10"></a><p> -<strong>10.</strong> - If you wish to incorporate parts of the Program into other free -programs whose distribution conditions are different, write to the author -to ask for permission. For software which is copyrighted by the Free -Software Foundation, write to the Free Software Foundation; we sometimes -make exceptions for this. Our decision will be guided by the two goals -of preserving the free status of all derivatives of our free software and -of promoting the sharing and reuse of software generally. -</p> - -<a name="section11"></a><p><strong>NO WARRANTY</strong></p> - -<p> - -<strong>11.</strong> - BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY -FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN -OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES -PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED -OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF -MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS -TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE -PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, -REPAIR OR CORRECTION. -</p> - -<a name="section12"></a><p> -<strong>12.</strong> - IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING -WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR -REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, -INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING -OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED -TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY -YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER -PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE -POSSIBILITY OF SUCH DAMAGES. -</p> - -<h3>END OF TERMS AND CONDITIONS</h3> - -<h3><a name="howto"></a><a name="SEC4">How to Apply These Terms to Your New Programs</a></h3> - -<p> - If you develop a new program, and you want it to be of the greatest -possible use to the public, the best way to achieve this is to make it -free software which everyone can redistribute and change under these terms. -</p> - -<p> - To do so, attach the following notices to the program. It is safest -to attach them to the start of each source file to most effectively -convey the exclusion of warranty; and each file should have at least -the "copyright" line and a pointer to where the full notice is found. -</p> - -<pre> -<var>one line to give the program's name and an idea of what it does.</var> -Copyright (C) <var>yyyy</var> <var>name of author</var> - -This program is free software; you can redistribute it and/or -modify it under the terms of the GNU General Public License -as published by the Free Software Foundation; either version 2 -of the License, or (at your option) any later version. - -This program is distributed in the hope that it will be useful, -but WITHOUT ANY WARRANTY; without even the implied warranty of -MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the -GNU General Public License for more details. - -You should have received a copy of the GNU General Public License -along with this program; if not, write to the Free Software -Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. -</pre> - -<p> -Also add information on how to contact you by electronic and paper mail. -</p> - -<p> -If the program is interactive, make it output a short notice like this -when it starts in an interactive mode: -</p> - -<pre> -Gnomovision version 69, Copyright (C) <var>year</var> <var>name of author</var> - -Gnomovision comes with ABSOLUTELY NO WARRANTY; for details -type `show w'. This is free software, and you are welcome -to redistribute it under certain conditions; type `show c' -for details. -</pre> - -<p> -The hypothetical commands <samp>`show w'</samp> and <samp>`show c'</samp> should show -the appropriate parts of the General Public License. Of course, the -commands you use may be called something other than <samp>`show w'</samp> and -<samp>`show c'</samp>; they could even be mouse-clicks or menu items--whatever -suits your program. -</p> - -<p> -You should also get your employer (if you work as a programmer) or your -school, if any, to sign a "copyright disclaimer" for the program, if -necessary. Here is a sample; alter the names: -</p> - - -<pre> -Yoyodyne, Inc., hereby disclaims all copyright -interest in the program `Gnomovision' -(which makes passes at compilers) written -by James Hacker. - -<var>signature of Ty Coon</var>, 1 April 1989 -Ty Coon, President of Vice -</pre> diff --git a/greek/legal/licenses/index.wml b/greek/legal/licenses/index.wml deleted file mode 100644 index e7539559939..00000000000 --- a/greek/legal/licenses/index.wml +++ /dev/null @@ -1,132 +0,0 @@ -#use wml::debian::template title="License information" GEN_TIME="yes" -#use wml::debian::translation-check translation="1aeaee4127e2958298108243a68a54e7e17edb99" maintainer="galaxico" - -<p>This page presents the opinion of some debian-legal contributors on how -certain licenses follow the -<a href="$(HOME)/social_contract#guidelines">Debian Free Software -Guidelines</a> (DFSG). Most of these opinions were formed in -discussions on the <a href="https://lists.debian.org/debian-legal/">\ -debian-legal mailing list</a> in response to questions from -potential package maintainers or licensors. We welcome -enquiries from maintainers considering particular licenses, but -we encourage most maintainers to use one of the common licenses: -GPL, LGPL, modified BSD, or Artistic.</p> - -<p>Software packaged for Debian is normally classified into one of four -categories. There is free software (main), non-free software -(non-free), free software which depends on some non-free -software (contrib) and software which cannot be redistributed -(not included). -<a href="$(DOC)/debian-policy/ch-archive.html">Debian Policy section 2</a> -explains exactly how the DFSG -are applied to the archive. If in doubt, maintainers are -asked to email debian-legal about licenses, including the text -of any new license into the body of the email. -You may find it helpful to -<a href="https://lists.debian.org/search.html">search the list archives</a> -for the name of the license before emailing lists with questions -about it. If you still email questions, please link to some of -the previous relevant discussions.</p> - -<p>debian-legal is advisory. The actual decision-makers are the -ftpmasters and the package maintainers. However, if one cannot -convince most of the generally liberal debian-legal contributors, -it's probably not clear that the software follows the DFSG.</p> - -<p>Because the actual decision-makers are the -ftpmasters and the package maintainers, it is a very good idea -to check -<a href="https://ftp-master.debian.org/REJECT-FAQ.html">the ftpmasters REJECT FAQ</a> -and search site:packages.debian.org for any license that you doubt, -to look for other examples of its handling for debian. -(The search works because package copyright files are published on -packages.debian.org as plain text.)</p> - -<p>Other lists are maintained by the -<a href="https://www.gnu.org/licenses/license-list">Free Software -Foundation</a> (FSF) and the -<a href="https://opensource.org/licenses/">Open Source -Initiative</a> (OSI). Please note however, that -the Debian project decides on particular packages rather than -licenses in abstract, and the lists are general explanations. It -is possible to have a package containing software under a -"free" license with some other aspect that makes it non-free. -Sometimes, debian-legal comments on a license in abstract, not -applied to any particular software. While these discussion -can suggest possible problems, often no firm answers can be -reached until some specific software is examined.</p> - -<p>You may contact debian-legal if you have questions or comments -about these summaries.</p> - -<p>Licenses currently found in Debian main include:</p> - -<ul> -<li><a href="https://www.gnu.org/licenses/gpl.html">GNU General Public License</a> (common)</li> -<li><a href="https://www.gnu.org/licenses/lgpl.html">GNU Lesser General Public License</a> (common)</li> -<li>GNU Library General Public License (common)</li> -<li><a href="https://opensource.org/licenses/BSD-3-Clause">Modified BSD License</a> (common)</li> -<li><a href="http://www.perl.com/pub/a/language/misc/Artistic.html">Perl Artistic license</a> (common)</li> -<li><a href="http://www.apache.org/licenses/">Apache License</a></li> -<li><a href="http://www.jclark.com/xml/copying.txt">Expat/MIT-style licenses</a></li> -<li><a href="https://zlib.org/zlib_license.html">zlib-style licenses</a></li> -<li><a href="http://www.latex-project.org/lppl/">LaTeX Project Public License</a></li> -<li><a href="http://www.python.org/download/releases/2.5.2/license/">Python Software Foundation License</a></li> -<li><a href="http://www.ruby-lang.org/en/LICENSE.txt">Ruby's License</a></li> -<li><a href="http://www.php.net/license/">PHP License</a></li> -<li><a href="http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231">W3C Software Notice and License</a></li> -<li><a href="http://www.openssl.org/source/license.html">OpenSSL License</a></li> -<li><a href="https://opensource.org/licenses/Sleepycat">Sleepycat License</a></li> -<li><a href="http://www.cups.org/book/examples/LICENSE.txt">Common UNIX Printing System License Agreement</a></li> -<li>vhf Public License</li> -<li><a href="http://tunes.org/legalese/bugroff.html">"No problem Bugroff" license</a></li> -<li>Unmodified BSD License (also known as the -original or 4-clause BSD license. -It included an advertising requirement and is now deprecated even -by the BSD project.)</li> -<li>public domain (not a license, strictly speaking)</li> -<li><a href="http://www.openafs.org/frameset/dl/license10.html">IBM Public License Version 1.0</a></li> -</ul> - -<p>If you use one of these licenses, -please try to use the latest version and edit no more than necessary, -unless indicated otherwise. -Licenses marked (common) can be found in <tt>/usr/share/common-licenses</tt> -on a Debian system.</p> - -<p>Licenses currently found in the non-free archive section include:</p> - -<ul> -<li>NVIDIA Software License</li> -<li>SCILAB License</li> -<li>Limited Use Software License Agreement</li> -<li>Non-Commercial License</li> -<li>FastCGI / Open Market License</li> -<li>LaTeX2HTML License</li> -<li>Open Publication License</li> -<li>Free Document Dissemination License</li> -<li>AT&T Open Source License</li> -<li>Apple Public Source License</li> -<li>Aladdin Free Public License</li> -<li>Generic amiwm License (an XV-style license)</li> -<li>Digital License Agreement</li> -<li>Moria/Angband license</li> -<li>Unarj License</li> -<li>id Software License</li> -<li>qmail terms</li> -</ul> - -<p>Please do not upload software under these licenses to the -main archive.</p> - -<p>Additionally, some software is not distributable (for example, -has no license at all), even in non-free.</p> - - -<h2>Work in Progress</h2> - -<p>For help with interpreting the DFSG, you should check the -<a href="https://people.debian.org/~bap/dfsg-faq">DFSG FAQ</a> -that answers some common questions about the DFSG and how to analyse -software.</p> - diff --git a/greek/legal/licenses/mit.wml b/greek/legal/licenses/mit.wml deleted file mode 100644 index b631a9f15ae..00000000000 --- a/greek/legal/licenses/mit.wml +++ /dev/null @@ -1,24 +0,0 @@ -#use wml::debian::template title="MIT License (Expat)" NOCOPYRIGHT="true" -#use wml::debian::translation-check translation="5425c35dc1781f6f22e3c8d056fbde54079fca34" maintainer="galaxico" - -<p> -Permission is hereby granted, free of charge, to any person obtaining a copy -of this software and associated documentation files (the "Software"), to deal -in the Software without restriction, including without limitation the rights -to use, copy, modify, merge, publish, distribute, sublicense, and/or sell -copies of the Software, and to permit persons to whom the Software is -furnished to do so, subject to the following conditions: -</p> -<p> -The above copyright notice and this permission notice shall be included in -all copies or substantial portions of the Software. -</p> -<p> -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR -IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, -FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE -AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER -LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, -OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN -THE SOFTWARE. -</p> diff --git a/greek/legal/notificationforarchive.wml b/greek/legal/notificationforarchive.wml deleted file mode 100644 index 7cca3d3d682..00000000000 --- a/greek/legal/notificationforarchive.wml +++ /dev/null @@ -1,65 +0,0 @@ -#use wml::debian::template title="Unrestricted Encryption Source Code Notification" BARETITLE=true -#use wml::debian::translation-check translation="8da95139c3595d47371ba8d288784086ae2ebacd" maintainer="galaxico" - -# Nota bene! This is basically draft text from the lawyers, and it must -# _not_ be modified for spelling errors and such. Formatting changes are -# fine (I think). -- Joy - -<table border=0 width="100%" summary="mail headers"> -<colgroup span="2"> -<col width="10%"> -<col> -<tr><td>To:</td> <td><email crypt@bxa.doc.gov></td></tr> -<tr><td>Subject:</td> <td>Initial one-time notification for Debian GNU/Linux</td></tr> -</table> - -<p class="right"> - Department of Commerce<br> - Bureau of Export Administration<br> - Office of Strategic Trade and Foreign Policy Controls<br> - 14th Street and Pennsylvania Ave., N.W.<br> - Room 2705<br> - Washington, DC 20230<br> -</p> - -<p><strong>Re: Unrestricted Encryption Source Code Notification -Commodity: Debian Source Code</strong></p> - -<p>Dear Sir/Madam,</p> - -<p> -Pursuant to paragraph (e)(1) of Part 740.13 of the U.S. Export -Administration Regulations ("EAR", 15 CFR Part 730 et seq.), we are -providing this written notification of the Internet location of the -unrestricted, publicly available Source Code of packages in the Debian -operating system. Debian is a free operating system developed by a group -of individuals, coordinated by the non-profit Software in the Public -Interest. This archive is updated from time to time, but its location -is constant. At present, the software listed in this notification does -not include cryptographic functionality, however we expect cryptographic -functionality to be added to much of it in future. Therefore this -notification serves as a one-time notification for subsequent updates -that may occur in the future to software covered by this notification. -Such updates may add or enhance cryptographic functionality of the -Debian operating system. Additional notifications will be submitted as -new components are added to the Debian operating system. The Internet -location for the Debian Source Code is: http://ftp.debian.org/debian/</p> - -<p>This site is mirrored to a number of other sites located both within -and outside the United States.</p> - -<p>Descriptions of the contents of the Debian archive are -<a href="https://ftp-master.debian.org/crypto-in-main/archive_contents.txt">attached</a>.</p> - -<p>Further information about the Debian project is available at -<a href="$(HOME)/">https://www.debian.org/</a></p> - -<p>If you have any questions, please contact Ben Collins, via email at -xxx@xxx, or telephone on (XXX) XXX-XXXX.</p> - -<pre><cite> - Sincerely, - Ben Collins (Project Leader) - and Anthony Towns (Release Manager) - for the Debian Project -</cite></pre> diff --git a/greek/legal/notificationfornewpackages.wml b/greek/legal/notificationfornewpackages.wml deleted file mode 100644 index 5e289704e98..00000000000 --- a/greek/legal/notificationfornewpackages.wml +++ /dev/null @@ -1,66 +0,0 @@ -#use wml::debian::template title="Unrestricted Encryption Source Code Notification" BARETITLE=true -#use wml::debian::translation-check translation="16f8863b5a80b644458dbf8f2ffc4ef0ef0644e8" maintainer="galaxico" - -# Nota bene! This is basically draft text from the lawyers, and it must -# _not_ be modified for spelling errors and such. Formatting changes are -# fine (I think). -- Joy - -<table border=0 width="100%" summary="mail headers"> -<colgroup span="2"> -<col width="10%"> -<col> -<tr><td>To:</td> <td><email crypt@bxa.doc.gov></td></tr> -<tr><td>Subject:</td> <td>Addition to <var>__DISTRO__</var> Source Code</td></tr> -</table> - -<p class="right"> - Department of Commerce<br> - Bureau of Export Administration<br> - Office of Strategic Trade and Foreign Policy Controls<br> - 14th Street and Pennsylvania Ave., N.W.<br> - Room 2705<br> - Washington, DC 20230<br> -</p> - -<p><strong>Re: Unrestricted Encryption Source Code Notification -Commodity: Addition to Debian Source Code</strong></p> - -<p>Dear Sir/Madam,</p> - -<p> -Pursuant to paragraph (e)(1) of Part 740.13 of the U.S. Export -Administration Regulations ("EAR", 15 CFR Part 730 et seq.), we are -providing this written notification of the Internet location of the -unrestricted, publicly available Source Code of a package being added -to the Debian Source Code. Debian Source Code is a free operating -system developed by a group of individuals, coordinated by the -non-profit Software in the Public Interest. This notification serves -as a notification of an addition of new software to the Debian -archive. Previous notifications have covered the archive as a whole -and other software added in the past. This archive is updated from -time to time, but its location is constant. Therefore this -notification serves as a one-time notification for subsequent updates -that may occur in the future to the software covered by this -notification. Such updates may add or enhance cryptographic -functionality of the Debian operating system. The Internet location -for the Debian Source Code is: http://ftp.debian.org/debian/</p> - -<p>This site is mirrored to a number of other sites located outside the -United States.</p> - -<p>The following software is being added to the Debian archive:</p> - -<pre> ----------------------------------------------------------------------- -<var>__BINARY_DESCRIPTIONS__</var> ----------------------------------------------------------------------- -</pre> - -<p>If you have any questions, please email me at xxx@xxx, -or call me on (XXX) XXX-XXXX.</p> - -<pre><cite> - Sincerely, - Ben Collins - Debian Developer -</cite></pre> diff --git a/greek/legal/patent.wml b/greek/legal/patent.wml deleted file mode 100644 index 424dc148a02..00000000000 --- a/greek/legal/patent.wml +++ /dev/null @@ -1,83 +0,0 @@ -#use wml::debian::template title="Debian Position on Software Patents" BARETITLE="true" -#use wml::debian::translation-check translation="088c528e5eb9d95504ef91aa449795178ac06be1" maintainer="galaxico" - -<pre><code>Version: 1.0 -Published: 19 February 2012 -</code></pre> - - -<h1>Introduction</h1> - -<p>This document describes Debian's position on patents. Debian recognizes the -threat that patents pose to Free Software, and continues to work with others in -the Free Software community on patent defense.</p> - -<p>The policy included below intends to provide clear and useful guidance for -community members confronted with patent issues, so that the Debian community -can coordinate its patent defense free from fear, uncertainty, and doubt.</p> - - -<h1>Policy Statement</h1> - -<ol> - -<li><p>Debian will not knowingly distribute software encumbered by patents; - Debian contributors should not package or distribute software they know to - infringe a patent.</p></li> - -<li><p>Debian will not accept a patent license that is inconsistent with - the <a href="$(HOME)/social_contract">Debian Social Contract</a> - or <a href="$(HOME)/social_contract#guidelines">Debian Free Software - Guidelines</a>.</p></li> - -<li><p>Unless communications related to patents are subject to attorney-client - privilege, community members may be forced to produce them in a lawsuit. - Also, patent concerns expressed publicly may turn out to be unfounded but - create a good deal of fear, uncertainty, and doubt in the meantime. - Therefore, please refrain from posting patent concerns publicly or - discussing patents outside of communication with legal counsel, where they - are subject to attorney-client privilege.</p></li> - -<li><p>Patent risks affect the entire community. If you are concerned about a - specific patent, please do not keep it to yourself — notify legal - counsel.</p></li> - -<li><p>All communication related to specific patent risk should be directed to - <a href="mailto:patents@debian.org">patents@debian.org</a>, which is - maintained under the rules of attorney-client privilege. The risk will be - evaluated and any necessary response will be made directly to affected - parties.</p></li> - -</ol> - - -<h1>Contact Information</h1> - -<p>In case you want to contact us about specific patent risks in the Debian -archive, please mail <a href="mailto:patents@debian.org">patents@debian.org</a> -mentioning:</p> - -<ul> -<li>your name,</li> -<li>your role in Debian,</li> -<li>the name of the involved packages or projects,</li> -<li>the title, number, and jurisdiction of the involved patent(s),</li> -<li>a narrative of your concerns.</li> -</ul> - - -<h1>Further Information</h1> - -<p>For further information on patents and how they interact with community Free -Software distributions we recommend reading our -<a href="$(HOME)/reports/patent-faq">Community Distribution Patent Policy -FAQ</a>, a document meant to educate Free Software developers, and especially -distribution editors, about software patent risks.</p> - - -<hr /> - -<p>The Debian Project thanks -the <a href="http://www.softwarefreedom.org">Software Freedom Law Center</a> -(SFLC) for their legal advice on these matters.</p> - diff --git a/greek/legal/privacy.wml b/greek/legal/privacy.wml deleted file mode 100644 index fc86f8e0557..00000000000 --- a/greek/legal/privacy.wml +++ /dev/null @@ -1,313 +0,0 @@ -#use wml::debian::template title="Privacy Policy" NOCOMMENTS="yes" -#use wml::debian::translation-check translation="1b02209a4926cd501ca7c0996d9295f8aa18d354" maintainer="galaxico" - -## Translators may want to add a note stating that the translation -## is only informative and has no legal value, and people -## should look at the original English for that. -## Some languages have already put such a note in the -## translations of /trademark and /license, for example. - -<p>The <a href="https://www.debian.org/">Debian Project</a> is a volunteer -association of individuals who have made common cause to create a free -operating system, referred to as Debian. </p> - -<p>There is no requirement for anyone who -wishes to use Debian to provide the project with any personal information; it -is freely downloadable without registration or other form of identification -from both official mirrors run by the project and numerous third parties.</p> - -<p>Various other aspects of interacting with the Debian Project will, however, -involve the collection of personal information. This is primarily in the form -of names and email addresses in emails received by the project; all Debian -mailing lists are publicly archived, as are all interactions with the bug -tracking system. This is in keeping with our <a -href="https://www.debian.org/social_contract">Social Contract</a>, in -particular our statement that we will give back to the free software community -(#2), and that we will not hide our problems (#3). We do not perform further -processing on any of the information we hold, but there are instances where it -is automatically shared with third parties (such as emails to lists, or -interactions with the bug tracking system).</p> - -<p>The list below categorises the various services run by the project, the -information used by those services and the reasons it is required.</p> - -<p>Questions about these services are best directed in the first instance to the -service owner. If it's unclear who that is then you can contact the Data Protection -team at <a href="mailto:data-protection@debian.org">data-protection@debian.org</a>, -who will attempt to direct your enquiry to the right team.</p> - -<p>Please note that (unless stated otherwise on this page) hosts and -services under the <strong>debian.net</strong> domain are not part of the -official Debian project; -they are run by individuals who have an association with the project rather -than the project themselves. -Questions about exactly what data those services hold should be directed -at the service owners rather than the Debian Project itself.</p> - -<h2>Contributors (<a href="https://contributors.debian.org/">contributors.debian.org</a>)</h2> - -<p>The Debian Contributors site provides an aggregation of data about where -someone has contributed to the Debian Project, whether that's through filing a -bug report, making an upload to the archive, posting to a mailing list or -various other interactions with the Project. It receives its information from -the services in question (details about an identifier such as login name and -time of last contribution) and provides a single reference point to see where -the Project is storing information about an individual.</p> - -<h2>The Archive (<a href="https://ftp.debian.org/debian/">ftp.debian.org</a>)</h2> - -<p>The primary distribution method of Debian is via its public archive network. -The archive consists of all of the binary packages and their associated source -code, which will include personal information in the form of names and email -addresses stored as part of changelogs, copyright information, and general -documentation. The majority of this information is provided via the upstream -software authors distributed source code, with Debian adding additional -information to track authorship and copyright to ensure that licenses are being -correctly documented and the Debian Free Software Guidelines adhered to.</p> - -<h2>Bug Tracking System (<a href="https://bugs.debian.org/">bugs.debian.org</a>)</h2> - -<p>The bug tracking system is interacted with via email, and stores all emails -received in relation to a bug as part of that bug's history. In order that the -project can effectively deal with issues found in the distribution, and to -enable users to see details about those issues and whether a fix or workaround -is available, the entirety of the bug tracking system is openly accessible. -Therefore any information, including names and email addresses as part of email -headers, sent to the BTS will be archived and publicly available.</p> - -<h2>DebConf (<a href="https://www.debconf.org/">debconf.org</a>)</h2> - -<p>The DebConf registration structure stores the details of conference -attendees. These are required to determine eligibility to bursaries, association -to the project, and to contact attendees with appropriate details. They may -also be shared with suppliers to the conference, e.g. attendees staying in the -conference provided accommodation will have their name and attendance date -shared with the accommodation provider.</p> - -<h2>Developers LDAP (<a href="https://db.debian.org">db.debian.org</a>)</h2> - -<p>Project contributors (developers and others with guest accounts) who -have account access to machines within the Debian infrastructure have -their details stored within the project's LDAP infrastructure. This -primarily stores name, username and authentication information. However -it also has the optional facility for contributors to provide additional -information such as gender, instant messaging (IRC/XMPP), country and -address or phone details, and a message if they are on vacation. -</p> - -<p> -Name, username and some of the voluntarily provided details -are freely available via the web interface or LDAP search. Additional -details are only shared with other individuals who have account access -to the Debian infrastructure and is intended to provide a centralised -location for project members to exchange such contact information. It is -not explicitly collected at any point and can always be removed by -logging into the db.debian.org web interface or sending signed email to -the email interface. See <a href="https://db.debian.org/">https://db.debian.org/</a> and -<a href="https://db.debian.org/doc-general.html">https://db.debian.org/doc-general.html</a> for more details. -</p> - -<h2>Gitlab (<a href="https://salsa.debian.org/">salsa.debian.org</a>)</h2> - -<p>salsa.debian.org provides an instance of the <a -href="https://about.gitlab.com/">GitLab</a> DevOps lifecycle management tool. -It is primarily used by the Project to allow Project contributors to host -software repositories using Git and encourage collaboration between -contributors. As a result it requires various pieces of personal information to -manage accounts. For Project members this is tied to the central Debian LDAP -system, but guests may also register for an account and will have to provide -name and email details in order to facilitate the setup and use of that -account.</p> - -<p>salsa's primary purpose is to manage our git history. See below.</p> - -<h2><a name="git">git</a></h2> - -<p>Debian maintains multiple git servers, containing source code and -similar materials, and their revision and contribution histories. -Individual Debian contributors also typically -have information managed in git.</p> - -<p>git history contains the name and email address of contributors -(including bug reporters, authors, reviewers, and so on). -git retains this information permanently in an append-only history. -We use an append-only history because it has important integrity -properties, notably significant protection against untracked changes. -We retain it indefinitely so that we can always verify the copyright -and other legal status of contributions, and so that we can always -identify the originators for software integrity reasons. - -<p>The append-only nature of the git system implies that that any -modification to these commit details once they are incorporated into -the repository is extremely disruptive and in some cases (such as when -signed commits are in use) impossible. So we avoid this in all but -extreme cases. -Where appropriate, we use git features (eg <code>mailmap</code>) -to arrange that historical personal information, though it is retained, -can be elided or corrected when it is displayed or used. -</p> - -<p>Unless there are exceptional reasons to do otherwise, -Debian's git histories, -including the associated personal information about contributors, -are completely public.</p> - -<h2>Gobby (<a href="https://gobby.debian.org/">gobby.debian.org</a>)</h2> - -<p>Gobby is a collaborative online text editor, which tracks contributions and -changes against connected users. No authentication is required to connect to -the system and users may choose any username they wish. However while no -attempt is made by the service to track who owns usernames it should be -understand that it may prove possible to map usernames back to individuals -based upon common use of that username or the content they post to a -collaborative document within the system.</p> - -<h2>Mailing Lists (<a href="https://lists.debian.org/">lists.debian.org</a>)</h2> - -<p>Mailing lists are the primary communication mechanism of the Debian Project. -Almost all of the mailing lists related to the project are open, and thus -available for anyone to read and/or post to. All lists are also archived; for -public lists this means in a web accessible manner. This fulfils the project -commitment to transparency, and helps our users and developers understand -what is happening in the project, or understand the historical reasons for -certain aspects of the project. Due to the nature of email these archives -will therefore potentially hold personal information, such as names and -email addresses.</p> - -<h2>Alioth Lists -(<a href="https://alioth-lists.debian.net/">alioth-lists.debian.net</a>)</h2> - -<p>Alioth Lists provides additional, subject-specific mailing lists for -the Debian Project. Most of the mailing lists on this system project are -open, and thus available for anyone to read and/or post to. Many lists are -also archived; for public lists this means in a web accessible manner. -This fulfils the project commitment to transparency, and helps our users -and developers understand what is happening in the project, or understand -the historical reasons for certain aspects of the project. Due to the -nature of email these archives will therefore potentially hold personal -information, such as names and email addresses.</p> - -<p>The Alioth Lists service is also known as <tt>lists.alioth.debian.org</tt>.</p> - -<h2>New Members site (<a href="https://nm.debian.org/">nm.debian.org</a>)</h2> - -<p>Contributors to the Debian Project who wish to formalise their involvement -may choose to apply to the New Members process. This allows them to gain the -ability to upload their own packages (via Debian Maintainership) or to become -full voting members of the Project with account rights (Debian Developers, in -uploading and non-uploading variants). As part of this process various personal -details are collected, starting with name, email address and -encryption/signature key details. Full Project applications also involve the -applicant engaging with an Application Manager who will undertake an email -conversation to ensure the New Member understands the principles behind Debian -and has the appropriate skills to interact with the Project infrastructure. -This email conversation is archived and available to the applicant and -Application Managers via the nm.debian.org interface. Additionally details of -outstanding applicants are publicly visible on the site, allowing anyone to see -the state of New Member processing within the Project to ensure an appropriate -level of transparency.</p> - -<h2>Popularity Contest (<a href="https://popcon.debian.org/">popcon.debian.org</a>)</h2> - -<p>"popcon" tracks which packages are installed on a Debian system, to enable -the gathering of statistics about which packages are widely used and which are -no longer in use. It uses the optional "popularity-contest" package to collect -this information, requiring explicit opt-in to do so. This provides useful -guidance about where to devote developer resources, for example when migrating -to newer library versions and having to spend effort on porting older -applications. Each popcon instance generates a random 128 bit unique ID which -is used to track submissions from the same host. No attempt is made to map this -to an individual about submissions are made via email or HTTP and it is thus -possible for personal information to leak in the form of the IP address used -for access or email headers. This information is only available to the Debian -System Administrators and popcon admins; all such meta-data is removed before -submissions are made accessible to the project as a whole. However users should -be aware that unique signatures of packages (such as locally created packages -or packages with very low install counts) may make machines deducible as -belonging to particular individuals.</p> - -<p>Raw submissions are stored for 24 hours, to allow replaying in the event of -issues with the processing mechanisms. Anonymized submissions are kept for at -most 20 days. Summary reports, which contain no personally identifiable -information, are kept indefinitely.</p> - -<h2>snapshot (<a href="http://snapshot.debian.org/">snapshot.debian.org</a>)</h2> - -<p>The snapshot archive provides a historical view of the Debian archive -(ftp.debian.org above), allowing access to old packages based on dates and -version numbers. It carries no additional information over the main archive -(and can thus contain personal information in the form of names + email address -within changelogs, copyright statements and other documentation), but can -contain packages that are no longer part of shipping Debian releases. This -provides a useful resource to developers and users when tracking down -regressions in software packages, or providing a specific environment to run a -particular application.</p> - -<h2>Votes (<a href="https://vote.debian.org/">vote.debian.org</a>)</h2> - -<p>The vote tracking system (devotee) tracks the status of ongoing General -Resolutions and the results of previous votes. In the majority of cases this -means that once the voting period is over details of who voted (usernames + -name mapping) and how they voted becomes publicly visible. Only Project -members are valid voters for the purposes of devotee, and only valid votes are -tracked by the system.</p> - -<h2>Wiki (<a href="https://wiki.debian.org/">wiki.debian.org</a>)</h2> - -<p>The Debian Wiki provides a support and documentation resource for the -Project which is editable by everyone. As part of that contributions are -tracked over time and associated with user accounts on the wiki; each -modification to a page is tracked to allow for errant edits to be reverted and -updated information to be easily examined. This tracking provides details of -the user responsible for the change, which can be used to prevent abuse by -blocking abusive users or IP addresses from making edits. User accounts also -allow users to subscribe to pages to watch for changes, or see details of -changes throughout the entire wiki since they last checked. In general user -accounts are named after the name of the user, but no validation is performed -of the account names and a user may choose any free account name. An email -address is required for the purposes of providing a mechanism for account -password reset, and notifying the user of any changes on pages they are -subscribed to.</p> - -<h2>dgit git server (<a href="https://browse.dgit.debian.org/">*.dgit.debian.org</a>)</h2> - -<p>The dgit git server is the repository of the git (revision control) -histories of packages uploaded to Debian via <code>dgit -push</code>, used by <code>dgit clone</code>. -It contains similar information to the Debian -archive and the Salsa gitlab instance: copies of (and past snapshots -of) of the same information - in git format. -Except for packages which are being first-time reviewed by Debian -ftpmasters for inclusion in Debian: all this git information is always -public, and retained forever. -See <a href="#git">git</a>, above.</p> - -<p>For access control purposes, there is a hand-maintained list of the -ssh public keys of Debian Maintainers who have asked to be added. -This manually maintained list is not public. We hope to retire it and -instead use complete data maintained by another Debian service.</p> - -<h2>Echelon</h2> - -<p>Echelon is a system used by the Project to track member activity; in -particular it watches the mailing list and archive infrastructures, looking for -posts and uploads to record that a Debian member is active. Only the most -recent activity is stored, in the member's LDAP record. It is thus limited to -only tracking details of individuals who have accounts within the Debian -infrastructure. This information is used when determining if a project member -is inactive or missing and thus that there might be an operational requirement -to lock their account or otherwise reduce their access permissions to ensure -Debian systems are kept secure.</p> - -<h2>Service related logging</h2> - -<p>In addition to the explicitly listed services above the Debian -infrastructure logs details about system accesses for the purposes of ensuring -service availability and reliability, and to enable debugging and diagnosis of -issues when they arise. This logging includes details of mails sent/received -through Debian infrastructure, web page access requests sent to Debian -infrastructure, and login information for Debian systems (such as SSH logins to -project machines). None of this information is used for any purposes other than -operational requirements and it is only stored for 15 days in the case of web -server logs, 10 days in the case of mail log and 4 weeks in the case of -authentication/ssh logs.</p> diff --git a/greek/license.wml b/greek/license.wml deleted file mode 100644 index 9033f88f642..00000000000 --- a/greek/license.wml +++ /dev/null @@ -1,42 +0,0 @@ -#use wml::debian::template title="Debian WWW Pages License" NOCOPYRIGHT="true" BARETITLE="true" -#use wml::debian::translation-check translation="94c775a38ae2efdeac87af56fe60a8b27ea0992e" maintainer="galaxico" - -# Note to translators: you are free to link to <a href="license.en.html">the -# original license</a> here -- this is legal text and only the original -# version is authoritative. In fact, you needn't even bother translating this. - -<div class="centerblock"> -<p>Copyright © 1997-$(CUR_YEAR) -<a href="https://www.spi-inc.org/">Software in the Public Interest, Inc.</a> and others<br /> -SPI can be contacted at:<br /> -1732 1st Ave #20327<br /> -New York, NY 10128-5177<br /> -United States -</p> -</div> - -<p> -Since 25 January 2012, the new material can be redistributed and/or -modified under the terms of the <a href="legal/licenses/mit">\ -MIT (Expat) License</a> or, at your option, of the <a -href="legal/licenses/gpl2">GNU General Public License</a>; either version 2 -of the License, or (at your option) any later version (the latest version -is usually available at <url https://www.gnu.org/licenses/gpl.html>). -</p> - -<p> -Work is in progress to make the older material compliant -with the above licenses. Until then, please refer to the -following terms of the Open Publication License. -</p> - -<p>This material may be distributed only subject to the terms and conditions set -forth in the Open Publication License, Draft v1.0 or later (you can -read our <a href="opl">local copy</a>, the latest version -is usually available at -<a href="http://www.opencontent.org/openpub/">http://www.opencontent.org/openpub/</a>). -</p> - -<p>“Debian” and <a href="logos/">the Debian Logo</a> are <a -href="$(HOME)/trademark">trademarks</a> of Software in the Public Interest, -Inc.</p> diff --git a/greek/mirror/Makefile b/greek/mirror/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/mirror/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/mirror/ftpmirror.wml b/greek/mirror/ftpmirror.wml deleted file mode 100644 index feafa43853a..00000000000 --- a/greek/mirror/ftpmirror.wml +++ /dev/null @@ -1,200 +0,0 @@ -#use wml::debian::template title="Setting up a Debian archive mirror" -#use wml::debian::toc -#include "$(ENGLISHDIR)/releases/sid/archive.data" -#include "$(ENGLISHDIR)/releases/arches.data" -#use wml::debian::translation-check translation="e466bedb14f9f661d1f4a77514cbe26596877486" maintainer="galaxico" - -<toc-display /> - -<toc-add-entry name="whether">Whether to mirror</toc-add-entry> - -<p>While we appreciate new mirrors, every prospective mirror maintainer -should make sure that they can answer these questions before trying to -start their own mirror:</p> - -<ul> - <li>Is a mirror necessary at my location? Maybe there are already - mirrors nearby.</li> - <li>Do I have the resources to host a mirror? Mirrors take up considerable - <a href="size">disk space</a> and bandwidth, one has to be able to commit to the cost.</li> - <li>Is a mirror the right choice? If you primarily want to support - users at your ISP/facility, then maybe a caching proxy such as - apt-cacher-ng, squid, or varnish might be the better choice.</li> -</ul> - -<toc-add-entry name="what">What to mirror</toc-add-entry> - -<p>The <a href="./">main mirror page</a> lists the archives available for -mirroring.</p> - -<ul> -<li> -Users will look for the debian/ archive to install Debian over -the network, to build CDs from (with jigdo), and to upgrade already -installed systems. <em>We recommend you mirror this repository.</em></li> - -<li> -debian-cd/ is an archive that isn't identical across all the different -mirror servers. On some sites it contains jigdo templates to build CD images -from (used in combination with files from debian/), on some it contains -already built CD images, and on some sites both. -<br /> -Please see the page for <a href="$(HOME)/CD/mirroring/">mirroring the CD -images</a> for further information on this.</li> - -<li> -debian-archive/ contains the true <em>archive</em>, the old and obsolete -versions of Debian. It will generally be interesting only to a small segment -of users. (If you don't know whether you want to mirror this, you probably don't.)</li> - -</ul> - -<p>Please see <a href="size">the mirror size</a> page for -more precise information about mirror sizes.</p> - -<p>The debian-security/ archives contain the security updates released by -the Debian security team. While it sounds interesting to everyone, we do -not recommend to our users to use mirrors to obtain security updates and -instead ask them to directly download them from our distributed -security.debian.org service. <em>We recommend debian-security -<strong>not</strong> be mirrored.</em></p> - -<toc-add-entry name="wherefrom">Where to mirror from</toc-add-entry> - -<p>Note that <code>ftp.debian.org</code> is not canonical location of Debian -packages, instead it is merely one of several servers that get updated from an -internal Debian server. - -There are many <a href="list-full">public mirrors</a> which support rsync -and that are good to mirror from. Please use one that is close to you -network-wise.</p> - -<p>You should avoid mirroring from any service name that resolves to more -than one address (such as <code>ftp.us.debian.org</code>) as this might cause -you to sync between different states across your own mirror-runs should your -upstream mirrors get out of sync. -# -Also note that HTTP is the only service that we guarantee to exist on -<code>ftp.CC.debian.org</code>. If you want to mirror using rsync (using -ftpsync as recommended), we suggest you pick the proper site name for the -machine that currently provides the <code>ftp.CC.debian.org</code>. (Consult -the <code>/debian/project/trace</code> directory of that server to learn it). - -<toc-add-entry name="how">How to mirror</toc-add-entry> - -<p>The recommended method of mirroring is with the ftpsync scriptset, available -in two forms:</p> -<ul> - <li>as a tarball from <url "https://ftp-master.debian.org/ftpsync.tar.gz"></li> - <li>as a git repository: <kbd>git clone https://salsa.debian.org/mirror-team/archvsync.git</kbd> (see <url "https://salsa.debian.org/mirror-team/archvsync/">)</li> -</ul> - -<p>Do not use your own scripts, and do not just use single-pass rsyncs. Using -ftpsync ensures updates are done in a way so that apt does not get confused. -In particular, ftpsync processes translations, contents, and other metadata -files in an order such that apt is not running into validation errors should a -user update the package list while a mirror-run is in progress. Furthermore, -it also produces trace files that contain more information that is useful for -determining whether a mirror works, what architectures it carries, and where it -syncs from.</p> - -<toc-add-entry name="partial">Partial mirroring</toc-add-entry> - -<p>Considering the already <a href="size">large size of Debian archive</a>, -it might be advisable to only mirror parts of the archive. Public mirrors -should carry all suites (testing, unstable, etc.), but they may restrict the -architecture set that they carry. The configuration file for ftpsync has -ARCH_EXCLUDE and ARCH_INCLUDE settings for this purpose.</p> - -<toc-add-entry name="when">When to mirror</toc-add-entry> - -<p>The main archive gets updated four times a day. -The mirrors commonly start updating around 3:00, 9:00, 15:00 and 21:00 (all times UTC), -but these are never fixed times and you should not fixate your mirror on them.</p> - -<p>Your mirror should update a few hours after one of the main archive mirror -pulses. You should check if the site you're mirroring from leaves a time stamp -file in their <kbd>project/trace/</kbd> subdirectory. The time stamp file -will be named like that site, and it will contain the completion time of -their last mirror update. Add a couple of hours to that time (to be safe) -and mirror then.</p> - -<p><b>It is essential that your mirror is in sync with the main archive</b>. A -minimum of 4 updates per 24 hours will ensure that your mirror is a true -reflection of the archive. Please understand that mirrors that are not in sync -with the main archive will not be listed in the official mirrors listing.</p> - -<p>The easiest way to automatically have the mirror run every day is to use -cron. See <kbd>man crontab</kbd> for details.</p> - -<p>Note that if your site is being triggered with a push mechanism, then you -don't need to worry about any of this.</p> - -<h3>Push-triggered mirroring</h3> - -<p><q>Push</q> mirroring is a form of mirroring that we have developed -to minimize the time it takes for changes to the archive to reach mirrors. -An upstream mirror uses an SSH trigger to tell the downstream mirror to -update itself. -For a more detailed description of how this works, why it is secure, and -how to set a push mirror, please see <a href="push_mirroring">the complete -explanation</a>.</p> - -<toc-add-entry name="settings">Recommended additional settings</toc-add-entry> - -<p>Public mirrors should make the Debian archive available over HTTP at <code>/debian</code>.</p> - -<p>Furthermore, please ensure directory listings are enabled (with full length -filenames) and symlinks followed. - -If you use Apache, something like this might work: -<pre> -<Directory <var>/path/to/your/debian/mirror</var>> - Options +Indexes +SymlinksIfOwnerMatch - IndexOptions NameWidth=* +SuppressDescription -</Directory> -</pre> - -<toc-add-entry name="submit">How to add a mirror to the mirror list</toc-add-entry> - -<p> -If you would like to have your mirror listed on the official mirrors list please: -</p> - -<ul> -<li>Ensure that your mirror synchronizes 4 times per 24 hours with the archive</li> -<li>Ensure that your mirror includes the source files for the architectures the -mirror carries</li> -</ul> - -<p>Once the mirror is set up, it should be <a href="submit">registered with Debian</a> -in order to get included in the <a href="list">official mirror list</a>. -Submissions can be done using our <a href="submit">simple web form</a>.</p> - - -<p>Any problems or enquiries can be sent to <email mirrors@debian.org>.</p> - -<toc-add-entry name="mailinglists">Mailinglists</toc-add-entry> - -<p>There are two public <a href="../MailingLists/">mailing lists</a> about -Debian mirrors, -<a href="https://lists.debian.org/debian-mirrors-announce/">debian-mirrors-announce</a> -and -<a href="https://lists.debian.org/debian-mirrors/">debian-mirrors</a>. -We encourage all mirror maintainers to subscribe to the announcement list as -it will be used for any important announcements. This list is moderated and will -receive only a low amount of traffic. The second mailing list is meant for general -discussion and is open to all.</p> - -<p>If you have any questions that aren't answered on these web pages, you -can contact us at <email mirrors@debian.org> or using IRC, #debian-mirrors on -<tt>irc.debian.org</tt>.</p> - - -<toc-add-entry name="private-mirror">Notes for private (partial) mirrors</toc-add-entry> - -<p> -If you want to operate a mirror for your own site only, and you need to carry only a -subset of suites (such as stable), <a href="https://packages.debian.org/stable/debmirror">debmirror</a> -might be a good fit for you also. -</p> diff --git a/greek/mirror/index.wml b/greek/mirror/index.wml deleted file mode 100644 index ca8838a9fb2..00000000000 --- a/greek/mirror/index.wml +++ /dev/null @@ -1,38 +0,0 @@ -#use wml::debian::template title="Debian mirrors" BARETITLE="true" -#use wml::debian::translation-check translation="6ab524a7b127f07748ca4f2b1168f6ed8b785a81" maintainer="galaxico" - -<p>Debian is distributed all around the world using mirrors -in order to provide users with better access to our archive.</p> - -<p>The following Debian archives are mirrored:</p> - -<dl> -<dt><strong>Debian packages</strong> (<code>debian/</code>)</dt> - <dd>The Debian package pool -- this includes the vast majority of .deb - packages, the installation materials and the sources. - <br> - See the list of <a href="list">Debian mirrors that include the - <code>debian/</code> archive</a>. - </dd> -<dt><strong>CD images</strong> (<code>debian-cd/</code>)</dt> - <dd>The repository of CD images: Jigdo files and ISO image files. - <br> - See the list of <a href="$(HOME)/CD/http-ftp/#mirrors">Debian mirrors that - include the <code>debian-cd/</code> archive</a>. - </dd> -<dt><strong>Old releases</strong> (<code>debian-archive/</code>)</dt> - <dd>The archive of old released versions of Debian. - <br> - See <a href="$(HOME)/distrib/archive">Distribution Archives</a> - for more information. - </dd> -</dl> - -<h2>Information for mirror owners</h2> - -<p>Debian mirrors are maintained by volunteers, so if there are no good mirrors -near you and you are in a position to donate disk space and connectivity, -consider creating a mirror and contribute to making Debian more accessible. -See the pages on <a href="ftpmirror">setting up a mirror of the Debian -archive</a> for more information about mirroring.</p> - diff --git a/greek/mirror/list-full.wml b/greek/mirror/list-full.wml deleted file mode 100644 index 2fb83a44edb..00000000000 --- a/greek/mirror/list-full.wml +++ /dev/null @@ -1,47 +0,0 @@ -#use wml::debian::template title="Debian worldwide mirror sites" BARETITLE=true -#use wml::debian::translation-check translation="d83882f2dd9b20c81d0cb83b32c028d9765578c7" maintainer="galaxico" - -<p>This is a <strong>complete</strong> list of mirrors of Debian. -For each site, the different types of material available are listed, -along with the access method for each type.</p> - -<p>The following things are mirrored:</p> - -<dl> -<dt><strong>Packages</strong></dt> - <dd>The Debian package pool.</dd> -<dt><strong>CD Images</strong></dt> - <dd>Official Debian CD Images. See - <url "https://www.debian.org/CD/"> for details.</dd> -<dt><strong>Old releases</strong></dt> - <dd>The archive of old released versions of Debian. - <br /> - Some of the old releases also included the so-called debian-non-US - archive, with sections for Debian packages that could not be - distributed in the US due to software patents or use of encryption. - The debian-non-US updates were discontinued with Debian 3.1.</dd> - -</dl> - -<p>The following access methods are possible:</p> - -<dl> -<dt><strong>HTTP</strong></dt> - <dd>Standard web access, but it can be used for downloading files.</dd> -<dt><strong>rsync</strong></dt> - <dd>An efficient means of mirroring.</dd> -</dl> - -<p>The authoritative copy of the following list can always be found at: -<url "https://www.debian.org/mirror/list-full">. -<br /> -Everything else you want to know about Debian mirrors: -<url "https://www.debian.org/mirror/">. -</p> - -<hr style="height:1"> - -<p>Jump directly to a country on the list: -<br /> - -#include "$(ENGLISHDIR)/mirror/list-full.inc" diff --git a/greek/mirror/list.wml b/greek/mirror/list.wml deleted file mode 100644 index 226014ab713..00000000000 --- a/greek/mirror/list.wml +++ /dev/null @@ -1,77 +0,0 @@ -#use wml::debian::template title="Debian worldwide mirror sites" BARETITLE=true -#use wml::debian::translation-check translation="c1ef6c3811be792e129656bbfcf09866d9880eb5" maintainer="galaxico" - -<p>Debian is distributed (<em>mirrored</em>) on hundreds of -servers on the Internet. Using a nearby server will probably speed up -your download, and also reduce the load on our central servers and -on the Internet as a whole.</p> - -<p class="centerblock"> - Debian mirrors exist in many countries, and for some we have - added a <code>ftp.<country>.debian.org</code> alias. This - alias usually points to a mirror that syncs regularly and quickly - and carries all of Debian's architectures. The debian archive - is always available via <code>HTTP</code> at the <code>/debian</code> - location on the server. -</p> - -<p class="centerblock"> - Other <strong>mirror sites</strong> may have restrictions on what - they mirror (due to space restrictions). Just because a site is not the - country's <code>ftp.<country>.debian.org</code> does not necessarily - mean that it is any slower or less up to date than the - <code>ftp.<country>.debian.org</code> mirror. - In fact, a mirror that carries your architecture and is closer to you as the - user and, therefore, faster, is almost always preferable to other mirrors - that are farther away. -</p> - -<p>Use the site closest to you for the fastest downloads possible -whether it is a per-country mirror alias or not. -The program -<a href="https://packages.debian.org/stable/net/netselect">\ -<em>netselect</em></a> can be used to -determine the site with the least latency; use a download program such as -<a href="https://packages.debian.org/stable/web/wget">\ -<em>wget</em></a> or -<a href="https://packages.debian.org/stable/net/rsync">\ -<em>rsync</em></a> for determining the site with the most throughput. -Note that geographic proximity often isn't the most important factor for -determining which machine will serve you best.</p> - -<p> -If your system moves around a lot, you may be best served by a "mirror" -that is backed by a global <abbr title="Content Delivery Network">CDN</abbr>. -The Debian project maintains -<code>deb.debian.org</code> for this -purpose and you can use this in your apt sources.list — consult -<a href="http://deb.debian.org/">the service's website for details</a>. - -<p> -Everything else you want to know about Debian mirrors: -<url "https://www.debian.org/mirror/">. -</p> - -<h2 class="center">Debian per-country mirror aliases</h2> - -<table border="0" class="center"> -<tr> - <th>Country</th> - <th>Site</th> - <th>Architectures</th> -</tr> -#include "$(ENGLISHDIR)/mirror/list-primary.inc" -</table> - -<h2 class="center">List of mirrors of the Debian archive</h2> - -<table border="0" class="center"> -<tr> - <th>Host name</th> - <th>HTTP</th> - <th>Architectures</th> -</tr> -#include "$(ENGLISHDIR)/mirror/list-secondary.inc" -</table> - -#include "$(ENGLISHDIR)/mirror/list-footer.inc" diff --git a/greek/mirror/push_mirroring.wml b/greek/mirror/push_mirroring.wml deleted file mode 100644 index 3d9c4610df4..00000000000 --- a/greek/mirror/push_mirroring.wml +++ /dev/null @@ -1,65 +0,0 @@ -#use wml::debian::template title="Push Mirroring" -#use wml::debian::translation-check translation="82968214595db755ef0c09f5d6c1b11a6660b5cd" maintainer="galaxico" - -<p>Push mirroring is a form of mirroring that minimizes the time it takes -for changes to the archive to reach mirrors. The master server uses -a triggering mechanism to immediately inform the client mirror that it -needs to be updated.</p> - -<p>Push mirroring takes a more effort to set up since the maintainers -of the upstream and downstream mirror must exchange information. The benefit -is that the upstream mirror initiates the mirror process immediately after -its archive has been updated. This allows changes to the archive to -propagate quickly. -</p> - -<h2>Explanation of the method</h2> - -<p>Triggers are done using ssh. The push-server sshs into the pushed server's -mirror account using public-key authentication. The key is set up such that -this action may only trigger a mirror run, no other commands. The pushed -server then runs ftpsync to update the archive using rsync as normal. -<br /> -Exchanging public keys and potentially access to restricted rsync servers -requires coordination between a mirror operator and their upstream source. -</p> - -<h2>Setting up a push client mirror</h2> - -<p>To become a push client for the FTP archive, you will need to set up -mirroring using our standard <a href="ftpmirror#how">ftpsync</a> script set. -<br /> -Once that is working, add the public sshkey of your upstream mirror -in your <code>~<user>/.ssh/authorized_keys</code> with a -<code>command="~/bin/ftpsync</code> -restriction. (You may have ftpsync in a different directory, adapt -accordingly.) -</p> - -<h2>Push-Primary client sites</h2> - -<p>Push-Primary client mirrors, also referred to as Tier-1 mirrors, are the -push client mirrors which sync directly from Debian's internal syncproxy -network. -</p> - -<p>If your site is <strong>very</strong> well connected (both very good -bandwidth and well connected to major backbones) and you are willing to let -other sites mirror from your site, you may want to let us know so we can -consider you for a push mirror. Please contact the Debian mirrors team for -set-up details. Note however, that we can't accept all requests for becoming a -primary push mirror as we already have a fair number of Tier-1 mirrors. -</p> - -<h2>Setting up a push server mirror</h2> - -<p>Given the large number of mirrors and the size of the Debian archive, it -is not feasible for all the mirrors to use Debian's internal syncproxies as the -upstream source for Debian. It is much more efficient if the load is -distributed among a number of push mirrors distributed throughout the globe. -</p> - -<p>Therefore, a number of Push-Primary sites are, in turn, push servers for -their downstreams. If you want to configure your site as a push server for -your downstream sites, see the <a href="push_server">details on setting up a push server</a>. -</p> diff --git a/greek/mirror/push_server.wml b/greek/mirror/push_server.wml deleted file mode 100644 index c0bd498ec79..00000000000 --- a/greek/mirror/push_server.wml +++ /dev/null @@ -1,106 +0,0 @@ -#use wml::debian::template title="Setting up a push server" -#use wml::debian::toc -#use wml::debian::translation-check translation="8af469f41d65d1e2618d91408e57a4313cf98f8b" maintainer="galaxico" - -<p>Setting up a push server consists of two basic tasks: setting up rsync -access (for normal, <q>pull</q> mirroring) and setting up ssh trigger mechanism -(for <q>pushing</q> the pull mirroring). -</p> - -<p><small>(For more information on what a push server is, please read -<a href="push_mirroring">the explanation of push mirroring</a>.)</small> -</p> - -<toc-display /> - -<toc-add-entry name="rsync">Setting up rsync</toc-add-entry> - -<p>Install <code>rsync</code>. If your site is running Debian, just install the -<a href="https://packages.debian.org/stable/rsync">rsync</a> package. -</p> - -<p>Create <code>rsyncd.conf</code> file and put something similar to this -in it: -</p> - -<pre> -uid = nobody -gid = nogroup -max connections = 50 -socket options = SO_KEEPALIVE - -[debian] - path = /srv/debian/mirror - comment = The Debian Archive (https://www.debian.org/mirror/size) - auth users = * - read only = true - secrets file = /etc/rsyncd/debian.secrets -</pre> - -<p>Add an entry for each site you are pushing to in the -<code>/etc/rsyncd/debian.secrets</code> file: -</p> - -<pre> -site1.example.com:a_password -site2.example.com:another_password -site3.example.net:password -</pre> - -<p>You have now given the downstream mirrors access to the archive on your -machine. If you are willing to provide rsync access to everyone, skip -the <code>auth users</code> and <code>secrets file</code> setting in -<code>rsyncd.conf</code>. You don't need a secrets file then either. -</p> - -<p>You will probably want to start the rsync daemon from inetd. -To enable the daemon, add the following to your -<code>/etc/inetd.conf</code> file: -</p> - -<pre> -rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon -</pre> - -<p> -(Remember to send inetd an HUP signal to tell it to reread its config file -after modifying the file.) -</p> - -<toc-add-entry name="sshtrigger">Setting up ssh trigger mechanism</toc-add-entry> - -<p>Create a new ssh key for the account that you use to mirror Debian using -<code>ssh-keygen</code>. If your account already has a key for other purposes, -you may want to create a new one and store it in a different file using -<code>ssh-keygen -f ~/.ssh/identity.mysite</code></p> - -<p> -Your downstream mirrors will then need to add -</p> -<pre> -command="~/bin/ftpsync",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty <contents of your ~/.ssh/<key>.pub file> -</pre> -<p> -to their <code>~/.ssh/authorized_keys</code> file. -</p> - -<p>You need to set up your mirroring process to contact your downstreams when your -mirror-run is finished. -The ftpsync suite contains the script <code>runmirrors</code> which is handling all -needed tasks for you. Simply change your ftpsync.conf to include the setting -<code>HUB=true</code>, copy the <code>runmirrors.conf.sample</code> to -<code>runmirrors.conf</code> and <code>runmirrors.mirror.sample</code> to -<code>runmirrors.mirror</code> and configure the config file to suit your system. -Then list all your downstream mirrors inside runmirrors.mirror and the ftpsync/runmirror -duo will do all the heavy lifting for you. -</p> - -<p>The effect will be that your system will try to ssh to your downstream mirrors, -after your own mirror updated, so they can start their own updates. This assumes -you gave your downstream mirror operators the ssh key you told runmirrors to use -and that they added it to their own ~/.ssh/authorized_keys as described above. -</p> - -<p>If you have any trouble with this, <a href="mailto:mirrors@debian.org">\ -contact us</a>. -</p> diff --git a/greek/mirror/size.wml b/greek/mirror/size.wml deleted file mode 100644 index 423e182df58..00000000000 --- a/greek/mirror/size.wml +++ /dev/null @@ -1,49 +0,0 @@ -#use wml::debian::template title="Mirror Size" -#use wml::debian::translation-check translation="a7c92aeb803830d49fd98ee440c90a54f3ee1be9" maintainer="galaxico" - -<h2>How big is the Debian archive?</h2> - -# (note for the English editors on how to update some of the numbers below) -# dak psql database on ftp-master is 'projectb' -# and there's a copy on merkel -# projectb=> select architecture.arch_string as Architecture, -# sum(files.size)/1024/1024/1024 as Size -# from files,binaries,architecture -# where architecture.id=binaries.architecture -# and files.id=binaries.file -# group by architecture.arch_string -# order by Size; -# projectb=> select sum(size)/1024/1024/1024 from files where -# filename ~ '.diff.gz$' or filename ~ '.dsc$' -# or filename ~ '.orig.tar.gz$'; -# projectb=> select sum(files.size)/1024/1024/1024 -# from files, binaries, architecture -# where architecture.id=binaries.architecture -# and files.id=binaries.file -# and architecture.arch_string='i386'; - -# wc -c'ing files inside the debian/ directory might occasionally give -# slightly different results than the SQL queries, but the difference -# is usually negligible -joy - -<p>Numbers on this page are updated daily.</p> - -<table> -<tr><th>Architecture</th> <th>Size in GB</th></tr> -#include "$(ENGLISHDIR)/mirror/size.data" -</table> - -<p>Note that the archive is constantly growing; testing will grow especially -as a release approaches. Also, we do not recommend reducing size of a mirror -by excluding specific distributions; exclude specific architectures instead, -according to their <a href="https://popcon.debian.org/">popularity</a>.</p> - -<h3>How big is the Debian CD archive?</h3> - -<p>The CD archive varies greatly across mirrors — the Jigdo files are -around 100-150 MB per architecture, while the full DVD/CD images are -around 15 GB each, plus extra space for the <q>update</q> CD images, -Bittorrent files, etc.</p> - -<p>For more information about the CD archive mirroring, please see -the <a href="../CD/mirroring/">Debian CD mirror pages</a>.</p> diff --git a/greek/mirror/sponsors.wml b/greek/mirror/sponsors.wml deleted file mode 100644 index 665580d2878..00000000000 --- a/greek/mirror/sponsors.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Sponsors of all the Debian mirrors" BARETITLE=true -#use wml::debian::translation-check translation="4c8b93213b94b668e35914c3405b2e29c672043a" maintainer="galaxico" - -<h2>Debian FTP archive mirrors</h2> - -<table width="100%" summary=""> -<colgroup span="3"> -<col class="top"> -<col class="center"> -<col> - -<tr> - <th>Country</th> - <th>Site</th> - <th>Sponsors</th> -</tr> -#include "$(ENGLISHDIR)/mirror/sponsors.list" -</table> diff --git a/greek/mirror/submit.wml b/greek/mirror/submit.wml deleted file mode 100644 index 57474797dce..00000000000 --- a/greek/mirror/submit.wml +++ /dev/null @@ -1,100 +0,0 @@ -#use wml::debian::template title="Submit Mirror Information" -#include "$(ENGLISHDIR)/mirror/submit.inc" -#use wml::debian::translation-check translation="cd8f39027a950a5174d2d49109ba6800c0f0cdec" maintainer="galaxico" - -<p>If you would like to submit information about a mirror of Debian, -you can do so using the form below. Information provided will be displayed in -the mirror list. -</p> - -<p>Please note that all submitted mirrors should follow the -<a href="ftpmirror">rules and guidelines laid out in our documentation</a>. In -particular, -</p> -<ul> -<li>you should be using <a href="ftpmirror#how">ftpsync</a> to mirror Debian, -<li>pick a good upstream (<strong>not</strong> a (http) service name like - <code>ftp.CC.debian.org</code>, not DNS round robins, not CDNs), -<li>update four times a day to match the archive update frequency (or set up - triggers with upstream, or use <code>ftpsync-cron</code> hourly to monitor - your upstream for changes and initiate syncs). Furthermore, -<li>your mirror must have an appropriately named tracefile (ftpsync will do - that if MIRRORNAME is set correctly), -<li>should touch <code>/Archive-Update-in-Progress-XXX</code> and - <code>/Archive-Update-Required-XXX</code> flagfiles when appropriate - (again, ftpsync will do that for you) to help mirrors downstream of - you to sync correctly. -</ul> - -<form-action "" archive-upstream https://cgi.debian.org/cgi-bin/submit_mirror.pl> - -<h2>Basic information</h2> - -<p> -<input type="radio" name="submissiontype" value="new" checked> -New mirror submission - -<input type="radio" name="submissiontype" value="update"> -Update of an existing mirror -</p> - -<p> -Mirror name: <input type="text" name="site" size="30"></p> - -<p>Enter the paths to the Debian mirror on your site in the fields below. -Leave non-relevant fields blank.</p> - -<table> - <tr><td>Packages archive, over HTTP: </td><td><input type="text" name="archive-http" id="archve-http" size="30" value="/debian" readonly="readonly"> <small>The archive needs to be available at <code>/debian</code>.</small></td></tr> -<tablerowdef "Packages archive, over rsync" archive-rsync 30 "debian" " <small>If you offer rsync, <code>debian</code> is suggested as module name.</small>"> -# <tablerow "CD/DVD images, over HTTP" cdimage-http 30> -# <tablerow "CD/DVD images, over rsync" cdimage-rsync 30> -# <tablerow "Old Debian releases, over HTTP" old-http 30> -# <tablerow "Old Debian releases, over rsync" old-rsync 30> -</table> - -<h2>Information about the mirror site</h2> - -<table> -<tr> -<td>Mirrored architectures: -<td> -<label><input type=checkbox name=architectures id="allarch" value="ALL" onclick="allarches()"> <em>all of them (i.e. no per-architecture exclusion is done)</em></label><br> -<archlist> -</td></tr> -</table> - -<table> -<tablerow "Name of site maintainer" maint_name 30> -<tablerow "Public e-mail of site maintainer" maint_public_email 30> -<tr><td>Country of site: <td><select name="country"> -<countrylist> -</select> -<tablerow "Location of site (optional)" location 30> -<tablerow "Name of site sponsor (optional)" sponsor_name 30> -<tablerow "URL of site sponsor (optional)" sponsor_url 30> -</table> - -<table><tr> -<td valign="top">Comment:</td> -<td><textarea name="comment" cols=40 rows=7></textarea></td> -</tr></table> - -<p><label>I have subscribed to the -<a href="https://lists.debian.org/debian-mirrors-announce/"> -announcements mailing list</a> -<input type="checkbox" name="mlannounce"></label> -</p> - -<p> -<input type="submit" value="Submit"> <input type="reset" value="Clear form"> -</p> -</form> - -<p>Your site should appear on the list within a couple of weeks, as soon as a -human operator verifies it and includes it. We will email you in case of any -problems with the submitted entry.</p> - -<p>If you don't get any feedback within three months, you can contact us at -<email mirrors@debian.org>.</p> - diff --git a/greek/opl.wml b/greek/opl.wml deleted file mode 100644 index 2f3438abce0..00000000000 --- a/greek/opl.wml +++ /dev/null @@ -1,138 +0,0 @@ -#use wml::debian::template title="Open Publication License" NOCOPYRIGHT="true" -#use wml::debian::translation-check translation="d54152841794e2e9a156f6f2abb5445fb98cb218" maintainer="galaxico" - - <p><strong>v1.0, 8 June 1999</strong></p> - - - <h2 id="section1">I. REQUIREMENTS ON BOTH UNMODIFIED AND MODIFIED VERSIONS</h2> - - <p>The Open Publication works may be reproduced and distributed in - whole or in part, in any medium physical or electronic, provided - that the terms of this license are adhered to, and that this - license or an incorporation of it by reference (with any options - elected by the author(s) and/or publisher) is displayed in the - reproduction.</p> - - <p>Proper form for an incorporation by reference is as follows: - Copyright (c) <year> by <author's name or designee>. This - material may be distributed only subject to the terms and - conditions set forth in the Open Publication License, vX.Y or - later (the latest version is presently available at - <url "http://www.opencontent.org/openpub/" />). The reference must be - immediately followed with any options elected by the author(s) - and/or publisher of the document (see <a href="#section6">section - VI</a>).</p> - - <p>Commercial redistribution of Open Publication-licensed material - is permitted.</p> - - <p>Any publication in standard (paper) book form shall require the - citation of the original publisher and author. The publisher and - author's names shall appear on all outer surfaces of the book. On - all outer surfaces of the book the original publisher's name shall - be as large as the title of the work and cited as possessive with - respect to the title.</p> - - - <h2 id="section2">II. COPYRIGHT</h2> - - <p>The copyright to each Open Publication is owned by its - author(s) or designee.</p> - - - <h2 id="section3">III. SCOPE OF LICENSE</h2> - - <p>The following license terms apply to all Open Publication - works, unless otherwise explicitly stated in the document.</p> - - <p>Mere aggregation of Open Publication works or a portion of an - Open Publication work with other works or programs on the same - media shall not cause this license to apply to those other - works. The aggregate work shall contain a notice specifying the - inclusion of the Open Publication material and appropriate - copyright notice.</p> - - <p><em>SEVERABILITY</em>. If any part of this license is found to - be unenforceable in any jurisdiction, the remaining portions of - the license remain in force.</p> - - <p><em>NO WARRANTY</em>. Open Publication works are licensed and - provided <q>as is</q> without warranty of any kind, express or implied, - including, but not limited to, the implied warranties of - merchantability and fitness for a particular purpose or a warranty - of non-infringement.</p> - - - <h2 id="section4">IV. REQUIREMENTS ON MODIFIED WORKS</h2> - - <p>All modified versions of documents covered by this license, - including translations, anthologies, compilations and partial - documents, must meet the following requirements:</p> - - <ul> - <li>The modified version must be labeled as such.</li> - <li>The person making the modifications must be identified and - the modifications dated.</li> - <li>Acknowledgement of the original author and publisher if - applicable must be retained according to normal academic - citation practices.</li> - <li>The location of the original unmodified document must be - identified.</li> - <li>The original author's (or authors') name(s) may not be used - to assert or imply endorsement of the resulting document without - the original author's (or authors') permission.</li> - </ul> - - - <h2 id="section5">V. GOOD-PRACTICE RECOMMENDATIONS</h2> - - <p>In addition to the requirements of this license, it is - requested from and strongly recommended of redistributors - that:</p> - - <ul> - <li>If you are distributing Open Publication works on hardcopy or - CD-ROM, you provide email notification to the authors of your - intent to redistribute at least thirty days before your - manuscript or media freeze, to give the authors time to provide - updated documents. This notification should describe - modifications, if any, made to the document.</li> - <li>All substantive modifications (including deletions) be either - clearly marked up in the document or else described in an - attachment to the document.</li> - <li>Finally, while it is not mandatory under this license, it is - considered good form to offer a free copy of any hardcopy and - CD-ROM expression of an Open Publication-licensed work to its - author(s).</li> - </ul> - - - <h2 id="section6">VI. LICENSE OPTIONS</h2> - - <p>The author(s) and/or publisher of an Open Publication-licensed - document may elect certain options by appending language to the - reference to or copy of the license. These options are - considered part of the license instance and must be included - with the license (or its incorporation by reference) in derived - works.</p> - - <p>A. To prohibit distribution of substantively modified versions - without the explicit permission of the author(s). <q>Substantive - modification</q> is defined as a change to the semantic content of - the document, and excludes mere changes in format or typographical - corrections.</p> - - <p>To accomplish this, add the phrase <q>Distribution of - substantively modified versions of this document is prohibited - without the explicit permission of the copyright holder.</q> to the - license reference or copy.</p> - - <p>B. To prohibit any publication of this work or derivative works - in whole or in part in standard (paper) book form for commercial - purposes is prohibited unless prior permission is obtained from - the copyright holder.</p> - - <p>To accomplish this, add the phrase <q>Distribution of the work or - derivative of the work in any standard (paper) book form is - prohibited unless prior permission is obtained from the copyright - holder.</q> to the license reference or copy.</p> diff --git a/greek/partners/2015/Makefile b/greek/partners/2015/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/partners/2015/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/partners/2015/index.wml b/greek/partners/2015/index.wml deleted file mode 100644 index db24e0fce6e..00000000000 --- a/greek/partners/2015/index.wml +++ /dev/null @@ -1,25 +0,0 @@ -#use wml::debian::template title="Debian Partners for 2015" -#use wml::debian::recent_list -#include "$(ENGLISHDIR)/partners/index.include" -#use wml::debian::translation-check translation="76bf549f521db7d60c1dda7a64c8b70bb265f90b" maintainer="galaxico" - - -<p>Information about the current partners program -and list of current partners can be viewed at the -<a href="..">main partners program page</a>. - -<h3>2015 Partners Program conditions</h3> - -<p>For more information on the Debian Partners Program for the year 2015, visit -the <a href="./partners">2015 Partners Program</a>.</p> - -<h3>2015 Partners</h3> - -#include "$(ENGLISHDIR)/partners/2015/partners.data" - -<hrline> - -<h3>DebConf15 Sponsors</h3> - -<p>The DebConf15 Sponsors are listed in the -<a href="https://debconf15.debconf.org">DebConf15 website</a>.</p> diff --git a/greek/partners/2015/partners.wml b/greek/partners/2015/partners.wml deleted file mode 100644 index 5203256a948..00000000000 --- a/greek/partners/2015/partners.wml +++ /dev/null @@ -1,119 +0,0 @@ -#use wml::debian::template title="Debian Partners Program 2015 - description" -#use wml::debian::translation-check translation="f7210a80d7468806cac65059e70b3f611bfaab48" maintainer="galaxico" - -<h3>What is the Debian Partners Program?</h3> -<div class="centerblock"> - <p>The Partners Program was created to recognize companies and organizations - that provide ongoing assistance to the Debian project. Because of the substantial - support provided by these partners, we have been able to expand and improve - Debian. We would like to officially recognize their efforts, and continue - to maintain a good working relationship.</p> -</div> - -<h3>What are the criteria for Partners?</h3> - There are several types of partnerships. - -<ul> -<li><b>Development Partners</b><br> - <ul> - <li> provide equipment to Debian (at greatly reduced cost or on extended loan) - <li> provide equipment for use at conferences, trade shows, etc. - <li> provide a hardware based service to Debian (net access, accounts, etc.) - <li> commercial vendors who maintain key Debian packages - <li> assist or lead efforts to port and maintain Debian packages - on their hardware - <li> provide free or reduced cost technical service or consulting to Debian - </ul> -<li><b>Service Partners</b><br> - <ul> - <li> assist Debian in distribution of releases - <li> provide a forum for Debian's press releases and announcements - <li> provide a free or reduced cost non technical service to Debian - </ul> -<li><b>Financial Partners</b><br> - <ul> - <li>Provide ongoing financial support, - like revenue sharing programs. - </ul> -</ul> - -<p> -To be a partner, at least one of the criteria above must be met. -Partners who fall under more than one category can be listed under each -category that they qualify for. - -<h3>What does Debian do for the partners?</h3> - Debian will work closely with all partners to ensure that Debian -understands the partners needs and concerns, and vice versa. This will -enable Debian to remain properly focused within the market through -the partner's feedback. - -<p> - Each partner will have space on the Debian partners web page of that year - describing the nature of the partnership. -The partner may provide links to be included in this information. - -<!-- -<p> - For companies supplying hardware for porting projects, this page will be - linked from the relevant porting pages directly as well. - --> - -<h3>What do the partners do for Debian?</h3> -In addition to meeting the criteria for partnership stated above, -the partners should prominently mention Debian in the areas affected by the -partnership. -They should work with Debian to promote the projects interests. -Possibilities include: -<ul> -<li> Links to relevant Debian web pages -<li> Advertising Banners/Buttons/Splashes -<li> Links to current Debian News/Events/Projects -<li> ...and many more! -</ul> - - -<h3>How does a vendor become a partner?</h3> - -An email should be sent to -<a href="mailto:partners@debian.org">partners@debian.org</a> -with a <a href="../partners-form">proposal</a> for partnership. -This proposal will be reviewed -by Debian and discussed with the prospective partner. Debian will -then make a decision on whether or not a partnership is possible. - - -<h3>How and when do partnerships end?</h3> - -Debian or the partner may choose to end the partnership at any time. -When the partnership ends, the web page entries related to the -partner are removed in the current listing (entries in former years remain). -Partnerships may end for several reasons: -<ul> -<li>the equipment that was loaned is withdrawn -<li>the service is no longer provided -<li>the goals of the partners no longer coincide with the goals of Debian -</ul> - -<h3>Are there other ways my organization can contribute to Debian?</h3> -<div class="centerblock"> -<p> -For donations of money, equipment, or services, visit our -<a href="../../donations">donations</a> page.</p> - -<p> -Sponsorship of DebConf (the annual Debian Conference) is handled by -each year's DebConf Organization Team. -For DebConf Sponsorship, visit the -<a href="https://www.debconf.org">DebConf</a> page.</p> - -<p> -Debian LTS funding is handled by the LTS Team. -For LTS funding, visit the -<a href="https://wiki.debian.org/LTS">LTS</a> wiki page.</p> - -<p> -If you have another idea that does not suit the above suggestion, -<a href="../../contact">contact us</a>. -</p> -</div> diff --git a/greek/partners/2016/Makefile b/greek/partners/2016/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/partners/2016/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/partners/2016/index.wml b/greek/partners/2016/index.wml deleted file mode 100644 index b3ce0a5d547..00000000000 --- a/greek/partners/2016/index.wml +++ /dev/null @@ -1,25 +0,0 @@ -#use wml::debian::template title="Debian Partners for 2016" -#use wml::debian::recent_list -#include "$(ENGLISHDIR)/partners/index.include" -#use wml::debian::translation-check translation="ae40b5ae7d5946779124fa97f22c20fde387d8f4" maintainer="galaxico" - - -<p>Information about the current partners program -and list of current partners can be viewed at the -<a href="..">main partners program page</a>. - -<h3>2016 Partners Program conditions</h3> - -<p>For more information on the Debian Partners Program for the year 2016, visit -the <a href="./partners">2016 Partners Program</a>.</p> - -<h3>2016 Partners</h3> - -#include "$(ENGLISHDIR)/partners/2016/partners.data" - -<hrline> - -<h3>DebConf16 Sponsors</h3> - -<p>The DebConf16 Sponsors are listed in the -<a href="https://debconf16.debconf.org">DebConf16 website</a>.</p> diff --git a/greek/partners/2016/partners.wml b/greek/partners/2016/partners.wml deleted file mode 100644 index 3459207bbc8..00000000000 --- a/greek/partners/2016/partners.wml +++ /dev/null @@ -1,119 +0,0 @@ -#use wml::debian::template title="Debian Partners Program 2016 - description" -#use wml::debian::translation-check translation="f7210a80d7468806cac65059e70b3f611bfaab48" maintainer="galaxico" - -<h3>What is the Debian Partners Program?</h3> -<div class="centerblock"> - <p>The Partners Program was created to recognize companies and organizations - that provide ongoing assistance to the Debian project. Because of the substantial - support provided by these partners, we have been able to expand and improve - Debian. We would like to officially recognize their efforts, and continue - to maintain a good working relationship.</p> -</div> - -<h3>What are the criteria for Partners?</h3> - There are several types of partnerships. - -<ul> -<li><b>Development Partners</b><br> - <ul> - <li> provide equipment to Debian (at greatly reduced cost or on extended loan) - <li> provide equipment for use at conferences, trade shows, etc. - <li> provide a hardware based service to Debian (net access, accounts, etc.) - <li> commercial vendors who maintain key Debian packages - <li> assist or lead efforts to port and maintain Debian packages - on their hardware - <li> provide free or reduced cost technical service or consulting to Debian - </ul> -<li><b>Service Partners</b><br> - <ul> - <li> assist Debian in distribution of releases - <li> provide a forum for Debian's press releases and announcements - <li> provide a free or reduced cost non technical service to Debian - </ul> -<li><b>Financial Partners</b><br> - <ul> - <li>Provide ongoing financial support, - like revenue sharing programs. - </ul> -</ul> - -<p> -To be a partner, at least one of the criteria above must be met. -Partners who fall under more than one category can be listed under each -category that they qualify for. - -<h3>What does Debian do for the partners?</h3> - Debian will work closely with all partners to ensure that Debian -understands the partners needs and concerns, and vice versa. This will -enable Debian to remain properly focused within the market through -the partner's feedback. - -<p> - Each partner will have space on the Debian partners web page of that year - describing the nature of the partnership. -The partner may provide links to be included in this information. - -<!-- -<p> - For companies supplying hardware for porting projects, this page will be - linked from the relevant porting pages directly as well. - --> - -<h3>What do the partners do for Debian?</h3> -In addition to meeting the criteria for partnership stated above, -the partners should prominently mention Debian in the areas affected by the -partnership. -They should work with Debian to promote the projects interests. -Possibilities include: -<ul> -<li> Links to relevant Debian web pages -<li> Advertising Banners/Buttons/Splashes -<li> Links to current Debian News/Events/Projects -<li> ...and many more! -</ul> - - -<h3>How does a vendor become a partner?</h3> - -An email should be sent to -<a href="mailto:partners@debian.org">partners@debian.org</a> -with a <a href="../partners-form">proposal</a> for partnership. -This proposal will be reviewed -by Debian and discussed with the prospective partner. Debian will -then make a decision on whether or not a partnership is possible. - - -<h3>How and when do partnerships end?</h3> - -Debian or the partner may choose to end the partnership at any time. -When the partnership ends, the web page entries related to the -partner are removed in the current listing (entries in former years remain). -Partnerships may end for several reasons: -<ul> -<li>the equipment that was loaned is withdrawn -<li>the service is no longer provided -<li>the goals of the partners no longer coincide with the goals of Debian -</ul> - -<h3>Are there other ways my organization can contribute to Debian?</h3> -<div class="centerblock"> -<p> -For donations of money, equipment, or services, visit our -<a href="../../donations">donations</a> page.</p> - -<p> -Sponsorship of DebConf (the annual Debian Conference) is handled by -each year's DebConf Organization Team. -For DebConf Sponsorship, visit the -<a href="https://www.debconf.org">DebConf</a> page.</p> - -<p> -Debian LTS funding is handled by the LTS Team. -For LTS funding, visit the -<a href="https://wiki.debian.org/LTS">LTS</a> wiki page.</p> - -<p> -If you have another idea that does not suit the above suggestion, -<a href="../../contact">contact us</a>. -</p> -</div> diff --git a/greek/partners/2017/Makefile b/greek/partners/2017/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/partners/2017/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/partners/2017/index.wml b/greek/partners/2017/index.wml deleted file mode 100644 index 75ec3ef9bd9..00000000000 --- a/greek/partners/2017/index.wml +++ /dev/null @@ -1,25 +0,0 @@ -#use wml::debian::template title="Debian Partners for 2017" -#use wml::debian::recent_list -#include "$(ENGLISHDIR)/partners/index.include" -#use wml::debian::translation-check translation="2364043ee09abec2ab4aead9d75aa82206045aa5" maintainer="galaxico" - - -<p>Information about the current partners program -and list of current partners can be viewed at the -<a href="..">main partners program page</a>. - -<h3>2017 Partners Program conditions</h3> - -<p>For more information on the Debian Partners Program for the year 2017, visit -the <a href="./partners">2017 Partners Program</a>.</p> - -<h3>2017 Partners</h3> - -#include "$(ENGLISHDIR)/partners/2017/partners.data" - -<hrline> - -<h3>DebConf17 Sponsors</h3> - -<p>The DebConf17 Sponsors are listed in the -<a href="https://debconf17.debconf.org">DebConf17 website</a>.</p> diff --git a/greek/partners/2017/partners.wml b/greek/partners/2017/partners.wml deleted file mode 100644 index 2a7e8d5a50c..00000000000 --- a/greek/partners/2017/partners.wml +++ /dev/null @@ -1,119 +0,0 @@ -#use wml::debian::template title="Debian Partners Program 2017 - description" -#use wml::debian::translation-check translation="f7210a80d7468806cac65059e70b3f611bfaab48" maintainer="galaxico" - -<h3>What is the Debian Partners Program?</h3> -<div class="centerblock"> - <p>The Partners Program was created to recognize companies and organizations - that provide ongoing assistance to the Debian project. Because of the substantial - support provided by these partners, we have been able to expand and improve - Debian. We would like to officially recognize their efforts, and continue - to maintain a good working relationship.</p> -</div> - -<h3>What are the criteria for Partners?</h3> - There are several types of partnerships. - -<ul> -<li><b>Development Partners</b><br> - <ul> - <li> provide equipment to Debian (at greatly reduced cost or on extended loan) - <li> provide equipment for use at conferences, trade shows, etc. - <li> provide a hardware based service to Debian (net access, accounts, etc.) - <li> commercial vendors who maintain key Debian packages - <li> assist or lead efforts to port and maintain Debian packages - on their hardware - <li> provide free or reduced cost technical service or consulting to Debian - </ul> -<li><b>Service Partners</b><br> - <ul> - <li> assist Debian in distribution of releases - <li> provide a forum for Debian's press releases and announcements - <li> provide a free or reduced cost non technical service to Debian - </ul> -<li><b>Financial Partners</b><br> - <ul> - <li>Provide ongoing financial support, - like revenue sharing programs. - </ul> -</ul> - -<p> -To be a partner, at least one of the criteria above must be met. -Partners who fall under more than one category can be listed under each -category that they qualify for. - -<h3>What does Debian do for the partners?</h3> - Debian will work closely with all partners to ensure that Debian -understands the partners needs and concerns, and vice versa. This will -enable Debian to remain properly focused within the market through -the partner's feedback. - -<p> - Each partner will have space on the Debian partners web page of that year - describing the nature of the partnership. -The partner may provide links to be included in this information. - -<!-- -<p> - For companies supplying hardware for porting projects, this page will be - linked from the relevant porting pages directly as well. - --> - -<h3>What do the partners do for Debian?</h3> -In addition to meeting the criteria for partnership stated above, -the partners should prominently mention Debian in the areas affected by the -partnership. -They should work with Debian to promote the projects interests. -Possibilities include: -<ul> -<li> Links to relevant Debian web pages -<li> Advertising Banners/Buttons/Splashes -<li> Links to current Debian News/Events/Projects -<li> ...and many more! -</ul> - - -<h3>How does a vendor become a partner?</h3> - -An email should be sent to -<a href="mailto:partners@debian.org">partners@debian.org</a> -with a <a href="../partners-form">proposal</a> for partnership. -This proposal will be reviewed -by Debian and discussed with the prospective partner. Debian will -then make a decision on whether or not a partnership is possible. - - -<h3>How and when do partnerships end?</h3> - -Debian or the partner may choose to end the partnership at any time. -When the partnership ends, the web page entries related to the -partner are removed in the current listing (entries in former years remain). -Partnerships may end for several reasons: -<ul> -<li>the equipment that was loaned is withdrawn -<li>the service is no longer provided -<li>the goals of the partners no longer coincide with the goals of Debian -</ul> - -<h3>Are there other ways my organization can contribute to Debian?</h3> -<div class="centerblock"> -<p> -For donations of money, equipment, or services, visit our -<a href="../../donations">donations</a> page.</p> - -<p> -Sponsorship of DebConf (the annual Debian Conference) is handled by -each year's DebConf Organization Team. -For DebConf Sponsorship, visit the -<a href="https://www.debconf.org">DebConf</a> page.</p> - -<p> -Debian LTS funding is handled by the LTS Team. -For LTS funding, visit the -<a href="https://wiki.debian.org/LTS">LTS</a> wiki page.</p> - -<p> -If you have another idea that does not suit the above suggestion, -<a href="../../contact">contact us</a>. -</p> -</div> diff --git a/greek/partners/2018/Makefile b/greek/partners/2018/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/partners/2018/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/partners/2018/index.wml b/greek/partners/2018/index.wml deleted file mode 100644 index 23929a5aa94..00000000000 --- a/greek/partners/2018/index.wml +++ /dev/null @@ -1,25 +0,0 @@ -#use wml::debian::template title="Debian Partners for 2018" -#use wml::debian::recent_list -#include "$(ENGLISHDIR)/partners/index.include" -#use wml::debian::translation-check translation="6138cc7f51274a495f7383ebf5733c86238606ec" maintainer="galaxico" - - -<p>Information about the current partners program -and list of current partners can be viewed at the -<a href="..">main partners program page</a>. - -<h3>2018 Partners Program conditions</h3> - -<p>For more information on the Debian Partners Program for the year 2018, visit -the <a href="./partners">2018 Partners Program</a>.</p> - -<h3>2018 Partners</h3> - -#include "$(ENGLISHDIR)/partners/2018/partners.data" - -<hrline> - -<h3>DebConf18 Sponsors</h3> - -<p>The DebConf18 Sponsors are listed in the -<a href="https://debconf18.debconf.org">DebConf18 website</a>.</p> diff --git a/greek/partners/2018/partners.wml b/greek/partners/2018/partners.wml deleted file mode 100644 index 25e36e70c00..00000000000 --- a/greek/partners/2018/partners.wml +++ /dev/null @@ -1,119 +0,0 @@ -#use wml::debian::template title="Debian Partners Program 2018 - description" -#use wml::debian::translation-check translation="6138cc7f51274a495f7383ebf5733c86238606ec" maintainer="galaxico" - -<h3>What is the Debian Partners Program?</h3> -<div class="centerblock"> - <p>The Partners Program was created to recognize companies and organizations - that provide ongoing assistance to the Debian project. Because of the substantial - support provided by these partners, we have been able to expand and improve - Debian. We would like to officially recognize their efforts, and continue - to maintain a good working relationship.</p> -</div> - -<h3>What are the criteria for Partners?</h3> - There are several types of partnerships. - -<ul> -<li><b>Development Partners</b><br> - <ul> - <li> provide equipment to Debian (at greatly reduced cost or on extended loan) - <li> provide equipment for use at conferences, trade shows, etc. - <li> provide a hardware based service to Debian (net access, accounts, etc.) - <li> commercial vendors who maintain key Debian packages - <li> assist or lead efforts to port and maintain Debian packages - on their hardware - <li> provide free or reduced cost technical service or consulting to Debian - </ul> -<li><b>Service Partners</b><br> - <ul> - <li> assist Debian in distribution of releases - <li> provide a forum for Debian's press releases and announcements - <li> provide a free or reduced cost non technical service to Debian - </ul> -<li><b>Financial Partners</b><br> - <ul> - <li>Provide ongoing financial support, - like revenue sharing programs. - </ul> -</ul> - -<p> -To be a partner, at least one of the criteria above must be met. -Partners who fall under more than one category can be listed under each -category that they qualify for. - -<h3>What does Debian do for the partners?</h3> - Debian will work closely with all partners to ensure that Debian -understands the partners needs and concerns, and vice versa. This will -enable Debian to remain properly focused within the market through -the partner's feedback. - -<p> - Each partner will have space on the Debian partners web page of that year - describing the nature of the partnership. -The partner may provide links to be included in this information. - -<!-- -<p> - For companies supplying hardware for porting projects, this page will be - linked from the relevant porting pages directly as well. - --> - -<h3>What do the partners do for Debian?</h3> -In addition to meeting the criteria for partnership stated above, -the partners should prominently mention Debian in the areas affected by the -partnership. -They should work with Debian to promote the projects interests. -Possibilities include: -<ul> -<li> Links to relevant Debian web pages -<li> Advertising Banners/Buttons/Splashes -<li> Links to current Debian News/Events/Projects -<li> ...and many more! -</ul> - - -<h3>How does a vendor become a partner?</h3> - -An email should be sent to -<a href="mailto:partners@debian.org">partners@debian.org</a> -with a <a href="../partners-form">proposal</a> for partnership. -This proposal will be reviewed -by Debian and discussed with the prospective partner. Debian will -then make a decision on whether or not a partnership is possible. - - -<h3>How and when do partnerships end?</h3> - -Debian or the partner may choose to end the partnership at any time. -When the partnership ends, the web page entries related to the -partner are removed in the current listing (entries in former years remain). -Partnerships may end for several reasons: -<ul> -<li>the equipment that was loaned is withdrawn -<li>the service is no longer provided -<li>the goals of the partners no longer coincide with the goals of Debian -</ul> - -<h3>Are there other ways my organization can contribute to Debian?</h3> -<div class="centerblock"> -<p> -For donations of money, equipment, or services, visit our -<a href="../../donations">donations</a> page.</p> - -<p> -Sponsorship of DebConf (the annual Debian Conference) is handled by -each year's DebConf Organization Team. -For DebConf Sponsorship, visit the -<a href="https://www.debconf.org">DebConf</a> page.</p> - -<p> -Debian LTS funding is handled by the LTS Team. -For LTS funding, visit the -<a href="https://wiki.debian.org/LTS">LTS</a> wiki page.</p> - -<p> -If you have another idea that does not suit the above suggestion, -<a href="../../contact">contact us</a>. -</p> -</div> diff --git a/greek/partners/2019/Makefile b/greek/partners/2019/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/partners/2019/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/partners/2019/index.wml b/greek/partners/2019/index.wml deleted file mode 100644 index e63637520d0..00000000000 --- a/greek/partners/2019/index.wml +++ /dev/null @@ -1,25 +0,0 @@ -#use wml::debian::template title="Debian Partners for 2019" -#use wml::debian::recent_list -#include "$(ENGLISHDIR)/partners/index.include" -#use wml::debian::translation-check translation="241ba6624b17b96c8e8e21b0eabdc4b08114b5b4" maintainer="galaxico" - - -<p>Information about the current partners program -and list of current partners can be viewed at the -<a href="..">main partners program page</a>. - -<h3>2019 Partners Program conditions</h3> - -<p>For more information on the Debian Partners Program for the year 2019, visit -the <a href="./partners">2019 Partners Program</a>.</p> - -<h3>2019 Partners</h3> - -#include "$(ENGLISHDIR)/partners/2019/partners.data" - -<hrline> - -<h3>DebConf19 Sponsors</h3> - -<p>The DebConf19 Sponsors are listed in the -<a href="https://debconf19.debconf.org">DebConf19 website</a>.</p> diff --git a/greek/partners/2019/partners.wml b/greek/partners/2019/partners.wml deleted file mode 100644 index a8f1300bf2f..00000000000 --- a/greek/partners/2019/partners.wml +++ /dev/null @@ -1,119 +0,0 @@ -#use wml::debian::template title="Debian Partners Program 2019 - description" -#use wml::debian::translation-check translation="774a35e9c48f7157e2a3a171061a9ac9188af90b" maintainer="galaxico" - -<h3>What is the Debian Partners Program?</h3> -<div class="centerblock"> - <p>The Partners Program was created to recognize companies and organizations - that provide ongoing assistance to the Debian project. Because of the substantial - support provided by these partners, we have been able to expand and improve - Debian. We would like to officially recognize their efforts, and continue - to maintain a good working relationship.</p> -</div> - -<h3>What are the criteria for Partners?</h3> - There are several types of partnerships. - -<ul> -<li><b>Development Partners</b><br> - <ul> - <li> provide equipment to Debian (at greatly reduced cost or on extended loan) - <li> provide equipment for use at conferences, trade shows, etc. - <li> provide a hardware based service to Debian (net access, accounts, etc.) - <li> commercial vendors who maintain key Debian packages - <li> assist or lead efforts to port and maintain Debian packages - on their hardware - <li> provide free or reduced cost technical service or consulting to Debian - </ul> -<li><b>Service Partners</b><br> - <ul> - <li> assist Debian in distribution of releases - <li> provide a forum for Debian's press releases and announcements - <li> provide a free or reduced cost non technical service to Debian - </ul> -<li><b>Financial Partners</b><br> - <ul> - <li>Provide ongoing financial support, - like revenue sharing programs. - </ul> -</ul> - -<p> -To be a partner, at least one of the criteria above must be met. -Partners who fall under more than one category can be listed under each -category that they qualify for. - -<h3>What does Debian do for the partners?</h3> - Debian will work closely with all partners to ensure that Debian -understands the partners needs and concerns, and vice versa. This will -enable Debian to remain properly focused within the market through -the partner's feedback. - -<p> - Each partner will have space on the Debian partners web page of that year - describing the nature of the partnership. -The partner may provide links to be included in this information. - -<!-- -<p> - For companies supplying hardware for porting projects, this page will be - linked from the relevant porting pages directly as well. - --> - -<h3>What do the partners do for Debian?</h3> -In addition to meeting the criteria for partnership stated above, -the partners should prominently mention Debian in the areas affected by the -partnership. -They should work with Debian to promote the projects interests. -Possibilities include: -<ul> -<li> Links to relevant Debian web pages -<li> Advertising Banners/Buttons/Splashes -<li> Links to current Debian News/Events/Projects -<li> ...and many more! -</ul> - - -<h3>How does a vendor become a partner?</h3> - -An email should be sent to -<a href="mailto:partners@debian.org">partners@debian.org</a> -with a <a href="../partners-form">proposal</a> for partnership. -This proposal will be reviewed -by Debian and discussed with the prospective partner. Debian will -then make a decision on whether or not a partnership is possible. - - -<h3>How and when do partnerships end?</h3> - -Debian or the partner may choose to end the partnership at any time. -When the partnership ends, the web page entries related to the -partner are removed in the current listing (entries in former years remain). -Partnerships may end for several reasons: -<ul> -<li>the equipment that was loaned is withdrawn -<li>the service is no longer provided -<li>the goals of the partners no longer coincide with the goals of Debian -</ul> - -<h3>Are there other ways my organization can contribute to Debian?</h3> -<div class="centerblock"> -<p> -For donations of money, equipment, or services, visit our -<a href="../../donations">donations</a> page.</p> - -<p> -Sponsorship of DebConf (the annual Debian Conference) is handled by -each year's DebConf Organization Team. -For DebConf Sponsorship, visit the -<a href="https://www.debconf.org">DebConf</a> page.</p> - -<p> -Debian LTS funding is handled by the LTS Team. -For LTS funding, visit the -<a href="https://wiki.debian.org/LTS">LTS</a> wiki page.</p> - -<p> -If you have another idea that does not suit the above suggestion, -<a href="../../contact">contact us</a>. -</p> -</div> diff --git a/greek/partners/2021/Makefile b/greek/partners/2021/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/partners/2021/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/partners/2021/index.wml b/greek/partners/2021/index.wml deleted file mode 100644 index 66f270e90a8..00000000000 --- a/greek/partners/2021/index.wml +++ /dev/null @@ -1,25 +0,0 @@ -#use wml::debian::template title="Debian Partners for 2021" -#use wml::debian::recent_list -#include "$(ENGLISHDIR)/partners/index.include" -#use wml::debian::translation-check translation="2c4b4c13f8074c3e9847dac51a344706d2fa2640" maintainer="galaxico" - - -<p>Information about the current partners program -and list of current partners can be viewed at the -<a href="..">main partners program page</a>. - -<h3>2021 Partners Program conditions</h3> - -<p>For more information on the Debian Partners Program for the year 2021, visit -the <a href="./partners">2021 Partners Program</a>.</p> - -<h3>2021 Partners</h3> - -#include "$(ENGLISHDIR)/partners/2021/partners.data" - -<hrline> - -<h3>DebConf21 Sponsors</h3> - -<p>The DebConf21 Sponsors are listed in the -<a href="https://debconf21.debconf.org">DebConf21 website</a>.</p> diff --git a/greek/partners/2021/partners.wml b/greek/partners/2021/partners.wml deleted file mode 100644 index 2d8d9ecd5bb..00000000000 --- a/greek/partners/2021/partners.wml +++ /dev/null @@ -1,119 +0,0 @@ -#use wml::debian::template title="Debian Partners Program 2021 - description" -#use wml::debian::translation-check translation="2c4b4c13f8074c3e9847dac51a344706d2fa2640" maintainer="galaxico" - -<h3>What is the Debian Partners Program?</h3> -<div class="centerblock"> - <p>The Partners Program was created to recognize companies and organizations - that provide ongoing assistance to the Debian project. Because of the substantial - support provided by these partners, we have been able to expand and improve - Debian. We would like to officially recognize their efforts, and continue - to maintain a good working relationship.</p> -</div> - -<h3>What are the criteria for Partners?</h3> - There are several types of partnerships. - -<ul> -<li><b>Development Partners</b><br> - <ul> - <li> provide equipment to Debian (at greatly reduced cost or on extended loan) - <li> provide equipment for use at conferences, trade shows, etc. - <li> provide a hardware based service to Debian (net access, accounts, etc.) - <li> commercial vendors who maintain key Debian packages - <li> assist or lead efforts to port and maintain Debian packages - on their hardware - <li> provide free or reduced cost technical service or consulting to Debian - </ul> -<li><b>Service Partners</b><br> - <ul> - <li> assist Debian in distribution of releases - <li> provide a forum for Debian's press releases and announcements - <li> provide a free or reduced cost non technical service to Debian - </ul> -<li><b>Financial Partners</b><br> - <ul> - <li>Provide ongoing financial support, - like revenue sharing programs. - </ul> -</ul> - -<p> -To be a partner, at least one of the criteria above must be met. -Partners who fall under more than one category can be listed under each -category that they qualify for. - -<h3>What does Debian do for the partners?</h3> - Debian will work closely with all partners to ensure that Debian -understands the partners needs and concerns, and vice versa. This will -enable Debian to remain properly focused within the market through -the partner's feedback. - -<p> - Each partner will have space on the Debian partners web page of that year - describing the nature of the partnership. -The partner may provide links to be included in this information. - -<!-- -<p> - For companies supplying hardware for porting projects, this page will be - linked from the relevant porting pages directly as well. - --> - -<h3>What do the partners do for Debian?</h3> -In addition to meeting the criteria for partnership stated above, -the partners should prominently mention Debian in the areas affected by the -partnership. -They should work with Debian to promote the projects interests. -Possibilities include: -<ul> -<li> Links to relevant Debian web pages -<li> Advertising Banners/Buttons/Splashes -<li> Links to current Debian News/Events/Projects -<li> ...and many more! -</ul> - - -<h3>How does a vendor become a partner?</h3> - -An email should be sent to -<a href="mailto:partners@debian.org">partners@debian.org</a> -with a <a href="../partners-form">proposal</a> for partnership. -This proposal will be reviewed -by Debian and discussed with the prospective partner. Debian will -then make a decision on whether or not a partnership is possible. - - -<h3>How and when do partnerships end?</h3> - -Debian or the partner may choose to end the partnership at any time. -When the partnership ends, the web page entries related to the -partner are removed in the current listing (entries in former years remain). -Partnerships may end for several reasons: -<ul> -<li>the equipment that was loaned is withdrawn -<li>the service is no longer provided -<li>the goals of the partners no longer coincide with the goals of Debian -</ul> - -<h3>Are there other ways my organization can contribute to Debian?</h3> -<div class="centerblock"> -<p> -For donations of money, equipment, or services, visit our -<a href="../../donations">donations</a> page.</p> - -<p> -Sponsorship of DebConf (the annual Debian Conference) is handled by -each year's DebConf Organization Team. -For DebConf Sponsorship, visit the -<a href="https://www.debconf.org">DebConf</a> page.</p> - -<p> -Debian LTS funding is handled by the LTS Team. -For LTS funding, visit the -<a href="https://wiki.debian.org/LTS">LTS</a> wiki page.</p> - -<p> -If you have another idea that does not suit the above suggestion, -<a href="../../contact">contact us</a>. -</p> -</div> diff --git a/greek/partners/Makefile b/greek/partners/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/partners/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/partners/index.wml b/greek/partners/index.wml deleted file mode 100644 index d537a9d5f1b..00000000000 --- a/greek/partners/index.wml +++ /dev/null @@ -1,28 +0,0 @@ -#use wml::debian::template title="Debian Partners" BARETITLE=true -#use wml::debian::recent_list -#include "$(ENGLISHDIR)/partners/index.include" -#use wml::debian::translation-check translation="2364043ee09abec2ab4aead9d75aa82206045aa5" maintainer="galaxico" - - -<H3>What is the Partners Program?</H3> -<div class="centerblock"> - <p>The Partners Program was created to recognize companies and organizations - that provide ongoing assistance to Debian. Because of the substantial - support provided by these partners, we have been able to expand and improve - Debian. We would like to officially recognize their efforts, and continue - to maintain a good working relationship.</p> - -<p>For more information on the Debian Partners Program, visit - <A HREF="$(CUR_YEAR)/partners">Partners Program</A>.</p> - -<h3><a href="$(CUR_YEAR)/">Current Partners</a></h3> - -#include "$(ENGLISHDIR)/partners/$(CUR_YEAR)/partners.data" - -<hrline> - -#include "$(ENGLISHDIR)/partners/years.include" -<p>Information about partners program and list of partners from previous years can be viewed using the following pages: -<:= get_past_partners_list(); :> - -</div> diff --git a/greek/partners/partners-form.wml b/greek/partners/partners-form.wml deleted file mode 100644 index c3d79584152..00000000000 --- a/greek/partners/partners-form.wml +++ /dev/null @@ -1,96 +0,0 @@ -#use wml::debian::template title="Debian Partners Program - New Partner Proposal" -#use wml::debian::translation-check translation="302d741b69f5f237b778c8cab313998345eb27b7" maintainer="galaxico" - -<div class="centerblock"> - - <p>The success of Debian has been due to the people and - organizations, who support the many Debian projects. We believe that - our Partners play a crucial role in the continued development of - Debian and related applications. Debian partners have provided - substantial assistance to the cooperative development, availability, - and day to day support of our world wide presence.</p> - - <p>If you would like to become an actively contributing part - of the Debian community, and feel that you can contribute expertise - and resources to helping Debian, please take a moment to tell us a - bit about your company and your ideas. Let us know how your organization - could not only contribute to Debian, but how a continued relationship might - benefit your organization.</p> - - <p>You may either use the form below, or email your proposal to - <A HREF="mailto:partners@debian.org">partners@debian.org</A>. - We look forward to hearing from you.</p> - -</div> - - <hr> - -<div class="center"> -<form method=post action="https://cgi.debian.org/cgi-bin/submit_partner.pl"> -<p> -<input type="hidden" name="success" value="https://www.debian.org/partners/thankyou"> -</p> -<p>Company name: -<input type="text" name="partner" size="50"></p> - -<p>Website: -<input type="text" name="url" size="50"></p> - -<p>Contact person for Debian partnership: -<input type="text" name="contact_person" size="50"></p> - -<p>Email address for Debian partnership: -<input type="text" name="email" size="50"></p> - -<p> -<textarea name="description" cols="80" rows="24" > - -Brief description of your company: - - - - -Primary products/services: - - - - -How are you currently using Debian and how do you plan -to utilize Debian in the future? - - - - -What are you doing to aid the Debian project? -Please provide detailed information. - - - - -How is Debian helping to accomplish your goals? - - - - -What could Debian do to help you better achieve your goals? - - - -Any other comments / questions you may have: - - - -</textarea> -</p> -<p> -<input type="submit" value="Send as e-mail to Debian Partners Program" name="submit"> -</p> -</form> -</div> - -# Version History -# v1.16 1999-05-24 Added verbage and corrections. jwest -# v1.15 1999-05-23 Fixed version history, added verbage. jwest -# v0... ??? -# v0.1 1999-05-20 changed relative to absolute links. jwest -# v0.0 1999-05-19 Created form for use with cgimail. jwest diff --git a/greek/partners/partners.wml b/greek/partners/partners.wml deleted file mode 100644 index c68cd359d2d..00000000000 --- a/greek/partners/partners.wml +++ /dev/null @@ -1,110 +0,0 @@ -#use wml::debian::template title="Debian Partners Program - description" -#use wml::debian::translation-check translation="5299291e877dcc4aceca30fdd6ebe880a8594d35" maintainer="galaxico" - - -<h3>What is the Debian Partners Program?</h3> - This program provides a way to recognize companies and projects -that provide ongoing assistance to the Debian project. -Since these partners are providing a -service of some sort to Debian, we will officially recognize them and -maintain a good working relationship with them. - -<p> -Donations to the Debian project do not qualify an organization for Partner -status. Donations will be recognized separately. - - -<h3>What are the criteria for Partners?</h3> - There are several types of partnerships. - Development partners contribute directly to the development of - the distributions and related materials. - Service partners provide other services to Debian. -<ul> -<li><b>Development Partners</b><br> - <ul> - <li> provide equipment to Debian (at greatly reduced cost or on extended loan) - <li> provide equipment for use at conferences, trade shows, etc. - <li> provide a hardware based service to Debian (net access, accounts, etc.) - <li> commercial vendors who maintain key Debian packages - <li> assist or lead efforts to port and maintain Debian packages - on their hardware - <li> provide free or reduced cost technical service or consulting to Debian - </ul> -<li><b>Service Partners</b><br> - <ul> - <li> assist Debian in distribution of releases - <li> provide a forum for Debian's press releases and announcements - <li> provide a free or reduced cost non technical service to Debian - </ul> -</ul> -<p> -To be a partner, at least one of the criteria above must be met. -Partners who fall under more than one category can be listed under each -category that they qualify for. - - -<h3>What does Debian do for the partners?</h3> - Debian will work closely with all partners to ensure that Debian -understands the partners needs and concerns, and vice versa. This will -enable Debian to remain properly focused within the market through -the partner's feedback. - -<p> - Each partner will have space on the Debian partners web page that - describes the nature of the partnership. -The partner may provide links to be included in this information. - -<!-- -<p> - For companies supplying hardware for porting projects, this page will be - linked from the relevant porting pages directly as well. - --> - - - -<h3>What do the partners do for Debian?</h3> -In addition to meeting the criteria for partnership stated above, -the partners should prominently mention Debian in the areas affected by the -partnership. -They should work with Debian to promote the projects interests. -Possibilities include: -<ul> -<li> Links to relevant Debian web pages -<li> Advertising Banners/Buttons/Splashes -<li> Links to current Debian News/Events/Projects -<li> ...and many more! -</ul> - - -<h3>How does a vendor become a partner?</h3> - -An email should be sent to -<a href="mailto:partners@debian.org">partners@debian.org</a> -with a <a href="partners-form">proposal</a> for partnership. -This proposal will be reviewed -by Debian and discussed with the prospective partner. Debian will -then make a decision on whether or not a partnership is possible. - - -<h3>How and when do partnerships end?</h3> - -Debian or the partner may choose to end the partnership at any time. -When the partnership ends, the web page entries related to the -partner are removed. Partnerships may end for several reasons: -<ul> -<li>the equipment that was loaned is withdrawn -<li>the service is no longer provided -<li>the goals of the partners no longer coincide with the goals of Debian -</ul> - -# Version History -# v1.3 1999-05-26 Version history version repair jwest -# v0.81 1999-05-20 JJW Added link to partners-form -# v0.8 1999-03-11 NL Added 'How to become a Partner' section, some language cleanups -# v0.7 1999-03-05 NL Revisions to partnership qualifications -# v0.6 1999-03-04 NL Minor edits and cleanups -# v0.5 1998-11-09 NL Minor changes in termination of partner status -# v0.4 1998-11-05 NL Modified after some feedback from potential partners -# v0.3 1998-10-28 NL Modified after comments from debian-private -# v0.2 1998-07-30 NL Modified after comments from debian-publicity -# v0.1 1998-07-20 NL Created Proposal diff --git a/greek/partners/thankyou.wml b/greek/partners/thankyou.wml deleted file mode 100644 index 493ac4094f5..00000000000 --- a/greek/partners/thankyou.wml +++ /dev/null @@ -1,16 +0,0 @@ -#use wml::debian::template title="Debian Partners Program - Thank You" NOHEADER=true -#use wml::debian::translation-check translation="7bfc805a5c07d173ae8bf82f220c8ea41f83860d" maintainer="galaxico" - -<h1>Thank you for your proposal</h1> - -<hr> - -We will be reviewing your proposal, and will be in contact with you -in the near future.<br> -<br> -Thanks again,<br> -<br> -<a href="./">Debian Partners Program</a> - -# Revision history -# 05-19-99 jwest@debian.org diff --git a/greek/ports/alpha/Makefile b/greek/ports/alpha/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/alpha/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/alpha/index.wml b/greek/ports/alpha/index.wml deleted file mode 100644 index 7bd69a182bc..00000000000 --- a/greek/ports/alpha/index.wml +++ /dev/null @@ -1,28 +0,0 @@ -#use wml::debian::template title="Alpha Port" NOHEADER="true" -#include "$(ENGLISHDIR)/ports/alpha/menu.inc" -#use wml::debian::translation-check translation="8da95139c3595d47371ba8d288784086ae2ebacd" maintainer="galaxico" - -<h1>Debian GNU/Linux on Alpha Systems</h1> - -<p>The Alpha port is <a -href="https://lists.debian.org/debian-devel-announce/2009/10/msg00000.html">\ -no longer officially supported</a> in the Debian stable release. -The last release with official Alpha support was <a -href="https://www.debian.org/releases/lenny/releasenotes">Debian 5.0 -<q>lenny</q></a>. -For further information, please visit the <a href="port-status">port -status page</a>.</p> - - -<p>If you'd like to join us in this project, please peruse this page -and <a href="links#lists">join the mailing list</a>. -Things can be fast-moving and we all -realise that not everyone has the technical expertise to do it all, -but any help that people can or want to offer would be gladly -accepted.</p> - -<p><em>Cheers and happy Alpha-ing!<br /> -Helge Kreutzmann (former maintainer of these webpages),<br /> -Chris Chimelis (original maintainer of these webpages)</em></p> - -<p class="center"><img src="alpha-penguin.jpg" /></p> diff --git a/greek/ports/alpha/links.wml b/greek/ports/alpha/links.wml deleted file mode 100644 index 6330a7f17b7..00000000000 --- a/greek/ports/alpha/links.wml +++ /dev/null @@ -1,97 +0,0 @@ -#use wml::debian::template title="Alpha Port -- Links" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/alpha/menu.inc" -#use wml::debian::translation-check translation="b9cb4ebb36a3cc48be8b8b2ac3b06f113491d26f" maintainer="galaxico" - -<h1>Alpha Links</h1> - -<ul> - -<li><a href="http://www.alphalinux.org/">AlphaLinux.org</a><br /> -This page pretty much contains everything you may want or need to know -about running Linux on Alphas. Includes numerous links and an excellent -news section. This site is also the home of the official -<a href="http://www.alphalinux.org/docs/">FAQs and HOWTOs</a> related to Linux on Alphas.</li> - -<li><a href="http://www.alphalinux.org/docs/alpha-howto.html">\ -Intro to Alpha Systems</a><br /> -A rather old, but still informative document for the new or experienced user. -It describes -the differences between Alphas and other architectures as well as describing -the different systems. <b>If you have an old system and you really need to -know what your system is -despite what it says on the case, see -<a href="http://www.alphalinux.org/docs/alpha-howto.html#The%20Systems">this subsection</a>.</b></li> - -<li><a href="http://www.alphalinux.org/faq/FAQ.html">Linux/Alpha FAQ</a><br /> -A good source of information, the Linux/Alpha FAQ was originally put -together by Red Hat users, but has expanded to include more general info -and is still a great reference.</li> - -<li><a href="http://www.alphalinux.org/faq/SRM-HOWTO/index.html">SRM Firmware HOWTO</a><br /> -The official HOWTO for systems using SRM firmware. If you need to use -<a href="https://sourceforge.net/projects/aboot/">aboot</a> -to boot your Alpha, this is the page for you. -#This HOWTO is included in -#the latest version of the -#<a href="https://tracker.debian.org/pkg/aboot">Debian packet</a> -#as well. -</li> - -<li><a href="http://alphalinux.org/faq/MILO-HOWTO/t1.html">MILO HOWTO</a><br /> -The official HOWTO for MILO. Please note that -<a href="$(HOME)/devel/debian-installer/">debian-installer</a> lacks MILO support. -SRM is highly recommended, but if you cannot switch -and you are interested -in MILO support for post-Woody releases of Debian, then read -<a href="https://lists.debian.org/debian-alpha/2004/debian-alpha-200402/msg00003.html">this post to debian-alpha</a> and subscribe to -<a href="https://lists.debian.org/debian-boot/">debian-boot</a> to add MILO support. The latest known locations -are -<a href="http://www.suse.de/~stepan/">Stepan Rainauers page</a>, <a href="ftp://genie.ucd.ie/pub/alpha/milo/">Nikita Schmidt</a> -and the -work done by <a href="http://dev.gentoo.org/~taviso/milo/">Gentoo</a>.</li> - -<li><a href="http://www.alphalinux.org/faq/alphabios-howto.html">AlphaBIOS Firmware HOWTO</a><br /> -The official HOWTO for systems using AlphaBIOS firmware.</li> - -<li><a href="https://digital.com/about/dec/">Digital's Old Documentation Library</a> <!-- with a <a href="ftp://ftp.unix-ag.org/user/nils/Alpha-Docs/">Mirror by Nils Faerber</a> --> </li> - -<!-- <li><a href="http://www.alphanews.net/">alphanews.net</a><br /> -Some alpha related news are posted here, for several OS which run or used -to run on alphas.</li> --> - -<li><a href="http://www.helgefjell.de/browser.php">Browsers running on Linux Alpha</a><br /> -If you have troubles with your browser in an 64bit environment (should not be the case anymore, nowadays) or -if you just want to try out a new one, here you find a list of known-to work (and not to work) browsers.</li> - -<li><a href="http://alphacore.info/wiki/">AlphaCore WikiPage</a><br /> -This Wiki, currently mainly focused on AlphaCore (Fedora Core on Alpha) also -intends to collect general useful alpha related information.</li> -</ul> - -<p> -Thanks to Nils Faerber for allowing me to -include parts of his link collection here. -</p> - -<h1><a name="lists">Mailing Lists</a></h1> - -<ul> - -<li>The debian-alpha mailing list<br /> -Send an email with the subject 'subscribe' to -<email "debian-alpha-request@lists.debian.org" /> to subscribe. -<a href="https://lists.debian.org/debian-alpha/">Archives are -available</a>.</li> - -<li>Red Hat's Linux/Alpha List - -<p> -This list is oriented towards Red Hat Linux/Alpha users, but also has -valuable tips for general Linux-Alpha issues. To subscribe, -go to the <a href="https://www.redhat.com/mailman/listinfo/axp-list">List Info page</a>. -<a href="https://www.redhat.com/archives/axp-list/">Archives</a> of this list are also available. -An alternative (searchable) archive can be found at -<url "http://www.lib.uaa.alaska.edu/axp-list/" />. -</p></li> - -</ul> diff --git a/greek/ports/alpha/port-status.wml b/greek/ports/alpha/port-status.wml deleted file mode 100644 index f28a808274a..00000000000 --- a/greek/ports/alpha/port-status.wml +++ /dev/null @@ -1,53 +0,0 @@ -#use wml::debian::template title="Alpha Port -- Status" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/alpha/menu.inc" -#use wml::debian::translation-check translation="b8114b588961778dbd04974c1464a2f388a90c28" maintainer="galaxico" - -<h1>Debian GNU/Linux on Alpha – Status</h1> - -<p>The Alpha port, first officially released with Debian 2.1 -<q>slink</q>, is now archived: the last release with official support -for it was Debian 5.0 <q>lenny</q>. -</p> - -<h2>Debian GNU/Linux 5.0 <q>lenny</q></h2> - -<p>This is the last Debian release which includes the Alpha port.</p> - -<h2>Debian GNU/Linux 4.0 <q>etch</q></h2> - -<p>This release had support for Alpha, but only -those machines which can use SRM/aboot to boot can be installed with the - new installer.</p> - - -<h2>Debian GNU/Linux 3.1 <q>sarge</q></h2> - -<p>This release had full support for Alpha.</p> - -<h2>Debian GNU/Linux 3.0 <q>woody</q></h2> - -<p>This release had solid support for Alpha and is the last one to support - machines soly using milo (i.e. not SRM).</p> - -<h2>Debian GNU/Linux 2.2 <q>potato</q></h2> - -<p>Potato has much more software available and supports -more types of Alphas than slink did.</p> - -<h2>Debian GNU/Linux 2.1 <q>slink</q></h2> - -<p>The Alpha port was initially released with this release.</p> - -<h1>Hardware support</h1> - -<p>Quite a lot of hardware is now supported on Linux/Alpha. Unfortunately, - the exact combination of machine, hardware and kernel version is - non-trivial, so if you don't find your combo in - <a href="http://alphalinux.org/ALOHcl/">this list on alphalinux.org</a>, - and researching the - <a href="links#lists">list archives for Debian and Red Hat</a>-AXP-Lists - neither yields a result, then - <a href="https://lists.debian.org/debian-alpha/">subscribe</a> to the - Debian-Alpha list and ask. - Usually someone has tried already and can provide useful - information.</p> diff --git a/greek/ports/alpha/sys_types.wml b/greek/ports/alpha/sys_types.wml deleted file mode 100644 index 8e17082d2fb..00000000000 --- a/greek/ports/alpha/sys_types.wml +++ /dev/null @@ -1,1033 +0,0 @@ -#use wml::debian::template title="Alpha Port -- System Types" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/alpha/menu.inc" -#use wml::debian::translation-check translation="6f3adf6374f35194686f89dec2ba66b1ecf3bb5f" maintainer="galaxico" - -<p> -This list might not be complete, so if you see something that is not -on here or something that is incorrect please post it to -<a href="mailto:debian-alpha@lists.debian.org">debian-alpha</a> for verification -and inclusion. Please note that -<a href="https://www.gnu.org/software/hurd/gnumach.html">GNUMach</a> -currently only supports -<a href="https://www.gnu.org/software/hurd/faq.en.html#q2-3">IA 32</a> -based machines. As soon as porting to alpha is started, -this list will be updated to show which machines are actually supported.</p> - -#FIXME: Add links where appropriate, to e.g. BSDs info pages? -#FIXME: Also Niels has some machine specific links - -<br> -<br> -<table class="ridgetable"> -<tr> -<th>Model:</th> - -<th>Alias:</th> -<th>Supported by Linux</th> -<th>Supported by GNUMach</th> -</tr> - -<tr> -<td>21164 PICMG SBC (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part — single board computer)</td> - -<td>Takara/DMCC</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>DMCC 21264 PICMG (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part)</td> - -<td>Eiger <i>(Tsunami family, but with 1 p-chip)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Alphabook1</td> - -<td>Alphabook1/Burns <i>(Alpha Notebook family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Alpha Demonstration Unit (prototype unit)</td> - -<td>ADU</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164</td> - -<td>PC164 <i>(EB164 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164-BX</td> - -<td>Ruffian <i>(Samsung produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164-LX</td> - -<td>LX164 <i>(EB164 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164-SX</td> - -<td>SX164 <i>(EB164 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC164-UX</td> - -<td>Ruffian <i>(Samsung produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPC64</td> - -<td>Cabriolet <i>(EB64+ family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaPCI64</td> - -<td>Cabriolet <i>(EB64+ family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 200 4/100...166</td> - -<td>Mustang <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 200 4/233</td> - -<td>Mustang+ <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 205 4/133...333</td> - -<td>LX3 <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 250 4/300</td> - -<td>M3+ <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 255 4/233...300</td> - -<td>LX3+ <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 300 4/266</td> - -<td>Melmac <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 400 4/166</td> - -<td>Chinet <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 400 4/233...300</td> - -<td>Avanti <i>(Avanti family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 500 5/266...300</td> - -<td>Maverick <i>(Alcor family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 500 5/333...500</td> - -<td>Bret <i>(Alcor family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 600/266...300</td> - -<td>Alcor <i>(Alcor family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 600/300...433</td> - -<td>XLT <i>(Alcor family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaStation 600A</td> - -<td>Alcor-Primo <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td><a name="as800">AlphaServer 800</a> 5/333...500</td> - -<td>Corelle <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000 4/200</td> - -<td>Mikasa <i>(Mikasa family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000 4/233...266</td> - -<td>Mikasa+ <i>(Mikasa family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000 5/300</td> - -<td>Pinnacle <i>(Mikasa family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000 5/333...500</td> - -<td>Primo <i>(Mikasa family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000A 4/233...266</td> - -<td>Noritake <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000A 5/300</td> - -<td>Pinnacle <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 1000A 5/333...500</td> - -<td>Primo <i>(Noritake family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td><a name="as1200">AlphaServer 1200</a> 5/xxx</td> - -<td>Tincup/DaVinci <i>(Rawhide family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2000 4/xxx</td> - -<td>Demi-Sable <i>(Sable family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2000 5/xxx</td> - -<td>Demi-Gamma-Sable <i>(Sable family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2100 4/xxx</td> - -<td>Sable <i>(Sable family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2100 5/xxx</td> - -<td>Gamma-Sable <i>(Sable family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2000a 4/xxx</td> - -<td>Demi-Lynx</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2000a 5/xxx</td> - -<td>Demi-Gamma-Lynx</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2100a 4/xxx</td> - -<td>Lynx</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 2100a 5/xxx</td> - -<td>Gamma-Lynx</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 4000 5/xxx</td> - -<td>Wrangler/Durango <i>(Rawhide family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td><a name="as4100">AlphaServer 4100</a> 5/xxx</td> - -<td>Dodge <i>(Rawhide family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 8200</td> - -<td>TurboLaser <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer 8400</td> - -<td>TurboLaser <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS10</td> - -<td>Slate <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS15</td> - -<td>Hyperbrick II <i>(Titan family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS20</td> - -<td>Catamaran/Goldrush <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS20E</td> - -<td>Goldrack <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS20L</td> - -<td>Shark <i>(Tsunami family)</i> (orig. CS20 by API)</td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer DS25</td> - -<td>Granite <i>(Titan family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer ES40</td> - -<td>Clipper <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer ES45</td> - -<td>Privateer <i>(Titan family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer ES47</td> - -<td>Marvel 2P <i>(Marvel family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer ES80</td> - -<td>Marvel 4x2P <i>(Marvel family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS60</td> - -<td>TurboLaser <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS60E</td> - -<td>TurboLaser-Lite <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS80</td> - -<td>Wildfire <i>(Wildfire family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS1280</td> - -<td>Marvel 8P <i>(Marvel family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS140</td> - -# TL67 ? -<td>Turbo-Laser <i>(Turbolaser family)</i></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS160</td> - -<td>Wildfire <i>(Wildfire family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaServer GS320</td> - -<td>Wildfire <i>(Wildfire family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>Alpha XL-233...266</td> - -<td>XL <i>(Alpha XL family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AXPpci33</td> - -<td>Noname <i>(Noname family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 2000/300</td> - -<td>Jensen <i>(Jensen family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 2000/500</td> - -<td>Culzen <i>(Jensen family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/300</td> - -<td>Pelican</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/300L</td> - -<td>Pelica</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/300LX</td> - -<td>Pelica+</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/300X</td> - -<td>Pelican+</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/400</td> - -<td>Sandpiper</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/500</td> - -<td>Flamingo</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/500X</td> - -<td>Hot Pink</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/600</td> - -<td>Sandpiper+</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/700</td> - -<td>Sandpiper45</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/800</td> - -<td>Flamingo II</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 3000/900</td> - -<td>Flamingo45</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 4000 model 610</td> - -<td>Fang</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 4000 model 710</td> - -<td>Cobra</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 7000 model 610/180</td> - -<td>Laser/Ruby</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 7000 model 610/200</td> - -<td>Laser/Ruby+</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 7000 model 710</td> - -<td>Laser/Ruby45</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DEC 10000</td> - -<td>Blazer/Ruby</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>DECpc 150</td> - -<td>Jensen <i>(Jensen family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 3300</td> - -#Note to translators: Whitebox means that these machines where limited -#to run NT instead of Digital Unix (though they still could be made to -#run Linux :-)) ) -<td>Whiteboxed <a href="#as800">Alpha Server 800</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 3300R</td> - -<td>Rackmount whiteboxed <a href="#as800">Alpha Server 800</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 3305</td> - -<td>Whiteboxed <a href="#as800">Alpha Server 800</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 3305R</td> - -<td>Rackmount whiteboxed <a href="#as800">Alpha Server 800</a></td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 5300</td> - -<td>Whiteboxed <a href="#as1200">Alpha Server 1200</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 5305</td> - -<td>Whiteboxed <a href="#as1200">Alpha Server 1200</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 7300</td> - -<td>Whiteboxed <a href="#as4100">Alpha Server 4100</a></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 7305</td> - -<td>Whiteboxed <a href="#as4100">Alpha Server 4100</a></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>Digital Server 7310</td> - -<td>Whiteboxed <a href="#as4100">Alpha Server 4100</a></td> -<td>Unknown</td> -<td>No</td> -</tr> - -<tr> -<td>DP264</td> - -<td>DP264 <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>EB64+ (PCI Eval Board)</td> - -<td>EB64+ <i>(EB64+ family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>EB66</td> - -<td>EB66 <i>(EB66 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>EB66+</td> - -<td>EB66+ <i>(EB66 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>EB164</td> - -<td>EB164 <i>(EB164 family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 433a</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 433au</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 500a</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 500au</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 600a</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>Personal WorkStation 600au</td> - -<td>Miata <i>(Miata family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>RPL164-2</td> - -<td>Ruffian <i>(DeskStation produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>RPL164-4</td> - -<td>Ruffian <i>(DeskStation produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>RPX164-2</td> - -<td>Ruffian <i>(DeskStation produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>RPX164-4</td> - -<td>Ruffian <i>(DeskStation produced)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>SMARTengine 21264 PCI/ISA SBC</td> - -<td>Eiger <i>(Tsunami family, but with 1 p-chip)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>UDB/Multia</td> - -<td>UDB/Multia <i>(Noname family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>UP1000</td> - -<td>Nautilus <i>(Nautilus family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>UP1100</td> - -<td>Galaxy-Train/Nautilus Jr. <i>(Nautilus family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>UP2000</td> - -<td>Swordfish <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>XP900</td> - -<td>Webbrick <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>XP1000</td> - -<td>Monet/Brisbane <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaVME 4/xxx (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part)</td> - -<td>Cortex</td> -<td>No</td> -<td>No</td> -</tr> - -#Most likely never produced: -<tr> -<td>Unknown</td> - -<td>Cusco</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AXPvme xxx (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part)</td> - -<td>Medulla</td> -<td>Unknown</td> -<td>No</td> -</tr> - -#Was cancelled: -<tr> -<td>Unknown</td> - -<td>Tradewind</td> -<td>No</td> -<td>No</td> -</tr> - -#Never produced: -<tr> -<td>Unknown</td> - -<td>Warhol <i>(Tsunami family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -#Never produced: -<tr> -<td>Unknown</td> - -<td>Windjammer <i>(Tsunami family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -#Never produced: -<tr> -<td>Unknown</td> - -<td>PC264 <i>(Tsunami family)</i></td> -<td>Unknown</td> -<td>No</td> -</tr> - -#Ever produced? -<tr> -<td>Unknown</td> - -<td>XXM</td> -<td>No</td> -<td>No</td> -</tr> - -<tr> -<td>AlphaVME 5/xxx (<abbr lang="en" title="original equipment manufacturer">OEM</abbr> part)</td> - -<td>Yukon <i>(Titan family)</i></td> -<td>Yes</td> -<td>No</td> -</tr> - -</table> - diff --git a/greek/ports/amd64/Makefile b/greek/ports/amd64/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/amd64/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/amd64/index.wml b/greek/ports/amd64/index.wml deleted file mode 100644 index 9800c83094d..00000000000 --- a/greek/ports/amd64/index.wml +++ /dev/null @@ -1,78 +0,0 @@ -#use wml::debian::template title="AMD64 Port" -#use wml::debian::translation-check translation="3d9c842c8a62070d2b0db0fed7812af4619c7b91" maintainer="galaxico" - - -#use wml::debian::toc - -<toc-display/> - -<toc-add-entry name="about">Debian on AMD64</toc-add-entry> -<p>This page is meant to assist users and Debian developers running -Debian GNU/Linux on the AMD64 architecture. Here, you will find -information about the current status of the port, which machines are -publicly accessible by developers, where to discuss development of -the port, where to get further information about Debian porters, and -pointers to more information.</p> - -<toc-add-entry name="status">Current Status</toc-add-entry> -<p>AMD64 has been an officially supported Debian architecture since the -release of Debian 4.0 (etch).</p> - -<p>The port consists of a kernel for all AMD 64bit CPUs with <em>AMD64</em> -extension and all Intel CPUs with <em>Intel 64</em> extension, and a common -64bit userspace.</p> - -<toc-add-entry name="features">A complete 64bit userland</toc-add-entry> -<p>The AMD64 port is thoroughly 64bit, allowing the user to benefit from all -advantages this architecture has compared to i386: -</p> -<ul> -<li>no memory segmentation into low and high memory</li> -<li>up to 128TiB virtual address space per process (instead of 2GiB)</li> -<li>64TiB physical memory support instead of 4GiB (or 64GiB with the PAE -extension)</li> -<li>16 general purpose registers in the CPU instead of 8</li> -<li>gcc defaults to SSE2 math instead of 387 FPU</li> -<li>gcc omits frame-pointers by default at -O2</li> -<li>compilation time optimization uses a common base for AMD64/Intel 64 instead of legacy i386 cruft</li> -<li>memory pages are not executable by default</li> -</ul> - -<p>Native execution of legacy 32bit binaries is supported by the kernel, and -core libraries needed are provided via Debian's <a -href="https://wiki.debian.org/Multiarch">Multiarch mechanism</a>.</p> - - -<toc-add-entry name="i386support">Minimalistic AMD64 runtime support for i386</toc-add-entry> -<p>The official i386 distribution actually includes minimalistic AMD64 -support, consisting of a 64bit kernel, a toolchain able to create 64bit binaries -and the amd64-libs package to run third-party amd64 binaries with native shared -libraries.</p> - - -<toc-add-entry name="ml">Mailing List</toc-add-entry> - -<p>Discussions and development for this port take place on the <a -href="https://lists.debian.org/debian-amd64/">debian-amd64</a> -list.</p> - - -<toc-add-entry name="publicmachines">Public machines</toc-add-entry> - -<p> -All Debian members can port packages using the Debian -<a href="https://db.debian.org/machines.cgi">porterbox machines</a>. -</p> - -<toc-add-entry name="links">Links</toc-add-entry> - -<ul> -#<li><a href="https://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html">The debian-amd64 howto and FAQ</a></li> - -#<li><a href='https://anonscm.debian.org/viewvc/debian-amd64/'>CVS Repository</a></li> - -#<li><a href="https://alioth.debian.org/projects/debian-amd64/">the debian-amd64 Alioth project</a></li> - -<li><a href="https://wiki.debian.org/DebianAMD64">the debian-amd64 Wiki</a></li> -</ul> - diff --git a/greek/ports/arm/Makefile b/greek/ports/arm/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/arm/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/arm/index.wml b/greek/ports/arm/index.wml deleted file mode 100644 index bd370605c1b..00000000000 --- a/greek/ports/arm/index.wml +++ /dev/null @@ -1,127 +0,0 @@ -#use wml::debian::template title="ARM Ports" -#include "$(ENGLISHDIR)/releases/info" -#use wml::debian::toc -#use wml::debian::translation-check translation="51585e94038fbe80235329bd777a3ef8e5016e69" maintainer="galaxico" - -<toc-display/> - -<toc-add-entry name="about">Debian on arm</toc-add-entry> <p>On these -pages you'll find information about the ongoing effort of porting -Debian GNU/Linux to various versions of the <a -href="https://en.wikipedia.org/wiki/ARM_architecture">ARM -architecture</a> which are found in all types of system, from embedded -through to large server.</p> - -<toc-add-entry name="status">Current Status</toc-add-entry> -<p>Debian fully supports three ports to different flavours of -little-endian ARM hardware:</p> - -<ul> - -<li>The <a href="https://wiki.debian.org/ArmEabiPort">ARM EABI</a> -(armel) port targets a range of older 32-bit ARM devices, particularly -those used in NAS hardware and a variety of *plug computers.</li> - -<li>The newer <a href="https://wiki.debian.org/ArmHardFloatPort">ARM -hard-float</a> (armhf) port supports newer, more powerful 32-bit -devices using version 7 of the ARM architecture specification.</li> - -<li>The <a href="https://wiki.debian.org/Arm64Port">64-bit ARM</a> -(arm64) port supports the latest 64-bit ARM-powered devices.</li> - -</ul> - -<p>Other ports to ARM hardware exist / have existed in and around -Debian - see <a href="https://wiki.debian.org/ArmPorts">the wiki</a> -for more links and an overview.</p> - -<p>For a full and up-to-date list of the different hardware supported -by each of the ports, check the respective wiki pages. New ARM devices -are released every week, and it's easier for people to keep -information updated there.</p> - -<toc-add-entry name="availablehw">Available Hardware for Debian Developers</toc-add-entry> -<p>Multiple machines are made available to Debian developers for ARM -porting work: abel.debian.org (armel/armhf), asachi.debian.org -(armhf/arm64) and harris.debian.org (armhf). The machines have -development chroot environments which you can access with -<em>schroot</em>. Please see the <a -href="https://db.debian.org/machines.cgi">machine database</a> for -more information about these machines.</p> - -<toc-add-entry name="contacts">Contacts</toc-add-entry> -<h3>Mailing lists</h3> - -<p>The Debian ARM port mailing list is located at -<email "debian-arm@lists.debian.org">. -If you wish to sign up, send a message with the word <q>subscribe</q> as the -subject to <email "debian-arm-request@lists.debian.org">. The list is -archived at the <a href="https://lists.debian.org/debian-arm/">debian-arm -list archives</a>.</p> - -<p> -It's also a good idea to sign up with the -<a href="http://www.arm.linux.org.uk/mailinglists/">\ -linux-arm</a> mailing list.</p> - -<h3>IRC</h3> - -<p>You can find us on IRC on <em>irc.debian.org</em> on the channel -<em>#debian-arm</em>.</p> - -<toc-add-entry name="people">People</toc-add-entry> -<p> -This is a list of significant people who are currently involved in the Debian -ARM ports. -</p> - -<ul> - -<li>Ian Campbell <email "ijc@debian.org"> -<br /> -debian-installer, kernel -</li> - -<li>Aurelien Jarno <email "aurel32@debian.org"> -<br /> -ARM buildd maintainer and general porter -</li> - -<li>Steve McIntyre <email "steve@einval.com"> -<br /> -Local admin for ARM machines, documentation and general porter -</li> - -<li>Martin Michlmayr <email "tbm@cyrius.com"> -<br /> -Documentation, debian-installer -</li> - -<li>Riku Voipio <email "riku.voipio@iki.fi"> -<br /> -armel porter and buildd maintainer -</li> - -<li>Wookey <email "wookey@wookware.org"> -<br /> -Documentation -</li> - -</ul> - -<toc-add-entry name="dedication">Dedication</toc-add-entry> - -<p>Chris Rutter -who was the Project Coordinator and Autobuilder Coordinator for Debian ARM -port got killed in a car accident. We dedicate the ARM port's -release in the Debian GNU/Linux <q>woody</q> distribution to his -memory.</p> - -<toc-add-entry name="thanks">Thanks</toc-add-entry> - -<p> -These people were helpful in making the ARM port viable for Debian: - -Jim Studt, Jim Pick, Scott Bambrough, Peter Naulls, Tor Slettnes, -Phil Blundell, Vincent Sanders -</p> diff --git a/greek/ports/hppa/Makefile b/greek/ports/hppa/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/hppa/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/hppa/index.wml b/greek/ports/hppa/index.wml deleted file mode 100644 index 66d3e331b86..00000000000 --- a/greek/ports/hppa/index.wml +++ /dev/null @@ -1,48 +0,0 @@ -#use wml::debian::template title="PA-RISC Port" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hppa/menu.inc" -#use wml::debian::translation-check translation="1f99c642fe56e0113f0730c6247f562992a7e25f" maintainer="galaxico" - -<h1>Debian for PA-RISC</h1> - -<h2>Status</h2> -HPPA became an officially supported Debian architecture in release -3.0 (woody), and was dropped as of stable release 6.0 (squeeze). -Additional information about the port may be found at -<a href="https://parisc.wiki.kernel.org/">https://parisc.wiki.kernel.org/</a>. - -<p> -If you have questions, or would like to help, start by subscribing to the -debian-hppa mailing list, documented below! - -<h2>Contacts</h2> - -The principal instigator of this port was Bdale Garbee, but he no longer -actively contributes to it. -The best way to ask questions now is via the mailing list. - -<h2>Mailing List</h2> - -<p> -To subscribe to the mailing list for this port, send a message with the -word "subscribe" as the subject to -<a -href="mailto:debian-hppa-request@lists.debian.org">\ -debian-hppa-request@lists.debian.org</a> to sign up, or use the -<a href="$(HOME)/MailingLists/subscribe">mailing list subscription</a> page. -<p> -The list is archived at the -<a href="https://lists.debian.org/debian-hppa/">list archives</a>. - -<h2>Links</h2> - -<ul> - -<li><a href="https://parisc.wiki.kernel.org/">The PA-RISC Linux Project Web</a> -<li><a href="https://www.pateam.org/doc.html">ESIEE's HOWTO Documents</a> -<li><a href="http://docs.hp.com/hpux/hw/">HP Systems Documentation</a> -<li><a href="http://h21007.www2.hp.com/dev/">\ - HP PA-RISC Architecture Reference Documents, Etc</a> -<li><a href="https://www.openpa.net/">The OpenPA Project</a> - -</ul> - diff --git a/greek/ports/hppa/news.wml b/greek/ports/hppa/news.wml deleted file mode 100644 index 8abb4906f33..00000000000 --- a/greek/ports/hppa/news.wml +++ /dev/null @@ -1,77 +0,0 @@ -#use wml::debian::template title="PA-RISC Port -- News" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hppa/menu.inc" -#use wml::debian::translation-check translation="1f99c642fe56e0113f0730c6247f562992a7e25f" maintainer="galaxico" - -<h1>News about Debian for PA-RISC</h1> - -<h3><:=spokendate ("2001-08-06"):></h3> - -<p><strong>Debian accepts hppa for release with Debian 3.0 (woody)!</strong> - -<p> -It is with great pleasure that we announce the acceptance of hppa as an -architecture for the upcoming Debian 3.0 stable release, codename woody. -Installation tools for hppa are now in the woody tree, and packages now in -unstable are beginning to be promoted to the testing/woody tree. - -<h3><:=spokendate ("2001-07-17"):></h3> - -<p><strong>Official Request to Release with Debian 3.0 (woody)</strong> - -<p> -Nearly 70% of all Debian packages are built and up to date in the archive, -an automated build system is running smoothly, installation tools are -available in the archive, and the number of running systems is growing -steadily. - -<h3><:=spokendate ("2001-05-31"):></h3> - -<p><strong>HP Releases 0.9 CD Images!</strong> - -<p> -HP has made a snapshot of the "sid" unstable Debian tree for hppa available -as a set of CDROM images. See <a href="http://www.parisc-linux.org/release-0.9/"> -the release page </a> for more information. This release makes it plausible -that the hppa architecture might be ready to release with woody, though there -is much work left to do between now and then! - -<h3><:=spokendate ("2000-10-16"):></h3> - -<p><strong>Binary Trees Created</strong> - -<p> -Binary trees for the hppa architecture were added to the 'sid' distribution -on Debian's master site today. Bdale is running an auto-builder, and packages -should start showing up on Debian mirror sites shortly. Installation info and -some critical packages are still available only through the -<a href="https://parisc.wiki.kernel.org/">PA-RISC Linux</a> -web site, however. - -<h3><:=spokendate ("2000-08-01"):></h3> - -<p><strong>Name Change</strong> - -<p> -At OLS, the issue of using 'parisc' vs 'hppa' for the Debian architecture -string was finally decided, in favor of 'hppa'. This ports page is being -moved to reflect the change, and a request is in the works to rename the -debian-parisc mailing list to debian-hppa. - -<h3><:=spokendate ("2000-03-31"):></h3> - -<p><strong>HP Contributes Build Machine</strong> - -<p> -HP has made a -J5000 -available to Debian on long-term loan to aid in compiling packages when we get -to that point. -<p> -Also, the mailing list debian-parisc has been activated. - -<h3><:=spokendate ("2000-03-04"):></h3> - -<p><strong>Debian PA-RISC Port Officially Starts</strong> - -<p> -A new mailing list, debian-parisc, has been requested but is not active yet. diff --git a/greek/ports/hppa/systems.wml b/greek/ports/hppa/systems.wml deleted file mode 100644 index 1cb12caf10f..00000000000 --- a/greek/ports/hppa/systems.wml +++ /dev/null @@ -1,12 +0,0 @@ -#use wml::debian::template title="PA-RISC Port -- Systems" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hppa/menu.inc" -#use wml::debian::translation-check translation="2fc9dfddd8c0dbff8db3c43eebd31df1cdfab7d1" maintainer="galaxico" - -<h2>Systems Overview</h2> - -<h3>HP9000 715/50 (Scorpio)</h3> - -<p>Linux will work quite well on that machine, but you may have to run -with a serial console, as Linux doesn't support graphics on all -hardware yet. Also, Linux doesn't support EISA cards on any PA-RISC -boxes yet, so if you have any of those they won't work. diff --git a/greek/ports/hurd/hurd-cd.wml b/greek/ports/hurd/hurd-cd.wml deleted file mode 100644 index 1ebb53fe81b..00000000000 --- a/greek/ports/hurd/hurd-cd.wml +++ /dev/null @@ -1,100 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Hurd-CDs" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="f1e7499d83a6ebf7321674af80d60a51cf5db6fd" maintainer="galaxico" - -<define-tag cdserie>L1</define-tag> -<define-tag cdbasetarball>gnu-2009-10-18.tar.gz</define-tag> -<define-tag cdbasename>debian-<cdserie>-hurd-i386</define-tag> - -<h1>Debian GNU/Hurd</h1> - -<p>While many people call the GNU system GNU/Hurd this is not strictly true. -The kernel is GNU Mach not the Hurd. The Hurd is a series of servers which -run on top of the microkernel, GNU Mach. Both the Hurd and GNU Mach are -part of the GNU project while the Linux kernel is an independent project.</p> - -<p>The easiest (and well-tested) method of trying Debian GNU/Hurd is to use a -virtual machine via KVM. Some pre-installed images are available on -<url "https://cdimage.debian.org/cdimage/ports/stable/hurd-i386/README.txt">, but one can also -use the Debian Installer to install in KVM or a native machine (but hardware -support vary, so it is more recommended to give a try with KVM). -</p> - -<h2>Using the Debian Installer installation CD-ROM</h2> - -<p>A hurd-i386 port of the standard Debian Installer can be -downloaded from <url "https://cdimage.debian.org/cdimage/ports/stable/hurd-i386/"> . -Make sure to read the README file available along the iso images. -It works like the usual Linux port of the Debian Installer, i.e. automatically, except a -few details:</p> - -<ul> - -<li>Make sure to enable swap space, else Mach will have troubles if you use all -your memory.</li> - -<li>Do not mount a separate partition on <code>/usr</code>, else the boot will -fail.</li> - -<li> -Read <a href="hurd-install">the notes about manual installation</a> which -document some of the final configuration steps. -</li> - -</ul> - -<p>Instructions for burning CDs from the images can be found in the -<a href="$(HOME)/CD/faq/">Debian CD FAQ</a>.</p> - -<h2>Newer snapshots</h2> - -<p>Some newer snapshots are available on <url "https://cdimage.debian.org/cdimage/ports/latest/hurd-i386/"></p> - -<p>Daily (untested!) snapshots are available on <url "https://people.debian.org/~sthibault/hurd-i386/installer/cdimage/">. Since they are based on the unstable distribution, quite often they cannot actually install a system, due to ongoing transitions in unstable etc. So really rather use the snapshot linked above.</p> - -<h2>Making a GRUB boot-disk</h2> - -<p> -If you are installing the Hurd alone on your system, you can let the installer -install GRUB itself. If you are installing the Hurd along an existing system, -you will most probably want to be able to choose between both. If your existing -system is Linux, you can probably simply run update-grub and it will detect your -newly-installed Hurd system. Otherwise, or if you do not manage to boot the Hurd -that way, you can use a GRUB boot-disk.</p> - -<p> -Install the package grub-disk or grub-rescue-pc, they contain a GRUB floppy -image. You can use "dd" if you are working in GNU/Linux or rawrite if you are -working in MS. -</p> - -<p> -Make certain that you understand Linux, GRUB and Hurd methods -of naming drives and partitions. You will be using all three and the -relationship between them can be confusing. -</p> - -<p>Hurd uses different partition names to Linux, so be careful. IDE -hard disks are numbered in order, beginning from hd0 for the primary -master and its slave hd1, followed by the secondary master hd2 and -its slave hd3. SCSI drives are also numbered in absolute order. They will -always be sd0, sd1, and so on regardless of whether the two drives are -SCSI id 4 and 5 or whatever. Experience has shown that CD-ROM drives -can be tricky. More about this later.</p> - -<p>Linux-style partitions are always called sn when using the Hurd, -where n is the partition number, so the first partition on the first -IDE drive will be hd0s1, the third partition on the second SCSI drive -will be sd1s3, and so on.</p> - -<p>GRUB1 has yet another partition naming system. It calls partitions (hdN,n), -but this time the disk number and partition number are both zero indexed, and -the disks run in order, all the IDE disks first, and the SCSI ones second. This -time, the first partition on the first IDE drive will be (hd0,0). GRUB2 does -the same, but the partition number is one indexed, so in that case it will be -(hd0,1). To really cause a confusion, (hd1,2) could refer to the first SCSI -drive if you only have one IDE drive, or it could refer to the second IDE drive. -So it is important that you have worked out the various names of your partitions -before you start.</p> - -<p>Enjoy the Hurd.</p> diff --git a/greek/ports/hurd/hurd-devel-debian.wml b/greek/ports/hurd/hurd-devel-debian.wml deleted file mode 100644 index 932f99212db..00000000000 --- a/greek/ports/hurd/hurd-devel-debian.wml +++ /dev/null @@ -1,165 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Development" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="dd86de49807cb957ea73388b4bf2565163644a0c" maintainer="galaxico" - -<h1> -Debian GNU/Hurd</h1> -<h2> -Development of the Distribution</h2> - -<h3> -Porting Debian Packages</h3> -<p> -If you want to help the Debian GNU/Hurd port, you should make yourself -familiar with the Debian packaging system. Once you have done this by -reading the available documentation and visiting the <a -href="$(HOME)/devel/">Developer's Corner</a> you should know how to -extract Debian source packages and build a Debian package. Here is a -crash course for the very lazy people:</p> - -<h3> -Obtaining Source and Building Packages</h3> - -<p> -Obtaining Source code can be done by simply running <code>apt-get source -package</code>, which will also extract the source. -</p> - -<p> -Extracting a Debian source package requires the file -<code>package_version.dsc</code> and the files listed in it. You build the -Debian build directory with the command -<code>dpkg-source -x package_version.dsc</code> -</p> - -<p> -Building a package is done in the now existing Debian build directory -<code>package-version</code> with the command -<code>dpkg-buildpackage -B "-mMyName <MyEmail>"</code>. -Instead <code>-B</code> you can use -<code>-b</code> if you also want to build the architecture independent -parts of the package. You can add -<code>-uc</code> to avoid signing the package with your pgp key.</p> - -<p> -Building may needed additional installed packages. The simplest way it to run -<code>apt-get build-dep package</code> which will install all required packages. -</p> - -<p> -Using pbuilder can be convenient. It can be built with -<code>sudo pbuilder create --mirror http://deb.debian.org/debian-ports/ --debootstrapopts --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg --debootstrapopts --extra-suites=unreleased --extrapackages debian-ports-archive-keyring</code> -and then one can use <code>pdebuild -- --binary-arch</code> which will handle downloading build dependencies, etc, and put the result in <code>/var/cache/pbuilder/result</code> -</p> - -<h3> -Pick One</h3> -<p> -Which package needs to be worked on? Well, every package that is not -yet ported, but needs to be ported. This changes constantly, so -it's preferred to concentrate first on packages with a lot of reverse -dependencies, which can be seen in the package dependency graph -<url "https://people.debian.org/~sthibault/graph-radial.pdf"> updated every day, -or on the most-wanted list -<url "https://people.debian.org/~sthibault/graph-total-top.txt"> (this is -long-term wanted, the short-term wanted is -<url "https://people.debian.org/~sthibault/graph-top.txt">). -It is also usually a good idea to pick from the out of date lists -<url "https://people.debian.org/~sthibault/out_of_date2.txt"> and -<url "https://people.debian.org/~sthibault/out_of_date.txt">, as these used to be -working, and are now broken probably only for just a couple of reasons. -You can also just pick one of the missing packages at random, or watch out for -autobuilding logs on the debian-hurd-build-logs mailing list, or use the -wanna-build list from -<url "https://people.debian.org/~sthibault/failed_packages.txt"> . Some build issues are easier to fix than the others. Typically, "undefined reference to foo", where foo is something like pthread_create, dlopen, cos, ... (which are obviously available on hurd-i386), which just shows that the configure step of the package forgot to include -lpthread, -ldl, -lm, etc. on the Hurd too. Note however that ALSA MIDI functions are not available. -</p> -<p> -Also, check whether work has already been done on -<url "https://alioth.debian.org/tracker/?atid=410472&group_id=30628&func=browse">, -<url "https://alioth.debian.org/tracker/?atid=411594&group_id=30628&func=browse">, -and the BTS (<url "https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-hurd@lists.debian.org;tag=hurd">), and <url "https://wiki.debian.org/Debian_GNU/Hurd">, -and the live state of packages on buildd.debian.org, e.g. -<url "https://buildd.debian.org/util-linux">. -</p> - -<h4> -Packages That Won't Be Ported</h4> -<p> -Some of these packages, or parts of them, might be portable later, but -currently they are considered to be unportable at least. They are normally -marked as NotForUs in the buildd database. -</p> - -<ul> -<li> -<code>base/makedev</code>, because the Hurd comes with its own version -of this script. The Debian source package only contains a Linux -specific version.</li> -<li> -<code>base/modconf</code> and <code>base/modutils</code>, because -modules are a concept specific to Linux.</li> -<li> -<code>base/netbase</code>, because the remaining stuff that is there -is highly specific to the Linux kernel. The Hurd uses -<code>inetutils</code> instead.</li> -<li> -<code>base/pcmcia-cs</code>, because this package is Linux specific.</li> -<li> -<code>base/setserial</code>, because it is specific to the Linux -kernel. However, with the port of Linux char drivers to GNU Mach, we -might be able to use it.</li> -</ul> - -<h3> <a name="porting_issues"> -General Porting Issues</a></h3> -<p> -<a href=https://www.gnu.org/software/hurd/hurd/porting/guidelines.html>A list of -common issues</a> is available on the upstream website. The following common -issues are specific to Debian.</p> -<p>Before attempting to fix something, check whether the kfreebsd* port maybe -has some fix already, which just needs to be extended to hurd-i386.</p> - -<ul> -<li> -<code>Broken libc6 dependency</code> -<p> -Some packages use an erroneous dependency on <code>libc6-dev</code>. This -is incorrect because <code>libc6</code> is specific to some architectures -of GNU/Linux. The corresponding package for GNU is <code>libc0.3-dev</code> -but other OSes will have different ones. You can locate the problem in the -<code>debian/control</code> file of the source tree. Typical solutions include -detecting the OS using <code>dpkg-architecture</code> and hardcoding the -soname, or better, use a logical OR. eg: -<code>libc6-dev | libc6.1-dev | libc0.3-dev | libc0.1-dev | libc-dev</code>. -The <code>libc-dev</code> is a -virtual package that works for any soname but you have to put it only as the -last option.</p></li> -<li> -<code>undefined reference to snd_*, SND_* undeclared</code> -<p> -Some packages use ALSA even on non-Linux architectures. The oss-libsalsa package -provides some emulation over OSS, but it is limited to 1.0.5, and some features -are not provided, such as all sequencer operations. -</p> -<p> -If the package permits it, alsa support should be disabled on the -<code>!linux-any</code> archs (e.g. through a <code>configure</code> -option), and a <code>[linux-any]</code> qualifier added to the -alsa <code>Build-Depends</code>, and the converse added to -<code>Build-Conflicts</code>, such as -<code>Build-Conflicts: libasound2-dev [!linux-any]</code>. -</p> -</li> -<li> -<code>dh_install: Cannot find (any matches for) "foo" (tried in ., debian/tmp)</code> -<p> -That typically happens when upstream didn't install something because it didn't -recognize the OS. Sometimes it's just dumb (e.g. it doesn't know that building -a shared library on GNU/Hurd is exactly like on GNU/Linux) and that needs -fixing. Sometimes it actually makes sense (e.g. not installing systemd service -files). In that case, one can use dh-exec: build depend on <tt>dh-exec</tt>, -<tt>chmod +x</tt> the <tt>.install</tt> file, and prepend the problematic lines -with e.g. <tt>[linux-any]</tt> or <tt>[!hurd-any]</tt>. -</p> -</li> -</ul> diff --git a/greek/ports/hurd/hurd-doc-server.wml b/greek/ports/hurd/hurd-doc-server.wml deleted file mode 100644 index 4dd790aef9d..00000000000 --- a/greek/ports/hurd/hurd-doc-server.wml +++ /dev/null @@ -1,967 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Τεκμηρίωση" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="f4f6753d2f1e1d5bb9708ce8b3f7dde77940b870" maintainer="galaxico" - -<h1>Debian GNU/Hurd</h1> - -<p> Ο Dirk Ritter μου έστειλε το παρακάτω κείμενο, που περιέχει την έξοδο της -επιλογής <tt>--help</tt> για κάθε πρόγραμμα εξυπηρετητή Hurd. Αυτό μπορεί να -είναι ένα καλό σημείο αφετηρίας για περαιτέρω τεκμηρίωση των προγραμμάτων των -εξυπηρετητών, ιδιαίτερα εκείνων που είναι χρήσιμοι σε έναν χρήστη όπως οι -ext2fs, ufs, isofs, ftpfs, crash, κλπ. -</p> - -<p> -Since then, I updated the text using mail excerpts from the Hurd mailing -lists. Thanks to Martin von Loewis. - -<h2>Προκαταρκτική Περιγραφή της Διεπαφής χρήστη του GNU/Hurd</h2> - -<p> -Currently there is next to nothing but this might be better than nothing at -all, so please send complaints, corrections and additions to -<a href="mailto:dirk@gnumatic.s.bawue.de">Dirk Ritter</a>, -<dirk@gnumatic.s.bawue.de>. Please note that my programming skills are -<em>very</em> limited, so you should not expect me to actually understand -anything related to Operating Systems design and implementations.</p> - -<table border="2" - summary="Index of HURD servers and translators:"> - -<caption><em>Index of HURD servers and translators:</em></caption> - -<tr> - <th><a href="#auth" name="TOC_auth" type="text/html"> - The authentication server</a></th> - <th>"<code>auth</code>"</th> -</tr> -<tr> - <th><a href="#crash" name="TOC_crash" type="text/html"> - The crash server</a></th> - <th>"<code>crash</code>"</th> -</tr> -<tr> - <th><a href="#exec" name="TOC_exec" type="text/html"> - The exec server</a></th> - <th>"<code>exec</code>"</th> -</tr> -<tr> - <th><a href="#ext2fs" name="TOC_ext2fs" type="text/html"> - The ext2fs server</a></th> - <th>"<code>ext2fs</code>"</th> -</tr> -<tr> - <th><a href="#fifo" name="TOC_fifo" type="text/html"> - The fifo translator</a></th> - <th>"<code>fifo</code>"</th> -</tr> -<tr> - <th><a href="#firmlink" name="TOC_firmlink" type="text/html"> - The firmlink translator</a></th> - <th>"<code>firmlink</code>"</th> -</tr> -<tr> - <th><a href="#ftpfs" name="TOC_ftpfs" type="text/html"> - The ftp filesystem translator</a></th> - <th>"<code>ftpfs</code>"</th> -</tr> -<tr> - <th><a href="#fwd" name="TOC_fwd" type="text/html"> - The fwd server</a></th> - <th>"<code>fwd</code>"</th> -</tr> -<tr> - <th><a href="#hostmux" name="TOC_hostmux" type="text/html"> - The hostmux server</a></th> - <th>"<code>hostmux</code>"</th> -</tr> -<tr> - <th><a href="#ifsock" name="TOC_ifsock" type="text/html"> - The ifsock server</a></th> - <th>"<code>ifsock</code>"</th> -</tr> -<tr> - <th><a href="#init" name="TOC_init" type="text/html"> - The init server</a></th> - <th>"<code>init</code>"</th> -</tr> -<tr> - <th><a href="#isofs" name="TOC_isofs" type="text/html"> - The iso filesystem server</a></th> - <th>"<code>isofs</code>"</th> -</tr> -<tr> - <th><a href="#magic" name="TOC_magic" type="text/html"> - The magic server</a></th> - <th>"<code>magic</code>"</th> -</tr> -<tr> - <th><a href="#new-fifo" name="TOC_new-fifo" type="text/html"> - The new-fifo server</a></th> - <th>"<code>new-fifo</code>"</th> -</tr> -<tr> - <th><a href="#nfs" name="TOC_nfs" type="text/html"> - The nfs server</a></th> - <th>"<code>nfs</code>"</th> -</tr> -<tr> - <th><a href="#null" name="TOC_null" type="text/html"> - The null server</a></th> - <th>"<code>null</code>"</th> -</tr> -<tr> - <th><a href="#pfinet" name="TOC_pfinet" type="text/html"> - The pfinet server</a></th> - <th>"<code>pfinet</code>"</th> -</tr> -<tr> - <th><a href="#pflocal" name="TOC_pflocal" type="text/html"> - The pflocal server</a></th> - <th>"<code>pflocal</code>"</th> -</tr> -<tr> - <th><a href="#proc" name="TOC_proc" type="text/html"> - The process server</a></th> - <th>"<code>proc</code>"</th> -</tr> -<tr> - <th><a href="#storeio" name="TOC_storeio" type="text/html"> - The storage translator</a></th> - <th>"<code>storeio</code>"</th> -</tr> -<tr> - <th><a href="#symlink" name="TOC_symlink" type="text/html"> - The symbolic link translator</a></th> - <th>"<code>symlink</code>"</th> -</tr> -<tr> - <th><a href="#term" name="TOC_term" type="text/html"> - The terminal server</a></th> - <th>"<code>term</code>"</th> -</tr> -<tr> - <th><a href="#ufs" name="TOC_ufs" type="text/html"> - The ufs server</a></th> - <th>"<code>ufs</code>"</th> -</tr> -<tr> - <th><a href="#usermux" name="TOC_usermux" type="text/html"> - The usermux server</a></th> - <th>"<code>usermux</code>"</th> -</tr> - -# Uncomment and fill the blanks... -#<tr> -# <th><a href="#" name="TOC_" type="text/html"> -# The server</a></th> -# <th>"<code></code>"</th> -#<tr> -</table> - - -<h2 class="center"><a href="#TOC_auth" name="auth" type="text/html"> -The authentication server - "<code>auth</code>"</a></h2> - -<p> -Passes credentials when two mutually untrusting servers communicate. -In a sense, each auth server establishes a domain of trust. (Martin von -Loewis, 10 Oct 1996)</p> - -<P> -One of its interesting features is that it makes it possible for -processes to impersonate several identities at the same time, and -also to dynamically acquire or relinquish identities.</p> - -<p> -Running "<code>/hurd/auth --help</code>" gives: -<br> -<pre> -Usage: auth [OPTION...] - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - -<h2 class="center"><a href="#TOC_crash" name="crash" type="text/html"> -The crash server - "<code>crash</code>"</a></h2> - -<p> -The crash server gets active whenever a task gets a fatal error signal, -for example because it violates memory boundaries (segmentation fault). -The crash server has three modes of operation: suspending the process group -(pgrp) of the offending task, killing it or dumping a core file. -The latter is not yet implemented. Think of the crash -server of an airbag.</p> -<p> -You can set the mode of operation with <code>settrans</code> of course, but -also with <code>fsysopts</code> at runtime. This is true for the system wide -default and usually requires root privileges. A user can select a different -default with the <code>CRASHSERVER</code> environment variable. You set this -variable to an inode that has the <code>crash</code> server attached to it. -On a default Debian GNU/Linux system, there three default operations have -corresponding translators in <code>/servers/crash-*</code>.</p> - -<pre> - - These options specify the disposition of a crashing process: - -s, --suspend Suspend the process - -k, --kill Kill the process - -c, --core-file Dump a core file - --dump-core -</pre> - - -<h2 class="center"><a href="#TOC_exec" name="exec" type="text/html"> -The execute server - "<code>exec</code>"</a></h2> - -<p> -Exec manages the creation of a new process image from the image file.</p> - -<P> -Actually this server has support to create a runnable process image -out of any image file recognized by the BFD library (this includes -a.out, ELF, and many others). Gzipped executable are also -recognized (useful for boot floppies).</p> - -<p> -Running "<code>/hurd/exec --help</code>" gives: -<br> -<pre> -Usage: exec [OPTION...] -Hurd standard exec server - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_ext2fs" name="ext2fs" type="text/html"> -The ext2 filesystem server - "<code>ext2fs</code>"</a></h2> - -<p> -This server manages ext2-type filesystems. It does the same as -<code>ext2fs.static</code>, only that <code>ext2fs.static</code> -is a statically linked executable. - -<p> -Running "<code>/hurd/ext2fs --help</code>" gives: -<br> -<pre> -Usage: ext2fs [OPTION...] DEVICE... - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - - -E, --no-exec Don't permit any execution of files on this - filesystem - -I, --interleave=BLOCKS Interleave in runs of length BLOCKS - -L, --layer Layer multiple devices for redundancy - -n, --no-sync Don't automatically sync data to disk - -r, --readonly Never write to disk or allow opens for writing - -s, --sync[=INTERVAL] If INTERVAL is supplied, sync all data not - actually written to disk every INTERVAL seconds, - otherwise operate in synchronous mode (the default - is to sync every 30 seconds) - -S, --no-suid Don't permit set-uid or set-gid execution - -T, --store-type=TYPE Each DEVICE names a store of type TYPE - -w, --writable Use normal read/write behavior - - Boot options: - --bootflags=FLAGS - -C, --directory=DIRECTORY - --device-master-port=PORT - --exec-server-task=PORT - --host-priv-port=PORT - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_fifo" name="fifo" type="text/html"> -The fifo server - "<code>fifo</code>"</a></h2> - -<p> -The fifo translator implements named pipes. - -<p> -Running "<code>/hurd/fifo --help</code>" gives: -<br> -<pre> -Usage: fifo [OPTION...] -Translator for fifos - - -d, --dgram Reads reflect write record boundaries - -m, --multiple-readers Allow multiple simultaneous readers - -n, --noblock Don't block on open - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_firmlink" name="firmlink" type="text/html"> -The firmlink server - "<code>firmlink</code>"</a></h2> - -<p> -A translator for firmlinks. - -<p> -Running "<code>/hurd/firmlink --help</code>" gives: -<br> -<pre> -Usage: firmlink [OPTION...] TARGET -A translator for firmlinks - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -A firmlink is sort of half-way between a symbolic link and a hard link; - -Like a symbolic link, it is `by name', and contains no actual reference to the -target. However, the lookup returns a node which will redirect parent lookups -so that attempts to find the cwd that go through the link will reflect the link -name, not the target name. The target referenced by the firmlink is looked up -in the namespace of the translator, not the client. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_ftpfs" name="ftpfs" type="text/html"> -The ftp filesystem server - "<code>ftpfs</code>"</a></h2> - -<p> -A server for ftp filesystems. - -<p> -Running "<code>/hurd/ftpfs --help</code>" gives: -<br> -<pre> -Usage: ftpfs [OPTION...] REMOTE_FS [SERVER] -Hurd ftp filesystem translator - - -D, --debug[=FILE] Print debug output to FILE - - Parameters: - --bulk-stat-period=SECS Period for detecting bulk stats (default 10) - --bulk-stat-threshold=SECS Number of stats within the bulk-stat-period - that trigger a bulk stat (default 5) - --name-timeout=SECS Time directory names are cached (default 300) - --node-cache-size=ENTRIES Number of recently used filesystem nodes that - are cached (default 50) - --stat-timeout=SECS Time stat information is cached (default 120) - - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If SERVER is not specified, an attempt is made to extract it from REMOTE_FS, -using `SERVER:FS' notation. SERVER can be a hostname, in which case anonymous -ftp is used, or may include a user and password like `USER:PASSWORD@HOST' (the -`:PASSWORD' part is optional). - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_fwd" name="fwd" type="text/html"> -The fwd server - "<code>fwd</code>"</a></h2> - -<p> -When accessed, the fwd translator forwards requests to another server. -It is used in the fifo and symlink server. The idea is so that you don't get -a jillion servers for such trivial things; fwd is used to coordinate -having one server handle several different nodes conveniently. - -<p> -Running "<code>/hurd/fwd --help</code>" gives: -<br> -<pre> -Usage: /hurd/fwd SERVER [TRANS_NAME [TRANS_ARG...]] -</pre> - - - -<h2 class="center"><a href="#TOC_hostmux" name="hostmux" type="text/html"> -The hostmux server - "<code>hostmux</code>"</a></h2> - -<p> -I have no idea what this server is good for. - -<small> -(A server for host lookups?) -</small> - -<p> -Running "<code>/hurd/hostmux --help</code>" gives: -<br> -<pre> -Usage: hostmux [OPTION...] TRANSLATOR [ARG...] -A translator for invoking host-specific translators - - -H, --host-pattern=PAT The string to replace in the translator - specification with the hostname; if empty, or - doesn't occur, the hostname is appended as - additional argument instead (default `${host}') - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -This translator appears like a directory in which hostnames can be looked up, -and will start TRANSLATOR to service each resulting node. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_ifsock" name="ifsock" type="text/html"> -The ifsock server - "<code>ifsock</code>"</a></h2> - -<p> -<code>ifsock</code> only handles <code>S_IFSOCK</code> filesystem -nodes for filesystems which don't do it themselves, acting as a hook -upon which to hang Unix domain socket addresses. pfinet and pflocal -implement the socket API. (Thomas Bushnell, 10 Oct 1996) - -<p> -Running "<code>/hurd/ifsock --help</code>" gives: -<br> -<pre> -/hurd/ifsock: Must be started as a translator -</pre> - - - -<h2 class="center"><a href="#TOC_init" name="init" type="text/html"> -The initialisation server - "<code>init</code>"</a></h2> - -<p> -A server for system boot procedures and basic runtime configurations. - -<p> -Running "<code>/hurd/init --help</code>" gives: -<br> -<pre> -Usage: init [OPTION...] -Start and maintain hurd core servers and system run state - - -d, --debug - -f, --fake-boot This hurd hasn't been booted on the raw machine - -n, --init-name - -q, --query Ask for the names of servers to start - -s, --single-user Startup system in single-user mode - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_isofs" name="isofs" type="text/html"> -The iso filesystem server - "<code>isofs</code>"</a></h2> - -<p> -A server for iso-type filesystems, commonly used on compact disks. - -<p> -Running "<code>/hurd/isofs --help</code>" gives: -<br> -<pre> -Usage: isofs [OPTION...] DEVICE... - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - - -E, --no-exec Don't permit any execution of files on this - filesystem - -I, --interleave=BLOCKS Interleave in runs of length BLOCKS - -L, --layer Layer multiple devices for redundancy - -n, --no-sync Don't automatically sync data to disk - -r, --readonly Never write to disk or allow opens for writing - -s, --sync[=INTERVAL] If INTERVAL is supplied, sync all data not - actually written to disk every INTERVAL seconds, - otherwise operate in synchronous mode (the default - is to sync every 30 seconds) - -S, --no-suid Don't permit set-uid or set-gid execution - -T, --store-type=TYPE Each DEVICE names a store of type TYPE - -w, --writable Use normal read/write behavior - - Boot options: - --bootflags=FLAGS - -C, --directory=DIRECTORY - --device-master-port=PORT - --exec-server-task=PORT - --host-priv-port=PORT - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_magic" name="magic" type="text/html"> -The magic server - "<code>magic</code>"</a></h2> - -<p> -A translator that returns the magic retry result <code>MAGIC</code>. - -Normal end users probably need not to know much about it since it is used, -for example, to facilitate terminal I/O. Programmers might benefit from the -following pieces of information Thomas Bushnell gave: - -<blockquote> -<p> -The key here is to know what a "magic retry result" is. -The thing to do is to look at the <code>dir_lookup</code> <abbr>RPC</abbr> -documented in <code><hurd/fs.defs></code> and -<code><hurd/hurd_types.defs></code>. - -<br> -Magic lookup results are basically for cases where the lookup needs -information that is part of the calling process's state, and not part -of the normal name lookup procedure. These "punt to caller's state" -things have to each be implemented specially in the C library (see -<code>libc/hurd/hurdlookup.c</code>), and cover the known cases to provide the -functionality that many other systems provide. -</p> -</blockquote> - -<p> -He also kindly explained a particular behavior that usually puzzles normal -end users when they first encounter it: - -<blockquote> -<p> -The inability to "<kbd>ls /dev/fd</kbd>" is because the translator -doesn't know what file descriptors you have open, so it can't tell you which -ones exist. But the behavior of it is exactly as on other systems. -</p> -</blockquote> - -<p> -Running "<code>/hurd/magic --help</code>" gives: -<br> -<pre> -Usage: magic [OPTION...] MAGIC -A translator that returns the magic retry result MAGIC - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_new-fifo" name="new-fifo" type="text/html"> -The new-fifo server - "<code>new-fifo</code>"</a></h2> - -<p> -Alternative server for named pipes. - -<p> -Running "<code>/hurd/new-fifo --help</code>" gives: -<br> -<pre> -Usage: new-fifo [OPTION...] - - -d, --dgram Reflect write record boundaries - -n, --noblock Don't block on open - -r, --multiple-readers Allow multiple simultaneous readers - -s, --server Operate in server mode - -S, --standalone Don't attempt to use a fifo server - -U, --use-server=NAME Attempt use server NAME - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_nfs" name="nfs" type="text/html"> -The network filesystem server - "<code>nfs</code>"</a></h2> - -<p> -Network file system support for Sun's Network File System. - -<p> -Running "<code>/hurd/nfs --help</code>" gives: -<br> -<pre> -Usage: nfs [OPTION...] REMOTE_FS [HOST] -Hurd nfs translator - - -h, --hard Retry file systems requests until they succeed - -s, --soft[=RETRIES] File system requests will eventually fail, after - RETRIES tries if specified, otherwise 3 - -R, --read-size=BYTES, --rsize=BYTES - Max packet size for reads (default 8192) - -W, --write-size=BYTES, --wsize=BYTES - Max packet size for writes (default 8192) - - Timeouts: - --cache-timeout=SEC Timeout for cached file data (default 3) - --init-transmit-timeout=SEC - --max-transmit-timeout=SEC - --name-cache-neg-timeout=SEC - Timeout for negative directory cache entries - (default 3) - --name-cache-timeout=SEC Timeout for positive directory cache entries - (default 3) - --stat-timeout=SEC Timeout for cached stat information (default 3) - - Server specification: - --default-mount-port=PORT Port for mount server, if none can be found - automatically - --default-nfs-port=PORT Port for nfs operations, if none can be found - automatically - --mount-port=PORT Port for mount server - --mount-program=ID[.VERS] - --nfs-port=PORT Port for nfs operations - --nfs-program=ID[.VERS] - --pmap-port=SVC|PORT - - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If HOST is not specified, an attempt is made to extract it from REMOTE_FS, -using either the `HOST:FS' or `FS@HOST' notations. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_null" name="null" type="text/html"> -The kitchen sink - "<code>null</code>"</a></h2> - -<p> -A server for lots of free space and countless numbers of zeroes, implements -<code>/dev/null</code> and <code>/dev/zero</code>. - -<p> -Running "<code>/hurd/null --help</code>" gives: -<br> -<pre> -Usage: null [OPTION...] -Endless sink and null source - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_pfinet" name="pfinet" type="text/html"> -The TCP/IP server - "<code>pfinet</code>"</a></h2> - -<p> -A server for TCP/IP, which implements the (IPv4) PF_INET protocol -family. The server which will implement the IPv6 protocol family would -be called pfinet6 in the current scheme.</p> -<p> -Setting this up isn't hard at all. It always is placed in -<code>/servers/socket/2</code>, because that's where glibc will look for it. -So be sure to install it this way: -<code>settrans /servers/socket/2 /hurd/pfinet -6 /servers/socket/26 --interface=/dev/eth0 OPTIONS</code> and -<code>settrans /servers/socket/26 /hurd/pfinet -4 /servers/socket/2 --interface=/dev/eth0 OPTIONS</code>, -where <code>OPTIONS</code> -specify your IP address, netmask and the gateway (if any). Only one -network interface is supported currently. Later, you can also set further -interfaces like <code>eth1</code> and so on with the same command.</p> -<p> -If you don't have a network card you should at least install the loopback -interface, so localhost works (important for print spooling and other useful -stuff). Do this with the above command, but don't specify any interface or -<code>OPTIONS</code>. A simple <code>settrans /servers/socket/1 -/hurd/pfinet</code> will do it.</p> -<p> -Running "<code>/hurd/pfinet --help</code>" gives: -<br> -<pre> -Swansea University Computer Society TCP/IP for NET3.019 -IP Protocols: ICMP, UDP, TCP -Usage: pfinet [OPTION...] -Interface-specific options before the first interface specification apply to -the first following interface; otherwise they apply to the previously specified -interface. - - -i, --interface=DEVICE Network interface to use - - These apply to a given interface: - -a, --address=ADDRESS Set the network address - -g, --gateway=ADDRESS Set the default gateway - -m, --netmask=MASK Set the netmask - -s, --shutdown Shut it down - - -?, --help Give this help list - --usage Give a short usage message - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_pflocal" name="pflocal" type="text/html"> -The pflocal server - "<code>pflocal</code>"</a></h2> - -<p> -Implements UNIX domain sockets. Needed for pipes, for example. - -<p> -Running "<code>/hurd/pflocal --help</code>" gives: -<br> -<pre> -Usage: /hurd/pflocal -</pre> - -<h2 class="center"><a href="#TOC_proc" name="proc" type="text/html"> -The process server - "<code>proc</code>"</a></h2> - -<p> -The proc server assigns PID's and process structures to tasks, and manages -all the process level stuff like wait, bits of fork, C library support. - -<p> -Running "<code>/hurd/proc --help</code>" gives: -<br> -<pre> -Usage: proc [OPTION...] -Hurd process server - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_storeio" name="storeio" type="text/html"> -The storage translator - "<code>storeio</code>"</a></h2> - -<p> -A translator for devices and other stores. - -<p> -Running "<code>/hurd/storeio --help</code>" gives: -<br> -<pre> -Usage: storeio [OPTION...] DEVICE... -Translator for devices and other stores - - -I, --interleave=BLOCKS Interleave in runs of length BLOCKS - -L, --layer Layer multiple devices for redundancy - -n, --rdev=ID The stat rdev number for this node; may be either - a single integer, or of the form MAJOR,MINOR - -r, --readonly Disallow writing - -T, --store-type=TYPE Each DEVICE names a store of type TYPE - -w, --writable Allow writing - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_symlink" name="symlink" type="text/html"> -The symbolic link server - "<code>symlink</code>"</a></h2> - -<p> -A server for symbolic links for filesystems which don't support it -themselves. - -<p> -Running "<code>/hurd/symlink --help</code>" gives: -<br> -<pre> -? -</pre> -(There has not been any output? Strange...) - - -<h2 class="center"><a href="#TOC_term" name="term" type="text/html"> -The terminal server - "<code>term</code>"</a></h2> - -<p> -Implements a POSIX terminal. - -<p> -Running "<code>/hurd/term --help</code>" gives: -<br> -<pre> -Usage: term ttyname type arg -</pre> - - - -<h2 class="center"><a href="#TOC_ufs" name="ufs" type="text/html"> -The ufs server - "<code>ufs</code>"</a></h2> - -<p> -A server for ufs-type filesystems. It does the same as -<code>ufs.static</code>, only that <code>ufs.static</code> -is a statically linked executable. - -<p> -Running "<code>/hurd/ufs --help</code>" gives: -<br> -<pre> -Usage: ufs [OPTION...] DEVICE... - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - - -C, --compat=FMT FMT may be GNU, 4.4, or 4.2, and determines which - filesystem extensions are written onto the disk - (default is GNU) - -E, --no-exec Don't permit any execution of files on this - filesystem - -I, --interleave=BLOCKS Interleave in runs of length BLOCKS - -L, --layer Layer multiple devices for redundancy - -n, --no-sync Don't automatically sync data to disk - -r, --readonly Never write to disk or allow opens for writing - -s, --sync[=INTERVAL] If INTERVAL is supplied, sync all data not - actually written to disk every INTERVAL seconds, - otherwise operate in synchronous mode (the default - is to sync every 30 seconds) - -S, --no-suid Don't permit set-uid or set-gid execution - -T, --store-type=TYPE Each DEVICE names a store of type TYPE - -w, --writable Use normal read/write behavior - - Boot options: - --bootflags=FLAGS - --device-master-port=PORT - --directory=DIRECTORY - --exec-server-task=PORT - --host-priv-port=PORT - - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - -Mandatory or optional arguments to long options are also mandatory or optional -for any corresponding short options. - -If neither --interleave or --layer is specified, multiple DEVICEs are -concatenated. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -<h2 class="center"><a href="#TOC_usermux" name="usermux" type="text/html"> -The usermux translator - "<code>usermux</code>"</a></h2> - -<p> -A translator for invoking user-specific translators. - -<p> -Running "<code>/hurd/usermux --help</code>" gives: -<br> -<pre> -Usage: usermux [OPTION...] [TRANSLATOR [ARG...]] -A translator for invoking user-specific translators - - -C, --clear-patterns Reset all patterns to empty; this option may then - be followed by options to set specific patterns - --home-pattern=PAT The string to replace in the translator - specification with the user's home directory - (default `${home}') - --uid-pattern=PAT The string to replace in the translator - specification with the uid (default `${uid}') - --user-pattern=PAT The string to replace in the translator - specification with the user name (default - `${user}') - -?, --help Give this help list - --usage Give a short usage message - -This translator appears like a directory in which user names can be looked up, -and will start TRANSLATOR to service each resulting node. If no pattern occurs -in the translator specification, the users's home directory is appended to it -instead; TRANSLATOR defaults to /hurd/symlink. - -Report bugs to bug-hurd@gnu.org. -</pre> - - - -# Uncomment and fill the blanks... -#<h2 class="center"><a href="#TOC_" name="" type="text/html"> -#The server - "<code></code>"</a></h2> -# -#<p> -#A server for . -# -#<p> -#Running "<code>/hurd/ --help</code>" gives: -#<br> -#<pre> -# -#</pre> diff --git a/greek/ports/hurd/hurd-doc-translator.wml b/greek/ports/hurd/hurd-doc-translator.wml deleted file mode 100644 index 037dade40e6..00000000000 --- a/greek/ports/hurd/hurd-doc-translator.wml +++ /dev/null @@ -1,241 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Documentation" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="55a70d0c0f3df8d4df237334ac6de72daaa99f73" maintainer="galaxico" - -<h1>Debian GNU/Hurd</h1> -<h2>Translators</h2> -<ul> -<li><a href="#concept" name="TOC_concept">Concept</a></li> -<li><a href="#examples" name="TOC_examples">Examples</a></li> -<li><a href="#actpas" name="TOC_actpas">Passive Translators, Active Translators</a></li> -<li><a href="#manage" name="TOC_manage">Managing Translators</a></li> -</ul> - -<h3><a href="#TOC_concept" name="concept">Concept</a></h3> -<p> -Before we take a closer look at translators, let us consider regular -filesystems. A filesystem is a store for a hierarchical tree of directories -and files. You access directories and files by a special character string, -the path. Furthermore, there are symbolic links to refer to one file at -several places in the tree, there are hard links to give one and the same -file several names. There are also special device files for communication -with the hardware device drivers of the kernel, and there are mount points -to include other stores in the directory tree. Then there are obscure -objects like FIFOs.</p> -<p> -Although these objects are very different, they share some common -properties, for example, they have all an owner and a group associated with -them as well as access rights (permissions). This information is written in -inodes. This is actually a further commonality: Every object has exactly -one inode associated with it (hard links are somewhat special as they share -one and the same inode). Sometimes, the inode has further information -stored in it. For example, the inode can contain the target of a symbolic -link.</p> -<p> -However, these commonalities are usually not exploited in the -implementations, despite the common programming interface to them. All -inodes can be accessed through the standard POSIX calls, for example -<code>read()</code> and <code>write()</code>. For example, to add a new -object type (for example a new link type) to a common monolithic unix -kernel, you would need to modify the code for each filesystem -separately.</p> -<p> -In the Hurd, things work differently. Although in the Hurd a special -filesystem server can exploit special properties of standard object types -like links (in the ext2 filesystem with fast links, for example), it has a -general interface to add such features without modifying existing code.</p> -<p> -The trick is to allow a program to be inserted between the actual content of -a file and the user accessing this file. Such a program is called a -translator, because it is able to process the incoming requests in many -different ways. In other words, a translator is a Hurd server which provides -the basic filesystem interface.</p> -<p> -Translators have very interesting properties. From the kernel's point of -view, they are just another user process. This means, translators can be run -by any user. You don't need root privileges to install or modify a -translator, you only need the access rights for the underlying inode the -translator is attached to. Many translators don't require an actual file to -operate, they can provide information by their own means. This is why -the information about translators is stored in the inode.</p> -<p> -Translators are responsible to serve all file system operations that involve -the inode they are attached to. Because they are not restricted to the usual -set of objects (device file, link etc), they are free to return anything -that makes sense to the programmer. One could imagine a translator that -behaves like a directory when accessed by <code>cd</code> or -<code>ls</code> and at the same time behaves like a file when accessed by -<code>cat</code>.</p> - -<h3><a href="#TOC_examples" name="examples">Examples</a></h3> -<h4>Mount Points</h4> -<p> -A mount point can be seen as an inode that has a special translator attached -to it. Its purpose would be to translate filesystem operations on the mount -point in filesystem operations on another store, let's say, another -partition.</p> -<p> -Indeed, this is how filesystems are implemented under the Hurd. A -filesystem is a translator. This translator takes a store as its argument, -and is able to serve all filesystem operations transparently.</p> - -<h4>Device Files</h4> -<p> -There are many different device files, and in systems with a monolithical -kernel, they are all provided by the kernel itself. In the Hurd, all device -files are provided by translators. One translator can provide support for -many similar device files, for example all hard disk partitions. This way, -the number of actual translators needed is quite small. However, note that -for each device file accessed, a separate translator task is started. -Because the Hurd is heavily multi threaded, this is very cheap.</p> -<p> -When hardware is involved, a translator usually starts to communicate with -the kernel to get the data from the hardware. However, if no hardware access -is necessary, the kernel does not need to be involved. For example, -<code>/dev/zero</code> does not require hardware access, and can therefore -be implemented completely in user space.</p> - -<h4>Symbolic Links</h4> -<p> -A symbolic link can be seen as a translator. Accessing the symbolic link -would start up the translator, which would forward the request to the -filesystem that contains the file the link points to.</p> -<p> -However, for better performance, filesystems that have native support -for symbolic links can take advantage of this feature and implement -symbolic links differently. Internally, accessing a symbolic link would not -start a new translator process. However, to the user, it would still look -as if a passive translator is involved (see below for an explanation what a -passive translator is).</p> -<p> -Because the Hurd ships with a symlink translator, any filesystem server that -provides support for translators automatically has support for symlinks (and -firmlinks, and device files etc)! This means, you can get a working -filesystem very fast, and add native support for symlinks and other features -later.</p> - -<h3><a href="#TOC_actpas" name="actpas">Passive Translators, Active Translators</a></h3> -<p> -There are two types of translators, passive and active. They are really -completely different things, so don't mix them up, but they have a close -relation to each other.</p> - -<h4>Active Translators</h4> -<p> -An active translator is a running translator process, as introduced above. -You can set and remove active translators using the -<code>settrans -a</code> -command. The <code>-a</code> option is necessary to tell -<code>settrans</code> that you want to modify the active translator.</p> -<p> -The <code>settrans</code> command takes three kind of arguments. First, you -can set options for the <code>settrans</code> command itself, like -<code>-a</code> to modify the active translator. Then you set the inode you -want to modify. Remember that a translator is always associated with an -inode in the directory hierarchy. You can only modify one inode at a time. -If you do not specify any more arguments, <code>settrans</code> will try to -remove an existing translator. How hard it tries depends on the force -options you specify (if the translator is in use by any process, you will -get "device or resource busy" error message unless you force it to go away).</p> -<p> -But if you specify further arguments, it will be interpreted as a command -line to run the translator. This means, the next argument is the filename of -the translator executable. Further arguments are options to the translator, -and not to the <code>settrans</code> command.</p> -<p> -For example, to mount an ext2fs partition, you can run -<code>settrans -a -c /mnt /hurd/ext2fs /dev/hd2s5</code>. The -<code>-c</code> option will create the mount point for you if it doesn't -exist already. This does not need to be a directory, by the way. To unmount, -you would try <code>settrans -a /mnt</code>.</p> - -<h4>Passive Translators</h4> -<p> -A passive translator is set and modified with the same syntax as the active -translator (just leave away the <code>-a</code>), so everything said above is -true for passive translators, too. However, there is a difference: passive -translators are not yet started.</p> -<p> -This makes sense, because this is what you usually want. You don't want the -partition mounted unless you really access files on this partition. You -don't want to bring up the network unless there is some traffic and so -on.</p> -<p> -Instead, the first time the passive translator is accessed, it is -automatically read out of the inode and an active translator is started on -top of it using the command line that was stored in the inode. This is -similar to the Linux automounter functionality. However, it does not come as -an additional bonus that you have to set up manually, but an integral part of -the system. So, setting passive translators defers starting the translator -task until you really need it. By the way, if the active translator dies for -some reason, the next time the inode is accessed the translator is -restarted.</p> -<p> -There is a further difference: active translators can die or get lost. As -soon as the active translator process is killed (for example, because you -reboot the machine) it is lost forever. Passive translators are not transient -and stay in the inode during reboots until you modify them with the -<code>settrans</code> program or delete the inodes they are attached to. -This means, you don't need to maintain a configuration file with your mount -points.</p> -<p> -One last point: Even if you have set a passive translator, you can still -set a different active translator. Only if the translator is automatically -started because there was no active translator the time the inode was -accessed the passive translator is considered.</p> - -<h3><a href="#TOC_manage" name="manage">Managing Translators</a></h3> -<p> -As mentioned above, you can use -<code>settrans</code> -to set and alter passive and active translators. There are a lot of options -to change the behaviour of <code>settrans</code> in case something goes -wrong, and to conditionalize its action. Here are some common usages:</p> -<ul><li><code>settrans -c /mnt /hurd/ext2fs /dev/hd2s5</code> mounts a -partition, the translator will stay across reboots.</li> -<li><code>settrans -a /mnt /hurd/ext2fs ~/dummy.fs</code> mounts a -filesystem inside a data file, the translator will go away if it dies.</li> -<li><code>settrans -fg /nfs-data</code> forces a translator to go away.</li> -</ul> -<p> -You can use the <a href="hurd-doc-utils#showtrans"><code>showtrans</code></a> -command to see if a translator is attached to an inode. This will only show -you the passive translator though.</p> -<p> -You can change the options of an active (filesystem) translator with -<code>fsysopts</code> without actually restarting it. This is very -convenient. For example, you can do what is called "remounting a -partition read-only" under Linux simply by running <code>fsysopts -/mntpoint --readonly</code>. The running active translator -will change its behaviour according to your request if possible. -<code>fsysopts /mntpoint</code> without a parameter shows you the current -settings.</p> - -<h4>Examples</h4> -<p> -I recommend that you start by reading the <code>/bin/mount</code> command, -it is only a small script. Because setting filesystem translators is -similar to mounting partitions, you can easily grasp the concept this way. -Make a file system image with <code>dd if=/dev/zero of=dummy.fs bs=1024k -count=8; mke2fs dummy.fs</code> and "mount" it with <code>settrans -c dummy -/hurd/ext2fs `pwd`/dummy.fs</code>. Note that the translator is not started -yet, no new <code>ext2fs</code> process is running (verify with <code>ps -Aux</code>). Check that everything is correct using <code>showtrans</code>.</p> -<p> -Now type <code>ls dummy</code> and you will notice the short delay that -occurs while the translator is started. After that, there will be no more -delays accessing dummy. Under Linux, one would say that you automounted a -loop file system. Check with <code>ps Aux</code> that there is an <code>ext2fs -dummy</code> process up and running now. Now put some files into the new -directory. Try to make the filesystem read-only with <code>fsysopts</code>. -Note how further write attempts fail now. Try to kill the active translator -with <code>settrans -g</code>.</p> -<p> -You should have some understanding of what is going on now. Now remember -that this was only <em>one</em> special server, the Hurd ext2fs server. -There are many more server in the <code>hurd</code> directory. Some of them -are for filesystems. Some are needed for file system features like links. -Some are needed for device files. Some are useful for networking. Imagine -"mounting" an FTP Server with <code>settrans</code> and downloading files -simply with the standard <code>cp</code> command. Or editing your web sites -with <code>emacs /ftp/homepage.my.server.org/index.html</code>!</p> diff --git a/greek/ports/hurd/hurd-doc-utils.wml b/greek/ports/hurd/hurd-doc-utils.wml deleted file mode 100644 index 8b1081045b4..00000000000 --- a/greek/ports/hurd/hurd-doc-utils.wml +++ /dev/null @@ -1,123 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd --- Documentation" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="cdc565969852e30580c3ad8ce3e7952261f03573" maintainer="galaxico" - -<h1>Debian GNU/Hurd</h1> - -<table border="2" - summary="Index of GNU/Hurd utilities"> - -<caption><em>Index of GNU/Hurd utilities:</em></caption> - -<tr> - <th><a href="#syncfs" name="TOC_syncfs" type="text/html"> - Sync'ing filesystems</a></th> - <th>"<code>syncfs</code>"</th> -</tr> -<tr> - <th><a href="#showtrans" name="TOC_showtrans" type="text/html"> - Show the passive translator of a FILE</a></th> - <th>"<code>showtrans</code>"</th> -</tr> -<tr> - <th><a href="#devprobe" name="TOC_devprobe" type="text/html"> - Probing for hardware devices</a></th> - <th>"<code>devprobe</code>"</th> -</tr> - -#Uncomment and fill the blanks... -#<tr> -# <th><a href="#" name="TOC_" type="text/html"> -# The server</a></th> -# <th>"<code></code>"</th> -#</tr> -</table> - - -<h2 class="center"><a href="#TOC_syncfs" name="syncfs" type="text/html"> -Sync'ing filesystems - "<code>syncfs</code>"</a></h2> - -<p> -<code>syncfs</code> can be used to flush the write cache for disk -filesystems. - -<p> -Running "<code>/bin/syncfs --help</code>" gives: -<br> -<pre> -Usage: syncfs [FILE...] - Force all pending disk writes to be done immediately - - -s, --synchronous Wait for completion of all disk writes - -c, --no-children Do not synchronize child filesystems - -?, --help Give this help list - --usage Give a short usage message - -V, --version Print program version - - The filesystem containing each FILE is synchronized, and its child - filesystems unless --no-children is specified. With no FILE argument - synchronizes the root filesystem. - -Report bugs to bug-hurd@gnu.org. -</pre> - -<h2 class="center"><a href="#TOC_showtrans" name="showtrans" type="text/html"> -Show the passive translator of a FILE - "<code>showtrans</code>"</a></h2> - -<p> -If you want to know which passive translator is connected to an inode if -any, use <code>settrans</code> to figure it out. - -<p> -Running "<code>/bin/showtrans --help</code>" gives: -<br> -<pre> -Usage: showtrans FILE... - Show the passive translator of FILE... - - -p, --prefix Always display `FILENAME: ' before translators - -P, --no-prefix Never display `FILENAME: ' before translators - -s, --silent No output; useful when checking error status - -t, --translated Only display files that have translators - - A FILE argument of `-' prints the translator on the node - attached to standard input. - -</pre> - -<h2 class="center"><a href="#TOC_devprobe" name="devprobe" type="text/html"> -Probing for devices - "<code>devprobe</code>"</a></h2> - -<p> -The <code>devprobe</code> utility probes for one or multiple Mach devices. -Just specify the names as arguments on the command line: If some of the -devices exists it will echo their names one per line and exits successfully, -otherwise it will return 1. The provided options make it easier to use this -utility in batch mode. - -<p> -Running "<code>/bin/devprobe --help</code>" gives: -<br> -<pre> -Usage: devprobe DEVNAME... - Test for the existence of mach device DEVNAME... - - -s, --silent Don't print devices found - -f, --first Stop after the first device found - - The exit status is 0 if any devices were found. -</pre> - -#Uncomment and fill the blanks... -#<h2 class="center"><a href="#TOC_" name="" type="text/html"> -#The server - "<code></code>"</a></h2> -# -#<p> -#A server for . -# -#<p> -#Running "<code>/hurd/ --help</code>" gives: -#<br> -#<pre> -# -#</pre> diff --git a/greek/ports/hurd/hurd-install.wml b/greek/ports/hurd/hurd-install.wml deleted file mode 100644 index 77bdd2a048f..00000000000 --- a/greek/ports/hurd/hurd-install.wml +++ /dev/null @@ -1,917 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd — Configuration" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="ad90efc904807b8db1f35dd7d05b950182b3c1fa" maintainer="galaxico" - -<h1>Debian GNU/Hurd Configuration</h1> - -<p> -This document aims to provide an easy and relatively painless set of -instructions on how to configure Debian GNU/Hurd with a minimum -amount of effort. -</p> - -<p> -It is based in Neal H. Walfield's <q>The Hurd Installation Guide</q>. -Many thanks to Neal for his contribution. -</p> - -<h2>Overview </h2> - -<p> -GNU is similar in nature to any Unix-like system: after logging in, the user is -presented with a shell and the familiar Unix VFS (virtual filesystem). Although -GNU tries to be POSIX compliant, it is <q>Not Unix</q>. GNU/Hurd builds upon many of -the Unix concepts and extends them to either add new functionality or to fix -what has been perceived as flaws in the original design. The most noticeable -difference is translators, user space programs which interact with the VFS. -These filesystems do not live in the kernel nor do they need to be run -as root; they only need access to the backing store and the -<code>mount point</code>. Another difference is that processes, rather than having a single -user identity fixed at creation time, have identity tokens which are disjoint -from the process, i.e. they may be added with the appropriate permission from -an authority or destroyed. -</p> - -<p> -Being familiar with the Unix environment (and especially GNU userland, found in -popular variants such as GNU/Linux) is an imperative for feeling at ease in -GNU. Having experience with the Debian tools will also prove invaluable to the -configuration and maintenance of a GNU/Hurd box. -</p> - -<p> -This guide endeavors to make installing GNU/Hurd as painless a process as -possible. If there are errors, they are most certainly the author's. Please -report them, along with any other suggestions or criticisms, to him; all are -gladly accepted. -</p> - -#<h2> 2. Real Estate or Finding A Home </h2> -# -#<p> -#If you do not have an available partition or an extra hard drive, this can be -#the longest step. In this case, you will need to repartition the hard drive. -#One solution is to use GNU's partition editor, -#<a href="https://packages.debian.org/parted">Parted</a>. It features not only -#basic partition editing but also partition resizing and moving functionality. -#The manual is quite complete and includes several tutorials. Note that also -#there is a <code>63 GNU HURD or SysV</code> partition type, it should not be -#used or else the installation CD will not find it. Just use <code>83 -#Linux</code> -#</p> -# -#<p> -#The Hurd supports several extensions to the ext2fs filesystem format. Foremost -#among these are passive translators and a fourth set of permission bits for -#unknown users (users without an identity, not the other user). To use these -#extensions, the owner of the partition must be set to <code>hurd</code>. -#<code>mke2fs</code>, unless specifically overridden on the command line, will -#set the owner to whatever kernel it is running on. As the Hurd will diligently -#respect this setting, care must be taken to set this appropriately or the Hurd -#will fail in subtle ways. Be aware that even if a file system is owned by a -#particular kernel, others may still use it; they just may not be able to use -#certain extensions. -#</p> -# -#<p> -#To create a filesystem, use <code>mke2fs</code> and pass it <q><var>-b 4096 -#-I 128 -o hurd</var></q> to designate the Hurd as the owner of the new file -#system. For instance, assuming the partition is <tt><q>/dev/hda1</q></tt>: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# mke2fs -b 4096 -I 128 -o hurd /dev/hda1 -#</pre></td></tr></table> -# -# -#<h2> 3. The Boot Loader </h2> -# -#<p> -#The bootloader of the GNU system is Grub, the GRand Unified Boot loader, -#and it is its main purpose to boot the GNU system core (Mach and the Hurd). -#Any boot loader that supports the multiboot standard, though, may be used to -#load Mach and the Hurd. At the moment (that we're aware of), GNU Grub is the -#only bootloader that supports such standard. -#</p> -# -#<p> -#A word about Grub. Unlike traditional boot loaders on the x86, such as LILO, -#Grub is very powerful. It has a command line interface, bootp, dummy terminal -#support and a plethora of other features. In addition, it can boot almost any -#kernel. If you have ever booted an alpha or sparc, you will understand what -#Grub can do. Therefore, do not be scared: Grub is better. You will like it. -#You will not go back. -#</p> -# -#<p> -#It is probably better if you install -#<a href="https://packages.debian.org/grub2">Grub</a> before installing the -#Hurd, but you can always install it onto your hard drive at a later date. -#</p> -# -# -#<h2> 4. Cross Install </h2> -# -#<p> -#The next step is to get a base system. There are several alternatives, if you -#are running a Debian system you can use the package crosshurd. Otherwise you -#can get an updated base system tarball from any of the mirrors listed at -#<url "https://wiki.debian.org/DebianPorts/Mirrors" />. -#</p> -# -#<p> -#The tarball is set up to extract everything into the current directory. -#After the filesystem is mounted, the archive can be extracted. -#Assuming that the filesystem is on <tt><q>/dev/hda2</q></tt>, the mount point -#is <tt><q>/gnu</q></tt> and archive is in current user's home directory, the -#following is required: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# mount -t ext2 /dev/hda2 /gnu -# \# cd /gnu -# \# tar --same-owner -xvjpf ~/gnu.tar.bz2 -#</pre></td></tr></table> -# -# -#<h2> 5. Booting GNU/Hurd </h2> -# -#<p> -#All is now in readiness to boot GNU/Hurd for the first time. Note that depending -#on your version of GRUB, small details with vary. Please make sure whether you -#have GRUB1 (aka legacy aka 0.95 and later up to 0.97), or GRUB2 (aka 1.95 and -#later). Examples below will provide both versions, make sure to pick the right -#one. -#</p> -# -#<p> -#Please also note that some problems have been reported when booting with only -#128MB memory, because of swap not being setup yet at this stage. Make sure to -#provide at least 256MB memory. -#</p> -# -#<p> -#If your system already has GRUB installed, just reboot it. Else, you need to use -#a Grub boot disk. On Debian, the grub-disk (grub1) or grub-rescue-pc (grub2) -#packages provides CD and Floppy disk images. Make sure that the Grub boot disk -#is in the drive, reboot. If all goes well, either a Grub menu or command line -#will be displayed. If the menu has a <tt><q>GNU/Hurd</q></tt> entry, you will -#probably be able to just reuse it to save a lot of typing burden. For now, if -#presented with a menu, press <kbd>c</kbd> to go to the command line. -#</p> -# -#<p> -#First, GNU Mach needs to be loaded. This requires knowing the filesystem -#and the path to GNU Mach. Grub uses a partition nomenclature that is a bit -#different from both Linux and the Hurd: both IDE and SCSI drives are named -#<tt><q>(hdN,M)</q></tt>. <code>N</code> is the drive number (zero based) as -#enumerated by the BIOS. That is, Grub makes no distinction between IDE and SCSI -#disks. <code>M</code> identifies the partition on the drive. It is zero based -#in grub1 but one based in grub2. If this sounds confusing, relax: Grub is also -#helpful. -#</p> -# -#<p> -#To determine on which filesystem a particular file resides, Grub provides the -#<code>find</code> command. When this command is issued along with a filename, -#Grub searches on each filesystem for the specified file and prints where it was -#found. For example, to search for the kernel, <tt><q>/boot/gnumach.gz</q></tt>: -#</p> -# -#<table> -#<tr><td> </td><td class=example><pre> -# grub1> find /boot/gnumach.gz -# (hd0,0) -#</pre></td></tr> -#<tr><td> </td><td class=example><pre> -# grub2> search -f /boot/gnumach.gz -# (hd0,1) -#</pre></td></tr> -#</table> -# -#<p> -#Here, Grub1 indicates that <tt><q>/boot/gnumach.gz</q></tt> is on -#<tt><q>(hd0,0)</q></tt> and Grub2, on <tt><q>(hd0,1)</q></tt> (remember the difference -#in partition numbering between Grub1 and Grub2). To save you a couple of -#typing, set Grub's root to that value: -#</p> -# -#<table> -#<tr><td> </td><td class=example><pre> -# grub1> root (hd0,0) -#</pre></td></tr> -#<tr><td> </td><td class=example><pre> -# grub2> set root=(hd0,1) -#</pre></td></tr> -#</table> -# -#<p> -#Before loading the kernel, at least one option, the root partition, must be -#specified on the command line. This will be used by the Hurd itself (i.e. not -#Grub). As such, it must be in terms that the Hurd can understand. -#</p> -# -#<p> -#GNU Mach enumerates disks starting at zero. IDE drives are prefixed with -#<code>hd</code>, while SCSI disks are prefixed with <code>sd</code>. Like -#Linux, drives are number by their position on the controller. For instance, the -#primary master is <code>hd0</code> and the secondary slave is <code>hd3</code>. -#Partitions use the BSD slice naming convention and append <code>sM</code> to the -#drive name to indicate a given partition. Note that <code>M</code> is a one, not -#zero, based index. The slice number is simple to calculate: if you have Grub2, -#just reuse the same index, if you have Grub1, just increment what was used for -#Grub1 by one. -#</p> -# -#<p> -#Since the Hurd has not yet been configured, it must be started in single user -#mode. Adding a <q><var>-s</var></q> to the kernel command line is all that is -#required. -#</p> -# -#<p> -#To sum it up, assuming that the first drive (i.e. <tt><q>(hd0)</q></tt>) is the -#master on the master controller, we would have: -#</p> -# -#<table> -#<tr><td> </td><td class=example><pre> -# grub1> kernel /boot/gnumach.gz root=device:hd0s1 -s -# [Multiboot-elf, ...] -#</pre></td></tr> -#<tr><td> </td><td class=example><pre> -# grub2> multiboot /boot/gnumach.gz root=device:hd0s1 -s -#</pre></td></tr> -#</table> -# -#<p> -#Next, the root filesystem server and the <code>exec</code> server must be -#loaded. This is done using Grub's boot module capability. The ${var} are -#filled in by GNU Mach. The arguments are used by the Hurd to indicate what -#type of information is being provided. Since the ext2fs command line is very -#long, it can be broken up by escaping the newline character in the normal Unix -#fashion. Be sure that there is not space after the antislash at the end of each -#line. Also be sure to differentiate <kbd>{</kbd> and <kbd>}</kbd> from <kbd> -#(</kbd> and <kbd>)</kbd>. Mind the subttle differences between Grub1 and -#Grub2: Grub2 needs that the filename be repeated and quotes need -#to be used. Note that at this stage the <var>--readonly</var> option of -#<code>ext2fs.static</code> must not be passed. -#</p> -# -#<table> -#<tr><td> </td><td class=example><pre> -# grub1> module /hurd/ext2fs.static \ -# --multiboot-command-line=${kernel-command-line} \ -# --host-priv-port=${host-port} \ -# --device-master-port=${device-port} \ -# --exec-server-task=${exec-task} -T typed ${root} \ -# $(task-create) $(task-resume) -# [Multiboot-module 0x1c4000, 0x2cfe6a bytes] -# grub1> module /lib/ld.so.1 /hurd/exec $(exec-task=task-create) -# [Multiboot-module 0x494000, 0x27afe bytes] -#</pre></td></tr> -#<tr><td> </td><td class=example><pre> -# grub2> module /hurd/ext2fs.static ext2fs \ -# --multiboot-command-line='${kernel-command-line}' \ -# --host-priv-port='${host-port}' \ -# --device-master-port='${device-port}' \ -# --exec-server-task='${exec-task}' -T typed '${root}' \ -# '$(task-create)' '$(task-resume)' -# grub2> module /lib/ld.so.1 exec /hurd/exec '$(exec-task=task-create)' -#</pre></td></tr> -#</table> -# -#<p> -#Alternatively, you can throw these lines into a <tt><q>menu.lst</q></tt> -#(Grub1) or <tt><q>grub.cfg</q></tt> (Grub2) configuration file in the partition, -#and load it by using <tt><q>configfile /path/to/menu.lst</q></tt> (Grub1) or -#<tt><q>configfile /path/to/grub.cfg</q></tt> (Grub2) from the grub prompt. You -#can of course also simply install grub in some MBR and point it to there. -#</p> -# -#<p> -#GNU/Hurd can be now booted: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -#grub> boot -#</pre></td></tr></table> -# -#<p> -#If GNU/Hurd fails to boot, it could be due to shared IRQs: GNU Mach does not -#play well with these. You can verify your situation by looking at, for -#instance, the <tt><q>/proc/interrupts</q></tt> file under GNU/Linux. Also, as GNU -#Mach does not support loadable kernel modules, many of the drivers are compiled -#into the default kernel. If there are old peripherals, this can be a problem: a -#device may incorrectly respond to a probe intended for a completely unrelated -#device and thereby cause a crash. Building a new kernel with only the required -#device drivers will usually solve this problem. GNU Mach is easily cross -#compiled. If you are running Debian, install the <tt><q>mig</q></tt> package, -#and your stock <tt><q>gcc</q></tt> should do. -#</p> -# -#<p> -#If this does not help, ask on the appropriate mailing list. -#</p> -# -# -#<h2> 6. Native Install </h2> -# -#<p> -#Once you are presented with a shell prompt, and any time that the Hurd is in -#single user mode, it is necessary to set the terminal type: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# export TERM=mach -#</pre></td></tr></table> -# -#<p> -#Be warned that <kbd>CONTROL-C</kbd> and family will not work in single user -#mode. -#</p> -# -#<p> -#We can now run the <code>native-install</code> script. This will configure the -#packages and set up several important translators: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# ./native-install -#</pre></td></tr></table> -# -#<p> -#Before the script terminates, it will indicate that you can now reboot and enter -#multi-user mode. Do so, this is the Hurd, welcome! -#</p> - - -<h2> Installation </h2> - -<p> -You can simply use the Debian installer, see the -<a href="hurd-cd">prepared CD images</a>. -Then the following steps will be needed for proper configuration. -</p> - -<p> -You can also get a pre-installed image and run it in qemu: -</p> - -<table><tr><td> </td><td class=example><pre> -$ wget https://cdimage.debian.org/cdimage/ports/stable/hurd-i386/debian-hurd.img.tar.gz -$ tar xzf debian-hurd.img.tar.gz -$ kvm -m 1G -drive file=$(echo debian-hurd*.img),cache=writeback -</pre></td></tr></table> - -<p> -To enable accessing the box through ssh, you can append -</p> - -<table><tr><td> </td><td class=example><pre> --net nic -net user,hostfwd=tcp:127.0.0.1:2222-:22 -</pre></td></tr></table> - -<p> -and ssh to your local TCP port 2222. -</p> - -<p> -You can also convert the image to the VDI format for virtualbox: -</p> - -<table><tr><td> </td><td class=example><pre> -$ VBoxManage convertfromraw debian-hurd-*.img debian-hurd.vdi --format vdi -</pre></td></tr></table> - -<h2> Configuration </h2> - -<h3> The Network </h3> - -<p> -The Debian way is supported starting from sysvinit 2.88dsf-48 and hurd 1:0.5.git20140320-1: <tt>/etc/network/interfaces</tt> is used like on -Linux. The only difference is that network boards appear in <tt>/dev</tt>, and -interfaces should thus be specified as <tt>/dev/eth0</tt> etc. -</p> - -#<p> -#First, make sure that your network card is recognized by GNU Mach: -#</p> -# -#<table><tr><td> </td><td class=example><pre> -# \# devprobe eth0 -# eth0 -#</pre></td></tr></table> -# -#<p> -#If <code>devprobe eth0</code> does not return <code>eth0</code>, the kernel -#didn't detect your network board and you need to try another board. For -#instance, qemu's e1000 board is not supported, the rtl8139 one should work: -#<code>-net nic,model=rtl8139 -net user</code> -#</p> - -#<p> -#Starting from version 20120520-1, the hurd package includes DDE drivers which -#are used to support more recent devices (drivers are taken from Linux -#2.6.32). Translators for that are already set up for you, and all you -#need to do is to replace <code>eth0</code> (the mach driver name) with -#<code>/dev/eth0</code> (the DDE driver path) in the remainder of this document. -#</p> -# -#<p> -#It is possible to try to use the DDE driver even if GNU Mach has a driver: -#passing <code>nonetdev</code> on the gnumach command line will disable the GNU -#Mach driver, and the DDE driver will start working. -#</p> - -<p> -If network does not seem to work, use the following to get debugging information -from the DDE driver: -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans -fga /dev/netdde /hurd/netdde -</pre></td></tr></table> - -<p> -and then kill any devnode and pfinet process to let them restart with the newer -netdde. If it still does not work, please post in a bug report the full output of the netdde settrans -above, as well as the output of <code>lspci</code> and <code>lspci -n</code> . -</p> - -<p> -To configure the network without going through <tt>/etc/network/interfaces</tt>, -the pfinet translator must be configured. -This can be done by using <code>dhclient</code> from the -<code>isc-dhcp-client</code> package. -This can also be done by hand by using <code>inetutils-ifconfig</code> -from the <code>inetutils-tools</code> package, and <code>ping</code> is -available in the <code>inetutils-ping</code> package. -Last but not least, this can be done (and recorded for good) by hand using the -<code>settrans</code> command to attach a translator to a given -filesystem node. When programs access the node by, for example sending an RPC, -the operating system will transparently start the server to handle the request. -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans -fgap /servers/socket/2 /hurd/pfinet -i /dev/eth0 \ - -a a.b.c.d -g e.f.g.h -m i.j.k.l -</pre></td></tr></table> - -<p> -Here, <code>settrans</code> is passed several options. The first two, -<q><var>fg</var></q>, force any existing translator to go away. The next two, -<q><var>ap</var></q>, make both active and passive translators. By making the -translator active, we will immediately see any error messages on -<tt><q>stderr</q></tt>. The latter saves the translator and arguments in the node -so it can be transparently restarted later (i.e. making the setting persistent -across reboots). The options are followed by the node to which the translator -is to be attached, then the program (i.e. translator) to run and any arguments -to give it. The <q><var>-i</var></q> option is the interface <code>pfinet</code> -will listen on, <q><var>-a</var></q> is the IP address, <q><var>-g</var></q> is the -gateway and <q><var>-m</var></q> is the network mask. -</p> - -<p> -Be sure to add name servers to your <tt><q>/etc/resolv.conf</q></tt> file: -</p> - -<table><tr><td> </td><td class=example><pre> - nameserver 192.168.1.1 -</pre></td></tr></table> - -<p> -To test the configuration, <code>ping -c2 gateway</code>. The -<q><var>-c</var></q> is important to limit the number of pings; recall, -<kbd>CONTROL-C</kbd> does not work in single user mode. -</p> - -<p> -Help on <code>settrans</code> can be obtained by passing it the -<q><var>--help</var></q> option. Help on a specific translator can be gotten by -invoking it from the command line with the same argument, e.g.: -</p> - -<table><tr><td> </td><td class=example><pre> - \# /hurd/pfinet --help -</pre></td></tr></table> - -<p> -As there can be a lot of output, consider piping this through a pager such as -<code>less</code>. -</p> - -<p> -To also configure IPv6 support, the same configuration has to be recorded on -both <tt>/servers/socket/2</tt> and <tt>/servers/socket/26</tt>, referencing -each other so that only one is actually started, bound to both nodes: -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans -fgap /servers/socket/2 /hurd/pfinet -6 /servers/socket/26 -i /dev/eth0 \ - -a a.b.c.d -g e.f.g.h -m i.j.k.l - \# settrans -p /servers/socket/26 /hurd/pfinet -4 /servers/socket/2 -i /dev/eth0 \ - -a a.b.c.d -g e.f.g.h -m i.j.k.l -</pre></td></tr></table> - -<p> -The pfinet server enables IPv6 autoconfiguration by default. The current status -can be obtained from <tt>fsysopts /servers/socket/26</tt>. Addresses can also -be set by hand, by using e.g. <tt>-A 2001:123:123::42/64 -G 2001:123:123::1</tt>. -</p> - -<p> -The configuration of pfinet can also be changed live -(without record on disk) by using <tt>fsysopts</tt>: -</p> - -<table><tr><td> </td><td class=example><pre> - \# fsysopts /servers/socket/2 - /hurd/pfinet --interface=/dev/eth0 --address=10.3.0.1 --netmask=255.255.0.0 --gateway=10.3.0.128 - \# fsysopts /server/socket/2 -a 10.3.0.2 -m 255.255.0.0 -g 10.3.0.128 -</pre></td></tr></table> - -<p> -A firewall can be set up by interposing the <tt>eth-filter</tt> translator, for instance, this prevents access to port 22: -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans -c /dev/eth0f /hurd/eth-filter -i /dev/eth0 -r "not port 22" -</pre></td></tr></table> - -<p> -The filtered device, <tt>/dev/eth0f</tt>, can then be given to <tt>pfinet</tt> -or <tt>dhclient</tt> instead of /dev/eth0. -</p> - - -<h3> Keyboard layout </h3> - -<p> -The layout of the keyboard can be configured through the standard -<code>keyboard-configuration</code> package. Make sure that it is installed, and -run <code>dpkg-reconfigure keyboard-configuration</code>. Only the layout is -supported, variants are not (yet). The effect will not -be immediate, as the console needs to be restarted to take the parameter into -account. Rebooting should be fine for instance. -</p> - -<h3> Other File Systems </h3> - -<p> -Next, edit <tt><q>/etc/fstab</q></tt> to add any additional filesystems as well as -swap space. It is <em>very important</em> that swap space be used; the Hurd -will be an order of magnitude more stable. Note that the Hurd can transparently -share a swap partition with Linux but will happily page to any device including -a raw partition such as your home partition. By default, <code>nano</code> and <code>vi</code> are -the only editors installed by the base distribution. -</p> - -<p> -Here is an example <tt><q>/etc/fstab</q></tt> file: -</p> - -<table><tr><td> </td><td class=example><pre> -\# <file system> <mount point> <type> <options> <dump> <pass> -/dev/hd0s1 / ext2 rw 0 1 -/dev/hd0s2 /home ext2 rw 0 2 -/dev/hd0s3 none swap sw 0 0 -</pre></td></tr></table> - -<p> -If any <code>/dev</code> device entry is missing, remember to create it using the <code>MAKEDEV</code> command: -</p> - -<table><tr><td> </td><td class=example><pre> - \# cd /dev - \# ./MAKEDEV hd0s1 hd0s2 hd0s3 -</pre></td></tr></table> - -<p> -You can also mount a filesystem by hand by calling <code>settrans</code>: -</p> - -<table><tr><td> </td><td class=example><pre> - \# settrans /mnt /hurd/ext2fs /dev/hd0s5 -</pre></td></tr></table> - -<p> -The idea behind this command is that you set on the <code>/mnt</code> node the -<code>/hurd/ext2fs /dev/hd0s5</code> translator. <code>/hurd/ext2fs</code> will -get executed and start read/writing <code>/dev/hd0s5</code> and show its content -on <code>/mnt</code>. More information can be found in the -<a href="hurd-doc-translator">Translator documentation</a>. -</p> - -<p> -To mount an nfs filesystem, <code>/hurd/nfs</code> translator is used. When -run as non-root, the translator will connect to the server using a port above -1023. By default, GNU/Linux will reject this. To tell GNU/Linux to accept -connections originating from a non-reserved port, add the -<q><var>insecure</var></q> option to the export line. Here is an example -<tt><q>/etc/exports</q></tt> file assuming the client's ip address is -<tt><q>192.168.1.2</q></tt>: -</p> - -<table><tr><td> </td><td class=example><pre> - /home 192.168.1.2(rw,insecure) -</pre></td></tr></table> - -<p> -To mount this from a GNU box and assuming that nfs server's ip address is -<tt><q>192.168.1.1</q></tt>: -</p> - -<table><tr><td> </td><td class=example><pre> -\# settrans -cga /mount/point /hurd/nfs 192.168.1.1:/home -</pre></td></tr></table> - - -<h2> Have fun with Debian GNU/Hurd </h2> - -<p> -Now, what nice things can we do with the Hurd? -</p> - -<h3> Mount disk images </h3> - -<p> -Accessing the content of a CD image is a bit tedious with standard Unix systems -if you are not root. On GNU/Hurd, it amounts to this: -</p> - -<table><tr><td> </td><td class=example><pre> -settrans ~/mnt /hurd/iso9660fs CD_image.iso -</pre></td></tr></table> - -<p> -And it is completely safe: the <code>iso9660fs</code> translator is running -under your identity, not root. You can even code your own translator for any -kind of filesystem. Yes, this is like FUSE. Without all the kludge. -</p> - -<h3> Transparent FTP </h3> - -<p> -The following sets up a transparent <code>ftp</code> directory: -</p> - -<table><tr><td> </td><td class=example><pre> -settrans -c /ftp: /hurd/hostmux /hurd/ftpfs / -</pre></td></tr></table> - -<p> -Now, <code>cd</code> to e.g. <code>/ftp://ftp.gnu.org/</code>, and run <code>ls</code> there. -Yes, you can from your home simply run <code>tar xf ftp://ftp.gnu.org/pub/gnu/gcc/gcc-4.6.0/gcc-4.6.0.tar.bz2</code> ! -</p> - -<h3> Sub-Hurd </h3> - -<p> -A <a href="https://www.gnu.org/software/hurd/hurd/subhurd.html">sub-Hurd</a> is a -complete subsystem. Very much like virtualization containers on first -sight. Except that you do not need to be root at all to run one. -</p> - -<h3> gdb ext2fs, pfinet, ... </h3> - -<p> -Yes, you can run gdb on e.g. the ext2fs implementation, the <code>pfinet</code> TCP/IP stack, etc. -</p> - -<h3> And many more things! </h3> - -<p> -Some in-progress work include <code>mboxfs</code>, <code>tarfs</code>, <code>xmlfs</code>, <code>gopherfs</code>, ... -</p> - -#<h3> 7.3 Rebooting </h3> -# -#<p> -#Finally, reboot into multiuser mode, i.e. in the same way single user mode was -#brought up minus the <q><var>-s</var></q> option when loading the kernel. For -#details, see section 5. Booting GNU/Hurd. -#</p> -# -#<p> -#Happy Hacking! -#</p> - -<h2>Final Words </h2> - -<p> -The following are just install-time quickies, make sure to also read -documentation for the installed system: the <a href=hurd-doc>Debian GNU/Hurd documentation</a>, -but also the <a href=http://hurd.gnu.org/>Upstream website</a>. -</p> - - -#<h3> 8.1 The Grub Menu </h3> -# -#<p> -#Having to always load the kernel by hand can be very tedious. Edit the -#<tt><q>/boot/grub/menu.lst</q></tt> for Grub1 or -#<tt><q>/boot/grub/grub.cfg</q></tt> for Grub2 and tailor it appropriately; -#booting will become much quicker and easier. -#</p> -# -# -#<h3> 8.2 Adding Devices </h3> -# -#<p> -#By default, only a few devices are created in the <tt><q>/dev</q></tt> directory. -##Use the <code>MAKEDEV</code> script to create any needed device nodes. -#</p> - -<h3><a name=morepackages> Installing More Packages </a></h3> - -<p> -There are several ways to add packages. Downloading and using -<code>dpkg -i</code> works but is very inconvenient. The easiest method -is to use <code>apt-get</code>. -</p> - -<p> -If you have used the Debian GNU/Hurd 2021 release, the safest -way is use the snapshot of this release, by creating a file -<code>/etc/apt/apt.conf.d/99ignore-valid-until</code> containing -</p> - -<table><tr><td> </td><td class=example><pre> -Acquire::Check-Valid-Until "false"; -</pre></td></tr></table> - -<p> -And then the snapshot can be used as apt source: edit -<tt><q>/etc/apt/sources.list</q></tt>, add the following unreleased entry. -</p> - -<table><tr><td> </td><td class=example><pre> -deb http://snapshot.debian.org/archive/debian-ports/20210812T100000Z/ sid main -deb-src http://snapshot.debian.org/archive/debian/20210812T100000Z/ sid main -deb [trusted=yes] https://snapshot.debian.org/archive/debian-ports/20210812T100000Z/ unreleased main -</pre></td></tr></table> - -<p> -Update, install the <code>debian-ports-archive-keyring</code> package, and update again, you now have the -full Debian GNU/Hurd 2021 release available. -</p> - - -<p> -If you have used a snapshot later than the 2021 release, you can add these -sources to get the most recent packages: -</p> - -<table><tr><td> </td><td class=example><pre> -deb http://deb.debian.org/debian-ports unstable main -deb-src http://deb.debian.org/debian unstable main -deb http://deb.debian.org/debian-ports unreleased main -</pre></td></tr></table> - -<p> -Update, install the <code>debian-ports-archive-keyring</code> package, and -update again. -</p> - -<p> -If when doing your first <code>apt-get</code>, <code>dpkg</code> complains of -missing programs, get root in a login shell (i.e. <code>su -</code>, not just -<code>su</code>). -</p> - -<p> -If GNU Mach does not recognize your network card or you use a modem, the only -way to upgrade will be to download the packages and then transfer them to the -GNU system. The easiest way to do this is to use apt off-line. Refer to -<tt><q>/usr/share/doc/apt-doc/offline.text.gz</q></tt> for detailed instructions. -</p> - - -<h3>The Hurd console</h3> - -<p> -Besides the Mach console you encountered during installation, the GNU/Hurd -features a powerful user-space console providing virtual terminals. -If you have installed in pseudo-graphical mode, it should be started -automatically at boot, otherwise you can start it manually with the following -command: -</p> - -<table><tr><td> </td><td class=example><pre> - \# console -d vga -d pc_mouse --repeat=mouse -d pc_kbd --repeat=kbd -d generic_speaker -c /dev/vcs -</pre></td></tr></table> - -<p> -If it is confirmed to be working, it can be enabled at boot from -<tt>/etc/default/hurd-console</tt>: turn <tt>ENABLE="false"</tt> into -<tt>ENABLE="true"</tt>. -</p> - -<p> -Inside the Hurd console, you can switch between virtual terminals via -<kbd>ALT+F1</kbd>, <kbd>ALT+F2</kbd> and so on. <kbd>ALT+CTRL+BACKSPACE</kbd> detachs -the Hurd console and brings you back to the Mach console, from where you -can reattach again with the above command. -</p> - - -<h3>X.Org </h3> - -<p> -X.Org has been ported and all video cards, which it supports that do not -require a kernel module or drm should work. -</p> - -<p> -You need to already be running the Hurd console and have repeaters setup as -indicated in the previous section. For instance, check that <code>echo -$TERM</code> prints <code>hurd</code>, and check that <code>/dev/cons/kbd</code> -and <code>/dev/cons/mouse</code> exist. -</p> - -<p> -You need to run <tt>dpkg-reconfigure x11-common xserver-xorg-legacy</tt> to allow any user to start -Xorg, because the X wrapper does not know about the Hurd and Mach consoles. -</p> - -<p> -You also need to create a <tt>/etc/X11/xorg.conf</tt> to enable the control-alt-backspace shortcut: -</p> - -<table><tr><td> </td><td class=example><pre> -Section "InputDevice" - Identifier "Generic Keyboard" - Driver "kbd" - Option "XkbOptions" "terminate:ctrl_alt_bksp" -EndSection -</pre></td></tr></table> - -<p> -It may happen that for some reason Xorg chooses a 16/9 resolution but a 4/3 desktop size. Blame Xorg, not the Hurd :) To avoid the issue, append this to <tt>/etc/X11/xorg.conf</tt> : -</p> - -<table><tr><td> </td><td class=example><pre> -Section "Screen" - Identifier "myScreen" - SubSection "Display" - Virtual 1024 768 - EndSubSection -EndSection -</pre></td></tr></table> - -<p> -You will need several X packages. <code>xorg</code>, -<code>rxvt</code> and a window manager: <code>twm</code>, <code>icewm</code>, <code>openbox</code>, ... -are a good start. If you want X to get started at boot, you have to install a -display manager. <code>lightdm</code> and <code>gdm</code> do not work yet, but -<code>xdm</code> should just work fine. -</p> - -<p> -Finally, run <code>startx /usr/bin/yourwm</code> -</p> - -<p> -If that doesn't work, as mentioned by the error message, look in <tt>/var/log/Xorg.0.log</tt> (or post it to the list for people to have a look). -</p> - -<h3>Upgrading your System</h3> - -<p> -If you are using a Debian release snapshot, you will not have any upgrade -available, since the released distribution is frozen at the release date. -<b>This means you will not get security updates!</b> You may rather want to -enable the unstable distribution as described in section -<a href=#morepackages>Installing More Packages</a>. -</p> - -<p> -Once you have enabled the unstable distribution, note that since this is -unstable, it is affected by library transition hickups, so do not be surprised -that it will sometimes not be able to upgrade some packages. Generally, you can -use the recommended Debian upgrade procedure: first use -</p> - -<table><tr><td> </td><td class=example><pre> -\# apt upgrade --without-new-pkgs -</pre></td></tr></table> - -<p>to upgrade what can be without changing the list of packages, and then use</p> - -<table><tr><td> </td><td class=example><pre> -\# apt full-upgrade -</pre></td></tr></table> - -<p>to upgrade the rest.</p> - -<p>Note: if you very seldomly upgrade your system, you may hit upgrade -issues. Make sure to first upgrade to the latest release snapshot (Hurd 2021, -see section <a href=#morepackages>Installing More Packages</a>) before upgrading -from the unstable distribution.</p> - -<h3>Last words</h3> - -<p> -To shutdown your system, simply use <code>halt</code>, <code>poweroff</code> or <code>reboot</code>. If that happens to sometimes hang because some daemon is not terminating properly, you can use instead <code>halt-hurd</code>, <code>poweroff-hurd</code>, <code>reboot-hurd</code>, which don't actually shut down daemons, but properly sync data to disk. -</p> diff --git a/greek/ports/hurd/hurd-news.wml b/greek/ports/hurd/hurd-news.wml deleted file mode 100644 index 7dc9ac47872..00000000000 --- a/greek/ports/hurd/hurd-news.wml +++ /dev/null @@ -1,433 +0,0 @@ -#use wml::debian::template title="Debian GNU/Hurd -- News" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/hurd/menu.inc" -#use wml::debian::translation-check translation="b913c6c68c2f0764dc42c375ce0fc712fe6f2d1f" maintainer="galaxico" - -<h1>News about Debian GNU/Hurd</h1> - -<h3><:=spokendate ("2021-08-14"):></h3> - -<p>Debian GNU/Hurd 2021 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2021</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the stable Debian -"Bullseye" release (August 2021), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/11.0/hurd-i386/">cdimage</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd. The easiest way to run it is -<a href="https://www.debian.org/ports/hurd/hurd-install">inside a VM such as qemu</a></p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with about -70% of the Debian archive, and more to come!</p> - -<ul> -<li>The port of go is complete</li> -<li>Support for file record locking was added</li> -<li>Some parts of experimental APIC, SMP and 64bit support was added</li> -<li>Userland IRQ delivery was reworked</li> -<li>An experimental rump-based userland disk driver was introduced. This - means dropping the Linux glue from the GNU Mach kernel is getting - very close!</li> -<li>Many fixes, including some important security fixes.</li> -</ul> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a> (or <a href="http://darnassus.sceen.net/~hurd-web/faq/">its latest version</a>), -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>in the past</a>. -There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2019-07-07"):></h3> - -<p>Debian GNU/Hurd 2019 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2019</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the stable Debian -"buster" release (July 2019), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/10.0/hurd-i386/">cdimage</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd. The easiest way to run it is -<a href="https://www.debian.org/ports/hurd/hurd-install">inside a VM such as qemu</a></p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with about -80% of the Debian archive, and more to come!</p> - -<ul> -<li>An ACPI translator is available, it is currently only used to shut down the -system.</li> -<li>The LwIP TCP/IP stack is now available as an option.</li> -<li>A PCI arbiter has been introduced, and will be useful to properly manage PCI -access, as well as provide fine-grain hardware access.</li> -<li>Support for LLVM was introduced.</li> -<li>New optimisations include protected payloads, better paging management and -message dispatch, and gsync synchronization.</li> -</ul> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a> (or <a href="http://darnassus.sceen.net/~hurd-web/faq/">its latest version</a>), -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>in the past</a>. -There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2017-06-18"):></h3> - -<p>Debian GNU/Hurd 2017 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2017</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the stable Debian -"stretch" release (May 2017), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/9.0/hurd-i386/">cdimage</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd. The easiest way to run it is -<a href="https://www.debian.org/ports/hurd/hurd-install">inside a VM such as qemu</a></p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with about -80% of the Debian archive, and more to come!</p> - -<ul> -<li>The core GNU Hurd and GNU Mach packages were updated to versions 0.9 and - 1.8, respectively. Besides numerous other improvements, they bring vastly - improved stability under memory load and prolonged uptime.</li> -<li>The native fakeroot tool has been greatly improved, allowing to be used for - building packages, making that quite faster and safer.</li> -<li>It is now possible to run subhurds as unprivileged user, thus providing easy -lightweight virtualization.</li> -<li>The supported memory size was extended beyond 3GiB.</li> -</ul> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a> (or <a href="http://darnassus.sceen.net/~hurd-web/faq/">its latest version</a>), -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>in the past</a>. -There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2015-04-25"):></h3> - -<p>Debian GNU/Hurd 2015 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2015</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the stable Debian -"jessie" release (April 2015), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/8.0/hurd-i386/">Debian Ports</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd. The easiest way to run it is -<a href="https://www.debian.org/ports/hurd/hurd-install">inside a VM such as qemu</a></p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with more -than 80% of the Debian archive, and more to come!</p> - -<p>Since the last snapshot release coinciding with "wheezy", the init system has been -switched to sysvinit for a more Debian-like experience. Further changes since -the last snapshot include:</p> - -<ul> -<li>The core GNU Hurd and GNU Mach packages were updated to versions 0.6 and - 1.5, respectively. Besides numerous other improvements, they bring vastly - improved stability under load and prolonged uptime.</li> -<li>The networking drivers were migrated to user-space drivers using the NetDDE - framework and a Linux-2.6.32 codebase.</li> -</ul> - -<p> -Notable new or upgraded packages which required considerable porting effort and/or -are known to work well on Debian GNU/Hurd include Iceweasel 31 ESR, Xfce 4.10, -X.org 7.7 and Emacs 24.4. -</p> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a> (or <a href="http://darnassus.sceen.net/~hurd-web/faq/">its latest version</a>), -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>in the past</a>. -There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2013-05-21"):></h3> - -<p>Debian GNU/Hurd 2013 <em>released</em>!</p> - -<p>It is with huge pleasure that the Debian GNU/Hurd team announces the -<strong>release of Debian GNU/Hurd 2013</strong>. <br /> -This is a snapshot of Debian "sid" at the time of the Debian -"wheezy" release (May 2013), so it is mostly based on the same sources. It is <em>not</em> an -official Debian release, but it is an official Debian GNU/Hurd port release.</p> - -<p>The installation ISO images can be downloaded from -<a href="https://cdimage.debian.org/cdimage/ports/7.0/hurd-i386/">Debian Ports</a> -in the usual three Debian flavors: NETINST, CD, or DVD. Besides the friendly -Debian installer, a pre-installed disk image is also available, making it even easier to try -Debian GNU/Hurd.</p> - -<p>Debian GNU/Hurd is currently available for the i386 architecture with more than 75% of the Debian archive, and more to come!</p> - -<p>Please make sure to read the -<a href="https://www.debian.org/ports/hurd/hurd-install">configuration information</a>, -the <a href="https://www.gnu.org/software/hurd/faq.html">FAQ</a>, -and the <a href="https://www.gnu.org/software/hurd/hurd/documentation/translator_primer.html">translator primer</a> -to get a grasp of the great features of GNU/Hurd.</p> - -<p>Due to the very small number of developers, -our progress of the project has not been as fast as other successful -operating systems, but we believe to have reached <a -href="https://www.gnu.org/software/hurd/hurd/status.html">a very decent -state</a>, even with our limited resources. </p> - -<p>We would like to thank all the people who have worked on GNU/Hurd <a -href=https://www.gnu.org/software/hurd/history.html>over the past -decades</a>. There were not many people at any given time (and still not many people -today, please <a href="https://www.gnu.org/software/hurd/contributing.html">join</a>!), but in the end a lot of people have -contributed one way or the other. <strong>Thanks everybody!</strong></p> - -<h3><:=spokendate ("2011-06-11"):></h3> - -<p>Various bugs of the debian-installer based image were fixed, there is no -known issue except that GNOME and KDE are not installable yet.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2011-02-15"):></h3> - -<p>The debian-installer based image was updated to squeeze d-i packages.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2010-09-01"):></h3> - -<p>A debian-installer based image is available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2009-10-19"):></h3> - -<p>The L1 DVD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2007-12-21"):></h3> - -<p>The K16 CD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2007-11-19"):></h3> - -<p>The K15 CD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2006-11-27"):></h3> - -<p>The K14 CD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2006-04-26"):></h3> - -<p>The K11 CD mini image is now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2005-10-26"):></h3> - -<p>The K10 CD and DVD images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2005-05-14"):></h3> - -<p>The K9 CD Images are now available.<br/> -See the <a href="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2004-12-30"):></h3> - -<P>The K8 CD Images are now available. These Images support Filesystems bigger -than 2 GB and feature an update of the network device drivers.<br/> -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2004-03-06"):></h3> - -<P>After a long time of not being updated, new CVS snapshots of <a -href="https://tracker.debian.org/pkg/hurd">the Hurd</a> and <a -href="https://tracker.debian.org/pkg/gnumach">GNU Mach</a> are uploaded.</p> - -<h3><:=spokendate ("2003-07-31"):></h3> - -<P>The K4 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2003-04-30"):></h3> - -<P>The K3 CD images are now available. -They have been renamed to GNU-K3-CDx.iso <br> -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - - -<h3><:=spokendate ("2003-03-06"):></h3> - -<P>The K2 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2002-10-10"):></h3> - -<P>The J2 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - - -<P>Upgrading Debian GNU/Hurd from a libio-based system before -2002-08-12 (including J1 CD series). - -<P>Updating a Debian GNU/Hurd system in August 2002 requires to follow -the procedure outlined in the <A HREF="extra-files/hurd-upgrade.txt">upgrade -manual</A>. This update procedure is necessary because the Hurd -interfaces went through an incompatible change to prepare support of -long files. - -<h3><:=spokendate ("2002-08-05"):></h3> - -<P>The J1 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2002-02-26"):></h3> - -<P>The H3 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-12-15"):></h3> - -<P>The H2 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-11-11"):></h3> - -<P>The H1 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-10-05"):></h3> - -<P>The G1 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-08-07"):></h3> - -<p> -Today is the first time we crossed the 40% mark in the <a -href="https://buildd.debian.org/stats/graph.png">statistic about -up-to-date packages</a> per architecture.</p> - -<h3><:=spokendate ("2001-07-31"):></h3> - -<P>The F3 CD images are now available. -See the <A HREF="./hurd-cd">Hurd CD page</a> for further information.</p> - -<h3><:=spokendate ("2001-07-12"):></h3> - -<p>Marcus Brinkmann has made available his presentation about the hurd. -It is currently available from:</p> -<a href="http://www.marcus-brinkmann.de/talks.en.html">http://www.marcus-brinkmann.de/talks.en.html</a> - -<h3><:=spokendate ("1999-11-01"):></h3> - -<p> -Cleaned up some outstanding bug reports which were closed by now. Going to -upload some more packages, in addition to those uploaded in the last days -(inetutils, grub, man-db, now coming hostname, mtools, ...). All those now -compile without any changes, which is a good thing. Seems we are slowly -stabilizing the basic set of packages.</p> - -<h3><:=spokendate ("1999-09-29"):></h3> - -<p> -There are <a -href="ftp://alpha.gnu.org/gnu/hurd/contrib/marcus/">patches to glue -Linux character devices into GNU Mach</a> now. These patches are very -experimental, and the tty driver does not work correctly with the term -translator, but we are working on it and hope to be able to provide a -binary soon. Note that this will bring the Linux console to the Hurd -(including color and virtual consoles), as well as drivers for various -non standard mice and other serial devices.</p> - -<p> -I heard that some people are concerned about the size of GNU Mach, as -well as it becoming a subset of Linux. Please note that we are only -searching for a temporary solution here, until we have the time to -redesign the driver interface in GNU Mach (or use another -Microkernel). The microkernel is not at all that important as the Hurd -servers are which run on top of it.</p> - -<p> -On the package side, we have now a proper <code>shadow</code> package -(which produces <code>passwd</code> (thanks, BenC!)). Also, -<code>man-db</code> should work out of the box now even with long -filenames, but I haven't checked the other changes. All in all, the -base section is getting into a good shape. Torin has applied my patch -for <code>perl</code>, and that's another package I have to check out -if it can be `finalized' now.</p> - -<h3><:=spokendate ("1999-08-31"):></h3> - -<p> -<code>debianutils 1.12</code> does now compile without patch.</p> - -<h3><:=spokendate ("1999-08-05"):></h3> - -<p> -Source NMU for <code>passwd</code> (<code>shadow</code>) should fix -all remaining problems in this package. This should make for a -smoother install. On the other side, <code>mutt</code> requires a -small patch.</p> - -<h3><:=spokendate ("1999-07-27"):></h3> - -<p> -New packages of the core system are finished now. The Hurd has a new -way to boot (the part that happens after init is started), take a look -at <code>/libexec/runsystem</code>. This is useful for the -<code>sysvinit</code> package, which is almost done. Fixed a buglet in -GNU Lib C and one in GNU Mach. Autodetection of all network cards -should work now, but maybe we need to tweak the order a bit (3c5x9 -before 3c59x).</p> - -<h3><:=spokendate ("1999-07-22"):></h3> - -<p> -<code>cpio 2.4.2-25</code> fixes the remaining Hurd compatibility issue -and can now be compiled without changes. Thanks Brian!</p> - -<h3><:=spokendate ("1999-07-05"):></h3> - -<p> -Perl 5.005.03 patches submitted to the maintainer. The upstream code -was already clean (thanks, Mark!), but the Debian packaging scripts -were linux specific.</p> diff --git a/greek/ports/i386/Makefile b/greek/ports/i386/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/i386/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/i386/index.wml b/greek/ports/i386/index.wml deleted file mode 100644 index 0af2351dba4..00000000000 --- a/greek/ports/i386/index.wml +++ /dev/null @@ -1,22 +0,0 @@ -#use wml::debian::template title="Debian GNU/Linux on x86 Machines" BARETITLE=true -#use wml::debian::translation-check translation="e9c587fe48386f2bedf1d5a6284b6959c2b4635c" maintainer="galaxico" - -<p>Being the first architecture supported by Debian, -most of the general Debian web pages apply to this port.</p> - -<p>There is some information specific to this architecture, however, that we -will list here.</p> - -<h2>Installing</h2> - -<p>If you wish to install Debian, you should look at the -<a href="$(HOME)/releases/stable/i386/">installation instructions</a> -whether you are installing from a CD or downloading off the -Internet.</p> - -<h2>Development</h2> - -<p> -The build servers for this architecture are operated by -<a href="https://dsa.debian.org/">DSA</a>. -</p> diff --git a/greek/ports/ia64/Makefile b/greek/ports/ia64/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/ia64/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/ia64/index.wml b/greek/ports/ia64/index.wml deleted file mode 100644 index ef761bc7faa..00000000000 --- a/greek/ports/ia64/index.wml +++ /dev/null @@ -1,64 +0,0 @@ -#use wml::debian::template title="IA-64 Port" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/ia64/menu.inc" -#use wml::debian::translation-check translation="09225985e5d001870fb942c6fb74704fe3fc552a" maintainer="galaxico" - -<h1>Debian for IA-64</h1> - -<h2>Status</h2> - -<p> -IA-64 was a supported Debian architecture from Debian 3.0 (woody) to Debian 7 (wheezy) - -<p> -If you would like to help, start by subscribing to the -<a href="#mailinglist">debian-ia64 mailing list</a>. - -<p> -The normal Debian channels for acquiring installation media and documentation -include ia64 CD images. - -<h2>BIOS Versions</h2> - -<p> -All modern ia64 systems should work fine. -<p> -It's possible that you may find a very early ia64 machine that needs a BIOS -upgrade to work well with Linux. -One particular combination we've heard about is trying to run new -kernels on "Lion" systems with really old BIOS versions. -To try to make this easier, -here's what we know about BIOS versions that work well for Debian on older -ia64 systems: - -<ul> -<li> Lion, aka HP rx4610, version 99b works well. -<li> BigSur, aka HP i2000, version 130 works well. -</ul> - -<p> -Firmware downloads for -<a href="http://www.hp.com">HP</a> -systems are available starting -<a href="http://welcome.hp.com/country/us/eng/software_drivers.htm"> HERE </a>. -</p> - -<p> -If anyone has information about suitable BIOS versions for other IA-64 systems -that are successfully running Debian, let us know on the debian-ia64 list! </p> - -<h2>Contacts</h2> - -<p> -The instigators of the IA-64 port were Bdale Garbee and Randolph Chung. -The best way to ask questions now is via the mailing list. - -<h2><a name="mailinglist">Mailing List</a></h2> - -<p> -To subscribe to the mailing list for this port, send a message containing -the word "subscribe" as the subject to -<email "debian-ia64-request@lists.debian.org"> to sign up, or use the -<a href="https://lists.debian.org/debian-ia64/">list web page</a>. -You can also browse and search the -<a href="https://lists.debian.org/debian-ia64/">list archive</a>. -</p> diff --git a/greek/ports/ia64/news.wml b/greek/ports/ia64/news.wml deleted file mode 100644 index 85a7e17a8c2..00000000000 --- a/greek/ports/ia64/news.wml +++ /dev/null @@ -1,74 +0,0 @@ -#use wml::debian::template title="IA-64 Port -- News" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/ia64/menu.inc" -#use wml::debian::translation-check translation="f832fa04df640fc3eba2bdbd0d92b593c3b68afd" maintainer="galaxico" - -<h1>News about Debian for IA-64</h1> - -<h3><:=spokendate ("2003-03-04"):></h3> - -<p><strong>Installer CD image updated</strong> - -<p> -A new installation CDROM image is now available. This version uses a -2.4.19 020821.1 kernel. This kernel includes all the storage and network -drivers required to install on every ia64 system Bdale has access to. -Enjoy! -<a href="http://gluck.debian.org/ia64/ia64-net-20030304.iso">HTTP</a>. - -<h3><:=spokendate ("2002-05-06"):></h3> - -<p><strong>Installer CD image updated</strong> - -<p> -The ISO image for creating a CDROM containing the Debian installation toolset -for IA-64 has been freshened to the kernel and "boot floppies" versions that -we expect to be included in the Debian 3.0 (woody) release. Enjoy! -<a href="http://gluck.debian.org/ia64/ia64-net-20020506.iso">HTTP</a>. - -<h3><:=spokendate ("2002-01-28"):></h3> - -<p><strong>Installer CD image updated</strong> - -<p> -The ISO image for creating a CDROM containing the Debian installation toolset -for IA-64 has been freshened to a version from early December that works well -on the systems we have access to. -<a href="http://gluck.debian.org/ia64/ia64-base-20011202-rc1.iso.gz">HTTP</a>. - -<h3><:=spokendate ("2001-08-10"):></h3> - -<p><strong>Installer CD image published</strong> - -<p> -An ISO image for creating a CDROM containing the Debian installation toolset -for IA-64 is now available via -<a href="http://gluck.debian.org/ia64/cd-20010810.iso.gz">HTTP</a>. - -<h3><:=spokendate ("2001-08-06"):></h3> - -<p><strong>Debian accepts ia64 for release with Debian 3.0 (woody)!</strong> - -<p> -It is with great pleasure that we announce the acceptance of ia64 as an -architecture for the upcoming Debian 3.0 stable release, codename woody. -Installation tools for ia64 are now in the woody tree, and packages now in -unstable are beginning to be promoted to the testing/woody tree. - -<h3><:=spokendate ("2001-07-24"):></h3> - -<p><strong>Official Request to Release with Debian 3.0 (woody)</strong> - -<p> -Approximately 70% of all Debian packages are built and up to date in the -archives, an automated build system is running smoothly, installation tools -are available in the archive, and the number of systems running is growing -rapidly. - -<h3><:=spokendate ("2001-01-16"):></h3> - -<p><strong>First Native Boot</strong> - -<p> -Debian booted on IA-64 natively for the first time, after development in a -chroot environment on top of a TurboLinux base install. - diff --git a/greek/ports/kfreebsd-gnu/Makefile b/greek/ports/kfreebsd-gnu/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/kfreebsd-gnu/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/kfreebsd-gnu/index.wml b/greek/ports/kfreebsd-gnu/index.wml deleted file mode 100644 index 71d328728c2..00000000000 --- a/greek/ports/kfreebsd-gnu/index.wml +++ /dev/null @@ -1,53 +0,0 @@ -#use wml::debian::template title="Debian GNU/kFreeBSD" -#use wml::debian::translation-check translation="6f3adf6374f35194686f89dec2ba66b1ecf3bb5f" maintainer="galaxico" - -#use wml::debian::toc - -<toc-display/> - -<p>Debian GNU/kFreeBSD is a port that consists of -<a href="https://www.gnu.org/">GNU userland</a> using the -<a href="https://www.gnu.org/software/libc/">GNU C library</a> on top of -<a href="https://www.freebsd.org/">FreeBSD</a>'s kernel, coupled with the -regular <a href="https://packages.debian.org/">Debian package set</a>.</p> - -<div class="important"> -<p>Debian GNU/kFreeBSD is not an officially supported -architecture. It has been released with Debian 6.0 (Squeeze) and 7.0 -(Wheezy) as a <em>technology preview</em> and the first non-Linux -port. Since Debian 8 (Jessie) it is though no more included in official -releases.</p> -</div> - -<toc-add-entry name="resources">Resources</toc-add-entry> - -<p>There's more information about the port (including an FAQ) in the -<a href="https://wiki.debian.org/Debian_GNU/kFreeBSD">Debian GNU/kFreeBSD</a> -wiki page. -</p> - -<h3>Mailing lists</h3> -<p><a href="https://lists.debian.org/debian-bsd">Debian GNU/k*BSD mailing list</a>.</p> -<h3>IRC</h3> -<p><a href="irc://irc.debian.org/#debian-kbsd">#debian-kbsd IRC channel</a> (at irc.debian.org).</p> - -<toc-add-entry name="Development">Development</toc-add-entry> - -<p>Because we use Glibc the portability problems are very simple and most times it's -just a matter of copying a test case for "k*bsd*-gnu" from another Glibc-based -system (like GNU or GNU/Linux). Look at the -<a href="https://salsa.debian.org/bsd-team/web/raw/master/porting/PORTING">porting</a> -document for details.</p> - -<p>Also look at the <a href="https://salsa.debian.org/bsd-team/web/raw/master/TODO">TODO</a> -file for more details on what needs to be done.</p> - -<toc-add-entry name="availablehw">Available Hardware for Debian Developers</toc-add-entry> - -<p>lemon.debian.net (kfreebsd-amd64) is -available to Debian developers for porting work. Please see the -<a href="https://db.debian.org/machines.cgi">machine database</a> for more -information about these machines. In general, you will be able to use the -two chroot environments: testing and unstable. Note that these systems -are not administrated by DSA, so <b>do not send requests to debian-admin -about it</b>. Instead use <email "admin@lemon.debian.net">.</p> diff --git a/greek/ports/m68k/Makefile b/greek/ports/m68k/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/m68k/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/m68k/index.wml b/greek/ports/m68k/index.wml deleted file mode 100644 index efee34d5b4e..00000000000 --- a/greek/ports/m68k/index.wml +++ /dev/null @@ -1,141 +0,0 @@ -#use wml::debian::template title="Motorola 680x0 Port" NOHEADER="yes" -#use wml::debian::toc -#use wml::debian::translation-check translation="821d2af3a565be7b911813a3fb1a5543be4391e6" maintainer="galaxico" - -<toc-display/> - -<toc-add-entry name="about">Debian on Motorola 680x0</toc-add-entry> - -<p>The Motorola 680x0 series of processors have powered personal -computers and workstations since the mid-1980s. Debian currently runs -on the 68020, 68030, 68040 and 68060 processors: this is an unofficial port -meaning that there's not an official and released m68k port any more but -this port is under development.</p> - -<p>Please note that a -<a href="https://foldoc.org/memory+management+unit"> -memory management unit (MMU)</a> is -<em>required</em>; this rules out the "EC" variants of these -processors. Floating-point emulation is available; however, it is not -functional on some mac models due to a bug in some revisions of the 68LC040 -processor. (68LC040 processors in other subarchitectures are fine; only -Macintoshes appear to have been shipped with the broken 68LC040 -processors).</p> - -<toc-add-entry name="status">Status</toc-add-entry> - -<p>The Debian m68k port was first officially released with Debian 2.0 -(hamm) and was an official port until Debian 4.0 (etch). There's now an effort -to revive this port.</p> - -<p>Currently, the Debian/m68k port supports Atari, Amiga, VMEbus, and some -Macintosh systems.</p> - -<p>For further information on the current status of the m68k port, please -visit our <a href="https://wiki.debian.org/M68k/Status">wiki page</a>.</p> - -<p>Help is always needed and welcome! In particular, kernels and boot -images supporting other ports of <a href="http://www.linux-m68k.org/">\ -the Linux/m68k kernel</a>, like the Q40/Q60 and Sun 3, would be nice.</p> - -<p>If you're willing to help, we maintain TODO lists on <a -href='https://wiki.debian.org/'>the Debian wiki</a> for <a -href='https://wiki.debian.org/M68k/Porting'>the Debian/m68k system</a> and -<a href='https://wiki.debian.org/DebianInstaller/M68k'>The Debian-installer -port to the m68k architecture</a>.</p> - - -<p>The <a href="http://unstable.buildd.net/index-m68k.html">Debian/68k autobuild -system</a> contains up to date information about the porting effort. -In case of questions and/or problems related to the autobuild system -please contact <email "debian-68k@lists.debian.org" /> with a subject tag of -"[buildd]".</p> - -<toc-add-entry name="credits">Credits</toc-add-entry> - -<p> -This is a list of people who are working on the Debian/m68k project. -It also includes some significant contributors who have "moved on" to -other things. Let us know if you're missing from this list! - -<dl> - -<dt>Frank Neumann -<dd> -Launched m68k port of Debian. - -<dt>Martin "Joey" Schulze -<dd> -Provided infrastructure at Infodrom for "kullervo", the primary build -daemon, to be connected to the Internet. Also helped organize Linux -hacker meetings at Oldenburg. - -<dt>Roman Hodek -<dd> -With James Troup, created <tt>buildd</tt>, the automated build daemon -for the m68k port. buildd is now used by other architectures, too. - -<dt>James Troup -<dd> -Wrote <tt>quinn-diff</tt> and other utilities to automate package building. - -<dt>David Huggins-Daines -<dd> -Maintained m68k support on the boot-floppies team. Also supports the <a -href="http://www.mac.linux-m68k.org/">upstream Mac kernel</a>. - -<dt>Michael Schmitz -<dd> -Built and tested the installation system for 2.1. - -<dt>Christian T. Steigies -<dd> -Maintains Debian/68k kernel packages. - -<dt>Stephen R. Marenka -<dd> -Together with Wouter Verhelst, ported debian-installer (the installation -system for Debian 3.1 and above) to the m68k architecture. - -<dt>Wouter Verhelst -<dd> -Together with Stephen Marenka, ported debian-installer (the installation system -for Debian 3.1 and above) to the m68k architecture. - -<dt>Thorsten Glaser -<dd> -Collected patches from Debian/m68k maintainers, Linux m68k developers, and -other people; brought Debian/m68k through the transition from linuxthreads to -NPTL with TLS by integrating those into the Debian packages and being the -human equivalent of a buildd for long enough to bootstrap Sid again. -Finn Thain, Andreas Schwab and Geert Uytterhoeven provided valuable input to -this, besides those already mentioned above. - -</dl> - - -<toc-add-entry name="contact">Contact information</toc-add-entry> - -<p> -The mailing list for this project is <email "debian-68k@lists.debian.org" />. -To subscribe, send a message containing the word "subscribe" as the subject -to <email "debian-68k-request@lists.debian.org" />, or use the -<a href="https://lists.debian.org/debian-68k/">mailing list web page</a>. -You can also browse and search -<a href="https://lists.debian.org/debian-68k/">the list archives</a>. - -<p>The m68k porters' mailing list used to be at <email -"m68k-build@nocrew.org"/>. This also used to be the contact address for -the m68k autobuild system. However, to contact m68k porters today, the -preferred procedure is to use debian-68k@lists.debian.org with a subject -tag of [buildd].</p> - -<p>Please send comments about these web pages to -<a href="mailto:debian-68k@lists.debian.org">the Debian/m68k mailing -list</a>.</p> - -<toc-add-entry name="links">Links</toc-add-entry> - -<p> -A dedicated page gather some <a href="links">links related to the m68k port</a>. -</p> diff --git a/greek/ports/m68k/links.wml b/greek/ports/m68k/links.wml deleted file mode 100644 index 00848aab106..00000000000 --- a/greek/ports/m68k/links.wml +++ /dev/null @@ -1,39 +0,0 @@ -#use wml::debian::template title="Motorola 680x0 Port -- Links" NOHEADER="yes" -#use wml::debian::translation-check translation="534d1b782cfb92f46dc41fd064f779fffc329b12" maintainer="galaxico" - - -<h1>Links about Linux on Motorola 680x0</h1> - -<ul> -<li><a href="http://www.linux-m68k.org/">The Linux/m68k Home -Pages</a>: support site for the Linux kernel on 680x0 hardware, -regardless of distribution. - -<li>The <a href="http://www.linux-m68k.org/faq/faq.html">Linux/m68k -FAQ</a> and <a -href="http://www.us.linux-m68k.org/cgi-bin/faqw.py?req=home">Linux/m68k -FAQ Wizard</a>. The FAQ Wizard will eventually replace the "old" FAQ; -in the meantime, you'll need to refer to the old FAQ where the FAQ -Wizard is incomplete. - -<li>The <a href="http://www.linux-m68k.org/Registry/">Linux/m68k User -Registry</a>, a rough "counter" of how many people use Linux/m68k. - -<li><a href="http://www.mac.linux-m68k.org/">Linux/m68k for the -Macintosh Project</a> - -<li>Installation guides for <a -href="http://www.linux-m68k.org/debian-amiga.html">Amigas</a>, <a -href="http://www.linux-m68k.org/debian-atari.html">Ataris</a>, <a -href="http://www.linux-m68k.org/debian-mac.html">Macs</a> and <a -href="http://www.linux-m68k.org/debian-vme.html">VMEbus</a> machines. - -<li>Christian Steigies has written <a -href="https://people.debian.org/~cts/debian-m68k-faq/">a page</a> with the -"Number One FAQ" for Debian/m68k: how to get X running. Please read -it before asking why your X11 isn't working! - -<li>The <a href="$(HOME)/CD/vendors/">Debian CD vendors</a> listing, -showing who sells CD-ROMs with Debian for m68k platforms. - -</ul> diff --git a/greek/ports/mips/Makefile b/greek/ports/mips/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/mips/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/mips/index.wml b/greek/ports/mips/index.wml deleted file mode 100644 index 830beedbb4e..00000000000 --- a/greek/ports/mips/index.wml +++ /dev/null @@ -1,133 +0,0 @@ -#use wml::debian::template title="MIPS Port" -#use wml::debian::translation-check translation="821d2af3a565be7b911813a3fb1a5543be4391e6" maintainer="galaxico" - -#include "$(ENGLISHDIR)/releases/info" -#use wml::debian::toc - -<toc-display/> - -<toc-add-entry name="about">Overview</toc-add-entry> -<p>The MIPS port is actually two ports, <em>debian-mips</em> and -<em>debian-mipsel</em>. They differ in the <a -href="https://foldoc.org/endian">endianness</a> -of the binaries. MIPS CPUs are able to run at both endiannesses, but -since that's normally not changeable in software, we need to have both -architectures. SGI machines run in <a -href="https://foldoc.org/big-endian">big-endian</a> -mode (debian-mips) while the Loongson 3 machines run in -<a -href="https://foldoc.org/little-endian">little-endian</a> -mode (debian-mipsel). Some boards, such as Broadcom's BCM91250A evaluation -board (aka SWARM) can run in both modes, selectable by a switch on the board. -Some Cavium Octeon based machines can switch between both modes in the -bootloader.</p> - -<p>Given most MIPS machines have 64-bit CPUs, a <em>debian-mips64el</em> port -is currently in development and might be released with Debian GNU/Linux 9.</p> - -<toc-add-entry name="status">Current Status</toc-add-entry> -<p>Debian GNU/Linux <current_release_jessie> supports the following machines:</p> - -<ul> - -<li>SGI Indy with R4x00 and R5000 CPUs, and Indigo2 with R4400 CPU (IP22).</li> - -<li>SGI O2 with R5000, R5200 and RM7000 CPU (IP32).</li> - -<li>Broadcom BCM91250A (SWARM) evaluation board (big and little-endian).</li> - -<li>MIPS Malta boards (big and little-endian, 32 and 64-bit).</li> - -<li>Loongson 2e and 2f machines, including the Yeelong laptop (little-endian).</li> - -<li>Loongson 3 machines (little-endian).</li> - -<li>Cavium Octeon (big-endian).</li> - -</ul> - -<p>In addition to the above machines, it is possible to use Debian on a lot more -machines provided that a non-Debian kernel is used. This is for example the -case of the MIPS Creator Ci20 development board.</p> - -<toc-add-entry name="info">General Information about</toc-add-entry> - -<p>Please see the <a href="$(HOME)/releases/stable/mips/release-notes/">\ -release notes</a> and <a href="$(HOME)/releases/stable/mips/">\ -installation manual</a> for more information.</p> - - -<toc-add-entry name="availablehw">Available Hardware for Debian Developers</toc-add-entry> - -<p>Two machines are made available to Debian developers for MIPS porting -work: etler.debian.org (mipsel/mips64el) and minkus.debian.org (mips). -The machines have development chroot environments which you can access -with <em>schroot</em>. Please see the -<a href = "https://db.debian.org/machines.cgi"> machine database</a> for more -information about these machines.</p> - - -<toc-add-entry name="credits">Credits</toc-add-entry> - -<p>This is a list of people who are working on the MIPS port:</p> - -#include "$(ENGLISHDIR)/ports/mips/people.inc" - -<toc-add-entry name="contacts">Contacts</toc-add-entry> - -<h3>Mailing lists</h3> - -<p>There are a couple of mailing lists dealing with Linux/MIPS and especially -Debian on MIPS.</p> - -<ul> - -<li>debian-mips@lists.debian.org — This list deals with Debian on MIPS.<br /> -Subscribe via mail to <email debian-mips-request@lists.debian.org>.<br /> -The archive is at <a href="https://lists.debian.org/debian-mips/">lists.debian.org</a>.</li> - -<li>linux-mips@linux-mips.org — This list is for discussions about -MIPS kernel supports.<br /> -See the <a href = "https://www.linux-mips.org/wiki/Net_Resources#Mailing_lists">Linux/MIPS</a> -page for subscription information.</li> - -</ul> - -<h3>IRC</h3> - -<p>You can find us on IRC on <em>irc.debian.org</em> on the channel -<em>#debian-mips</em>.</p> - - -<toc-add-entry name="links">Links</toc-add-entry> - -<dl> - <dt>Linux/MIPS kernel development — Lots of related information about MIPS</dt> - <dd><a href="https://www.linux-mips.org/">linux-mips.org</a></dd> - <dt>CPU Vendor</dt> - <dd><a href="https://imgtec.com/mips">https://imgtec.com/mips</a></dd> - <dt>Information about SGI hardware</dt> - <dd><a href="http://www.sgistuff.net/hardware/">http://www.sgistuff.net/hardware/</a></dd> - <dt>Debian on SGI Indy</dt> - <dd><a href="http://www.pvv.org/~pladsen/Indy/HOWTO.html">http://www.pvv.org/~pladsen/Indy/HOWTO.html</a></dd> - <dt>Debian on SGI Indy</dt> - <dd><a href="https://nathan.chantrell.net/linux/sgi-indy-and-debian-linux/">https://nathan.chantrell.net/linux/sgi-indy-and-debian-linux/</a></dd> - <dt>Debian on SGI O2</dt> - <dd><a href="https://cyrius.com/debian/o2/">http://www.cyrius.com/debian/o2</a></dd> -</dl> - - -<toc-add-entry name="thanks">Thanks</toc-add-entry> - -<p>The porterboxes and most of the build servers for the <em>mips</em> and -<em>mipsel</em> architectures are provided by <a href="https://imgtec.com"> -Imagination Technologies</a>.</p> - - -<toc-add-entry name="dedication">Dedication</toc-add-entry> - -<p>Thiemo Seufer, who was the lead MIPS porter in Debian, got killed in a -car accident. We <a href = -"$(HOME)/News/2008/20081229">dedicate the release</a> of the -Debian GNU/Linux <q>lenny</q> distribution to his memory.</p> - diff --git a/greek/ports/netbsd/Makefile b/greek/ports/netbsd/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/netbsd/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/netbsd/index.wml b/greek/ports/netbsd/index.wml deleted file mode 100644 index de8e3ebffac..00000000000 --- a/greek/ports/netbsd/index.wml +++ /dev/null @@ -1,134 +0,0 @@ -#use wml::debian::template title="Debian GNU/NetBSD" BARETITLE="yes" NOHEADER="yes" -#use wml::fmt::verbatim -#use wml::debian::translation-check translation="c9a7e0f78250fe2fea728e669907c9ee47374e1c" maintainer="galaxico" - -############################################################################# -<div class="important"> -<p><strong> -This porting effort has long been abandoned. It has had no updates since October -2002. The information in this page is only for historical purposes. -</strong></p> -</div> - -<h1> -Debian GNU/NetBSD -</h1> - -<p> -Debian GNU/NetBSD (i386) was a port of the Debian Operating System to the -NetBSD kernel and libc (not to be confused with the other Debian BSD ports -based on glibc). At the time it was abandoned (around October 2002), it was -in an early stage of development - however, it was installable from scratch. -</p> - -<p> -There was also an attempt to start a Debian GNU/NetBSD (alpha) port, which -could be run from a chroot in a native NetBSD (alpha) system, but was not -able to boot of its own, and was using most of the native NetBSD libraries. -A <a -href="https://lists.debian.org/debian-bsd/2002/debian-bsd-200201/msg00203.html">status -message</a> was sent to the list. -</p> - -<h2>Historical News</h2> - -<dl class="gloss"> - <dt class="new">2002-10-06:</dt> - <dd> - Experimental install floppies are now available for installing - a Debian GNU/NetBSD system. - </dd> - <dt>2002-03-06:</dt> - <dd> - Matthew hacked <a href="https://packages.debian.org/ifupdown">ifupdown</a> - in a workable state. - </dd> - <dt>2002-02-25:</dt> - <dd> - Matthew has reported that shadow support and PAM works on NetBSD - now. <a href="https://packages.debian.org/fakeroot">fakeroot</a> - seems to work on FreeBSD, but still has issues on NetBSD. - </dd> - <dt>2002-02-07:</dt> - <dd> - Nathan has just <a - href="https://lists.debian.org/debian-bsd/2002/debian-bsd-200202/msg00091.html">reported</a> - that he got Debian GNU/FreeBSD to boot multiuser. Also, he's - working on a packages-only install (using a hacked debootstrap) - featuring a considerably smaller tarball. - </dd> - <dt>2002-02-06:</dt> - <dd> - According to Joel gcc-2.95.4 passed most of its test-suite and - is packaged. - </dd> - <dt>2002-02-06:</dt> - <dd>X11 works on NetBSD! Again, kudos to Joel Baker - </dd> - <dt>2002-02-04:</dt> - <dd>First step towards a Debian/*BSD archive: <br /> - <a href="mailto:lucifer@lightbearer.com">Joel Baker</a> - <a href="https://lists.debian.org/debian-bsd/2002/debian-bsd-200202/msg00067.html"> - announced</a> a <kbd>dupload</kbd>able archive for FreeBSD and - NetBSD Debian packages. - </dd> - <dt>2002-02-03:</dt> - <dd>Debian GNU/NetBSD now - <a href="https://lists.debian.org/debian-bsd/2002/debian-bsd-200202/msg00043.html"> - self-hosting</a>! Note that it still needs a working NetBSD for - installation. - </dd> - <dt>2002-01-30:</dt> - <dd>The Debian GNU/*BSD port now has a webpage!</dd> -</dl> - -<h2>Why Debian GNU/NetBSD?</h2> - -<ul> -<li>NetBSD runs on hardware unsupported by Linux. Porting Debian to -the NetBSD kernel increases the number of platforms that can run a -Debian-based operating system.</li> - -<li>The Debian GNU/Hurd project demonstrates that Debian is not tied -to one specific kernel. However, the Hurd kernel was still relatively -immature - a Debian GNU/NetBSD system would be usable at a production -level.</li> - -<li>Lessons learned from the porting of Debian to NetBSD can be used -in porting Debian to other kernels (such as those of <a -href="https://www.freebsd.org/">FreeBSD</a> and <a -href="https://www.openbsd.org/">OpenBSD</a>).</li> - -<li>In contrast to projects like <a href="https://www.finkproject.org/">Fink</a>, -Debian GNU/NetBSD did not exist in order to provide extra software or a -Unix-style environment to an existing OS (the *BSD ports trees are already -comprehensive, and they unarguably provide a Unix-style environment). -Instead, a user or administrator used to a more traditional Debian system -would feel comfortable with a Debian GNU/NetBSD system immediately and -competent in a relatively short period of time.</li> - -<li>Not everybody likes the *BSD ports tree or the *BSD userland (this -is a personal preference thing, rather than any sort of comment on -quality). Linux distributions have been produced which provide *BSD -style ports or a *BSD style userland for those who like the BSD user -environment but also wish to use the Linux kernel - Debian GNU/NetBSD -is the logical reverse of this, allowing people who like the GNU -userland or a Linux-style packaging system to use the NetBSD -kernel.</li> - -<li>Because we can.</li> -</ul> - -<h2> -Resources -</h2> - -<p> -There is a Debian GNU/*BSD mailing list. Most of the historic discussions -about this port happened there, which are accessible from the web archives at -<url "https://lists.debian.org/debian-bsd/" />. -</p> - -## Local variables: -## sgml-default-doctype-name: "HTML" -## End: diff --git a/greek/ports/powerpc/Makefile b/greek/ports/powerpc/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/powerpc/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/powerpc/devel.wml b/greek/ports/powerpc/devel.wml deleted file mode 100644 index 31f632e223d..00000000000 --- a/greek/ports/powerpc/devel.wml +++ /dev/null @@ -1,15 +0,0 @@ -#use wml::debian::template title="PowerPC Port -- Development" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::translation-check translation="b8114b588961778dbd04974c1464a2f388a90c28" maintainer="galaxico" - -<br> -<br> - -<p>For more up-to-date information on Debian PowerPC port development, please -contact us on the <a href="https://lists.debian.org/debian-powerpc/"> -debian-powerpc</a> mailing list. - -<ul> -<li> <a href="https://buildd.debian.org/stats/">The PowerPC Autobuilder Status Pages</a> -<li> <a href="https://buildd.debian.org/quinn-diff/output/unstable/by_section-powerpc/index.html">The Quinn-Diff List</a> -</ul> diff --git a/greek/ports/powerpc/docu.wml b/greek/ports/powerpc/docu.wml deleted file mode 100644 index 0e4313db058..00000000000 --- a/greek/ports/powerpc/docu.wml +++ /dev/null @@ -1,76 +0,0 @@ -#use wml::debian::template title="PowerPC Port -- Documentation" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::translation-check translation="e7b0e9e8622d110f19021682096b635ff8d35735" maintainer="galaxico" - -<h2> Documents & Information </h2> - -<h3> OpenFirmware, FirmWorks and PPCBug Documents </h3> -<ul> - <li> <a href="http://til.info.apple.com/techinfo.nsf/artnum/n60285"> OpenFirmware (Apple) </a> </li> - <li> <a href="http://www.firmworks.com/"> FirmWorks </a> </li> - <li> <a href="http://playground.sun.com/pub/1275/"> OpenFirmware (Sun) </a> </li> - <li> <a href="http://www.linuxppc.org/userguide/of.html"> OpenFirmware (Page 1) </a> </li> - <li> <a href="http://www.linuxppc.org/userguide/old_install.html#bv"> OpenFirmware (Page 2)</a> </li> - <li> <a href="http://www.linuxppc.org/userguide/output_dev.html"> Videomodes </a> </li> - <li> PPCBug -- no URL available </li> -</ul> - -<h3> General Information on Installation and Processor/Microcontroller </h3> -<ul> - <li> <a href="https://www.ibm.com/it-infrastructure/power"> IBM (RS/6000) </a> </li> - <li> <a href="http://www.dartmouth.edu/cgi-bin/cgiwrap/jonh/lppc/faq.pl?file=572"> Conversion from Red Hat/LinuxPPC to Debian/PowerPC </a> </li> - <li> <a href="http://www.mot.com/PowerPC/"> PowerPC </a> </li> - <li> <a href="http://www-3.ibm.com/chips/techlib/techlib.nsf/products/PowerPC_604e_Microprocessor"> PowerPC 604e </a> </li> -# <li> <a href="http://www.mklinux.apple.com"> MkLinux </a> </li> - <li> <a href="http://www.dartmouth.edu/cgi-bin/cgiwrap/jonh/lppc/faq.pl"> FAQ-O-Matic </a> </li> -</ul> - -<h3> Motorola Documentation </h3> -<ul> - <li> <a href="http://www.mot.com/SPS/PowerPC/teksupport/teklibrary/index.html"> Motorola Scripts (Table of Contents) </a> </li> - <li> <a href="http://www.mot.com/SPS/PowerPC/teksupport/teklibrary/manuals/pem32b.pdf"> The PEM </a> </li> - <li> <a href="http://www.mot.com/SPS/PowerPC/teksupport/teklibrary/manuals/PRG.pdf"> The PRG </a> </li> -</ul> - -<h3> ISDN Installation </h3> -<p> - The Elsa PCI ISDN card doesn't work currently. ISA cards should be fully functional. -</p> -<ul> - <li> <a href="http://www.hrz.uni-wuppertal.de/zugang/netzanschluss/isdn4l/linux_isdn-2.html"> ISDN Installation </a> </li> -</ul> - -<h3> Beowulf/Clustering </h3> -<ul> - <li> <a href="http://metalab.unc.edu/mdw/HOWTO/Parallel-Processing-HOWTO-2.html"> Parallel-Processing </a> </li> - <li> <a href="http://www.scl.ameslab.gov/Projects/ClusterCookbook/"> Cluster-Processing </a> </li> - <li> <a href="http://source.rfc822.org/pub/local/cluster/"> Pics, movies, ... </a> </li> -</ul> - -<h2>News and Other Information</h2> - -<h3> News </h3> -<ul> - <li> <a href="http://penguinppc.org/">PenguinPPC</a> </li> - <li> <a href="http://www.macosrumors.com/">Mac OS Rumors</a> </li> - <li> <a href="https://slashdot.org/">Slashdot</a> </li> -# <li> <a href="http://www.corplinux.com/powerpenguin">PowerPenguin</a> </li> -</ul> - -<h3> Info </h3> -<ul> - <li> <a href="https://www.linuxjournal.com/"> Linux Journal </a> </li> - <li> <a href="http://www.eet.com/story/OEG19990512S0025">Nintendo (1)</a> </li> - <li> <a href="http://www.chips.ibm.com/news/1999/gekko/index.html">Nintendo (2)</a> </li> - <li> <a href="http://www.opensource.apple.com/projects/darwin/">Darwin Project</a> </li> - <li> <a href="http://www.MacKiDo.com/Hardware/">The MacKiDo Info Pages (Hardware)</a> </li> - <li> <a href="http://www.maconlinux.org/">Mac-on-Linux (MOL)</a> </li> -</ul> - - - - - - - - diff --git a/greek/ports/powerpc/history.wml b/greek/ports/powerpc/history.wml deleted file mode 100644 index dcce86df2c1..00000000000 --- a/greek/ports/powerpc/history.wml +++ /dev/null @@ -1,78 +0,0 @@ -#use wml::debian::template title="PowerPC Port -- History" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::translation-check translation="70cf45edbaeb4b8fc8f99d683f2f5c5c4435be92" maintainer="galaxico" - -<br> -<br> - -<h1>Debian/PowerPC History</h1> - -<p> - The PowerPC port started in 1997 after the German <a - href="http://www.linux-kongress.org/">Linux Kongress</a> in - Würzburg where the Debian project was sponsored a <a - href="http://www.infodrom.north.de/Infodrom/tervola.html">PowerPC</a> - for development issues. -</p> - -<p> - Fortunately working boot- and rootdisks were found at <a - href="http://www.linuxppc.org/">LinuxPPC</a> and we could try to - install something on the machine. Unfortunately this required - some programs that only run under Mac OS. The only way to install - them was to get another machine running Mac OS who has them already - installed. Since data exchange with other non-Mac OS machines were - only able through msdos-formatted floppies this was a chicken-and-egg - problem. -</p> - -<p> - Somehow we managed to hook another disk to the machine and - installed Linux on it. That was Apple's famous DR 1. Suddenly we - begun to port dpkg and friends to the new system. Wow, that was - possible. It was impressive how the first packages were ported - and built. Unfortunately DR one didn't come with a dynamic linker - and shared libraries. Another problem was that the libraries and - header files seemed to be somewhat outdated and we weren't able to - compile a new libc out of the box. However, the biggest and most - serious problem were these suspicious crashes that also screwed - the file systems entirely. Fixable only by re-installations. -</p> - -<p> - Klee Dienes, another Debian Developer, worked on this problem and - suddenly came up with a <a - href="ftp://ftp.infodrom.north.de/pub/Linux/linux-pmac/debian/mklinuxfs.tar.gz">mklinux tarball</a> - of a more recent system - a haxored Debian GNU/Linux. This - tarball came with an old 1.99 version of libc. From this time the - machine run stable on the network and we could continue our - effort. We were compiling a lot of packages and noticed that some - header files were not proper and that many programs were not - compilable by the regular compiler. -</p> - -<p> - So Joel Klecker, a new Debian Developer at that time, started to - work on egcs and it's compilation on the PowerPC machine. After - this was done the next step was to work on current libc versions. - It turned out that our libc-1.99 version is incompatible to the next - pre2.1 version that was needed in order to move the port into a - stable state. -</p> - -<p> - At this stage Hartmut Koptein switched over from m68k to the powerpc - port and started development for it. Development versions of - Debian/PowerPC were available in 1998 and 1999. -</p> - -<p> - The port was officially released for the first time with Debian GNU/Linux - 2.2 ("potato"), in August 2000. -</p> - -<p> - The development of the port continues. A build daemon has been set up - on voltaire.debian.org, - a PowerPC machine donated by Daniel Jacobowitz, also a Debian developer. -</p> diff --git a/greek/ports/powerpc/index.wml b/greek/ports/powerpc/index.wml deleted file mode 100644 index 4a6e5ef85ad..00000000000 --- a/greek/ports/powerpc/index.wml +++ /dev/null @@ -1,202 +0,0 @@ -#use wml::debian::template title="PowerPC Port" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::toc -#use wml::debian::translation-check translation="bd1362b966297f3e701c0512bd20e9497fda943e" maintainer="galaxico" - -<toc-display/> - -<toc-add-entry name="about">Debian for PowerPC</toc-add-entry> - -<p> -<img src="pics/ppc750.jpg" alt="PPC-750 picture" class="rightico"> - The PowerPC is a <a href="https://en.wikipedia.org/wiki/Reduced_instruction_set_computer">\ - RISC</a> microprocessor architecture - developed by <a href="https://www.ibm.com/it-infrastructure/power">IBM</a>, - Motorola (now <a href="http://www.freescale.com/">Freescale</a>) and <a - href="https://www.apple.com/">Apple</a>. The PowerPC architecture allows both - 64-bit and 32-bit implementations (the 64-bit implementation includes - the 32-bit implementation). The first PowerPC microprocessor was the - 601, a 32-bit implementation released in 1992. Several other 32-bit - implementations have since been released, including the 603, 604, 750 - (G3), 7400 (G4) and the PowerQUICC embedded communications - processors. 64-bit implementations include the 620, POWER4, POWER5 - and the 970 (G5). -</p> - -<p> - Linux for the PowerPC was first released at the 2.2.x version of - the kernel. A key resource for PowerPC Linux development is <a - href="http://penguinppc.org/">penguinppc</a>, which also includes - a hardware compatibility list. PowerPC support in the - Linux kernel is now developed as part of the `main' Linux kernel at - <a href="https://www.kernel.org/">kernel.org</a>. -</p> - -<p> - The Debian PowerPC port began in 1997 at the <a href="http://www.linux-kongress.org/"> - German Linux Congress</a> in Würzburg. - <a href="http://www.infodrom.north.de/Infodrom/tervola.html">A - PowerPC machine</a> (Motorola StarMax 4000, 200 MHz 604e) was donated to - the Debian project. Additional information about this computer is available - from <a href="history">the history page</a>. -</p> - -<toc-add-entry name="powerpc">Debian on 32-bit PowerPC (powerpc)</toc-add-entry> - -<p> -It first became an official <q>release architecture</q> with Debian -GNU/Linux 2.2 (<q>potato</q>) and had retained that status until the publication -of Debian 9 (<q>stretch</q>). The last supported release for 32-bit PowerPC is Debian 8 (<q>jessie</q>). - -See the <a href="$(HOME)/releases/jessie/powerpc/release-notes/">\ -release note</a> and <a href="$(HOME)/releases/jessie/powerpc/">\ -installation manual</a> for further information. -</p> - -<toc-add-entry name="ppc64el">Debian on 64-bit Little Endian PowerPC (ppc64el)</toc-add-entry> -<p> -Starting on the release of Debian 8 (<q>jessie</q>), ppc64el is an officially -supported architecture on Debian. - -See the <a href="$(HOME)/releases/stable/ppc64el/release-notes/">\ -release note</a> and <a href="$(HOME)/releases/stable/ppc64el/">\ -installation manual</a>. -</p> - -<p> -Here you can find information about the -<a href="https://en.wikipedia.org/wiki/Ppc64">64-bit PowerPC</a> -<a href="https://en.wikipedia.org/wiki/Endianness">Little Endian</a> -architecture. -</p> -<p> -However, note that there is also information at the -<a href="https://wiki.debian.org/ppc64el">ppc64el wiki</a> page, such as -installation and ABI information. -</p> - -<toc-add-entry name="installation">Installation</toc-add-entry> - -<p> - There are a variety of systems using the PowerPC - microprocessor. Check our <a href="inst/install">Installation</a> pages - for specific information about installing Debian/PowerPC on your system. -</p> - - -<p> - There are some quirks you need to know about when installing on an - iBook, TiBook, or iBook2, especially when dual booting with Mac - OS X. Some iBook2 hardware, especially on recently introduced models, - is not well supported as yet. For specific information on potential - problems and solutions, study these web pages: -</p> - -<ul> -<li>William R. Sowerbutts' <a - href="http://www.sowerbutts.com/linux-mac-mini/">Installing - Debian GNU/Linux on the Mac Mini</a></li> -<li>Mij's <a href="http://mij.oltrelinux.com/ibook/ppc_linux.html">\ - Hints on installing debian on an iBook2</a></li> -<li><a href="http://seb.france.free.fr/linux/ibookG4/iBookG4-howto.html">\ - Installing Debian GNU/Linux on an iBook 3.3 (G4)</a> by Sébastien FRANÇOIS</li> -<li><a href="https://lists.debian.org/debian-powerpc/2002/07/msg00858.html">\ - Debian network installation on IBM RS/6000 44P-170 (POWER3) - HOWTO</a> by Rolf Brudeseth</li> -<li> Installing Debian GNU/Linux on a p630 LPAR (7028-6C4) - <a - href="https://web.archive.org/web/20080625231946/http://people.debian.org/~fmw/p630-LPAR-Debian-en.txt">English</a> - and <a - href="https://web.archive.org/web/20080916213451/http://people.debian.org/~fmw/p630-LPAR-Debian-de.txt">German</a> - (Florian M. Weps)</li> -<li>Daniel DeVoto's <a href="http://ppcluddite.blogspot.de/2012/03/installing-debian-linux-on-ppc-part-i.html">\ -Installing Debian Wheezy/testing on an iBook G3</a></li> -</ul> - -<p> - Debian GNU/Linux does not officially support NuBus PowerPC - machines, such as the 6100, 7100, 8100 and most of the Performa - series. However, an MkLinux-based kernel is available, which can be - launched from a Mac OS boot loader. A Debian system can be installed - using this kernel, which is available at - <url "http://nubus-pmac.sourceforge.net/">. -</p> - -<p> - When upgrading from Potato to Woody or upgrading really old kernels, - there is some <a href="keycodes">important information</a> you should - be aware of regarding a change in keyboard coding. This could save - you some time and headaches! -</p> - -<toc-add-entry name="docs">Links - Documentation</toc-add-entry> - -<p>Up-to-date information on Linux for PowerPC is at -<a href="http://penguinppc.org/">PenguinPPC</a>. -We have an <a href="docu">older collection of PowerPC links</a> and -a couple of <a href="devel">pointers</a> for Debian PowerPC developers.</p> - -<p>Hardware specifications for Apple computers are available at -<a href="https://support.apple.com/specs">AppleSpec</a>.</p> -<p> -More information and documentation about the POWER architecture: -</p> -<ul> -<li><a href="https://www-03.ibm.com/technologyconnect/tgcm/TGCMServlet.wss?alias=OpenPOWER"> -Official ELFv2 ABI Specification</a> (under section 'Link') -or this -<a href="https://www-03.ibm.com/technologyconnect/tgcm/TGCMFileServlet.wss/ABI64BitOpenPOWER_21July2014_pub.pdf?id=B81AEC1A37F5DAF185257C3E004E8845"> -PDF</a>. Registration required. </li> -<li><a href="https://gcc.gnu.org/wiki/cauldron2014#Slides_and_Notes">GNU Tools -Caldron 2014</a> slides & video</li> -</ul> - -<toc-add-entry name="availablehw">Available Hardware for Contributors</toc-add-entry> - -<p> Please read the <a href="https://db.debian.org/machines.cgi">list of -Debian machines</a> to access powerpc/ppc64el Debian porterboxen. -</p> - -<toc-add-entry name="contact">Contact information</toc-add-entry> - -<p>If you need help, try asking for help in the following places:</p> - -<h3>Mailing Lists</h3> - -<p>The Debian PowerPC mailing list is the proper place for questions, -suggestions for improvements, or just for chat concerning PowerPC -systems running Debian. The debian-user list is also available for -general Debian questions which are not specific to PowerPC.</p> - -<p>To join the list, send e-mail to -<a href="mailto:debian-powerpc-request@lists.debian.org"> -<debian-powerpc-request@lists.debian.org></a> with the word -"subscribe" in the Subject line. -<a href="https://lists.debian.org/debian-powerpc/">List archives are -available</a>.</p> - -<h3>Usenet Newsgroups</h3> - -<p>Linux for PowerPC Systems</p> -<ul> - <li><a href="news:comp.os.linux.powerpc">comp.os.linux.powerpc</a></li> -</ul> - -<p>Linux in general</p> -<ul> - <li><a href="news:comp.os.linux.misc">comp.os.linux.misc</a></li> - <li><a href="news:comp.os.linux.networking">comp.os.linux.networking</a></li> - <li><a href="news:comp.os.linux.hardware">comp.os.linux.hardware</a></li> - <li><a href="news:comp.os.linux.x">comp.os.linux.x</a></li> -</ul> - -<h3>IRC</h3> - -<p>The <code>#debian</code> channel on <code>irc.debian.org</code> is -for general topics relating to Debian, and there is the -<code>#debianppc</code> channel for topics specific to Debian on -PowerPC processors. You will almost always find someone on-line who is -happy to share information and help you with your problem.</p> - -<hr /> - -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" diff --git a/greek/ports/powerpc/inst/Makefile b/greek/ports/powerpc/inst/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/powerpc/inst/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/powerpc/inst/apus.wml b/greek/ports/powerpc/inst/apus.wml deleted file mode 100644 index 09184ca3ead..00000000000 --- a/greek/ports/powerpc/inst/apus.wml +++ /dev/null @@ -1,226 +0,0 @@ -#use wml::debian::template title="PowerPC Port (APUS)" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="a9738774706d265243f4d1b6f43b411f8536f5c8" maintainer="galaxico" - -<h1>Installing Debian GNU/Linux on a PowerPC APUS Machine</h1> - -<p> - -Apus is the "Amiga PowerUp System", and consists of an Amiga computer, -A1200, A3000 or A4000, together with one of the PowerPC/m68k -accelerator boards from the now dead company Phase5, the BlizzardPPC -or CyberStormPPC board. - -<h2>Known Problems</h2> -<p> - -There are some issues involved with bootstrap on systems which don't -use either PowerUp or WarpUp only, but some hybrid mutant of them -both. I am not very familiar with this stuff as I use plain powerup -only, so I hope someone will contribute a more complete description of -it. -<p> - -Also the SCSI controller of the CyberStormPPC is not yet supported by -Linux, so you cannot use disks attached to it. - -<h2>Partitioning from the AmigaOS side</h2> -<p> - -<code>amiga-fdisk</code> is the fdisk variant for RDB partition tables -used by the Amiga hardware. It is working, but I recommend you use the -Amiga partitioning tools to do it from AmigaOS instead. -<p> - -HDToolbox, being the official Commodore partitioning tool, should be -installed on every AmigaOS system. Just launching HDToolbox should -partition the IDE disk of the onboard IDE interface. If you want to -access the SCSI disk on your BlizzardPPC board SCSI controller, you -should use the "hdtoolbox blizzppcscsi.device" command. -<p> - -Another option is to use SCSIConfig, the partitioner from Phase5 which -is on the floppies that came with your accelerator board. -<p> - -You will need to set the partition type to custom, and provide the -following partition type IDs: -<pre> - * Linux partition: 0x4c4e5800 - * Linux swap partition: 0x53575000 -</pre> - -<h2>Bootstrap</h2> -<p> - -You will find the <code>bootstrap</code> program in the -<code>apus/bootstrap</code> directory of the powerpc boot floppies -distribution (found at /debian/dists/woody/main/disks-powerpc/current). -<p> - -The <code>bootstrap</code> program consists of three programs. All -three need to be executable and in your AmigaOS path. They are the -<code>bootstrap</code> executable and the ppcboot_wup or ppcboot_pup -part, that is the actual launcher (ppcboot_pup for the powerup system -and ppcboot_wup for the warpup system). -<p> - -You will launch <code>bootstrap</code> with a line like this: -<pre> -\# bootstrap --apus "kernel options" -</pre> -where "kernel options" are defined in the following sections. -<p> - -<code>bootstrap</code> will then give some output, then blank the -screen for 10 to 30 seconds, and then you will have the Linux console. - -<h3>The Debian <code>bootstrap</code> Command</h3> -<p> - -The actual <code>bootstrap</code> command to launch the Debian -installer system would be: -<pre> -\# bootstrap --apus -k apus/linux -r apus/images-1.44/root.bin root=/dev/ram -</pre> -After installation, to launch Debian, use: -<pre> -\# bootstrap --apus -k apus/linux root=/dev/sda3 -</pre> -where sda3 is my Debian root partition, change it to the partition -that is hosting your root partition. - - -<h2>Kernel Options</h2> -<p> -You will need to add some kernel options depending on your actual -configuration, which will be explained in the following sections. - -<h3>Graphic Card Options</h3> -<p> - -The graphic device to be used is an option prefaced with video=. Some -examples are shown below. To enable the native graphics in vga mode -(640x480): -<pre> - video=amifb:vga -</pre> -To enable the Bvision/CyberVision graphic card in 1152x864 at 60Hz mode, -with the SUN12x22 fonts: -<pre> - video=pm2fb:mode:1152x864-60,font:SUN12x22 -</pre> - -To disable one of the graphic devices: -<pre> - video=amifb:disable -</pre> -You can map virtual consoles to the different devices being used. Use -<tt> - video=map:01 -</tt> -to map virtual console (vc) 1 to device 0, vc 2 to device 1, and after -that repeat the same pattern (vc3 to device 0, vc4 to device 1, etc.). -To map vc 1,2,3,5,6,7 to device 0 and vc 4,8 to device 1 you would use -<pre> - video=map:0001 -</pre> - - -<h3>The nobats Option</h3> -<p> - -Blizzard users with scsi disks will need to use the "nobats" option. -<pre> -\# bootstrap --apus -k apus/linux root=/dev/sda3 nobats -</pre> - -<h3>The 60nsram Option</h3> -<p> -People with 60ns ram can also use the 60nsram option. -<pre> -\# bootstrap --apus -k apus/linux root=/dev/sda3 60nsram -</pre> - -<h3>Debugging Options</h3> -<p> -If you are experiencing problems, you can use the debug option to -specify console message output to go to a serial console or memory -instead of the normal console. This is useful for debugging when the -kernel output doesn't come to the console output. -<pre> -\# bootstrap --apus -k apus/linux root=/dev/sda3 60nsram debug=mem -</pre> -Then you can read the result with the bootmesg utility from the apus/bootstrap -directory. -<p> - -Another useful tool is the dmesg utility which will give you the bootstrap -process debugging info. - -<h2>Apus Particularities in <code>dbootstrap</code></h2> -<p> - -There are some specific differences for apus in the use of -<code>dbootstrap</code>. - -<h3>Partitioning the Hard Disk - <code>amiga-fdisk</code></h3> -<p> - -The apus subarch uses the <code>amiga-fdisk</code> partitioning tool. As noted -above, you can also use AmigaOS-side partitioning tools. - -<h3>Installing the OS Kernel and Modules</h3> -<p> - -This option is actually not working. I am in the process of proposing -an "Install the OS Modules" option to replace it, but in the meantime -you can just skip this step. The kernel is not needed anyway, since it -resides on the -# <!-- FIXME Sven?? server? network? --> - -<h3>Options Not Applicable for apus</h3> -<p> - -Well some options simply don't make sense on apus, so until I exclude them -from the menu, just ignore them. They should not work anyway. - -<p> -These options are: -<pre> -* Make System Bootable directly from the Hard Disk. - -* Make a Boot Floppy. - -* Eject the Floppy. -</pre> - -<h2>Links for Further Information</h2> -<p> - -The official Linux-apus doc and FAQ is at: -<p> -<a href="http://sourceforge.net/projects/linux-apus/"> -http://sourceforge.net/projects/linux-apus/</a> -<p> - -Another source of valuable information is the Linux-m68k web site and faq -found at: - -<p> -<a href="http://sourceforge.net/projects/linux-m68k/"> -http://sourceforge.net/projects/linux-m68k/</a> -<p> - -There you will find lots of information regarding Linux on the amiga platform -that is common to Linux-m68k and Linux-apus. - -<h2>Conclusion</h2> -<p> - -Well, this little guide tries to explain all the particularities of the -Linux-apus installation of Debian. The rest of it is quite similar to any -other Debian/powerpc installation, as well as the generic Debian installation. -You will thus find further info in the <a href="$(DOC)/">Debian documentation -directory</a> as well as in the other generic Linux information sites and -docs. diff --git a/greek/ports/powerpc/inst/chrp.wml b/greek/ports/powerpc/inst/chrp.wml deleted file mode 100644 index 41ea689d7ba..00000000000 --- a/greek/ports/powerpc/inst/chrp.wml +++ /dev/null @@ -1,23 +0,0 @@ -#use wml::debian::template title="PowerPC Port (CHRP)" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="cf494cce15b1c5c14c9d7c7f2f6226e11abb143a" maintainer="galaxico" - -<h1 class="center">Debian GNU/Linux PowerPC CHRP Page</h1> - -<h2>Download</h2> - -To install Debian GNU/Linux 3.0 on a CHRP system download the following files:<br> -<br> -<ul> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/linux.bin">linux.bin</a></li> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/rescue.bin">rescue.bin</a></li> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/driver-1.bin">driver-1.bin</a></li> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/current/chrp/images-1.44/driver-2.bin">driver-2.bin</a></li> -<li><a href="http://http.us.debian.org/debian/dists/woody/main/disks-powerpc/base-images-current/basedebs.tar">basedebs.tar</a></li> -</ul> - -<h2>Useful links</h2> - -<ul> -<li><a href="http://users.telenet.be/geertu/Linux/PPC/">CHRP System from Geert Uytterhoeven</a></li> -</ul> diff --git a/greek/ports/powerpc/inst/install.wml b/greek/ports/powerpc/inst/install.wml deleted file mode 100644 index 7a32dc2fdfc..00000000000 --- a/greek/ports/powerpc/inst/install.wml +++ /dev/null @@ -1,220 +0,0 @@ -#use wml::debian::template title="PowerPC Port -- Install " NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="70cf45edbaeb4b8fc8f99d683f2f5c5c4435be92" maintainer="galaxico" - -<h2> Debian GNU/Linux installation on PowerPC machines </h2> -<p> - Check the following pages for specific information about - installing Debian/PowerPC on your system: -</p> -<ul> - <li> <a href="apus">Amiga PowerUP System</a> </li> - <li> <a href="chrp">CHRP</a> </li> - <li> <a href="prep">PReP</a> </li> - <li> <a href="pmac">PowerMac</a> </li> -</ul> - <p> -There are four major supported <em>powerpc</em> flavors: -PMac (Power-Macintosh), Apus, CHRP and PReP machines. Ports to other -<em>powerpc</em> architectures, such as the Be-Box and MBX -architecture, are underway but not yet supported by Debian. We may -have a 64bit port in the future. - -<p> -There are also four flavours of the powerpc kernel in Debian. These -are based on the specific CPU type in use (and should not be confused -with the architecture flavours discussed above):</p> - -<div><dl> - -<dt>powerpc</dt> - -<dd><p> -Most systems use this kernel flavour, which supports the PowerPC 601, -603, 604, 740, 750, and 7400 processors. All Apple Power Macintosh -systems up to and including the G4 use processors supported by this -kernel.</p></dd> - -<dt>power3</dt> - -<dd><p> -The POWER3 processor is used in older IBM 64-bit server systems: known -models include the IntelliStation POWER Model 265, the pSeries 610 and -640, and the RS/6000 7044-170, 7043-260, and 7044-270.</p></dd> - -<dt>power4</dt> - -<dd><p> -The POWER4 processor is used in more recent IBM 64-bit server systems: -known models include the pSeries 615, 630, 650, 655, 670, and 690. -The Apple G5 is also based on the POWER4 architecture, and uses this -kernel flavour.</p></dd> - -<dt>apus</dt> - -<dd><p> -This kernel flavour supports the Amiga Power-UP System. -</p></dd> - -</dl></div> - - <p> -Apple (and briefly a few other manufacturers - Power Computing, for -example) makes a series of Macintosh computers based on the PowerPC -processor. For purposes of architecture support, they are categorized -as Nubus, OldWorld PCI, and NewWorld. - <p> -Nubus systems are not currently supported by debian/powerpc. The -monolithic Linux/PPC kernel architecture does not have support for -these machines; instead, one must use the MkLinux Mach microkernel, -which Debian does not yet support. These include the 6100/7100/8100 -line of Power Macintoshes. - <p> -OldWorld systems are most Power Macintoshes with a floppy drive and a -PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are -OldWorld machines. The beige colored G3 systems are also OldWorld. - <p> -The so called NewWorld PowerMacs are any PowerMacs in translucent -colored plastic cases, all iMacs, iBooks, G4 and G5 systems. The -NewWorld PowerMacs are also known for using the `ROM in RAM' system -for Mac OS, and were manufactured from mid-1998 onwards. - -<p>Here is a list of powerpc machines which should work with Debian.</p> - -<table class="reltable"> -<colgroup span="2"> -<tr> - <th><strong>Model Name/Number</strong></th> - <th><strong>Architecture</strong></th> -</tr> -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Apple</strong></td> - <td></td> -</tr> - -<tr class="even"><td>iMac Bondi Blue, 5 Flavors, Slot Loading</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iMac Summer 2000, Early 2001</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iMac G5</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iBook, iBook SE, iBook Dual USB</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iBook2</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>iBook G4</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh Blue and White (B&W) G3</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh G4 PCI, AGP, Cube</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh G4 Gigabit Ethernet</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh G4 Digital Audio, Quicksilver</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Power Macintosh G5</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>PowerBook G3 FireWire Pismo (2000)</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>PowerBook G3 Lombard (1999)</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>PowerBook G4 Titanium</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>PowerBook G4 Aluminum</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Mac mini</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td>Xserve G5</td> <td><a href="pmac">powermac-NewWorld</a></td></tr> -<tr class="even"><td colspan="2"></td></tr> - -<tr class="even"><td>Performa 4400, 54xx, 5500</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Performa 6300, 6360, 6400, 6500</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh 4400, 5400</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh 7200, 7300, 7500, 7600</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh 8200, 8500, 8600</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh 9500, 9600</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh (Beige) G3 Minitower</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Power Macintosh (Beige) Desktop, All-in-One</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>PowerBook 2400, 3400, 3500</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>PowerBook G3 Wallstreet (1998)</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Twentieth Anniversary Macintosh</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Workgroup Server 7250, 8550, 9650, G3</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Power Computing</strong></td> - <td></td> -</tr> - -<tr class="even"><td>PowerBase, PowerTower / Pro, PowerWave</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>PowerCenter / Pro, PowerCurve</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>UMAX</strong></td> - <td></td> -</tr> - -<tr class="even"><td>C500, C600, J700, S900</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>APS</strong></td> - <td></td> -</tr> - -<tr class="even"><td>APS Tech M*Power 604e/2000</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Motorola</strong></td> - <td></td> -</tr> - -<tr class="even"><td>Starmax 3000, 4000, 5000, 5500</td> <td><a href="pmac">powermac-OldWorld</a></td></tr> -<tr class="even"><td>Firepower, PowerStack Series E, PowerStack II</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>MPC 7xx, 8xx</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>MTX, MTX+</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>MVME2300(SC)/24xx/26xx/27xx/36xx/46xx</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>MCP(N)750</td> <td><a href="prep">PReP</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>IBM RS/6000</strong></td> - <td></td> -</tr> - -<tr class="even"><td>40P, 43P</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>Power 830/850/860 (6070, 6050)</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>6015, 6030, 7025, 7043</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>p640</td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>B50, 43-P150, 44P</td> <td><a href="chrp">CHRP</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Genesi</strong></td> - <td></td> -</tr> - -<tr class="even"><td>Pegasos I, Pegasos II</td> <td><a href="chrp">CHRP</a></td></tr> - -<tr class="even"><td colspan="2"></td></tr> -<tr class="odd"> - <td><strong>Amiga Power-UP Systems (APUS)</strong></td> - <td></td> -</tr> - -<tr class="even"><td>A1200, A3000, A4000</td> <td><a href="apus">APUS</a></td></tr> -</table> -<p> -Here is a list of machines which are not known to work with -Debian. They may well work, and we'd like to hear if you test one and -have some success. -</p> -<table class="reltable"> -<colgroup span="2"> -<tr> - <th><strong>Model Name/Number</strong></th> - <th><strong>Architecture</strong></th> -</tr> -<tr class="even"><td>IBM Longtrail II, First 'free' or 'open' PowerPC Board</td> <td><a href="chrp">CHRP</a></td></tr> -<tr class="even"><td>7248-100,7248-120,7248-132 </td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>Notebook Thinkpad 820: 7247-821/822/823 </td> <td><a href="prep">PReP</a></td></tr> -<tr class="even"><td>Notebook Thinkpad 850: 7247-851/860 </td> <td><a href="prep">PReP</a></td></tr> -</table> - - - - - - - - - - - diff --git a/greek/ports/powerpc/inst/pmac.wml b/greek/ports/powerpc/inst/pmac.wml deleted file mode 100644 index 7725f0b64e9..00000000000 --- a/greek/ports/powerpc/inst/pmac.wml +++ /dev/null @@ -1,91 +0,0 @@ -#use wml::debian::template title="PowerPC Port (PowerMac)" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="b5617866ae4047b55b0439a5c5796df65590cec3" maintainer="galaxico" - -<h1 class="center">Debian GNU/Linux PowerPC PowerMac Page</h1> - -<p> -Here are some highlights of the PowerMac installation of Debian. For -detailed instructions, please study -<a href="$(HOME)/releases/stable/powerpc/">the fine Installation -Manual</a>. The -Debian Installer team have spent many long hours attempting to answer -your questions in advance and give you excellent written guidance as -you install Debian. -</p> - -<p> -It is certainly possible, and there are actually quite elegant -solutions for the NewWorld Macs, to dual boot your Debian PowerMac -system with Mac OS and/or Mac OS X. If you are planning on doing a new -installation of Mac OS X, though, do it before installing Debian. The -Mac OS X installer is very unkind to existing systems when it -installs. Shortly, you may also have the option of running Debian -within a Darwin system. -</p> - -<p> -The Debian installation uses a 2.6 series kernel. This kernel should -support most PowerMac hardware. A 2.4 series powerpc flavour kernel is -available for users with externally supplied modules that have not -been ported to 2.6 kernels. However, the use of this kernel is -strongly discouraged. -</p> - -<p> -You will need to partition your disk; Linux must be installed on its -own partition(s). If you have a single-disk system, that will entail -backing up everything on your system and restoring it after -partitioning is complete. Some third-party partitioning tools may be -able to 'shrink' a partition so you have room for more partitions on -your disk without destroying what's already there, but they will -undoubtedly advise a backup also. Drive Setup does not offer that -option, it erases the entire drive. -</p> - -<p> -1 GB is probably enough space for an experimental Linux system. You can -get by with less, perhaps as little as 400 MB for a really basic system, -but you'll more than likely want more than just the basics. -</p> - -<p> -After partitioning your disk, you will need to obtain an installation -CD or download the installer system. Once you finally sit down to do -the installation (preferably with installation manual in hand), you -will probably burn up 2 or 3 hours making it happen. An experienced -installer can get a basic install done in under half an hour. -</p> - -<p> -If you're really uncomfortable with command lines, then install the X -desktop after you've finished the basic system install. But give it a -second thought, too: there's a world of power in the Linux command -line. Some things that are very difficult to do in a graphical -interface are very fast and efficient on the command line. Also, since -the Linux system is command-line based, there are some functions which -are only accessible from the command line. The default system sets up -6 command line consoles, and one graphical one. You can get a lot of -work done in those other consoles while you're browsing the web... and -that way you can have the best of both worlds. -</p> - -<p> -The PowerPC platform runs really well with Linux. It's highly -respected in much of the Linux world. Enjoy, and remember to give -something back! -</p> - -<p> -For help with Quik on OldWorld Macs, see -<a href="http://penguinppc.org/bootloaders/quik/">\ -http://penguinppc.org/bootloaders/quik/</a> -</p> - -<p> -For detailed information on the various Mac models and in particular -info on working with OpenFirmware with any given model, check out the -<a href="http://www.netbsd.org/Ports/macppc/models.html">NetBSD -PowerPC Model list</a>. Since their installation requires one to get -OpenFirmware up first, they're the experts on that angle. -</p> diff --git a/greek/ports/powerpc/inst/prep.wml b/greek/ports/powerpc/inst/prep.wml deleted file mode 100644 index a040fb5f66b..00000000000 --- a/greek/ports/powerpc/inst/prep.wml +++ /dev/null @@ -1,209 +0,0 @@ -#use wml::debian::template title="PowerPC Port (PReP)" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/powerpc/inst/menu.inc" -#use wml::debian::translation-check translation="baca2cc9eb45158bf723feec7aa48e19ee745253" maintainer="galaxico" - -<h1>Debian GNU/Linux PowerPC PReP Page</h1> - -<h3>Intro</h3> -<p> - - IBM and Motorola both make or have made PReP architecture - machines. At this point, the PReP support has only been tested on - Motorola legacy PowerStack(tm) (Blackhawk, Comet, Utah motherboard) - systems and the current embedded solution in the PowerPlus(tm) - family. These include the MTX, MTX+, - MVME2300(sc)/2400/2600/2700/3600/4600, and MCP(n)750. IBM produces a - variety of desktop workstation that are PowerPC PReP compliant. These - include the RS/6000 40P, 43P, 830, 850, 860, 6015, and 6030. - -</p> - -<h3>Known Problems</h3> -<p> -MTX+ (7 PCI slot MTX system) cannot boot the 2.2 kernel, it hangs on the IDE -driver initialization. This is a known problem and will be fixed in an -upcoming kernel patch. -</p> -<p> -All Motorola PowerPlus systems have broken IDE support in the kernel. -This problem has been identified and fixed. Changes will soon be available -as a Debian kernel patch package and will be rolled into the kernel -source. -</p> - -<h3>Firmware</h3> -<p> - -Depending on the age and/or maker of your PReP system you will have -either PPCBUG (Motorola), Open Firmware (IBM or Motorola), or IBM's -PReP firmware. The boot commands are slightly different but all of -these systems implement the PReP standard so the same kernel can be -booted on all platforms. A complete explanation of firmware commands -is out of the scope of this document but some information will be -provided where necessary. - -</p> - -<h3>Setup for Installation</h3> - -<h4>Floppy Based Install</h4> - -<p> -Write the <code>boot1440.bin</code>, <code>root1440.bin</code>, -<code>resc1440.bin</code>, <code>drv14-*.bin</code>, and -images to floppy disks. <code>dd</code> can -be used on a Linux/Unix system or <code>rawrite</code> can be used on -a DOS/Windows system. -</p> - -<h4>Network Based Install</H4> -<p> - -Place <code>resc1440.bin</code> and <code>drivers.tgz</code> files -into an exported NFS filesystem on your NFS server. It is best to -place the files as follows: -<code>/[mountpoint]/debian/[installfiles]</code> . -</p> - -<p> -Place the <code>boot.bin</code> file in the tftp directory on your TFTP server. -</p> - -<h4>Console Options</h4> -<p> -On Motorola PPCBUG systems you may boot and install using - either VGA console or serial console. PPCBUG and Linux will fall back to serial console - mode if no VGA or keyboard is detected. -</p> - -<p> -In order to properly view the installation on a serial console, some -terminal emulation capabilities are necessary. In order to see the -installation in color, it is necessary to have a terminal emulator with -support for ANSI color. The standard color xterm included with most -Linux distribution is sufficient, as are most terminal programs on -Windows (for example, <a -href="http://www.chiark.greenend.org.uk/~sgtatham/putty/">PuTTY</a>). -In order to view the line drawing characters -that make the GUI boxes, it is essential that a font containing the IBM -extended line art character be used. Under Linux, the "linux8x8" font -can be used and under Windows one can select the MSLineDraw font. -</p> - - -<h3>Booting</h3> -<dl> -<dt> PPCBUG -<dd> Use the "ENV" command and turn on the "Network PReP boot enable" option. -<dd> Use the "NIOT" command to configure the client, server, and optional gateway IP addr - that will be used to tftp the kernel. If it is a brand new board, be sure to - <tt>SET <var><date/time></var></tt> to start the hwclock or networking and other things will not function. -<dt> Boot the image with -<dd> PPCBUG>NBO 0 0 ,,, bootprep.bin -<dt> OpenFirmware -<dt> Use the following command to tftp boot a PReP image: -<dd> >boot ‹server_ipaddr›,‹file›,‹client_ipaddr› -</dl> - - - -<h2>Debian Installation</h2> -<ol> -<li> Configure the keyboard -<p> - If on serial console, the configure keyboard step is skipped. -</p> - -<li> Partition the Harddrive -<p> -Create a primary partition of 2MB and change its type to PPC PReP boot -(type 41). OF PReP machines may have trouble booting if the PPC PReP boot -partition is anywhere other than primary partition 1. Although all the -Motorola PPCBUG systems can have PPC PReP boot located on any primary -partition, it is general practice to make the PPC PReP boot partition on -sda1 or hda1. -</p> -<p> -After the PPC PReP boot partition is created, follow the normal Linux -conventions for partitioning. At least a root and swap partition should -be created and they may be on either primary or logical partitions. -</p> - -<li> Install Rescue and Driver disks -<p> -Installing from floppy is straightforward, insert the rescue and driver -disks as you are prompted for them. -</p> -<p> -For a network based install, choose the NFS option and you will be -prompted to configure networking. When it prompts for the NFS server -to utilize, enter the NFS server and directory that you set up -earlier. Choose the defaults for the rest of the questions. -</p> - -<li> Configure Driver modules -<p> - For now, important modules are built in the kernel so just choose "Exit". -</p> - -<li> Install Base System -<p> -If a floppy install is selected, simply insert the base disks as requested. -If NFS install is selected, enter the NFS server and directory in -which the base system is located and choose the defaults to install -the Debian base system. -</p> - -<li> Make Bootable from Harddrive -<p> -Makes the system bootable from the PPC PReP boot partition that was -created earlier. If that partition is missing, an error will be displayed. -</p> - -<li> Make Boot Floppy -<p> -Writes a bootable image to a disk in the floppy drive. -</p> - -</ol> - -<h2>Debian Base System Boot</h2> -<p> - If you configured a type 41 PReP boot partition and had the installation - program make the system bootable from the hard drive then you can simply - issue a firmware boot command to have it boot from hard disk (PPCBUG and - OF both have autoboot options you may also turn on). -</p> -<p> -Note: to force the kernel to root from the correct partition, it may be -necessary to write to the PReP Global Environment variable, "bootargs". -In the case of a Motorola PReP installation which will default to root from -sda1 and where the root filesystem is actually on sda2, one must set -<tt>bootargs=/dev/sda2</tt> . -</p> - -<p>PPCBUG</p> - -<dl> -<dt>Set the bootargs parameter -<dd>PPCBUG>GEVEDIT bootargs -<dd>PPCBUG>bootargs=root=/dev/sda2 -<dt>Perform a boot (assumes SCSI disk on controller 0, SCSI ID 0): -<dd>PPCBUG>PBOOT 0 -<dt>Perform a boot (assumes SCSI disk on controller 0, SCSI ID x) -<dd>PPCBUG>PBOOT 0 x0 -</dl> -<dl> -<dt>Openfirmware -<dt>Perform a boot (for installed IDE/SCSI disk aliased to disk0) -<dd>>boot disk0 -<dt>Perform a boot (for installed IDE/SCSI disk aliased to hdisk0) -<dd>>boot hdisk0 -</dl> -<p> - Now the kernel boots from the hard disk. -</p> - -<hr> -Please email with any suggestions/complaints/problems with the installation -on PReP and this documentation to <a href="mailto:porter@debian.org">Matt Porter</a> diff --git a/greek/ports/powerpc/keycodes.wml b/greek/ports/powerpc/keycodes.wml deleted file mode 100644 index ad58a37fcad..00000000000 --- a/greek/ports/powerpc/keycodes.wml +++ /dev/null @@ -1,224 +0,0 @@ -#use wml::debian::template title="PowerPC Keycodes Change" NOHEADER="yes" -#use wml::fmt::verbatim -#include "$(ENGLISHDIR)/ports/powerpc/menu.inc" -#use wml::debian::translation-check translation="0cfff43768945b514bb734757927bbbd8b043626" maintainer="galaxico" - - -<h2>PowerPC Linux Keycodes Alert!</h2> -<p> -If you're running a kernel built previous to around April 2001, and -are considering an upgrade to woody, a kernel upgrade, or a keymap -change, it's ESSENTIAL you be aware of the Debian keycodes change for -PowerPC in woody.</p> -<p> -Here's what happened: to pull powerpc into the linux mainstream and -eliminate present and future conflicts, woody's console-data package -was changed to present linux keycode maps for installation instead of -ADB keycode maps (which used to be the norm for powerpc kernels). The -ADB keycode maps are no longer officially Debian supported.</p> -<p> -The installation system's kernel was changed to follow that path, so -the new installation kernel uses linux keycodes, not ADB -keycodes. That is a permanent change; a kernel compiled without -support for ADB keycodes is unable to use ADB keymaps. Linux keycodes -are a feature of the `New Input Layer' which is set to become the -standard for all input devices on all architectures during the -post-2.4 kernel version cycle.</p> -<p> -If you would rather stay with ADB keycodes for the time being, and the -kernel you want to use has been compiled with -CONFIG_MAC_ADBKEYCODES=n, you can re-compile it with -CONFIG_MAC_ADBKEYCODES=y and continue to use an ADB keymap.</p> -<p> -The mac/apple keyboard maps for ADB keycodes vs. linux keycodes are very -different. That's why you must be prepared. If you don't coordinate -your boot instructions, your kernel, and your keymap, you may someday -type 'root' and the login prompt and instead see 'sswj'. A very -disconcerting circumstance.</p> - - -<h2>Planning Ahead</h2> -<p> -A very common circumstance for this to come up is upgrading from -potato to woody. In that case, a special dialog has been incorporated -when console-data is upgraded. A check is made of the kernel you're -running when the upgrade takes place, and if you are running an ADB -kernel, you are warned about the situation and asked to make a choice.</p> -<p> -Since you already know everything about the issue, it will be an easy -choice. Put in a new boottime keymap, then after the upgrade is -complete (BEFORE rebooting), modify your boot configuration (quik.conf -or yaboot.conf) to add a line as follows to the kernel image section -you are booting:</p> -<pre> -append="keyboard_sends_linux_keycodes=1" -</pre> -<p> -If you already have an append= line, add the new term inside the -quotes like</p> -<pre> -append="video=ofonly keyboard_sends_linux_keycodes=1" -</pre> -<p> -Don't forget to run quik or ybin after your editing is complete, to -save the config changes to the real bootloader files.</p> -<p> -Another instance where this issue can come up is when upgrading X from -4.0.x to 4.1.x with an ADB keycodes kernel. Your XF86Config-4 probably -has XkbModel set to "macintosh", but the meaning of that changed so -that a macintosh keyboard is assumed to use the new Linux keycodes. If -you are staying with ADB keycodes, you'll need to change the XkbModel -to "macintosh_old". </p> - -<h2>New Woody Installations</h2> -<p> -For a new woody installation, you will have a linux-keycode keymap and -linux-keycode kernel installed for you. So they'll match, and you -won't have any problem. Unless...</p> -<p> -Unless you change the kernel after installation and it turns out to be -an ADB kernel. Then you will have the same problem in reverse. Or -unless...</p> -<p> -Unless you change the keymap manually, selecting from -/usr/share/keymaps/mac. Those are all ADB keymaps, and they won't -match your linux-keycode kernel! </p> - - -<h2>It Won't Happen To Me -- But When It Does</h2> -<p> -So, how to extract yourself when you type root and see sswj? Or in -the reverse case, type (tab)ssw and see root?</p> -<p> -Linux people hate to turn the switch off on their computers. And -there's always some filesystem corruption when you do that, which may -or may not be repaired correctly. So here are some suggestions to get -the system shut down gracefully if this happens.</p> -<p> -If you have ssh installed on your system and can connect from another -computer, you can temporarily correct the problem remotely. Login to -the root account, and execute the following:</p> - -<verbatim> -cd /proc/sys/dev/mac_hid/ -echo 0 > keyboard_lock_keycodes -echo 1 > keyboard_sends_linux_keycodes -</verbatim> - -<p> -Your keyboard will then respond normally until you reboot. Use the -opportunity to synchronize your keymap, kernel and bootloader!</p> -<p> -If your system has a key combination used as a reboot or shutdown -command, you can try to use the tables below to figure out what the -combination is and apply it. On PowerPC, a common key combo is -Control-Shift-Delete. With an ADB keymap loaded, interpreted as linux -keycodes, that would be Control-F6-F12. With a linux keycodes map -loaded, interpreted by an ADB mapped kernel, you'd need -Shift-AltGr-Equals. Good luck.</p> -<p> -My keyboard doesn't have a Delete key, so when I had a linux-keycodes -map loaded in an ADB-configured kernel, I figured out from the table -how to login as root ( 2==3 followed by F5 ). For my root -password, I used the table below. For reboot, I typed ( 21 tab-key -==3 followed by F5 ). You could also use halt ( p]j3 followed by F5 ).</p> -<p> -Some characters can't be typed in the wrong keymap. Those are blank or -missing in the tables.</p> - -<h2>Linux-keycodes keymap loaded, kernel configured for ADB</h2> - -<p> </p> - -<pre> -If you want: a b c d e f g h i j k l m n o p q r s t u v w -instead type: ] TAB m u 1 [ i p 5 Return l j ` Space = 9 y 2 o 3 6 . t - - x y z 0 1 2 3 4 5 6 7 8 9 * / [ ] , = - ` \ ; - n 4 / b d f h g z x c v Alt F7 7 - Backspace w q ; , ' - - Control Shift Enter Tab Backspace Fwd-Del Space - F6 Ctrl or \ F5, 8 r e F12 CapsLock - - Home NumLock Clear AltGr =(numkpd) Escape F11 F12 - Clear +(numkpd) F6-6 Shift Fwd-Del s kp-5 kp-6 - - F1 F2 F3 F4 F7 F9 - Left-Arrow Right-Arrow Down-Arrow Up-Arrow kp-. kp-* - - Left-Arrow Right-Arrow Up-Arrow Down-Arrow - F13 F11 -</pre> - -<h2>Kernel configured for Linux-keycodes, ADB keymap loaded</h2> - -<pre> -If you want: a b c d e f g h i j k l m n o p q r s t u v w -instead type: 0 7 1 Backspace 2 4 3 g l ' k c x s h - Tab Esc w d 8 = - - x y z 0 1 2 3 4 5 6 7 8 9 * / [ ] , = - ` ; - 6 q 5 Control e r t y i u [ Return p z f a \ o ] m ` - - Control Shift Return Tab Backspace Fwd-Del \ Space - Shift AltGr j b , =(numkpd) Shift n - - Clear AltGr =(numkpd) CapsLock Escape Alt - Home CapsLock Fwd-Del Space / kp-* - - F1 F2 F3 F4 F5 F6 F7 F8 F9 F0 F11 F12 - Enter Ctrl / Fwd-Del - - Left-Arrow Right-Arrow Up-Arrow Down-Arrow - F1 F2 F4 F3 -</pre> - - -<h2>How To Figure Out Your Current Status</h2> -<p> -The keymaps don't currently have comments inside, so if you're -wondering which kind of map is active, you can tell by peeking at the -keycode 1 line with</p> -<pre> -zgrep 'keycode *1 =' /etc/console/boottime.kmap.gz -</pre> -If keycode 1 = Escape, that's the linux (actually i386) keycodes map. -If keycode 1 = s, that's ADB (except for ADB dvorak, keycode 1 = o). -<p> -The config-XXXXX files in /boot will reveal whether the kernel you're -booting with is compiled with ADB keycode support or not. To find -out, use</p> -<pre> -grep MAC_ADB /boot/* -</pre> -<p> -You should get a list of config files for kernels you can boot. If -there's an entry like</p> -<pre> -/boot/config-2.4.12-powerpc:CONFIG_MAC_ADBKEYCODES=y -</pre> -<p>then your kernel is compiled with ADB codes support. If the last -letter is n, it's a linux-keycode kernel.</p> - -<h2>How To Fix It</h2> -<p> -Once you've got your errant system shut down, you still need to -fix it. How can you tell what is needed? You may have to use your -rescue disk or boot another partition in order to fix things up. </p> -<p> -If your problem is an ADB-compiled kernel trying to use a linux-codes -keymap, just add </p> -<pre> -keyboard_sends_linux_keycodes=1 -</pre> -<p>at the boot: prompt after typing your kernel image label. That is only -a one-boot fix, though; you need to make the change permanent by -editing your boot config file and saving it for the bootloader.</p> -<p> -If your problem is the reverse (linux-keycodes kernel trying to use an -ADB keymap), you'll need to get rid of the ADB keymap. You can copy in -any keymap from the /usr/share/keymaps/i386 folder, there are lots to -choose from. For example</p> -<pre> -cd /usr/share/keymaps/i386/qwerty/ -cp mac-usb-us.kmap.gz /etc/console/boottime.kmap.gz -</pre> diff --git a/greek/ports/s390/Makefile b/greek/ports/s390/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/s390/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/s390/index.wml b/greek/ports/s390/index.wml deleted file mode 100644 index 06a7e63c7f2..00000000000 --- a/greek/ports/s390/index.wml +++ /dev/null @@ -1,56 +0,0 @@ -#use wml::debian::template title="S/390 Port" -#use wml::debian::toc -#use wml::debian::translation-check translation="0d2ff40f3ac99634f3bb83bb7589af752e6783c5" maintainer="galaxico" - -<toc-display/> - -<toc-add-entry name="status">Status</toc-add-entry> - -<p>S/390 has been an officially supported Debian architecture since the release -of Debian 3.0 (woody).</p> - -<p>For instructions on installing Debian, see the -<a href="$(HOME)/releases/stable/s390x/">Installation Guide</a>.</p> - -<toc-add-entry name="team">S/390 porting team</toc-add-entry> - -<p> -The following people contributed to the Debian port to s390: -</p> - -<ul> - <li>Aurélien Jarno</li> - <li>Bastian Blank</li> - <li>Chu-yeon Park and Jae-hwa Park</li> - <li>Frank Kirschner</li> - <li>Frans Pop</li> - <li>Gerhard Tonn</li> - <li>Jochen Röhrig</li> - <li>Matt Zimmerman</li> - <li>Philipp Kern</li> - <li>Richard Higson</li> - <li>Stefan Gybas</li> -</ul> - -<toc-add-entry name="development">Development</toc-add-entry> - -<p>One build server and the porterbox for the <em>s390x</em> architectures are -currently hosted by <a href="https://www.itzbund.de/">Informationstechnikzentrum -Bund (ITZBund)</a>. Other build servers -are provided by <a href="http://www.iic.kit.edu">Informatics Innovation Center, -Karlsruhe Institute of Technology (KIT)</a> and <a -href="https://www.marist.edu/">Marist College</a>. We thank those hosters for -their support!</p> - -<p>In the past <a href="http://www.millenux.de/">Millenux</a> and the <a -href="https://www.ibm.com/it-infrastructure/z/os/linux-support">Linux -Community Development System</a> hosted such build machines.</p> - -<toc-add-entry name="contact">Contact information</toc-add-entry> - -<p>If you would like to help, you should subscribe to the debian-s390 -mailing list. To do this, send a message containing the word "subscribe" -as the subject to <email "debian-s390-request@lists.debian.org">, or use the -<a href="https://lists.debian.org/debian-s390/">mailing list web page</a>. -You can also browse and search the -<a href="https://lists.debian.org/debian-s390/">mailing list archive</a>.</p> diff --git a/greek/ports/sparc/Makefile b/greek/ports/sparc/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/ports/sparc/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/ports/sparc/credits.wml b/greek/ports/sparc/credits.wml deleted file mode 100644 index 8546252961b..00000000000 --- a/greek/ports/sparc/credits.wml +++ /dev/null @@ -1,46 +0,0 @@ -#use wml::debian::template title="Debian SPARC -- Credits" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/sparc/menu.inc" -#use wml::debian::translation-check translation="05db930935ccece0e86ce3e75f8029e944ca0888" maintainer="galaxico" - -<h1>Debian SPARC Credits</h1> - <p> -A selected list of people that we'd like to thank for helping with the -SPARC porting effort are: -<ul> - <li> -Johnie `netgod' Ingram who ran SPARC auto-compiles, getting the huge -majority of packages ported with no hassles (no hassles to the rest of -us, anyway ;-) - <li> -Adam Haberlach who produced a Debian SPARC page before I did, from -which I have filched some information. Adam's email address and web -site have bitten the dust -- if you're out there, Adam, contact me! - <li> -Eric Delaunay, the fearless master of the boot floppies - <li> -Steve Dunham, general hacker on the bleeding edge - <li> -Anders Hammarquist, master of X on SPARC <em>and</em> alpha - <li> -Christian Meder, who kicks us all into line on the mailing list, and -uploads packages by the dozen! - <li> -Steve McIntyre, for masterminding the CD efforts - <li> -Ben Collins, who is porting a lot of packages and working on the -autobuilder - <li> -Ward Deng, from Kachina Technologies, who has provided assistance and -hardware for porting - <li> -Jules Bean who originally set up these web pages. - </ul> - - -# <!-- Keep this comment at the end of the file -# Local variables: -# mode: sgml -# sgml-indent-data:nil -# sgml-doctype:"../../releases/.doctype" -# End: -# --> diff --git a/greek/ports/sparc/index.wml b/greek/ports/sparc/index.wml deleted file mode 100644 index c2d6c58b42c..00000000000 --- a/greek/ports/sparc/index.wml +++ /dev/null @@ -1,133 +0,0 @@ -#use wml::debian::template title="SPARC Port" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/sparc/menu.inc" -#use wml::debian::translation-check translation="f9d5abd797e762089776545824869e3e44bd2c42" maintainer="galaxico" - -<h1>Debian SPARC Port</h1> - -<ul> - <li><a href="#intro">Overview</a></li> - <li><a href="#status">Current Status</a></li> - <li><a href="#sparc64bit">About 64-bit SPARC support</a> - <ul> - <li><a href="#kernelsun4u">Compiling kernels for sun4u</a></li> - </ul></li> - <li><a href="#errata">Errata</a></li> - <li><a href="#who">Who are we? How can I help?</a></li> - <li><a href="#links">Where can I find out more information?</a></li> -</ul> - -<h2 id="intro">Overview</h2> - <p> -These pages are meant to assist users and Debian developers running -Debian GNU/Linux on the SPARC architecture. In these pages, you will -find information about the current status, currently known problems, -information for and about Debian porters, and pointers to more -information. - </p> - -<h2 id="status">Current Status</h2> - <p>Support for pre-UltraSPARC machines was dropped with the end of -service life of Debian Etch (see <a href="https://wiki.debian.org/Sparc32"> -https://wiki.debian.org/Sparc32</a>). -After that, the 32-bit port required an UltraSPARC CPU and ran a 64-bit kernel. - </p> - <p> -This 32-bit port was eventually dropped with the end of the service -life of Debian Wheezy. - </p> - <p> -Currently, there is no official Debian port for SPARC, but a full 64-bit -SPARC port called sparc64 is supported by the Debian Ports team. - </p> - -<h2 id="sparc64bit">About 64-bit SPARC support</h2> - <p> -The Debian SPARC port, -as mentioned above, does support the sun4u (<q>Ultra</q>) -and sun4v (Niagara CPU) architectures. -It uses a 64-bit kernel (compiled with gcc 3.3 or newer), but most of the -applications run in 32-bit. This is also called a <q>32-bit -userland</q>. - </p> - <p> -The Debian SPARC 64 (a.k.a., <q>UltraLinux</q>) porting effort is not -currently conceived as a full porting effort like other ports. -Rather, it is intended to be an <em>add-on</em> to the SPARC Port. - </p> - <p> -In fact, there is really no point in having all applications running -in 64-bit mode. Full 64-bit mode involves a significant overhead -(memory and disk size) with often no benefit. Some applications -really can benefit from being in 64-bit mode, and that is the purpose -of this porting effort. - </p> - -<h3 id="kernelsun4u">Compiling kernels for sun4u</h3> - <p> -To compile a Linux kernel for Sun4u, you'll need to use the Linux 2.2 -or newer source tree. - </p> - <p> -We highly suggest you also use the <tt>kernel-package</tt> package to -help with the installation and management of kernels. You can compile -a configured kernel in one command (as root): - </p> -<pre> - make-kpkg --subarch=sun4u --arch_in_name --revision=custom.1 kernel_image -</pre> - - -<h2 id="errata">Errata</h2> - <p> -Some of the common problems with fixes or workarounds can be found on our -<a href="problems">Errata page</a>. - </p> - - -<h2 id="who">Who are we? How can I help?</h2> - <p> -The Debian SPARC port is a distributed effort, just as Debian is. -Countless people have helped with the porting and documentation -efforts, although a short list of <a href="credits">credits</a> are -available. - </p> - <p> -If you'd like to help, please -join in the <debian-sparc@lists.debian.org> mailing list as -<a href="#links">described below</a>, and chime in. - </p> - <p> -Registered developers who would like to actively port and upload -ported packages should read the porter guidelines in the <a href="$(DOC)/developers-reference/">Developers -Reference</a>, and see the <a href="porting">SPARC porting page</a>. - </p> - - -<h2 id="links">Where can I find out more information?</h2> - <p> -A Debian Wiki page is dedicated about <a href="https://wiki.debian.org/Sparc64">Debian Sparc64 port</a>. - </p> - <p> -The best place to ask Debian-specific questions about the SPARC port -is on the mailing list, <a href="https://lists.debian.org/debian-sparc/">\ -<debian-sparc@lists.debian.org></a>. -Mailing list <a -href="https://lists.debian.org/debian-sparc/">archives</a> are -browsable on the web. - </p> - <p> -To subscribe to the list, send a mail to -<a href="mailto:debian-sparc-request@lists.debian.org">\ -debian-sparc-request@lists.debian.org</a>, with the word `subscribe' -in the subject line, and no body. Alternatively, subscribe on the web -with the <a href="https://lists.debian.org/debian-sparc/">Mailing List -subscription</a> page. - </p> - <p> -Kernel questions should be addressed to the list -<sparclinux@vger.rutgers.edu>. Subscribe by sending a message -with body <q>subscribe sparclinux</q> to the address <a -href="mailto:majordomo@vger.rutgers.edu">majordomo@vger.rutgers.edu</a>. -There is also a Red Hat list, of course. - </p> - diff --git a/greek/ports/sparc/porting.wml b/greek/ports/sparc/porting.wml deleted file mode 100644 index fbfb45e5781..00000000000 --- a/greek/ports/sparc/porting.wml +++ /dev/null @@ -1,67 +0,0 @@ -#use wml::debian::template title="Debian SPARC -- Porting Documentation" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/sparc/menu.inc" -#use wml::debian::translation-check translation="f9d5abd797e762089776545824869e3e44bd2c42" maintainer="galaxico" - -<h1>Debian SPARC Porting Documentation</h1> - -<h2>Porting Debian Packages to SPARC</h2> - <p> -If you want to be an official porter, you must be a registered Debian -developer. That is, your public key must appear in the official -keyring. - <p> -The Debian SPARC porting effort is now organized around the excellent -<code>wanna-build</code> system, first used for the <a -href="../m68k/">m68k</a> port. With <code>wanna-build</code> in -place, porting boils down to locating the packages where automatic -compilation failed, and then going though and determining what went -wrong. - <p> -Failed build logs can be found at -<a href="https://buildd.debian.org/status/architecture.php?a=sparc64">the SPARC 64 buildd web pages</a>. -Also, you can email <code>wanna-build</code> and ask it for the failed -build logs (see the file <code>README.mail</code> from the -<code>wanna-build</code> distribution). - <p> -Serious porters should learn how to interact with -<code>wanna-build</code> via email. You'll need to ask <a -href="mailto:bcollins@debian.org">Ben Collins -<bcollins@debian.org></a> to add your public key to the known -list of keys. - <p> -All Debian developers can use Debian's -<a href="https://db.debian.org/machines.cgi">porterbox machines</a> to -test their packages on the SPARC architecture. - - -<h2>I'm not an official developer; can I still help?</h2> - <p> -Certainly. In fact, most of the real work in a Debian port requires -not official status, just knowledge. There are a number of things you -can do: -<ul> - <li> -Track down bugs, and report them to the <a href="$(HOME)/Bugs/">Debian -Bug Tracking System</a>. - <li> -Figure out patches for known bugs. Be sure to submit the patch to the -Bug Tracking System! - <li> -Help with documentation. Most documentation areas are managed under -CVS, and most documentation authors can give out CVS access to -non-porters who are interested in helping. - </ul> - <p> -So, go ahead and email <a -href="mailto:debian-sparc@lists.debian.org"><debian-sparc@lists.debian.org></a> -with a description of how you'd like to help; we're sure someone there -can get you started. - - -# <!-- Keep this comment at the end of the file -# Local variables: -# mode: sgml -# sgml-indent-data:nil -# sgml-doctype:"../../releases/.doctype" -# End: -# --> diff --git a/greek/ports/sparc/problems.wml b/greek/ports/sparc/problems.wml deleted file mode 100644 index eb1f835637f..00000000000 --- a/greek/ports/sparc/problems.wml +++ /dev/null @@ -1,56 +0,0 @@ -#use wml::debian::template title="SPARC Port -- Errata" NOHEADER="yes" -#include "$(ENGLISHDIR)/ports/sparc/menu.inc" -#use wml::debian::translation-check translation="bc5a5b465aa5f94e13b4ed873d83cbd36b1a2f2b" maintainer="galaxico" - -<h1>Debian SPARC Errata</h1> - <p> -This page contains a list of well-known problems with Debian SPARC. -Stress is placed on the stable release (or freeze, if appropriate), -since these problems turn over much less frequently, and effect a -greater number of people. - <p> -The following list of problems do not attempt to replace the Debian -bug-tracking system (BTS). The main purpose of this information is to -reduce user confusion, reduce traffic on the mailing list, and to -explain workarounds until the bug is fixed. If there is a bug number -associated with a problem, that bug number will be noted. - - -<h2>X Window System</h2> - <p> -Problems relating to the X Window System. - -<h3>How do I know which X server to run?</h3> - <p> -This depends on your machine and which framebuffer (video card) you -have installed. The following list of X server packages should help -- pick the -one which matches your hardware and install the package (and set it -the default X server when asked during installation). -<dl> - <dt>xserver-xsun</dt> - <dd> -Used for most Sun and clone 8-bit framebuffers, such as CG3, CG6, etc. Also -includes monochrome support. - <dt>xserver-xsun-mono</dt> - <dd> -Used for BWTWO and other monochrome framebuffers, or operating color -framebuffers in monochrome mode. - <dt>xserver-xsun24</dt> - <dd> -X server supporting 24-bit color -- suitable for 24-bit framebuffers -supported by the Linux kernel. Not too many folks can use this. - <dt>xserver-mach64</dt> - <dd> -Use this X server for ATI Rage framebuffers, such as found in many -PCI-based UltraSPARC machines. - </dl> - -# <p> -# There are experimental Creator accelerated X servers somewhere to be -# found. Is that in the distribution already? - - -<h3>Issues with Mach64 Server</h3> - <p> -This server will only look for the framebuffer on <tt>/dev/fb0</tt>. -You may have to fool around with symlinks in there to fake it. diff --git a/greek/reports/Makefile b/greek/reports/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/reports/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/reports/index.wml b/greek/reports/index.wml deleted file mode 100644 index db379415d44..00000000000 --- a/greek/reports/index.wml +++ /dev/null @@ -1,18 +0,0 @@ -#use wml::debian::template title="Debian reports" BARETITLE="true" -#use wml::debian::translation-check translation="837e12c68494152286a980220c723c0686bc1bcb" maintainer="galaxico" - -<p>Debian publishes and disseminates reports or position statements on topics -related to Free Software and its distribution.</p> - -<h2>Available reports</h2> - -<ul> - -<li> The <strong><a href="patent-faq">Community Distribution Patent Policy - FAQ</a></strong>, first published in July 2011, answers frequently asked - questions about (software) patents and their effects on community-driven Free - Software distributions.<br /> This report has been prepared with the help of - the <a href="http://www.softwarefreedom.org/">Software Freedom Law - Center</a>.</li> - -</ul> diff --git a/greek/reports/patent-faq.wml b/greek/reports/patent-faq.wml deleted file mode 100644 index 01dc165ea56..00000000000 --- a/greek/reports/patent-faq.wml +++ /dev/null @@ -1,419 +0,0 @@ -#use wml::debian::template title="Community Distribution Patent Policy FAQ" BARETITLE="true" -#use wml::debian::translation-check translation="ba01cfdc529712e3626bdf15fd37d39e94126794" maintainer="galaxico" - -<pre><code>Version: 1.0 -Published: 8 July 2011 -</code></pre> - -<h1>Introduction</h1> - -<h2>For whom is this document intended?</h2> - -<p>This document presents information about patents and patent liability useful -for developers working on community distributions of Free and Open Source -Software (FOSS). By community distributions, we mean collections of free -software packages maintained and distributed by organizations composed of -volunteers, where neither the organization nor the volunteers seek to make a -profit from the activity. Such community-based distributions may sell as well -as give away their work product, possibly on CDs or USB storage media or by -paid-for downloads as well as by gratis distribution.</p> - -<p>This document has been prepared by lawyers at the <a href="http://www.softwarefreedom.org">Software Freedom Law -Center</a> (SFLC) at the request of the <a href="https://www.debian.org/">Debian -project</a>, and may be helpful to similar community FOSS -distributions. Its statements about legal matters are accurate as of the date -of composition regarding US law, and may be applicable to other legal systems. -But this document does not constitute legal advice. It has not been based on -analysis of any particular factual situation, and any lawyer providing an -opinion on the questions presented below would need to ascertain the particular -facts and circumstances that might vary this information in a particular -setting. You should not rely upon this document to make decisions affecting -your project's legal rights or responsibilities in a real-life situation -without consulting SFLC or other lawyers.</p> - -<h1>Background on Patents</h1> - -<h2>What is a patent?</h2> - -<p>A patent is a state-granted monopoly granting an inventor exclusive rights to -make, sell, offer for sale, have made, or import the claimed invention for the -limited term of the patent. The patent holder may then license, on an -exclusive or non-exclusive basis, one or more of the rights granted.</p> - -<h2>How long is a patent's term?</h2> - -<p>Generally, patents issued in the last 15 years by most governments expire 20 -years from the filing date of the patent application. US patents with a filing -date before June 8, 1995, provide protection for up to 17 years counting from -the date of grant, or 20 years from the filing date, whichever occurs later.</p> - -<p>There are exceptions. Patents may have their terms extended by the issuing -office or a court, but this rarely happens for patents on software. Patent -terms may also be shortened by agreement with the applicant during -<q>prosecution</q>, that is, during the patent office procedure leading to issuance. -If a patent's terms has been shortened during prosecution, a <q>terminal -disclaimer</q> statement will appear on the patent's front page.</p> - -<h2>How does patent protection differ from copyright protection?</h2> - -<p>A copyright owner has the right to prevent others from making unauthorized -copies of the copyrighted program, but not from independently creating a -program with the same features. Independent creation is therefore a complete -defense to an allegation of copyright infringement. In addition, <q>fair use</q> is -a defense against copyright infringement, or is a substantive limitation of -copyright, in every copyright system. Patent law lacks any fair use exemption, -so independent creation, use for research, or reverse engineering for -interoperation or educational purposes are not defenses against allegations of -patent infringement.</p> - -<h2>Is there a world-wide patent on anything?</h2> - -<p>At present, no world-wide patents exist. Outside the European Union, where -applications may be consolidated, patents generally must be applied for in each -country in which patent protection is sought.</p> - -<h2>What are patent claims?</h2> - -<p>Claims, which are the most important part of the patent, determine the actual -scope of the invention to which the patent applies. Only the claims define -what exclusive rights cover, that is, practicing the claims without license is -infringement. Reading and understanding the claims of a patent is the key to -determining if a given product or process infringes.</p> - -<p>Each claim is a single sentence. Claims begin with a <q>preamble</q> followed by one -or more <q>limitations</q>.</p> - -<p>For software to infringe a patent, the software (or system with embedded -software) must implement everything recited in one of the patent's claims. If -you do not practice one or more of the elements of a claim, then you cannot -directly infringe that claim.</p> - -<h2>What are independent claims?</h2> - -<p>A patent claim is called <q>independent</q>, if it makes no reference to any other -claim in the patent.</p> - -<h2>What are dependent claims?</h2> - -<p>Dependent claims explicitly incorporate the contents of other claims in the -patent. A dependent claim is necessarily narrower in scope than the claim on -which it depends, because it includes one or more additional limitations. In -Venn diagram terms, the area of coverage for a dependent claim is fully -contained within the coverage of the claim it references.</p> - -<h2>How are software-related patent claims written?</h2> - -<p>Software-related patent claims in recently-issued patents often take the form -of <q>system</q> or <q>apparatus</q> claims, <q>method</q> claims, and <q>computer program -product</q> or <q>computer-readable medium</q> claims. System claims recite the -elements of a system (which might include one or more computers) as a kind of -machine or static object. Method claims are algorithmic in -form. Computer-readable medium claims typically duplicate the limitations found -in corresponding system or method claims in the patent, but are intended to -cover software embodied in a storage or distribution medium. Computer-readable -medium claims are also often used when claiming inventions that focus on data -structures and user interfaces.</p> - -<h1>Infringing a patent</h1> - -<h2>What does <q>patent liability</q> mean?</h2> - -<p>Liability is a legal responsibility that is enforceable by a court. In this -document we use term <q>patent liability</q> to encompass orders that a court can -give if a party is found to infringe a patent. For example, once a party is -found to infringe, a court can order that party to pay money to the patent -holder, called <q>damages</q>, and/or an order to stop the infringing conduct, which -is called an <q>injunction</q>.</p> - -<h2>What does it mean to <q>infringe</q> a patent?</h2> - -<p>Infringing a patent means practicing one or more of its claims without license. -If someone uses, makes, sells, has made, offers for sale, or imports software -that practices every element taught by a claim in a patent, that patent is -infringed by the software.</p> - -<p>It is possible to be liable for infringement without directly infringing. -<q>Contributing to</q> or <q>inducing</q> infringement also give rise to patent -liability.</p> - -<h2>What is inducing infringement?</h2> - -<p><q>Inducing infringement</q> means actively encouraging someone else to infringe a -patent. Liability requires proving that the party charged intended to cause a -third party to infringe. Additionally, the inducer must either know the patent -exists, or strongly suspect its existence and make efforts not to know. If, -for example, documentation is written by someone with knowledge of a patent's -claims, and that documentation explains how to use the program in an infringing -fashion, the instructions might be held to induce infringement. Where a -community of volunteers maintains a software package, and associated -documentation, unless the volunteers who produce the documentation know of the -patent supposedly infringed, they cannot induce infringement.</p> - -<h2>What is contributory infringement?</h2> - -<p><q>Contributory infringement</q> means providing material assistance to the -infringement of a patent. In the context of software, this would mean -providing non-infringing software that could be combined with other software or -hardware to produce an infringing system. Contributory infringement also -requires knowledge of the patent infringed. Moreover, if the software has -substantial non-infringing uses, it is not contributory infringement to provide -it, even if it is subsequently used in an infringing combination.</p> - -<h2>What are the consequences of infringing a patent?</h2> - -<p>If a party is found to be infringing a patent, courts may order a stop to the -infringing conduct, the payment of damages for past infringement, or both. In -this document we use term <q>patent liability</q> to encompass all of these -consequences.</p> - -<h2>What is an injunction?</h2> - -<p>An injunction is a court order to a person or persons to do something or to -refrain from doing something. Violating an injunction leads to being held in -contempt of court. Injunctions may be <q>preliminary</q>, to prevent change of -state while litigation is occurring, or <q>permanent</q>, to order or prohibit -conduct as remedy at the end of a lawsuit, once liability has been found. A -preliminary injunction to prevent infringing conduct during litigation may be -issued if the court finds damages at the end of the case would be insufficient -to protect the patent holder's rights, and if success in the case is held to be -likely, and the public interest would not be harmed by the injunction. A -permanent injunction to prevent infringing conduct may result from a finding of -infringement liability.</p> - -<h2>Can injunctions be issued against FOSS distributions?</h2> - -<p>Yes. If a FOSS distribution was found to infringe someone's valid patent, a -permanent injunction against continued distribution of the infringing program -or feature might well occur.</p> - -<p>It is not likely, however, that such an injunction would prevent distribution -of the whole distro, or even of an entire package. More likely, a feature or -set of features, would have to be disabled, modified so that the software no -longer infringes, or removed entirely, in the country where the finding of -patent infringement was made.</p> - -<p>Further, designing around the patent claims at stake can prevent even a feature -or features from being removed. Once even one element of a patent claim is no -longer being practiced, as we have said, the patent claim is no longer -infringed. In US patent litigation, the crucial moment of definition occurs in -what is called a <q><em>Markman</em> hearing</q>, after which the trial court gives a -definitive ruling on what the patent claims at issue mean for the purposes of -that lawsuit. Once a <em>Markman</em> hearing has happened, and the scope of the -asserted claims have been narrowly and conclusively defined, it becomes much -easier to design around.</p> - -<h2>What are damages?</h2> - -<p>In patent law, damages are money awarded by the court to the plaintiff when the -defendant has been found liable for patent infringement. While the law provides -no maximum damages for patent infringement, it does provide a minimum--the -reasonable royalty for the use made of the invention by the -infringer. Additionally, the court may increase the damages, up to three times -the actual damages, in cases of willful infringement.</p> - -<h2>What is willful infringement?</h2> - -<p>Infringement is willful if the infringer knew of the patent, unless the -infringer had a good faith belief that the patent was invalid, or that his -conduct did not infringe. The patent holder must show all the elements of -willfulness, and in the US courts must do so at a higher standard of proof, -which is called <q>clear and convincing evidence</q>.</p> - -<h2>I had no prior knowledge of a patent, can I still be held liable?</h2> - -<p>Knowledge of a patent is not in general required if the party is charged with -direct infringement. To be found liable for inducing or contributing to -infringement, as we have said, knowledge of the patent or specific efforts to -avoid learning of the patent is required.</p> - -<p>In practice, patent holders usually request those they believe infringe to take -licenses. If the party takes the license offered, the holder gets royalties -without suing for them. If the party declines the license, the patent holder -has put them on notice, and is therefore in a position to claim intentional -infringement, which results in higher damages and the possibility of recovering -attorney's fees. It is likely but not certain that before any community-based -distribution is sued for patent infringement, it will receive at least one -letter demanding that a license be taken.</p> - -<h2>What if the infringement was accidental, inadvertent and unintentional?</h2> - -<p>An unintentional or inadvertent infringement cannot be willful, as we said -above. Nor can one contribute to or induce an infringement accidentally, as -knowledge and intention are both required. But one could be liable for direct -infringement, without knowledge or intention, by using or selling or making or -having made infringing software without more.</p> - -<h2>How do I become aware of the existence of a patent?</h2> - -<p>There are innumerable ways by which you may become aware of the existence of a -specific patent. Aside from being directly contacted by a patent holder, you -may learn about a particular patent through a web search or mailing list, or in -connection with your employment, etc. If you do become aware of a patent that -concerns you, it is best that you speak to an attorney, rather than share such -knowledge or speculation in a public forum.</p> - -<h2>What are the defenses available in a patent infringement action?</h2> - -<p>First, there may be many defenses specific to the facts and circumstances of a -particular situation, and it is the lawyer's job to spot and develop those -defenses. Some defenses are or may be present in most cases, and they include:</p> - -<p>Permission: You are not liable for infringement if you have permission to use -the claims. Such permission could be explicit. An explicit permission is -called a <q>license</q>. Permission can also be implicit: it can result from -conduct or statements by the patent holder which appeared to constitute -permission and on which you relied. (Lawyers call this <q>estoppel</q>.) It can -also result from sheer inaction by the patent holder, who can effectively -permit infringing conduct by <q>going to sleep on its rights</q>, which lawyers call -<q>laches</q>.</p> - -<p>Non-Infringement: A non-infringement determination is a showing that none of -the patent claims actually <q>read on</q> the software charged. In other words, the -software does not actually implement every element of what is recited in any -claim.</p> - -<p>Invalidity: If the patent is invalid, it cannot be infringed. Invalidity can -be shown by proving that the subject matter of the patent is outside the scope -of patent law. It can also be shown by demonstrating, under US law, that the -patent is <q>non-novel</q> or <q>obvious</q>. Under patent law, in order for a patent to -be valid, the claimed invention must have been useful, reducible to practice, -novel, and non-obvious to a <q>person having ordinary skill in the art</q> at the -time that the invention was made. An invalidity defense, therefore, shows that -the patent failed to meet one of these requirements.</p> - -<h1>The patent risk to a community distribution</h1> - -<h2>Can you provide examples of patent infringement suits against FOSS communities?</h2> - -<p>No. Fortunately, few such cases exist, and none has yet developed to final -judgment. To date, no court has ever addressed most of the issues unique to -free software distribution. We believe that this is because FOSS communities do -not have <q>deep pockets</q> from which to pay royalties, and suing individual -developers who do not have large revenues makes bad press for patent holders -without achieving any useful outcome.</p> - -<h2>We are a FOSS distribution and we don't make any money. How will we pay damages if they are awarded against us?</h2> - -<p>This question, like all other similar questions about the legal risks and -responsibilities of projects, depends very much on the details of their legal -structure and commercial relations. There is no general answer about how -projects deal with their legal risks, including the risks of damages judgments -for patent infringement or other liabilities. -<a href="http://www.softwarefreedom.org">SFLC</a>, the <a href="http://sfconservancy.org/">Software Freedom -Conservancy</a>, the <a href="http://www.apache.org/">Apache Software -Foundation</a>, the <a href="http://www.fsf.org">Free Software -Foundation</a>, <a href="https://www.spi-inc.org/">Software in the Public -Interest</a> and other organizations help projects to fit -within legal contexts and organizations that can usefully address these -questions at a general level. If your distribution or a project within your -distribution believes that it faces potential legal liability, you should -consult us or one of the other organizations named.</p> - -<h2>We are a FOSS distribution and we make money. Does that make us more susceptible to a patent infringement suit?</h2> - -<p>Anyone making revenue is a more attractive target for a patent holder to sue -than someone who makes no money out of which damages could be paid. A -community distribution that has absolutely no revenue is not an attractive -target. But even if you make a few hundred thousand dollars a year in sales, -compared to a profit-making enterprise the size of Microsoft, or even Red Hat, -you are not worth the expenses of litigation to a patent troll or other -rational plaintiff.</p> - -<h2>I have heard that distributing source code is safer than distributing object code. Is that true?</h2> - -<p>Yes. Distributing source code is probably safer than distributing binaries, -for a few reasons. First, source code, like the patent disclosures themselves, -teaches how the invention works, rather than being the invention. If source -code standing alone can infringe the patent, it is difficult to understand how -handing out photocopies of the patent itself wouldn't infringe. Second, in the -US, courts <em>may</em> find source code to be speech, as we believe they should find, -thus making source code subject to First Amendment protection. We know little -about how the Supreme Court would harmonize the patent law with First Amendment -requirements. We at SFLC have written several briefs in the Supreme Court -addressing these issues, but the Court has never reached or decided them. -Furthermore, as mentioned above, liability for patent infringement can be -imposed where one enables or encourages another to infringe a patent, but the -requirements of knowledge and intent are more strict in secondary liability -situations. Because a user must first compile the source code and install the -software in order to infringe, a court is less likely to hold the community -liable for inducing or contributing to the infringement.</p> - -<h2>As part of a community distribution project, who is most likely to get sued for patent infringement?</h2> - -<p>This is a problem for the potential patent aggressor, more than for the -distribution. A community distribution comprised by volunteers, without any -hierarchical structure of employment or supervision, cannot be sued by suing -<q>the head</q>. If infringement requires intent and knowledge or specific efforts -not to know, as it does in cases of inducing or contributing to infringement, -the individual with such intent and knowledge must probably be found and sued -in his own person. If people who write code and documentation don't read -patents, and the volunteers who develop code for a package do not maintain the -same package or a related package, the aggressor may find it difficult to sue -anybody at all.</p> - -<p>The specifics of any given situation, however, will undoubtedly be crucial. As -with all other matters of the kind, if you believe a patent is likely to be -asserted against your distribution or its volunteers, you should contact SFLC -or another lawyer immediately.</p> - -<h2>Are you suggesting that it is better for developers and contributors not to read patents? If yes, why?</h2> - -<p>Yes. Unfortunately, U.S. patent law creates disincentives for searching through -patents, even though one of the main justifications given for the patent system -is that the patent teaches the public how to practice an invention that might -otherwise be secret. <q>Willful</q> infringement subjects the infringer to enhanced -damages when they are aware of the patent and intend to infringe, and reading -patents increases the probability that subsequent infringement will be found to -be willful. Moreover, we find that developers often assume that the patents -they discover are broader in scope than they actually are, and thus such -developers become overly or needlessly worried. If, despite this, you do intend -to conduct a patent search, you should seek legal advice first.</p> - -<h2>I am outside the United States. Do I have anything to worry about?</h2> - -<p>Although most countries are members of the World Intellectual Property -Organization (WIPO) as well as signatories to the Patent Cooperation Treaty -(PCT), large corporations generally restrict their patent acquisition -activities to the <q>Big Three</q>: the US, EU, and Japan. This is considered -sufficient protection for most companies, although companies are increasingly -filing patent applications in China with the hope that patent rights will -eventually be adequately respected by the government and business -communities. In addition, large multi-national corporations in other -jurisdictions, such as Korea and Canada, will usually file patent applications -in their own countries before filing patent applications internationally. In -India, some software has been patented despite the clear statutory declaration -that software <em>per se</em> is unpatentable. SFLC in India has begun challenging -such patents.</p> - -<p>But regardless of where you work, software that infringes patents cannot be -imported into countries where those patents have issued, which means that you -must at least be concerned about the ability to reach your intended users.</p> - -<p>As always, consultation with a local lawyer is a good step if you have any -questions about your situation or liabilities.</p> - -<h2>Are there any guidelines to limit our risk of patent infringement?</h2> - -<p>Yes. This document is meant to educate about patent risk, and while it is -difficult to give advice regarding every reader's specific situation, there are -a few guidelines that may be extracted.</p> - -<ul> -<li><p>Reading patents, especially when researching how to design a contribution to -your free software project, may expose communities to liability that they -would not otherwise have.</p></li> -<li><p>Parts of a free software community that distribute source code and not object -code probably have slightly less patent risk.</p></li> -<li><p>Distributing free software commercially is probably more risky than -distributing software gratis.</p></li> -<li><p>Having the ability to remove features and packages quickly and easily from -distribution will help mitigate any damages the community could incur.</p></li> -<li><p>Patent litigation is not an amateur sport. If you are contacted by anyone -threatening to assert a patent against you, contact the Software Freedom Law -Center or another qualified attorney as soon as possible.</p></li> -</ul> - -<hr /> - -<p><strong>Acknowledgements.</strong> This document has been prepared by lawyers at SFLC, with -inputs from Stefano Zacchiroli, on behalf of the Debian Project.</p> diff --git a/greek/security/faq.wml b/greek/security/faq.wml deleted file mode 100644 index 23aaef3fa6b..00000000000 --- a/greek/security/faq.wml +++ /dev/null @@ -1,389 +0,0 @@ -#use wml::debian::template title="Debian security FAQ" -#include "$(ENGLISHDIR)/security/faq.inc" -#use wml::debian::translation-check translation="1fe91e1ee0d4350b235e726f3f93da47d0639b19" maintainer="galaxico" - -<maketoc> - -<toc-add-entry name=buthow>I received a DSA via debian-security-announce, how can I upgrade the vulnerable packages?</toc-add-entry> - -<p>A: As the DSA mail says, you should upgrade the packages affected by the - announced vulnerability. You can do this by just upgrading (after - updating the list of available packages with <tt>apt-get update</tt>) - every package in your system with <tt>apt-get upgrade</tt> or by - upgrading just a particular package, with <tt>apt-get install - <i>package</i></tt>.</p> - -<p>The announcement mail mentions the source package in which the vulnerability - was present. Therefore, you should update all the binary packages from - that source package. To check the binary packages to update, visit - <tt>https://packages.debian.org/src:<i>source-package-name</i></tt> and - click on <i>[show ... binary packages]</i> for the distribution you - are updating.</p> - -<p>It may also be necessary to restart a service or a running process. The - command <a href="https://manpages.debian.org/checkrestart"><tt>checkrestart</tt></a> - included in the package - <a href="https://packages.debian.org/debian-goodies">debian-goodies</a> - might help to find which ones.</p> - - -<toc-add-entry name=signature>The signature on your advisories does not verify correctly!</toc-add-entry> -<p>A: This is most likely a problem on your end. The - <a href="https://lists.debian.org/debian-security-announce/">\ - debian-security-announce</a> - list has a filter that only allows messages with a correct signature - from one of the security team members to be posted.</p> - -<p>Most likely some piece of mail software on your end slightly changes - the message that breaks the signature. Make sure your software does - not do any MIME encoding or decoding, or tab/space conversions.</p> - -<p>Known culprits are fetchmail (with the mimedecode option enabled), - formail (from procmail 3.14 only) and evolution.</p> - -<toc-add-entry name="handling">How is security handled in Debian?</toc-add-entry> -<p>A: Once the security team receives a notification of an incident, - one or more members review it and consider its impact on the stable - release of Debian (i.e. if it's vulnerable or not). - If our system is vulnerable, we work on a fix for the - problem. The package maintainer is contacted as well, if they didn't - contact the security team already. Finally, the fix is tested and - new packages are prepared, which are then compiled on all stable - architectures and uploaded afterwards. After all of that is done, - an advisory is published.</p> - -<toc-add-entry name=oldversion>Why are you fiddling with an old version of that package?</toc-add-entry> - -<p>The most important guideline when making a new package that fixes a - security problem is to make as few changes as possible. Our users and - developers are relying on the exact behaviour of a release once it is made, - so any change we make can possibly break someone's system. This is - especially true in case of libraries: make sure you never change the - Application Program Interface (API) or Application Binary Interface (ABI), - no matter how small the change is.</p> - -<p>This means that moving to a new upstream version is not a good solution, - instead the relevant changes should be backported. Generally upstream - maintainers are willing to help if needed, if not the Debian security team - might be able to help.</p> - -<p>In some cases it is not possible to backport a security fix, for example - when large amounts of source code need to be modified or rewritten. If that - happens it might be necessary to move to a new upstream version, but this - has to be coordinated with the security team beforehand.</p> - -<toc-add-entry name=version>The version number for a package indicates that I am still running - a vulnerable version!</toc-add-entry> -<p>A: Instead of upgrading to a new release we backport security fixes to - the version that was shipped in the stable release. The reason we do - this is to make sure that a release changes as little as possible - so things will not change or break unexpectedly as a result of a - security fix. You can check if you are running a secure version of - a package by looking at the package changelog, or comparing its - exact version number with the version indicated in the Debian - Security Advisory.</p> - -<toc-add-entry name=archismissing>I received an advisory, but the build for one - processor architecture seems to be missing.</toc-add-entry> -<p>A: Generally the Security Team releases an advisory with builds of the updated - packages for all architectures that Debian supports. However, some architectures - are slower than others and it may happen that builds for most architectures - are ready while some are still missing. These smaller archs represent a small - fraction of our user base. Depending on the urgency of the issue - we may decide to release the advisory forthwith. The missing builds will be - installed as soon as they come available, but no further notice of this will - be given. Of course we will never release an advisory where the i386 or amd64 - builds are not present.</p> - -<toc-add-entry name=unstable>How is security handled for <tt>unstable</tt>?</toc-add-entry> -<p>A: Security for unstable is primarily handled by package maintainers, not - by the Debian Security Team. Although the security team may upload - high-urgency security-only fixes when maintainers are noticed to be - inactive, support for stable will always have priority. - If you want to have a secure (and stable) server you are strongly encouraged - to stay with stable.</p> - -<toc-add-entry name=testing>How is security handled for <tt>testing</tt>?</toc-add-entry> -<p>A: Security for testing benefits from the security efforts of the entire - project for unstable. However, there is a minimum two-day migration delay, - and sometimes security fixes can be held up by transitions. The Security - Team helps to move along those transitions holding back important - security uploads, but this is not always possible and delays may occur. - Especially in the months after a new stable release, when many new versions - are uploaded to unstable, security fixes for testing may lag behind. - If you want to have a secure (and stable) server you are strongly - encouraged to stay with stable.</p> - -<toc-add-entry name=contrib>How is security handled for <tt>contrib</tt> and - <tt>non-free</tt>?</toc-add-entry> -<p>A: The short answer is: it's not. Contrib and non-free aren't official - parts of the Debian Distribution and are not released, and thus not - supported by the security team. Some non-free packages are distributed - without source or without a license allowing the distribution of modified - versions. In those cases no security fixes can be made at all. If it - is possible to fix the problem, and the package maintainer or someone else - provides correct updated packages, then the security team will generally - process them and release an advisory.</p> - -<toc-add-entry name=sidversionisold>The advisory says unstable is fixed in - version 1.2.3-1, but unstable has 1.2.5-1, what's up?</toc-add-entry> -<p>A: We try to list the first version in unstable that fixed the problem. - Sometimes the maintainer has uploaded even newer versions in the meantime. - Compare the version in unstable with the version we indicate. If it's the - same or higher, you should be safe from this vulnerability. If you want to - be sure, you can check the package changelog with <tt>apt-get changelog - package-name</tt> and search for the entry announcing the fix.</p> - -<toc-add-entry name=mirror>Why are there no official mirrors for security.debian.org?</toc-add-entry> -<p>A: Actually, there are. There are several official mirrors, implemented - through DNS aliases. The purpose of security.debian.org is to make security - updates available as quickly and easily as possible.</p> - -<p>Encouraging the use of unofficial mirrors would add extra complexity - that is usually not needed and that can cause frustration if these - mirrors are not kept up to date.</p> - -<toc-add-entry name=missing>I've seen DSA 100 and DSA 102, now where is DSA 101?</toc-add-entry> -<p>A: Several vendors (mostly of GNU/Linux, but also of BSD - derivatives) coordinate security advisories for some incidents and - agree to a particular timeline so that all vendors are able to - release an advisory at the same time. This was decided in order to - not discriminate some vendors that need more time (e.g. when the - vendor has to pass packages through lengthy QA tests or has to - support several architectures or binary distributions). Our own - security team also prepares advisories in advance. Every now and - then, other security issues have to be dealt with before the parked - advisory could be released, and hence temporarily leaving out one or - more advisories by number. -</p> - -<toc-add-entry name=contact>How can I reach the security team?</toc-add-entry> - -<p>A: Security information can be sent to security@debian.org or - team@security.debian.org, both of which are read by the members of - the security team. -</p> - -<p>If desired, email can be encrypted with the Debian Security - Contact key (key ID <a - href="https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x0d59d2b15144766a14d241c66baf400b05c3e651">\ - 0x0D59D2B15144766A14D241C66BAF400B05C3E651</a>). For the PGP/GPG keys of individual team members, please - refer to the <a href="https://keyring.debian.org/">keyring.debian.org</a> - keyserver.</p> - -<toc-add-entry name=discover>I guess I found a security problem, what should I do?</toc-add-entry> - -<p>A: If you learn about a security problem, either in one of your own - packages or in someone else's please always contact the security team. If - the Debian security team confirms the vulnerability and other vendors are - likely to be vulnerable as well, they usually contact other vendors as - well. If the vulnerability is not yet public they will try to coordinate - security advisories with the other vendors, so all major distributions are - in sync.</p> - -<p>If the vulnerability is already publicly known, be sure to file a bug - report in the Debian BTS, and tag it <q>security</q>.</p> - -<p>If you are a Debian maintainer, <a href="#care">see below</a>.</p> - -<toc-add-entry name=care>What am I supposed to do with a security problem in one of - my packages?</toc-add-entry> - -<p>A: If you learn of a security problem, either in your package or - someone else's please always contact the security team via email at - team@security.debian.org. They keep track - of outstanding security problems, can help maintainers with - security problems or fix problems on their own, are responsible for - sending out security advisories and maintaining - security.debian.org.</p> - -<p>The <a href="$(DOC)/developers-reference/pkgs.html#bug-security">\ - Developer's Reference</a> has complete instructions on what to do.</p> - -<p>It's particularly important that you don't upload to any other - distribution other than unstable without prior agreement by the - security team, because bypassing them will cause confusion and more - work.</p> - -<toc-add-entry name=enofile>I tried to download a package listed in one of the security - advisories, but I got a `file not found' error.</toc-add-entry> - -<p>A: Whenever a newer bugfix supersedes an older package on - security.debian.org, chances are high that the old package will be - removed by the time the new one gets installed. Hence, you'll get - this `file not found' error. We don't want to distribute packages - with known security bugs longer than absolutely necessary.</p> - -<p>Please use the packages from the latest security advisories, which are - distributed through the <a - href="https://lists.debian.org/debian-security-announce/">\ - debian-security-announce</a> mailing list. It's best to simply run - <code>apt-get update</code> before upgrading the package.</p> - -<toc-add-entry name=upload>I've got a bugfix, can I upload to security.debian.org directly?</toc-add-entry> - -<p>A: No, you can't. The archive at security.debian.org is maintained - by the security team, who have to approve all packages. You should - instead send patches or proper source packages to the security team - via team@security.debian.org. They will be - reviewed by the security team and eventually uploaded, either with - or without modifications.</p> - -<p>The <a href="$(DOC)/developers-reference/pkgs.html#bug-security">\ - Developer's Reference</a> has complete instructions on what to do.</p> - -<toc-add-entry name=ppu>I've got a bugfix, can I upload to proposed-updates instead?</toc-add-entry> - -<p>A: Technically speaking, you can. However, you should not do this, - since this interferes badly with the work of the security team. - Packages from security.debian.org will be copied into the - proposed-updates directory automatically. If a package with the - same or a higher version number is already installed into the - archive, the security update will be rejected by the archive - system. That way, the stable distribution will end up without a - security update for this package instead, unless the <q>wrong</q> - packages in the proposed-updates directory were rejected. Please contact the - security team instead and include all details of the vulnerability - and attach the source files (i.e. diff.gz and dsc files) to your mail.</p> - -<p>The <a href="$(DOC)/developers-reference/pkgs.html#bug-security">\ - Developer's Reference</a> has complete instructions on what to do.</p> - -<toc-add-entry name=SecurityUploadQueue>I'm pretty sure my packages are fine, - how can I upload them?</toc-add-entry> - -<p>A: If you are very sure that your packages don't break anything, that the - version is sane (i.e. greater than the version in stable and less than the - version in testing/unstable), that you didn't change the behaviour of the - package, despite the corresponding security problem, that you compiled it - for the correct distribution (that is <code>oldstable-security</code> or - <code>stable-security</code>), that the package contains the original - source if the package is new on security.debian.org, that you can confirm - the patch against the most recent version is clean and only touches the - corresponding security problem (check with <code>interdiff -z</code> and - both <code>.diff.gz</code> files), that you have proofread the patch at - least thrice, and that <code>debdiff</code> doesn't display any changes, - you may upload the files into the incoming directory - <code>ftp://ftp.security.upload.debian.org/pub/SecurityUploadQueue</code> on the - security.debian.org directly. Please send a notification with all details - and links to team@security.debian.org as well.</p> - -<toc-add-entry name=help>How can I help with security?</toc-add-entry> -<p>A: Please review each problem before reporting it to - security@debian.org. If you are able to provide patches, that - would speed up the process. Do not simply forward bugtraq mails, - because we already receive them — but do provide us with - additional information about things reported on bugtraq.</p> - -<p>A good way to get started with security work is helping - out on the Debian Security Tracker (<a - href="https://security-tracker.debian.org/tracker/data/report">instructions</a>).</p> - -<toc-add-entry name=proposed-updates>What is the scope of proposed-updates?</toc-add-entry> -<p>A: This directory contains packages which are proposed to enter the - next revision of Debian stable. Whenever packages are uploaded by - a maintainer for the stable distribution, they end up in the - proposed-updates directory. Since stable is meant to be stable, no - automatic updates are made. The security team will upload fixed - packages mentioned in their advisories to stable, however they will - be placed in proposed-updates first. Every couple of months the - Stable Release Manager checks the list of packages in - proposed-updates and discusses whether a package is suited for - stable or not. This is compiled into another revision of stable - (e.g. 2.2r3 or 2.2r4). Packages that don't fit will probably be - rejected and dropped from proposed-updates as well. -</p> - -<p>Note that the packages uploaded by maintainers (not by the security team) - in the proposed-updates/ directory are not supported by the security - team.</p> - -<toc-add-entry name=composing>How is the security team composed?</toc-add-entry> -<p>A: The Debian security team consists of - <a href="../intro/organization#security">several officers and secretaries</a>. - The security team itself appoints people to join the team.</p> - -<toc-add-entry name=lifespan>How long will security updates be provided?</toc-add-entry> -<p>A: The security team tries to support a stable distribution for - about one year after the next stable distribution has been - released, except when another stable distribution is released - within this year. It is not possible to support three - distributions; supporting two simultaneously is already difficult - enough. -</p> - -<toc-add-entry name=check>How can I check the integrity of packages?</toc-add-entry> -<p>A: This process involve checking the Release file signature against - the <a href="https://ftp-master.debian.org/keys.html">\ - public key</a> used for the archive. The Release file contains the - checksums of Packages and Sources files, which contain - checksums of binary and source packages. Detailed instruction on how - to check packages integrity can be found in the <a - href="$(HOME)/doc/manuals/securing-debian-howto/ch7#s-deb-pack-sign">\ - Debian Securing Manual</a>.</p> - -<toc-add-entry name=break>What to do if a random package breaks after a security update?</toc-add-entry> -<p>A: First of all, you should figure out why the package breaks and - how it is connected to the security update, then contact the - security team if it is serious or the stable release manager if it - is less serious. We're talking about random packages that break - after a security update of a different package. If you can't - figure out what's going wrong but have a correction, talk to the - security team as well. You may be redirected to the stable release - manager though.</p> - -<toc-add-entry name=cvewhat>What is a CVE identifier?</toc-add-entry> -<p>A: The Common Vulnerabilities and Exposures project assignes - unique names, called CVE identifiers, to specific security - vulnerabilities, to make it easier to uniquely refer to a specific - issue. More information can be found at <a - href="https://en.wikipedia.org/wiki/Common_Vulnerabilities_and_Exposures">\ - Wikipedia</a>.</p> - -<toc-add-entry name=cvedsa>Does Debian issue a DSA for every CVE id?</toc-add-entry> -<p>A: The Debian security team keeps track of every issued CVE identifier, - connect it to the relevant Debian package and assess its impact in a - Debian context - the fact that something is assigned a CVE id does not - necessarily imply that the issue is a serious threat to a Debian system. - This information is tracked in the - <a href="https://security-tracker.debian.org">Debian Security Tracker</a> - and for the issues that are considered serious a Debian Security Advisory - will be issued.</p> - -<p>Low-impact issues not qualifying for a DSA can be fixed in the next - release of Debian, in a point release of the current stable or oldstable - distributions, or are included in a DSA when that is being issued for a - more serious vulnerability.</p> - -<toc-add-entry name=cveget>Can Debian assign CVE identifiers?</toc-add-entry> -<p>A: Debian is a CVE Numbering Authority and can assign ids, but per - CVE policy only to yet-undisclosed issues. If you have an undisclosed - security vulnerability for software in Debian and would like to get an - identifier for it, contact the Debian Security Team. For cases where the - vulnerability is already public, we advise to follow the procedure - detailed in the <a - href="https://github.com/RedHatProductSecurity/CVE-HOWTO">\ - CVE OpenSource Request HOWTO</a>.</p> - -<toc-add-entry name=disclosure-policy>Does Debian have a vulnerability disclosure policy?</toc-add-entry> -<p>A: Debian has published a <a href="disclosure-policy">vulnerability - disclosure policy</a> as part of its participation in the CVE - program. - -<h1>Deprecated Debian security FAQ</h1> - -<toc-add-entry name=localremote>What does <q>local (remote)</q> mean?</toc-add-entry> -<p><b>The field <i>Problem type</i> in DSA mails is not used since April 2014.</b><br/> - A: Some advisories cover vulnerabilities that cannot be identified - with the classic scheme of local and remote exploitability. Some - vulnerabilities cannot be exploited from remote, i.e. don't - correspond to a daemon listening to a network port. If they can be - exploited by special files that could be provided via the network - while the vulnerable service is not permanently connected with the - network, we write <q>local (remote)</q> in such cases.</p> - -<p>Such vulnerabilities are somewhat between local and remote - vulnerabilities and often cover archives that could be provided - through the network, e.g. as mail attachment or from a download - page.</p> - diff --git a/greek/sitemap.wml b/greek/sitemap.wml deleted file mode 120000 index 1c70b6bd571..00000000000 --- a/greek/sitemap.wml +++ /dev/null @@ -1 +0,0 @@ -../english/sitemap.wml
\ No newline at end of file diff --git a/greek/social_contract.1.0.wml b/greek/social_contract.1.0.wml deleted file mode 100644 index d8580a2c8d8..00000000000 --- a/greek/social_contract.1.0.wml +++ /dev/null @@ -1,145 +0,0 @@ -#use wml::debian::template title="Debian Social Contract, Version 1.0" BARETITLE=true -#use wml::debian::translation-check translation="5477c3c791fabf2db59622d9eec1061b6f73aa57" maintainer="galaxico" - -# Original document: contract.html -# Author : Manoj Srivastava ( srivasta@tiamat.datasync.com ) -# Created On : Wed Jul 2 12:47:56 1997 - -<p> - Version 1.0 ratified on July 5, 1997. Superseded by - <a href="social_contract">Version 1.1</a>, ratified on April 26, 2004. -</p> - -<p>Debian, the producers of the Debian GNU/Linux system, have created the -<strong>Debian Social Contract</strong>. The <a href="#guidelines">Debian Free Software -Guidelines (DFSG)</a> part of the contract, initially designed -as a set of commitments that we agree to abide by, has been adopted by -the free software community as the basis of the -<a href="https://opensource.org/docs/osd">Open Source Definition</a>. - -<HR> -<h2>"Social Contract" with the Free Software Community</h2> -<ol> - <li><p><strong>Debian Will Remain 100% Free Software</strong> - <p>We promise to keep the Debian GNU/Linux Distribution - entirely free software. As there are many definitions of - free software, we include the guidelines we use to determine - if software is "<em>free</em>" below. We will support our - users who develop and run non-free software on Debian, but - we will never make the system depend on an item of non-free - software.</p> - <li><strong>We Will Give Back to the Free Software Community</strong> - <p>When we write new components of the Debian system, we will - license them as free software. We will make the best system - we can, so that free software will be widely distributed and - used. We will feed back bug-fixes, improvements, user - requests, etc. to the "<em>upstream</em>" authors of software - included in our system.</p> - <li><p><strong>We Won't Hide Problems</strong> - <p>We will keep our entire bug-report database open for public - view at all times. Reports that users file on-line will - immediately become visible to others.</p> - <li><p><strong>Our Priorities are Our Users and Free Software</strong> - <p>We will be guided by the needs of our users and the - free-software community. We will place their interests first - in our priorities. We will support the needs of our users - for operation in many different kinds of computing - environment. We won't object to commercial software that is - intended to run on Debian systems, and we'll allow others to - create value-added distributions containing both Debian and - commercial software, without any fee from us. To support - these goals, we will provide an integrated system of - high-quality, 100% free software, with no legal restrictions - that would prevent these kinds of use.</p> - <li><p><strong>Programs That Don't Meet Our Free-Software Standards</strong> - <p>We acknowledge that some of our users require the use of - programs that don't conform to the - <a href="#guidelines">Debian Free Software Guidelines</a>. - We have created "<tt>contrib</tt>" and "<tt>non-free</tt>" - areas in our FTP archive for this software. The software in - these directories is not part of the Debian system, although - it has been configured for use with Debian. We encourage CD - manufacturers to read the licenses of software packages in - these directories and determine if they can distribute that - software on their CDs. Thus, although non-free software - isn't a part of Debian, we support its use, and we provide - infrastructure (such as our bug-tracking system and mailing - lists) for non-free software packages. -</ol> -<HR> -<h2 id="guidelines">The Debian Free Software Guidelines (DFSG)</h2> -<ol> - <li><p><strong>Free Redistribution</strong> - <p>The license of a Debian component may not restrict any - party from selling or giving away the software as a - component of an aggregate software distribution containing - programs from several different sources. The license may not - require a royalty or other fee for such sale.</p> - <li><p><strong>Source Code</strong> - <p>The program must include source code, and must allow - distribution in source code as well as compiled - form.</p> - <li><p><strong>Derived Works</strong> - <p>The license must allow modifications and derived works, and - must allow them to be distributed under the same terms as - the license of the original software.</p> - <li><p><strong>Integrity of The Author's Source Code</strong> - <p>The license may restrict source-code from being distributed - in modified form <strong>only</strong> if the license allows - the distribution of "<tt>patch files</tt>" with the source - code for the purpose of modifying the program at build - time. The license must explicitly permit distribution of - software built from modified source code. The license may - require derived works to carry a different name or version - number from the original software. (<em>This is a - compromise. The Debian group encourages all authors not to - restrict any files, source or binary, from being - modified.</em>)</p> - <li><p><strong>No Discrimination Against Persons or Groups</strong> - <p>The license must not discriminate against any person or - group of persons.</p> - <li><p><strong>No Discrimination Against Fields of Endeavor</strong> - <p>The license must not restrict anyone from making use of the - program in a specific field of endeavor. For example, it may - not restrict the program from being used in a business, or - from being used for genetic research.</p> - <li><p><strong>Distribution of License</strong> - <p>The rights attached to the program must apply to all to - whom the program is redistributed without the need for - execution of an additional license by those - parties.</p> - <li><p><strong>License Must Not Be Specific to Debian</strong> - <p>The rights attached to the program must not depend on the - program's being part of a Debian system. If the program is - extracted from Debian and used or distributed without Debian - but otherwise within the terms of the program's license, all - parties to whom the program is redistributed should have the - same rights as those that are granted in conjunction with - the Debian system.</p> - <li><p><strong>License Must Not Contaminate Other Software</strong> - <p>The license must not place restrictions on other software - that is distributed along with the licensed - software. For example, the license must not insist that all - other programs distributed on the same medium must be free - software.</p> - <li><p><strong>Example Licenses</strong> - <p>The "<strong><a href="https://www.gnu.org/copyleft/gpl.html">GPL</a></strong>", - "<strong><a href="https://opensource.org/licenses/BSD-3-Clause">BSD</a></strong>", and - "<strong><a href="https://perldoc.perl.org/perlartistic.html">Artistic</a></strong>" - licenses are examples of licenses that we consider "<em>free</em>". -</ol> - -<p><em>The concept of stating our "social contract with the free -software community" was suggested by Ean Schuessler. This document -was drafted by Bruce Perens, refined by the other Debian developers -during a month-long e-mail conference in June 1997, and then -<a href="https://lists.debian.org/debian-announce/debian-announce-1997/msg00017.html">\ -accepted</a> as the publicly stated policy of the Debian Project.</em></p> - -<p><em>Bruce Perens later removed the Debian-specific references from the -Debian Free Software Guidelines to create -<a href="https://opensource.org/docs/definition.php">“The Open -Source Definition”</a>.</em></p> - -<p><em>Other organizations may derive from and build on this document. -Please give credit to the Debian project if you do.</em> diff --git a/greek/support.wml b/greek/support.wml deleted file mode 100644 index 0a426b520cc..00000000000 --- a/greek/support.wml +++ /dev/null @@ -1,169 +0,0 @@ -#use wml::debian::template title="User Support" MAINPAGE="true" -#use wml::debian::recent_list -#use wml::debian::translation-check translation="c7a64739b495b3bd084b972d820ef78fc30a3f8a" maintainer="galaxico" - -<link href="$(HOME)/font-awesome.css" rel="stylesheet" type="text/css"> - - -<ul class="toc"> - <li><a href="#irc">IRC (real time Support)</a></li> - <li><a href="#mail_lists">Mailing Lists</a></li> - <li><a href="#usenet">Usenet Newsgroups</a></li> - <li><a href="#forums">Debian User Forums</a></li> - <li><a href="#maintainers">How to contact Package Maintainers</a></li> - <li><a href="#bts">Bug Tracking System</a></li> - <li><a href="#release">Known Problems</a></li> -</ul> - -<aside> -<p><span class="fas fa-caret-right fa-3x"></span> Debian support is offered by a group of volunteers. If this community-driven support doesn't fulfil your needs and you can't find the answer in our <a href="doc/">documentation</a>, you may hire a <a href="consultants/">consultant</a> to answer your questions or to maintain or add additional functionality to your Debian system.</p> -</aside> - -<h2><a id="irc">IRC (real time Support)</a></h2> - -<p> -<a href="http://www.irchelp.org/">IRC</a> (Internet Relay Chat) is a great way to chat with people from all over the world in real time. It's a text-based chat system for instant messaging. On IRC you can enter chat rooms (so-called channels) or you can directly chat with individual persons via private messages. -</p> - -<p> -IRC channels dedicated to Debian can be found on <a href="https://www.oftc.net/">OFTC</a>. For a full list of Debian channels, please refer to our <a href="https://wiki.debian.org/IRC">Wiki</a>. You can also use a <a href="https://netsplit.de/channels/index.en.php?net=oftc&chat=debian">search engine</a> to check for Debian-related channels. -</p> - -<h3>IRC Clients</h3> - -<p> -To connect to the IRC network, you can either use OFTC's <a href="https://www.oftc.net/WebChat/">WebChat</a> in your preferred web browser or install a client on your computer. There are lots of different clients out there, some with a graphical interface, some for the console. Some popular IRC clients have been packaged for Debian, for example: -</p> - -<ul> - <li><a href="https://packages.debian.org/stable/net/irssi">irssi</a> (text mode)</li> - <li><a href="https://packages.debian.org/stable/net/weechat-curses">WeeChat</a> (text mode)</li> - <li><a href="https://packages.debian.org/stable/net/hexchat">HexChat (GTK)</a></li> - <li><a href="https://packages.debian.org/stable/net/konversation">Konversation</a> (KDE)</li> -</ul> - -<p> -The Debian Wiki offers a more comprehensive <a href="https://wiki.debian.org/IrcClients">list of IRC clients</a> which are available as Debian packages. -</p> - -<h3>Connect to the Network</h3> - -<p> -Once you have the client installed, you need to tell it to connect -to the server. In most clients, you can do that by typing: -</p> - -<pre> -/server irc.debian.org -</pre> - -<p>The hostname irc.debian.org is an alias for irc.oftc.net. In some clients (such as irssi) you will need to type this instead:</p> - -<pre> -/connect irc.debian.org -</pre> - -# Note to translators: -# You might want to insert here a paragraph stating which IRC channel is available -# for user support in your language and pointing to the English IRC channel. -# <p>Once you are connected, join channel <code>#debian-foo</code> by typing</p> -# <pre>/join #debian</pre> -# for support in your language. -# <p>For support in English, read on</p> - -<h3>Join a Channel</h3> - -<p>Once you are connected, join channel <code>#debian</code> by typing this command:</p> - -<pre> -/join #debian -</pre> - -<p>Note: graphical clients like HexChat or Konversation often have a button -or a menu entry for connecting to servers and joining channels. -</p> - -<p style="text-align:center"><button type="button"><span class="fas fa-book-open fa-2x"></span> <a href="https://wiki.debian.org/DebianIRC">Read our IRC FAQ</a></button></p> - -<h2><a id="mail_lists">Mailing Lists</a></h2> - -<p> -More than thousand active <a href="intro/people.en.html#devcont">developers</a> spread around the world work on Debian in their spare time—and in their own timezones. Therefore we communicate primarily through e-mail. Similarly, most of the conversation between Debian developers and users happens on different <a href="MailingLists/">mailing lists</a>: -</p> - -# Note to translators: -# You might want to adapt the following paragraph, stating which list -# is available for user support in your language instead of English. - -<ul> - <li>For user support in English, please contact the <a href="https://lists.debian.org/debian-user/">debian-user</a> mailing list.</li> - <li>For user support in other languages, please check the <a href="https://lists.debian.org/users.html">index</a> of other user mailing lists.</li> -</ul> - -<p> -You can browse our <a href="https://lists.debian.org/">mailing list archive</a> or <a href="https://lists.debian.org/search.html">search</a> the archives without the need to be subscribed. -</p> - -<p> -Of course, there are plenty of other mailing lists, dedicated to some aspect of the Linux ecosystem and not Debian-specific. Please use your favorite search engine to find the most suitable list for your purpose. -</p> - -<h2><a id="usenet">Usenet Newsgroups</a></h2> - -<p> -A lot of our <a href="#mail_lists">mailing lists</a> can be browsed as newsgroups, in the <kbd>linux.debian.*</kbd> hierarchy. -</p> - -<h2><a id="forums">Debian User Forums</h2> - -# Note to translators: -# If there is a specific Debian forum for your language you might want to -# insert here a paragraph stating which list is available for user support -# in your language and pointing to the English forums. -# <p><a href="http://someforum.example.org/">someforum</a> is a web portal -# on which you can use your language to discuss Debian-related topics, -# submit questions about Debian, and have them answered by other users.</p> -# -# <p><a href="https://forums.debian.net">Debian User Forums</a> is a web portal -# on which you can use the English language to discuss Debian-related topics, -# submit questions about Debian, and have them answered by other users.</p> - -<p> -<a href="https://forums.debian.net">Debian User Forums</a> is a web portal -where thousands of other users discuss Debian-related topics, ask questions, -and help each other by answering them. You can read all boards without -having to register. If you want to participate in the discussion and publish -your own postings, please register and log in. -</p> - -<h2><a id="maintainers">How to contact Package Maintainers</a></h2> - -<p> -Basically, there are two common ways to get in touch with a maintainer of a Debian package: -</p> - -<ul> - <li>If you'd like to report a bug, simply file a <a href="Bugs/Reporting">bug report</a>; the maintainer automatically receives a copy of your bug report.</li> - <li>If you simply want to send an email to the maintainer, use the special mail aliases set up for each package:<br> - <<em>package_name</em>>@packages.debian.org</li> -</ul> - - -<h2><a id="bts">Bug Tracking System</a></h2> - -<p> -The Debian distribution has its own <a href="Bugs/">bug tracker</a> with bugs reported by users and developers. Every bug has a unique number and is kept on file until it is marked as resolved. There are two different ways to report a bug: -</p> - -<ul> - <li>The recommended way is to use the Debian package <em>reportbug</em>.</li> - <li>Alternatively, you can send an email as described on this <a href="Bugs/Reporting">page</a>.</li> -</ul> - -<h2><a id="release">Known Problems</a></h2> - -<p>Limitations and severe problems of the current stable distribution -(if any) are described on <a href="releases/stable/">the release page</a>.</p> - -<p>Please pay particular attention to the <a href="releases/stable/releasenotes">release -notes</a> and the <a href="releases/stable/errata">errata</a>.</p> diff --git a/greek/trademark.wml b/greek/trademark.wml deleted file mode 100644 index fab88b77921..00000000000 --- a/greek/trademark.wml +++ /dev/null @@ -1,219 +0,0 @@ -#use wml::debian::template title="Debian Trademarks" -#use wml::debian::toc -#use wml::debian::translation-check translation="7877b46be9028804be6ca61d385c4aeecc91c653" maintainer="galaxico" - -<toc-display /> - - -<toc-add-entry name="trademarks">Trademarks</toc-add-entry> - -<p>Debian is committed to protect and ensure consistent usage of its trademark, -logos, and styles and also make it easier for every <em>bonafide</em> user to -use. As a part of this process, the Debian trademark is a registered United -States trademark of <a -href="https://www.spi-inc.org/corporate/trademarks/">Software in the Public -Interest, Inc.</a>, managed by the Debian project. For <em>registration outside -the United States</em>, we have filed a <a -href="https://en.wikipedia.org/wiki/Madrid_system">Madrid Protocol</a> -application to extend the protection in the European Union, China and -Japan; the Debian trademark is also registered -<a href="https://gru.inpi.gov.br/pePI/servlet/MarcasServletController?Action=searchMarca&tipoPesquisa=BY_NUM_PROC&Source=OAMI&NumPedido=827045310">in Brazil</a>, -N. do processo 827045310, but it is expired.</p> - -<p>The Debian trademark was first <a -href="http://tarr.uspto.gov/servlet/tarr?regser=serial&entry=75386376">registered</a> -the 21st of December of 1999, but has been in use since August 1993. It is -registered under the Nice Class 009: <q>Computer Utility and Operating System -Software</q>.</p> - - -<toc-add-entry name="policy">Trademark Policy</toc-add-entry> - -<pre><code>Version: 2.0 -Published: 19 January 2013 -</code></pre> - -<p><a href="https://www.spi-inc.org/">Software in the Public Interest, Inc.</a> -owns a number of trademarks in both word and logo form including brands, -slogans, styles. This policy encompasses all marks, in word and logo form, -collectively referred to as <q>Debian trademarks</q>. You can see a -non-exhaustive list of Debian trademarks, including both registered and -unregistered (but otherwise legally recognized) trademarks at our -<a href="#trademarks">trademarks page</a>.</p> - -<p>The objective of this trademark policy is:</p> - -<ol> - <li>to encourage widespread use and adoption of the Debian trademarks,</li> - <li>to clarify proper usage of Debian trademarks by third parties,</li> - <li>to prevent misuse of Debian trademarks that can confuse or mislead users - with respect to Debian or its affiliates.</li> -</ol> - -<p>Please note that it is not the goal of this policy to limit commercial -activity around Debian. We encourage businesses to work on Debian while being -compliant with this policy.</p> - -<p>Following are the guidelines for the proper use of Debian trademarks by -publishers and other third parties. Any use of or reference to Debian -trademarks that is inconsistent with these guidelines, or other unauthorized -use of or reference to Debian trademarks, or use of marks that are confusingly -similar to Debian trademarks, is prohibited and may violate Debian trademark -rights.</p> - -<p>Any use of Debian trademarks in a misleading and false manner or in a manner -that disparages Debian, such as untruthful advertising, is always -prohibited.</p> - - -<h3>When You Can Use the Debian Trademarks Without Asking Permission</h3> - -<ol> - - <li>You can use Debian trademarks to make true factual statements about - Debian or communicate compatibility with your product truthfully.</li> - - <li>Your intended use qualifies as <q>nominative fair use</q> of the Debian - trademarks, i.e., merely identifying that you are talking about Debian in a - text, without suggesting sponsorship or endorsement.</li> - - <li>You can use Debian trademarks to describe or advertise your services - or products relating to Debian in a way that is not misleading.</li> - - <li>You can use Debian trademarks to describe Debian in articles, titles - or blog posts.</li> - - <li>You can make t-shirts, desktop wallpapers, caps, or other merchandise - with Debian trademarks for <em>non-commercial usage</em>.</li> - - <li>You can also make merchandise with Debian trademarks - for <em>commercial usage</em>. In case of commercial usage, we recommend - that you truthfully advertise to customers which part of the selling - price, if any, will be donated to the Debian project. See - our <a href="$(HOME)/donations">donations page</a> for more information - on how to donate to the Debian project.</li> - -</ol> - - -<h3>When You Can NEVER Use the Debian Trademarks Without Asking Permission</h3> - -<ol> - - <li>You cannot use Debian trademarks in any way that suggests an - affiliation with or endorsement by the Debian project or community, if the - same is not true.</li> - - <li>You cannot use Debian trademarks in a company or organization name or - as the name of a product or service.</li> - - <li>You cannot use a name that is confusingly similar to Debian - trademarks.</li> - - <li>You cannot use Debian trademarks in a domain name, with or without - commercial intent.</li> - -</ol> - - -<h3>How to Use the Debian Trademarks</h3> - -<ol> - - <li>Use the Debian trademarks in a manner that makes it clear that your - project is related to the Debian project, but that it is not part of - Debian, produced by the Debian project, or endorsed by the Debian - project.</li> - - <li>Acknowledge Software in the Public Interest, Inc.'s ownership of the - Debian trademark prominently. - - <p><em>Example:</em></p> - - <p>[TRADEMARK] is a (<q>registered,</q> if applicable) trademark owned by - Software in the Public Interest, Inc.</p> - </li> - - <li>Include a disclaimer of sponsorship, affiliation, or endorsement by - Debian on your website and on all related printed materials. - - <p><em>Example:</em></p> - - <p>X PROJECT is not affiliated with Debian. Debian is a registered - trademark owned by Software in the Public Interest, Inc.</p> - </li> - - <li>Distinguish the Debian trademarks from the surrounding words by - italicizing, bolding or underlining it.</li> - - <li>Use the Debian trademarks in their exact form, neither abbreviated or - hyphenated, nor combined with any other word or words.</li> - - <li>Do not create acronyms using the Debian trademarks.</li> - -</ol> - - -<h3>Permission To Use</h3> - -<p>When in doubt about the use of Debian trademarks, or to request permission -for uses not allowed by this policy, please send an email to -<a href="mailto:trademark@debian.org?subject=Trademark%20Use%20Request">\ -trademark@debian.org with subject <q>Trademark Use Request</q></a>; be sure to -include the following information in the body of your message:</p> -<ul> -<li>Name of the User</li> -<li>Name of the organization/project</li> -<li>Purpose of Use (commercial/non-commercial)</li> -<li>Nature of Use</li> -</ul> - - -<h3>Newer Versions of this Policy</h3> - -<p>This policy may be revised from time to time and updated versions shall be -available at <url https://www.debian.org/trademark>.</p> - - -<h3>Guidelines for Using Logos</h3> - -<ul> - - <li>Any scaling must retain the original proportions of the logo. - - <li>Do not use the Debian logos as part of your company logo or product logo - or branding itself. They can be used as part of a page describing your - products or services. - - <li>You need not ask us for permission to use logos on your own website - solely as a hyperlink to the Debian project website. - -</ul> - -<p> -For any queries with respect to these guidelines, please send an email to -<email "trademark@debian.org">. -</p> - -<toc-add-entry name="licenses">Organisations Licensed to Use Debian Trademarks</toc-add-entry> - -<p>The following organisations have been licensed to use -the Debian trademark through a License Agreement:</p> - -<ul> - -<li>Stiftelsen SLX Debian Labs, per SPI's resolution -<a href="https://www.spi-inc.org/corporate/resolutions/2004/2004-01-05.bmh.1/">\ -2004-01-05.bmh.1</a>.</li> - -<li>Vincent Renardias and <q>Les logiciels du soleil</q>, per SPI's resolution -<a href="https://www.spi-inc.org/corporate/resolutions/1999/1999-08-06.mgs/">\ -1999-08-06.mgs</a>.</li> - -<li> -debian.ch, <a -href="https://lists.debian.org/debian-www/2011/04/msg00163.html">\ -by Stefano Zacchiroli</a>, Debian Project Leader in 2011. -</li> - -</ul> diff --git a/greek/women/Makefile b/greek/women/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/women/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/women/about.wml b/greek/women/about.wml deleted file mode 100644 index 7a4b134134f..00000000000 --- a/greek/women/about.wml +++ /dev/null @@ -1,44 +0,0 @@ -#use wml::debian::template title="About Debian Women" -#use wml::debian::translation-check translation="b8114b588961778dbd04974c1464a2f388a90c28" maintainer="galaxico" - - -<p> - The Debian Women project was founded in May 2004. We seek to balance - and diversify the Debian Project by actively engaging with interested - women and encouraging them to become more involved with Debian. We will - promote women's involvement in Debian by increasing the visibility of - active women, providing mentoring and role models, and creating - opportunities for collaboration with new and current members of the - Debian Project. We welcome the involvement of all people who are - interested in increasing the participation of women in Debian. -</p> - -<p> - Our activities include the following: -</p> - -<ul> - <li>Running a <a href="https://lists.debian.org/debian-women">mailing - list</a> for discussion of related issues.</li> - <li> - Running an IRC channel for discussion of related issues, technical - questions and to allow women who are interested in contributing to - Debian to meet each other and some of Debian's current contributors. - See the <a href="$(WOMEN)/contact">contact</a> page for - more information on our IRC channel. - </li> - <li> - Organising BOF discussions at Linux conferences, to promote - discussion of issues facing women and their involvement in Debian - and Linux. - </li> - <li> - Giving talks at conferences, universities, LUGs and schools. - </li> - <li> - Actively encouraging and educating the Debian community to increase - understanding of the specific issues facing women who wish to - contribute more to Debian. - </li> -</ul> - diff --git a/greek/women/contact.wml b/greek/women/contact.wml deleted file mode 100644 index 7af1969fb84..00000000000 --- a/greek/women/contact.wml +++ /dev/null @@ -1,56 +0,0 @@ -#use wml::debian::template title="Contact" -#use wml::debian::translation-check translation="0ffebbe103f18771f13025648d0fe9782f74a283" maintainer="galaxico" - -<h2>Mailing List</h2> - -<p> -The <a href="https://lists.debian.org/debian-women/">debian-women list -page</a> includes a form for subscribing and unsubscribing, as well as -list archives. -</p> - -<h2>IRC</h2> -<p> -To join us in IRC, connect to irc.debian.org and /join #debian-women. -For more information on how to join an IRC network please refer to <a -href="$(WOMEN)/faq">the FAQ</a>. -</p> - -<h2>Contact by E-mail</h2> - -<p> -If you'd like to contact one of the members of Debian Women with -questions, please use the contact list below. -</p> - -<ul> -<li> - <a href="mailto:larjona@debian.org">Laura Arjona Reina</a> (English, Spanish) -</li> -<li> - <a href="mailto:soraia_esteves@hotmail.com">Soraia Esteves</a> (English, French, Portuguese) -</li> -<li> - <a href="mailto:contactkeerthana@gmail.com">Keerthana Krishnan</a> (English, Hindi, Malayalam) -</li> -<li> - <a href="mailto:ulrike@debian.org">Ulrike Uhlig</a> (German, French, English) -</li> - -### 2017/03/11: larjona sent mail to Erin, Helen, Fernanda and Meike. - -<li> - <a href="mailto:erinn@debian.org">Erinn Clark</a> (English) -</li> -<li> - <a href="mailto:helen@debian.org">Helen Faulkner</a> (English) -</li> -<li> - <a href="mailto:fernanda@softwarelivre.org">Fernanda Weiden</a> (Português) -</li> -</ul> - -### 2017/03/11: Meike retired, agrees to be listed as emeritus. - - -Thanks to Meike Reichle for her previous dedication to this task. diff --git a/greek/women/faq.wml b/greek/women/faq.wml deleted file mode 100644 index e43c5f86c33..00000000000 --- a/greek/women/faq.wml +++ /dev/null @@ -1,40 +0,0 @@ -#use wml::debian::template title="Frequently Asked Questions" BARETITLE="true" -#use wml::debian::faqs -### todo: verify links -#use wml::debian::translation-check translation="6191f0bac9b523a75f2b86a89e7eb3f900be73da" maintainer="galaxico" - - - <question> - Why are there so few women in the computer field / F/OSS - </question> - <answer><p> - There are a lot of theories about this, but no one can know for - sure. However, Ellen Spertus has a wonderful paper, - <a href="https://dspace.mit.edu/bitstream/handle/1721.1/7040/?sequence=2">Why - Are There So Few Female Computer Scientists?</a> that will explain - some of the cultural phenomena that might be a cause. Also, please - read Val Henson's - <a href="https://tldp.org/HOWTO/Encourage-Women-Linux-HOWTO/"> - HOWTO Encourage Women in Linux</a>. - </p></answer> - - - <question>What's on topic for the mailing list?</question> - <answer><p> - If it pertains to women in Debian, it's probably on topic. That - said, we're not trying to recreate - <a href="https://lists.debian.org/debian-user/">debian-user</a>, - <a href="https://lists.debian.org/debian-mentors/">debian-mentors</a>, or - <a href="https://lists.debian.org/debian-devel/">debian-devel</a>. The list is primarily for discussing - Debian Women related projects and collaboration. - </p></answer> - <question>How do I get on IRC?</question> - <answer><p> - For people that have never been on IRC before, you should first - install an IRC client. Popular Linux clients available in Debian are - <a href="http://www.hexchat.org/">HexChat</a>, <a href="http://www.pidgin.im">Pidgin</a> and - <a href="http://irssi.org/">irssi</a>. Once installed, connect - to irc.debian.org and /join #debian-women. For more general IRC - information, read the - <a href="http://www.irchelp.org/faq/">IRC FAQ</a>. - </p></answer> diff --git a/greek/women/index.wml b/greek/women/index.wml deleted file mode 100644 index e3aae283bdf..00000000000 --- a/greek/women/index.wml +++ /dev/null @@ -1,32 +0,0 @@ -#use wml::debian::template title="The Debian Women Project" -#use wml::debian::translation-check translation="8da95139c3595d47371ba8d288784086ae2ebacd" maintainer="galaxico" -<img style="float: right;" src="dw.png" alt="Debian Women"/> - - -<h2>What can be found here</h2> -<p> -This is the homepage of the Debian Women Project, a subproject of the <a -href="https://www.debian.org">Debian Project</a>. If you want to know more -about the Debian Women project, check out the <a -href="$(WOMEN)/about">About</a> -section and our <a href="$(WOMEN)/faq">Frequently Asked Questions</a>. The -<a href="https://wiki.debian.org/DebianWomen/Press">Press</a> section provides links to other -publications about our project. If you want to know who the women behind -the Debian Women project are, have a look at our <a -href="$(WOMEN)/profiles">Profiles</a>. -</p> - -<h2>Join us!</h2> - -<p> -If you are interested in joining the <a -href="https://www.debian.org">Debian</a> project, there are many things -you can do: you can be a Debian developer, maintainer, documenter or -translator, or help us by testing and reporting bugs. If you are not yet -sure how to get started, maybe our <a -href="$(WOMEN)/mentoring">Mentoring Program</a> is something for you. -You are also very welcome to join our own project! There are a lot of -ways how to get <a href="$(WOMEN)/participate">involved</a>. Feel -free to <a href="$(WOMEN)/contact">contact</a> us if you have any -questions or comments! -</p> diff --git a/greek/women/mentoring.wml b/greek/women/mentoring.wml deleted file mode 100644 index 0d453b08caf..00000000000 --- a/greek/women/mentoring.wml +++ /dev/null @@ -1,93 +0,0 @@ -#use wml::debian::template title="Debian Women Mentoring Program" -#use wml::debian::translation-check translation="8a7389809695b9d1808cb8a306cede14fe193209" maintainer="galaxico" - -## updated as for 11/2012 - -<h2>Welcome to the mentoring program!</h2> - -<p> -The goal of the Mentoring Program is to support and guide anyone who -wants to contribute to Debian (but who might not be sure where or how to -start) as they take their first steps. -</p> - -<h3>What do we mean by <q>mentoring</q>?</h3> - -<p> -Mentors involved in the program are people who have experience in some -Debian-related skills, and who would like to help other people improve -their skills in those areas. We expect that mentoring will be mainly -conducted in 1:1 relationships which might include a fairly broad set of -activities, such as the following: - -<ul> - <li> - the mentor giving the mentee technical assistance to - achieve a planned task that contributes to Debian - </li> - <li> - the mentor helping the mentee interact within the Debian - project in ways that are consistent with achieving the - planned tasks - </li> - <li> - the mentor providing help to the mentee in finding - documentation that is relevant to the planned tasks - </li> - <li> - the mentor introducing the mentee to aspects of the Debian - community and culture, especially those which relate to the - planned task - </li> - </ul> - -<p> -It is important to understand that mentors are not intended to do the -actual work involved in solving the problem that the mentee is working -on. That would defy the point of the program, which is to have the -mentees learn new skills and increase their interaction with and -contributions to Debian. It should also be noted that a mentor will not -necessarily be able (or willing) to sponsor a mentee's package, even if -the mentor is a Debian Developer and the agreed project involves -packaging. -</p> - -<h3>How the program works</h3> - - -<p> -Potential mentors can email <a -href="mailto:mentoring@women.debian.org">mentoring@women.debian.org</a>. -We are deeply appreciative of the people who are willing to volunteer their time -to help others in this way, and we hope you will find it interesting and -rewarding. -</p> - -<p> -Potential mentees can email -<a href="mailto:mentoring@women.debian.org">mentoring@women.debian.org</a> -to be matched with a potential mentor. Please explain in your email the -kinds of activities you are interested in being involved in, and the kind -of help you are looking for. We will do our best to match you up with a -mentor who is interested in helping out with those things. -</p> - -<p> -Once a mentor and mentee have been paired up, it is essentially up to you -to decide together what you will do. Please note that we expect both -mentor and mentee to be able to devote at least the amount of time -required to get into contact and discuss what you plan to do. Beyond -that, time commitments may differ considerably. We hope mentees will be -able to commit the amount of time required to do the tasks they are -interested in, and we hope mentors will be able to commit enough time to -help out their mentees with their tasks. However, bearing in mind that -people's lives and workloads can change, we recognize that people may -have to vary their level of commitment at times. -</p> - -<p> -If you have any problems with the mentoring program or with your mentor -or mentee, you can contact <a -href="mailto:mentoring@women.debian.org">mentoring@women.debian.org</a>, -and we will do our best to sort things out. -</p> diff --git a/greek/women/participate.wml b/greek/women/participate.wml deleted file mode 100644 index 4cfc58f64c0..00000000000 --- a/greek/women/participate.wml +++ /dev/null @@ -1,63 +0,0 @@ -#use wml::debian::template title="How to get involved in Debian Women" -#use wml::debian::translation-check translation="5a7a3715c7867ab7fa464be77965b7cf5050e2c0" maintainer="galaxico" - - <!-- Mailing list --> - <h3>Subscribe to the mailing list</h3> - <p> - Get to know the other people involved in the Debian Women project and - help shape the future of the project by participating in discussion - on our mailing list. The <a href="https://lists.debian.org/debian-women">debian-women - list page</a> includes a form for subscribing and unsubscribing, as - well as list archives. (This is true for all the Debian list links in - this document). - </p> - - <p> - In addition, everyone is encouraged to subscribe to the - <a href="https://lists.debian.org/debian-devel-announce">debian-devel-announce - mailing list</a>, to stay informed about - the most important changes affecting Debian. - </p> - - <!-- Profiles --> - ### FIXME: check with meike if she still want to be the contact for - ### this - - <h3>Submit your bio for the Profiles page</h3> - <p> - Are you a Debian volunteer, package maintainer, translator, or HOWTO - author? We would like to recognize you for your hard work by adding - you to our <a href="$(WOMEN)/profiles/">Profiles</a> page of women who - have contributed to Debian. Please tell us about yourself and your - efforts by answering some questions and submitting your answers to <a - href="mailto:larjona@debian.org">Laura Arjona</a>. - </p> - - ### FIXME: check with Erinn and Meike about this ↓↓↓↓ - <h3>Contribute content for the project website</h3> - <p> - We are always looking for new content for the site. If you have - suggestions or content to contribute, contact the maintainer of that - area:</p> - <ul> - <li> - <strong>General, Documents, FAQs, and Links:</strong> If - you want to help out with the website but don't have a - particular area of interest, contact - <a href="mailto:erinn@debian.org">Erinn</a>. - </li> - <li> - <strong>Events:</strong> If you have an idea for a Debian - Women event or are giving a Debian Women related talk or BoF - at another Linux/FOSS event, let the - <a href="https://lists.debian.org/debian-women">mailing list</a> - know, so others can join you. - </li> - <li> - <strong>Profiles:</strong> If you would like to help - compile information for the - <a href="$(WOMEN)/profiles/">Profiles</a> - page or recommend someone for inclusion, please contact - <a href="mailto:larjona@debian.org">Laura Arjona</a>. - </li> - </ul> diff --git a/greek/women/profiles/Makefile b/greek/women/profiles/Makefile deleted file mode 100644 index c26323c0c92..00000000000 --- a/greek/women/profiles/Makefile +++ /dev/null @@ -1 +0,0 @@ -include $(subst webwml/greek,webwml/english,$(CURDIR))/Makefile diff --git a/greek/women/profiles/akira.wml b/greek/women/profiles/akira.wml deleted file mode 100644 index c67a7bed2ec..00000000000 --- a/greek/women/profiles/akira.wml +++ /dev/null @@ -1,47 +0,0 @@ -#use wml::debian::translation-check translation="97dfe4170725c2f076dd47e272ebd749cd0b40e6" maintainer="galaxico" -<define-tag pagetitle>Akira</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Akira" picture=""> - - <email>marivalenm@gmail.com</email> - IRC: akira in #debian-reproducible and #debian-women - - <question1> - # How long have you been using Debian? - <answer> - I am a Debian user since 2012. I started making some contributions since <a href= - "https://bugs.debian.org/cgi-bin/pkgreport.cgi?correspondent=marivalenm%40gmail.com;archive=both;dist=unstable"> - January 18 of 2015</a>. - </answer> - - <question3> - <answer> - I was a Google Summer of Code student working on the reproducibly-builds effort during the summer of 2015. I plan to continue working with them afterwards :) - </answer> - - <question4> - # What got you interested in working with Debian? - <answer> - your answer - </answer> - - <question5> - # Do you have any tips for women interested in getting more involved with Debian? - <answer> - your answer - </answer> - - <question6> - # Are you involved with any other women in technology group? Which one(s)? - <answer> - your answer - </answer> - - <question7> - # A bit more about you... - <answer> - I was born in Venezuela but I came to Germany to do my bachelor in Biochemistry and Cell Biology. After my bachelor I went to Lund University in Sweden to do my Masters in Bioinformatics. Currently I am back in Germany to do the practical work for my master thesis. During my time in Sweden I took a course on Perl programming as part of my masters. I also know a bit of Python and JavaScript. - </answer> -</profile> diff --git a/greek/women/profiles/alba.wml b/greek/women/profiles/alba.wml deleted file mode 100644 index fd576a743ce..00000000000 --- a/greek/women/profiles/alba.wml +++ /dev/null @@ -1,47 +0,0 @@ -#use wml::debian::translation-check translation="737e31d579fb28438d16dc3ad6afeb3a068dbd81" maintainer="galaxico" -<define-tag pagetitle>Alba Ferri</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Alba Ferri" picture="alba.jpg"> - <email>branvan2k@gmail.com</email> - <question1> - <answer><p>Around 10 years. -</p></answer> - - <question2> - <answer><p>Nop</p></answer> - - <question3> - <answer><p> - Translation -</p></answer> - - <question4> - - <answer><p> - While I was studying networking engineer at college, I found out that I -could "see" all the info I wanted using Linux. - </p></answer> - - <question5> - <answer><p> - There's plenty of info in the net about Linux, if you like to have a -personalised window manager, great software and a different way to do -things, that's your S.O. - </p></answer> - - <question6> - <answer><p>No. - </p></answer> - - <question7> - <answer><p> -I'm a network engineer, that loves to see what goes on through the frames - -And that's why i started to use linux, to be able to "see" inside the -network. -I'm curious person in all fields of my life. -My other passion is to learn about the emotional brain of the human being. - </p></answer> -</profile>
\ No newline at end of file diff --git a/greek/women/profiles/alice.wml b/greek/women/profiles/alice.wml deleted file mode 100644 index c8a6c5706c7..00000000000 --- a/greek/women/profiles/alice.wml +++ /dev/null @@ -1,54 +0,0 @@ -#use wml::debian::translation-check translation="737e31d579fb28438d16dc3ad6afeb3a068dbd81" maintainer="galaxico" -<define-tag pagetitle>Alice Ferrazzi</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Alice Ferrazzi" picture="alice.jpg"> - <URL>http://www.aliceinwire.net/</URL> - <email>aliceinwire@gnumerica.org</email> - - <question1> - <answer><p>Since October 2005</p></answer> - - <question2> - <answer><p>No but I hope to be someday!</p></answer> - - <question3> - <answer><p> - <a - href="https://qa.debian.org/developer.php?login=aliceinwire@gnumerica.org">Packaging - and Maintaining</a>, - <a href="https://wiki.debian.org/Teams/unknown-package">Debian QA unknown package</a>. - I want more people in Debian!!! - </p></answer> - - <question4> - <answer><p> - When I saw Debian for the first time in 2005 I was really - impressed by the stability and security of Sarge for networking. - Most of all I was impressed by the activity of the Debian Women Project. - </p></answer> - - <question5> - <answer><p> - Debian is in continuous evolving and everyone can contribute in it. - Don't find fault. Find a remedy! There are a lot of packages only waiting - for your <q><a href="http://wnpp.debian.net/">lovin'</a></q> - </p></answer> - - <question6> - <answer><p> - Unfortunately not. - </p></answer> - - <question7> - <answer><p> - I had to start using computers in 2000, I gradually learned more - and more as time went by and I believe that the Debian community - is a fantastic place for learning. Not only does one get to help - the Debian community but it is also a good way to work on - self-improvement. - </p></answer> -</profile> - - diff --git a/greek/women/profiles/amaya.wml b/greek/women/profiles/amaya.wml deleted file mode 100644 index 7a526f1cddb..00000000000 --- a/greek/women/profiles/amaya.wml +++ /dev/null @@ -1,58 +0,0 @@ -#use wml::debian::translation-check translation="737e31d579fb28438d16dc3ad6afeb3a068dbd81" maintainer="galaxico" -<define-tag pagetitle>Amaya Rodrigo Sastre</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Amaya Rodrigo Sastre" picture="amaya.jpg"> - <URL>http://www.amayita.com/</URL> - <email>amaya@debian.org</email> - - <question1> - <answer><p>Since October 1998</p></answer> - - <question2> - <answer><p>Yes!</p></answer> - - <question3> - <answer><p> - Packaging: maintaining my packages - QA: testing and running latest experimental Debian - releases. - Evangelizing: I was in a way responsible for the Spanish - government (among others) to choose to use Debian. - I keep looking for good prospective DD. - I want more women in Debian. - </p></answer> - - <question4> - <answer><p> - I must confess I was encouraged by the guys... Santiago Vila and - Héctor García. I never thought I'd be up to it until they showed an - interest to sponsor me. - </p></answer> - - <question5> - <answer><p> - Be yourself. Take it with a grain of salt. Stay focused on your - goals. Debian is a great community. I wouldn't want to give anyone - a hard time. I enjoy being a DD a lot. It's a fulfilling - experience. Go for it. - </p></answer> - - <question6> - <answer><p> - It's something I have always wanted to do. I started a women - oriented mailing list for the Spanish speaking some years ago. It - was a huge failure ;-( Nowadays I am involved with: - <a href="http://www.systers.org/">Systers</a>; - Women and Free Software (Spanish local effort). - (Mujeresred-softwarelibre) - </p></answer> - - <question7> - <answer><p> - I was supposed to be an English teacher. Or a technical translator. - Free Software gave me a chance to change my destiny, grow up as a - person, find new goals and motivations. - </p></answer> -</profile> diff --git a/greek/women/profiles/brenda.wml b/greek/women/profiles/brenda.wml deleted file mode 100644 index 4bcaa881c1d..00000000000 --- a/greek/women/profiles/brenda.wml +++ /dev/null @@ -1,43 +0,0 @@ -#use wml::debian::translation-check translation="737e31d579fb28438d16dc3ad6afeb3a068dbd81" maintainer="galaxico" -<define-tag pagetitle>Brenda J. Butler</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Brenda J. Butler" picture=""> - <URL>https://sourcerer.ca</URL> - <email>bjb@sourcerer.ca</email> - - <question1> - <answer><p>I started using Debian around the time potato was released, wow, -around 2000. I switched from RedHat when they stopped supporting -the Sparc architecture. Since that time, I switched to Intel/AMD -based machines, but stuck with Debian.</p></answer> - - <question2> - <answer><p>No.</p></answer> - - <question3> - <answer><p>A devoted user. I file the occasional bug, help the occasional -person on irc, answer the occasional Debian mailing list question. -Ask the occasional question.</p></answer> - - <question6> - <answer><p> -I mentored at a Ladies Learning Code event a while ago. - - </p></answer> - - <question7> - <answer><p> -I'm a programmer, mainly on *nix platforms. - -My non-computing activities include knitting, contradancing, home cooking. - -My (current) GPG key fingerprint is -030F AFB9 85A4 ACF1 4AD7 A1B9 CE75 CB63 AA20 E051. - -This info was supplied 2014/Oct/14. - - - </p></answer> -</profile>
\ No newline at end of file diff --git a/greek/women/profiles/elizabeth.wml b/greek/women/profiles/elizabeth.wml deleted file mode 100644 index 7cfa8c8b527..00000000000 --- a/greek/women/profiles/elizabeth.wml +++ /dev/null @@ -1,82 +0,0 @@ -#use wml::debian::translation-check translation="08da87bf88f0132c810bd37c7312b5d0c4675a51" maintainer="galaxico" -<define-tag pagetitle>Elizabeth K. Joseph</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Elizabeth K. Joseph" picture="elizabeth.png"> - <URL>https://princessleia.com</URL> - <email>lyz@princessleia.com</email> - - <question1> - <answer><p>Since 2002.</p></answer> - - <question2> - <answer><p>No.</p></answer> - - <question3> - <answer><p> - These days I host the Debian dinner for the San Francisco Bay Area -Debian (bad.debian.net) group every other month where we chat about -Debian, sign keys and welcome traveling Debian contributors who -frequently attend our dinners. I also pitch in with the Debian News -team here and there, sharing links when I come across them and since -attending DebConf14 in Portland have started to also pitch in with -summary writing and editorial review. - -As a bit of background, I got started with working on Debian with -Debian packaging in 2006 when I was working for a company that was -using a number of Debian packages internally for some of our -applications. In that role I was also able to work with a Debian -Developer on staff to get a couple tools into the Debian archive. I -also spent some time working on PHP Pear packages. I've since shifted -focus in my day job so it's been some time since I've been involved -with packaging, though I'd love to get back into it. - </p></answer> - - <question4> - <answer><p> -I love contributing to open source software, so it was pretty natural -for me to be interested in learning about packaging after I'd been -using Debian on my home computers for a couple years. As I mentioned, -it was actually a paying job that finally got me to do packaging, -since we were using the packages in our infrastructure at work. - -My relation to the news team started because I'm the editor for the -Ubuntu Weekly Newsletter, I routinely come across Debian-related -articles when looking for Ubuntu ones, so it made sense for me to -start sharing those. - - </p></answer> - - <question5> - <answer><p> -Dive in, ask questions and don't get discouraged. Debian is -complicated, and there are lots of ways to do things, so it's easy -even for the smartest people to get lost. There are lots of teams -inside of Debian for whatever you may be interested in, and most of -them are eager to get new contributors so they're happy to help you -out. You're also welcome to ask folks on the Debian Women mailing list -and IRC channel, there are plenty of helpful folks there who can point -you in the right direction. - </p></answer> - - <question6> - <answer><p> -I spent several years working with the Ubuntu Women project -(ubuntu-women.org), which seeks to get more women involved with and -using Ubuntu. - </p></answer> - - <question7> - <answer><p> -My day job is a Systems Administrator working on the fully open source -infrastructure that OpenStack developers use, it's really exciting to -blend my passion for open source with my skills as a sysadmin. The -OpenStack project uses a large Continuous Integration (CI) system, so -I'm very interested in keeping an eye on what the Debian project does -with CI work moving forward. - -I also am on the board of directors for Partimus.org, a non-profit -which puts Linux-based desktops into schools in need. - </p></answer> -</profile>
\ No newline at end of file diff --git a/greek/women/profiles/erinn.wml b/greek/women/profiles/erinn.wml deleted file mode 100644 index 0ef7a6e72ee..00000000000 --- a/greek/women/profiles/erinn.wml +++ /dev/null @@ -1,57 +0,0 @@ -#use wml::debian::translation-check translation="08da87bf88f0132c810bd37c7312b5d0c4675a51" maintainer="galaxico" -<define-tag pagetitle>Erinn Clark</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Erinn Clark" picture="erinn.jpg"> - <URL></URL> - <email>erinn@debian.org</email> - - <question1> - <answer><p> - Since 2003. - </p></answer> - - <question2> - <answer><p> - Yes. - </p></answer> - - <question3> - <answer><p> - Packaging, the Debian Women Project, torturing my sparc64 with d-i tests. - </p></answer> - - <question4> - <answer><p> - Initially, it was the community. What keeps me with Debian is its - integrity and commitment to freedom and technical - excellence. - </p></answer> - - <question5> - <answer><p> - Certainly. Rule number one: Don't be afraid. The Debian - community has acquired a bit of a reputation, and it is always wise - to observe before one jumps in head first, but do not be put off by - the mailing lists. There are a great many friendly and helpful - people to be found. Find a subsection of Debian that you can be a - part of which will value your contributions. Participate on the - Debian Women mailing list. We will certainly be able to find you - many things to do that you might not have thought of yourself. - Likewise, look at the <a href="$(WOMEN)/participate">involvement</a> page for ideas on how to get started. - </p></answer> - - <question6> - <answer><p> - Yes, <a href="http://linuxchix.org">LinuxChix</a> occasionally. - </p></answer> - - <question7> - <answer><p> - <i>Noli me tangere, for Caesar's I am,<br /> - And wild for to hold, though I seem tame.</i><br /> - -- Whoso List to Hunt, Sir Thomas Wyatt - </p></answer> -</profile> - diff --git a/greek/women/profiles/fernanda.wml b/greek/women/profiles/fernanda.wml deleted file mode 100644 index 864ee8de9b3..00000000000 --- a/greek/women/profiles/fernanda.wml +++ /dev/null @@ -1,68 +0,0 @@ -#use wml::debian::translation-check translation="08da87bf88f0132c810bd37c7312b5d0c4675a51" maintainer="galaxico" -<define-tag pagetitle>Fernanda G. Weiden</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Fernanda G. Weiden" picture="nanda.jpg"> - <URL></URL> - <email>fernanda@softwarelivre.org</email> - - <question1> - <answer><p> - Since the 22nd of November of 2003. - </p></answer> - - <question2> - <answer><p> - Not yet. - </p></answer> - - <question3> - <answer><p> - Packaging. (<a - href="https://qa.debian.org/developer.php?login=fernanda@softwarelivre.org">officially</a> - and <a - href="http://people.softwarelivre.org/~fernanda/packages/">unofficially</a>), - advocacy. - </p></answer> - - <question4> - <answer><p> - Its adherence to principles and the development model. Also, it feels - good taking part on the creation of something I use daily. - </p></answer> - - <question5> - <answer><p> - Do not be intimidated is the first advice, but mainly, have people - know about your work and do not let anyone diminish it. Something - I've been noticing since I started working with women's groups inside - the Free Software community is that many women are there taking part, - but just a small number of them expose their ideas. Give priority to - that. having an opinion, even if it is not the brightest, is better - than having none or hiding it so nobody knows about it. Any idea is a - bright idea when people around you get to know it. - </p></answer> - - <question6> - <answer><p> - Yes! I am one of the founders of <a - href="http://mulheres.softwarelivre.org/">PSL-Mulheres</a> (Projeto - Software Livre Mulheres). We work on projects to increase digital - inclusion of women, assist feminist NGO's and social groups with - understanding and using Free Software. - </p></answer> - - <question7> - <answer><p> - I work for IBM as a developer at their Linux Technology Center - installed at UNICAMP, a university of the State of São Paulo. I - became involved with Free Software in 1997. I still haven't finished - university, although I've started two university courses, already: - mathematics, and computer science, but I'm planning to start (and - finish, this time) a technology-related course real soon - now. - </p></answer> -</profile> - - diff --git a/greek/women/profiles/hanna.wml b/greek/women/profiles/hanna.wml deleted file mode 100644 index 8f3730e4e0e..00000000000 --- a/greek/women/profiles/hanna.wml +++ /dev/null @@ -1,78 +0,0 @@ -#use wml::debian::translation-check translation="08da87bf88f0132c810bd37c7312b5d0c4675a51" maintainer="galaxico" -<define-tag pagetitle>Hanna Wallach</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Hanna Wallach" picture="hanna.jpg"> - <URL>https://dirichlet.net</URL> - <email>hanna@join-the-dots.org</email> - - <question1> - <answer><p> - Since April 1999 - </p></answer> - - <question2> - <answer><p> - Not yet; I plan to enter the New Maintainer process within the next - couple of months, however. - </p></answer> - - <question3> - <answer><p> - My primary contribution to the Debian project is packaging. I - currently co-maintain one package and have just filed an ITP (Intent - to Package) for another.<br /> I also take an active role in - couraging others to use Debian. I believe that one of the most - important ways to support the growth of a project like Debian is to - encourage people to find out more and, if interested, get involved. - Over the past few years, I have initiated both formal and informal - discussions about Debian with a variety of individuals, and helped - run several Debian installfests. - </p></answer> - - <question4> - <answer><p> - Debian has one of the most active and interesting developer - communities of any Linux distribution - it was this that originally - drew me to the project. - </p></answer> - - <question5> - <answer><p> - Think about what you'd like to contribute to Debian, and what - you hope to gain from your involvement. On a more practical level, - help fix bugs, take over orphaned packages, check the <a - href="https://www.debian.org/devel/wnpp/">WNPP</a> (Work-Needing and - Prospective Packages) regularly, and do read the <a - href="https://lists.debian.org/">Debian mailing lists</a> - they're - all a great way to learn more about the Debian community and - ethos. - </p></answer> - - <question6> - <answer><p> - I'm part of the <a - href="http://www.cl.cam.ac.uk/women/">Women@CL</a> project, a - Cambridge-based initiative that provides local, national and - international activities for women engaged in computing research and - academic leadership. I'm also a member of <a - href="http://www.seas.upenn.edu/~cisters/">CISters</a>, an informal - group of graduate women in the University of Pennsylvania's - Department of Computer and Information Science. - </p></answer> - - <question7> - <answer><p> - I got my BA from the University of Cambridge Computer - Laboratory, after transferring into the Computer Science Tripos from - Engineering during my second year. Since then, I've completed an MSc - at the University of Edinburgh, where I specialised in neural - computing and learning from data, and have started a PhD in - Cambridge's Inference Group. When not working on my PhD, I spend an - inordinate amount of time drinking coffee, playing with computers, - contributing to the Debian project, and updating my <a - href="http://join-the-dots.org/">blog</a>. - </p></answer> -</profile> - diff --git a/greek/women/profiles/helen.wml b/greek/women/profiles/helen.wml deleted file mode 100644 index 27330367ebb..00000000000 --- a/greek/women/profiles/helen.wml +++ /dev/null @@ -1,67 +0,0 @@ -#use wml::debian::translation-check translation="737e31d579fb28438d16dc3ad6afeb3a068dbd81" maintainer="galaxico" -<define-tag pagetitle>Helen Faulkner</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Helen Faulkner" picture="helen.jpg"> - <email>helen_ml_faulkner@debian.org</email> - - <question1> - <answer><p> - Since about 2000. I'm not exactly sure - it seems like a long time - ago. My housemate foisted Debian on me for his own amusement, and - it grew from there... - </p></answer> - - <question2> - <answer><p> - Yes. - </p></answer> - - <question3> - <answer><p> - I'm packaging several useful and/or funny KDE panel applets - as well as a little thing I wrote myself (kdoomsday) and labplot - (a great scientific plotter). I may take on a couple of others - soon. - I'm active on the Debian Women mailing list. I'm interested - in seeing Debian become a community that is more varied and more - accessible to groups that are currently under-represented. - </p></answer> - - <question4> - <answer><p> - Mainly I'm really interested in how it all works. I enjoy - learning how to package things, how the system is put together, etc. - And I like volunteer work. - </p></answer> - - <question5> - <answer><p> - Just do it. It's not as scary as you might think. Get into - the Debian Women mailing list and ask people, read the information - on the website, join us on IRC. There are a lot of friendly and - helpful people about. - </p></answer> - - <question6> - <answer><p> - Nope. - </p></answer> - - <question7> - <answer><p> - I'm a physicist with an interest in technology and - programming. When I'm not being those things I'm into music, - sailing, dogs and whatever takes my interest at the time. I've done - volunteer stuff in all of those areas and others. In my experience - you get back more than you put in, if you are prepared to take time - to help other people out in a way that you enjoy.<br /><br /> - - I like the ideals of the free/open-source software movement, not to - mention the excellent software you get to use! I would like to see - more women involved in that world, and Debian specifically, because - I know women have a lot to contribute. - </p></answer> -</profile> - diff --git a/greek/women/profiles/index.wml b/greek/women/profiles/index.wml deleted file mode 100644 index a4e5106ce19..00000000000 --- a/greek/women/profiles/index.wml +++ /dev/null @@ -1,19 +0,0 @@ -#use wml::debian::template title="Debian Women profiles" -#use wml::debian::users_list -#use wml::debian::translation-check translation="5a7a3715c7867ab7fa464be77965b7cf5050e2c0" maintainer="galaxico" - -<:= get_users_list ('$(ENGLISHDIR)/women/profiles', '.' , '(?!index).*') :> - - <h3>Submit your bio for the Profiles page</h3> - <p> - Are you a Debian volunteer, package maintainer, translator, or HOWTO - author? We would like to recognize you for your hard work by adding - you to our <a href="$(WOMEN)/profiles/">profiles</a> page of women who - have contributed to Debian. Please tell us about yourself and your - efforts by answering some questions and submitting your answers to <a - href="mailto:larjona@debian.org">Laura Arjona</a>. - - Thanks to Meike Reichle for her previous dedication to this task. - </p> - - diff --git a/greek/women/profiles/katharina.wml b/greek/women/profiles/katharina.wml deleted file mode 100644 index a009f20621e..00000000000 --- a/greek/women/profiles/katharina.wml +++ /dev/null @@ -1,45 +0,0 @@ -#use wml::debian::translation-check translation="08da87bf88f0132c810bd37c7312b5d0c4675a51" maintainer="galaxico" -<define-tag pagetitle>Katharina Sabel</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Katharina Sabel (aka SpaceKookie)" picture=""> - <URL></URL> - <email>sabel.katharina@gmail.com</email> - <question1> - <answer><p> -For about 1 ½ years now. Though I have been using Debian based distributions since I was 15 (and I’m 21 now) -</p></answer> - - <question2> - <answer><p>I am a software developer but not specifically a Debian dev. -</p></answer> - - <question3> - <answer><p> -Not really anything apart from getting people to ditch Windows and install Linux (aka Debian) -</p></answer> - - <question4> - <answer><p> -I do/ want to contribute to the Debian community because I think it is important to have free and open-source software to use, Debian is a great operating system and I like the idea of groups like the Debian Women. - - </p></answer> - - <question5> - <answer><p> -Not really as I don’t really know what I’m doing yet either. I think being involved in the forums and IRC channels is a good start, get involved with other people working on Debian, learn about technology that fascinates you. - </p></answer> - - <question6> - <answer><p> -Unfortunately None. - - </p></answer> - - <question7> - <answer><p> -I’m 21 years old, I study computer science at the Humboldt University in Berlin. I develop software in my free time and I really love cats :3 - - </p></answer> -</profile>
\ No newline at end of file diff --git a/greek/women/profiles/larissa.wml b/greek/women/profiles/larissa.wml deleted file mode 100644 index 7087be853f8..00000000000 --- a/greek/women/profiles/larissa.wml +++ /dev/null @@ -1,52 +0,0 @@ -#use wml::debian::translation-check translation="737e31d579fb28438d16dc3ad6afeb3a068dbd81" maintainer="galaxico" -<define-tag pagetitle>Larissa Reis</define-tag>
-#use wml::debian::profiles
-#include "$(ENGLISHDIR)/women/profiles/profiles.def"
-
-<profile name="Larissa Reis" picture="">
-
- <URL></URL>
- <email></email>
-
- <question1>
- # How long have you been using Debian?
- <answer><p>
- I had my first contact with Free Software and open source philosophy when I got into University in 2009. Thankfully, a few years before, some of my seniors advocated the use of only open source software in our department laboratories, despite ongoing resistance from other students and some staff. Debian was their distro of choice in our University labs, but I was using Ubuntu from 2009 until 2012, when I finally changed to Debian. I've been using Debian exclusively ever since :-)
- </p></answer>
-
- <question2>
- # Are you a Debian Developer?
- <answer><p>
- Nope. Maybe someday.
- </p></answer>
-
- <question3>
- # What areas of Debian are you involved in?
- <answer><p>
- I help package python modules as a member of the Debian Python Modules Team.
- </p></answer>
-
- <question4>
- # What got you interested in working with Debian?
- <answer><p>
- I was inspired by people I work with who work with Debian.
- </p></answer>
-
- <question5>
- # Do you have any tips for women interested in getting more involved with Debian?
- <answer><p>
- Don't be afraid to ask, there are no stupid questions. debian-mentors and debian-women IRC channels are very helpful.
- </p></answer>
-
- <question6>
- # Are you involved with any other women in technology group? Which one(s)?
- <answer><p>
- I help as mentor in <a href="http://railsgirls.com/">RailsGirls</a> events, which aims to show girls programming is easy and everybody can learn how to do it :-)
- </p></answer>
-
- <question7>
- # A bit more about you...
- <answer><p>
- I'm a computer scientist from Brazil working with Web Development. I'm studying for a masters in computer science, focused on network research and working primarily with performance optimization for Optical Networks. You can contact me at larissa @ IRC freenode or IRC OFTC
- </p></answer>
-</profile>
\ No newline at end of file diff --git a/greek/women/profiles/marga.wml b/greek/women/profiles/marga.wml deleted file mode 100644 index 6513b5f92ea..00000000000 --- a/greek/women/profiles/marga.wml +++ /dev/null @@ -1,93 +0,0 @@ -#use wml::debian::translation-check translation="08da87bf88f0132c810bd37c7312b5d0c4675a51" maintainer="galaxico" -<define-tag pagetitle>Margarita Manterola</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Margarita Manterola" picture="marga.jpg"> - <URL>https://www.marga.com.ar/blog</URL> - <email>marga@debian.org</email> - - <question1> - <answer><p> - I've been using Debian since 2000. At first I was just a - simple user, but with time I grew more involved, first reporting - bugs, then submitting patches, and by 2004 I started maintaining - packages. - <br /><br /> - A turning point in my life was the - <a href="https://wiki.debian.org/DebConf4">DebConf4</a> in Brazil, - where I was able to meet a lot of Debian Developers, - put faces to names and learn a lot about how Debian works. - I highly recommend that people attend DebConf and meet people - there. It's been a long time, and by this time I have the feeling - that Debian people are part of my extended family. - </p></answer> - - <question2> - <answer><p> - Yes. I became a Debian Developer on November 13th, 2005. - </p></answer> - - <question3> - <answer><p> - I maintain some packages but not too many, the biggest thing - regarding packaging that I do is participate in the team that - maintains the Cinnamon Desktop Environment. - <br /><br /> - Also, I've been very actively involved in the organization of - several DebConfs, particularly for - <a href="https://wiki.debian.org/DebConf8">DebConf8</a>, - which took place in my country, Argentina. - Later on I moved to Germany and also took an active part - of the organization of DebConf15, in Heidelberg. - On top of this, I particularly enjoy doing QA: - I've done quite a lot of NMUs to fix RC bugs in packages - that were not fit for a release, and I usually have a lot of fun - participating on Bug Squashing Parties. I am part of the - anti-harassment team, trying to make Debian a safe place where - everyone is welcome and can express themselves. - I am also part of the Technical Committee, which is the body - that helps make difficult technical decisions. - </p></answer> - - <question4> - <answer><p> - The free software philosophy. I liked that it was developed - by a community instead of a company, and that my contributions - could be accepted if they were worthy.<br /><br /> Also, the magic - of apt-get and the immense repository. I usually have this - perception that if something is not in Debian, it's not worth using - it (and if it is, then I can make it my responsibility to make sure - that it's packaged and uploaded). What has kept me interested - in working in Debian over the years is that there's always - more work to be done, more software to get into Debian, - more bugs to fix, more new ideas to try out. - </p></answer> - - <question5> - <answer><p> - There are many things to do in Debian, and usually the hardest part - is to find where you will fit. For example, if you are into - programming, look for a team that maintains packages in a - programming language that you like and join them. - If you are like me and like to fix many small bugs, - look at the list of bugs and try to find the fix for one. - There are lots of easy ones, and people will be really grateful - that you took the time to fix the bugs. But even if you are not - into code or bug fixing, there are many things to do. - We need better graphical design, we need better documentation, - we need translations, and many many more things. - </p></answer> - - <question7> - # A bit more about you... - <answer><p> - I've been mostly a Python Programmer for more than 10 years. - I lived in Argentina until 2012, and then moved to Munich, Germany - to work for Google as a Site Reliability Engineer. - <br /><br /> - I've been married to Maximiliano Curia (another DD) since 2004 - (DebConf4 was our honeymoon trip!) - </p></answer> -</profile> - diff --git a/greek/women/profiles/mechtilde.wml b/greek/women/profiles/mechtilde.wml deleted file mode 100644 index ab705045ea8..00000000000 --- a/greek/women/profiles/mechtilde.wml +++ /dev/null @@ -1,75 +0,0 @@ -#use wml::debian::translation-check translation="6cc946cc2a23489bd6745d24425db8d5f07005c0" maintainer="galaxico" -<define-tag pagetitle>Mechtilde Stehmann</define-tag>
-#use wml::debian::profiles
-#include "$(ENGLISHDIR)/women/profiles/profiles.def"
-
-<profile name="Mechtilde Stehmann" picture="">
-
- <URL></URL>
- <email>ooo@mechtilde.de</email>
-
- <question1>
- # How long have you been using Debian?
- <answer><p>
- My first installation of Debian was Woody (3.0) in 2002.
- </p></answer>
-
- <question2>
- # Are you a Debian Developer?
- <answer><p>
- In November 2015 I become a Debian Maintainer.
- </p></answer>
-
- <question3>
- # What areas of Debian are you involved in?
- <answer><p>
- I start my work for Debian with some translations in the wiki and some bugreports. In November 2013 I published my first package Loook. Now I also maintain libreoffice-canzeley-client and calendar-exchange provider.
- </p></answer>
-
- <question4>
- # What got you interested in working with Debian?
- <answer><p>
- I want to make Debian more useful for "normal users" especially around Office applications.
- </p></answer>
-
- <question5>
- # Do you have any tips for women interested in getting more involved with Debian?
- <answer><p>
- They should answer the following questions for themselves: What are your skills? What are your interests? How can you use it to make Debian more popular? There are a lot of skills useful in Debian, not only programming and packaging.
- </p></answer>
-
- <question6>
- # Are you involved with any other women in technology group? Which one(s)?
- <answer><p>
- No specific group.
- </p></answer>
-
- <question7>
- # A bit more about you...
- <answer>
- <p>
- I am a Debian-Woman from North Rhine Westfalia in Germany.
- I also work on Apache OpenOffice and being there a member of the PMC.
- I translate parts of the Gnucash documentation to German.
- <br /><br />
-
- iRC: Mechtilde, #debian.de, #debian-women at OFTC
- Mechtilde #dev.openoffice.org,#openoffice.org,#openoffice.org-de at Freenode
- </p>
- <div>
- <strong>Debian Maintainer</strong>
- <ul>
- <li>My bugs : ooo@mechtilde.de</li>
- <li>
- My packages :
- <ul>
- <li>* loook</li>
- <li>* libreoffice-canzeley-client</li>
- <li>* calendar-exchange-provider</li>
- </ul>
- </li>
- <li>My QA page : <a href="https://qa.debian.org/developer.php?login=ooo@mechtilde.de">https://qa.debian.org/developer.php?login=ooo@mechtilde.de</a></li>
- </ul>
- </div>
- </answer>
-</profile>
diff --git a/greek/women/profiles/meike.wml b/greek/women/profiles/meike.wml deleted file mode 100644 index a56e5109d3e..00000000000 --- a/greek/women/profiles/meike.wml +++ /dev/null @@ -1,85 +0,0 @@ -#use wml::debian::translation-check translation="08da87bf88f0132c810bd37c7312b5d0c4675a51" maintainer="galaxico" -<define-tag pagetitle>Meike Reichle</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Meike Reichle" picture="meike.jpg"> - <URL></URL> - <email>meike@debian.org</email> - - <question1> - <answer><p> - I started collecting first Linux experiences somewhen - in the mid to late 90s, when a friend of mine put Linux on his - machine and showed me what it could do. I was quite - fascinated but couldn't try it out myself since I didn't have - a computer of my own (computers used to be classical boys toys - at that time) and fiddling with the family 486 was a total - no-go. When I started studying at the university in 2001 I finally - bought the first computer of my own. Working on the University's - Unix terminals quickly got me hooked on *nixes. From 2001 - to 2004 I on and off tried several different distributions - (Mandrake, RedHat, Gentoo, even Solaris x86), but none of them - fully convinced me. In 2004 I finally switched to Debian and - have never looked back since then. - </p></answer> - - <question2> - <answer><p> - Yes, since 2008. - </p></answer> - - <question3> - <answer><p> - I maintain packages and am one of currently three delegated Debian - Press Officers. - Besides my press work I do a lot of travelling to represent Debian at - all kinds of Linux and Free Software events, usually by - staffing/organising Debian booths and giving talks on all things - Debian and Free Software related. - I am, by now, also somewhat of a Debian Women veteran :). - </p></answer> - - <question4> - <answer><p> - I tried a few other Unix and Linux distributions before I - finally ended up with Debian. After using it for some time I decided - that I liked the project so much that I wanted to be a part of it. I - started of by reading and writing on mailing lists and irc and then - got more and more involved until I finally applied for a developer - account myself. - </p></answer> - - <question5> - <answer><p> - Don't be shy. Don't give up after the first failure, nor after the - second or third. Debian and the people in it sometimes need some time - to get acquainted with, but it's definitely worth it! I guess the - best is to find a niche that fits your interests and begin working - there, getting more and more involved in the whole project as times - goes on. - </p></answer> - - - <question6> - <answer><p> - I am subscribed to several mailing lists at <a - href="http://www.technixen.net/">technixen.net</a>, a German - platform for women in different areas of computing. Also I am a <a - href="http://www.cybermentor.de/">Cyber Mentor</a> and have by now - acquired something like a reputation for giving <q>Non-Dogmatic Women - in IT Talks</q>. - </p></answer> - - <question7> - <answer><p> - I've got my Master's Degree (<q>Magister</q>) in Information Sciences - and work as Project Manager at an embedded Linux company. - In my spare time I like crafting and all sort of DIY activities. - I read a lot (mostly SF), like to listen to music (mostly ska, punk - and blues), love to travel and always enjoy meeting - fellow Debianists at the places I travel to. - </p></answer> -</profile> - - diff --git a/greek/women/profiles/miriam.wml b/greek/women/profiles/miriam.wml deleted file mode 100644 index a8ac8c6ec1c..00000000000 --- a/greek/women/profiles/miriam.wml +++ /dev/null @@ -1,69 +0,0 @@ -#use wml::debian::translation-check translation="737e31d579fb28438d16dc3ad6afeb3a068dbd81" maintainer="galaxico" -<define-tag pagetitle>Miriam Ruiz</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Miriam Ruiz" picture="miriam.jpg"> - <email>little_miry@yahoo.es</email> - - <question1> - <answer><p> - For some years now: I started using Potato. It has only - become my main system for the last year and a half or so, - anyway. - </p></answer> - - <question2> - <answer><p> - No, not yet, but I maintain some packages for Debian. I'd - like to enter NM process as soon as I can. - </p></answer> - - <question3> - <answer><p> - Mainly packaging, writing some documentation and - translating a few things. I'm also quite involved in teaching other - people how to package things for Debian and trying to get more - girls into the Free Software World. - </p></answer> - - <question4> - <answer><p> - It's not the first time I have given a bit of my time to a - Free Software Project, but I've never been as involved in one as I - am in Debian. What I value the most is the freeness of the project - as well as the community around it. I think that the most important - part of Debian is its social side, both in its development and in - its goals. - </p></answer> - - <question5> - <answer><p> - First of all, enjoy what you do, or do things you enjoy. - Second, don't let anyone scare you, Debian is a big community in - which most of the people are very nice and kind, even though there - might be some trolls around sometime. You'll have to learn a lot - and go through a bunch of documents, so be patient, Rome wasn't - built in a day. If you ever have doubts, just ask. Finally, if your - English is not so good, try to improve it as much as you can. At - the moment English is the main language in which Debian is - developed. - </p></answer> - - <question6> - <answer><p> - Yes, I've joined some other groups like LinuxChix, Systers - or ChicasLinux, and I'm very involved in a new group we're creating - called Alixa. - </p></answer> - - <question7> - <answer><p> - I'm a Spanish girl who's always, since I was very little, - has been interested in computers and technology. I also like - reading a lot, my favourite books are "Momo" by Michael Ende (yes, - the author of "The Neverending Story") and "The Little Prince" by - Antoine de Saint Exupéry. Apart from that I like a lot being with - my friends, travelling and learning things. - </p></answer> -</profile> diff --git a/greek/women/profiles/solveig.wml b/greek/women/profiles/solveig.wml deleted file mode 100644 index 14575a02330..00000000000 --- a/greek/women/profiles/solveig.wml +++ /dev/null @@ -1,47 +0,0 @@ -#use wml::debian::translation-check translation="9bd1612c99ab421989a44d574a12d1409018e2ba" maintainer="galaxico" -<define-tag pagetitle>Solveig</define-tag>
-#use wml::debian::profiles
-#include "$(ENGLISHDIR)/women/profiles/profiles.def"
-
-<profile name="Solveig" picture="">
-
- <question1>
- # How long have you been using Debian?
- <answer>
- I've been using Debian since around 2004. I contribute to it since 2013 only :)
- </answer>
-
- <question2>
- # Are you a Debian Developer?
- <answer>
- Nope. I might become a non-uploading DD at some point, but not yet.
- </answer>
-
- <question3>
- # What areas of Debian are you involved in?
- <answer>
-<p>
- I mostly contribute to Tails, a Debian derivative.
-</p>
-<p>
- In Debian, I did some bug triaging, translations, and participated to 2 DebConfs so far :)
-</p>
- </answer>
-
- <question4>
- # What got you interested in working with Debian?
- <answer>
- I was using Debian since a long time, and contributing to Tails since the beginning, so at some point I was interested in bringing back to upstream.
- </answer>
-
- <question5>
- # Do you have any tips for women interested in getting more involved with Debian?
- <answer>
-<p> It helps to find a team where people work on things that interest you and are willing to mentor your beginnings in Debian. Most teams are happy to welcome new people :)
-</p>
-<p>
- Also don't hesitate to join the debian-women irc chan, mailing-list and events. The activity varies, but it's a fabulous bunch of people :)
-</p>
- </answer>
-
-</profile>
\ No newline at end of file diff --git a/greek/women/profiles/template.wml b/greek/women/profiles/template.wml deleted file mode 100644 index 43aa25b4827..00000000000 --- a/greek/women/profiles/template.wml +++ /dev/null @@ -1,57 +0,0 @@ -#use wml::debian::translation-check translation="c3a3b8986d2ffef95ef7bb8f7d99f36678ff0e8f" maintainer="galaxico" -<define-tag pagetitle>Template for new Debian Women profile</define-tag> -#use wml::debian::profiles -#include "$(ENGLISHDIR)/women/profiles/profiles.def" - -<profile name="Template for new Debian Women profile" picture=""> - # IN THE ABOVE LINES, CHANGE "Template for new Debian Women profile" FOR THE NAME OF WOMAN. - - Download the template: - # REMOVE THE ABOVE LINE ("Download the template") - - <url>https://salsa.debian.org/webmaster-team/webwml/blob/master/english/women/profiles/template.wml</url> - # CHANGE THE URL TO THE URL OF WOMAN'S WEBSITE, IF ANY - <email></email> - - <question1> - # How long have you been using Debian? - <answer><p> - your answer - </p></answer> - - <question2> - # Are you a Debian Developer? - <answer><p> - your answer - </p></answer> - - <question3> - # What areas of Debian are you involved in? - <answer><p> - your answer - </p></answer> - - <question4> - # What got you interested in working with Debian? - <answer><p> - your answer - </p></answer> - - <question5> - # Do you have any tips for women interested in getting more involved with Debian? - <answer><p> - your answer - </p></answer> - - <question6> - # Are you involved with any other women in technology group? Which one(s)? - <answer><p> - your answer - </p></answer> - - <question7> - # A bit more about you... - <answer><p> - your answer - </p></answer> -</profile> diff --git a/greek/women/profiles/u.wml b/greek/women/profiles/u.wml deleted file mode 100644 index 54143ce977f..00000000000 --- a/greek/women/profiles/u.wml +++ /dev/null @@ -1,53 +0,0 @@ -#use wml::debian::translation-check translation="e16bb4b6d9c24a557e2eb36b0a86e8361cf66605" maintainer="galaxico" -<define-tag pagetitle>U</define-tag>
-#use wml::debian::profiles
-#include "$(ENGLISHDIR)/women/profiles/profiles.def"
-
-<profile name="U" picture="">
-
- <URL></URL>
- <email></email>
-
- <question1>
- # How long have you been using Debian?
- <answer><p>
- I've been using Debian since 2004 on my personal computer and web servers I administer.
- </p></answer>
-
- <question2>
- # Are you a Debian Developer?
- <answer><p>
- I'm currently in the NM queue to become one :)
- </p></answer>
-
- <question3>
- # What areas of Debian are you involved in?
- <answer><p>
- I contribute to <a href="https://wiki.debian.org/AppArmor">AppArmor</a> in Debian and have completed an internship with the <a href="http://outreachy.org/">Outreachy</a> program in 2014. Read <a href="https://apparmor.451f.org/">my blog</a> about this internship. Furthermore, I am involved with packaging privacy related software through the pkg-privacy-tools packaging team (pkg-otr-team & pkg-anonymity-tools team). In the past, I also helped working on Debian related webpages, like the <a href="https://security-tracker.debian.org/tracker/">security tracker</a>.
- </p></answer>
-
- <question4>
- # What got you interested in working with Debian?
- <answer><p>
- I like that Debian is a non commercial and fairly secure distribution, tweakable to perfectly suit my needs, made by excellent individuals :)
- </p></answer>
-
- <question5>
- # Do you have any tips for women interested in getting more involved with Debian?
- <answer><p>
- You do not need to be afraid of not being good enough! People at Debian are keen to help getting you started if you can tell them what you are interested in and what you already know.
- Many things are well documented, but you still need to find them. The <a href="https://wiki.debian.org">Debian wiki</a> is a great place to start.
- </p></answer>
-
- <question6>
- # Are you involved with any other women in technology group? Which one(s)?
- <answer><p>
- In the past I've been teaching women how to take apart computers and put them back together, which is a method I learned from the <a href="http://genderchangers.org/">Genderchangers</a>, but I am not involved with any women in technology group.
- </p></answer>
-
- <question7>
- # A bit more about you...
- <answer><p>
- I work as web developer since over 10 years and got involved with Debian mainly through contributing to <a href="https://tails.boum.org/">Tails</a>, a Debian based live distribution aiming at protecting your privacy and anonymity.
- </p></answer>
-</profile>
|