Hello all,
A reminder that WikiSym 2009 will be in Orlando, Florida, from October
25-27. The deadline for submitting papers, workshops and panel
proposals is March 27; April 24th is the deadline for posters,
demonstrations and WikiFest (practical experience) proposals.
Topics of interest include:
* social software for collaboration and work group processes
* wiki user experiences, usability, and discourse analysis
* reputation systems, quality assurance processes
* scalability---social and technical
* wiki technologies and implementations
* translation and multilingual wiki content
* educational applications
* wiki for non-textual media (images, video, audio)
* content dynamics and wiki evolution
* wiki journalism
* wiki archiving and versioning
* wiki administration: dealing with abuse and resolving conflict
* wiki and the semantic web, knowledge management, tacit knowledge
* wiki for small audiences (departmental and family wikis)
* legal issues (copyright, licensing)
* visualization of wiki structure
* wiki fiction
For more information, see the Call for Papers:
http://www.wikisym.org/ws2009/tiki-index.php?page=Call+for+Papers
WikiSym is an annual conference devoted to research into all aspects
of wikis, including wiki communities, wiki software and technology,
and using wikis in education and organizations. Research papers about
the Wikimedia projects are welcome! Papers are peer reviewed and
archived in the ACM digital library (see past proceedings:
http://portal.acm.org/toc.cfm?id=SERIES11299&coll=ACM&dl=ACM&type=series&id…
The conference is colocated with OOPSLA 2009. For more, see:
http://www.wikisym.org/ws2009/
-- Phoebe Ayers (2009 Wikimedia Liason)
In the quest to simplify and improve Wikipedia's HTML code, the turn
has come to footnotes. Here is a proposal that describes how the
number of elements needed to represent footnotes can be halved:
http://www.princexml.com/howcome/2009/wikipedia/ref/
As far as I can tell, the proposed markup works in legacy browsers,
too.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
howcome(a)opera.com http://people.opera.com/howcome
Hello,
Given that the current dump process is having problem, why not provide
a simple fix such as providing raw table format , SQL files or even
CSV files?
I think there are quite still many people using MySQL and prefer these
format instead of XML (as you know XML generation and parsing really
take time...)
Howard
What test wiki other than one's own runs the current SVN version?
Even test.wikipedia.org is "only" at r48811.
How does one confirm a problem is not just local before posting a bug
without waiting a few days for test.wikipedia.org to catch up?
Hello all,
I think that when such a number of people come together it would be nice to
have a key-signing in Berlin. If you have no idea, what a key-signing is, look
at the wikipedia-article [[en:Key_signing_party]].
If you don't own a pgp-key yet and are an linux-user there are several how-tos
on the net to get one fast (there are how-tos for windows-users too, but it's
more complex, but that doesn't need to stop you).
Because there is no time (and place) for a hash-methode-keysigning (you know,
all standing in a line for hours ;)), I would organise a
list-methode-keysigning. That means that you send me
*Your nick (if you have one)
*Your realname (optional, but some people don't sign non-realname-keys)
*Your keynumber
*Your key-hash
*Your key (if it is not on normal key-servers)
to pgp(a)daniel.baur4.info.
I will make a list of that data. Then I (respectively the verein) will print
out several copies of that list and place them at central places (like the
reception or the c-base) for hand-out. You can also place sticker on your
nameplate (to let people easier find you) if you like (I have colorful
sticker-dots here ;)).
You will take such an list and start looking for other people, that stand on
the list, check your hash on his/her list and his/her hash on your list and
mark your name as checked on his/her list and his/her name on your list if
all is right. Then continue until all entries on your list are checked (or
the meeting is over).
It would be very nice if many people would participate to increase the level
of trust (at least the key-trust) between us.
Follow up to foundation-list.
Sincerly,
DaB.
P.S: Even if you come just to the party on saturday, you can take part!
2.P.S: I organize a key-signing for the first time, so please be patient if I
did anything wrong.
--
Diese eMail sollte mit dem PGP-Schlüssel 0x2D3EE2D42B255885 digital signiert
sein. Bitte beachten Sie, das unsignierte eMails beliebig gefälscht sein
können. Achten Sie daher auf Signaturen.
An out-of-memory condition crashed the database master for English
Wikipedia; we were down for about 25 minutes. All is restarted and
recovered now (thanks Domas!); our other sites were not affected.
http://techblog.wikimedia.org/2009/03/english-wikipedia-database-temporaril…
-- brion vibber (brion @ wikimedia.org)
CTO, Wikimedia Foundation
San Francisco
Gentlemen, why doesn't the database's text table use Linus Torvalds'
"git" style mapping of identical contents to the same row, as they
have the same SHA1 hash?
Currently even undoing a user's edit just points to a fresh row in the
text table instead of pointing to the identical old one.
This despite these words in tables.sql:
-- It's possible for multiple revisions to use the same text,
-- for instance revisions where only metadata is altered
-- or a rollback to a previous version.
Examining my wiki,
echo "SELECT old_text FROM text;"|mysql --default-character-set=binary radioscanningtw -N|\
perl -nwle 'use Digest::SHA1 qw/sha1_hex/;$h{sha1_hex($_)}++;END{for(keys %h){print $h{$_}}}'|sort -nr|uniq -c
1 247
1 5
2 4
10 3
261 2
1206 1
I find all but the last 1206 records are duplicated.
echo "SELECT old_text FROM text;"|mysql --default-character-set=binary radioscanningtw -N|\
perl -lnwe 'use Digest::SHA1 qw/sha1_hex/;print sha1_hex($_),"\t", $_'|sort|uniq -c|sort -nr|\
perl -C -nwle '/.{0,88}/;print $&;exit if $.==5'
247 da39a3ee5e6b4b0d3255bfef95601890afd80709
5 bf36408b7db0ea4b834b935ae2992e97fd438539 請問台中港務警察局的頻率、頻道，有人知道嗎？可以分享嗎？
4 fa21b2d9a4ace2bb86917e7a83ad20a1f5301917 {{c|486.1000}}|{{c|DCS 065}}|{{c|呼 8xx}
4 a860f97b87c81344239766c2f243bfff05ae7cdd #REDIRECT [[Project:幫助]]
3 edabb0d4f0f21cd9dfba867ef9cdbc584c8937c1 全國監獄 {{c|150.6750}}
I even have 247 separate entries for a file with 0 bytes, from a page
blanking incident. One would be enough.
Also note that the 'patrolled revisions' aspect is particularly messy to
implement. Some changes have been made but more are still needed to the
extension. I'm tempted to split off patrolling into its own code other
tables.
-Aaron
--------------------------------------------------
From: "Brion Vibber" <brion(a)wikimedia.org>
Sent: Monday, March 30, 2009 1:02 PM
To: "Wikimedia developers" <wikitech-l(a)lists.wikimedia.org>
Subject: Re: [Wikitech-l] Progress on the Flagged Revisions front
> On 3/29/09 3:32 AM, private musings wrote:
>> Because I'm an idiot, I tried to send this before subscribing to this
>> particular list. I don't have high hopes of understanding much herein,
>> but hope the below is clear :-)
>
> It's all in the queue; further code and UI cleanup is ongoing.
>
> -- brion
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
>
Because I'm an idiot, I tried to send this before subscribing to this
particular list. I don't have high hopes of understanding much herein,
but hope the below is clear :-)
I gather Jimbo is putting some sort of proposal before the (WMF) board
too, and look forward to hearing exactly what that entails - it'll be
great to read something out in public somewhere fairly soon - however
per the below I hope readers of this list will concur that the best
step forward is to enable to extension to facilitate the trial :-)
cheers,
PM.
---------- Forwarded message ----------
From: private musings <thepmaccount(a)gmail.com>
Date: Thu, 26 Mar 2009 13:36:48 +1100
Subject: Progress on the Flagged Revisions front
To: wikitech-l(a)lists.wikimedia.org
This proposal;
http://en.wikipedia.org/wiki/Wikipedia:Flagged_protection_and_patrolled_rev…
would seem to have a strong consensus in support, following a 9 day poll here;
http://en.wikipedia.org/wiki/Wikipedia_talk:Flagged_protection_and_patrolle…
It's a very gentle implementation, but the description is crystal
clear, and hopefully this is clear and defined enough for the dev.s to
'switch on'.
If more information or parameters are required, it would be fantastic
for decision makers to try and be explicit in how best to clear the
path - perhaps the feature can be turned on by the first of next
month? ;-)
cheers,
PM.