Interesting use of comments related to paragraphs in wiki pages --
functional in MediaWiki and deployed in a top site. I didn't know about
this, it looks very interesting.
---------- Forwarded message ----------
From: *Markus Glaser* <markus.glaser(a)wikimedia.de>
Date: Friday, June 20, 2014
Subject: [Wikimedia-l] Interesting comment system for Wikipedia
To: wikimedia-l(a)lists.wikimedia.org
Hi Micru,
Basically the comments are associated to each paragraph, and a little
> number appears next to it. When clicking it, it displays the comments.
>
There's already a similar implementation for MediaWiki. It's basically a
modification of Extension:Comments and it allows to associate comments with
sections. You can see it live at WebPlatform.org [1].
Best,
Markus
[1] http://docs.webplatform.org/wiki/Main_Page
_______________________________________________
Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
wiki/Mailing_lists/Guidelines
Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
On 06/02/2014 08:16 PM, Steven Walling wrote:
> GuidedTour's backend has also undergone a major refactor, which is close
> to being merged. This is described in full at the commit, which is just
> waiting on us to update logging: https://gerrit.wikimedia.org/r/#/c/116228/
As Steven noted, you should not have to change your code using the old
API immediately. However, we hope you will see a benefit to the new
API, in flexibility, new features, and readability.
We are polishing the API and finishing final testing. The documentation
for the upcoming API is available at
http://growthdoc.wmflabs.org/NonLinearGuidedTourPreview/ (this URL is
temporary), so if you think something could be clarified or tweaked,
please let us know.
The basic idea of the new API is that you start by constructing a
TourBuilder. From that, you construct StepBuilder objects by calling
firstStep (for the entry point)
(http://growthdoc.wmflabs.org/NonLinearGuidedTourPreview/#!/api/mw.guidedTou…)
or step
(http://growthdoc.wmflabs.org/NonLinearGuidedTourPreview/#!/api/mw.guidedTou…)
for other steps.
Steps
(http://growthdoc.wmflabs.org/NonLinearGuidedTourPreview/#!/api/mw.guidedTou…)
can listen for events, which can then trigger a transition to another
step, hide the tour, or end it. This is controlled by .transition()
(http://growthdoc.wmflabs.org/NonLinearGuidedTourPreview/#!/api/mw.guidedTou…).
.next() sets the next step, which can also be dynamic.
The details are covered by the API documentation; I just wanted to give
a broad overview.
The old API is deprecated, and will not be maintained permanently (we
will keep you updated on any plans to remove it).
Matt Flaschen
Hello Flow folk,
Just a quick note to say that now that Zeljko is back from parental leave,
we are proceeding to dismantle the Cloudbees Jenkins jobs that run browser
tests (including for Flow)[1] in favor of jobs on WMF Jenkins. [2]
The tests for Flow on beta labs running in headless Firefox under xvfb are
reliably green as of today[3] and we'll be working to keep them that way.
In the near future you can expect to see WMF Jenkins jobs with Flow tests
running in Chrome and also Flow tests running on our dedicated WMF
SauceLabs account (with which we have 10 simultaneous test VMs, 5X as much
as we had on Cloudbees).
O Brave New World and all that,
-Chris
[1]
https://wmf.ci.cloudbees.com/job/Flow-en.wikipedia.beta.wmflabs.org-linux-f…
[2] https://integration.wikimedia.org/ci/view/BrowserTests/
[3]
https://integration.wikimedia.org/ci/view/BrowserTests/job/browsertests-Flo…
This is an interesting topic about RecentChanges and its many uses and variants. I'm copying Analytics, EE and Research lists because I hope that some of our colleagues from these lists will hop over to Wikimedia-l to participate in this discussion. [a]
In particular I would call my colleagues' attention to this section of Mingli's email:
"Content is only one aspect to observe, people are another:
* Who are the experts on some topics?
* Who are my buddies on some articles?
* Who did help me to improve an article originally I wrote?
In all, we may reshape our technical infrastructure in this direction for
new spaces of participation.
And finally, one open question for the system
designer:
* Towards better content and community, what is the most important things
we want our user to observe?"
I'll just note here some observability work on user contributions that has been done or is in progress.
1. User Analysis Tool [b], similar to the legacy tool by User:X!. Be sure to look at the "Future plans" tab.
2. Listen to Wikipedia [c] visualization tool of recent changes, mostly for aesthetics but there may be ways to adapt some of the ideas or code used here for other interesting purposes.
2. Snuggle [d] which is a tool that helps to identify good-faith and bad-faith new editors.
4. Finding a Collaborator [e] is a current research project, also see [f] a visualization example. As part of this work the researchers seem to have formulated a way of quantifying an editor's impact, although I haven't seen the formula yet. As you probably know the quality of edits and editors is a topic that gets discussed repeatedly.
5. WikiStats [g] which provides high-level statistics about Wikimedia projects.
6. WikiMetrics [h] cohort analysis, has a lot of potential for expanding its tool set.
7. For code and related technical contributions see [i].
8. There are a variety of tools next to users' requests at English Wikipedia's Requests for Permissions page [j] such as WikiChecker [k] and automated edits logs [l].
This is a good discussion and I would be happy to have an office hour meeting for live chat.
Pine
[a] http://lists.wikimedia.org/pipermail/wikimedia-l/2014-June/072507.html
[b] https://tools.wmflabs.org/supercount/index.php
[c] http://listen.hatnote.com/
[d] https://en.wikipedia.org/wiki/Wikipedia:Snuggle
[e] https://meta.wikimedia.org/wiki/Research:Finding_a_Collaborator
[f] https://depts.washington.edu/reflex/
[g] https://stats.wikimedia.org
[h] https://meta.wikimedia.org/wiki/Wikimetrics
[i] http://korma.wmflabs.org/browser/
[j] https://en.wikipedia.org/wiki/Wikipedia:Requests_for_permissions
[k] http://en.wikichecker.com/user/?t=Jimbo%20Wales
[l] https://tools.wmflabs.org/xtools/autoedits/index.php?user=Jimbo%20Wales&lan…
Hi everyone,
For those interested, we've made a number of small design updates to the
guided tours interface. We're also close to merging a major backend
refactoring to support more sophisticated tour behavior, like waiting to
suggest that the user click Save until after they type in VisualEditor.
For the sake of not cross-posting, I'll link you to the full list of
changes I posted to your technical outreach mailing list:
http://lists.wikimedia.org/pipermail/wikitech-ambassadors/2014-June/000717.…
Thanks,
--
Steven Walling,
Product Manager
https://wikimediafoundation.org/