> you can't have volunteer resources run the video
> equipment for you. You need a professional crew.
Is there a more specific description of the specific authority,
wording, and legislative intent for this, please?
Dear all,
it's my pleasure to inform you that the call for paper for OpenSym 2018
is available.
Conference Website and call for papers: http://opensym.org
Papers are due by March 15, 23h59 (any time on Earth).
Submission: https://easychair.org/conferences/?conf=opensym2018
(accepted rate in 2017: 45%)
Topics: The conference provides peer-reviewed research tracks on
subjects related to open collaboration including:
- Open Collaboration Research, esp. Wikis and Social Media
- Free/Libre and Open Source Software (FLOSS)
- Open Data, Open Access, and Open Science
- Open Education
- IT-Driven Open Innovation
- Open Policy/Open Government/Open Law
- Wikipedia and Wikimedia Research
Looking forward to seeing your paper's presentation in Paris
Nicolas Jullien, general chair of OpenSym 2018
About the Conference
--------------------
OpenSym is the only conference that brings together the different
strands of open collaboration research and practice, seeking to create
synergies and inspire new collaborations between people from computer
science, information science, social science, humanities, and everyone
interested in understanding open collaboration and how it is changing
our society.
This year’s conference will be held in Paris, France on August 22-24,
2018. A Doctoral Symposium will take place on August 21, 2018.
OpenSym is held in-cooperation with ACM SIGWEB and ACM SIGSOFT and the
conference proceedings will be archived in the ACM digital library like
all prior editions.
Submission Information and Instructions
---------------------------------------
Topics: The conference provides peer-reviewed research tracks on
subjects related to open collaboration including:
- Open Collaboration Research, esp. Wikis and Social Media
- Free/Libre and Open Source Software (FLOSS)
- Open Data, Open Access, and Open Science
- Open Education
- IT-Driven Open Innovation
- Open Policy/Open Government/Open Law
- Wikipedia and Wikimedia Research
Paper Presentation: OpenSym 2018 will be organized as a one track
conference in order to emphasize the interdisciplinary character of this
conference and to encourage discussion.
Submission Deadline: The research paper submission deadline is March
15th 2018. Submitted papers should present integrative reviews or
original reports of substantive new work: theoretical, empirical, and/or
in the design, development and/or deployment of novel concepts, systems,
and mechanisms. Research papers will be reviewed to meet rigorous
academic standards of publication. Papers will be reviewed for
relevance, conceptual quality, innovation and clarity of presentation.
All the submissions are done via the EasyChair platform, here:
https://easychair.org/conferences/?conf=opensym2018
Paper Length: There is no minimum or maximum length for submitted
papers. Rather, reviewers will be instructed to weigh the contribution
of a paper relative to its length. Papers should report research
thoroughly but succinctly: brevity is a virtue. A typical length of a
“long research paper” is 10 pages (formerly the maximum length limit and
the limit on OpenSym tracks), but may be shorter if the contribution can
be described and supported in fewer pages—shorter, more focused papers
(called “short research papers” previously) are encouraged and will be
reviewed like any other paper. While we will review papers longer than
10 pages, the contribution must warrant the extra length. Reviewers will
be instructed to reject papers whose length is incommensurate with the
size of their contribution. Papers should be formatted in ACM SIGCHI
paper format. Reviewing is not double-blind so manuscripts do not need
to be anonymized.
Posters: As in previous years, OpenSym will also be hosting a poster
session at the conference. To propose a poster, authors should submit an
extended abstract (not more than 4 pages) describing the content of the
poster which will be published in a non-archival companion proceedings
to the conference. Posters should use the ACM SIGCHI templates for
extended abstracts. An example of a poster abstract can be found here.
Reviewing is not double-blind so abstracts do not need to be anonymized.
Paper Proceedings: OpenSym is held in-cooperation with ACM SIGWEB and
ACM SIGSOFT and the conference proceedings will be archived in the ACM
digital library like all prior editions. OpenSym seeks to accommodate
the needs of the different research disciplines it draws on including
disciplines with archival conference proceedings and disciplines where
authors usually present at conferences and publish later. Authors, whose
submitted papers have been accepted for presentation at the conference
have a choice of:
having their paper become part of the official proceedings, archived in
the ACM Digital Library,
having their paper published in the conference website only, with no
transfer of copyright from the authors,
having no publication record at all but only the presentation at the
conference.
Response from authors: For the second time at OpenSym, authors will be
given the opportunity to write a response to their reviews before final
decisions are made. This should be treated as an opportunity to correct
any mistakes or misconceptions in the reviews as well as to propose
minor changes that the authors can make during the two weeks between
notification and the camera-ready deadline.
Important Dates
Submission deadline: March 15, 2018
Reviews sent to authors: May 11, 2018
Response to reviews from authors due: May 20, 2018
Final decision notification: June 15, 2018
Camera-ready papers due: June 22, 2018
Papers available online: July 13, 2018
Conference Organization
The general chairs of the conference are Nicolas Jullien and Olivier
Berger, IMT, France. Feel free to contact us with any questions you
might have at info(a)opensym.org.
--
Maître de Conférences (HDR) / Associate Professor.
https://nicolasjullien.wp.mines-telecom.fr/
Directeur de M@rsouin http://www.marsouin.org
Membre du LEGO http://labo-lego.fr
Responsable du M2 management innovation
parcours Mgt du SI et des données @ischool IMT Atlantique
https://innovationmanagement.wp.imt.fr/
--
Maître de Conférences (HDR) / Associate Professor.
https://nicolasjullien.wp.mines-telecom.fr/
Directeur de M@rsouin http://www.marsouin.org
Membre du LEGO http://labo-lego.fr
Responsable du M2 management innovation
parcours Mgt du SI et des données @ischool IMT Atlantique
https://innovationmanagement.wp.imt.fr/
Resending the email below, as it does not have seem to have made to the
inboxes of several recipients - including myself - even though it is recorded
in the list's archives
<https://lists.wikimedia.org/pipermail/wiki-research-l/2018-January/date.html>
.
---
From: masssly at ymail.com
Subject: [Wiki-research-l] Upcoming research newsletter: new papers open
for review
Date: Fri Jan 19 20:12:18 UTC 2018
Hi everyone,
We’re preparing for the January 2018 research newsletter and looking for
contributors. Please take a look at:
https://etherpad.wikimedia.org/p/WRN201801 and add your name next to any
paper you are interested in covering. Our target publication date is on
January 26 UTC. As usual, short notes and one-paragraph reviews are most
welcome.
Highlights from this month:
• Can conference papers have information value through Wikipedia? An
investigation of four engineering fields
• Collaborative Approach to Developing a Multilingual Ontology: A Case
Study of Wikidata
• Determining Quality of Articles in Polish Wikipedia Based on Linguistic
Features
• Emo, Love, and God: Making Sense of Urban Dictionary, a Crowd-Sourced
Online Dictionary
• Fostering Public Good Contributions with Symbolic Awards: A Large-Scale
Natural Field Experiment at Wikipedia
• Knowledge categorization affects popularity and quality of Wikipedia
articles
• The Conceptual Correspondence between the Encyclopaedia and Wikipedia
• The Wisdom of Polarized Crowds
• Use of Louisiana's Digital Cultural Heritage by Wikipedians
• What Makes Wikipedia's Volunteer Editors Volunteer?
• Wikipedia-integrated publishing: a comparison of successful models
If you have any question about the format or process feel free to get in
touch off-list.
Masssly, Tilman Bayer and Dario Taraborelli
[1] http://meta.wikimedia.org/wiki/Research:Newsletter
--
Tilman Bayer
Senior Analyst
Wikimedia Foundation
IRC (Freenode): HaeB
Cross-post.
---------- Forwarded message ----------
From: Adam Baso <abaso(a)wikimedia.org>
Date: Thu, Jan 18, 2018 at 6:38 AM
Subject: [Input requested] Knowledge as a Service at the Wikimedia
Developer Summit 2018
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Howdy Wikitechnorati,
(And thank you for patience with me cross-posting if you're on other lists.)
I'm writing to invite your input on the following Phabricator task ahead of
next week's Wikimedia Developer Summit 2018 [1] session.
Knowledge as a Service
https://phabricator.wikimedia.org/T183315
The purpose [2] of the Wikimedia Developer Summit 2018 sessions is to
provide guidance for Phase 2 of the Movement Strategic Direction [3] on
buildout of technology capabilities. We'd really love your thoughts to help
set context for our session next week, as Knowledge as a Service is a
primary consideration in the Movement Strategic Direction.
What is Knowledge as a Service? Its essence is about information
architecture approaches and the necessary software that will ultimately
allow content consumption and creation to radiate to new and different
types of interfaces and devices in addition to browser-based approaches. As
you review position papers from attendees [4] you'll notice that the way
they (myself included) think about best solving this is through a heavy
emphasis on technology that makes it easier to better structure information
and its metadata for re-use, remixing, and querying.
What might this mean? Does it mean we should build Wikimedia software in an
API- and metadata-first manner following industry standards compatible with
content structuration? Does it mean weaving our existing structured and
semi-structured data technologies together? How do we build technology that
can ensure successful collaboration between communities on increasingly
structured and interdependent information sources? And how can we ensure
the tech will bolster growth of multilingual and multimedia content
creation and consumption?
I've copied some of the essential material from the Movement Strategic
Direction concerning Knowledge as a Service so you have it here. We would
appreciate your input and hope you will subscribe to the Phabricator task
to contribute and follow along as we explore this topic.
https://phabricator.wikimedia.org/T183315
The following content is copied from https://meta.wikimedia.org/
wiki/Strategy/Wikimedia_movement/2017/Direction :
Knowledge as a service: To serve our users, we will become a platform that
serves open knowledge to the world across interfaces and communities. We
will build tools for allies and partners to organize and exchange free
knowledge beyond Wikimedia. Our infrastructure will enable us and others to
collect and use different forms of free, trusted knowledge.
...
As technology spreads through every aspect of our lives, Wikimedia's
infrastructure needs to be able to communicate easily with other connected
systems.
...
As a platform, we need to transform our structures to support new formats,
new interfaces, and new types of knowledge. We have a strategic opportunity
to go further and offer this platform as a service to other institutions,
beyond Wikimedia. In a world that is becoming more and more connected,
building the infrastructure for knowledge gives others a vested interest in
our success. It is how we ensure our place in the larger network of
knowledge, and become an essential part of it. As a service to users, we
need to build the platform for knowledge or, in jargon, provide knowledge
as a service.
...
Knowledge as a service: A platform that serves open knowledge to the world
across interfaces and communities
Our openness will ensure that our decisions are fair, that we are
accountable to one another, and that we act in the public interest. Our
systems will follow the evolution of technology. We will transform our
platform to work across digital formats, devices, and interfaces. The
distributed structure of our network will help us adapt to local contexts.
...
We will build tools for allies and partners to organize and exchange free
knowledge beyond Wikimedia.
We will continue to build the infrastructure for free knowledge for our
communities. We will go further by offering it as a service to others in
the network of knowledge. We will continue to build the partnerships that
enable us to develop knowledge we can't create ourselves.
...
Our infrastructure will enable us and others to collect and use different
forms of free, trusted knowledge.
We will build the technical infrastructures that enable us to collect free
knowledge in all forms and languages. We will use our position as a leader
in the ecosystem of knowledge to advance our ideals of freedom and
fairness. We will build the technical structures and the social agreements
that enable us to trust the new knowledge we compile. We will focus on
highly structured information to facilitate its exchange and reuse in
multiple contexts.
Thank you.
-Adam
[1] https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2018
[2] https://www.mediawiki.org/wiki/Wikimedia_Developer_
Summit/2018/Purpose_and_Results
[3] https://meta.wikimedia.org/wiki/Strategy/Wikimedia_
movement/2017/Direction
[4] https://wikifarm.wmflabs.org/devsummit/index.php/Session:10
Forwarding a reply from Joseph that somehow didn't go through.
---------- Forwarded message ----------
From: Joseph Allemandou <jallemandou(a)wikimedia.org>
To: Research into Wikimedia content and communities <wiki-research-l@lists.
wikimedia.org>, gerard.meijssen(a)gmail.com
Hi Gerard,
Here are my two cents on your questions.
About redlinks, you are correct in saying that the 3% of "other" link-type
are jumps from a page to another (using http-referer), while the hyperlink
from the origin to the target allowing for such a jump doesn't exist in the
origin page at the moment of computation.
>From my exploration of the dataset, such "other" links happen with the
"manually-edited-with-error" url class (the "-" article has a lot of such
entering links for instance), as well as with links that I think have been
edited in the origin page (for instance in November 2017 dataset, there are
"other" links from page "Kevin Spacey" to "Dan Savage",
"hebephilia","pedophilia or "Harvey_Weinstein" - Those links are confirmed
as existing at some point in the page in November, but not anymore at the
beginning of December when the pages hyperlinks are snapshot).
As for your question about what people are looking for and don't find, the
one way I can think of to get ideas is to use detailed session analysis
correlated with search results, in order to try to get a signal of pages
reached from search and not being visited for long. Even if I think we have
data we could use in that respect on the cluster, we can't publish such
details externally for privacy concerns, obviously.
Please let me know if what I say makes sense :)
Many thanks
Joseph Allemandou
> Hoi,
> Do I understand well that the 3% of "other" links are the ones that have
> articles at *this *time but they did not exist at the time of the dump. So
> in effect they are not red links?
>
> Is there any way to find the articles people were seeking but could not
> find??
> Thanks,
> GerardM
>
> On 16 January 2018 at 20:21, Leila Zia <leila(a)wikimedia.org> wrote:
>
> > Hi all,
> >
> > For archive happiness:
> >
> > Clickstream dataset is now being generated on a monthly basis for 5
> > Wikipedia languages (English, Russian, German, Spanish, and Japanese).
> You
> > can access the data at https://dumps.wikimedia.org/other/clickstream/
> and
> > read more about the release and those who contributed to it at
> > https://blog.wikimedia.org/2018/01/16/wikipedia-rabbit-hole-clickstream/
> >
> > Best,
> > Leila
> >
>
Hoi,
I am a big fan of suggesting people to write articles / do work that will
be read, will be used. In a blogpost [1], I suggest the accumulation of
these click streams and use the missing popular articles as suggestions for
new articles. Articles that people seek and are truly missing are also
obvious candidates as suggestions for new articles.
My question: how hard is it to do this accumulation and analysis for
missing new articles and, combine it with suggestions to authors to write
something that is likely to prove popular? Does this idea have merit?
Thanks,
GerardM
[1]
https://ultimategerardm.blogspot.nl/2018/01/wikipedia-entering-rabbit-hole.…
On 18 January 2018 at 21:37, Joseph Allemandou <jallemandou(a)wikimedia.org>
wrote:
> Hi Gerard,
> Here are my two cents on your questions.
>
> About redlinks, you are correct in saying that the 3% of "other" link-type
> are jumps from a page to another (using http-referer), while the hyperlink
> from the origin to the target allowing for such a jump doesn't exist in the
> origin page at the moment of computation.
> From my exploration of the dataset, such "other" links happen with the
> "manually-edited-with-error" url class (the "-" article has a lot of such
> entering links for instance), as well as with links that I think have been
> edited in the origin page (for instance in November 2017 dataset, there are
> "other" links from page "Kevin Spacey" to "Dan Savage",
> "hebephilia","pedophilia or "Harvey_Weinstein" - Those links are confirmed
> as existing at some point in the page in November, but not anymore at the
> beginning of December when the pages hyperlinks are snapshot).
>
> As for your question about what people are looking for and don't find, the
> one way I can think of to get ideas is to use detailed session analysis
> correlated with search results, in order to try to get a signal of pages
> reached from search and not being visited for long. Even if I think we have
> data we could use in that respect on the cluster, we can't publish such
> details externally for privacy concerns, obviously.
>
> Please let me know if what I say makes sense :)
> Many thanks
> Joseph Allemandou
>
>
>> Hoi,
>> Do I understand well that the 3% of "other" links are the ones that have
>> articles at *this *time but they did not exist at the time of the dump. So
>>
>> in effect they are not red links?
>>
>> Is there any way to find the articles people were seeking but could not
>> find??
>> Thanks,
>> GerardM
>>
>> On 16 January 2018 at 20:21, Leila Zia <leila(a)wikimedia.org> wrote:
>>
>> > Hi all,
>> >
>> > For archive happiness:
>> >
>> > Clickstream dataset is now being generated on a monthly basis for 5
>> > Wikipedia languages (English, Russian, German, Spanish, and Japanese).
>> You
>> > can access the data at https://dumps.wikimedia.org/other/clickstream/
>> and
>> > read more about the release and those who contributed to it at
>> > https://blog.wikimedia.org/2018/01/16/wikipedia-rabbit-hole-
>> clickstream/
>> >
>> > Best,
>> > Leila
>> >
>> >
>> >
>> > --
>> > Leila Zia
>> > Senior Research Scientist
>> > Wikimedia Foundation
>> >
>> > On Tue, Feb 17, 2015 at 11:00 AM, Dario Taraborelli <
>> > dtaraborelli(a)wikimedia.org> wrote:
>> >
>> > > We’re glad to announce the release of an aggregate clickstream dataset
>> > > extracted from English Wikipedia
>> > >
>> > > http://dx.doi.org/10.6084/m9.figshare.1305770
>> > >
>> > > This dataset contains counts of *(referer, article) *pairs aggregated
>> > > from the HTTP request logs of English Wikipedia. This snapshot
>> captures
>> > 22
>> > > million *(referer, article)* pairs from a total of 4 billion requests
>> > > collected during the month of January 2015.
>> > >
>> > > This data can be used for various purposes:
>> > > • determining the most frequent links people click on for a given
>> article
>> > > • determining the most common links people followed to an article
>> > > • determining how much of the total traffic to an article clicked on a
>> > > link in that article
>> > > • generating a Markov chain over English Wikipedia
>> > >
>> > > We created a page on Meta for feedback and discussion about this
>> release:
>> > > https://meta.wikimedia.org/wiki/Research_talk:Wikipedia_clickstream
>> > >
>> > > Ellery and Dario
>> > >
>> > > _______________________________________________
>> > > Analytics mailing list
>> > > Analytics(a)lists.wikimedia.org
>> > > https://lists.wikimedia.org/mailman/listinfo/analytics
>> > >
>> > >
>> > _______________________________________________
>> > Wiki-research-l mailing list
>> > Wiki-research-l(a)lists.wikimedia.org
>> > https://lists.wikimedia.org/mailman/listinfo/wiki-research-l
>> >
>> _______________________________________________
>> Wiki-research-l mailing list
>> Wiki-research-l(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wiki-research-l
>>
>>
>>
>> --
>>
>> *Dario Taraborelli *Director, Head of Research, Wikimedia Foundation
>> wikimediafoundation.org • nitens.org • @readermeter
>> <http://twitter.com/readermeter>
>>
>
>
>
> --
> *Joseph Allemandou*
> Data Engineer @ Wikimedia Foundation
> IRC: joal
>
Hi everyone,
We’re preparing for the January 2018 research newsletter and looking for contributors. Please take a look at: https://etherpad.wikimedia.org/p/WRN201801 and add your name next to any paper you are interested in covering. Our target publication date is on January 26 UTC. As usual, short notes and one-paragraph reviews are most welcome.
Highlights from this month:
• Can conference papers have information value through Wikipedia? An investigation of four engineering fields
• Collaborative Approach to Developing a Multilingual Ontology: A Case Study of Wikidata
• Determining Quality of Articles in Polish Wikipedia Based on Linguistic Features
• Emo, Love, and God: Making Sense of Urban Dictionary, a Crowd-Sourced Online Dictionary
• Fostering Public Good Contributions with Symbolic Awards: A Large-Scale Natural Field Experiment at Wikipedia
• Knowledge categorization affects popularity and quality of Wikipedia articles
• The Conceptual Correspondence between the Encyclopaedia and Wikipedia
• The Wisdom of Polarized Crowds
• Use of Louisiana's Digital Cultural Heritage by Wikipedians
• What Makes Wikipedia's Volunteer Editors Volunteer?
• Wikipedia-integrated publishing: a comparison of successful models
If you have any question about the format or process feel free to get in touch off-list.
Masssly, Tilman Bayer and Dario Taraborelli
[1] http://meta.wikimedia.org/ wiki/Research:Newsletter
Hi everyone,
We’re preparing for the January 2018 research newsletter and looking for contributors. Please take a look at: https://etherpad.wikimedia.org/p/WRN201801 and add your name next to any paper you are interested in covering. Our target publication date is on January 26 UTC. As usual, short notes and one-paragraph reviews are most welcome.
Highlights from this month:
• Can conference papers have information value through Wikipedia? An investigation of four engineering fields
• Collaborative Approach to Developing a Multilingual Ontology: A Case Study of Wikidata
• Determining Quality of Articles in Polish Wikipedia Based on Linguistic Features
• Emo, Love, and God: Making Sense of Urban Dictionary, a Crowd-Sourced Online Dictionary
• Fostering Public Good Contributions with Symbolic Awards: A Large-Scale Natural Field Experiment at Wikipedia
• Knowledge categorization affects popularity and quality of Wikipedia articles
• The Conceptual Correspondence between the Encyclopaedia and Wikipedia
• The Wisdom of Polarized Crowds
• Use of Louisiana's Digital Cultural Heritage by Wikipedians
• What Makes Wikipedia's Volunteer Editors Volunteer?
• Wikipedia-integrated publishing: a comparison of successful models
If you have any question about the format or process feel free to get in touch off-list.
Masssly, Tilman Bayer and Dario Taraborelli
[1] http://meta.wikimedia.org/ wiki/Research:Newsletter
Hi everyone,
We’re preparing for the January 2018 research newsletter and looking for contributors. Please take a look at: https://etherpad.wikimedia.org/p/WRN201801 and add your name next to any paper you are interested in covering. Our target publication date is on January 26 UTC. As usual, short notes and one-paragraph reviews are most welcome.
Highlights from this month:
• Can conference papers have information value through Wikipedia? An investigation of four engineering fields
• Collaborative Approach to Developing a Multilingual Ontology: A Case Study of Wikidata
• Determining Quality of Articles in Polish Wikipedia Based on Linguistic Features
• Emo, Love, and God: Making Sense of Urban Dictionary, a Crowd-Sourced Online Dictionary
• Fostering Public Good Contributions with Symbolic Awards: A Large-Scale Natural Field Experiment at Wikipedia
• Knowledge categorization affects popularity and quality of Wikipedia articles
• The Conceptual Correspondence between the Encyclopaedia and Wikipedia
• The Wisdom of Polarized Crowds
• Use of Louisiana's Digital Cultural Heritage by Wikipedians
• What Makes Wikipedia's Volunteer Editors Volunteer?
• Wikipedia-integrated publishing: a comparison of successful models
If you have any question about the format or process feel free to get in touch off-list.
Masssly, Tilman Bayer and Dario Taraborelli
[1] http://meta.wikimedia.org/ wiki/Research:Newsletter
At the Dev Summit, Birgit Müller and I will run a session on Growing the
MediaWiki Technical Community. If you're attending, we hope you will
consider joining us.
Everyone (attending the Dev Summit or not) is welcome and encouraged to
participate at https://phabricator.wikimedia.org/T183318 (please comment
there, rather than by email).
We are discussing the following questions:
* What would allow you to develop and plan your software more efficiently?
* What would make software development more fun for you?
* What other Open Source communities do we share interests with?
* How can we change our processes to take technical debt more seriously?
"Develop" means any kind of work on a software system, including design,
documentation, etc.
Our topics are:
* Better processes and project management practices, integrating all
developers and allowing them to work more efficiently
* Building partnerships with other Open Source communities on shared
interests (e.g. translation, audio, video)
* Reducing technical debt
Matt Flaschen