Brion said:
/It doesn't solve our specified requirement (single Wikimedia-wide
namespace so a
single username works on all 600+ Wikimedia wikis transparently, no
muss no fuss).
/
Really? I'd think that an Interwiki-namespaced username would solve that
problem nicely, without requiring a big name-clash-fixing step when the
technology rolls out. I think that having a single username across all
wikis would be nice, if you didn't have to do resolve dupes across the
system, but if you do, it's really kind of a hassle.
I'd think that, since single-signon between wikis is a feature useful
only for a minority of registered Wikimedia users (how many actually log
into more than one Wikimedia wiki, ever? 10-20%, maybe? how many log
into more than, say, 5 wikis? Or log into more than one wiki on a
regular basis? 2%? 0.2%?), it'd be a good political idea to minimize the
namespace-sorting hassle. That nameclash-fixing step is gonna suck, and
it's not even helpful most users. It seems to me that a minor effort on
the part of "interwikiists" -- just using a project+language namespace
-- would be painless for them and unnoticeable for everyone else.
I think that if we use Interwiki prefixes on the UI side, OpenID becomes
that much easier. A user could login to French Wikibooks as
/wp:en:User:EvanProdromou/ or whatever, and the UI translates that into
the right OpenID URL (http://en.wikipedia.org/wiki/User:EvanProdromou)
and goes through the OpenID two-step to get credentials checked. Under
the covers, the OpenID stuff would get worked out right, but we could
use simpler Interwiki strings for the UI.
In fact, a drop-down box for project, and another for language, could
also significantly reduce the complexity for users. For example, I could
choose "Wikipedia" out of "Wikipedia, Wikibooks, Wiktionary, ..." and
"English" out of "English, Français, Esperanto, ..." and then my
username on that project.
Lastly, I think having a couple of professional developers eagerly
awaiting a chance to get this implemented and who know OpenID and
authentication issues inside and out is a really good thing. We
shouldn't rollout every technology that people volunteer to throw into
the software, but this seems like a pretty good match between Mediawiki
(and Wikimedia) needs and what's being offered.
~Evan
P.S. Sorry about the broken threading -- I had some mail server problems
and missed my daily dose of wikitech-l.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> If they don't break anything and fix bugs, you should have no trouble
> getting the patches accepted.
Of course, it's quite hard /not/ to break anything. (especially when
you're noodling around in a system that you have little knowledge
about). :-P
- --
Edward Z. Yang Personal: edwardzyang(a)thewritingpot.com
SN:Ambush Commander Website: http://www.thewritingpot.com/
GPGKey:0x869C48DA http://www.thewritingpot.com/gpgpubkey.asc
3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFD6UZ9qTO+fYacSNoRAmgUAJ0WzSIVnpKaeFtdFSThBTM1/hW+aACggiCN
2chBkvtbsCS0D1kPkkPyWxA=
=uBCz
-----END PGP SIGNATURE-----
hi all (my fist post here)
First, my understanding (from irc and bugzilla) is that there's nobody
working on texvc. I was going to fix bug (or to add feature, if you
like it better) which can be found on more places in bugzilla:
http://bugzilla.wikimedia.org/show_bug.cgi?id=615http://bugzilla.wikimedia.org/show_bug.cgi?id=798http://bugzilla.wikimedia.org/show_bug.cgi?id=2458
...
Problem is regarding UTF and localization, but since every languages
has its own latex package, i was thinking of somehow general approach.
OK, I'm not going to go into details right now, first I'm interested:
Am I allowed to work on texvc?
To whom to consult for details (if any)?
Will you accept my patches (of course, if they work:) (I don't want to
do it just for myself)?
If my mail is on wrong mailing list, where to ask?
Thanks in advance, Kokanovic Branko
--
"Since light travels faster than sound, people appear bright until you
hear them speak." -Anonymous
Hi,
how can I delete old versions of articles in my mediawiki
installation? I know that I can delete all versions and restore the
latest. But I have to to this on about 500 articles.
greetings
Juergen
An automated run of parserTests.php showed the following failures:
Running test BUG 361: URL within URL, not bracketed... FAILED!
Running test External links: invalid character... FAILED!
Running test Bug 2702: Mismatched <i> and <a> tags are invalid... FAILED!
Running test A table with no data.... FAILED!
Running test A table with nothing but a caption... FAILED!
Running test Link containing "#<" and "#>" % as a hex sequences... FAILED!
Running test Magic links: PMID incorrectly converts space to underscore... FAILED!
Running test Template with thumb image (wiht link in description)... FAILED!
Running test Link to image page... FAILED!
Running test BUG 1887: A ISBN with a thumbnail... FAILED!
Running test BUG 1887: A <math> with a thumbnail... FAILED!
Running test Image caption containing another image... FAILED!
Running test BUG 561: {{/Subpage}}... FAILED!
Running test Simple category... FAILED!
Running test Section headings with TOC... FAILED!
Running test Media link with nasty text... FAILED!
Running test Image link to nonexistent file (bug 1850 - good)... FAILED!
Running test Bug 2095: link with pipe and three closing brackets... FAILED!
Running test Sanitizer: Validating the contents of the id attribute (bug 4515)... FAILED!
Passed 262 of 281 tests (93.24%) FAILED!
Hello,
I'm helping someone use my OpenID patch with MediaWiki, and it seems
that MediaWiki can't easily be used with things in the standard PHP
include path. These two lines in LocalSettings.php are the culprit:
$path = array( $IP, "$IP/includes", "$IP/languages" );
set_include_path( implode( PATH_SEPARATOR, $path ) );
So, if /usr/share/php is in the PHP include path, it'll get blown
away. Is MediaWiki so self-sufficient that this has never stepped on
efforts to include things in, say, PEAR? Is modifying the above code
an acceptable way to customize a given MediaWiki install if things in
/usr/share/php are needed? Any advice would be appreciated.
Thanks!
--
Jonathan Daugherty
JanRain, Inc.
Hello all,
A few days ago I posted a patch to the list, I realized the site where
I put the patch isn't working properly.
In the hope this is usefull, here is the patch.
Regards,
Manuel.
An automated run of parserTests.php showed the following failures:
Running test BUG 361: URL within URL, not bracketed... FAILED!
Running test External links: invalid character... FAILED!
Running test Bug 2702: Mismatched <i> and <a> tags are invalid... FAILED!
Running test A table with no data.... FAILED!
Running test A table with nothing but a caption... FAILED!
Running test Link containing "#<" and "#>" % as a hex sequences... FAILED!
Running test Magic links: PMID incorrectly converts space to underscore... FAILED!
Running test Template with thumb image (wiht link in description)... FAILED!
Running test Link to image page... FAILED!
Running test BUG 1887: A ISBN with a thumbnail... FAILED!
Running test BUG 1887: A <math> with a thumbnail... FAILED!
Running test Image caption containing another image... FAILED!
Running test BUG 561: {{/Subpage}}... FAILED!
Running test Simple category... FAILED!
Running test Section headings with TOC... FAILED!
Running test Media link with nasty text... FAILED!
Running test Image link to nonexistent file (bug 1850 - good)... FAILED!
Running test Bug 2095: link with pipe and three closing brackets... FAILED!
Running test Sanitizer: Validating the contents of the id attribute (bug 4515)... FAILED!
Passed 262 of 281 tests (93.24%) FAILED!
I would like to see wiki markup support for outlining, ie for
hierarchical lists which can be expanded or contracted by clicking on
icons.
I did not find any reference to this in the newsgroup version of
wikitech-l at gmane.org; my apologies if this has been brought up before.
Henry
I've finally upgraded to 1.5.5 but now I can't get any of the great
new extensions to work.
For example here is what I get with Erik Möller's Inputbox extension:
http://www.eco-gites.com/wiki/index.php/Main_Page
Any idea what's gone wrong?
I'm baffled - the same thing happens with all extensions. So it must
be something wrong with the set-up.
Paul