git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J.H." <warthog19@eaglescrag.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Petr Baudis <pasky@suse.cz>,
	git@vger.kernel.org
Subject: Re: [RFC] Git Wiki Move
Date: Mon, 18 Jan 2010 10:47:25 -0800	[thread overview]
Message-ID: <4B54ACBD.6000000@eaglescrag.net> (raw)
In-Reply-To: <alpine.DEB.1.00.1001181258540.3044@intel-tinevez-2-302>

On 01/18/2010 04:03 AM, Johannes Schindelin wrote:
> Hi,
> 
> On Mon, 18 Jan 2010, Johannes Schindelin wrote:
> 
>> On Sun, 17 Jan 2010, J.H. wrote:
>>
>>> On 01/17/2010 03:06 PM, Johannes Schindelin wrote:
>>>
>>>> BTW there is a file KHTMLFixes.css in the directory skins/monobook/ 
>>>> which makes the layout break with Chromium.  Apparently, it is no 
>>>> longer needed by KHTML anyway.  So could you please replace that 
>>>> file with an empty one, or comment out the offending part, like so:
>>>>
>>>> 	/* #column-content { margin-left: 0; } */
>>>
>>> I'm not keen on making changes since that file is still coming from 
>>> the shipping version of mediawiki and I'm trying, quite a lot, to not 
>>> run a modified version of it.  I've got enough troubles with the fact 
>>> that that one change would affect 22 wikis in a single go.
>>>
>>> As bad as it is to say this, I'd rather wait for 1.16 to come out vs. 
>>> modify it in place.  Mediawiki is claiming they are in continuous 
>>> integration development with quarterly releases but their last release 
>>> was June of 2009, so take that as you will.
>>
>> Fair enough.  As long as Chromium has a fairly small share of the 
>> market, I think it is safe to tell everybody to wait a little until the 
>> side bar is no longer displayed at the left _below_ the main body text.  
>> AFAICT the problem was solved with Wikipedia, so the next release should 
>> magically fix the issue.
> 
> Actually, in a rare case of cleverness, I found out how to fix it (at 
> least for me, it works):
> 
> 	http://git.wiki.kernel.org/index.php/MediaWiki:Monobook.css
> 
> Of course, this is only a work-around, and it will get broken once 
> Monobook changes dimensions (or more).  But hopefully Chromium will be 
> fixed by then, extending the canvas into the negative arm of the x axis 
> whenever needed.  And then I will happily delete the custom Monobook.css.

That works.

> These are the things left that I would like to see soon:
> 
> - add a link from the old Wiki (with rewrite rules)

I think the rewrites should be simple enough (the pages seem to line up
1:1 easily enough) so all I would need to do is discuss this with Petr.

> - use whatever logo (anything is better than the sunflower)

It's easy enough to change just need to know which one to use.

> - enable anonymous edits

Anonymous edits will *NEVER* be enabled.  You are going to need to have
an account and your going to have to verify it's e-mail to be able to do
eits.  Completely anonymous edits are too much of a risk considering
bots and spam and the abuse they can do.

Even then there is at least one case of a spammer actually going through
and using a verified account.

> - a major cleanup of the broken autolinks and faulty formatting.
> 
> The latter point is probably the most tedious one, so I suggest that only 
> those get a vote on the logo who fix at least 3 pages.

sound fair to me.

- John 'Warthog9' Hawley

  reply	other threads:[~2010-01-18 18:47 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 23:29 [ANNOUNCE] Git wiki & repo.or.cz migration, donations and volunteers pledge Petr Baudis
2010-01-14  1:24 ` [RFC] Git Wiki Move Petr Baudis
2010-01-14 10:28   ` J.H.
2010-01-14 10:35     ` Matthieu Moy
2010-01-14 18:56       ` J.H.
2010-01-15 23:18         ` J.H.
2010-01-15 23:21           ` Sverre Rabbelier
2010-01-15 23:50             ` Junio C Hamano
2010-01-16  0:05               ` J.H.
2010-01-16  0:02             ` J.H.
2010-01-16  0:08               ` Sverre Rabbelier
2010-01-16  0:12                 ` Junio C Hamano
2010-01-16  0:28                 ` J.H.
2010-01-16  0:44                   ` Sverre Rabbelier
2010-01-16  1:18                     ` J.H.
2010-01-16 10:17                       ` Clemens Buchacher
2010-01-17 12:00           ` Matthieu Moy
2010-01-17 23:06             ` Johannes Schindelin
2010-01-18  0:43               ` J.H.
2010-01-18  9:53                 ` Johannes Schindelin
2010-01-18 12:03                   ` Johannes Schindelin
2010-01-18 18:47                     ` J.H. [this message]
2010-01-18 20:46                       ` Johannes Schindelin
2010-01-21 21:35                       ` Petr Baudis
2010-01-22  0:21                         ` Jakub Narebski
2010-01-22  0:31                           ` Petr Baudis
2010-01-22  0:39                           ` Johannes Schindelin
2010-01-14 10:43     ` Johannes Schindelin
2010-01-14 11:01       ` Johannes Schindelin
2010-01-14 18:52       ` J.H.
2010-01-14 10:48     ` Petr Baudis
2010-01-14 11:03       ` Johannes Schindelin
2010-02-12 11:38     ` Petr Baudis
2010-01-14 10:48   ` Wincent Colaiuta
2010-01-15 17:17   ` Joey Hess
2010-01-15 19:16     ` Johannes Schindelin

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=4B54ACBD.6000000@eaglescrag.net \
    --to=warthog19@eaglescrag.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).