<html><head></head><body>Cross-posting on debian-desktop as some designers and artists might be lurking around.<br>
<br>
Is there a starting point like an existing theme or documentation on the theming process where people can have a look and hack around ?<br>
<br>
Are there guidelines on the new design ? That it should somehow match other Debian web presence or existing Debian documentation themes ?<br>
<br>
I feel that the work on this will require iterations, improvements and bug/usability fixes, so people who are already regular or occasional contributors to Debian design and theming are welcome to help and voice their thoughts, whichever proposal ends up being selected.<br>
<br>
<br>
Cheers,<br>
--Aurélien<br><br><div class="gmail_quote">Le 21 août 2017 23:46:17 GMT+02:00, Laura Arjona Reina <larjona@debian.org> a écrit :<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Hello designers!<br /><br />Quoting from the message below:<br /><br />"We are seeking volunteers to design a Debian documentation Sphinx<br />theme. The maintainers of other core pieces of Debian documentation are<br />also looking to move to Sphinx, so such a theme would see wide use."<br /><br />Maybe somebody in this list can help on this?<br /><br />Thanks<br /><br /><br />-------- Mensaje Original --------<br />De: Sean Whitton <spwhitton@spwhitton.name><br />Enviado: 21 de agosto de 2017 23:35:39 CEST<br />Para: debian-devel-announce@lists.debian.org<br />Asunto: Debian Policy <a href="http://4.1.0.0">4.1.0.0</a> released<br /><br />Hello everyone,<br /><br />Debian Policy <a href="http://4.1.0.0">4.1.0.0</a> is on its way into unstable.<br /><br />The source of the Policy Manual is now in reStructuredText, and the<br />Sphinx toolchain is used to produce our output formats. This has<br />enabled us to introduce new ePub and Texinfo output formats, so it's now<br />more comfortable to read Policy on the beach, and in Emacs.<br /><br />Many thanks to Hideki Yamane for writing the rST conversion scripts and<br />pushing the project forward, and David Bremner for help proofreading.<br />Russ Allbery and I updated the build system.<br /><br />We are seeking volunteers to design a Debian documentation Sphinx<br />theme. The maintainers of other core pieces of Debian documentation are<br />also looking to move to Sphinx, so such a theme would see wide use.<br /><br />Here are the changes from the previously announced version of Policy<br />(4.0.1):<br /><br />2.2.1<br /> Non-default alternative dependencies on non-free packages are<br /> permitted for packages in main.<br /><br />4.11<br /> If upstream provides OpenPGP signatures, including the upstream<br /> signing key as debian/upstream/signing-key.asc in the source<br /> package and using the pgpsignurlmangle option in<br /> debian/watch configuration to indicate how to find the upstream<br /> signature for new releases is recommended.<br /><br />4.15<br /> Packages should build reproducibly when certain factors are held<br /> constant; see 4.15 for the list.<br /><br />4.15<br /> Packages are recommended to build reproducibly even when build<br /> paths and most environment variables are allowed to vary.<br /><br />9.1.1<br /> Only the dynamic linker may install files to /lib64/.<br /><br /> No package for a 64 bit architecture may install files to<br /> /usr/lib64/ or any subdirectory.<br /><br />11.8.3<br /> The required behaviour of x-terminal-emulator -e has been<br /> clarified, and updated to replace a false claim about the<br /> behaviour of xterm.<br /><br /> Programs must support `-e command` where command may include<br /> multiple arguments, which must be executed as if the arguments<br /> were passed to execvp directly, bypassing the shell.<br /><br /> If this execution fails and -e has a single argument,<br /> xterm's fallback behaviour of passing command to the shell<br /> is permitted but not required.<br /></pre></blockquote></div></body></html>