diff options
Diffstat (limited to 'debian')
54 files changed, 16341 insertions, 0 deletions
diff --git a/debian/NEWS.Debian b/debian/NEWS.Debian new file mode 100644 index 00000000..d4be674a --- /dev/null +++ b/debian/NEWS.Debian @@ -0,0 +1,43 @@ +sisu (2.0.0-1) unstable; urgency=low + + Version 2, introducing some incompatibility as document headers have changed, + compare markup samples[*] provided in: + /usr/share/doc/sisu/v2/sisu_markup_samples/samples and + /usr/share/doc/sisu/v1/sisu_markup_samples/samples + + If postgresql is made use of version 2 also makes its own databases and + leaves those of version 1 untouched + + The version 1 engine remains available and can be invoked using: + sisu --v1 [operations] + + [* version 2 of non-free package sisu-markup-samples provides additional + samples of markup at: + /usr/share/doc/sisu-markup-samples/v2/samples + /usr/share/doc/sisu-markup-samples/v1/samples + sisu-markup-sasmples package is non dfsg as book copyright holders place + some restrictions on what can be done with their work most commonly no + changing of content, and in some non commercial use] + + -- Ralph Amissah <ralph@amissah.com> Sat, 06 Mar 2010 06:50:00 -0500 + +sisu (0.62.0-1) unstable; urgency=medium + + Output directory structure related to images and optional shared source + files has been changed, existing sites will need to be manually adjusted + + * site images: + [outputpath]/_sisu/image_local is now [outputpath]/_sisu/image + + * package images: + [outputpath]/_sisu/image is now [outputpath]/_sisu/image_sys + + shared source if any now is placed in separate directories + + * shared markup text: + [outputpath]/src + + * shared (zipped) sisupods: + [outputpath]/pod + + -- Ralph Amissah <ralph@amissah.com> Sat, 20 Oct 2007 15:04:46 +0100 diff --git a/debian/changelog b/debian/changelog new file mode 100644 index 00000000..04f90721 --- /dev/null +++ b/debian/changelog @@ -0,0 +1,3204 @@ +sisu (2.0.5-1) unstable; urgency=medium + + * new upstream, minor fix release, see upstream changelog + [inter alia: harvest topics; manifest search form for db; sql search form; + db_create issue for sqlite] + + -- Ralph Amissah <ralph@amissah.com> Wed, 31 Mar 2010 19:46:01 -0400 + +sisu (2.0.4-1) unstable; urgency=medium + + * new upstream, minor fix release, see upstream changelog + [inter alia re: use of param title.full, [fix occasional sql load + breakage]] + + -- Ralph Amissah <ralph@amissah.com> Tue, 23 Mar 2010 19:46:41 -0400 + +sisu (2.0.3-1) unstable; urgency=medium + + * new upstream, minor fix release, see upstream changelog + [inter alia fix to occasional odf:odt breakage] + + -- Ralph Amissah <ralph@amissah.com> Mon, 22 Mar 2010 20:11:15 -0400 + +sisu (2.0.2-1) unstable; urgency=medium + + * new upstream, minor fix release, see upstream changelog + [inter alia fix to occasional sql load breakage] + + -- Ralph Amissah <ralph@amissah.com> Sun, 21 Mar 2010 11:27:21 -0400 + +sisu (2.0.1-1) unstable; urgency=medium + + * new upstream, minor fix release, (most significant related to html tables) + see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Wed, 17 Mar 2010 15:44:23 -0400 + +sisu (2.0.0-1) unstable; urgency=low + + * new upstream, introducing v2 with new middle layer and downstream + libraries; includes epub output + + * sisu v2 installed by default as sisu + + * debian/sisu.install now installs version 1 and version 2 libraries + + * debian/control package description adds mention of Epub output introduced + with this version + + * same lintian overrides added to version 2 as were in version 1, some sample + scripts are provided as text, and not intended to be executable + + * debian News provided for this version, warning of incompatibility with + version 1 markup, brought about by change to document header + + -- Ralph Amissah <ralph@amissah.com> Sat, 06 Mar 2010 06:50:00 -0500 + +sisu (1.0.3-1) unstable; urgency=medium + + * upstream, plaintext footnote / endnote fix, and in sample skins + specification of utf-8 (in some cases needed by ruby 1.9.1) + + * move ruby 1.9 branch to 1.9.1 from 1.9.0 (this should address #569888, if + not reopen) (Closes: #569888) + + * update standards version to 3.8.4 (from 3.8.3) + + * medium urgency retained (previous upload transition to testing prevented by + #569888) + + -- Ralph Amissah <ralph@amissah.com> Wed, 17 Feb 2010 11:06:01 -0500 + +sisu (1.0.2-1) unstable; urgency=medium + + * upstream, sample markup document, markup modified, affects document + numbering + + * medium urgency retained, as impedes progress of previous upload, + (modification needed for future consistency) + + -- Ralph Amissah <ralph@amissah.com> Wed, 10 Feb 2010 16:51:20 -0500 + +sisu (1.0.1-1) unstable; urgency=medium + + * upstream contains an odf fix + + * markup samples directory structure, minor adjustments, (and no longer + shared by package sisu_markup_samples, about which, see that package) + + -- Ralph Amissah <ralph@amissah.com> Mon, 08 Feb 2010 21:45:17 -0500 + +sisu (1.0.0-1) unstable; urgency=low + + * version 1 declared and directory structure modified to allow parallel + development of version 2, through introduction v1 directories where + needed (the moving of sample markup files helps account for large + diffs) + + * sisu markup, old style header support dropped to simplify and make cleaner + introduction of version 2 headers, (i.e./e.g. old style headers like + '0~title' are no longer supported, use '@title:') + + * debian/sisu.install explicit mention of a number of files to make debian + switch to version 2 trivial + + * debian/control "conflicts" and "replaces" versions of sisu-markup-samples + (non-free, due to copyright restrictions on modifying original text) 1.0.11 + and older due to package directory structure changes + + * debian/control "recommends" removed for hyperestraier; "suggests" removed + for kdissert + + * debian/sisu.lintian-overrides, maintained with changed directory structure + + * documentation, modified description of command flags -m and -n (in line + with communication on bug report) (Closes: #555496) + + -- Ralph Amissah <ralph@amissah.com> Sun, 20 Dec 2009 19:05:08 -0500 + +sisu (0.71.4-1) unstable; urgency=low + + * new upstream, sql fix, population of databases see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Sat, 29 Aug 2009 23:46:52 -0400 + +sisu (0.71.3-1) unstable; urgency=low + + * new upstream with fix to use imagemagick directly (when imagemagick is + available and rmagick declares versions not in sync) + + * switch to latest Standards-Version 3.8.3 + + -- Ralph Amissah <ralph@amissah.com> Fri, 28 Aug 2009 16:02:11 -0400 + +sisu (0.71.2-1) unstable; urgency=low + + * new upstream with a couple of fixes, see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Sun, 02 Aug 2009 12:01:28 -0400 + +sisu (0.71.1-1) unstable; urgency=low + + * new upstream with relatively minor adjustments that are nonetheless worth + including, see upstream changelog + + * debian/control added imagemagick as ruby 1.9.* rmagick package not yet + available program will system call imagemagick identify where needed + directly in absence of rmagick + + * debian/sisu.install make libraries available to ruby 1.9 currently 1.9.0 + (commencement of further testing awaits imminent upload ruby 1.9.1 and + subsequent build) + + -- Ralph Amissah <ralph@amissah.com> Fri, 24 Jul 2009 21:33:56 -0400 + +sisu (0.71.0-1) unstable; urgency=low + + * upstream lib/sisu version directory moved from v0 to v1 + + * upstream housekeeping, see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Thu, 09 Jul 2009 10:45:01 -0400 + +sisu (0.70.6-1) unstable; urgency=medium + + * fixes to sql interface + + * fix to generated sample search form + + * debian/control sisu-pdf Suggests: evince | pdf-viewer (Closes: #516714) + + * switch to latest version of Debian Policy + (Standards-Version 3.8.2 instead of 3.8.0) + + -- Ralph Amissah <ralph@amissah.com> Wed, 01 Jul 2009 10:58:47 -0400 + +sisu (0.70.5-1) unstable; urgency=low + + * new minor upstream release, see upstream changelog + + * debian/ new year cleaning: + * debian/copyright use parse-able format; + * debian/rules cleanup; + * debian/control fcgi-ruby made a dependency for sisu-postgresql and + sisu-sqlite as sample script needs it, git repo move noted, package + description touched; + * removed sisu.postrm, forced removal on purge /etc/sisu draconian if + it contains admin edits + * minor sorting + + * note git repo moved: + <http://git.sisudoc.org/?p=code/sisu.git;a=summary> + + -- Ralph Amissah <ralph@amissah.com> Sun, 18 Jan 2009 00:38:58 -0400 + +sisu (0.70.4-1) unstable; urgency=medium + + * new upstream, see upstream changelog, sisu-pdf, workaround necessitated by + texlive behaving differently with tilde characters, similar to recent issue + with tetex behavior with "bullet" mark + + -- Ralph Amissah <ralph@amissah.com> Wed, 31 Dec 2008 00:35:29 -0400 + +sisu (0.70.3-1) unstable; urgency=medium + + * new upstream, see upstream changelog, fixes to sqlite3 component and minor + fix and cosmetic modification to some html + + * new dependency on libsqlite3-ruby, now used to populate sqlite3 db + + -- Ralph Amissah <ralph@amissah.com> Wed, 24 Dec 2008 00:08:39 -0400 + +sisu (0.70.2-1) unstable; urgency=medium + + * new upstream, see upstream changelog, includes a fix and a minor + manpage/help update + + -- Ralph Amissah <ralph@amissah.com> Tue, 16 Dec 2008 00:45:19 -0400 + +sisu (0.70.1-1) unstable; urgency=medium + + * new upstream, see upstream changelog, includes fixes, better integration of + harvest, and additional metadata fields + + -- Ralph Amissah <ralph@amissah.com> Sun, 14 Dec 2008 00:31:23 -0400 + +sisu (0.70.0-1) unstable; urgency=low + + * new upstream, see upstream changelog, includes a sisu site metadata harvest + module, version bump for minor syntax alteration, introduction of a + formatting rule for header author / creator field + + -- Ralph Amissah <ralph@amissah.com> Tue, 02 Dec 2008 23:58:12 -0400 + +sisu (0.69.4-1) unstable; urgency=low + + * new upstream, notably includes emacs highlighting for sisu sisu-mode.el + see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Mon, 04 Nov 2008 18:38:01 -0400 + +sisu (0.69.3-1) unstable; urgency=low + + * new upstream, see upstream changelog, contains minor fix in manifest + reporting of markup source files (sisupod (.zip) where provided) + + -- Ralph Amissah <ralph@amissah.com> Fri, 10 Oct 2008 22:28:11 -0400 + +sisu (0.69.2-1) unstable; urgency=low + + * new upstream, see upstream changelog + (sample sisu markup "Free as in Freedom": book index markers included) + + * [debian/changelog corrected previous entry for 0.69.1 (which was a + repetition of 0.69.0)] + + -- Ralph Amissah <ralph@amissah.com> Fri, 19 Sep 2008 19:08:16 -0400 + +sisu (0.69.1-1) unstable; urgency=low + + * new upstream, contains fix, see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Wed, 17 Sep 2008 00:08:08 -0400 + +sisu (0.69.0-1) unstable; urgency=low + + * new upstream, see upstream changelog, many changes + + -- Ralph Amissah <ralph@amissah.com> Tue, 16 Sep 2008 00:38:28 -0400 + +sisu (0.68.0-1) unstable; urgency=medium + + * new upstream, should be easier to maintain, see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Tue, 22 Jul 2008 20:03:58 -0400 + +sisu (0.67.5-1) unstable; urgency=medium + + * texpdf fixes (xetex xelatex processing instruction and for A5 landscape), + see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Sat, 12 Jul 2008 14:49:02 -0400 + +sisu (0.67.4-1) unstable; urgency=medium + + * fixes (remote source files, default processing directory), see upstream + changelog + + -- Ralph Amissah <ralph@amissah.com> Sat, 12 Jul 2008 01:09:52 -0400 + +sisu (0.67.3-1) unstable; urgency=medium + + * fixes, (help env and fix of pdf papersize), see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Thu, 03 Jul 2008 23:04:30 -0400 + +sisu (0.67.2-1) unstable; urgency=medium + + * upstream fix for xetex landscape pdfs + + -- Ralph Amissah <ralph@amissah.com> Wed, 02 Jul 2008 22:13:02 -0400 + +sisu (0.67.1-2) unstable; urgency=medium + + * package updated to follow the last version of Debian Policy + (Standards-Version 3.8.0 instead of 3.7.3) + + -- Ralph Amissah <ralph@amissah.com> Sun, 22 Jun 2008 23:53:28 -0400 + +sisu (0.67.1-1) unstable; urgency=low + + * minor upstream update + + * vim-addon policy compliance (Closes: #464824) + + -- Ralph Amissah <ralph@amissah.com> Tue, 27 May 2008 19:34:22 -0400 + +sisu (0.67.0-1) unstable; urgency=low + + * new upstream, minor modification/simplification of markup syntax for files + imported to a composite/master document results in automatic version bump, + see upstream changelog and man pages + + * vim syntax modified to reflect change in markup syntax + + * debian / vim-addon-manager, investigate use of + + -- Ralph Amissah <ralph@amissah.com> Thu, 22 May 2008 22:01:19 -0400 + +sisu (0.66.3-1) unstable; urgency=low + + * new upstream, see upstream changelog + + * debhelper 7 + + * debian/control vcs info added + + -- Ralph Amissah <ralph@amissah.com> Sun, 11 May 2008 14:29:34 -0400 + +sisu (0.66.2-1) unstable; urgency=low + + * new upstream, see upstream changelog + + * ruby-dbi dependencies in sisu-postgresql ruby and sisu-sqlite refer to + ruby version 1.8 + + -- Ralph Amissah <ralph@amissah.com> Fri, 25 Apr 2008 04:44:31 +0100 + +sisu (0.66.1-1) unstable; urgency=low + + * new upstream, see changelog + + * debhelper (>= 6) + + * sisu-pdf recommends texlive-xetex + + * [this changelog, cleaned trailing whitespaces] + + -- Ralph Amissah <ralph@amissah.com> Sun, 30 Mar 2008 02:02:54 +0100 + +sisu (0.66.0-1) unstable; urgency=low + + * new upstream, (version bump markup tag related) see changelog + + -- Ralph Amissah <ralph@amissah.com> Sun, 24 Feb 2008 22:44:20 +0000 + +sisu (0.65.0-1) unstable; urgency=low + + * new upstream, (version bump markup tag related) see changelog + + -- Ralph Amissah <ralph@amissah.com> Sat, 16 Feb 2008 02:56:00 +0000 + +sisu (0.64.4-1) unstable; urgency=low + + * new upstream, minor, see changelog, (markup tag related) + + * debian control description db names PostgreSQL and SQLite the former + requested by lintian + + -- Ralph Amissah <ralph@amissah.com> Thu, 14 Feb 2008 06:11:58 +0000 + +sisu (0.64.3-1) unstable; urgency=low + + * new upstream minor, see changelog, (related to open source ecosystem + upgrade transition: ruby 1.9; postgresql 8.3 [interim]) + + -- Ralph Amissah <ralph@amissah.com> Wed, 06 Feb 2008 00:21:00 +0000 + +sisu (0.64.2-1) unstable; urgency=low + + * new upstream, minor, see changelog + + * debian/control permit use with ruby 1.8 upgrade + (however limit retained on use with ruby 1.9) + + -- Ralph Amissah <ralph@amissah.com> Sat, 19 Jan 2008 03:37:11 +0000 + +sisu (0.64.1-1) unstable; urgency=medium + + * new upstream with odf bugfix, see changelog + + -- Ralph Amissah <ralph@amissah.com> Wed, 09 Jan 2008 06:16:44 +0000 + +sisu (0.64.0-1) unstable; urgency=medium + + * new upstream, see changelog, includes modifications to: + * processing files moved to user owned directory under + /tmp/_sisu_processing~ + * newly created databases primary keys; + * postgresql populating affecting use of tcp/ip sockets; + + * debian/sisu.postrm should fix #454372 + + -- Ralph Amissah <ralph@amissah.com> Wed, 02 Jan 2008 23:16:22 +0000 + +sisu (0.63.0-1) unstable; urgency=medium + + * new upstream, latex for pdf (landscape & portrait etc.) generated in single + pass [accounts for version bump], and contains rsync bugfix for sisupod + (remote placement, and for download and processing) [accounts for medium + urgency], see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Thu, 20 Dec 2007 00:25:51 +0000 + +sisu (0.62.4-1) unstable; urgency=medium + + * upstream with fix, and adjustment to gpl3 links + + * debian build update + + * debian/watch file + + * DM upload + + * gpg/pgp signature used changed (now B98F62B1 before BD76E77F) + + -- Ralph Amissah <ralph@amissah.com> Fri, 14 Dec 2007 21:41:13 +0000 + +sisu (0.62.3-3) unstable; urgency=medium + + * Dm-Upload-Allowed field needs XS- prefex + + -- Ralph Amissah <ralph@amissah.com> Fri, 30 Nov 2007 22:14:47 +0000 + +sisu (0.62.3-2) unstable; urgency=medium + + * debian/changelog (take more care with git reset) + + -- Ralph Amissah <ralph@amissah.com> Thu, 29 Nov 2007 01:42:04 +0000 + +sisu (0.62.3-1) unstable; urgency=medium + + * new upstream with minor fixes, see changelog + + * debian/control Dm-Upload-Allowed: yes + + -- Ralph Amissah <ralph@amissah.com> Tue, 27 Nov 2007 02:43:18 +0000 + +sisu (0.62.2-1) unstable; urgency=medium + + * new upstream, minor, but contains a bugfix to do with remote markup source + that contains images, see changelog + + * debian/control 'Homepage:' field (and accompanying lintian override) + + -- Ralph Amissah <ralph@amissah.com> Sat, 03 Nov 2007 01:48:41 +0000 + +sisu (0.62.1-1) unstable; urgency=medium + + * new upstream with minor regex match fix, replaces previous as debian + upload + + -- Ralph Amissah <ralph@amissah.com> Mon, 22 Oct 2007 19:42:07 +0100 + +sisu (0.62.0-1) unstable; urgency=medium + + * new upstream, several things, see upstream changelog + + * some output directories moved that will require manual fixing for existing + sites, [outputpath]/_sisu/image_local becomes [outputpath]/_sisu/image; + [outputpath]/_sisu/image for system images becomes + [outputpath]/_sisu/image_sys; shared source if any now is placed in separate + directories, [outputpath]/src for shared markup text, [outputpath]/pod for + shared (zipped) sisupods [accounts for version bump] + + * debian/control added 'Depends' on rsync (previously 'Recommends') as used + even more extensively + + * debian/control, 'Replaces' and 'Conflicts' placed on sisu-doc sub-package + which was introduced for the duration of the 0.59 release series only, + (and never uploaded to Debian), [unlikely to exist, remove if it does] + + -- Ralph Amissah <ralph@amissah.com> Sat, 20 Oct 2007 15:04:38 +0100 + +sisu (0.61.0-1) unstable; urgency=medium + + * new upstream, consolidates changes introduced in 0.59 and 0.60 series, + version bump due to change in treatment of available text outputs markup + shortcut, results now presented as a single object (changes the resulting + object numbering for document where used), includes some fixes + + -- Ralph Amissah <ralph@amissah.com> Fri, 12 Oct 2007 20:59:45 +0100 + +sisu (0.60.1-1) unstable; urgency=low + + * new upstream with minor fixes + + -- Ralph Amissah <ralph@amissah.com> Sun, 07 Oct 2007 14:22:08 +0100 + +sisu (0.60.0-2) unstable; urgency=low + + * debian/changelog, removed references to sisu-doc sub-package, (introduced + in 0.59 and removed again in 0.60) + + -- Ralph Amissah <ralph@amissah.com> Thu, 04 Oct 2007 19:31:32 +0100 + +sisu (0.60.0-1) unstable; urgency=low + + * new upstream, contains a number of additions/fixes (see changelog) and + source tarball back to sane size (after 0.59 inflation, not in debian + archive), this includes sisu documentation as sisu source, but no generated + output, other than a few man pages, rationale for change provided in + upstream changelog + + * [Note: previous 0.59 builds were not for debian upload] + + -- Ralph Amissah <ralph@amissah.com> Wed, 03 Oct 2007 04:53:48 +0100 + +sisu (0.59.1-1) unstable; urgency=low + + * new upstream, minor fixes, see changelog + + -- Ralph Amissah <ralph@amissah.com> Tue, 25 Sep 2007 03:14:21 +0100 + +sisu (0.59.0-1) unstable; urgency=low + + * new upstream, primarily documentation, new sub-package sisu-doc, increases + size of package considerably, many other changes, see changelog + + * debian/control restrict ruby use: 1.8.4 < ruby < 1.9 + + * debian package specific manpages moved to main package + + * debian note: lintian warnings on some sisu generated man-pages - certain + characters and line-breaks + + -- Ralph Amissah <ralph@amissah.com> Sun, 23 Sep 2007 19:32:17 +0100 + +sisu (0.58.3-1) unstable; urgency=low + + * new upstream, minor detail, see changelog + + -- Ralph Amissah <ralph@amissah.com> Thu, 06 Sep 2007 18:35:51 +0100 + +sisu (0.58.2-1) unstable; urgency=low + + * new upstream, detail, composite documents, code-block exception + + -- Ralph Amissah <ralph@amissah.com> Wed, 05 Sep 2007 21:00:16 +0100 + +sisu (0.58.1-1) unstable; urgency=low + + * new upstream with minor fixes for grouped text (primarily code-blocks), + see changelog + + -- Ralph Amissah <ralph@amissah.com> Tue, 04 Sep 2007 22:23:59 +0100 + +sisu (0.58.0-1) unstable; urgency=low + + * new upstream, mostly to do with escaping code-blocks from being marked up, + see changelog + + * debian/changelog kdissert and trang moved to Suggests, minor reordering + + -- Ralph Amissah <ralph@amissah.com> Mon, 03 Sep 2007 23:14:43 +0100 + +sisu (0.57.0-1) unstable; urgency=low + + * new upstream, cleaning up output (as opposed to code), a minor syntax + addition, and change to sisurc.yml for search forms, see changelog + + -- Ralph Amissah <ralph@amissah.com> Thu, 23 Aug 2007 01:30:10 +0100 + +sisu (0.56.3-1) unstable; urgency=low + + * new upstream, minor fixes, see changelog + + -- Ralph Amissah <ralph@amissah.com> Sun, 19 Aug 2007 02:47:40 +0100 + +sisu (0.56.2-1) unstable; urgency=medium + + * new upstream, odf fix, see changelog + + -- Ralph Amissah <ralph@amissah.com> Tue, 31 Jul 2007 21:16:20 +0100 + +sisu (0.56.1-1) unstable; urgency=medium + + * new upstream, minor refinement in a regex match, see changelog + + -- Ralph Amissah <ralph@amissah.com> Tue, 31 Jul 2007 19:04:59 +0100 + +sisu (0.56.0-1) unstable; urgency=medium + + * same as 0.55.7, more significant version number used to flag (minor) + change to search db structure, (which may necessitate rebuild if used), + see changelog + + -- Ralph Amissah <ralph@amissah.com> Tue, 31 Jul 2007 01:54:22 +0100 + +sisu (0.55.7-1) unstable; urgency=medium + + * new upstream, minor adjustments, some such as increase of auto-generated + identifier db field size verge on fixes, also addition of semi-colon as + possible url terminator, see changelog + + -- Ralph Amissah <ralph@amissah.com> Tue, 31 Jul 2007 00:04:10 +0100 + +sisu (0.55.6-1) unstable; urgency=medium + + * new upstream, see changelog, includes url match fix and refinements + + * vim syntax and ftplugin files moved back to /usr/share/vim/addons + + * debian/control added recommends vim-addon-manager + + -- Ralph Amissah <ralph@amissah.com> Sat, 28 Jul 2007 14:20:12 +0100 + +sisu (0.55.5-1) unstable; urgency=medium + + * initialize output directory, fix (Closes: #434168) + + * vim syntax and ftplugin files install moved to /usr/share/vim-scripts + + * minor upstream changes see changelog + + -- Ralph Amissah <ralph@amissah.com> Sun, 22 Jul 2007 11:17:32 +0100 + +sisu (0.55.4-1) unstable; urgency=medium + + * new upstream, minor fix, see changelog + + -- Ralph Amissah <ralph@amissah.com> Fri, 20 Jul 2007 07:44:03 +0100 + +sisu (0.55.3-1) unstable; urgency=medium + + * new upstream, polishing, see changelog + + * debian, renamed editor syntax file directory + + -- Ralph Amissah <ralph@amissah.com> Sat, 14 Jul 2007 10:31:07 +0100 + +sisu (0.55.2-1) unstable; urgency=medium + + * new upstream, various small fixes and improvements, see changelog + + -- Ralph Amissah <ralph@amissah.com> Sat, 07 Jul 2007 09:32:37 +0100 + +sisu (0.55.1-1) unstable; urgency=low + + * new upstream, reviewed and reposted, includes fixes to dal and odf, see + changelog + + -- Ralph Amissah <ralph@amissah.com> Mon, 02 Jul 2007 18:14:01 +0100 + +sisu (0.55.0-1) unstable; urgency=low + + * License change - GPL v3 or later + + * make lib available to ruby 1.9 + + * New upstream including some fixes, see changelog + + -- Ralph Amissah <ralph@amissah.com> Sun, 01 Jul 2007 11:41:09 +0100 + +sisu (0.54.1-1) unstable; urgency=low + + * new upstream, with fix in cgi-search related to match highlighting, see + upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Fri, 15 Jun 2007 12:59:25 +0100 + +sisu (0.54.0-1) unstable; urgency=low + + * new upstream, minor additions to syntax, extended indent levels, see + upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Thu, 14 Jun 2007 10:49:58 +0100 + +sisu (0.53.0-1) unstable; urgency=low + + * new upstream, housekeeping, see upstream changelog + * [OT, note] scm switched to git + * lib placed in v0 (instead of 0.53) + + -- Ralph Amissah <ralph@amissah.com> Sat, 02 Jun 2007 11:29:59 +0100 + +sisu (0.52.7-1) unstable; urgency=low + + * new upstream, texpdf minor fix + + -- Ralph Amissah <ralph@amissah.com> Thu, 17 May 2007 20:39:29 +0100 + +sisu (0.52.6-1) unstable; urgency=low + + * new upstream, minor fix + + -- Ralph Amissah <ralph@amissah.com> Mon, 14 May 2007 00:14:33 +0100 + +sisu (0.52.5-1) unstable; urgency=low + + * dependencies updated (Closes: #419294) [thanks for report Martin Pitt] + + * new upstream, minor changes related to setting of TCP/IP port to permit + the change of postgresql database version. (you may need to check the + postgresql port used and set it appropriately for your system, by setting + PGPORT or making sure sisurc.yml has the right value if the postgresql + default 5432 is not used). Postgresql database upgrades in debian that are + used by sisu should occur independently of sisu version. + + -- Ralph Amissah <ralph@amissah.com> Thu, 10 May 2007 01:50:08 +0100 + +sisu (0.52.4-1) unstable; urgency=low + + * new upstream, see changelog + + * debhelper >= 5 + + -- Ralph Amissah <ralph@amissah.com> Sat, 05 May 2007 10:51:18 +0100 + +sisu (0.52.3-1) unstable; urgency=medium + + * texpdf (LaTeX:pdf) utf-8 headers adjusted to work with new file magic + information (utf-8 markup file is assumed) + + * debian/control, reverted postgresql dependencies to 0.52.1 until update of + ruby drivers to comply with suggestions in #419294 + + -- Ralph Amissah <ralph@amissah.com> Thu, 26 Apr 2007 02:42:55 +0100 + +sisu (0.52.2-1) unstable; urgency=low + + * debian/control, postgresql dependency update, (was intended to close + 419294) [thank you for report Martin Pitt] + + * minor upstream adjustment todo with links to generated output in html, see + changelog + + -- Ralph Amissah <ralph@amissah.com> Sat, 21 Apr 2007 15:21:37 +0100 + +sisu (0.52.1-1) unstable; urgency=low + + * new upstream, minor, see changelog + + -- Ralph Amissah <ralph@amissah.com> Sat, 14 Apr 2007 17:56:19 +0100 + +sisu (0.52.0-1) unstable; urgency=low + + * new upstream, introduces: + * declared filetype identifier, + * a default action for 'sisu [recognised filename]' + * gpl3 draft 3 as document markup sample + and includes minor fixes, see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Sat, 07 Apr 2007 05:44:03 +0100 + +sisu (0.51.0-1) unstable; urgency=low + + * new upstream, mostly refactoring, but include changes to skins (their + simplification) which results in the need to modify existing skins + accordingly. + + -- Ralph Amissah <ralph@amissah.com> Sat, 31 Mar 2007 10:56:14 +0100 + +sisu (0.50.4-1) unstable; urgency=low + + * new upstream, fixes to sample generated search form (cgi) + + -- Ralph Amissah <ralph@amissah.com> Sat, 24 Mar 2007 09:32:49 +0000 + +sisu (0.50.3-1) unstable; urgency=low + + * new upstream, minor fixes + + -- Ralph Amissah <ralph@amissah.com> Sat, 17 Mar 2007 16:05:32 +0000 + +sisu (0.50.2-1) unstable; urgency=low + + * new upstream, many small changes, most significant to do with integration + of access to search features. Minor help updates. See upstream changelog + + * debian control, minor update to package description + + -- Ralph Amissah <ralph@amissah.com> Sat, 17 Mar 2007 01:28:01 +0000 + +sisu (0.50.1-1) unstable; urgency=low + + * new upstream, several minor adjustments, most notably indexes not built + (automatically) on postgresql text/content and endnote fields, (rely on + tsearch, suggest manual building of Gin index), see upstream changelog + + -- Ralph Amissah <ralph@amissah.com> Sat, 10 Mar 2007 00:56:59 +0000 + +sisu (0.50.0-1) unstable; urgency=low + + * new upstream, several modest changes, see upstream changelog + + * yaml files renamed with .yml extension including sisurc.yml + + -- Ralph Amissah <ralph@amissah.com> Tue, 6 Mar 2007 02:23:56 +0000 + +sisu (0.49.2-1) unstable; urgency=low + + * new upstream, minor adjustments, see version manifest + + -- Ralph Amissah <ralph@amissah.com> Sat, 24 Feb 2007 10:44:54 +0000 + +sisu (0.49.1-1) unstable; urgency=low + + * new upstream, see version manifest + + -- Ralph Amissah <ralph@amissah.com> Sat, 10 Feb 2007 10:36:45 +0000 + +sisu (0.49.0-1) unstable; urgency=low + + * 0.49 opened [see 0.48.8-10] merged 0.48.8-10 upstream + + -- Ralph Amissah <ralph@amissah.com> Fri, 26 Jan 2007 00:38:04 +0000 + +sisu (0.48.12-1) unstable; urgency=low + + * [see 0.48.8-8] merged 0.48.8-8 upstream (Etch freeze is at 0.48.8) + + -- Ralph Amissah <ralph@amissah.com> Wed, 24 Jan 2007 22:47:02 +0000 + +sisu (0.48.11-1) unstable; urgency=low + + * [see 0.48.8-7] merged 0.48.8-7 upstream (Etch freeze is at 0.48.8) + originally built on Fri, 12 Jan 2007 23:23:07 +0000 + + -- Ralph Amissah <ralph@amissah.com> Wed, 24 Jan 2007 22:37:06 +0000 + +sisu (0.48.10-1) unstable; urgency=low + + * [see 0.48.8-6] merged 0.48.8-6 upstream (Etch freeze is at 0.48.8) + originally built on Mon, 8 Jan 2007 22:25:23 +0000 + + -- Ralph Amissah <ralph@amissah.com> Wed, 24 Jan 2007 22:28:07 +0000 + +sisu (0.48.9-1) unstable; urgency=low + + * [see 0.48.8-2] merged 0.48.8-2 upstream (Etch freeze is at 0.48.8) + originally built on Wed, 27 Dec 2006 15:02:13 +0000 + + -- Ralph Amissah <ralph@amissah.com> Wed, 24 Jan 2007 21:09:40 +0000 + +sisu (0.48.8-11) unstable; urgency=medium + + * build "stable" + (based on stable upstream release = = = 0.49.1-1) + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Fri, 16 Feb 2007 00:36:09 +0000 + +sisu (0.48.8-10) unstable; urgency=medium + + * xml and xhtml adjustment of regex match of urls for xlink + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Tue, 23 Jan 2007 01:34:20 +0000 + +sisu (0.48.8-9) unstable; urgency=medium + + * use ISO 639-2 for language codes (Closes: #407937) + and related changes to help and man pages + + * removed Danish sample markup files, (which need to be renamed da instead of + dk following iso 639-2) to reduce the size of the inter-diff against the + package in testing + + * sisupod fixes: + * safeguard against accidental zipping (making sisupod) of entire + document markup directory, requests confirmation of action + (Closes: #407932) + * sisupod initialisation (and generation) in new work directory, + issue fixed (Closes: #407943) + + * xml and xhtml several adjustments with related css changes + (Closes: #407938) + + * vim syntax highlighting, minor fix to catch an existing markup shortcut + (Closes: #407941) + + * cosmetic fixes: + * html toc author line + * debian document samples, tex pdf page break instruction + adjusted/corrected + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Mon, 22 Jan 2007 17:33:43 +0000 + +sisu (0.48.8-8) unstable; urgency=medium + + * use ISO 639-2 for language codes, [best implement now] + (also results in renaming of some document samples) + + * sisupod fixes: + * added safeguard against accidental zipping (making sisupod) of entire + document markup directory, requests confirmation + * sisupod initialisation (and generation) in new work directory, fixed + + * xml and xhtml several adjustments with related css changes + + * cosmetic fixes: + * html toc author line + * debian document samples, tex pdf page break instruction + adjusted/corrected + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Sun, 21 Jan 2007 04:35:06 +0000 + +sisu (0.48.8-7) unstable; urgency=medium + + * modifications to sample search form introduced in -4 break it, reverted + (to use of static path for cgi-bin) + (Closes: #406281, Closes: #406280) [same bug] + + * debian/control removed suggests in sisu-sqlite and sisu-postgresql on + libdbd-sqlite and libdbd-pgsql respectively, as they are not present in + testing/Etch + (Closes: #406282, Closes: #406284) + + * sisu html man page updated/regenerated (from man page) + + * Debian Etch related fix (cleared by Marc 'HE' Brockschmidt), uploaded by + Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Wed, 10 Jan 2007 04:58:09 +0000 + +sisu (0.48.8-6) unstable; urgency=medium + + * sisu-pdf texlive dependency adjusted on feedback from Norbert Preining + (Closes: #402807) + <http://lists.debian.org/debian-tex-maint/2007/01/msg00034.html> + <http://lists.debian.org/debian-tex-maint/2007/01/msg00033.html> + + * Debian Etch related fix (cleared by Marc 'HE' Brockschmidt), uploaded by + Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Wed, 3 Jan 2007 17:21:27 +0000 + +sisu (0.48.8-5) unstable; urgency=medium + + * sisu-pdf texlive dependencies shortened and free from use of metapackages + [this should close #402807] + + * year rollover 2006 has become 2007, Happy New Year. + + * Debian Etch related fixes uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Tue, 2 Jan 2007 16:00:25 +0000 + +sisu (0.48.8-4) unstable; urgency=medium + + * cgi sample form related modifications (relatively minor but nice to have + sorted): + * cgi_pgsql and cgi_sqlite, dynamic path used instead (fixed path will + result in errors where the default path is not used). + * cgi_pgsql and cgi_sqlite, "documentation" tip for copying generated cgi + sample to cgi-bin directory, prevent accidental copying to a directory + instead of file. Dynamic path used. + * debian/control Recommends libfcgi-ruby1.8 moved to sisu-postgresql and + sisu-sqlite (only used in this context) + + * Debian Etch related fixes uploaded by Daniel Baumann + [depends for sisu-pdf introduced in -3 questioned/challenged by 'HE' + rightly as it turns out] + + -- Ralph Amissah <ralph@amissah.com> Sun, 31 Dec 2006 03:06:45 +0000 + +sisu (0.48.8-3) unstable; urgency=medium + + * sisu latex generated, usepackage url (improved placement of urls) + + * debian control, sisu-pdf now depends on texlive alone, (alternative tetex + depends removed - reason: problem keeping both working!), take on board + suggestion by to rely on texlive Frank Küster if tetex is problematic (this + addresses, but does not close #402807 without further discussion, dropping + alternative tetex depends simplifies sisu-pdf (tex) related depends, and + makes it much more reliable (also see in changelog earlier feedback on + sisu-pdf depends from Norbert Preining url at 0.47.7-3) depends here drop + reliance on metapackages, (extra checks required as to determine whether + texlive depends list may be shortened, playing safe)) + + * debian/control sisu recommends libfcgi-ruby1.8 + (previously 'suggested'', needed for sample search form) + + * documentation/help minor addition on initially creating postgresql + database for use if necessary + + * Debian Etch related fixes uploaded by Daniel Baumann + (followed in quick succession by minor build additions in -4) + + -- Ralph Amissah <ralph@amissah.com> Sat, 30 Dec 2006 12:52:05 +0000 + +sisu (0.48.8-2) unstable; urgency=medium + + * LaTeX, bugfix - restores missing left column object/paragraph numbers + (missing curly (close) brace) [important, though marked as normal] + [bug introduced somewhere between 0.47 and 0.48] (closes: #403037) + + * LaTeX use mathptmx.sty instead of "obsolete" times.sty (as suggested by + Frank Küster in Bug#402807) + + * cgi-sample form, an arbitrary limit set for sql query results + (1000 better than none) Closes: #403042) + + * defaults, update sisu default homepage to current, (mainly urls) + [documentation] + + * css, addition to correspond with change to homepage + + * debian control, adds mention of editors other than vim for which there is + some kind of syntax support, kate, kwrite, gedit, diakonos [documentation] + + * [note] alternative install script (ruby) is automatically updated during + this build (using rant-0.5.8 instead of rant-0.5.6) + + * [note] version.yaml date changes, automatically updated during build + + * Debian Etch fixes (cleared by HE), uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Thu, 14 Dec 2006 16:50:57 +0000 + +sisu (0.48.8-1) unstable; urgency=medium + + * new upstream, + * fix to visual tables, permitting inclusion of column information + (required for concurrently released sisu-markup-samples (1.0.4)) + * document samples update to include Debian constitution v1.3 + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Mon, 27 Nov 2006 15:48:35 +0000 + +sisu (0.48.7-1) unstable; urgency=medium + + * upstream fixes, related to: + - cgi html search form, multilingual documents, url mapping of results + - dcc, document content digest, multilingual, fixes related to translation + and metadata extraction + - other more minor detail, see version manifest + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Sun, 19 Nov 2006 00:36:32 +0000 + +sisu (0.48.6-1) unstable; urgency=medium + + * upstream fixes related to: + - html, doc (single text, scroll version) tables + - texpdf, bugfix for (asterisk marker type) footnotes in headings + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Sat, 11 Nov 2006 21:43:21 +0000 + +sisu (0.48.5-1) unstable; urgency=medium + + * upstream fixes, including sisupod create - file selection refinement + + * man pages minor update + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Thu, 9 Nov 2006 19:04:27 +0000 + +sisu (0.48.4-1) unstable; urgency=medium + + * upstream fixes (texpdf:tables, plaintext, conversion:footnotes) + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Tue, 7 Nov 2006 00:52:52 +0000 + +sisu (0.48.3-1) unstable; urgency=high + + * one file omitted in sisu 0.48.2 fix, see comments there + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Tue, 31 Oct 2006 18:09:38 +0000 + +sisu (0.48.2-1) unstable; urgency=high + + * ruby-1.8.5-3 uploaded yesterday, detects and breaks on cyclic include + errors which were found at a basic level of operation, rendering program + effectively broken. New ruby build affects all previous versions of sisu. + [Further code review is necessary to ascertain that this does not occur + anywhere else within sisu code base] (necessary fixes should not affect + previous versions of ruby) + + -- Ralph Amissah <ralph@amissah.com> Tue, 31 Oct 2006 14:26:44 +0000 + +sisu (0.48.1-2) unstable; urgency=medium + + * debian/control recommends hyperestraier put back (sisu and sisu-complete) + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Mon, 30 Oct 2006 01:16:50 +0000 + +sisu (0.48.1-1) unstable; urgency=medium + + * debian/control removed recommends/suggests on hyperestraier, rename and + pgaccess as cause issues + + * processing path, _sisu_processing, defaults to home or /tmp + + * issue dealt with, when requested image not found + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Sun, 29 Oct 2006 17:06:05 +0000 + +sisu (0.48.0-1) unstable; urgency=low + + * etch release candidate, extra testing, numerous small fixes, (several + related to method renaming in sisu-0.47.7, also checks against both ruby + 1.8.5 and current 1.9, and as specified in upstream version manifest) + + * new upstream introduces sisupod that sisu processing instructions can be + run against directly + + -- Ralph Amissah <ralph@amissah.com> Sat, 28 Oct 2006 17:17:03 +0100 + +sisu (0.47.8-1) unstable; urgency=low + + * upstream contains minor fix, see version manifest + + -- Ralph Amissah <ralph@amissah.com> Fri, 20 Oct 2006 00:12:52 +0100 + +sisu (0.47.7-3) unstable; urgency=low + + * debian/control sisu-pdf depends for tetex | texlive sorted, + feedback from Norbert Preining + http://lists.debian.org/debian-tex-maint/2006/10/msg00620.html + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Mon, 16 Oct 2006 19:26:28 +0100 + +sisu (0.47.7-2) unstable; urgency=low + + * sisu-pdf meta-package repackaged to work only with tetex, + alternative use of texlive meta-package dependency removed, + in its place a note that sisu will produce pdfs with the + texlive meta-package installed. + (May at later stage break package up into sisu-pdf-tetex + and sisu-pdf-texlive). + + * Debian release snapshot, uploaded by Daniel Baumann + + -- Ralph Amissah <ralph@amissah.com> Sun, 15 Oct 2006 17:38:20 +0100 + +sisu (0.47.7-1) unstable; urgency=low + + * sisu-pdf tetex|texlive installation depends + + * new upstream, see version manifest + + -- Ralph Amissah <ralph@amissah.com> Sat, 14 Oct 2006 12:50:20 +0100 + +sisu (0.47.6-1) unstable; urgency=low + + * new upstream, fixes to latex/pdf output, and a syntax extension + see version manifest + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sat, 7 Oct 2006 15:43:41 +0100 + +sisu (0.47.5-1) unstable; urgency=low + + * fix a break caused by change of library name in 0.47.4 + (that was not propagated into vc), related to creation of sisupod + (zipped markup with images etc.) + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sun, 1 Oct 2006 17:16:24 +0100 + +sisu (0.47.4-1) unstable; urgency=low + + * minor upstream change (syntax highlighting), see version manifest + + * debian policy violating firefox logo/image removed + (along with other browser related images) (Closes: #389500) + + -- Ralph Amissah <ralph@amissah.com> Fri, 29 Sep 2006 01:31:04 +0100 + +sisu (0.47.3-1) unstable; urgency=low + + * new upstream, minor code review + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sat, 23 Sep 2006 10:21:55 +0100 + +sisu (0.47.2-1) unstable; urgency=low + + * new upstream, minor fix required for ruby-1.8.5 + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Fri, 22 Sep 2006 01:45:17 +0100 + +sisu (0.47.1-1) unstable; urgency=low + + * new upstream, fixes, see version manifest + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Mon, 18 Sep 2006 23:18:41 +0100 + +sisu (0.47.0-1) unstable; urgency=low + + * new upstream, some fixes see version manifest changelog + + * debian/control depends zip and unzip added + used for sisupod.zip and ODF output + + * odt.zip file replaces odt.tgz for ODF base file + found in data/sisu/odf i.e. /usr/share/sisu/odf + easy way to keep keep directory structure + (version control issue, hg drops empty directories) + odf uses zip compression anyway + + * sisupod, (prepared sisu markup document) now uses zip compression and + file extension .zip (interoperability) + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sun, 17 Sep 2006 16:43:15 +0100 + +sisu (0.46.5-1) unstable; urgency=low + + * new upstream, minor, update to documentation + + * debian/control Priority at "optional" + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sat, 9 Sep 2006 21:58:28 +0100 + +sisu (0.46.4-1) unstable; urgency=low + + * new upstream, minor + + -- Ralph Amissah <ralph@amissah.com> Wed, 6 Sep 2006 03:03:39 +0100 + +sisu (0.46.3-1) unstable; urgency=low + + * debian/control moved from extra to optional - + does not conflict with anything, though a bit specialised perhaps + + * debian/copyright, year 2006 added + + * new upstream, see version manifest + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Mon, 4 Sep 2006 23:19:48 +0100 + +sisu (0.46.2-1) unstable; urgency=low + + * new upstream + + -- Ralph Amissah <ralph@amissah.com> Fri, 25 Aug 2006 22:38:44 +0100 + +sisu (0.46.1-1) unstable; urgency=low + + * new upstream + + * debian/control conflicts with sisu-vim which existed prior to vim-sisu + both of which are removed + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Wed, 16 Aug 2006 21:08:47 +0100 + +sisu (0.46.0-1) unstable; urgency=low + + * new upstream, (0.44 branch with newer code reinstated) see version manifest + + * debian/rules, repeated dh_compress removed + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sat, 12 Aug 2006 03:27:09 +0100 + +sisu (0.45.0-1) unstable; urgency=low + + * new upstream, reversion to older 0.43 code as 0.44 LaTeX generation does + not play well yet with new code base + + * debian changes introduced in 0.44 retained + + -- Ralph Amissah <ralph@amissah.com> Mon, 7 Aug 2006 05:49:44 +0100 + +sisu (0.44.0-1) unstable; urgency=low + + * new upstream, see version manifest changelog + + * debian/rules simplified + + * debian/control sisu-pdf Depends changed + + * debian/lintian/sisu added lintian override for man page and non-executables + + -- Ralph Amissah <ralph@amissah.com> Sun, 6 Aug 2006 18:19:06 +0100 + +sisu (0.43.0-1) unstable; urgency=low + + * new upstream, new endnote sequences, + see version manifest + + * debian vim/addons/syntax/sisu.vim add the new syntax file + (submit changes to Bram) + + * simple xml modeling files copied to directory + /usr/share/doc/sisu/model/relaxng + + * closing request for better package description + 0.42.2 (Closes: #377208) + + * man pages for meta-packages moved to man(7) + 0.42.4 (Closes: #377209) + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sat, 22 Jul 2006 02:33:41 +0100 + +sisu (0.42.4-1) unstable; urgency=low + + * minor touch upstream + + * debian/control in addition to existing Replaces: + added Conflicts: vim-sisu, sisu-remote + + * man pages for meta-packages moved to man(7) + (#377209) + + -- Ralph Amissah <ralph@amissah.com> Mon, 17 Jul 2006 01:46:24 +0100 + +sisu (0.42.3-1) unstable; urgency=low + + * new upstream, fix, no require ruby dbi unless dbi action requested + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Tue, 11 Jul 2006 22:34:30 +0100 + +sisu (0.42.2-1) unstable; urgency=low + + * debian/control, removed sisu-remote, added recommends rsync, + openssh-client|lsh-client, keychain, to main sisu package + instead + (Closes: #377206) + + * debian/control, removed vim-sisu, this used to contain syntax + highligter and color scheme now included in Vim 7, all that + remains is ftplugin, now installed by main sisu package + (Closes: #377207) + + * debian/control, sisu Replaces: vim-sisu + debian/sisu.install installs ftplugin originally in vim-sisu + + * debian/manpages, sisu (main package) now installs vim_sisu page + in man(7) + (Closes: #377209) [this was re-opened] + + * debian/control, package description related issues: + * modified sisu + * modified sisu-complete + * modified sisu-postgresql + * modified sisu-sqlite + * modified sisu-pdf + * removed sisu-remote, (as sisu-remote is no more) + * removed vim-sisu, (as vim-sisu is no more) + * removed sisu-remote, (as sisu-remote is no more) + [consider adding a note on remote placement of documents in + sisu(8) later] + (#377208 verify that descriptions are satisfactory before closing) + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sat, 8 Jul 2006 01:54:54 +0100 + +sisu (0.42.1-1) unstable; urgency=low + + * debian/control, removed recommends libtidy [non-existent, see + current libtidy-0.99-0, called in by tidy which is recommended + and sets libtidy dependency] (Closes: #377086) + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Thu, 6 Jul 2006 20:48:18 +0100 + +sisu (0.42.0-2) unstable; urgency=low + + * back to: control ruby >= 1.8.2 + (upgrade complains about 1.8.4 availability - though installed) + + -- Ralph Amissah <ralph@amissah.com> Thu, 6 Jul 2006 02:30:08 +0100 + +sisu (0.42.0-1) unstable; urgency=low + + * control ruby >= 1.8.4 + (no testing done on ruby 1.8.2 + and a report indicates there may be a problem) + + * control to sisu-pdf added Depends: texlive-latex-extra + (for use of asterisk markers in endnotes... + used in U.S. law scholarly writings) + + * vim-sisu package description changed (Closes: #374873) + + -- Ralph Amissah <ralph@amissah.com> Thu, 6 Jul 2006 01:17:01 +0100 + +sisu (0.41.8-1) unstable; urgency=low + + * new upstream, minor feature enhancement, see version manifest + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sat, 24 Jun 2006 20:49:53 +0100 + +sisu (0.41.7-1) unstable; urgency=low + + * Debian control, response to improved package description + request 'Home page' corrected to 'Homepage:' and vim folds + described in greater detail. Some detail added and + correction of name of package sisu-markup-samples + (provided in non-free) + + * Debian rules, .ssm and .ssi files added to list of not + compressed file types (/usr/share/doc/sisu) + + * Document samples "GPL2" and "Free as in Freedom" texts and + associated images included with package + (moved back from non-free sisu-markup-samples) + [FaiF is published under the GNU Free Documentation License, + without invariant sections] + + * includes bugfix (for segmented html endnotes), + see version manifest + + * includes minor feature enhancements, and first pass at proposed + alternative object model for sisu input (and metaverse), + see version manifest + + -- Ralph Amissah <ralph@amissah.com> Sat, 24 Jun 2006 16:52:43 +0100 + +sisu (0.41.6-1) unstable; urgency=low + + * new upstream, integration and fixes to the addition in 0.41.4, + see version manifest + + * debian control, recommends kdissert added + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Tue, 20 Jun 2006 01:20:13 +0100 + +sisu (0.41.5-1) unstable; urgency=low + + * new upstream, fix to minor addition in 0.41.4 see version manifest + + -- Ralph Amissah <ralph@amissah.com> Mon, 19 Jun 2006 02:37:13 +0100 + +sisu (0.41.4-1) unstable; urgency=low + + * new upstream, minor addition, see version manifest + + -- Ralph Amissah <ralph@amissah.com> Sun, 18 Jun 2006 02:07:47 +0100 + +sisu (0.41.3-2) unstable; urgency=low + + * /usr/share/doc/sisu for the time being do not compress + .sst or .rb files + + * debian/dirs removed reference to usr/sbin as not used + + * debian/rules minor cleaning of some commented out lines + + -- Ralph Amissah <ralph@amissah.com> Thu, 15 Jun 2006 01:59:08 +0100 + +sisu (0.41.3-1) unstable; urgency=low + + * new upstream, small adjustments and fixes, see version manifest + + -- Ralph Amissah <ralph@amissah.com> Wed, 14 Jun 2006 01:17:53 +0100 + +sisu (0.41.2-1) unstable; urgency=low + + * new upstream includes fixes, see version manifest + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Fri, 9 Jun 2006 07:23:31 +0100 + +sisu (0.41.1-1) unstable; urgency=low + + * new upstream, some fixes, see version manifest + + -- Ralph Amissah <ralph@amissah.com> Wed, 7 Jun 2006 13:11:30 +0100 + +sisu (0.41.0-1) unstable; urgency=low + + * new upstream, many changes (primarily program internals), + see version manifest + + -- Ralph Amissah <ralph@amissah.com> Sat, 3 Jun 2006 17:25:46 +0100 + +sisu (0.40.4-1) unstable; urgency=low + + * new upstream, minor changes tex pdf related + + * source package directory name convention changed + + -- Ralph Amissah <ralph@amissah.com> Sun, 28 May 2006 17:04:58 +0100 + +sisu (0.40.3-1) unstable; urgency=low + + * minor fixes, including (the (non-debian) rant/ruby make based) + installer + + -- Ralph Amissah <ralph@amissah.com> Wed, 24 May 2006 23:32:58 +0100 + +sisu (0.40.2-1) unstable; urgency=low + + * new upstream, minor update, greater use of translation module + + -- Ralph Amissah <ralph@amissah.com> Wed, 24 May 2006 05:31:34 +0100 + +sisu (0.40.1-1) unstable; urgency=low + + * [changed local apt archiver to reprepro] + + -- Ralph Amissah <ralph@amissah.com> Mon, 22 May 2006 15:34:00 +0100 + +sisu (0.40.0-1) unstable; urgency=low + + * sisu-examples, markup book samples removed as not compliant with dfsg + document substantive content have the original author or publisher's + license... sisu-markup-samples now exists as a package in non-free + + * a module for translations added + + -- Ralph Amissah <ralph@amissah.com> Mon, 22 May 2006 04:03:27 +0100 + +sisu (0.39.3-1) unstable; urgency=low + + * new upstream, minor fix + + * Debian release snapshot, uploaded by Wookey (at Debconf6) + [queue new: see 0.39.2 renaming of included packages] + + -- Ralph Amissah <ralph@amissah.com> Sun, 14 May 2006 05:39:46 +0100 + +sisu (0.39.2-2) unstable; urgency=low + + * debian package fixes, control states vim-sisu replaces sisu-vim, + and path for ftplugins corrected + + -- Ralph Amissah <ralph@amissah.com> Sat, 13 May 2006 07:30:32 +0100 + +sisu (0.39.2-1) unstable; urgency=low + + * debian policy standards version 3.7.2 + + * debian vim policy changes, rename sisu_vim vim_sisu + vim 7 in debian includes filetypes, syntax, and color, removed + vim-sisu includes ftplugin + + -- Ralph Amissah <ralph@amissah.com> Sat, 13 May 2006 03:28:28 +0100 + +sisu (0.39.1-1) unstable; urgency=low + + * repair for digests/dcc which provide image checksums once more + + -- Ralph Amissah <ralph@amissah.com> Mon, 8 May 2006 19:00:51 +0100 + +sisu (0.39.0-1) unstable; urgency=low + + * new upstream, changes to naming of html segments where automatic + + * (back to) using Debian Policy Standards Version 3.7.0, Lintian and + Linda do not appear to have caught up with the version on my box, + or the suggestion that 3.7.2 be used + + -- Ralph Amissah <ralph@amissah.com> Mon, 8 May 2006 01:32:16 +0100 + +sisu (0.38.10-2) unstable; urgency=low + + * rebuilt using new debian policy, Standards-Version 3.7.2 + (previous build 0.38.10-1, used 3.7.0) + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Fri, 5 May 2006 03:00:42 +0100 + +sisu (0.38.10-1) unstable; urgency=low + + * new upstream, minor fixes + + * Debian release + + -- Ralph Amissah <ralph@amissah.com> Thu, 4 May 2006 01:08:47 +0100 + +sisu (0.38.9-1) unstable; urgency=low + + * new upstream, with adjustments, see version manifest, + in debian package: 'recommends' placed on hyperestraier; + debian/control updated Standards, 3.7.0 + + -- Ralph Amissah <ralph@amissah.com> Wed, 3 May 2006 04:41:38 +0100 + +sisu (0.38.8-1) unstable; urgency=low + + * new upstream, a few small fixes + + -- Ralph Amissah <ralph@amissah.com> Sat, 29 Apr 2006 17:58:20 +0100 + +sisu (0.38.7-1) unstable; urgency=low + + * new upstream, code re-arrangement, minor, + code moved out of /usr/bin + + -- Ralph Amissah <ralph@amissah.com> Thu, 27 Apr 2006 20:22:33 +0100 + +sisu (0.38.6-1) unstable; urgency=low + + * new upstream, first look at ruby 1.9 + + -- Ralph Amissah <ralph@amissah.com> Tue, 25 Apr 2006 22:40:24 +0100 + +sisu (0.38.5-1) unstable; urgency=low + + * primarily a rebuild, lintian 1.23.17 ("published" yesterday) + complains about existing sisu builds + + -- Ralph Amissah <ralph@amissah.com> Sun, 23 Apr 2006 02:33:08 +0100 + +sisu (0.38.4-1) unstable; urgency=low + + * new upstream, a fix in markup version checking, and some + minor refinements, see version_manifest + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Fri, 21 Apr 2006 20:23:31 +0100 + +sisu (0.38.3-1) unstable; urgency=low + + * new upstream, minor refinement for conversions between + 0.37 and 0.38 markup + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Thu, 20 Apr 2006 02:29:10 +0100 + +sisu (0.38.2-1) unstable; urgency=low + + * new upstream, minor adjustments + + -- Ralph Amissah <ralph@amissah.com> Wed, 19 Apr 2006 01:53:46 +0100 + +sisu (0.38.1-1) unstable; urgency=low + + * new upstream, minor fixes, a converter between 0.37 and 0.38 + experimental markup (0.37 is substantially the same as 0.16, + the filenaming convention was changed) + see version manifest + + -- Ralph Amissah <ralph@amissah.com> Mon, 17 Apr 2006 19:10:15 +0100 + +sisu (0.38.0-1) unstable; urgency=low + + * new upstream, several small additions, introduces alternative headers, + alternative experimental structural markup, and other little things, + see version_manifest + + -- Ralph Amissah <ralph@amissah.com> Sun, 16 Apr 2006 02:24:17 +0100 + +sisu (0.37.12-1) unstable; urgency=low + + * new upstream, minor, vim syntax + + -- Ralph Amissah <ralph@amissah.com> Sun, 9 Apr 2006 18:07:12 +0100 + +sisu (0.37.11-1) unstable; urgency=low + + * new upstream, minor, mostly vim syntax related + + -- Ralph Amissah <ralph@amissah.com> Sun, 9 Apr 2006 00:05:42 +0100 + +sisu (0.37.10-1) unstable; urgency=low + + * new upstream, small things vim related + + -- Ralph Amissah <ralph@amissah.com> Thu, 6 Apr 2006 23:19:27 +0100 + +sisu (0.37.9-1) unstable; urgency=low + + * new upstream, some attention to vim syntax and ftplugin + + -- Ralph Amissah <ralph@amissah.com> Sat, 1 Apr 2006 14:39:13 +0100 + +sisu (0.37.8-1) unstable; urgency=low + + * new upstream, minor adjustments, + (ansi screen color default now off) see version_manifest + + -- Ralph Amissah <ralph@amissah.com> Sat, 25 Mar 2006 15:38:39 +0000 + +sisu (0.37.7-1) unstable; urgency=low + + * new upstream, single fix + + -- Ralph Amissah <ralph@amissah.com> Thu, 23 Mar 2006 23:19:10 +0000 + +sisu (0.37.6-1) unstable; urgency=low + + * new upstream, minor touches + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Thu, 23 Mar 2006 00:28:12 +0000 + +sisu (0.37.5-1) unstable; urgency=low + + * new upstream, several small changes, see version_manifest + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Wed, 22 Mar 2006 01:47:32 +0000 + +sisu (0.37.4-1) unstable; urgency=low + + * new upstream, minor fixes (in some html pages generated) + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Thu, 9 Mar 2006 18:59:34 +0000 + +sisu (0.37.3-1) unstable; urgency=low + + * new upstream, minor adjustment (default home page) + + -- Ralph Amissah <ralph@amissah.com> Thu, 9 Mar 2006 01:29:51 +0000 + +sisu (0.37.2-1) unstable; urgency=low + + * reduced number of file extensions used in the .ss space + .sst .ssm .ssi (& .ssd), temp/secondary files get ._sst & .-sst + sst == sisu structured text [.s1 .s2 .s3], + ssm == sisu structured master [.r1 .r2 .r3], + ssi == sisu structured insert/information [.si], + _sst == secondary file [.t1 .t2 .t3], + -sst == downloaded sst (url) [.u1, .u2 .u3], + ssd == sisu structured document, sisudoc.tgz + See version manifest. + + rename 's/\.s[123]$/\.sst/' *.s{1,2,3} + rename 's/\.r[123]$/\.ssm/' *.r{1,2,3} + rename 's/\.si$/\.ssi/' *.si + + * edited sisu description in debian control file. + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Tue, 7 Mar 2006 22:39:51 +0000 + +sisu (0.37.1-1) unstable; urgency=low + + * new upstream, minor update in sisu-examples. + edited sisu description in debian control file. + + -- Ralph Amissah <ralph@amissah.com> Mon, 6 Mar 2006 23:57:16 +0000 + +sisu (0.37.0-1) unstable; urgency=low + + * new upstream, new filename extensions, + using .ss extensions with a third identifying character: + .sst .ssf .ssm .ssc .ssi .ssu .sss .ssd + sst == sisu structured text, ssf == sisu structured file, + ssm == sisu structured master, ssc == sisu structured composite, + ssi == sisu structured insert/information, + ssu == downloaded sst (url), + sss == secondary file, + ssd == sisu structured document. + See version manifest. + + -- Ralph Amissah <ralph@amissah.com> Sun, 5 Mar 2006 23:26:44 +0000 + +sisu (0.36.25-1) unstable; urgency=low + + * new upstream, minor changes + + -- Ralph Amissah <ralph@amissah.com> Sun, 5 Mar 2006 11:52:25 +0000 + +sisu (0.36.24-1) unstable; urgency=low + + * new upstream, minor fixes, + also a fix and cross-linking in debian sample markup documents + + -- Ralph Amissah <ralph@amissah.com> Tue, 28 Feb 2006 18:54:38 +0000 + +sisu (0.36.23-1) unstable; urgency=low + + * new upstream, several small fixes + + -- Ralph Amissah <ralph@amissah.com> Mon, 27 Feb 2006 00:19:09 +0000 + +sisu (0.36.22-1) unstable; urgency=low + + * new upstream, minor fix, (odf endnote url matching) + + -- Ralph Amissah <ralph@amissah.com> Thu, 23 Feb 2006 19:20:22 +0000 + +sisu (0.36.21-1) unstable; urgency=low + + * new upstream, small fixes, metaverse auto-numbering + headings/titles rules& html nav band, minor + + -- Ralph Amissah <ralph@amissah.com> Wed, 22 Feb 2006 21:40:01 +0000 + +sisu (0.36.20-1) unstable; urgency=low + + * fix issue introduced by previous release, minor + + -- Ralph Amissah <ralph@amissah.com> Wed, 22 Feb 2006 02:49:11 +0000 + +sisu (0.36.19-1) unstable; urgency=low + + * new upstream, a minor intermediate processing rule change, + and minor fixes (see version_manifest) + + -- Ralph Amissah <ralph@amissah.com> Wed, 22 Feb 2006 01:08:37 +0000 + +sisu (0.36.18-1) unstable; urgency=low + + * new upstream, minor (cgi search form samples) + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Mon, 20 Feb 2006 02:11:54 +0000 + +sisu (0.36.17-1) unstable; urgency=low + + * new upstream, minor + + -- Ralph Amissah <ralph@amissah.com> Sun, 19 Feb 2006 15:40:52 +0000 + +sisu (0.36.16-1) unstable; urgency=low + + * new upstream, minor (cgi search form related, see manifest) + + -- Ralph Amissah <ralph@amissah.com> Sun, 19 Feb 2006 13:01:46 +0000 + +sisu (0.36.15-1) unstable; urgency=low + + * new upstream, minor + + -- Ralph Amissah <ralph@amissah.com> Sat, 18 Feb 2006 17:05:55 +0000 + +sisu (0.36.14-1) unstable; urgency=low + + * new upstream + + -- Ralph Amissah <ralph@amissah.com> Sat, 18 Feb 2006 03:00:29 +0000 + +sisu (0.36.13-1) unstable; urgency=low + + * new upstream, minor fix + + -- Ralph Amissah <ralph@amissah.com> Sun, 12 Feb 2006 23:16:05 +0000 + +sisu (0.36.12-1) unstable; urgency=low + + * new upstream, small fixes + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Thu, 9 Feb 2006 18:49:43 +0000 + +sisu (0.36.11-1) unstable; urgency=low + + * new upstream, minor + + -- Ralph Amissah <ralph@amissah.com> Thu, 9 Feb 2006 05:20:07 +0000 + +sisu (0.36.10-1) unstable; urgency=low + + * new upstream + + -- Ralph Amissah <ralph@amissah.com> Wed, 8 Feb 2006 18:23:38 +0000 + +sisu (0.36.9-1) unstable; urgency=low + + * upstream with filelist fix, see version_manifest + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Tue, 7 Feb 2006 05:13:52 +0000 + +sisu (0.36.8-1) unstable; urgency=low + + * new upstream, little things noted in version_manifest + + -- Ralph Amissah <ralph@amissah.com> Mon, 6 Feb 2006 21:29:10 +0000 + +sisu (0.36.7-1) unstable; urgency=low + + * new upstream, minor fixes + + -- Ralph Amissah <ralph@amissah.com> Sun, 5 Feb 2006 21:47:36 +0000 + +sisu (0.36.6-1) unstable; urgency=low + + * new upstream, many fixes, see version_manifest + + -- Ralph Amissah <ralph@amissah.com> Sat, 4 Feb 2006 13:43:30 +0000 + +sisu (0.36.5-1) unstable; urgency=low + + * proposed new build for Debian upload, built in manner described for + 0.36.4-2, (this would prevent the need to maintain two different + builds of the same package) + * fewer packages are created than in the rejected Debian upload + * it is much easier for the user to install the components they + need than in the current accpted build + * it is not necessary to install the likes of tetex, tetex-extra, + latex-ucs or postgresql and various drivers or sqlite etc. if you + are not going to use them + the three different builds are represented by + 0.36.4-1, 0.36.4-2, and 0.36.4-3, please see changelog notes below + + * copyright file makes mention of setup.rb by Minero Aoki which is + included in the tarball, and licensed under the Gnu Lesser GPL + + * copyright file makes mention of Rant which though not included generates + the install file included in the tarball (Rant is by Stephan Lang and + licensed under the Gnu Lesser GPL) [corrected erroneously referred to + the similar Rake] + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Fri, 6 Jan 2006 21:25:15 +0000 + +sisu (0.36.4-3) unstable; urgency=low + + * post 0.32.0 build style: + * sisu : basic build, no dependencies really beyond ruby + * sisu-pdf : dependencies for sisu to generate pdfs latex related + * sisu-postgresql : dependencies for sisu to populate a postgresql + database including postgresql itself and various ruby drivers + * sisu-remote : dependencies for remote placement of sisu output, + via ssh and rsync + * sisu-examples : markup and other examples in sisu, fairly large + * sisu-sqlite : dependencies for sisu to populate an sqlite + database including sqlite itself and various ruby drivers + * sisu-vim : vim syntax highlighting and folds only of interest + if vim/gvim is used + ** sisu-webrick : use of ruby webrick server with sisu + ** sisu-termsheet : a lesser used component, for producing output + by merging termsheets/forms against standard formm documents + ** sisu-texinfo : a lesser used component, for texinfo output + * sisu-complete : installing the whole of sisu and its component + parts + may end up using 0.36.4-2 which is proposed new build for Debian + + -- Ralph Amissah <ralph@amissah.com> Sun, 1 Jan 2006 18:20:44 +0000 + +sisu (0.36.4-2) unstable; urgency=low + + * proposed new build for Debian, would become future default build + package is broken into components with different dependencies + corresponding to different possible uses of sisu, which only are + of interest if the functions in those components are to be used. + For example if pdfs are not required the dependency on tetex + including tetex-extra and latex-ucs is unecessarily large, + likewise if postgresql is not going to be used to have a + dependency on postgresql is unecessary. + On the other hand if pdfs are to be generated, there are a number + of dependencies beyond tetex that are required which can be + confusing, (and which have cased users grief in the past). + Likewise for either sql database supported in the default install + the dependencies to get them working is not straightforward. + In this build specifying sisu-pdf will result in the dependencies + for producing pdfs being loaded and sisu-postgresql the necessary + dependencies for that (both large additions if not already + installed or required). Individual components in this build are: + * sisu : basic build, no dependencies really beyond ruby + * sisu-pdf : dependencies for sisu to generate pdfs latex related + * sisu-postgresql : dependencies for sisu to populate a postgresql + database including postgresql itself and various ruby drivers + * sisu-remote : dependencies for remote placement of sisu output, + via ssh and rsync + * sisu-examples : markup and other examples in sisu, fairly large + * sisu-sqlite : dependencies for sisu to populate an sqlite + database including sqlite itself and various ruby drivers + * sisu-vim : vim syntax highlighting and folds only of interest + if vim/gvim is used + * sisu-complete : installing the whole of sisu and its component + parts + [it is also much easier to keep track of which dependency and which + recommendation or suggestion belongs to which component] + + -- Ralph Amissah <ralph@amissah.com> Sun, 1 Jan 2006 17:34:15 +0000 + +sisu (0.36.4-1) unstable; urgency=low + + * built old way for Debian upload (pre-0.31.5 style build. + post 0.32.0 packages are also available in smaller component + parts) + * sisu : basic build, no dependencies really beyond ruby, + all additional requirements for various components specified as + recommendations + * sisu-vim : vim syntax highlighting and folds only of interest + if vim/gvim is used + * sisu-examples : markup and other examples in sisu, fairly large + + * Debian release snapshot (check), uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sun, 1 Jan 2006 17:27:48 +0000 + +sisu (0.36.3-1) unstable; urgency=low + + * New upstream, fixes related to multi-language, and sysnv change to + initialization of constants + + -- Ralph Amissah <ralph@amissah.com> Sat, 31 Dec 2005 15:07:18 +0000 + +sisu (0.36.2-1) unstable; urgency=low + + * New upstream, small fixes + + -- Ralph Amissah <ralph@amissah.com> Fri, 30 Dec 2005 23:54:34 +0000 + +sisu (0.36.1-1) unstable; urgency=low + + * New upstream, minor fix + html batch processing output file placement + + -- Ralph Amissah <ralph@amissah.com> Thu, 29 Dec 2005 23:22:47 +0000 + +sisu (0.36.0-1) unstable; urgency=low + + * New upstream, change to some default settings, + else minor refinements + + -- Ralph Amissah <ralph@amissah.com> Thu, 29 Dec 2005 17:43:00 +0000 + +sisu (0.35.0-1) unstable; urgency=low + + * New upstream, multilingual document model + + -- Ralph Amissah <ralph@amissah.com> Wed, 28 Dec 2005 01:32:32 +0000 + +sisu (0.34.2-1) unstable; urgency=low + + * New upstream: fix in css image path; digests added some doc info + + -- Ralph Amissah <ralph@amissah.com> Mon, 19 Dec 2005 18:42:42 +0000 + +sisu (0.34.1-1) unstable; urgency=low + + * New upstream, small mostly cosmetic changes related to metaverse: + (html and wmap output); url correction (html output); md5s for + sourcefiles if shared + + -- Ralph Amissah <ralph@amissah.com> Sun, 18 Dec 2005 23:00:16 +0000 + +sisu (0.34.0-1) unstable; urgency=low + + * New upstream: includes changes to directory structure for + configuration, of both + local markup directories, and + ouput/publishing directories + + -- Ralph Amissah <ralph@amissah.com> Sun, 18 Dec 2005 00:34:32 +0000 + +sisu (0.33.0-1) unstable; urgency=low + + * New upstream, (some changes to processing paths) + + -- Ralph Amissah <ralph@amissah.com> Thu, 15 Dec 2005 02:03:37 +0000 + +sisu (0.32.5-1) unstable; urgency=low + + * orig.tar.gz should now be updated together with debian package + orig.tar.gz has not been updated properly since 0.31.4, debian + package has issue with autopackage builder + + * debian package improved, however: diffs started from scratch, + information/history abandoned + Reason: undetermined problem with (home brewed) automated package + builder. automated package builder (which uses darcs and + darcs-buildpackage) builds package normally/properly with a + pristine directory structure, but not with accumulated debian + build history. + For now, the orig.tar.gz and debian package structure are + updated, and debian history is not included. + + * directory named extra removed from source tarball, + extra/debian/man moved to debian/man + + * debian, correction of a man page + + -- Ralph Amissah <ralph@amissah.com> Wed, 14 Dec 2005 05:39:43 +0000 + +sisu (0.32.4-1) unstable; urgency=low + + * New upstream (odf images, and document metadata) + + -- Ralph Amissah <ralph@amissah.com> Tue, 13 Dec 2005 02:11:01 +0000 + +sisu (0.32.3-1) unstable; urgency=low + + * New upstream, (includes minor re-fix to html endnote urls) + + -- Ralph Amissah <ralph@amissah.com> Sun, 11 Dec 2005 13:52:15 +0000 + +sisu (0.32.2-1) unstable; urgency=low + + * Upstream sqlite repair + + -- Ralph Amissah <ralph@amissah.com> Thu, 8 Dec 2005 18:54:18 +0000 + +sisu (0.32.1-1) unstable; urgency=low + + * Debian control, comma added to comma delimited depends list for + sisu_complete + + * Minor cleaning of upstream, and a file dropped (hmtl_css) + + -- Ralph Amissah <ralph@amissah.com> Sat, 3 Dec 2005 21:52:59 +0000 + +sisu (0.32.0-1) unstable; urgency=low + + * New upstream, minor changes + + -- Ralph Amissah <ralph@amissah.com> Thu, 1 Dec 2005 23:33:20 +0000 + +sisu (0.31.5-1) unstable; urgency=low + + * New upstream + + * Debian package, complete replaces composite, remote introduced + directory structure changed extra/debian instead of man.deb + + -- Ralph Amissah <ralph@amissah.com> Thu, 1 Dec 2005 19:20:14 +0000 + +sisu (0.31.4-1) unstable; urgency=low + + * Debian packages broken down, for better control over dependencies + several smaller packages, source package structure affected + (control, .install, .manpages) + + * sisu-composite together with sisu-examples installs all sisu + + -- Ralph Amissah <ralph@amissah.com> Tue, 29 Nov 2005 05:32:29 +0000 + +sisu (0.31.3-2) unstable; urgency=low + + * debian:control Depends: ruby (>=1.8.2) + + -- Ralph Amissah <ralph@amissah.com> Mon, 28 Nov 2005 20:17:53 +0000 + +sisu (0.31.3-1) unstable; urgency=low + + * New upstream, control file: + ruby depends made 1.8.3 + checked with pbuilder, misc:Depends removed + + -- Ralph Amissah <ralph@amissah.com> Mon, 28 Nov 2005 03:55:19 +0000 + +sisu (0.31.2-1) unstable; urgency=low + + * debian autobuilding fix to external scaffolding + [package has same contents as 0.31.1] + + -- Ralph Amissah <ralph@amissah.com> Sat, 26 Nov 2005 17:46:55 +0000 + +sisu (0.31.1-1) unstable; urgency=low + + * New upstream, minor fixes + [Note: change to automated debian build procedure] + + -- Ralph Amissah <ralph@amissah.com> Sat, 26 Nov 2005 15:20:47 +0000 + +sisu (0.31.0-1) unstable; urgency=low + + * New upstream following 0.30.9 path + for header regex: italics & bold (0.30.10 follows 0.30.8) + + -- Ralph Amissah <ralph@amissah.com> Fri, 25 Nov 2005 23:32:54 +0000 + +sisu (0.30.10-1) unstable; urgency=low + + * New upstream, rollback in behavior to 0.30.8 header matching for + bold and italics (comma delimited list), 0.30.9 changes now mapped + to version 0.31 + + -- Ralph Amissah <ralph@amissah.com> Fri, 25 Nov 2005 22:55:37 +0000 + +sisu (0.30.9-1) unstable; urgency=low + + * New upstream, adjustment to package unpack directory structure + to match new setup.rb default man directory moved from data/man + (install directory structure should remain the same) + Minero Aoki's setup.rb included as an alterantive installer + for source package + + -- Ralph Amissah <ralph@amissah.com> Wed, 23 Nov 2005 00:25:04 +0000 + +sisu (0.30.8-1) unstable; urgency=low + + * New upstream, LaTeX related, use of pdflatex, + and pdfetex with pdflatex parameters (Debian specific) + + -- Ralph Amissah <ralph@amissah.com> Tue, 22 Nov 2005 01:25:58 +0000 + +sisu (0.30.7-1) unstable; urgency=low + + * New upstream, composite document fix, manual closure of file + otherwise minor + + -- Ralph Amissah <ralph@amissah.com> Mon, 21 Nov 2005 01:23:49 +0000 + +sisu (0.30.6-1) unstable; urgency=low + + * New upstream, minor + + -- Ralph Amissah <ralph@amissah.com> Sun, 20 Nov 2005 19:46:48 +0000 + +sisu (0.30.5-1) unstable; urgency=low + + * New upstream, minor fixes + + -- Ralph Amissah <ralph@amissah.com> Sun, 20 Nov 2005 02:28:08 +0000 + +sisu (0.30.4-1) unstable; urgency=low + + * New upstream, minor fixes and a file renamed + + -- Ralph Amissah <ralph@amissah.com> Sat, 19 Nov 2005 23:19:08 +0000 + +sisu (0.30.3-1) unstable; urgency=low + + * New upstream, markup dir ./_sisu/conf replaces ./_sisu/config + minor bugfix for pgsql (8.1) + control file sisu reorganised + debian control suggests keychain (added) + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sat, 19 Nov 2005 01:25:34 +0000 + +sisu (0.30.2-1) unstable; urgency=low + + * New upstream, cleaning, minor + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Wed, 16 Nov 2005 00:26:57 +0000 + +sisu (0.30.1-1) unstable; urgency=low + + * New upstream, minor + + -- Ralph Amissah <ralph@amissah.com> Mon, 14 Nov 2005 18:14:39 +0000 + +sisu (0.30.0-1) unstable; urgency=low + + * New upstream, metadata, third acronym fixed + + -- Ralph Amissah <ralph@amissah.com> Sun, 13 Nov 2005 17:49:47 +0000 + +sisu (0.29.5-1) unstable; urgency=low + + * New upstream, retract latex to pdf changes for now + + -- Ralph Amissah <ralph@amissah.com> Fri, 11 Nov 2005 07:47:51 +0000 + +sisu (0.29.4-1) unstable; urgency=low + + * New upstream, latex to pdf looks to use pdfetex, pdftex or pdflatex + (there has been some debian renaming), + opendocument.rb renamed odf.rb + + -- Ralph Amissah <ralph@amissah.com> Fri, 11 Nov 2005 02:17:03 +0000 + +sisu (0.29.3-1) unstable; urgency=low + + * New upstream, new processing features, new processing flags, + plus some flags changed (is release candidate for 0.30.0) + + -- Ralph Amissah <ralph@amissah.com> Wed, 9 Nov 2005 06:11:53 +0000 + +sisu (0.29.2-1) unstable; urgency=low + + * New upstream, new directory data/sisu created to remove creaping + dependency of sisu main package on sisu-examples for run time png + and odf files, necessary adjustment in debian/sisu.install + + -- Ralph Amissah <ralph@amissah.com> Mon, 7 Nov 2005 07:55:59 +0000 + +sisu (0.29.1-1) unstable; urgency=low + + * New upstream, control adds suggests lv (file encoding conversions) + and rcs (as alternative to cvs, for document version number + tracking) + + -- Ralph Amissah <ralph@amissah.com> Sat, 5 Nov 2005 17:16:36 +0000 + +sisu (0.29.0-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Mon, 31 Oct 2005 18:22:28 +0000 + +sisu (0.28.4-1) unstable; urgency=low + + * New upstream, minor change to package description, + for other changes see version_manifest + + -- Ralph Amissah <ralph@amissah.com> Mon, 31 Oct 2005 17:56:13 +0000 + +sisu (0.28.3-1) unstable; urgency=low + + * New upstream, touch + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sun, 23 Oct 2005 00:28:44 +0100 + +sisu (0.28.2-1) unstable; urgency=low + + * New upstream, character encoding related, utf-8 + + -- Ralph Amissah <ralph@amissah.com> Sat, 22 Oct 2005 23:22:14 +0100 + +sisu (0.28.1-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Sat, 22 Oct 2005 18:47:25 +0100 + +sisu (0.28.0-1) unstable; urgency=low + + * New upstream, Debian released ruby-1.8.3-2 which does not segfault + sisu, this version number increse obsoletes emergency sisu-0.27.0 + build, that was made available, as workaround to ruby segfault + problem + + -- Ralph Amissah <ralph@amissah.com> Fri, 21 Oct 2005 02:40:25 +0100 + +sisu (0.26.4-1) unstable; urgency=low + + * New upstream, (a) control recommend added sqlite, previously + overlooked; (b) recommend zip added used in making of open + document (c) recommend removed incorrect libcgi_ruby + (libfcgi-ruby1.8 remains) (d) added basic open document file + structure as a .tgz file + + -- Ralph Amissah <ralph@amissah.com> Tue, 18 Oct 2005 03:09:12 +0100 + +sisu (0.26.3-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Fri, 7 Oct 2005 02:16:59 +0100 + +sisu (0.26.2-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Fri, 30 Sep 2005 20:51:19 +0100 + +sisu (0.26.1-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Sun, 18 Sep 2005 23:36:17 +0100 + +sisu (0.26.0-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Sun, 18 Sep 2005 12:21:55 +0100 + +sisu (0.25.11-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Sat, 17 Sep 2005 01:53:12 +0100 + +sisu (0.25.10-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Fri, 16 Sep 2005 00:01:49 +0100 + +sisu (0.25.9-1) unstable; urgency=low + + * New upstream + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Wed, 14 Sep 2005 18:30:27 +0100 + +sisu (0.25.8-1) unstable; urgency=low + + * New upstream, pinfo added to suggests + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Wed, 14 Sep 2005 01:41:04 +0100 + +sisu (0.25.7-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Tue, 13 Sep 2005 07:04:45 +0100 + +sisu (0.25.6-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Mon, 12 Sep 2005 19:00:04 +0100 + +sisu (0.25.5-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Mon, 12 Sep 2005 05:14:48 +0100 + +sisu (0.25.4-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Mon, 12 Sep 2005 04:37:36 +0100 + +sisu (0.25.3-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Mon, 12 Sep 2005 03:01:02 +0100 + +sisu (0.25.2-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Sat, 10 Sep 2005 21:37:18 +0100 + +sisu (0.25.1-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Sat, 10 Sep 2005 19:33:04 +0100 + +sisu (0.25.0-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Sat, 10 Sep 2005 16:11:25 +0100 + +sisu (0.24.2-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Fri, 9 Sep 2005 18:23:08 +0100 + +sisu (0.24.1-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Thu, 8 Sep 2005 22:08:45 +0100 + +sisu (0.24.0-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Wed, 7 Sep 2005 18:55:34 +0100 + +sisu (0.23.1-1) unstable; urgency=low + + * New upstream, cgi (naive) search form generator added to lib + + -- Ralph Amissah <ralph@amissah.com> Wed, 7 Sep 2005 01:33:34 +0100 + +sisu (0.23.0-1) unstable; urgency=low + + * New upstream, input files changed to use utf-8 or iso8859, + new recommends: latex-ucs (required if generating pdf) and + librmagick-ruby + + -- Ralph Amissah <ralph@amissah.com> Tue, 6 Sep 2005 02:11:55 +0100 + +sisu (0.22.1-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Thu, 1 Sep 2005 02:51:35 +0100 + +sisu (0.22.0-1) unstable; urgency=low + + * New upstream: + Recommends rmagick (ruby imagemagick library), + FSF address updated. + + -- Ralph Amissah <ralph@amissah.com> Wed, 31 Aug 2005 02:15:38 +0100 + +sisu (0.21.2-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Sun, 28 Aug 2005 19:43:15 +0100 + +sisu (0.21.1-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Sun, 28 Aug 2005 16:04:55 +0100 + +sisu (0.21.0-1) unstable; urgency=low + + * New upstream, some changes to directory structure + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sun, 28 Aug 2005 00:34:37 +0100 + +sisu (0.20.9-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Fri, 26 Aug 2005 01:08:38 +0100 + +sisu (0.20.8-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Thu, 25 Aug 2005 02:08:18 +0100 + +sisu (0.20.7-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Wed, 24 Aug 2005 17:45:22 +0100 + +sisu (0.20.6-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Mon, 22 Aug 2005 21:00:25 +0100 + +sisu (0.20.5-1) unstable; urgency=low + + * New upstream + + -- Ralph Amissah <ralph@amissah.com> Fri, 19 Aug 2005 15:54:26 +0100 + +sisu (0.20.4-1) unstable; urgency=low + + * New upstram. Removed ruby-libyaml (a bit of a story why it is there + in the first place, as is not required for ruby >=1.8 i.e. the + versions of ruby that sisu is written for) + + -- Ralph Amissah <ralph@amissah.com> Thu, 18 Aug 2005 23:17:26 +0100 + +sisu (0.20.3-1) unstable; urgency=low + + * New upstream + + * Debian release snapshot, uploaded by Wookey + + -- Ralph Amissah <ralph@amissah.com> Sun, 14 Aug 2005 13:54:33 +0100 + +sisu (0.20.2-1) unstable; urgency=low + + * New upstream (from now) signed against ralph@amissah.com + (previous against ralph.amissah@gmail.com) + + -- Ralph Amissah <ralph@amissah.com> Sun, 14 Aug 2005 03:11:10 +0100 + +sisu (0.20.1-1) unstable; urgency=low + + * signed dsc & changes files + + -- Ralph Amissah <ralph@amissah.com> Fri, 12 Aug 2005 12:27:56 +0100 + +sisu (0.20.0-2) unstable; urgency=low + + * debian/control recommend postgresql (>=8.0.0). correction + + -- Ralph Amissah <ralph@amissah.com> Thu, 11 Aug 2005 21:22:57 +0100 + +sisu (0.20.0-1) unstable; urgency=low + + * New upstream package, default database names changed + + -- Ralph Amissah <ralph@amissah.com> Thu, 11 Aug 2005 20:36:01 +0100 + +sisu (0.18.8-1) unstable; urgency=low + + * New upstream package + + -- Ralph Amissah <ralph@amissah.com> Wed, 10 Aug 2005 21:13:33 +0100 + +sisu (0.18.7-1) unstable; urgency=low + + * New upstream package: conflcting license note removed + + * Debian release snapshot, uploaded by Joachim Breitner + + -- Ralph Amissah <ralph@amissah.com> Tue, 9 Aug 2005 02:27:27 +0100 + +sisu (0.18.6-1) unstable; urgency=low + + * New upstream package + + -- Ralph Amissah <ralph@amissah.com> Mon, 8 Aug 2005 12:44:06 +0100 + +sisu (0.18.5-1) unstable; urgency=low + + * New upstream package + + -- Ralph Amissah <ralph@amissah.com> Sun, 7 Aug 2005 00:17:45 +0100 + +sisu (0.18.4-1) unstable; urgency=low + + * New upstream package + + -- Ralph Amissah <ralph@amissah.com> Wed, 3 Aug 2005 11:00:05 +0100 + +sisu (0.18.3-1) unstable; urgency=low + + * New upstream package + + -- Ralph Amissah <ralph@amissah.com> Tue, 26 Jul 2005 19:49:18 +0100 + +sisu (0.18.2-1) unstable; urgency=low + + * New upstream package + + -- Ralph Amissah <ralph@amissah.com> Mon, 25 Jul 2005 19:16:30 +0100 + +sisu (0.18.1-1) unstable; urgency=low + + * New upstream package + + -- Ralph Amissah <ralph@amissah.com> Sun, 24 Jul 2005 19:46:03 +0100 + +sisu (0.18.0-1) unstable; urgency=low + + * New upstream package: metaverse structure change, includes md5 + digests of objects (paragraphs, tables, images, endnotes etc) + + -- Ralph Amissah <ralph@amissah.com> Fri, 22 Jul 2005 11:41:30 +0100 + +sisu (0.16.25-1) unstable; urgency=low + + * change to markup for Free as in Freedom only + + * Initial Debian release, uploaded by Gunnar Wolf (at Debconf5) + + -- Ralph Amissah <ralph@amissah.com> Sat, 16 Jul 2005 21:15:32 +0100 + +sisu (0.16.24-1) unstable; urgency=low + + * copyright string made more clear as 1997, 1998, 1999, 2000, 2001, 2002, + 2003, 2004, 2005 ... only question being whether it should not have been + 1996. + + -- Ralph Amissah <ralph@amissah.com> Tue, 12 Jul 2005 20:04:21 +0100 + +sisu (0.16.23-1) unstable; urgency=low + + * copyright headers changed within files for Debian + + * some changes in use of ocn for segment naming in html output + + * a couple of postgresql fileds changed to text + + * cosmetic rearrangement of code + + -- Ralph Amissah <ralph@amissah.com> Tue, 12 Jul 2005 18:47:31 +0100 + +sisu (0.16.22-1) unstable; urgency=low + + * metaverse fix for alternative endnote markup marker + at end of line~^ + + * texpdf fix for images, (where dimensions not + provided) not final, may need to pass through + imagemagick at metaverse stage + + * fix to cgi sample sisu_search.cgi + + -- Ralph Amissah <ralph@amissah.com> Thu, 7 Jul 2005 19:04:52 +0100 + +sisu (0.16.21-1) unstable; urgency=low + + * minor bugfix (param screen print) + + -- Ralph Amissah <ralph@amissah.com> Sun, 3 Jul 2005 14:33:00 +0100 + +sisu (0.16.20-1) unstable; urgency=low + + * separated out sisu vim files (syntax & folds) + + * touch to syntax highlighting + + -- Ralph Amissah <ralph@amissah.com> Sun, 3 Jul 2005 12:56:13 +0100 + +sisu (0.16.19-1) unstable; urgency=low + + * small touches to vim syntax highlighting. + + -- Ralph Amissah <ralph@amissah.com> Fri, 1 Jul 2005 18:37:44 +0100 + +sisu (0.16.18-1) unstable; urgency=low + + * some fixes to vim syntax highlighing: - changes to markup syntax + introduced in 0.16 release broke parts of syntax highlighter, + more no doubt to follow. + + -- Ralph Amissah <ralph@amissah.com> Fri, 1 Jul 2005 02:35:13 +0100 + +sisu (0.16.17-1) unstable; urgency=low + + * separated color file out from ftplugin ... called dusk (or slate) by + me for several years i now call it sisu... perhaps i should stick + with slate as it is pretty appropriate... hmmm, slate + + * NB there is an issue with debuild or darcs-buildpackage after tonight's + update, have fallen to an older installation, lintian check version + given is from a newer install, so gives a warning. + + -- Ralph Amissah <ralph@amissah.com> Thu, 30 Jun 2005 01:03:25 +0100 + +sisu (0.16.16-1) unstable; urgency=low + + * small touches to offer vim config files working the way i am used to + with Debian install... needs testing by someone with different + habits though. + + -- Ralph Amissah <ralph@amissah.com> Wed, 29 Jun 2005 21:39:55 +0100 + +sisu (0.16.15-1) unstable; urgency=low + + * separated vim syntax and ftplugin directory... + have still got color file in ftplugin/sisu.vim file + which is not acceptable + + -- Ralph Amissah <ralph@amissah.com> Wed, 29 Jun 2005 18:17:16 +0100 + +sisu (0.16.14-1) unstable; urgency=low + + * sisu vim ftplugin ... for folds, syntax, colors, markup + auto installed in debian, + (but uses shared filetype in /usr/share/vim/addons + check how that is supposed to work) + else (non-debian install) + Rantfile places in /usr/share/sisu-examples/config/vim + + -- Ralph Amissah <ralph@amissah.com> Wed, 29 Jun 2005 17:02:20 +0100 + +sisu (0.16.13-1) unstable; urgency=low + + * debian setup of vim syntax ok... however much vim setup still + to automate, immediately noticable: folds for sisu not sorted; + and permitting cursor movement up and down without following + long lines with screen wrap; (and no clever way yet to + contribute colors other than through sisu-examples, but + they being user preference should be contributed with care). + + * on_markup.txt quick check & minor update + + -- Ralph Amissah <ralph@amissah.com> Wed, 29 Jun 2005 06:01:38 +0100 + +sisu (0.16.12-1) unstable; urgency=low + + * home page index.html creation, path precedence set: + ~/.sisu/skin/doc + /etc/sisu/skin/doc + defaults + and content is interchangeable (so future latent break + is less likely) + + * touch to Rantfile + + -- Ralph Amissah <ralph@amissah.com> Mon, 27 Jun 2005 23:26:52 +0100 + +sisu (0.16.11-1) unstable; urgency=low + + * bugfix a default variable, + in defaults version should be @ver + quick fix, revist: currently index.html taken from + ~/.sisu/skin/doc if it exists else defaults, + /etc/sisu/skin/doc is ignored, breaking expected precedence + + -- Ralph Amissah <ralph@amissah.com> Mon, 27 Jun 2005 18:09:13 +0100 + +sisu (0.16.10-1) unstable; urgency=low + + * small edits to man pages and help + NB have taken out reference to alternative markup possibilites + e.g. b{ for bold }b being available as well as + *{ bold text }* (as the letter the and html equivalents are + depreciated, having or using alternative markup styles is + less tidy) + + -- Ralph Amissah <ralph@amissah.com> Sun, 26 Jun 2005 23:49:31 +0100 + +sisu (0.16.9-1) unstable; urgency=low + + * cleaning up of man pages, largely for html presentation + generated by rman + + -- Ralph Amissah <ralph@amissah.com> Sun, 26 Jun 2005 03:10:51 +0100 + +sisu (0.16.8-1) unstable; urgency=low + + * minor edits + + -- Ralph Amissah <ralph@amissah.com> Sat, 25 Jun 2005 17:45:12 +0100 + +sisu (0.16.7-1) unstable; urgency=low + + * added the man pages in html (converted to html using rman) + http://polyglotman.sourceforge.net/rman.html + + * related rather cosmetic changes + + -- Ralph Amissah <ralph@amissah.com> Sat, 25 Jun 2005 16:37:30 +0100 + +sisu (0.16.6-1) unstable; urgency=low + + * vim folds for sisu markup files updated command is :F (ruby folds :R) + assuming the file is in place and in use + + -- Ralph Amissah <ralph@amissah.com> Sat, 25 Jun 2005 04:24:22 +0100 + +sisu (0.16.5-1) unstable; urgency=low + + * some cleaning of wordmap output, regex exclusions added, not elegant + (special issue pages include sha and md5 output, also excluded) + + * [released 0.16.6:] vim folds for sisu markup files updated command + is :F (ruby folds :R) assuming the file is in place and in use + + * comments, url locations of samples, output, etc. added to + markup syntax files (in addition to SiSU home which was already + there) + + * removed from tarball markup samples eu contract + law principles can be found at + http://www.jus.uio.no/sisu/sample + + -- Ralph Amissah <ralph@amissah.com> Fri, 24 Jun 2005 19:17:43 +0100 + +sisu (0.16.4-1) unstable; urgency=low + + * man 8 sisu post installation instructions looked at + + * an image path adjusted + + -- Ralph Amissah <ralph@amissah.com> Thu, 23 Jun 2005 06:08:38 +0100 + +sisu (0.16.3-1) unstable; urgency=low + + * tables fixed, much latent breakage sorted + * html segments fixed (scroll was ok) + * xml sax and dom sorted + * xml css naive but done + * latex/pdf done + + -- Ralph Amissah <ralph@amissah.com> Thu, 23 Jun 2005 00:42:04 +0100 + +sisu (0.16.2-1) unstable; urgency=low + + * conditional heading reinstated /^[12~{ }~ \?\s/ + (may be used when it is expected that a document may be + imported into another, and the controling documents level + 1 and/or 2 headings should be used instead (take precedence)) + + * rant install options, force specification of root if wish to + proceed as root, (previously was default on ok or continue) + + -- Ralph Amissah <ralph@amissah.com> Wed, 22 Jun 2005 18:08:19 +0100 + +sisu (0.16.1-1) unstable; urgency=low + + * touches to documentation, markup related + + * markup syntax table is out of date, reference to it removed + replaced by suggestion you see online markup sample directory + http://www.jus.uio.no/sisu/sample + + * fix, one sample document was overlooked in last package + (autonomy_markup2) + + * in ./debian/control updated lintian standards version number + to 3.6.2 from 3.6.1 + (to get rid of lintian warning: out-of-date-standards-version) + + -- Ralph Amissah <ralph@amissah.com> Wed, 22 Jun 2005 02:12:58 +0100 + +sisu (0.16.0-1) unstable; urgency=low + + * development branch folded back in to main, + plus a couple of touches + a bit early, testing now required in stable + WARNING Breaks Old Markup Syntax + + Markup Syntax Cleaning - reduction in characters used + and the removal of several uses of unclosed curly brackets + + Vim Regex Substitution Summary of Markup Syntax Changes: + :%s/\([0-6]\){\~\?/\1\~/c + :%s/ #\~\(\S\+\)/\*\~\1/c + :%s/^#{\~\?\s*/% /c + :%s/^r{ /<< /c + :%s/\~e/\~^/c + :%s/[-~]{ /^\~ /c + + -- Ralph Amissah <ralph@amissah.com> Tue, 21 Jun 2005 03:35:13 +0100 + +sisu (0.15.2-1) unstable; urgency=low + + * bugfix for composite documents, place newline + and mark end of import + (bug also in current stable 0.14.6) + + * bugfix for [html] endnotes introduced (in param) + in development branch + + * number paragraph in given heading sequence + while escaping from being a heading 5~- 6~- + + * filenames for termsheet and standard_form + sisu -t + + * fix webrick port settings sysenv + + * html subtoc touch required + + * cgi example touched + + * help files updated on syntax changes + + * vim syntax files updated + + * testing required + + -- Ralph Amissah <ralph@amissah.com> Tue, 21 Jun 2005 01:54:38 +0100 + +sisu (0.15.1-1) unstable; urgency=low + + * Syntax Changes, WARNING breaks old syntax, + + * endnotes where not embedded within text, + i.e. endnote following paragraph with endnote marker + ~^ replaces ~e as marker within text + ^~ for endnote content instead of -{ or ~{ [at the start of a + line] + {~^ shortcut for making link with url as endnote }http://url + instead of {~e previous shortcut}http://url + + * help files updated on syntax changes + + * vim syntax files updated + + * extensive testing required + + -- Ralph Amissah <ralph@amissah.com> Mon, 20 Jun 2005 04:17:13 +0100 + +sisu (0.15.0-1) unstable; urgency=low + + * syntax change, WARNING breaks old syntax, + a theme is the reduction of characters, + and the removal of most uclosed curly braces where used previously + + * to mark headers and heading levels: + ^[0-6~{ }~ replaces ^[0-6]\{~? + header & headings marked by digit tilde at start of the line + tilde replacing unclosed curly brace occuring after + digit at beginning of line + vim: + :%s/\([0-6]\){\~\?/\1\~/c + * to provide html name tag within text: + *~name replaces #~name + vim: + :%s/ #\~\(\S\+\)/\*\~\1/c + * a comment: + ^% replacing ^#{ + ^%% fold set in vim for such comment marker + vim: + :%s/^#{ /% /c + * require external document fold marker + << replacing r{ + vim: + :%s/^r{ /<< /c + header and headings change is fairly major as affects most code + worth the break, i think so, given goal of simplicity and minimalism + however, syntax higlighting becomes even more crucial + as becomes more difficult to spot headings otherwise + NB summary of vim conversions: + :%s/\([0-6]\){\~\?/\1\~/c + :%s/ #\~\(\S\+\)/\*\~\1/c + :%s/^#{ /% /c + + * help files updated on syntax changes + + * vim syntax files updated + + * extensive testing required + + -- Ralph Amissah <ralph@amissah.com> Sun, 19 Jun 2005 15:23:19 +0100 + +sisu (0.14.6-1) unstable; urgency=low + + * texpdf removed whitespace around \\href{[url]} in a few locations + (latexpdf appears possibly to have problem in passing url to browser + including whitespaces before and after url) + + * in all source code headers took out development branch reference, + leave it to the download page to keep other urls updated + author field Ralph Amissah, (instead of similar email address) + propagated alternative name 'Serialized Information, Structured + Units' + (used earlier but not consistently) + + * skin headers likewise looked at and modified + + * touch to default index.html (in defaults and associated + skin) + + -- Ralph Amissah <ralph@amissah.com> Sat, 18 Jun 2005 14:10:37 +0100 + +sisu (0.14.5-1) unstable; urgency=low + + * debian/control sisu now suggests sisu-examples + + * added reference to abandoned U.S. provisional patent application + + -- Ralph Amissah <ralph@amissah.com> Sat, 18 Jun 2005 00:14:20 +0100 + +sisu (0.14.4-1) unstable; urgency=low + + * removed copyright mark from 0{~prefix + is distinct from 0{~rights which is related to copyright + + * texpdf - pass author through "special character" filter + + * bug fix for minor numbering using # mark, and re-calibrating + removed an extraneous tilde (~) + + -- Ralph Amissah <ralph@amissah.com> Fri, 17 Jun 2005 17:12:48 +0100 + +sisu (0.14.3-1) unstable; urgency=low + + * removed files cgi.rb and cgi_supplies.rb as unused + + -- Ralph Amissah <ralph@amissah.com> Wed, 15 Jun 2005 14:36:55 +0100 + +sisu (0.14.2-1) unstable; urgency=low + + * removed -g option from sisu + + -- ralph <ralph@amissah.com> Tue, 14 Jun 2005 12:15:48 +0100 + +sisu (0.14.1-1) unstable; urgency=low + + * Documentation, minor changes + + -- ralph <ralph@amissah.com> Tue, 14 Jun 2005 02:06:59 +0100 + +sisu (0.14.0-1) unstable; urgency=low + + * Flattened directory structure for ./conf/sisu which maps to /etc/sisu + or equivalent i.e. removed the additional version number which is + not supported by debian packaging, and unnecessary anyway. + (this change is the reason for version the hop to 0.14.0) + + * Changed name of ./conf/sisu/sisurc.yaml.sample_disabled, + is now ./conf/sisu/sisurc.yaml + and enabled with some parts commented out + + * Source Document Digest (using openssl and + currently set to MD5) generated + were cvs document details requested, (request + set in document header). + + * Added man page summary of sisu-examples + (and a README for directory which refers + you to man page) + + -- ralph <ralph@amissah.com> Sat, 4 Jun 2005 01:08:33 +0100 + +sisu (0.12.7-1) unstable; urgency=low + + * NOTE: this version deb package was skipped, + released as tarball 2005w22/2 (20050601) + + * SiSU made convenient to use to produce other formats (including LaTeX) + without the software necessary to produce pdf, i.e. pdflatex + http://www.tug.org/applications/pdftex/ + all this does really is recognise when pdflatex is absent + and pdfs cannot be generated in html generated output + (i.e. no links to pdf are produced, as was + previously the case)) + where pdf output was assumed) + + * remove tetex-base, tetex-extra require dependency + + -- Ralph Amissah <ralph@amissah.com> Thu, 2 Jun 2005 01:21:06 +0100 + +sisu (0.12.6-1) unstable; urgency=low + + * removed sisu-[version number] executable], is not necessary + and did a bit more lintian cleaning + + -- Ralph Amissah <ralph@amissah.com> Thu, 26 May 2005 20:22:37 +0100 + +sisu (0.12.5-1) unstable; urgency=low + + * changed sisu_webrick default port 8081 (from 2000) + + * added short man page for sisu_webrick and sisu_termsheet + + -- Ralph Amissah <ralph@amissah.com> Thu, 26 May 2005 18:24:06 +0100 + +sisu (0.12.4-1) unstable; urgency=low + + * sisu_webrick fix and update + + -- Ralph Amissah <ralph@amissah.com> Thu, 26 May 2005 04:54:40 +0100 + +sisu (0.12.3-1) unstable; urgency=low + + * see changelog + man page update + added as required the virtual package libyaml-ruby + + -- Ralph Amissah <ralph@amissah.com> Wed, 25 May 2005 18:46:56 +0100 + +sisu (0.12.2-1) unstable; urgency=low + + * more packaging automation + * a fix to rant independent 'installer' file, [& added to auto build] + + -- Ralph Amissah <ralph@amissah.com> Mon, 23 May 2005 16:24:29 +0100 + +sisu (0.12.1-1) unstable; urgency=low + + * start with new source, remove last lintian E message + + -- Ralph Amissah <ralph@amissah.com> Mon, 23 May 2005 04:53:40 +0100 + +sisu (0.12.0-1) unstable; urgency=low + + * auto-debianize sisu using rant and darcs-buildpackage + + -- Ralph Amissah <ralph@amissah.com> Thu, 19 May 2005 22:52:27 +0100 + +sisu (0.10.9-1) unstable; urgency=low + + * [generic rant file] + + * [automating debian package builds] + + -- Ralph Amissah <ralph@amissah.com> Thu, 19 May 2005 22:46:54 +0100 + +sisu (0.10.8-1) unstable; urgency=low + + * directory remapping + + -- Ralph Amissah <ralph@amissah.com> Mon, 16 May 2005 22:27:52 +0100 + +sisu (0.10.8) unstable; urgency=low + + * Initial Debian release, uploaded by Gunnar Wolf + + -- Ralph Amissah <ralph@amissah.com> Mon, 16 May 2005 18:39:35 +0100 diff --git a/debian/compat b/debian/compat new file mode 100644 index 00000000..7f8f011e --- /dev/null +++ b/debian/compat @@ -0,0 +1 @@ +7 diff --git a/debian/control b/debian/control new file mode 100644 index 00000000..d5d6c02d --- /dev/null +++ b/debian/control @@ -0,0 +1,107 @@ +Source: sisu +Section: text +Priority: optional +Maintainer: Ralph Amissah <ralph@amissah.com> +Build-Depends: debhelper (>= 7) +Standards-Version: 3.8.4 +Homepage: http://www.jus.uio.no/sisu/ +Vcs-Browser: http://git.sisudoc.org/?p=code/sisu.git +Vcs-Git: git://git.sisudoc.org/git/code/sisu.git +XS-Dm-Upload-Allowed: yes + +Package: sisu +Architecture: all +Depends: ${misc:Depends}, ruby (>= 1.8.2), libwebrick-ruby, rsync, unzip, zip +Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, imagemagick, keychain, librmagick-ruby, librexml-ruby, openssl, openssh-client | lsh-client, tidy, vim-addon-manager +Suggests: lv, pinfo, texinfo, trang +Conflicts: sisu-markup-samples (<= 1.0.11) +Replaces: sisu-markup-samples (<= 1.0.11) +Description: documents - structuring, publishing in multiple formats and search + SiSU is a lightweight markup based, command line oriented, document + structuring, publishing and search framework for document collections. + . + With minimal preparation of a plain-text, (UTF-8) file, using its native + markup syntax in your text editor of choice, SiSU can generate various + document formats (most of which share a common object numbering system for + locating content), including plain text, HTML, XHTML, XML, EPUB, OpenDocument + text (ODF:ODT), LaTeX, PDF files, and populate an SQL database with objects + (roughly paragraph-sized chunks) so searches may be performed and matches + returned with that degree of granularity: your search criteria is met by these + documents and at these locations within each document. Object numbering is + particularly suitable for "published" works (finalized texts as opposed to + works that are frequently changed or updated) for which it provides a fixed + means of reference of content. Document outputs also share semantic meta-data + provided. + . + SiSU also provides concordance files, document content certificates and + manifests of generated output. + . + A vim syntax highlighting file and an ftplugin with folds for sisu markup is + provided, as are syntax highlighting files for kate, kwrite, gedit and + diakonos. Vim 7 includes syntax highlighting for SiSU. + . + man pages, and interactive help are provided. + . + Dependencies for various features are taken care of in sisu related packages. + The package sisu-complete installs the whole of SiSU. + . + Additional document markup samples are provided in the package + sisu-markup-samples which is found in the non-free archive the licenses for + the substantive content of the marked up documents provided is that provided + by the author or original publisher. + +Package: sisu-complete +Architecture: all +Depends: ${misc:Depends}, ruby (>= 1.8.2), sisu, sisu-pdf, sisu-postgresql, sisu-sqlite +Description: installs all SiSU related packages + SiSU is a lightweight markup based document structuring, publishing and search + framework for document collections. + . + This package installs SiSU and related packages that enable sisu to produce + pdf and to populate PostgreSQL and sqlite databases. + . + See sisu for a description of the package. + +Package: sisu-pdf +Architecture: all +Depends: ${misc:Depends}, sisu, texlive-latex-base, texlive-fonts-recommended, texlive-latex-recommended, texlive-latex-extra +Recommends: texlive-xetex +Suggests: evince | pdf-viewer +Description: dependencies to convert SiSU LaTeX output to pdf + SiSU is a lightweight markup based document structuring, publishing and search + framework for document collections. + . + This package enables the conversion of SiSU LaTeX output to pdf. + +Package: sisu-postgresql +Architecture: all +Depends: ${misc:Depends}, sisu, libdbd-pg-ruby, libdbd-pg-ruby1.8, libdbi-ruby, libdbi-ruby1.8, libdbm-ruby, postgresql, libfcgi-ruby1.8 | libfcgi-ruby1.9 +Suggests: postgresql-contrib +Description: SiSU dependencies for use with PostgreSQL database + SiSU is a lightweight markup based document structuring, publishing and search + framework for document collections. + . + This package enables SiSU to populate a PostgreSQL database. This is done at + an object/paragraph level, making granular searches of documents possible. + . + This relational database feature of SiSU is not required but provides + interesting possibilities, including that of granular searches of documents + for matching units of text, primarily paragraphs that can be displayed or + identified by object citation number, from which an index of documents + matched and each matched paragraph within them can be displayed. + +Package: sisu-sqlite +Architecture: all +Depends: ${misc:Depends}, sisu, sqlite3, libsqlite3-ruby, libdbd-sqlite3-ruby, libdbd-sqlite3-ruby1.8, libdbi-ruby, libdbi-ruby1.8, libdbm-ruby, libfcgi-ruby1.8 | libfcgi-ruby1.9 +Description: SiSU dependencies for use with SQLite database + SiSU is a lightweight markup based document structuring, publishing and search + framework for document collections. + . + This package enables SiSU to populate an SQLite database. This is done at an + object/paragraph level, making granular searches of documents possible. + . + This relational database feature of SiSU is not required but provides + interesting possibilities, including that of granular searches of documents + for matching units of text, primarily paragraphs that can be displayed or + identified by object citation number, from which an index of documents + matched and each matched paragraph within them can be displayed. diff --git a/debian/copyright b/debian/copyright new file mode 100644 index 00000000..bb85146f --- /dev/null +++ b/debian/copyright @@ -0,0 +1,41 @@ +Author: Ralph Amissah <ralph@amissah.com> +Download: http://www.jus.uio.no/sisu/ + +Files: * +Copyright: (C) 1997-2009 Ralph Amissah +License: GPL-3+ + 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 3 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, see <http://www.gnu.org/licenses/>. + . + On Debian systems, the complete text of the GNU General Public License + can be found in /usr/share/common-licenses/GPL-3 file. + +Files: setup.rb +Copyright: Minero Aoki <http://i.loveruby.net/en/projects/setup/> +License: LGPL-2.1 + This library is free software; you can redistribute it and/or + modify it under the terms of the GNU Library General Public + License as published by the Free Software Foundation; either + version 2.1 of the License. + . + This library 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 + Library General Public License for more details. + . + You should have received a copy of the GNU Library General Public + License along with this library; if not, write to the Free + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + . + On Debian systems, the complete text of the GNU Library General Public License + can be found in /usr/share/common-licenses/LGPL-2 file. diff --git a/debian/data/doc/sisu/v1/sisu_markup_samples/samples/_sisu/skin/doc/skin_debian.rb b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/_sisu/skin/doc/skin_debian.rb new file mode 100644 index 00000000..bc4008b5 --- /dev/null +++ b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/_sisu/skin/doc/skin_debian.rb @@ -0,0 +1,85 @@ +# coding: utf-8 +=begin + * Name: SiSU information Structuring Universe - Serialised information, Structured Units + * Author: Ralph@Amissah.com + * http://www.jus.uio.no/sisu + * http://www.jus.uio.no/sisu/SiSU/download + * Description: Document skin for SiSU descriptive pages, ... + * License: Same as SiSU see http://www.jus.uio.no/sisu + * Notes: Site default appearance variables set in defaults.rb + Generic site wide modifications set here scribe_skin.rb, and this file required by other "scribes" instead of defaults.rb +=end +module SiSU_Viz + require "#{SiSU_lib}/defaults" #<url:zxy_defaults.rb> + class Skin + #% path + def path_root + './sisu/' # the only parameter that cannot be changed here + end + def path_rel + '../' + end + #% url + def url_root_http + 'http://www.jus.uio.no/sisu' + end + def url_home + 'http://www.debian.org/' + end + def url_site # used in pdf header + 'http://www.debian.org' + end + def url_txt # text to go with url usually stripped url + 'www.debian.org' + end + def url_home_url + '../index.html' + end + #% color + def color_band1 + '"#ffffff"' + end + def color_band2 + '"#ffffff"' + end + #% txt + def txt_hp + ' Debian' + end + def txt_home + 'Debian' + end + #% icon + def icon_home_button + 'debian_home.png' + end + def icon_home_banner + home_button + end + #% banner + def banner_home_button + %{<table summary="home button" border="0" cellpadding="3" cellspacing="0"><tr><td align="left" bgcolor="#ffffff"><a href="#{url_site}/">#{png_home}</a></td></tr></table>\n} + end + def banner_home_and_index_buttons + %{<table><tr><td width="20%"><table summary="home and index buttons" border="0" cellpadding="3" cellspacing="0"><tr><td align="left" bgcolor="#ffffff"><a href="#{url_site}/" target="_top">#{png_home}</a>#{table_close}</td><td width="60%"><center><center><table summary="buttons" border="1" cellpadding="3" cellspacing="0"><tr><td align="center" bgcolor="#ffffff"><font face="arial" size="2"><a href="toc" target="_top"> This text sub- <br /> Table of Contents </a></font>#{table_close}</center></center></td><td width="20%"> #{table_close}} + end + def banner_band + %{<table summary="band" border="0" cellpadding="3" cellspacing="0"><tr><td align="left" bgcolor="#ffffff"><a href="#{url_site}/" target="_top">#{png_home}</a>#{table_close}} + end + end + class TeX + def header_center + "\\chead{\\href{#{@vz.url_site}/}{www.debian.org}}" + end + def home_url + "\\href{#{@vz.url_site}/}{www.debian.org}" + end + def home + "\\href{#{@vz.url_site}/}{Debian}" + end + def owner_chapter + "Document owner details" + end + end +end + diff --git a/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2.adjusted.sst b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2.adjusted.sst new file mode 100644 index 00000000..0f29c9f9 --- /dev/null +++ b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2.adjusted.sst @@ -0,0 +1,505 @@ +% SiSU 0.38 + +@title: Debian Constitution + +@subtitle: Constitution for the Debian Project (v1.2) [This Document has been Superseded by v1.3] + +@creator: Debian Project + +@type: information + +@subject: debian policy + +@date.created: 1998-12-03 + +@date.issued: 1998-12-03 + +@date.valid: 2003-10-29 + +@date.available: 2003-10-29 + +@date.modified: 2003-10-29 + +@date: 2003-10-29 + +@language.document: English + +@language.original: English + +@level: new=C; num_top=1 + +@skin: skin_debian + +@bold: Debian; DPL + +% @italics: + +@links: {Authoritative Source Document}http://www.debian.org/devel/constitution +{SiSU version using default markup}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{SiSU version markup adjusted to correspond to original document}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{Debian Social Contract @ SiSU}http://www.jus.uio.no/sisu/debian_social_contract_v1.1/sisu_manifest.html +{Debian Project}http://www.debian.org/ +{About Debian}http://www.debian.org/intro/about +{News}http://www.debian.org/News/ +{Getting Debian}http://www.debian.org/distrib/ +{Support}http://www.debian.org/support +{Developer's Corner}http://www.debian.org/devel/ +{Site map}http://www.debian.org/sitemap +{Search}http://search.debian.org/ +{License}http://www.debian.org/license + +@rights: http://www.debian.org/license Copyright © 1997-2006 Software in the Public Interest, Inc., P.O. Box 501248, Indianapolis, IN 46250-6248, United States, http://www.spi-inc.org/ <br>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 local copy http://www.debian.org/opl, the latest version is usually available at http://www.opencontent.org/ ). <br>"Debian" and the Debian Logo http://www.debian.org/logos/ are trademarks of Software in the Public Interest, Inc. + +@prefix: This Document is Superseded by Version 1.3.<br>This version 1.2 was taken from the authoritative source at http://www.debian.org/devel/constitution and is marked up as a SiSU sample document.<br>Version 1.2 ratified on October 29th, 2003. Supersedes Version 1.1 http://www.debian.org/devel/constitution.1.1 ratified on June 21st, 2003, which itself supersedes Version 1.0 http://www.debian.org/devel/constitution.1.0 ratified on December 2nd, 1998.<br>Two different SiSU marked up versions are provided http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html uses simpler markup, the default numbering mode; http://www.jus.uio.no/sisu/debian_constitution_v1.2.adjusted/sisu_manifest.html uses more complicated numbering in the markup and is more true to the original + +@rcs: $Id: debian_constitution_v1.2.adjusted.sst,v 1.2 2006/05/24 03:37:02 ralph Exp $ + +:A~ Debian Constitution + +:B~ Constitution for the Debian Project (v1.2) [This Document has been Superseded by v1.3] + +1~pre [Prefix]-# + +Version 1.2 ratified on October 29th, 2003. Supersedes {Version 1.1}http://www.debian.org/devel/constitution.1.1 ratified on June 21st, 2003, which itself supersedes {Version 1.0}http://www.debian.org/devel/constitution.1.0 ratified on December 2nd, 1998. + +1~ 1. Introduction + +/{The Debian Project is an association of individuals who have made common cause to create a free operating system.}/ + +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. + +1~ 2. Decision-making bodies and individuals + +Each decision in the Project is made by one or more of the following: + +_1 1. The Developers, by way of General Resolution or an election; + +_1 2. The Project Leader; + +_1 3. The Technical Committee and/or its Chairman; + +_1 4. The individual Developer working on a particular task; + +_1 5. Delegates appointed by the Project Leader for specific tasks; + +_1 6. The Project Secretary. + +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. /{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.}/ + +2~ 2.1 General rules + +_1 1. 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. + +_1 2. 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. + +_1 3. A person may leave the Project or resign from a particular post they hold, at any time, by stating so publicly. + +1~ 3 Individual Developers + +2~ 3.1 Powers + +An individual Developer may + +_1 1. make any technical or nontechnical decision with regard to their own work; + +_1 2. propose or sponsor draft General Resolutions; + +_1 3. propose themselves as a Project Leader candidate in elections; + +_1 4. vote on General Resolutions and in Leadership elections. + +2~ 3.2 Composition and appointment + +_1 1. 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. + +_1 2. The Project Leader's Delegate(s) may choose not to admit new Developers, or expel existing Developers. /{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.}/ + +2~ 3.3 Procedure + +Developers may make these decisions as they see fit. + +1~ 4. The Developers by way of General Resolution or election + +2~ 4.1 Powers + +Together, the Developers may: + +_1 1. Appoint or recall the Project Leader. + +_1 2. Amend this constitution, provided they agree with a 3:1 majority. + +_1 3. Override any decision by the Project Leader or a Delegate. + +_1 4. Override any decision by the Technical Committee, provided they agree with a 2:1 majority. + +_1 5. Issue, supersede and withdraw nontechnical policy documents and statements. + +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. + +They may also include position statements about issues of the day. + +_2 1. A Foundation Document is a document or statement regarded as critical to the Project's mission and purposes. + +_2 2. The Foundation Documents are the works entitled Debian Social Contract and Debian Free Software Guidelines. + +_2 3. 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. + +_1 6. Together with the Project Leader and SPI, make decisions about property held in trust for purposes related to Debian. (See §9.1.) + +2~ 4.2 Procedure + +_1 1. 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. + +_1 2. Delaying a decision by the Project Leader or their Delegate: + +_2 1. 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 s4.1(3). + +_2 2. 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). + +_2 3. 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. + +_2 4. 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. + +_2 5. If the Project Leader (or the Delegate) withdraws the original decision, the vote becomes moot, and is no longer conducted. + +_1 3. 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. + +_1 4. 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. + +_1 5. 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. + +_1 6. Votes are cast by email in a manner suitable to the Secretary. The Secretary determines for each poll whether voters can change their votes. + +_1 7. 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. + +1~ 5. Project Leader + +2~ 5.1 Powers + +The {Project Leader}http://www.debian.org/devel/leader may: + +_1 1. Appoint Delegates or delegate decisions to the Technical Committee. + +_1 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. + +_1 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. + +_1 2. Lend authority to other Developers. + +_1 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. + +_1 3. Make any decision which requires urgent action. + +_1 This does not apply to decisions which have only become gradually urgent through lack of relevant action, unless there is a fixed deadline. + +_1 4. Make any decision for whom noone else has responsibility. + +_1 5. Propose draft General Resolutions and amendments. + +_1 6. Together with the Technical Committee, appoint new members to the Committee. (See §6.2.) + +_1 7. Use a casting vote when Developers vote. + +_1 The Project Leader also has a normal vote in such ballots. + +_1 8. Vary the discussion period for Developers' votes (as above). + +_1 9. Lead discussions amongst Developers. + +_1 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. + +_1 10. Together with SPI, make decisions affecting property held in trust for purposes related to Debian. (See §9.1.) + +2~ 5.2 Appointment + +_1 1. The Project Leader is elected by the Developers. + +_1 2. The election begins nine weeks before the leadership post becomes vacant, or (if it is too late already) immediately. + +_1 3. For the following three weeks any Developer may nominate themselves as a candidate Project Leader. + +_1 4. 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. + +_1 5. 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. + +_1 6. 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. + +_1 7. 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 "None Of The Above". + +_1 8. The Project Leader serves for one year from their election. + +2~ 5.3 Procedure + +The Project Leader should attempt to make decisions which are consistent with the consensus of the opinions of the Developers. + +Where practical the Project Leader should informally solicit the views of the Developers. + +The Project Leader should avoid overemphasizing their own point of view when making decisions in their capacity as Leader. + +1~ 6. Technical committee + +2~ 6.1 Powers + +The {Technical Committee}http://www.debian.org/devel/tech-ctte may: + +_1 1. Decide on any matter of technical policy. + +_1 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).) + +_1 2. Decide any technical matter where Developers' jurisdictions overlap. + +_1 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. + +_1 3. Make a decision when asked to do so. + +_1 Any person or body may delegate a decision of their own to the Technical Committee, or seek advice from it. + +_1 4. Overrule a Developer (requires a 3:1 majority). + +_1 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. + +_1 5. Offer advice. + +_1 The Technical Committee may make formal announcements about its views on any matter. Individual members may of course make informal statements about their views and about the likely views of the committee. + +_1 6. Together with the Project Leader, appoint new members to itself or remove existing members. (See §6.2.) + +_1 7. Appoint the Chairman of the Technical Committee. + +_1 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. + +_1 8. The Chairman can stand in for the Leader, together with the Secretary + +_1 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. + +2~ 6.2 Composition + +_1 1. The Technical Committee consists of up to 8 Developers, and should usually have at least 4 members. + +_1 2. 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. + +_1 3. When there are 5 members or fewer the Technical Committee may appoint new member(s) until the number of members reaches 6. + +_1 4. 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. + +_1 5. If the Technical Committee and the Project Leader agree they may remove or replace an existing member of the Technical Committee. + +2~ 5.3 Procedure + +_1 1. The Technical Committee uses the Standard Resolution Procedure. + +_1 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. + +_1 2. Details regarding voting + +_1 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). + +_1 3. Public discussion and decision-making. + +_1 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. + +_1 4. Confidentiality of appointments. + +_1 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. + +_1 5. No detailed design work. + +_1 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. + +_1 The Technical Committee restricts itself to choosing from or adopting compromises between solutions and decisions which have been proposed and reasonably thoroughly discussed elsewhere. + +_1 /{Individual members of the technical committee may of course participate on their own behalf in any aspect of design and policy work.}/ + +_1 6. Technical Committee makes decisions only as last resort. + +_1 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. + +1~ 7. The Project Secretary + +2~ 7.1 Powers + +The {Secretary:}http://www.debian.org/devel/secretary + +_1 1. Takes votes amongst the Developers, and determines the number and identity of Developers, whenever this is required by the constitution. + +_1 2. Can stand in for the Leader, together with the Chairman of the Technical Committee. + +_1 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. + +_1 3. Adjudicates any disputes about interpretation of the constitution. + +_1 4. May delegate part or all of their authority to someone else, or withdraw such a delegation at any time. + +2~ 7.2 Appointment + +The Project Secretary is appointed by the Project Leader and the current Project Secretary. + +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. + +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. + +The Project Secretary's term of office is 1 year, at which point they or another Secretary must be (re)appointed. + +2~ 7.3 Procedure + +The Project Secretary should make decisions which are fair and reasonable, and preferably consistent with the consensus of the Developers. + +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. + +1~ 8. The Project Leader's Delegates + +2~ 8.1 Powers + +The Project Leader's Delegates: + +_1 1. have powers delegated to them by the Project Leader; + +_1 2. 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. This is to avoid concentration of power, particularly over membership as a Developer, in the hands of the Project Leader. + +2~ 8.2 Appointment + +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. + +2~ 8.3 Procedure + +Delegates may make decisions as they see fit, but should attempt to implement good technical decisions and/or follow consensus opinion. + +1~ 9. Software in the Public Interest + +{SPI}http://www.spi-inc.org/ and Debian are separate organisations who share some goals. Debian is grateful for the legal support framework offered by SPI. Debian's Developers are currently members of SPI by virtue of their status as Developers. + +2~ 9.1 Authority + +_1 1. 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. + +_1 2. 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. + +_1 3. 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. + +2~ 9.2 Management of property for purposes related to Debian + +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. + +SPI have made the following undertakings: + +_1 1. SPI will hold money, trademarks and other tangible and intangible property and manage other affairs for purposes related to Debian. + +_1 2. Such property will be accounted for separately and held in trust for those purposes, decided on by Debian and SPI according to this section. + +_1 3. 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. + +_1 4. SPI will consider using or disposing of property held in trust for Debian when asked to do so by the Project Leader. + +_1 5. 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. + +_1 6. 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. + +1~a A. Standard Resolution Procedure + +These rules apply to communal decision-making by committees and plebiscites, where stated above. + +2~a1 A.1. Proposal + +The formal procedure begins when a draft resolution is proposed and sponsored, as required. + +2~a1a A.1 Discussion and Amendment + +_1 1. 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. + +_1 2. A formal amendment may be accepted by the resolution's proposer, in which case the formal resolution draft is immediately changed to match. + +_1 3. 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. + +_1 4. 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).) + +_1 5. The proposer or 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. + +_1 6. 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. + +2~a2 A.2. Calling for a vote + +_1 1. 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. + +_1 2. The proposer or any sponsor of a resolution may call for a vote on that resolution and all related amendments. + +_1 3. 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). + +_1 4. 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. + +2~a3 A.3. Voting procedure + +_1 1. 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). + +_1 2. The default option must not have any supermajority requirements. Options which do not have an explicit supermajority requirement have a 1:1 majority requirement. + +_1 3. The votes are counted according to the rules in A.6. The default option is "Further Discussion", unless specified otherwise. + +_1 4. In cases of doubt the Project Secretary shall decide on matters of procedure. + +2~a4 A.4. Withdrawing resolutions or unaccepted amendments + +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. + +A sponsor of a resolution or amendment (unless it has been accepted) may withdraw. + +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. + +2~a5 A.5. Expiry + +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. + +The secretary may also include suggestions on how to proceed, if appropriate. + +2~a6 A.6. Vote Counting + +_1 1. 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. + +_1 2. 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. + +_1 3. Any (non-default) option which does not defeat the default option by its required majority ratio is dropped from consideration. + +_2 1. Given two options A and B, V(A,B) is the number of voters who prefer option A over option B. + +_2 2. 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). + +_2 3. If a supermajority of S:1 is required for A, its majority ratio is S; otherwise, its majority ratio is 1. + +_1 4. From the list of undropped options, we generate a list of pairwise defeats. + +_1 1. An option A defeats an option B, if V(A,B) is strictly greater than V(B,A). + +_1 5. From the list of [undropped] pairwise defeats, we generate a set of transitive defeats. + +_1 1. 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. + +_1 6. We construct the Schwartz set from the set of transitive defeats. + +_2 1. 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. + +_1 7. 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. + +_2 1. 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). + +_2 2. A weakest defeat is a defeat that has no other defeat weaker than it. There may be more than one such defeat. + +_1 8. 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. + +!_ Note: +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. + +/{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.}/ + +2~b B. Use of language and typography + +The present indicative ('is', for example) means that the statement is a rule in this constitution. 'May' or 'can' indicates that the person or body has discretion. 'Should' means that it would be considered a good thing if the sentence were obeyed, but it is not binding. 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. + +%% SiSU markup sample Notes: +% SiSU http://www.jus.uio.no/sisu +% SiSU markup for 0.16 and later: +% 0.20.4 header 0~links +% 0.22 may drop image dimensions (rmagick) +% 0.23 utf-8 ß +% 0.38 or later, may use alternative notation for headers, e.g. @title: (instead of 0~title) +% 0.38 document structure alternative markup, experimental (rad) A,B,C,1,2,3 maps to 1,2,3,4,5,6 +% Output: http://www.jus.uio.no/sisu/autonomy_markup0/sisu_manifest.html +% markup in this document is 0.38, (rad) experimental diff --git a/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2.sst b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2.sst new file mode 100644 index 00000000..e69d9eab --- /dev/null +++ b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2.sst @@ -0,0 +1,502 @@ +% SiSU 0.38 + +@title: Debian Constitution + +@subtitle: Constitution for the Debian Project (v1.2) [This Document has been Superseded by v1.3] + +@creator: Debian Project + +@type: information + +@subject: debian policy + +@date.created: 1998-12-03 + +@date.issued: 1998-12-03 + +@date.valid: 2003-10-29 + +@date.available: 2003-10-29 + +@date.modified: 2003-10-29 + +@date: 2003-10-29 + +@language.document: English + +@language.original: English + +@level: new=C; num_top=1 + +@skin: skin_debian + +@bold: Debian; DPL + +% @italics: + +@rights: http://www.debian.org/license Copyright © 1997-2006 Software in the Public Interest, Inc., P.O. Box 501248, Indianapolis, IN 46250-6248, United States, http://www.spi-inc.org/ <br>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 local copy http://www.debian.org/opl, the latest version is usually available at http://www.opencontent.org/ ). <br>"Debian" and the Debian Logo are trademarks of Software in the Public Interest, Inc. + +@links: {Authoritative Source Document}http://www.debian.org/devel/constitution +{SiSU version using default markup}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{SiSU version markup adjusted to correspond to original document}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{Debian Social Contract @ SiSU}http://www.jus.uio.no/sisu/debian_social_contract_v1.1/sisu_manifest.html +{About Debian}http://www.debian.org/intro/about +{News}http://www.debian.org/News/ +{Getting Debian}http://www.debian.org/distrib/ +{Support}http://www.debian.org/support +{Developer's Corner}http://www.debian.org/devel/ +{Sitemap}http://www.debian.org/sitemap +{Search}http://search.debian.org/ + +@prefix: This is taken from the authoritative source at http://www.debian.org/devel/constitution and is marked up and generated to check SiSU default settings, please note that the sub-numbering in using letters is not identical to the original.<br>Version 1.2 ratified on October 29th, 2003. Supersedes Version 1.1 http://www.debian.org/devel/constitution.1.1 ratified on June 21st, 2003, which itself supersedes Version 1.0 http://www.debian.org/devel/constitution.1.0 ratified on December 2nd, 1998.<br>Two different SiSU marked up versions are provided http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html uses simpler markup, the default numbering mode; http://www.jus.uio.no/sisu/debian_constitution_v1.2.adjusted/sisu_manifest.html uses more complicated numbering in the markup and is more true to the original + +@rcs: $Id: debian_constitution_v1.2.s3,v 1.7 2006/02/28 12:11:55 ralph Exp $ + +:A~ Debian Constitution + +:B~ Constitution for the Debian Project (v1.2) [This Document has been Superseded by v1.3] + +1~pre [Prefix]-# + +Version 1.2 ratified on October 29th, 2003. Supersedes {Version 1.1}http://www.debian.org/devel/constitution.1.1 ratified on June 21st, 2003, which itself supersedes {Version 1.0}http://www.debian.org/devel/constitution.1.0 ratified on December 2nd, 1998. + +1~ Introduction + +/{The Debian Project is an association of individuals who have made common cause to create a free operating system.}/ + +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. + +1~ Decision-making bodies and individuals + +Each decision in the Project is made by one or more of the following: + +# The Developers, by way of General Resolution or an election; + +# The Project Leader; + +# The Technical Committee and/or its Chairman; + +# The individual Developer working on a particular task; + +# Delegates appointed by the Project Leader for specific tasks; + +# The Project Secretary. + +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. /{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.}/ + +2~ General rules + +# 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. + +# 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. + +# A person may leave the Project or resign from a particular post they hold, at any time, by stating so publicly. + +1~ Individual Developers + +2~ Powers + +An individual Developer may + +# make any technical or nontechnical decision with regard to their own work; + +# propose or sponsor draft General Resolutions; + +# propose themselves as a Project Leader candidate in elections; + +# vote on General Resolutions and in Leadership elections. + +2~ Composition and appointment + +# 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. + +# The Project Leader's Delegate(s) may choose not to admit new Developers, or expel existing Developers. /{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.}/ + +2~ Procedure + +Developers may make these decisions as they see fit. + +1~ The Developers by way of General Resolution or election + +2~ Powers + +Together, the Developers may: + +# Appoint or recall the Project Leader. + +# Amend this constitution, provided they agree with a 3:1 majority. + +# Override any decision by the Project Leader or a Delegate. + +# Override any decision by the Technical Committee, provided they agree with a 2:1 majority. + +# Issue, supersede and withdraw nontechnical policy documents and statements. + +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. + +They may also include position statements about issues of the day. + +_# A Foundation Document is a document or statement regarded as critical to the Project's mission and purposes. + +_# The Foundation Documents are the works entitled Debian Social Contract and Debian Free Software Guidelines. + +_# 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. + +# Together with the Project Leader and SPI, make decisions about property held in trust for purposes related to Debian. (See §9.1.) + +2~ Procedure + +# 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. + +# Delaying a decision by the Project Leader or their Delegate: + +_# 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 s4.1(3). + +_# 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). + +_# 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. + +_# 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. + +_# If the Project Leader (or the Delegate) withdraws the original decision, the vote becomes moot, and is no longer conducted. + +# 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. + +# 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. + +# 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. + +# Votes are cast by email in a manner suitable to the Secretary. The Secretary determines for each poll whether voters can change their votes. + +# 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. + +1~ Project Leader + +2~ Powers + +The {Project Leader}http://www.debian.org/devel/leader may: + +# Appoint Delegates or delegate decisions to the Technical Committee. + +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. + +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. + +# Lend authority to other Developers. + +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. + +# Make any decision which requires urgent action. + +This does not apply to decisions which have only become gradually urgent through lack of relevant action, unless there is a fixed deadline. + +# Make any decision for whom noone else has responsibility. + +# Propose draft General Resolutions and amendments. + +# Together with the Technical Committee, appoint new members to the Committee. (See §6.2.) + +# Use a casting vote when Developers vote. + +The Project Leader also has a normal vote in such ballots. + +# Vary the discussion period for Developers' votes (as above). + +# Lead discussions amongst Developers. + +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. + +# Together with SPI, make decisions affecting property held in trust for purposes related to Debian. (See §9.1.) + +2~ Appointment + +# The Project Leader is elected by the Developers. + +# The election begins nine weeks before the leadership post becomes vacant, or (if it is too late already) immediately. + +# For the following three weeks any Developer may nominate themselves as a candidate Project Leader. + +# 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. + +# 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. + +# 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. + +# 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 "None Of The Above". + +# The Project Leader serves for one year from their election. + +2~ Procedure + +The Project Leader should attempt to make decisions which are consistent with the consensus of the opinions of the Developers. + +Where practical the Project Leader should informally solicit the views of the Developers. + +The Project Leader should avoid overemphasizing their own point of view when making decisions in their capacity as Leader. + +1~ Technical committee + +2~ Powers + +The {Technical Committee}http://www.debian.org/devel/tech-ctte may: + +# Decide on any matter of technical policy. + +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).) + +# Decide any technical matter where Developers' jurisdictions overlap. + +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. + +# Make a decision when asked to do so. + +Any person or body may delegate a decision of their own to the Technical Committee, or seek advice from it. + +# Overrule a Developer (requires a 3:1 majority). + +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. + +# Offer advice. + +The Technical Committee may make formal announcements about its views on any matter. Individual members may of course make informal statements about their views and about the likely views of the committee. + +# Together with the Project Leader, appoint new members to itself or remove existing members. (See §6.2.) + +# Appoint the Chairman of the Technical Committee. + +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. + +# The Chairman can stand in for the Leader, together with the Secretary + +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. + +2~ Composition + +# The Technical Committee consists of up to 8 Developers, and should usually have at least 4 members. + +# 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. + +# When there are 5 members or fewer the Technical Committee may appoint new member(s) until the number of members reaches 6. + +# 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. + +# If the Technical Committee and the Project Leader agree they may remove or replace an existing member of the Technical Committee. + +2~ Procedure + +# The Technical Committee uses the Standard Resolution Procedure. + +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. + +# Details regarding voting + +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). + +# Public discussion and decision-making. + +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. + +# Confidentiality of appointments. + +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. + +# No detailed design work. + +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. + +The Technical Committee restricts itself to choosing from or adopting compromises between solutions and decisions which have been proposed and reasonably thoroughly discussed elsewhere. + +/{Individual members of the technical committee may of course participate on their own behalf in any aspect of design and policy work.}/ + +# Technical Committee makes decisions only as last resort. + +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. + +1~ The Project Secretary + +2~ Powers + +The {Secretary:}http://www.debian.org/devel/secretary + +# Takes votes amongst the Developers, and determines the number and identity of Developers, whenever this is required by the constitution. + +# Can stand in for the Leader, together with the Chairman of the Technical Committee. + +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. + +# Adjudicates any disputes about interpretation of the constitution. + +# May delegate part or all of their authority to someone else, or withdraw such a delegation at any time. + +2~ Appointment + +The Project Secretary is appointed by the Project Leader and the current Project Secretary. + +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. + +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. + +The Project Secretary's term of office is 1 year, at which point they or another Secretary must be (re)appointed. + +2~ Procedure + +The Project Secretary should make decisions which are fair and reasonable, and preferably consistent with the consensus of the Developers. + +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. + +1~ The Project Leader's Delegates + +2~ Powers + +The Project Leader's Delegates: + +# have powers delegated to them by the Project Leader; + +# 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. This is to avoid concentration of power, particularly over membership as a Developer, in the hands of the Project Leader. + +2~ Appointment + +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. + +2~ Procedure + +Delegates may make decisions as they see fit, but should attempt to implement good technical decisions and/or follow consensus opinion. + +1~ Software in the Public Interest + +{SPI}http://www.spi-inc.org/ and Debian are separate organisations who share some goals. Debian is grateful for the legal support framework offered by SPI. Debian's Developers are currently members of SPI by virtue of their status as Developers. + +2~ Authority + +# 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. + +# 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. + +# 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. + +2~ Management of property for purposes related to Debian + +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. + +SPI have made the following undertakings: + +# SPI will hold money, trademarks and other tangible and intangible property and manage other affairs for purposes related to Debian. + +# Such property will be accounted for separately and held in trust for those purposes, decided on by Debian and SPI according to this section. + +# 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. + +# SPI will consider using or disposing of property held in trust for Debian when asked to do so by the Project Leader. + +# 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. + +# 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. + +1~a A. Standard Resolution Procedure + +These rules apply to communal decision-making by committees and plebiscites, where stated above. + +2~a1 A.1. Proposal + +The formal procedure begins when a draft resolution is proposed and sponsored, as required. + +2~a1a A.1 Discussion and Amendment + +# 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. + +# A formal amendment may be accepted by the resolution's proposer, in which case the formal resolution draft is immediately changed to match. + +# 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. + +# 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).) + +# The proposer or 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. + +# 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. + +2~a2 A.2. Calling for a vote + +# 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. + +# The proposer or any sponsor of a resolution may call for a vote on that resolution and all related amendments. + +# 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). + +# 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. + +2~a3 A.3. Voting procedure + +# 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). + +# The default option must not have any supermajority requirements. Options which do not have an explicit supermajority requirement have a 1:1 majority requirement. + +# The votes are counted according to the rules in A.6. The default option is "Further Discussion", unless specified otherwise. + +# In cases of doubt the Project Secretary shall decide on matters of procedure. + +2~a4 A.4. Withdrawing resolutions or unaccepted amendments + +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. + +A sponsor of a resolution or amendment (unless it has been accepted) may withdraw. + +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. + +2~a5 A.5. Expiry + +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. + +The secretary may also include suggestions on how to proceed, if appropriate. + +2~a6 A.6. Vote Counting + +# 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. + +# 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. + +# Any (non-default) option which does not defeat the default option by its required majority ratio is dropped from consideration. + +_# Given two options A and B, V(A,B) is the number of voters who prefer option A over option B. + +_# 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). + +_# If a supermajority of S:1 is required for A, its majority ratio is S; otherwise, its majority ratio is 1. + +# From the list of undropped options, we generate a list of pairwise defeats. + +_# An option A defeats an option B, if V(A,B) is strictly greater than V(B,A). + +# From the list of [undropped] pairwise defeats, we generate a set of transitive defeats. + +_# 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. + +# We construct the Schwartz set from the set of transitive defeats. + +_# 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. + +# 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. + +_# 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). + +_# A weakest defeat is a defeat that has no other defeat weaker than it. There may be more than one such defeat. + +# 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. + +/{Note}/: 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. + +/{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.}/ + +1~b B. Use of language and typography + +The present indicative ('is', for example) means that the statement is a rule in this constitution. 'May' or 'can' indicates that the person or body has discretion. 'Should' means that it would be considered a good thing if the sentence were obeyed, but it is not binding. 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. + +%% SiSU markup sample Notes: +% SiSU http://www.jus.uio.no/sisu +% SiSU markup for 0.16 and later: +% 0.20.4 header 0~links +% 0.22 may drop image dimensions (rmagick) +% 0.23 utf-8 ß +% 0.38 or later, may use alternative notation for headers, e.g. @title: (instead of 0~title) +% 0.38 document structure alternative markup, experimental (rad) A,B,C,1,2,3 maps to 1,2,3,4,5,6 +% Output: http://www.jus.uio.no/sisu/autonomy_markup0/sisu_manifest.html +% markup in this document is 0.38, (rad) experimental diff --git a/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2~da.sst b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2~da.sst new file mode 100644 index 00000000..c8abacb8 --- /dev/null +++ b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2~da.sst @@ -0,0 +1,504 @@ +% SiSU 0.38 + +@title: Debians vedtægter + +@subtitle: Debian-projektets vedtægter (v1.2) [This Document has been Superseded by v1.3] + +@creator: Debian Project + +@type: information + +@subject: debian policy + +@date.created: 1998-12-03 + +@date.issued: 1998-12-03 + +@date.valid: 2003-10-29 + +@date.available: 2003-10-29 + +@date.modified: 2003-10-29 + +@date: 2003-10-29 + +@language.document: Danish + +@language.original: English + +@level: new=C; num_top=1 + +@skin: skin_debian + +@bold: Debian; DPL + +% @italics: + +@rights: http://www.debian.org/license.da.html Copyright © 1997-2006 Software in the Public Interest, Inc., P.O. Box 501248, Indianapolis, IN 46250-6248, United States, http://www.spi-inc.org/ <br>Dette materiale må kun distribueres i henhold til vilkårene beskrevet i Open Publication License, udkast (draft) v1.0 eller senere (du kan læse vores lokale kopi http://www.debian.org/opl, den seneste version er normalt tilgængelig på http://www.opencontent.org/openpub/ ).<br>"Debian" og Debians logo http://www.debian.org/logos/ er varemærker tilhørende Software in the Public Interest, Inc.<br>Dette er en oversættelse af det originale engelsksprogede dokument http://www.debian.org/license.en.html. + +@links: {Authoritative Source Document}http://www.debian.org/devel/constitution +{SiSU version using default markup}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{SiSU version markup adjusted to correspond to original document}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{Debian Social Contract @ SiSU}http://www.jus.uio.no/sisu/debian_social_contract_v1.1/sisu_manifest.html +{About Debian}http://www.debian.org/intro/about +{News}http://www.debian.org/News/ +{Getting Debian}http://www.debian.org/distrib/ +{Support}http://www.debian.org/support +{Developer's Corner}http://www.debian.org/devel/ +{Sitemap}http://www.debian.org/sitemap +{Search}http://search.debian.org/ + +@prefix: This is taken from the authoritative source at http://www.debian.org/devel/constitution and is marked up and generated to check SiSU default settings, please note that the sub-numbering in using letters is not identical to the original.<br>Version 1.2 ratified on October 29th, 2003. Supersedes Version 1.1 http://www.debian.org/devel/constitution.1.1 ratified on June 21st, 2003, which itself supersedes Version 1.0 http://www.debian.org/devel/constitution.1.0 ratified on December 2nd, 1998.<br>Two different SiSU marked up versions are provided http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html uses simpler markup, the default numbering mode; http://www.jus.uio.no/sisu/debian_constitution_v1.2.adjusted/sisu_manifest.html uses more complicated numbering in the markup and is more true to the original + +@rcs: $Id: debian_constitution_v1.2~dk.s3,v 1.7 2006/02/28 12:11:55 ralph Exp $ + +:A~ Debians vedtægter + +:B~ Debian-projektets vedtægter (v1.2) [This Document has been Superseded by v1.3] + +1~pre [Prefix]-# + +Version 1.2 blev godkendt den 29. oktober 2003. Erstatter version 1.1 som blev godkendt den 21. juni 2003, der erstattede version 1.0 som blev godkendt den 2. december 1998. + +1~1 §1. Introduktion + +Debian-projektet er en sammenslutning af personer, som har det fælles mål at udvikle et frit tilgængeligt styresystem. + +Dette dokument beskriver organisationsstrukturen for formelle beslutninger i projektet. Det beskriver ikke projektets mål eller hvordan vi opfylder disse, og indeholder ingen retningslinier, bortset fra de retningslinier som direkte vedrører beslutningsprosessen. + +1~2 §2. Beslutningsdygtige organer og -personer + +Enhver beslutning i projektet er omfattet af en eller flere af følgende: + +# Udviklerne, via en fælles resolution eller et valg; + +# Projektlederen; + +# Den tekniske komité og/eller dennes formand; + +# Den individuelle udvikler som arbejder med en bestemt opgave; + +# Delegater udnævnt af projektlederen til at varetage særlige opgaver; + +# Projektsekretæren. + +Resten af dette dokument vil primært beskrive disse organers fuldmagter, deres sammensætning og udnævnelse, og procedurer for vedtagelser. En persons eller et organs fuldmagt kan i visse tilfælde blive genstand for gennemsyn af andre; i så fald vil det fremgå af afsnittet om det organ, der står for dette. I listen ovenfor er hver person eller hvert organ stort set anført før de personer eller organer de kan (hjælpe til med at) udnævne, og hvis beslutninger de kan ophæve - men ikke alle, der er anført tidligere, kan ophæve beslutninger fortaget af alle som er anført senere. + +2~2.1 §2.1. Generelle regler + +# Intet i disse vedtægter forpligter nogen til at arbejde for projeket. En person, der ikke vil udføre en opgave, som er blevet uddelegeret eller pålagt vedkommende, behøver at gøre det. Derimod kan man ikke aktivt modarbejde regler eller beslutninger, som er foretaget korrekt i henhold til reglerne. + +# En person kan bestride flere hverv, bortset fra at projektlederen, projektsekretæren og formanden for den tekniske komité skal være forskellige personer, og lederen kan ikke udnæve sig selv, som sin egen delegat. + +# En person kan til enhver tid forlade projektet eller fratræde et særskilt hverv vedkommende har, ved offentligt at erklære dette. + +1~3 §3. Individuelle udviklere + +2~3.1 §3.1. Fuldmagt + +En individuel udvikler kan + +# tage tekniske og ikke-tekniske beslutninger med hensyn til sit eget arbejde; + +# foreslå og støtte udkast til generelle resolutioner; + +# foreslå sig selv som kandidat til projektleder i valg; + +# stemme på generelle resolutioner og i ledervalg. + +2~3.2 §3.2. Sammensætning og udnævnelse + +# Udviklere er frivillige som er enige om at fremme projektets mål for så vidt som de deltager i det, og som vedligeholder pakke(r) for projektet eller gør andet arbejde, som projeketlederens delegater anser for værdifuldt. + +# Projektlederens delegater kan vælge ikke at optage nye udviklere, eller at ekskludere nuværende udviklere. Hvis udviklerne mener at delegaterne misbruger deres autoritet, kan de selvfølgelig ophæve en beslutning via en generel resolution - se §4.1(3) og §4.2. + +2~3.3 §3.3. Fremgangsmåder + +Udviklerne kan foretage disse beslutninger efter eget skøn. + +1~4 §4. Udviklerne via generel resolution eller et valg + +2~4.1 §4.1. Fuldmagt + +Udviklerne kan sammen: + +# Udnævne eller afsætte projektlederen. + +# Ændre disse vedtægter med et 3:1-flertal. + +# Ophæve enhver beslutning taget af projektlederen eller en delegat. + +# Ophæve enhver beslutning taget af den tekniske komité, såfremt de er enige med et 2:1-flertal. + +# Udgive, erstatte og tilbagetrække ikke-tekniske retningslinier og erklæringer. + +Dette inkluderer dokumenter som forklarer projektmål, dets forhold til andre organer indenfor fri software, samt ikke-tekniske vejledninger som de fri software-licensbetingelser, som Debians programmel skal leve op til. + +Det kan også være stillingtagen til aktuelle emner. + +_# Et grundlæggende dokument er et dokument eller en bekendtgørelse, der betragtes som kritisk for projekts arbejde og formål. + +_# De grundlæggende dokumenter er det arbejde som er udmundet i Debian sociale kontrake og Debians retningslinier for fri software. + +_# Et grundlæggende dokument kræver et 3:1-flertal for dets erstatning. Nye grundlæggende dokumenter udgives og eksisterende dokumenter trækkes tilbage ved at føje til listen over grundlæggende dokumenter i disse vedtægter. + +# Træffe beslutninger sammen med projektlederen og SPI om forvaltede ejendele til formål der har relation til Debian. (Se §9.1). + +2~4.1 §4.2. Fremgangsmåde + +# Udviklerne følger de generelle resolutionsprocedurer beskrevet nedenfor. En resolution eller ændring betragtes som introduceret, hvis den er foreslået af en hvilken som helst udvikler og mindst K andre udviklere støtter den, eller hvis den er foreslået af projektlederen eller den tekniske komité. + +# Udsættelse af en resolution foretaget af projektlederen eller dennes delegater: + +_# Hvis projektlederen, dennes delegater eller den tekniske komité har truffet en beslutning, kan udviklerne ophæve denne ved at vedtage en resolution derom, se §4.1(3). + +_# Hvis en sådan resolution støttes af mindst 2K udviklere eller hvis den er foreslået af den tekniske komité, vil resolutionen omgående tilsidesætte beslutningen (såfremt resolutionen selv siger dette). + +_# Hvis den oprindelige beslutning var at ændre en diskussionsperiode eller en stemmeperiode, eller hvis resolutionens formål er at ophæve en beslutning foretaget af den tekniske komité, behøver kun K udviklere at støtte resolutionen, for omgående at kunne tilsidesætte beslutningen. + +_# Hvis beslutningen er tilsidesat, holdes omgående en afstemning for at afgøre om beslutningen skal opretholdes indtil en fuldstændig afstemning om beslutningen kan holdes, eller om udførslen af den oprindelige beslutning skal udsættes indtil da. Der findes ikke et beslutningsdygtigt antal stemmer i denne omgående, proceduriske afstemning. + +_# Hvis projektlederen (eller dennes delegater) trækker den oprindelige beslutning tilbage, bliver det uaktuelt at holde afstemningen og den vil ikke blive afholdt. + +# Stemmer indsamles af projektsekretæren. Stemmerne og afstemningsresultatet offentliggøres ikke i stemmeperioden; efter afstemningen opremser projektsekretæren alle de afgivne stemmer, Afstemningsperioden er to uger, men projektlederen kan tilføje eller fjerne op til en uge. + +# Minimumstiden for diskussion er to uger, men projektlederen kan tilføje eller fjerne op til en uge. Projektlederen har den afgørende stemme. Det beslutningsdygtige antals stemmer er 3Q. + +# Forslag, støtte, ændringer, stemmeopråb og andre formelle handlinger foregår via erklæringer på en offentlig tilgængelig elektronisk postliste udvalgt af projektlederens delegat(er); alle udviklere har skriveadgang til den. + +# Stemmer afgives via e-mail på en måde der bestemmes af sekretæren. Sekretæren bestemmer for hver afstemning hvorvidt vælgerne kan ændre deres stemmer. + +# Q er halvdelen af kvadratroden af antallet af udviklere. K er den mindste af Q og 5. Q og K behøver ikke at være heltal, og de afrundes ikke. + +1~5 §5. Projektlederen + +2~5.1 §5.1. Fuldmagt + +Projektlederen kan: + +# Udnævne delegater eller uddelegere beslutninger til den tekniske komité. + +Lederen kan beskrive en opgave med løbende ansvar eller en særskilt beslutning. I begge tilfælde overføres denne til en anden udvikler eller til den tekniske komité. + +Efter en særskilt beslutning er blevet uddelegeret og afgjort, kan projektlederen ikke trække uddelegeringen tilbage. derimod kan en løbende uddelegerning til en bestemt opgave trækkes tilbage. + +# Give hjemmel til andre udviklere. + +Projektlederen kan udgive støtteerklæringer til andres synspunkter eller andre projektmedlemmer, uden at være blevet bedt om det. Disse støtteerklæringer er gyldige, hvis, og kun hvis, lederen ville have haft fuldmagt til at træffe den foreliggende beslutning. + +# Foretage beslutninger som kræver omgående handling. + +Dette gælder ikke beslutninger som gradvist er blevet påtrængende på grund af manglende, relevant handling, med mindre der er en fastsat frist. + +# Foretage beslutninger som ingen andre har ansvaret for. + +# Fremstille udkast til generelle resolutioner og ændringsforslag. + +# Sammen med den tekniske komité udpege nye medlemmer til komitéen. (Se §6.2.) + +# Afgive en afgørende stemme i udviklernes afstemninger. + +Projektlederen har også almindelig stemmeret i sådanne afstemninger. + +# Ændre diskussionsperioden for udviklernes afstemninger (som beskrevet ovenfor). + +# Lede diskussioner blandt udviklerne. + +Projektlederen bør prøve at deltage i diskussioner blandt udviklerne på en hjælpsom måde, som søger at bringe diskussionen på rette kurs mod sagens kerne. Projektlederen bør ikke bruge lederpositionen til at fremme sine egne personlige synspunkter. + +# Tage beslutninger sammen med SPI, der vedrører ejendele som administreres til formål der vedrører Debian. (Se §9.1.) + +2~5.2 §5.2. Udnævnelse + +# Projektlederen vælges af udviklerne. + +# Valget begynder ni uger før lederpositionen bliver ledig eller (hvis det ikke allerede er for sent) omgående. + +# I de følgende tre uger kan enhver udvikler nominere sig selv som projektlederkandidat. + +# I de efterfølgende tre uger kan der ikke nomineres flere kandidater; kandiaterne bør anvende dette tidsrum til deres valgkamp (for at gøre opmærksom på sig selv og sine synspunkter). Hvis der ikke er nogen kandidater efter nomineringsperioden er slut, bliver perioden udvidet med yderligere tre uger, om nødvendigt gentagne gange. + +# De næste tre uger er valgperioden, hvori udviklerene kan stemme. Afstemningen i ledervalg er hemmelig, selv efter afstemningen er afsluttet. + +# Valget vil være mellem de kandidater, der har nomineret sig selv og som ikke har trukket sig tilbage, samt Ingen af de nævnte ("None of the Above"). Hvis Ingen af de nævnte vinder valget, bliver denne procedure gentaget, om nødvendigt mange gange. + +# Beslutningen træffes ved hjælp af den metode, som er beskrevet i afsnit §A.6 i de generelle resolutionsprocedurer. Det beslutningsdygtige antal er det samme, som ved en generel resolution (§4.2), og standardvalget er Ingen af de nævnte. + +# Projektlederen vælges for et år ad gangen. + +2~5.3 §5.3. Fremgangsmåde + +Projektlederen bør prøve at træffe beslutninger som er i tråd med konsensus blandt udviklerne. + +Hvor det er praktisk bør projektlederen på en uformel måde bede om udviklernes synspunkter. + +Projektlederen bør undgå at lægge for megen vægt på sine egne synspunkter, når der træffes beslutninger i vedkommendes egenskab af leder. + +1~6 §6. Teknisk komité + +2~6.1 §6.1. Fuldmagt + +Den tekniske komité kan: + +# Træffe beslutninger om tekniske retningslinier. + +Deriblandt også indholdet af de tekniske retningslinier, udviklernes håndbogsmateriale, pakkeeksempler og hvordan ikke-eksperimentelle pakkeopbygningsværktøjer skal fungere. (I hvert tilfælde træffer den almindelige pakkevedligeholder af programmellet eller dokumentationen, de første beslutninger; se §6.3(5).) + +# Afgøre tekniske spørgsmål hvor udviklernes ansvarsområder overlapper. + +I tilfælde hvor udviklere skal implementere kompatible tekniske retningslinier eller holdninger (for eksempel hvis de ikke er enige om prioriteringerne ved uforenlige pakker, eller om ejerskab af et kommandonavn, eller om hvilken pakke der er ansvarlig for en fejl som begge pakkevedligeholdere er enige om er en fejl, eller om hvem der bør være vedligeholder af en pakke), kan den tekniske komité afgøre sagen. + +# Træffe en beslutning når den bliver bedt om at gøre dette. + +Enhver person og ethvert organ kan uddelegere en af sine egne beslutninger til den tekniske komité eller bede om råd fra den. + +# Tilsidesætte en udviklers beslutning (kræver et 3:1-flertal) + +Den tekniske komité kan bede en udvikler om at benytte en bestemt fremgangsmåde, selvom udvikleren ikke ønsker det; dette kræver et 3:1-flertal. For eksempel kan komitéen komme frem til at en klage fremsat i en fejlrapport er gyldig og at indsenderens foreslåede løsning bør iværksættes. + +# Give råd. + +Den tekniske komité kan give formelle erklæringer om sit syn på enhvert emne. Individuelle medlemmer kan selvfølgelig give uformelle erklæringer om deres synspunkter og om komitéens sandsynlige synspunkter. + +# Sammen med projektlederen udnævne nye medlemmer til sig selv eller fjerne nuværende medlemmer. (Se §6.2.) + +# Udnævne formanden for den tekniske komité. + +Komitéen vælger formand blandt sine medlemmer. Medlemmerne af komitéen nomineres automatisk; valget starter en uge før stillingen bliver ledig (eller omgående, hvis det allerede er for sent). Medlemmerne kan stemme via offentlig tilkendegivelse for hvilket som helst komitémedlem, også sig selv. Der er intet standardvalg. Valget afsluttes når alle medlemmerne har stemt eller stemmeperioden er afsluttet. Resultatet afgøres ved hjælp af den metode, som er angivet i §A.6 i de generelle resolutionsprocedurer. + +# Formanden kan vikariere for lederen, sammen med sekretæren + +Som beskrevet i §7.1(2), kan formanden for den tekniske komité og projektsekretæren i fællesskab vikariere for lederen, hvis der ikke er en leder. + +2~6.2 §6.2. Sammensætning + +# Den tekniske komité består af op til otte udviklere og bør normalt have mindst fire medlemmer. + +# Hvis det er mindre end otte medlemmer, kan den tekniske komité anbefale ny(e) medlem(mer) til projektlederen, som (på egen hånd) kan vælge at udnævne dem eller ej. + +# Hvis der er fem eller færre medlemmer, kan den tekniske komité udnævne ny(e) medlem(mer) indtil antallet af medlemmer når seks. + +# Når der har været fem eller færre medlemmer i mindst en uge, kan projektlederen udnævne nye medlem(mer) indtil antallet af medlemmer når seks, med mindst en uges mellemrum for hver udnævnelse. + +# Hvis den tekniske komité og projektlederen er enige kan de fjerne eller erstatte et nuværende medlem af den tekniske komité. + +2~6.3 §6.3. Fremgangsmåde + +# Den tekniske komité anvender den generelle resolutionsprocedure. + +Et udkast til en resolution eller ændring kan framsættes af ethvert medlem af den tekniske komité. Det er ingen minimumstid for diskussion; valgperioden varer i op til en uge eller indtil der ikke længere kan være nogen tvivl om resultatet. Medlemmerne kan ændre deres stemmer. Det beslutningsdygtige antal er to. + +# Detaljerede afstemningoplysninger + +Formanden har den afgørende stemme. Når den tekniske komité stemmer for at afgøre, om de skal tilsidesætte en afgørelse taget af en udvikler, der også er et medlem af komitéen, kan dette medlem ikke stemme (med mindre det er formanden, som i dette tilfælde kun kan benytte sin afgørende stemmeret). + +# Offentlig diskussion og afgørelser + +Diskussioner, udkast til resolutioner og ændringer og komitemedlemmernes stemmer offentliggøres på den tekniske komités offentlige diskussionsliste. Der er ikke en særskilt sekretær for komitéen. + +# Fortrolighed ved udnævnelser + +Den tekniske komité kan holde fortrolige diskussioner via privat e-mail eller en privat postliste, eller på andre måder diskutere udnævnelser til komitéen. Derimod skal stemmerne ved udnævnelser offentliggøres. + +# Ikke et detaljeret udviklingsarbejde + +Den tekniske komité giver sig ikke i kast med fremstilling af nye forslag og retningslinier. Sådant udviklingsarbejde bør foretages privat af personer eller grupper, og diskuteres i almindelige tekniske og udviklingsfora. + +Den tekniske komité begrænser sig selv til at vælge blandt, eller vælge et kompromis mellem, løsninger og afgørelser, der er blevet foreslået og er blevet drøftet tilpas meget andre steder. + +Medlemmer af den tekniske komité kan selvfølgelig deltage på egne vegne i alle aspekter af udviklings- og retningsliniearbejde. + +# Den teknisk komité træffer kun afgørelser som en sidste udvej + +Den tekniske komité træffer ikke en teknisk afgørelse før der uden held har været gjort forsøg på at løse problemet ved konsensus, med mindre den er blevet bedt om at træffe en afgørelse af personen eller organet, der normalt ville have haft ansvar for at gøre dette. + +1~7 §7. Projektsekretæren + +2~7.1 §7.1. Fuldmagt + +Sekretæren: + +# Indsamler stemmer fra udviklerne, finder ud af hvor mange udviklere der er og hvem de er, når dette kræves af vedtægterne. + +# Kan vikariere for lederen, i fællesskab med formanden for den tekniske komité. + +Hvis der ikke er en projektleder, kan formanden for den tekniske komité og projektsekretæren træffe afgørelser ved enighed, hvis de mener at det er vigtigt at gøre dette. + +# Dømmer i stridigheder om tolkning af vedtægterne. + +# Kan uddelegere dele af eller hele sin fuldmagt til andre, eller til enhver tid trække en sådan uddelegering tilbage. + +2~7.2 §7.2. Udnævnelse + +Projektsekretæren udnævnes af projektlederen og den forrige projektsekretær. + +Hvis projektlederen og den forrige projektsekretær ikke kan blive enige om en ny udnævnelse, skal de bede SPI's bestyrelse (se §9.1) om at udnævne en ny sekretær. + +Hvis der ikke er en projektsekretær eller den forrige sekretær ikke kan træffes og ikke har uddelegeret sin fuldmagt til en sådan beslutning, kan beslutningen træffes eller uddelegeres af formanden for den tekniske komité, som fungerende sekretær. + +Projektsekretæren er valgt for et år ad gangen, hvorefter en ny (gen)udnævnelse er nødvendig. + +2~7.3 §7.3. Fremgangsmåde + +Projektsekretæren bør træffe afgørelser som er retfærdige og rimelige, og helst i overensstemmelse med konsensus blandt udviklerne. + +Når projektsekretæren og formanden for den tekniske komité i fællesskab vikarierer for en projektleder som ikke kan træffes, bør de kun træffe beslutninger som er helt nødvendige og kun når det er i overensstemmelse med konsensus blandt udviklerne. + +1~8 §8. Projektlederens delegater + +2~8.1 §8.1. Fuldmagt + +Projektlederens delegater: + +# har fået uddelegeret en fuldmagt fra projektlederen; + +# kan træffe visse afgørelser som lederen ikke kan tage på egen hånd, deriblandt optagelse eller afvisning af udviklere, eller udnævne folk der ikke håndterer pakker, som udviklere. Dette er for at undgå en magtkoncentration hos projektlederen, særligt med hensyn til udviklermedlemskab. + +2~8.2 §8.2. Udnævnelse + +Delegaterne udnævnes af projektlederen, og lederen kan udskifte dem, som han finder det passende. Projektlederen kan ikke gøre udnævnelse betinget af at delegaten træffer bestemte afgørelser, lederen kan heller ikke ophævne en beslutning truffet af en delegat. + +2~8.3 §8.3. Fremgangsmåde + +Delegater kan til enhver tid træffe afgørelser, men bør prøve at opnå gode tekniske vilkår og/eller følge konsensus. + +1~9 §9. Software in the Public Interest ("Software i offentlighedens interesse") + +SPI og Debian er adskilte organisationer, der har nogle fælles mål. Debian er taknemlig for det juridiske støtteapparat, som SPI tilbyder. Debians udviklere er pt. medlemmer af SPI i kraft af deres hverv som udviklere. + +2~9.1 §9.1. Fuldmagt + +# SPI har ingen fuldmagt hvad angår Debians tekniske eller ikke-tekniske beslutninger, bortset fra at ingen beslutninger foretaget af Debian som vedrører ejendele der administreres af SPI, kan kræve at SPI handler udenfor sin juridiske fuldmagt, og Debians vedtægter kan af og til gøre SPI til en afgørende myndighed, som en sidste udvej. + +# Debian har ingen bestemmende kontrol over SPI, bortset fra anvendelse af visse ejendele som beskrevet nedenfor, selvom Debians udviklere kan få fuldmagt indenfor SPI efter SPI's regler. + +# Debians udviklere er ikke repræsentanter for, eller ansat af, SPI, eller af personer med fuldmagt i Debian-projektet. En person der handler som udvikler, gør dette som et individ på egne vegne. + +2~9.2 §9.2. Administration af ejendele til formål som vedrører Debian + +Da Debian ikke har fuldmagt til at forvalte penge eller ejendele, skal donationer til Debian-projektet gives til SPI, som håndterer den slags. + +SPI har påtaget sig følgende: + +# SPI vil forvalte penge, varemærker, andre konkrete ejendele og forretninger til formål som vedrører Debian. + +# Sådanne ejendele vil der blive holdt særskilt regnskab for og blive indsat i en fond med det formål, udvalgt af Debian og SPI i henhold til denne paragraf. + +# SPI vil ikke afhænde eller anvende ejendele, de administrerer for Debian, uden samtykke med Debian, som kan gives af projektlederen eller via en generel resolution blandt udviklerne. + +# SPI vil overveje anvendelse og/eller afhændelse af ejendele de administrerer for Debian, når de bliver bedt om det af projektlederen. + +# SPI vil anvende eller afhænde ejendele som administreres for Debian når de bliver bedt om at gøre dette, via en generel resolution blandt udviklerne, såfremt dette er foreneligt med SPI's juridiske fuldmagt. + +# SPI vil via elektronisk post til en af Debian-projektets postlister, gør opmærksom på når ejendele, der administreres for Debian, anvendes eller afhændes. + +1~a A. Generel resolutionsprocedure + +Disse regler gælder fælles beslutninger truffet af komitéer og ved afstemninger, som beskrevet ovenfor. + +2~a1 A.1. Forslag + +Den formelle procedure begynder når et udkast til en beslutning er foreslået og støttet, som krævet. + +2~a1a A.1. Diskussion og ændring + +# Efter forslaget er fremsat, kan resolutionen diskuteres. Ændringsforslag kan gøres formelle ved at fremsætte dem og skaffe støtter jævnfør kravene for nye resolutioner, eller direkte af forslagsstilleren af det oprindelige forslag. + +# Et formelt ændringsforslag kan accepteres af resolutionens forslagsstiller, hvorved det formelle resolutionsudkast omgående ændres. + +# Hvis et formelt ændringsforslag ikke accepteres, eller en af støtterne til resolutionen ikke er enig med forslagsstillerens accept af et formelt ændringsforslag, holdes en særskilt afstemning om dette. + +# Hvis andre ikke kan lide et ændringsforslag, som er accepteret af den oprindelige forslagsstiller, kan de foreslå en anden ændring for at fjerne den tidligere ændring (igen skal de leve op til kravene om forslagsstiller og støtte(r).) + +# Forslagsstilleren af en resolution kan foreslå revideringer af formuleringen af ændringensforslaget; disse træder i kraft hvis forslagsstilleren af ændringsforslaget er enig og ingen af støtterne protesterer. I så fald stemmes der om det reviderede ændringsforslag i stedet for det oprindelige. + +# Forslagsstilleren af en resolution kan foretage ændringer for at rette mindre fejl (for eksempel stavefejl eller selvmodsigelser) eller ændringer som ikke forandrer meningen, såfremt ingen protesterer indenfor 24 timer. I disse tilfælde starter minimumsdiskussionsperioden ikke igen. + +2~a2 A.2. Afstemning + +# Forslagsstilleren eller en støtte til en resolution eller et ændringsforslag kan bede om afstemning efter at minimumstiden for diskussion (hvis en sådan findes) er gået. + +# Foreslagsstilleren eller en støtte til en resolution kan bede om en afstemning vedrørende resolutionen eller alle beslægtede ændringsforslag. + +# Personen, der beder om en afstemning, fremsætter hvad vedkommende mener resolutionens og alle relevante ændringsforslags ordlyd skal være, og dermed hvilken udformning afstemningen skal have. Dog er det projektsekretæren som træffer den endelige beslutning - se §§ 7.1(1), 7.1(3), og A.3(4). + +# Den minimale diskussionsperiode regnes fra det tidspunkt, det sidste formelle ændringsforslag blev accepteret eller fra det tidspunkt hele resolutionen blev fremsat, hvis ingen ændringer er blevet foreslået og accepteret. + +2~a3 A.3. Afstemningsprocedure + +# Der stemmes på hver resolution og dennes beslægtede ændringsforslag i en enkelt afstemning, der indeholder en valgmulighed som er den originale resolution, hvert ændringsforslag, samt et standardvalg (hvor det er muligt). + +# Standardvalget må ikke have krav om et absolut flertal. Valgmuligheder som ikke eksplicit har krav om absolut flertal, har et 1:1-krav. + +# Stemmerne tælles jf. reglerne i A.6. Standardvalget er "Yderligere diskussion" ("Further Discussion"), med mindre andet er angivet. + +# I tvivlstilfælde skal projektsekretæren afgøre procedurespørgsmål. + +2~a4 A.4. Tilbagetrukne resolutioner og ikke-accepterede ændringsforslag + +Foreslagsstilleren af en resolution eller et ændringsforslag som ikke er accepteret, kan trække disse tilbage. I så fald kan andre foreslagsstillere overtage og holde resolutionen eller ændringsforslaget i live, dermed bliver den første person der gør dette, den nye foreslagsstiller og de andre bliver støtter, hvis de ikke allerede er det. + +En støtte til en resolution eller en ændring kan trække sig tilbage (med mindre resolutionen allerede er blevet accepteret). + +Hvis foreslagsstillers og/eller støttes tilbagetrækning betyder at resolutionen ikke har en foreslagsstiller eller der ikke er støtter nok, holdes der ikke en afstemning, med mindre dette udredes før resolutionen udløber. + +2~a5 A.5. Udløb + +Hvis en foreslået resolution ikke er blevet diskuteret, ændret, stemt på eller på anden måde taget hånd om i fire uger, kan sekretæren udsende en besked om, at den betragtes som tilbagetrukket. Hvis ingen af foreslagets støtter har indvendiger, trækkes foreslaget tilbage. + +Sekretæren kan også vedlægge forslag til hvordan man fortsætter, hvis det er relevat. + +2~a6 A.6. Stemmeoptælling + +# Hver vælgers stemme prioriterer valgmulighederne. Man behøver ikke at prioritere alle valgmulighederne. Prioriterede valgmuligheder betragtes som foretrukne fremfor valgmuligheder, der ikke er prioriteret. Vælgere kan give valgmuligheder samme prioritet. Valgmuligheder, der ikke er prioriteret, betragtes som ligestillede med hinanden. Nærmere oplysninger om hvordan stemmesedlerne skal udfyldes, vil være vedlagt valgindkaldelsen. + +# Hvis det beslutningsdygtige antal er R, vil enhver valgmulighed som ikke er standardvalget og som ikke modtager mindst R stemmer, der prioriterer den mulighed højere end standardvalget, vil ikke blivetaget i betragtning. + +# Alle (ikke-standard-) valgmuligheder, der ikke overgår standardvalgmuligheden med dens krævede flertalsgrad, tages ikke i betragtning. + +_# Med de to valgmuligheder A og B, er V(A,B) antallet af vælgere der foretrækker mulighed A fremfor mulighed B. + +_# Valgmulighed A overgår standardvalgmulighed D med flertalsgraden N, hvis V(A,D) er større end N * V(D,A). + +_# Hvis et absolut flertal på S:1 er krævet af A, er dennes flertalsgrad S; ellers er flertalsgraden 1. + +# Ud fra listen over valgmuligheder der tages i betragtning, genereres en liste over parvise nederlag. + +_# Valgmulighed A overgår mulighed B, hvis V(A,B) er større end V(B,A). + +# Ud fra en liste over parvise nederlag (som tages i betragtning), genereres en liste over transitive nederlag. + +_# Valgmulighed A overgår transitivt mulighed C, hvis A overgår C eller hvis der er en en mulighed B, hvor A overgår B OG B transitivt overgår C. + +# Ud fra sættet af transitive nederlag konstruere et Schwartz-sæt. + +_# Valgmulighed A er i Schwartz-sættet hvis, for alle B-muligheders vedkommende, A transitivt overgår B, eller B ikke overgår A transitivt. + +# Hvis der er nederlag mellem valgmuligheder i Schwartz-sættet, ses der bort fra de svageste af sådanne nederlag i listen over parvise nederlag, og man springer tilbage til trin 5. + +_# Nederlaget (A,X) er svagere end nederlaget (B,Y), hvis V(A,X) er mindre end V(B,Y). Hvis (A,X) desuden er svagere end (B,Y), hvis V(A,X) er lig med V(B,Y) og V(X,A) er større end V(Y,B). + +_# Et svageste nederlag, er et nederlag hvortil der ikke er et svagere nederlag. Der kan være mere end et af sådanne nederlag. + +# Hvis der ikke nogen nederlag i Schwartz-sættet, tages vinderen fra valgmulighederne i Schwartz-sættet. Hvis der kun er en af disse valgmuligheder, er den vinderen. Hvis der er flere valgmuligheder, afgørerer vælgeren med den afgørende stemme, hvem af disse valgmuligheder, der er vinderen. + +Bemærk: Valgmuligheder, som vælgerne prioriterer over standardvalgmuligheden, er muligheder de betragter som acceptable. Valgmuligheder, der prioriteres under standardvalgmuligheder, er muligheder, der betragtes som uacceptable. + +Når den generelle resolutionsprocedure anvendes, skal teksten som henviser til denne, fastsætte hvad der er tilstrækkeligt for at få et udkast til en resolution foreslået og/eller støttet, hvad minimumstiden for diskussion er, og hvad afstemningsperioden er. Den skal også fastsætte det eventuelle kvalificerede flertal og beslutningsdygtige antal, som skal anvendes. + +1~b B. Brug af sprog og typografi + +Nutid ("er", for eksempel) betyder at udtrykket er en regel i disse vedtægter. "Kan" og "skal" indikerer at personen eller organet kan anvende skøn. "Bør" betyder at det vil anses som en god ting om hvis sætningen følges, men den er ikke bindende. Tekst markeret som et citat, som dette, er baggrundsmateriale og udgør ikke en del af vedtægterne. Den kan kun anvendes til at hjælpe med at tolke teksten i tvivlstilfælde. + +Bemærk: Dette er en oversættelse af det originale engelsksprogede dokument. Brug altid originalen i diskussioner om vedtægterne, da denne dansksprogede udgave er oversætterens fortolkning, som desuden kan indeholde fejl og misforståelser. + +%% SiSU markup sample Notes: +% SiSU http://www.jus.uio.no/sisu +% SiSU markup for 0.16 and later: +% 0.20.4 header 0~links +% 0.22 may drop image dimensions (rmagick) +% 0.23 utf-8 ß +% 0.38 or later, may use alternative notation for headers, e.g. @title: (instead of 0~title) +% 0.38 document structure alternative markup, experimental (rad) A,B,C,1,2,3 maps to 1,2,3,4,5,6 +% Output: http://www.jus.uio.no/sisu/autonomy_markup0/sisu_manifest.html +% markup in this document is 0.38, (rad) experimental diff --git a/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2~de.sst b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2~de.sst new file mode 100644 index 00000000..70e1a523 --- /dev/null +++ b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2~de.sst @@ -0,0 +1,506 @@ +% SiSU 0.38 + +@title: Debian-Verfassung + +@subtitle: Verfassung für das Debian-Projekt (v1.2) [This Document has been Superseded by v1.3] + +@creator: Debian Project + +@type: information + +@subject: debian policy + +@date.created: 1998-12-03 + +@date.issued: 1998-12-03 + +@date.valid: 2003-10-29 + +@date.available: 2003-10-29 + +@date.modified: 2003-10-29 + +@date: 2003-10-29 + +@language.document: German + +@language.original: English + +@level: new=C; num_top=1 + +@skin: skin_debian + +@bold: Debian; DPL + +% @italics: + +@rights: http://www.debian.org/license.de.html Copyright © 1997-2006 Software in the Public Interest, Inc., P.O. Box 501248, Indianapolis, IN 46250-6248, United States, http://www.spi-inc.org/ <br>Dieses Material darf nur unter den Bestimmungen, die in der Open Publication License, Draft v1.0 oder später (Sie können unsere lokale Kopie lesen http://www.debian.org/opl, die neuste Version ist normalerweise unter unter http://www.opencontent.org/openpub/ verfügbar) festgehalten sind, weitergegeben werden.<br>"Debian" und das Debian-Logo http://www.debian.org/logos/ sind Warenzeichen von Software in the Public Interest, Inc.<br>Dies ist die deutsche Übersetzung von "Debian's license" http://www.debian.org/license.en.html. In Zweifelsfällen ist das englische Original maßgeblich. + +% @rights: http://www.debian.org/license Copyright © 1997-2006 Software in the Public Interest, Inc., P.O. Box 501248, Indianapolis, IN 46250-6248, United States, http://www.spi-inc.org/ <br>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 local copy http://www.debian.org/opl, the latest version is usually available at http://www.opencontent.org/ ). <br>"Debian" and the Debian Logo are trademarks of Software in the Public Interest, Inc. + +@links: {Authoritative Source Document}http://www.debian.org/devel/constitution +{SiSU version using default markup}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{SiSU version markup adjusted to correspond to original document}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{Debian Social Contract @ SiSU}http://www.jus.uio.no/sisu/debian_social_contract_v1.1/sisu_manifest.html +{About Debian}http://www.debian.org/intro/about +{News}http://www.debian.org/News/ +{Getting Debian}http://www.debian.org/distrib/ +{Support}http://www.debian.org/support +{Developer's Corner}http://www.debian.org/devel/ +{Sitemap}http://www.debian.org/sitemap +{Search}http://search.debian.org/ + +@prefix: This is taken from the authoritative source at http://www.debian.org/devel/constitution and is marked up and generated to check SiSU default settings, please note that the sub-numbering in using letters is not identical to the original.<br>Version 1.2 ratified on October 29th, 2003. Supersedes Version 1.1 http://www.debian.org/devel/constitution.1.1 ratified on June 21st, 2003, which itself supersedes Version 1.0 http://www.debian.org/devel/constitution.1.0 ratified on December 2nd, 1998.<br>Two different SiSU marked up versions are provided http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html uses simpler markup, the default numbering mode; http://www.jus.uio.no/sisu/debian_constitution_v1.2.adjusted/sisu_manifest.html uses more complicated numbering in the markup and is more true to the original + +@rcs: $Id: debian_constitution_v1.2~de.s3,v 1.7 2006/02/28 12:11:55 ralph Exp $ + +:A~ Debian-Verfassung + +:B~ Verfassung für das Debian-Projekt (v1.2) [This Document has been Superseded by v1.3] + +1~pre [Prefix]-# + +Dies ist die am 29. Oktober 2003 ratifizierte Version 1.2. Sie ersetzt die am 21. Juni 2003 ratifizierte Version 1.1, welche ihrerseits die am 2. Dezember 1998 ratifizierte Version 1.0 ersetzt. + +1~ Einleitung + +/{Das Debian-Projekt ist ein Verband von Einzelpersonen, die die Schaffung eines freien Betriebssystem zu ihrem gemeinsamen Anliegen gemacht haben.}/ + +Dieses Dokument beschreibt die Organisationsstruktur für formelle Entscheidungsfindung innerhalb des Projekts. Es beschreibt nicht die Ziele des Projekts oder wie es diese erreicht, und es enthält keine Richtlinien außer denen, die sich direkt auf den Prozess der Entscheidungsfindung beziehen. + +1~ Entscheidungsfindende Organe und Einzelpersonen + +Jede Entscheidung innerhalb des Projekts wird von einem oder mehreren der folgenden Organe und Einzelpersonen getroffen: + +# Den Entwicklern, durch einen Allgemeinen Beschluss oder eine Wahl. + +# Dem Projektleiter; + +# Dem Technischen Ausschuss und/oder seinem Vorsitzenden; + +# Dem an einer einzelnen Aufgabe arbeitenden Entwickler; + +# Vom Projektleiter für bestimmte Aufgaben ernannten Delegierten; + +# Dem Projekt-Schriftführer. + +Das meiste vom Rest dieses Dokuments beschreibt die Befugnisse dieser Organe, ihre Zusammensetzung und Ernennung und das Verfahren bei ihrer Entscheidungsfindung. Die Befugnisse einer Person oder eines Organs können der Überwachung und/oder Einschränkung durch Andere unterworfen sein; in diesem Fall gibt dies der Eintrag des überwachenden Organs oder der Person an. In der obigen Liste ist eine Person oder ein Organ in der Regel vor irgendwelchen Personen oder Organen aufgeführt, deren Entscheidungen sie aufheben können oder die sie ernennen (oder ihnen dabei helfen) – jedoch kann nicht jeder, der vorher aufgeführt wird, jeden, der nachher aufgeführt wird, überstimmen. + +2~ Allgemeine Vorschriften + +# Nichts in dieser Verfassung erlegt irgendjemandem die Verpflichtung auf, für das Projekt Arbeit zu verrichten. Eine Person, die eine an sie delegierte oder ihr zugewiesene Aufgabe nicht erledigen möchte, muss es nicht tun. Jedoch darf sie nicht diesen Vorschriften oder Entscheidungen, die nach diesen Vorschriften ordnungsgemäß getroffen wurden, aktiv entgegenwirken. + +# Eine Person kann verschiedene Ämter innehaben, mit der Ausnahme, dass sich der Projektleiter, der Projekt-Schriftführer und der Vorsitzende des Technischen Ausschusses unterscheiden müssen, und dass der Projektleiter sich nicht zu seinem eigenen Delegierten ernennen kann. + +# Eine Person kann das Projekt verlassen oder ein bestimmtes Amt zu jeder Zeit niederlegen, indem sie dies öffentlich erklärt. + +1~ Einzelne Entwickler + +2~ Befugnisse + +Ein einzelner Entwickler darf + +# jede technische oder nicht-technische Entscheidung hinsichtlich seiner eigenen Arbeit treffen; + +# einen Entwurf zu einem Allgemeinen Beschluss einbringen oder befürworten; + +# sich bei Wahlen selbst als Kandidat für das Amt des Projektleiters vorschlagen; + +# bei Allgemeinen Beschlüssen und bei Wahlen über die Leitung abstimmen. + +2~ Zusammensetzung und Ernennung + +# Entwickler sind Freiwillige, die sich darin einig sind, die Ziele des Projekts insofern zu fördern, als sie an ihm teilhaben, und die ein oder mehrere Pakete für das Projekt betreuen oder andere Arbeit verrichten, welche der oder die Delegierten des Projektleiters als lohnenswert erachten. + +# Der oder die Delegierten des Projektleiters können es vorziehen, keine neuen Entwickler aufzunehmen, oder vorhandene Entwickler auszuschließen. Wenn die Entwickler verspüren, dass die Delegierten ihre Autorität missbrauchen, können sie selbstverständlich die Entscheidung durch einen Allgemeinen Beschluss außer Kraft setzen - siehe §4.1(3), §4.2. + +2~ Verfahren + +Entwickler können diese Entscheidungen treffen, wie sie es für richtig halten. + +1~ Die Entwickler durch einen Allgemeinen Beschluss oder Wahl + +2~ Befugnisse + +Zusammen können die Entwickler + +# Den Projektleiter ernennen oder abberufen. + +# Diese Verfassung abändern, vorausgesetzt, sie stimmen dem mit einer 3:1-Mehrheit zu. + +# Jede vom Projektleiter oder einem Delegierten getroffene Entscheidung außer Kraft setzen. + +# Jede vom Technischen Ausschuss getroffene Entscheidung außer Kraft setzen, vorausgesetzt, sie stimmen dem mit einer 2:1-Mehrheit zu. + +# Nicht-technische schriftliche Richtlinien und Erklärungen herausgeben, ersetzen und zurückziehen. + +Diese beinhalten Dokumente, welche die Ziele des Projekts und seine Beziehung zu anderen Gebilden der Freien Software beschreiben, sowie nicht-technische Richtlinien wie die Lizenzbedingungen für Freie Software, die Debian-Software erfüllen muss. + +Sie können auch Positionserklärungen zu Tagesfragen hinzufügen. + +_# Ein Gründungsdokument ist ein Dokument oder eine Erklärung, die als entscheidend für den Auftrag und die Zwecke des Projekts betrachtet werden. + +_# Die Gründungsdokumente sind die Arbeiten mit dem Titel Debian-Gesellschaftsvertrag und Debian Richtlinien für freie Software. + +_# Ein Gründungsdokument benötigt eine 3:1-Mehrheit, um ersetzt zu werden. Durch Abändern der Liste der Gründungsdokumente in dieser Verfassung werden neue Gründungsdokumente herausgegeben und vorhandene zurückgezogen. + +# Zusammen mit dem Projektleiter und SPI Entscheidungen über mit Debian in Beziehung stehendes, treuhänderisch verwaltetes Eigentum treffen. (Siehe §9.1.) + +2~ Verfahren + +# Die Entwickler befolgen das Standard-Beschlussverfahren – siehe weiter unten. Einen Beschluss oder Abänderung wird eingebracht, indem sie von irgendeinem Entwickler beantragt und von mindestens K anderen Entwicklern befürwortet wird, oder wenn sie vom Projektleiter oder Technischen Ausschuss beantragt wird. + +# Aufschieben einer Entscheidung des Projektleiters oder seines Delegierten: + +_# Wenn der Projektleiter, sein Delegierter oder der Technische Ausschuss eine Entscheidung getroffen hat, können Entwickler diese überstimmen, indem sie dazu einen Beschluss verabschieden; siehe §4.1(3). + +_# Wenn ein solcher Beschluss von wenigstens 2K Entwicklern befürwortet oder vom Technischen Ausschuss beantragt wird, vertagt der Beschluss die Entscheidung unmittelbar (vorausgesetzt, dieser Beschluss selbst besagt dies). + +_# Falls die ursprüngliche Entscheidung darin bestand, eine Diskussions- oder Abstimmungsfrist zu ändern, oder wenn der Beschluss darin besteht, den Technischen Ausschuss zu überstimmen, dann brauchen nur K Entwickler den Beschluss zu befürworten, um die Entscheidung unmittelbar vertagen zu können. + +_# Falls die Entscheidung vertagt wird, wird eine sofortige Abstimmung abgehalten, um zu bestimmen, ob die Entscheidung solange bestehen bleibt, bis die vollständige Abstimmung über die Entscheidung durchgeführt wurde, oder ob die Erfüllung der ursprünglichen Entscheidung bis dahin verzögert wird. Es gibt bei dieser unmittelbaren verfahrensbezogenen Abstimmung kein Quorum. + +_# Falls der Projektleiter (oder der Delegierte) die ursprüngliche Entscheidung zurückzieht, so wird die Abstimmung gegenstandslos und wird nicht weiter durchgeführt. + +# Der Projekt-Schriftführer lässt abstimmen. Stimmen, Stimmensummen und Ergebnisse werden während der Abstimmungsfrist nicht offen gelegt; nach der Abstimmung listet der Projekt-Schriftführer alle abgegebenen Stimmen auf. Die Abstimmungsfrist beträgt zwei Wochen, kann aber durch den Projektleiter um bis zu eine Woche variiert werden. + +# Die Mindestfrist für Diskussionen beträgt zwei Wochen, kann aber durch den Projektleiter um bis zu eine Woche variiert werden. Die Stimme des Projektleiters gibt den Ausschlag. Es gibt ein Quorum von 3Q. + +# Anträge, Befürwortungen, Abänderungen, Aufrufe zur Abstimmung und andere formelle Handlungen werden auf einer für die Öffentlichkeit lesbaren Mailingliste bekanntgegeben, die von dem bzw. den Delegierten des Projekt-Leiters bestimmt wird; jeder Entwickler kann dort Beiträge abgeben. + +# Stimmen werden in einer für den Schriftführer geeigneten Weise durch E-Mail abgegeben. Der Schriftführer legt für jede Abstimmung fest, ob die Abstimmenden ihre Stimme ändern können. + +# Q ist die Hälfte der Quadratwurzel aus der Anzahl der gegenwärtigen Entwickler. K ist Q oder 5, je nachdem, welches davon kleiner ist. Q und K brauchen nicht ganze Zahlen sein und werden nicht gerundet. + +1~ Projektleiter + +2~ Befugnisse + +Der Projektleiter darf + +# Delegierte ernennen oder Entscheidungen an den Technischen Ausschuss delegieren. + +Der Leiter darf einen Bereich mit fortlaufender Verantwortung oder eine bestimmte Entscheidung festlegen und diese an einen anderen Entwickler oder den Technischen Ausschuss übergeben. + +Sobald eine bestimmte Entscheidung delegiert und getroffen wurde, darf der Projektleiter diese Delegierung nicht zurückziehen; jedoch darf er eine fortlaufende Delegierung eines bestimmten Verantwortungsbereichs zurückziehen. + +# Anderen Entwicklern Vollmacht erteilen. + +Der Projektleiter kann Erklärungen zur Unterstützung von Standpunkten oder von anderen Mitgliedern des Projekts abgeben, gebeten oder ungebeten; diese Erklärungen haben dann und nur dann Kraft, wenn der Projektleiter befugt wäre, die fragliche Entscheidung zu treffen. + +# Jede Entscheidung treffen, welche dringende Handlung erfordert. + +Dies gilt nicht für Entscheidungen, die nur durch einen Mangel an entsprechenden Maßnahmen allmählich dringend geworden sind, außer wenn es einen festen Stichtag gibt. + +# Jede Entscheidung treffen, für die niemand sonst Verantwortung trägt. + +# Entwürfe für Allgemeine Beschlüsse und Abänderungen einbringen. + +# Zusammen mit dem Technischen Ausschuss neue Mitglieder in den Ausschuss berufen. (Siehe §6.2.) + +# Sich einer ausschlaggebenden Stimme bedienen, wenn Entwickler abstimmen. + +Der Projektleiter hat auch eine normale Stimme bei solchen Abstimmungen. + +# Die Diskussionsfrist für Abstimmungen der Entwickler variieren (wie oben). + +# Diskussionen unter Entwicklern leiten. + +Der Projektleiter sollte versuchen, an Diskussionen unter den Entwicklern auf eine hilfreiche Weise teilzunehmen, die versucht, die Diskussion zu den vorhandenen Kernproblemen zu bringen. Der Projektleiter sollte nicht seine Leitungsposition benutzen, um seine eigenen persönlichen Ansichten zu befördern. + +# Zusammen mit SPI Entscheidungen treffen, die mit Debian in Beziehung stehendes, treuhänderisch verwaltetes Eigentum betreffen. (Siehe §9.1.) + +2~ Ernennung + +# Der Projektleiter wird von den Entwicklern gewählt. + +# Die Wahl beginnt neun Wochen, bevor das Amt der Leitung frei wird, oder (wenn es bereits zu spät ist) sofort. + +# In den darauf folgenden drei Wochen kann jeder Entwickler sich selbst als Kandidat für das Amt des Projektleiters nominieren. + +# Danach können für drei Wochen keine weiteren Kandidaten nominiert werden; Kandidaten sollten diese Zeit für die Wahlkampagne nutzen (um ihre Person und Positionen bekannt zu machen). Falls es am Ende der Nominierungsfrist keine Kandidaten gibt, so wird die Nominierung um weitere drei Wochen verlängert – falls nötig, wiederholt. + +# Die nächsten drei Wochen sind der Abstimmungszeitraum, in der Entwickler ihre Stimmen abgeben können. Stimmen bei Wahlen für das Amt des Projektleiters werden geheimgehalten, sogar nachdem die Abstimmung beendet ist. + +# Die Wahlmöglichkeiten auf dem Stimmzettel sind diejenigen Kandidaten, die sich selbst nominiert und die Kandidatur noch nicht zurückgezogen haben, und zusätzlich »Niemand von den Obigen«. Falls »Niemand von den Obigen« die Wahl gewinnt, so wird das Wahlverfahren wiederholt – viele Male, falls nötig. + +# Die Entscheidung wird nach der in §A.6 des Standard-Beschlussverfahrens bestimmten Methode getroffen. Das Quorum ist dasselbe wie für einen Allgemeinen Beschluss (§4.2), und die Vorgabe-Wahlmöglichkeit ist »Niemand von den Obigen«. + +# Der Projektleiter amtiert nach seiner Wahl ein Jahr lang. + +2~ Verfahren + +Der Projektleiter sollte versuchen, Entscheidungen zu treffen, die mit dem Meinungskonsens der Entwickler vereinbar sind. + +Sofern es praktikabel ist, sollte der Projektleiter sich informell um die Ansichten der Entwickler bemühen. + +Der Projektleiter sollte es vermeiden, seinen eigenen Standpunkt übermäßig zu betonen, wenn er in seiner Eigenschaft als Projektleiter Entscheidungen trifft. + +1~ Technischer Ausschuss + +2~ Befugnisse + +Der Technische Ausschuss darf + +# Über jede Angelegenheit entscheiden, die technische Grundsätze betrifft. + +Dies schließt die Inhalte der Handbücher für technische Richtlinien, Nachschlagematerial für Entwickler, Beispielpakete und das Verhalten nicht-experimenteller Paketbau-Werkzeuge ein. (In jedem dieser Fälle trifft jedoch der übliche Betreuer der entsprechenden Software oder Dokumentation anfänglich Entscheidungen; siehe §6.3.(5).) + +# Über jede technische Angelegenheit entscheiden, in der sich die Entscheidungsbefugnisse von Entwicklern überlappen. + +In Fällen, bei denen Entwickler technische Richtlinien oder Standpunkte erfüllen müssen, die miteinander vereinbar sind (zum Beispiel, wenn sie über die Priorität miteinander im Konflikt stehender Pakete oder über das Eigentum am Namen eines Befehls verschiedener Meinung sind; oder darüber, welches Paket für einen Fehler verantwortlich ist, bei dem beide Betreuer sich einig sind, dass er ein Fehler ist; oder darüber, wer der Betreuer eines Pakets sein sollte), kann der technische Ausschuss die Angelegenheit entscheiden. + +# Eine Entscheidung treffen, wenn er darum gebeten wird. + +Jede Person und jedes Organ kann eine eigene Entscheidung an den Technischen Ausschuss delegieren, oder von ihm Rat einholen. + +# Einen Entwickler überstimmen (benötigt eine 3:1-Mehrheit). + +Der Technische Ausschuss kann einen Entwickler darum bitten, einen bestimmten technischen Handlungsweg zu beschreiten, sogar wenn der Entwickler dies nicht wünscht; dazu wird eine 3:1-Mehrheit benötigt. Zum Beispiel kann der Ausschuss festlegen, dass eine Beanstandung, die vom Einsender eines Fehlerberichts erhoben wurde, gerechtfertigt ist, und dass die vom Einsender vorgeschlagene Lösung erfüllt werden sollte. + +# Rat anbieten. + +Der Technische Ausschuss kann seine Ansichten über jegliche Angelegenheit formell bekannt machen. Einzelne Mitglieder können natürlich informelle Erklärungen über ihre Ansichten und über die voraussichtlichen Ansichten des Ausschusses abgeben. + +# Zusammen mit dem Projektleiter neue Mitglieder in den Ausschuss berufen oder vorhandene Mitglieder abberufen. (Siehe §6.2.) + +# Den Vorsitzenden des Technischen Ausschusses ernennen. + +Der Vorsitzende wird vom Ausschuss aus seinen Mitgliedern gewählt. Alle Mitglieder des Ausschusses werden automatisch nominiert; der Ausschuss beginnt eine Woche vor dem Freiwerden des Amtes zu wählen (oder sofort, wenn es bereits zu spät ist). Die Mitglieder können durch öffentliche Akklamation (d.h. Zuruf) für jedes Mitglied des Ausschusses stimmen, inklusive ihrer selbst; es gibt keine Vorgabe-Wahlmöglichkeit. Die Abstimmung endet, wenn alle Mitglieder abgestimmt haben, oder wenn die Abstimmungsfrist abgelaufen ist. Das Ergebnis wird durch die in §A.6 des Standard-Beschlussverfahrens bestimmte Methode festgelegt. + +# Der Vorsitzende kann den Projektleiter zusammen mit dem Schriftführer vertreten. + +Wie in §7.1(2) detailliert beschrieben wird, können der Vorsitzende des Technischen Ausschusses und der Projekt-Schriftführer zusammen den Projektleiter vertreten, falls es keinen Projektleiter gibt. + +2~ Zusammensetzung + +# Der Technische Ausschuss besteht aus bis zu 8 Entwicklern und sollte für gewöhnlich mindestens 4 Mitglieder haben. + +# Wenn es weniger als 8 Mitglieder gibt, kann der Technische Ausschuss dem Projektleiter ein oder mehrere neue Mitglieder empfehlen, der seinerseits (im Einzelfall) entscheiden kann, ob er sie ernennt oder nicht. + +# Wenn es 5 oder weniger Mitglieder gibt, kann der Technische Ausschuss ein oder mehrere Mitglieder ernennen, bis die Anzahl der Mitglieder 6 erreicht. + +# Wenn es für mindestens eine Woche 5 oder weniger Mitglieder gegeben hat, kann der Projektleiter ein oder mehrere neue Mitglieder ernennen, bis die Anzahl der Mitglieder 6 erreicht – dies in Abständen von mindestens einer Woche pro Ernennung. + +# Falls der Technische Ausschuss und der Projektleiter sich einig sind, können sie ein im Technischen Ausschuss vorhandenes Mitglied entfernen oder ersetzen. + +2~ Verfahren + +# Der Technische Ausschuss bedient sich des Standard-Beschlussverfahrens. + +Ein Beschlussentwurf oder eine Abänderung kann von jedem Mitglied des Technischen Ausschusses vorgeschlagen werden. Es gibt keine Mindestfrist für Diskussionen; die Abstimmungsfrist dauert bis zu einer Woche, oder bis über den Ausgang kein Zweifel mehr besteht. Mitglieder können ihre Stimmen ändern. Das Quorum beträgt 2. + +# Einzelheiten, die die Abstimmung betreffen. + +Der Vorsitzende hat eine ausschlaggebende Stimme. Wenn der Technische Ausschuss darüber abstimmt, ob ein Entwickler, der ebenfalls Mitglied des Ausschusses ist, überstimmt werden soll, so darf dieser Entwickler nicht abstimmen (es sei denn, er ist der Vorsitzende – in diesem Fall kann er nur seine ausschlaggebende Stimme benutzen). + +# Öffentliche Diskussion und Entscheidungsfindung. + +Diskussion, Beschlussentwürfe und Abänderungen, sowie Stimmen von Mitgliedern des Ausschusses werden auf der öffentlichen Diskussionsliste des Technischen Ausschusses veröffentlicht. Es gibt keinen gesonderten Schriftführer für den Ausschuss. + +# Vertraulichkeit der Ernennungen. + +Der Technische Ausschuss kann vertrauliche Diskussionen durch private E-Mail, eine private Mailingliste oder andere Mittel abhalten, um Ernennungen in den Ausschuss zu diskutieren. Jedoch müssen Abstimmungen über Ernennungen öffentlich sein. + +# Keine Entwurfsarbeit in Einzelheiten. + +Der Technische Ausschuss nimmt nicht am Entwurf neuer Vorschläge oder Richtlinien teil. Solche Entwurfsarbeit sollte von Einzelpersonen für sich oder zusammen durchgeführt werden und in gewöhnlichen Foren für technische Richtlinien und Entwürfe diskutiert werden. + +Der Technische Ausschuss beschränkt sich darauf, Kompromisse zwischen Lösungen und Entscheidungen, welche anderswo vorgeschlagen und hinreichend gründlich diskutiert worden sind, auszuwählen oder aufzunehmen. + +Einzelne Mitglieder des Technischen Ausschusses können selbstverständlich in eigener Sache an jedem Aspekt der Arbeit an Entwürfen und Richtlinien teilhaben. + +# Der Technische Ausschuss fasst Beschlüsse nur als letzten Ausweg. + +Der Technische Ausschuss trifft keine technische Entscheidung, solange nicht Anstrengungen, diese durch einen Konsens zu entscheiden, unternommen wurden und fehlgeschlagen sind, außer wenn er von der Person oder dem Organ, das normalerweise dafür verantwortlich ist, darum gebeten wurde, eine Entscheidung zu treffen. + +1~ Der Projekt-Schriftführer + +2~ Befugnisse + +Der Schriftführer + +# Lässt unter den Entwicklern abstimmen und bestimmt die Anzahl und Person der Entwickler, wann immer dies die Verfassung erfordert. + +# Kann zusammen mit dem Vorsitzenden des Technischen Ausschusses an die Stelle des Projektleiters treten. + +Wenn es keinen Projektleiter gibt, können der Vorsitzende des Technischen Ausschusses und der Projekt-Schriftführer in gegenseitigem Einvernehmen Entscheidungen treffen, wenn sie dies als unumgänglich betrachten. + +# Über jegliche Streitigkeit urteilen, die die Auslegung der Verfassung betrifft. + +# Kann seine Befugnisse teilweise oder vollständig an jemand anderen übertragen oder eine solche Delegierung zu jeder Zeit zurücknehmen. + +2~ Ernennung + +Der Projekt-Schriftführer wird vom Projektleiter und dem gegenwärtigen Projekt-Schriftführer ernannt. + +Wenn der Projektleiter und der gegenwärtige Projekt-Schriftführer sich nicht auf eine neue Ernennung einigen können, müssen sie den Vorstand von SPI (siehe §9.1.) darum bitten, einen Schriftführer zu ernennen. + +Wenn es keinen Projekt-Schriftführer gibt, oder der gegenwärtige Projekt-Schriftführer nicht erreichbar ist und seine Vollmacht über eine Entscheidung nicht abgegeben hat, kann der Vorsitzende des Technischen Ausschusses als stellvertretender Schriftführer die Entscheidung treffen oder delegieren. + +Die Amtszeit des Projekt-Schriftführers beträgt 1 Jahr, nach dessen Ablauf dieser oder ein anderer Schriftführer (wieder-)ernannt werden muss. + +2~ Verfahren + +Der Projekt-Schriftführer sollte gerechte und vernünftige Entscheidungen treffen, die vorzugsweise mit dem Konsens der Entwickler vereinbar sind. + +Wenn der Vorsitzende des Technischen Ausschusses und der Projekt-Schriftführer zusammen stellvertretend für einen abwesenden Projektleiter handeln, sollten sie nur wenn absolut notwendig Entscheidungen treffen, und nur, wenn diese vereinbar mit dem Konsens der Entwickler sind. + +1~ Die Delegierten des Projektleiters + +2~ Befugnisse + +Die Delegierten des Projektleiters + +# haben vom Projektleiter an sie delegierte Befugnisse; + +# dürfen gewisse Entscheidungen treffen, die der Leiter nicht auf direkte Weise treffen darf. Dazu gehört, Entwickler anzuerkennen oder zu verweisen, oder Personen zu Entwicklern zu bestimmen, die keine Pakete betreuen. Dies dient dazu, eine Konzentration von Macht, besonders eine über Mitgliedschaft von Entwicklern, in den Händen des Projektleiters zu verhindern. + +2~ Ernennung + +Die Delegierten werden durch den Projektleiter ernannt und können vom Projektleiter nach seinem Ermessen ersetzt werden. Der Projektleiter kann weder die Position des Delegierten von bestimmten Entscheidungen des Delegierten abhängig machen, noch kann er sich über eine Entscheidung hinwegsetzen, die einmal von einem Delegierten getroffen wurde. + +2~ Verfahren + +Delegierte können Entscheidungen treffen, wie sie es für richtig halten, jedoch sollten sie versuchen, gute technische Entscheidungen zu vollziehen und/oder dem Meinungskonsens zu folgen. + +1~ Software in the Public Interest (»Software im öffentlichen Interesse«) + +SPI und Debian sind getrennte Organisationen, welche einige Ziele miteinander teilen. Debian ist dankbar für die rechtliche Unterstützung, die SPI anbietet. Die Entwickler von Debian sind gegenwärtig Mitglieder von SPI auf Grund ihres Status als Entwickler. + +2~ Befugnis + +# SPI hat keine Befugnis, die Debians technische oder nicht-technische Entscheidungen betrifft, mit den Ausnahmen, dass keine Entscheidung durch Debian in Hinsicht auf irgendwelches von SPI verwaltetes Eigentum erfordern darf, dass SPI außerhalb seiner rechtlichen Befugnis handelt, und dass Debians Verfassung SPI gelegentlich als entscheidendes Organ letzter Instanz verwenden darf. + +# Debian beansprucht keine Befugnis über SPI außer der über die Verwendung gewissen Eigentums von SPI, wie weiter unten beschrieben wird. Dennoch können den Debian-Entwicklern innerhalb von SPI nach den Vorschriften von SPI Befugnisse erteilt werden. + +# Debian-Entwickler sind keine Vertreter oder Angestellte von SPI oder voneinander oder von innerhalb des Debian-Projekts mit Befugnis versehenen Personen. Eine Person, die als Entwickler handelt, tut dies als Einzelperson, im eigenen Namen. + +2~ Verwaltung von Eigentum für Zwecke, die mit Debian in Beziehung stehen + +Da Debian keine Befugnis hat, Geld oder Eigentum zu besitzen, müssen jegliche Spenden für das Debian-Projekt an SPI gemacht werden, das solche Angelegenheiten handhabt. + +SPI hat folgende Zusicherungen gemacht: + +# SPI besitzt für mit Debian in Beziehung stehende Zwecke Geld, Warenzeichen und anderes materielle und immaterielle Eigentum und handhabt andere Angelegenheiten. + +# Solches Eigentum wird für diese Zwecke, über die Debian und SPI entsprechend dieses Abschnitts entscheiden, treuhänderisch mit separater Rechenschaft verwaltet. + +# SPI wird kein für Debian treuhänderisch verwaltetes Eigentum veräußern oder verwenden, ohne dass eine Genehmigung durch Debian vorliegt. Diese kann vom Projektleiter oder durch Allgemeine Beschlüsse der Entwickler erteilt werden. + +# SPI wird in Betracht ziehen, treuhänderisch verwaltetes Eigentum zu verwenden oder zu veräußern, wenn es durch den Projektleiter darum gebeten wird. + +# SPI wird für Debian treuhänderisch verwaltetes Eigentum verwenden oder veräußern, wenn es durch einen Allgemeinen Beschluss der Entwickler darum gebeten wird, vorausgesetzt, dass dies mit der rechtlichen Befugnis von SPI verträglich ist. + +# SPI wird die Entwickler durch E-Mail auf einer Mailingliste des Debian-Projekts benachrichtigen, wenn es für Debian treuhänderisch verwaltetes Eigentum verwendet oder veräußert. + +1~a A. Standard-Beschlussverfahren + +Diese Vorschriften betreffen gemeinschaftliche Entscheidungsfindung durch Ausschüsse sowie direkte Abstimmungen, wie oben angegeben. + +2~a1 A.1. Beantragung + +Das formelle Verfahren beginnt, wenn ein Beschlussentwurf beantragt und befürwortet wird, je nach Bedarf. + +2~a1a A.1. Diskussion und Abänderung + +# Nach der Beantragung kann der Beschluss diskutiert werden. Abänderungen können formell gemacht werden, indem sie entsprechend den Anforderungen an einen neuen Beschluss beantragt und befürwortet werden, oder auf direktem Wege durch den Antragsteller des ursprünglichen Beschlusses. + +# Eine formelle Abänderung kann durch den Antragsteller des Beschlusses angenommen werden. In diesem Fall wird der formelle Beschlussentwurf unmittelbar mit der Abänderung in Übereinstimmung gebracht. + +# Wenn eine formelle Abänderung nicht angenommen wird, oder einer der Befürworter des Beschlusses nicht mit der Annahme durch den Antragsteller einer formellen Abänderung einverstanden ist, bleibt die Abänderung eine Abänderung und es wird über sie abgestimmt. + +# Wenn eine vom ursprünglichen Antragsteller angenommene Abänderung nicht nach dem Geschmack Anderer ist, können diese eine weitere Abänderung einbringen, um die frühere Veränderung umzukehren (wieder müssen sie dann Antragsteller und Befürworter gemäß der Anforderungen sein). + +# Der Antragsteller eines Beschlusses kann Veränderungen an der Formulierung von Abänderungen vorschlagen; diese werden wirksam, wenn der Antragsteller der Abänderung damit einverstanden ist und keiner der Befürworter dagegen ist. In diesem Fall wird anstelle der ursprünglichen über die veränderten Abänderungen abgestimmt. + +# Der Antragsteller eines Beschlusses kann Veränderungen vornehmen, um unbedeutende Fehler (zum Beispiel Schreibfehler oder Ungereimtheiten) zu berichtigen, oder Veränderungen vornehmen, die nicht den Sinn ändern, vorausgesetzt niemand erhebt innerhalb von 24 Stunden Einwände. In diesem Fall beginnt die Mindestfrist für Diskussionen nicht von vorn. + +2~a2 A.2. Aufruf zur Abstimmung + +# Der Antragsteller oder ein Befürworter eines Antrages oder einer Abänderung kann zur Abstimmung aufrufen, vorausgesetzt, dass die Mindestfrist für Diskussionen (falls vorhanden) abgelaufen ist. + +# Der Antragsteller und jeder Befürworter eines Beschlusses können zu einer Abstimmung über diesen Beschluss und alle damit zusammenhängenden Abänderungen aufrufen. + +# Die Person, welche zu einer Abstimmung aufruft, gibt bekannt, welches ihrer Ansicht nach die Formulierung des Beschlusses und relevanter Abänderungen sind, und folglich, welche Form der Stimmzettel annehmen sollte. Dennoch liegt die endgültige Entscheidung über die Form des/der Stimmzettel beim Schriftführer – siehe §§7.1(1), 7.1(3) und A.3(4). + +# Die Mindestfrist für Diskussionen zählt ab dem Zeitpunkt, zu dem die letzte formelle Abänderung angenommen wurde, oder ab dem Zeitpunkt, zu dem der ganze Beschluss vorgeschlagen wurde, falls keine Abänderungen vorgeschlagen und angenommen wurden. + +2~a3 A.3. Wahlverfahren + +# Über jeden Beschluss und die damit zusammenhängenden Abänderungen wird auf einem einzigen Wahlzettel abgestimmt, der jeweils eine Wahlmöglichkeit für den ursprünglichen Beschluss, jede Abänderung und die Vorgabe-Wahlmöglichkeit (wo anwendbar) enthält. + +# Die Vorgabe-Wahlmöglichkeit darf keine Supermajorität erfordern. Wahlmöglichkeiten, die nicht explizit eine Supermajorität erfordern, erfordern eine 1:1-Mehrheit. + +# Die Stimmen werden nach den Vorschriften in §A.6. gezählt. Die Vorgabe-Wahlmöglichkeit heißt »Weitere Diskussion«, wenn nicht eine andere bestimmt wurde. + +# In Zweifelsfällen entscheidet der Projekt-Schriftführer über Angelegenheiten des Verfahrens. + +2~a4 A.4. Zurückziehen von Beschlüssen oder nicht angenommenen Abänderungen + +Der Antragsteller eines Beschlusses oder einer nicht angenommenen Abänderung kann diese zurückziehen. In diesem Fall können neue Antragsteller hervortreten, um sie am Leben zu halten; dann wiederum wird die erste Person, die dies tut, der neue Antragsteller, und alle anderen werden Befürworter, wenn sie dies nicht bereits sind. + +Ein Befürworter eines Beschlusses oder einer Abänderung (es sei denn, sie wurde angenommen) kann seine Befürwortung zurückziehen. + +Wenn die Zurückziehung durch den Antragsteller und/oder die Befürworter bedeutet, dass der Beschluss keinen Antragsteller oder nicht genug Befürworter hat, wird über sie nicht abgestimmt, es sei denn, dies wird berichtigt, bevor der Beschluss verfällt. + +2~a5 A.5. Verfall + +Wenn innerhalb von 4 Wochen ein vorgeschlagener Beschluss nicht diskutiert, nicht abgeändert, darüber abgestimmt oder auf andere Weise behandelt wurde, kann der Schriftführer eine Erklärung abgeben, dass man dabei ist, die Angelegenheit zurückzuziehen. Wenn keiner der Befürworter der Anträge innerhalb einer Woche Einwände erhebt, wird die Angelegenheit zurückgezogen. + +Der Schriftführer kann seiner Erklärung, falls angebracht, auch Vorschläge beifügen, wie man weiter vorgehen soll. + +2~a6 A.6. Stimmenzählung + +# Der Stimmzettel jedes Abstimmenden rangiert die Wahlmöglichkeiten (d.h.: ordnet ihnen einen Rang zu), über die abgestimmt wird. Nicht alle Wahlmöglichkeiten müssen rangiert werden. Rangierte Wahlmöglichkeiten werden als bevorzugt gegenüber allen nicht rangierten Wahlmöglichkeiten betrachtet. Die Abstimmenden können Wahlmöglichkeiten gleichrangig rangieren. Nicht rangierte Wahlmöglichkeiten werden als einander gleichrangig betrachtet. Einzelheiten darüber, wie Stimmzettel ausgefüllt werden können, werden mit in den »Aufruf zur Abstimmung« aufgenommen. + +# Falls der Wahlzettel ein Quorum R fordert, werden alle Wahlmöglichkeiten (außer der Vorgabe-Wahlmöglichkeit), die nicht mindestens R Stimmen erhalten, die diese Wahlmöglichkeit gegenüber der Vorgabe-Wahlmöglichkeit höher rangieren, fallen gelassen. + +# Jede (nicht-Vorgabe-) Wahlmöglichkeit, die die Vorgabe-Wahlmöglichkeit nicht mit ihrem benötigten Mehrheitsverhältnis überstimmt, wird fallengelassen. + +_# Sind zwei Wahlmöglichkeiten A und B gegeben, so ist V(A,B) die Anzahl der Abstimmenden, die Wahlmöglichkeit A gegenüber Wahlmöglichkeit B bevorzugen. + +_# Eine Wahlmöglichkeit A besiegt die Vorgabe-Wahlmöglichkeit D mit einem Mehrheitsverhältnis N, falls V(A,D) echt größer als N * V(D,A) ist. + +_# Wenn eine Supermajorität von S:1 für A benötigt wird, beträgt ihr Mehrheitsverhältnis S; im anderen Fall ist ihr Mehrheitsverhältnis 1. + +# Aus der Liste von nicht fallengelassenen Wahlmöglichkeiten erzeugen wir eine Liste von paarweisen Besiegungen. + +_# Eine Wahlmöglichkeit A besiegt eine Wahlmöglichkeit B, falls V(A,B) echt größer als V(B,A) ist. + +# Aus der Liste der paarweisen Besiegungen erzeugen wir eine Liste von transitiven Besiegungen. + +_# Eine Wahlmöglichkeit A besiegt eine Wahlmöglichkeit C transitiv, falls A C besiegt oder es eine andere Wahlmöglichkeit B gibt, so dass A B besiegt UND B transitiv C besiegt. + +# Wir konstruieren die Schwartzsche Menge aus der Menge der transitiven Besiegungen. + +_# Eine Wahlmöglichkeit A ist in der Schwartzschen Menge, falls für alle Wahlmöglichkeiten B entweder A transitiv B besiegt, oder B nicht transitiv A besiegt. + +# Wenn es Besiegungen zwischen Wahlmöglichkeiten gibt, die in der Schwartzschen Menge liegen, so lassen wir die schwächste solcher Besiegungen aus der Liste der paarweisen Besiegungen fallen und kehren zu Schritt 5 zurück. + +_# Eine Besiegung (A,X) ist schwächer als eine Besiegung (B,Y) falls V(A,X) kleiner als V(B,Y) ist. Außerdem ist (A,X) schwächer als (B,Y) falls V(A,X) gleich V(B,Y) ist, und V(X,A) größer als V(Y,B) ist. + +_# Eine schwächste Besiegung ist eine Besiegung, die keine andere schwächere Besiegung besitzt. Es kann mehr als eine solche Besiegung geben. + +# Falls es keine Besiegungen in der Schwartzschen Menge gibt, wird der Sieger aus den Wahlmöglichkeiten in der Schwartzschen Menge ausgewählt. Falls es nur eine solche Wahlmöglichkeit gibt, ist sie der Sieger. Falls es mehrere Wahlmöglichkeiten gibt, bestimmt der Stimmberechtigte mit der ausschlaggebenden Stimme, welche der Wahlmöglichkeiten siegt. + +Anmerkung: Wahlmöglichkeiten, welche die Abstimmenden über die Vorgabe-Wahlmöglichkeit rangieren, sind Wahlmöglichkeiten, die sie annehmbar finden. Unter die Vorgabe-Wahlmöglichkeit rangierte Wahlmöglichkeiten sind Wahlmöglichkeiten, die sie nicht annehmbar finden. + +Wenn das Standard-Beschlussverfahren benutzt werden soll, muss der darauf bezugnehmende Text bestimmen, was ausreicht, um einen Beschlussentwurf einzubringen und/oder zu befürworten, wie lange die Mindestfrist für Diskussionen dauert, und wie lange die Abstimmungsfrist dauert. Er muss auch jegliche Supermajorität und/oder das Quorum (und Vorgabe-Wahlmöglichkeit) bestimmen, die zu verwenden sind. + +1~b B. Sprachgebrauch und Typographie + +Der Präsens Indikativ (zum Beispiel »ist«) bedeutet, dass die Aussage eine Vorschrift in dieser Verfassung ist. »Darf« oder »kann« zeigt an, dass es im Ermessen der Person oder des Organs liegt. »Sollte« bedeutet, dass es als gute Sache betrachtet würde, wenn der Satz befolgt würde, aber er ist nicht bindend. Als Zitat markierter Text, so wie dieser, stellt nur Beweggründe dar, und bildet keinen Teil der Verfassung. Er darf nur dazu benutzt werden, um in Zweifelsfällen bei der Interpretation zu helfen. + +Anmerkung des Übersetzers: Obwohl diese Übersetzung mit Sorgfalt erstellt wurde, ist nur der englische Originaltext dieser Verfassung verbindlich. + +%% SiSU markup sample Notes: +% SiSU http://www.jus.uio.no/sisu +% SiSU markup for 0.16 and later: +% 0.20.4 header 0~links +% 0.22 may drop image dimensions (rmagick) +% 0.23 utf-8 ß +% 0.38 or later, may use alternative notation for headers, e.g. @title: (instead of 0~title) +% 0.38 document structure alternative markup, experimental (rad) A,B,C,1,2,3 maps to 1,2,3,4,5,6 +% Output: http://www.jus.uio.no/sisu/autonomy_markup0/sisu_manifest.html +% markup in this document is 0.38, (rad) experimental diff --git a/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2~es.sst b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2~es.sst new file mode 100644 index 00000000..94f6325d --- /dev/null +++ b/debian/data/doc/sisu/v1/sisu_markup_samples/samples/debian_constitution_v1.2~es.sst @@ -0,0 +1,518 @@ +% SiSU 0.38 + +@title: Constitución de Debian + +@subtitle: Constitución del Proyecto Debian (v1.2) [This Document has been Superseded by v1.3] + +@creator: Debian Project + +@type: information + +@subject: debian policy + +@date.created: 1998-12-03 + +@date.issued: 1998-12-03 + +@date.valid: 2003-10-29 + +@date.available: 2003-10-29 + +@date.modified: 2006-11-14 + +% Última modificación: mar, 14 de nov de 2006, 15:44:29 UTC + +@date: 2003-10-29 + +@language.document: Spanish + +@language.original: English + +@level: new=C; num_top=1 + +@skin: skin_debian + +@bold: Debian; DPL + +% @italics: + +@rights: http://www.debian.org/license.es.html Copyright © 1997-2006 Software in the Public Interest, Inc., P.O. Box 501248, Indianapolis, IN 46250-6248, United States, http://www.spi-inc.org/ <br>OJO: Esta es una traducción de la licencia original, y no tiene ningún valor jurídico http://www.debian.org/license.en.html. Si desea ver la versión verdadera debe acudir a la licencia original, en este mismo servidor.<br>Este material sólo puede ser distribuido sujeto a los términos y condiciones indicados en la Licencia de publicaciones abiertas, borrador v1.0 o posterior (puede consultar nuestra copia local http://www.debian.org/opl ; la última versión suele estar disponible en http://www.opencontent.org/openpub/ ). <br>"Debian" y el logotipo de Debian http://www.debian.org/logos/ son marcas registradas de Software in the Public Interest, Inc. + +@links: {Authoritative Source Document}http://www.debian.org/devel/constitution +{SiSU version using default markup}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{SiSU version markup adjusted to correspond to original document}http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html +{Debian Social Contract @ SiSU}http://www.jus.uio.no/sisu/debian_social_contract_v1.1/sisu_manifest.html +{About Debian}http://www.debian.org/intro/about +{News}http://www.debian.org/News/ +{Getting Debian}http://www.debian.org/distrib/ +{Support}http://www.debian.org/support +{Developer's Corner}http://www.debian.org/devel/ +{Sitemap}http://www.debian.org/sitemap +{Search}http://search.debian.org/ + +@prefix: This is taken from the authoritative source at http://www.debian.org/devel/constitution and is marked up and generated to check SiSU default settings, please note that the sub-numbering in using letters is not identical to the original.<br>Version 1.2 ratified on October 29th, 2003. Supersedes Version 1.1 http://www.debian.org/devel/constitution.1.1 ratified on June 21st, 2003, which itself supersedes Version 1.0 http://www.debian.org/devel/constitution.1.0 ratified on December 2nd, 1998.<br>Two different SiSU marked up versions are provided http://www.jus.uio.no/sisu/debian_constitution_v1.2/sisu_manifest.html uses simpler markup, the default numbering mode; http://www.jus.uio.no/sisu/debian_constitution_v1.2.adjusted/sisu_manifest.html uses more complicated numbering in the markup and is more true to the original + +@rcs: $Id: debian_constitution_v1.2~es.s3,v 1.6 2006/02/28 12:11:55 ralph Exp $ + +:A~ Constitución de Debian + +:B~ Constitución del Proyecto Debian (v1.2) [This Document has been Superseded by v1.3] + +1~pre [Prefix]-# + +Versión 1.2 ratificada el 29 de octubre de 2003. Sustituye a la versión 1.1 ratificada el 21 de junio de 2003, que a su vez sustituía a la versión 1.0 ratificada el 2 de diciembre de 1998. + +1~ 1. Introducción + +El Proyecto Debian es una asociación de individuos que han hecho causa común para crear un sistema operativo libre. + +Este documento describe la estructura organizativa para la toma de decisiones en el Proyecto. No describe las metas del Proyecto o cómo alcanzarlas, ni contiene ninguna norma excepto aquellas relacionadas directamente con el proceso de toma de decisiones. + +1~ 2. Individuos y organismos de toma de decisiones + +Cada decisión en el Proyecto la toman uno o más de los siguientes: + +# Los Desarrolladores, mediante una Resolución General o una elección; + +# El Líder del Proyecto; + +# El Comité Técnico o su Presidente (chairman); + +# El Desarrollador que trabaja en una tarea determinada; + +# Delegados nombrados por el Líder del Proyecto para tareas específicas; + +# El Secretario del Proyecto. + +La mayoría del resto de este documento le ayudará a formar una idea de las atribuciones de estos organismos, su composición y nombramientos, y el proceso de toma de decisiones. Las atribuciones de una persona u organismo pueden estar sujetos a revisión y/o limitación por parte de terceros; en ese caso el organismo o personas encargadas de la revisión indicarán dicha posibilidad. En la lista anterior, normalmente se lista a una persona u organismo antes de aquellos cuyas decisiones puede anular o a los que escoge (o ayuda a escoger); pero no todos los que se nombran al principio mandan sobre todos los posteriores. + +2~ Reglas generales + +# Nada en esta constitución impone obligaciones a nadie que trabaje para el Proyecto. Una persona que no quiera hacer la tarea que le ha sido delegada o asignada no necesita hacerla. Sin embargo, no se debe actuar activamente en contra de estas reglas y las decisiones tomadas apropiadamente siguiéndolas. + +# Una persona puede ocupar varios puestos, pero el Líder del Proyecto, el Secretario del Proyecto y el Presidente del Comité Técnico deben ser personas distintas, además de que el Líder no puede elegirlos como sus Delegados. + +# Una persona puede abandonar el Proyecto o dimitir de un cargo en particular, en cualquier momento, diciéndolo públicamente. + +1~ Desarrolladores individuales + |