From: Michael Veeck <michael.veeck@gmx.net>
To: kernel-janitors@vger.kernel.org
Subject: Re: [KJ] [RFC] new design for kerneljanitors.org?
Date: Thu, 11 Aug 2005 21:21:57 +0000 [thread overview]
Message-ID: <42FBC175.5040901@gmx.net> (raw)
In-Reply-To: <42C1CDE1.9010308@gmx.net>
Looks good. Now we would need someone with an older version of IE to
test it. Anyone here who can provide such service?
Best regards
MVeeck
Lukas Sandström schrieb:
> Michael Veeck wrote:
>
>>Alrighty then, I uploaded latest website to http://veeck.de/janitor/
>>
>>Small cleanups and added the presentation from IEEE2005.
>>
>>Best regards
>>Michael Veeck
>>
>
>
> Unfortunatley, it doesn't look very good in my Firefox setup, most
> likley due to the relative positioning of the <div>'s.
>
> See http://www.etek.chalmers.se/~lukass/linnewb/old_style.jpg for a
> screenshot of how http://veeck.de/janitor/index.html rendered for me at
> 20:43 GMT 2005-07-16.
>
> I took the liberty of making some improvements to the css and html. You
> can see the results at http://www.etek.chalmers.se/~lukass/linnewb/
>
> The attached diffs show the (fairly small) changes I made.
>
> The only regression, as I see it, is that I had to place the
> offsite-links before the local- and contact-info in order for the float
> to work nicely. This makes the offsite links appear before the local and
> contact when viewed in lynx or with stylesheets enabled.
>
> /Lukas Sandström
>
>
> ------------------------------------------------------------------------
>
> --- index-orig.html 2005-07-16 21:23:11.000000000 +0200
> +++ index.html 2005-07-16 21:33:58.000000000 +0200
> @@ -14,18 +14,34 @@
> <body>
>
> <div id="header">
> - <img class="padded_left" src="pengsmall.png" alt="Linux Penguin Picture"/>
> - <p>Welcome to The Linux Kernel Janitor Project home page.</p>
> + <img id="penguin" src="pengsmall.png" alt="Linux Penguin Picture"/>
> + <h1>Welcome to The Linux Kernel Janitor Project home page.</h1>
> </div>
>
> - <div id="headtext">
> + <div id="headtext"><p>
> We go through the Linux kernel sources, doing code reviews, fixing up
> unmaintained code and doing other cleanups and API conversion.
> - It is a good start to kernel hacking.
> + It is a good start to kernel hacking.</p>
> + </div>
> + <div id="offsite" class="box">
> + <div class="title"><h2>Offsite Links:</h2></div>
> + <ul>
> + <li><a href="http://coderock.org/kj/">Kernel janitor patchsets</a></li>
> + <li><a href="http://bugzilla.kernel.org/">2.5/2.6 kernel bugzilla database</a></li>
> + <li><a href="http://www.codemonkey.org.uk/projects/git-snapshots/sparse/">Sparse snapshot</a></li>
> + <li><a href="http://smatch.sourceforge.net/">Smatch project</a></li>
> + <li><a href="http://metacomp.stanford.edu/">Stanford Checker</a></li>
> + <li><a href="http://developer.osdl.org/cherry/compile/">2.6 Linux IA-32 compile statistics</a></li>
> + <li><a href="http://www.osdl.org/projects/26lnxstblztn/results/">2.6 Linux stabilization project</a></li>
> + <li><a href="http://www.linuxdevices.com/articles/AT5340618290.html">Writing portable device drivers</a> - Linux Journal article by Greg Kroah-Hartman</li>
> + <li><a href="http://people.redhat.com/arjanv/olspaper.pdf">How to NOT write a device driver</a> - OLS2002 paper by Arjan van de Ven</li>
> + <li><a href="http://developer.osdl.org/rddunlap/doc/scale-3x-kj-v5.pdf">Randy's KJ presentation at SCALE 2005</a></li>
> + <li><a href="http://archive.linuxsymposium.org/ols2003/Proceedings/All-Reprints/Reprint-Melo-OLS2003.pdf">ACME's KJ presentation at OLS 2003</a></li>
> + <li><a href="http://www.madrone.org/mentor/linux-mentoring.pdf">Linux Kernel Development: Getting Started</a> - IEEE Northcon 2005 paper by Randy Dunlap </li>
> + </ul>
> </div>
> -
> <div id="local" class="box">
> - <div class="title">Local Information:</div>
> + <div class="title"><h2>Local Information:</h2></div>
> <ul>
> <li><a href="http://kerneljanitors.org/TODO">The current TODO list</a></li>
> <li><a href="http://kerneljanitors.org/README">The project README file</a></li>
> @@ -38,7 +54,7 @@
> </div>
>
> <div id="contact" class="box">
> - <div class="title">Contact Information:</div>
> + <div class="title"><h2>Contact Information:</h2></div>
> <ul>
> <li>
> <dl>
> @@ -60,29 +76,11 @@
> </ul>
> </div>
>
> - <div id="offsite" class="box">
> - <div class="title">Offsite Links:</div>
> - <ul>
> - <li><a href="http://coderock.org/kj/">Kernel janitor patchsets</a></li>
> - <li><a href="http://bugzilla.kernel.org/">2.5/2.6 kernel bugzilla database</a></li>
> - <li><a href="http://www.codemonkey.org.uk/projects/git-snapshots/sparse/">Sparse snapshot</a></li>
> - <li><a href="http://smatch.sourceforge.net/">Smatch project</a></li>
> - <li><a href="http://metacomp.stanford.edu/">Stanford Checker</a></li>
> - <li><a href="http://developer.osdl.org/cherry/compile/">2.6 Linux IA-32 compile statistics</a></li>
> - <li><a href="http://www.osdl.org/projects/26lnxstblztn/results/">2.6 Linux stabilization project</a></li>
> - <li><a href="http://www.linuxdevices.com/articles/AT5340618290.html">Writing portable device drivers</a> - Linux Journal article by Greg Kroah-Hartman</li>
> - <li><a href="http://people.redhat.com/arjanv/olspaper.pdf">How to NOT write a device driver</a> - OLS2002 paper by Arjan van de Ven</li>
> - <li><a href="http://developer.osdl.org/rddunlap/doc/scale-3x-kj-v5.pdf">Randy's KJ presentation at SCALE 2005</a></li>
> - <li><a href="http://archive.linuxsymposium.org/ols2003/Proceedings/All-Reprints/Reprint-Melo-OLS2003.pdf">ACME's KJ presentation at OLS 2003</a></li>
> - <li><a href="http://www.madrone.org/mentor/linux-mentoring.pdf">Linux Kernel Development: Getting Started</a> - IEEE Northcon 2005 paper by Randy Dunlap </li>
> - </ul>
> - </div>
> -
> <div id="footer">
> <a href="http://validator.w3.org/check?uri=referer">
> - <img src="http://www.w3.org/Icons/valid-xhtml11" alt="Valid XHTML 1.1!" height="31" width="88" class="padded_left"/>
> + <img src="http://www.w3.org/Icons/valid-xhtml11" alt="Valid XHTML 1.1!" height="31" width="88" id="valid_xhtml"/>
> </a>
> - <p>page last modified 07-16-2005</p>
> + <p id="lastmod">page last modified 07-16-2005</p>
> </div>
>
> </body>
>
>
> ------------------------------------------------------------------------
>
> --- style-orig.css 2005-07-16 21:23:33.000000000 +0200
> +++ style.css 2005-07-16 21:39:00.000000000 +0200
> @@ -3,8 +3,13 @@ body {
> color: #000000;
> font-size: 12pt;
> font-family: verdana, arial, helvetica, sans-serif;
> + margin: 0 auto;
> + margin-top: 10px;
> + width: 910px;
> +}
> +#penguin {
> + float: left;
> }
> -
> #header {
> border-collapse: collapse;
> border-style: solid;
> @@ -20,7 +25,9 @@ body {
> margin-left: auto;
> margin-right: auto;
> }
> -
> +#header h1 {
> + font-size: 12pt;
> +}
> #headtext {
> border-collapse: collapse;
> border-style: solid;
> @@ -37,22 +44,19 @@ body {
> }
>
> #local {
> - position:relative; left:-189pt;
> width: 400px;
> }
>
> #contact {
> - position:relative; left:-252px; top: -10px;
> width: 400px;
> }
>
> #offsite {
> - position:relative; left: 204px; top: -362px;
> width: 495px;
> + float: right;
> }
>
> #footer {
> - position:relative; left: 500px; top: -330px;
> font-size: 0.7em;
> }
>
> @@ -60,10 +64,15 @@ div.title {
> padding-top: 2px;
> padding-bottom: 2px;
> width: 100%;
> +
> + background-color: #000000;
> +}
> +.title h2 {
> text-align: center;
> font-weight: bold;
> - background-color: #000000;
> + font-size: 12pt;
> color: #ffffff;
> + margin: 0;
> }
>
> div.box {
> @@ -76,10 +85,10 @@ div.box {
> background-color: #ffffff;
>
> text-align: center;
> - vertical-align: text-top;
> + vertical-align: text-top;
>
> padding: 0px;
> - margin: 1em auto;
> + margin-bottom: 10px;
> }
>
> a:link {
> @@ -106,12 +115,17 @@ a:hover {
> font-weight: bold;
> }
>
> -img.padded_left {
> +#valid_xhtml{
> position: relative;
> border: 0px;
> float: left;
> }
> -
> +#lastmod {
> + float: right;
> +}
> +p {
> + margin: 0;
> +}
> ul {
> list-style-type: none;
> margin: 0px;
> @@ -119,10 +133,10 @@ ul {
> border: 0px;
> }
>
> -li {
> +li {
> text-align: left;
> }
>
> -dt {
> +dt {
> font-weight: bold;
> }
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/kernel-janitors
next prev parent reply other threads:[~2005-08-11 21:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 22:23 [KJ] [RFC] new design for kerneljanitors.org? Michael Veeck
2005-06-29 6:55 ` Christophe Lucas
2005-06-29 10:40 ` Nico Golde
2005-06-29 12:40 ` Domen Puncer
2005-07-02 10:16 ` maximilian attems
2005-07-16 14:33 ` Michael Veeck
2005-07-16 15:42 ` randy_dunlap
2005-07-16 15:50 ` Michael Veeck
2005-07-16 16:29 ` randy_dunlap
2005-07-16 16:52 ` Michael Veeck
2005-07-16 17:12 ` randy_dunlap
2005-07-16 19:53 ` Lukas Sandström
2005-07-18 8:42 ` maximilian attems
2005-07-18 8:45 ` Carlo Perassi
2005-07-18 8:57 ` maximilian attems
2005-08-11 21:21 ` Michael Veeck [this message]
2005-08-12 10:07 ` Christophe Lucas
2005-08-12 10:51 ` Maximilian Attems
2005-08-12 13:41 ` Christophe Lucas
2005-08-12 18:04 ` Michael Veeck
2005-11-01 13:07 ` [KJ] [RFC] new design for kerneljanitors.org REV 2 Jerome Pinot
2005-11-01 13:43 ` Michael Veeck
2005-11-01 14:22 ` Jerome Pinot
2005-11-01 19:43 ` Michael Veeck
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 6:41 [KJ] [RFC] new design for kerneljanitors.org? Michael Veeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42FBC175.5040901@gmx.net \
--to=michael.veeck@gmx.net \
--cc=kernel-janitors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.