Earlier this week I had the pleasure of announcing the addition of
Moka Pantages to the Foundation staff. We've been busy with all-staff
meetings, so I haven't had a chance to share this news with you
earlier. Moka will report to me, here at our offices in San
Francisco. She'll be taking on some specific communications projects,
supporting staff on their communications needs, and hopefully leading
some new initiatives with the chapters. You may start seeing her name
on the lists and on the WMF blog as well.
Moka is new to the San Francisco Bay Area, previously living in Seoul,
South Korea where she worked for the Seoul Broadcasting Service as a
Program Manager while completing her MA at Yonsei University. Prior
to her move to Seoul, she lived in Seattle and Austin, Texas while
working with Porter Novelli, a multinational public relations agency
based in New York. Moka is originally from the DC/Metro area where
she graduated from the University of Maryland, and began her career in
communications working at a local NGO, the Black Leadership Council
for Excellence, and as an intern on Capitol Hill with Senator Barbra
Join me in welcoming Moka!
Head of Communications
+1 (415) 839 6885 x 609, @jansonw
Just found out about Free Software Foundation credit card
Similar credit card program for Linux exists since ~ 2001 - 2002
So may be Wikimedia Foundation could be interested in similar program?
Next Thursday's office hours will feature Kul Wadhwa, Wikimedia
Foundation's Head of Business Development. If you don't know Kul, you
can read about him at <http://wikimediafoundation.org/wiki/Kul_Wadhwa>.
Office hours on Thursday are from 1600 to 1700 UTC (9:00 AM - 10:00 AM PDT).
If you do not have an IRC client, there are two ways you can come chat
using a web browser: First is using the Wikizine chat gateway at
<http://chatwikizine.memebot.com/cgi-bin/cgiirc/irc.cgi>. Type a
nickname, select irc.freenode.net from the top menu and
#wikimedia-office from the following menu, then login to join.
Also, you can access Freenode by going to http://webchat.freenode.net/,
typing in the nickname of your choice and choosing wikimedia-office as
the channel. You may be prompted to click through a security warning.
It should be all right.
Please feel free to forward (and translate!) this email to any other
relevant email lists you happen to be on. (Kul is able to speak
English, Japanese and Portuguese with some degree of competancy!)
Volunteer Coordinator, Wikimedia Foundation
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
I am impressed.
Let me remind you of one thing,
most people are working on very small subsets of the data. Very few
people will want to have all the data, think about getting all the
versions from all the git repos, it would be the same.
My idea is for smaller chapters who want to get started easily, or
towns, regions to host their own branches of relevant data.
Given a world full of such servers, the sum would be great but the
individual branches needed at one time would be small.
On Wed, Oct 21, 2009 at 9:49 PM, Bernie Innocenti <bernie(a)codewiz.org> wrote:
> El Wed, 21-10-2009 a las 08:43 -0400, Samuel Klein escribió:
>> That sounds like a great idea. I know a few other people who have
>> worked on git-based wikis and toyed with making them compatible with
>> mediawiki (copying bernie innocenti, one of the most eloquent :).
> Then I'll do my best to sound as eloquent as expected :)
> While I think git's internal structure is wonderfully simple and
> elegant, I'm a little worried about its scalability in the wiki usecase.
> The scenario for which git's repository format was designed is "patch
> oriented" revision control of a filesystem tree. The central object of a
> git tree is the "commit", which represents a set of changes on multiple
> files. I'll disregard all the juicy details on how the changes are
> actually packed together to save disk space, making git's repository
> format amazingly compact.
> Commits are linked to each other in order to represent the history. Git
> can efficiently represent a highly non-linear history with thousands of
> branches, each containing hundreds of thousands revisions. Branching and
> merging huge trees is so fast that one is left wondering if anything has
> happened at all.
> So far, so good. This commit-oriented design is great if you want to
> track the history *the whole tree* at once, applying related changes to
> multiple files atomically. In Git, as well as most other version control
> systems, there's no such thing as a *file* revision! Git manages entire
> trees. Trees are assigned unique revision numbers (in fact, ugly sha-1
> hashes), and can optionally by tagged or branched at will.
> And here's the the catch: the history of individual files is not
> directly represented in a git repository. It is typically scattered
> across thousands of commit objects, with no direct links to help find
> them. If you want to retrieve the log of a file that was changed only 6
> times in the entire history of the Linux kernel, you'd have to dig
> through *all* of the 170K revisions in the "master" branch.
> And it takes some time even if git is blazingly fast:
> bernie@giskard:~/src/kernel/linux-2.6$ time git log --pretty=oneline REPORTING-BUGS | wc -l
> real 0m1.668s
> user 0m1.416s
> sys 0m0.210s
> (my laptop has a low-power CPU. A fast server would be 8-10x faster).
> Now, the English Wikipedia seems to have slightly more than 3M articles,
> with--how many? tenths of millions of revisions for sure. Going through
> them *every time* one needs to consult the history of a file would be
> 100x slower. Tens of seconds. Not acceptable, uh?
> It seems to me that the typical usage pattern of an encyclopedia is to
> change each article individually. Perhaps I'm underestimating the role
> of bots here. Anyway, there's no consistency *requirement* for mass
> changes to be applied atomically throughout all the encyclopedia, right?
> In conclusion, the "tree at a time" design is going to be a performance
> bottleneck for a large wiki, with no useful application. Unless of
> course the concept of changesets was exposed in the UI, which would be
> an interesting idea to explore.
> Mercurial (Hg) seems to have a better repository layout for the "one
> file at a time" access pattern... Unfortunately, it's also much slower
> than git for almost any other purpose, sometimes by an order of
> magnitude. I'm not even sure how well Hg would cope with a repository
> containing 3M files and some 30M revisions. The largest Hg tree I've
> dealt with is the "mozilla central" repo, which is already unbearably
> slow to work with.
> It would be interesting to compare notes with the other DSCM hackers,
> // Bernie Innocenti - http://codewiz.org/
> \X/ Sugar Labs - http://sugarlabs.org/
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo(a)vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
I don't think the social parts are included in the article count, but we
really need to ask someone who has actual experience with these sites. I
think it is clear that these sites fill the same role as Wikipedia in China.
Perhaps they also fill other roles that we intentionally do not, like
gossip, social networking, indiscriminate collection of information...
What I would really want to know is how they deal with vandalism and edit
wars. What I think the demise of the Swedish competitor Susning.nu told us,
is that less strict more hands-off wiki is very popular with writers and
readers, but fails to attract enough administrator types to deal with
I do not read much Chinese, but I have found Baidu Baike and Hudong
interesting. Let me share my impression of how they differ from Wikipedia.
* Like most of the Chinese web, there is little regard for copyrights. Most
of the article text seems to be copied from news articles, the official site
of the subject or various government websites. The images come from anywhere
on the web.
* They encourage rather than avoid the social networking and game-like
aspects of the community. As the CNN article says, there are general
chatrooms, friend functions, points, rankings etc.
* They are not at all strict with sources. We should remember that Wikipedia
became hugely popular before we really got serious about sources, and most
non-English Wikipedias are still mostly unsourced.
* They are generally anarchic. Not towards things the government might
object to, but to things like BLP, and sources. Celebrity articles are full
I am delighted to announce that this week, Pete Forsyth joins
Wikimedia as its first Public Outreach Officer. Pete will support me
in all of the Foundation's public outreach activities, including the
development of educational materials (Bookshelf Project), the
development of public outreach related grant proposals and the
communication of volunteer-led outreach activities to a global
Since January 2006, Pete has been an active Wikimedian, mainly on the
English Wikipedia where he has contributed a number of high-quality
articles. He is a founding member of WikiProject Oregon, and a group
blog (http://wikiprojectoregon.wordpress.com) which allows the
project's contributors to discuss their work with the broader public.
Pete has worked on numerous local political issues, and in that time,
has been a strong representative and advocate for using wikis and
Wikipedia to advance and improve democracy and public policy.
Pete participates in a number of wiki-based communities; these include
Portland non-profits Free Geek and the Bus Project, dreamfish.com, and
AboutUs.org, and the budding portlandwiki.org.
Pete holds a Bachelor's Degree in Philosophy from Reed College in
Portland, Oregon. His post-graduate work experience has ranged from
writing and editing to graphic design and information systems
architecture. He has worked as a political consultant on local and
statewide campaigns, and a communications consultant for businesses,
non-profits, and advocacy organizations.
Before moving to San Francisco, Pete will be working remotely from Portland.
Please join me in warmly welcoming Pete to the Wikimedia Foundation.
This is actually a fantastically cool idea.
---------- Forwarded message ----------
From: Larry Sanger <sanger(a)citizendium.org>
Subject: [SharedKnowing] WatchKnow launches!
I'm delighted to announce that WatchKnow (http://www.watchknow.org/)
is launching today! Dive in!
The new site makes educational videos for kids ridiculously easy to
find. We are launching with over 10,000 videos placed in over 2,000
categories, arranged in a very handy directory. The site is a new
kind of wiki: working together, contributors can edit video
information, and they can also edit the directory by drag and drop,
which will make building the resource truly "wikiwiki"--fast. While
the project is wide open and easy to get involved with (even
anonymously), the project engages teachers to act as community
moderators. It is non-profit and generously supported by an anonymous
donor through the Community Foundation of Northwest Mississippi. See
how to edit the site in this screencast video:
We decided to get the word out on the grassroots level--in other
words, virally--before we do a press release in a couple days (maybe
next week). So please, please, tweet about WatchKnow, blog about it,
talk about it with your friends, etc.--and start working on the site!
This is one Web 2.0 project that really has the potential to change
the world in great ways, so it needs your support. If you love
WatchKnow, say so and spread the word!
Lawrence M. Sanger, Ph.D.
Executive Director, WatchKnow.org
SharedKnowing mailing list
Strategic Planning office hours tomorrow - Tuesdays from 20:00-21:00
UTC, which is: 1-2pm PDT, 4-5pm EDT.
This is one of those rare and fun occasions when Eugene and Philippe
are co-located, so maybe we'll even turn on the skype camera or
something.... no promises, I'm not even sure if Skype works in the new
office yet. :-)
We meet in #wikimedia-strategy on the freenode network. You can
access the chat by going to https://webchat.freenode.net/ and filling
in a username and the channel name (#wikimedia-strategy). You may be
prompted to click through a security warning. It's fine. Another
option is http://chat.wikizine.org.
For more information about IRC clients, go to the Wikipedia entry on
IRC or the Meta page on Wikimedia IRC.
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!