Hi all!, I wanted to bring everyones attention to the discussion happening
on meta about global sysops. I know its been discussed before and it appears
that we have a fairly concrete concerns in favor on the discussion page but
its a smallish group and if we want this to be successful we need to have a
wider discussion and hopefully get some translations made and notices put up
for other wikis, especially the small ones which this would effect the most.
Current Discussion: http://meta.wikimedia.org/wiki/Talk:Global_sysops
cross posted to wikipedia-l, apologizes to those who get it twice if you
feel it should be posted elsewhere please feel free to let me know or do so
jalexan5(a)u.rochester.edu or gmail.com
100 gmail invites and no one to give them to :( let me know if you want one
I am working on a Deletopedia for the history of Kosovo,
to put them into the althistory wikia.
for this purpose I would like to have access to the
Deleted page and revision data. (private)
>From the database dumps.
I don't need all of the versions, just one.
I don't need all the articles, just the kosovo related ones.
For those of us who don't follow the tech blog , I'm pleased to
announce that LiquidThreads is now in beta testing in the Wikimedia
LiquidThreads is a next-generation discussion system for MediaWiki,
which turns talk pages into a real forum, while maintaining the
essential aspects of a wiki that make them so effective. It was
originally developed as a Google Summer of Code project by David
McCabe, and I've spent the last 4 months preparing it for deployment
on Wikimedia sites, under contract from the Foundation.
Presently, we're waiting for the labs project to become relatively
stable, and have all the features we need. Once that's been done, we
will commence a staged roll-out of LiquidThreads on various Wikimedia
sites. It should be noted that LiquidThreads has a mode in which it
can be switched on or off per-page. My intention is to activate it on
sites in that mode, and allow users to discuss pages that would
benefit from the enhanced discussion management (I'm thinking of high-
traffic noticeboards and discussion pages). Once it's been rolled out
and people are familiar with it, we can think about the possibility of
turning it on for all discussion pages.
LiquidThreads is very much a work in progress, and your feedback is
essential for it to get to a point at which we can deploy it on this
wiki. Please do send any and all constructive feedback to the feedback
page on the test wiki, and I will do my best to accommodate it.
I'm very excited about the opportunity to bring this technology to
Wikipedia, and to give our discussion pages a long-needed overhaul.
I'd like to share some exciting news with you all... After four awesome
years working for the Wikimedia Foundation full-time, next month I'm
going to be starting a new position at StatusNet, leading development on
the open-source microblogging system which powers identi.ca and other sites.
I've been contributing to StatusNet (formerly Laconica) as a user, bug
reporter, and patch submitter since 2008, and I'm really excited at the
opportunity to get more involved in the project at this key time as we
gear up for a 1.0 release, hosted services, and support offerings.
StatusNet was born in the same free-culture and free-software community
that brought me to Wikipedia; many of you probably already know founder
Evan Prodromou from his longtime work in the wiki community, launching
the awesome Wikitravel and helping out with MediaWiki development on
various fronts. The "big idea" driving StatusNet is rebalancing power in
the modern social web -- pushing data portability and open protocols to
protect your autonomy from siloed proprietary services... People need
the ability to control their own presence on the web instead of hoping
Facebook or Twitter always treat you the way you want.
This does unfortunately mean that I'll have less time for MediaWiki as
I'll be leaving my position as Wikimedia CTO sooner than originally
anticipated, but that doesn't mean I'm leaving the Wikimedia community
or MediaWiki development!
Just as I was in the MediaWiki development community before Wikimedia
hired me, you'll all see me in the same IRC channels and on the same
mailing lists... I know this is also a busy time with our fundraiser
coming up and lots of cool ongoing developments, so to help ease the
transition I've worked out a commitment to come into the WMF office one
day a week through the end of December to make sure all our tech staff
has a chance to pick my brain as we smooth out the code review processes
and make sure things are as well documented as I like to think they are. ;)
We've got a great tech team here at Wikimedia, and we've done so much
with so little over the last few years. A lot of really good work is
going on now, modernizing both our infrastructure and our user
interface... I have every confidence that Wikipedia and friends will
continue to thrive!
I'll start full-time at StatusNet on October 12. My key priorities until
then are getting some of our key software rollouts going, supporting the
Usability Initiative's next scheduled update and getting a useful but
minimally-disruptive Flagged Revisions configuration going on English
Wikipedia. I'm also hoping to make further improvements to our code
review process, based on my experience with our recent big updates as
well as the git-based workflow we're using at StatusNet -- I've got a
lot of great ideas for improving the CodeReview extension...
Erik Moeller will be the primary point of contact for WMF tech
management issues starting October 12, until the new CTO is hired. I'll
support the hiring process as much as I can, and we're hoping to have a
candidate in the door by the end of the year.
-- brion vibber (brion @ wikimedia.org)
CTO, Wikimedia Foundation
Reminder: Strategic Planning office hours will happen at:
04:00-05:00 UTC, Wednesday, October 7.
Tuesday (6 Oct), 9-10pm PDT
Wednesday, 12am-1am EDT
We'll meet in the channel #wikimedia-strategy on IRC. More details
are available at http://strategy.wikimedia.org/wiki/IRC_Office_Hours
We will provide some overview into the next phase of the strategic
planning process, as well as some ideas on how to have a local
discussion about strategic planning.
To find the time in your local time zone, go to: http://timeanddate.com/worldclock/fixedtime.html?month=10&day=07&year=2009&…
Facilitator, Strategic Planning
Imagine a world in which every human being can freely share in
the sum of all knowledge. Help us make it a reality!
As User:mizusumashi said in wikitech-list, now in Japanese Wikipedia,
it's proposed that to change sitename ($wgSitename) from "Wikipedia" into "ウィキペディア" at [[w:ja:Wikipedia:井戸端/subj/サイト名の設定を「ウィキペディア」にする提案]] (http://bit.ly/C7RPz).
wikitech-list member advised very useful thing for this changing, but it's a little more technical than I expected.
I want to know how other lang wikimedians think that Japanese wiki(pedia) uses English word "Wikipedia" as its sitename and Project namespace prefix.
Is it acceptable (if jawp users want)? Do we need to change it into Japanese word? Or don't need but recommended?
And how about using "ウィキペディア" as sitename of "Wikipedia"?
Some user says "ウィキペディア" is NOT localized or translated term of "Wikipedia" because it's only just [[w:Katakana]]-ized, and we must use other term (e.g. "ウィキ百科" - "ウィキ" is Katakana-ized of "Wiki", and "百科" is [[w:Kanji]] meaning "encyclopedia").
Just for information, NOW we use "ウィキペディア" in left-top logo.
And more, some user says we don't must use "ウィキペディア" or other Japanese terms as Project namespace prefix but must use "Wikipedia", because that situation makes us easy to tell Project pages from other pages.
How about to use different prefix for Project namespace from sitename for such reason?
Please tell me your opinion or WMF policy
http://meta.wikimedia.org/wiki/Improving_Foundation-l hasn't had any edits
in a couple weeks now. Have we decided this isn't such a big problem after
all? Have we given up? Just waiting a few months for someone to post a
complaint so we can repeat this all over again? Austin? Ryan? Anyone?