Forwarding an announcement. For what it's worth, WMF is listed as a sponsor
of the 2019 conference, and multiple conference tracks appear to be
relevant to Wikiverse activities. However, announcements which include
lofty adjectives such as "visionary" often give me pause due to the risk of
over-promising and under-delivering. Your views may vary.
Regards,
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: Jui-Yi Tsai <vincentthunder2011(a)gmail.com>
Date: Tue, Dec 24, 2019 at 2:42 AM
Subject: [AI] The WebConf (WWW 2020) Call for Papers (Demo Track)
To: <ai(a)lists.wikimedia.org>
*The WebConf (WWW) Call for Papers: Demo Track*
April 20-24, 2020
Taipei, Taiwan
https://www2020.thewebconf.org/
*Important Dates*
• Submission deadline: January 06, 2020
• Notification: February 10, 2020
For almost three decades, the Web Conference series has been the premier
venue for researchers, academics, businesses and standards bodies to come
together and discuss latest updates and the future of the Web. The
Demonstration Track of the Web Conference has become an important venue for
sharing cutting-edge and exciting web-based prototype systems with
significant research and development efforts. The Demonstrations Track
allows researchers and practitioners to demonstrate first-hand visionary
systems with innovative features and functionalities in a dedicated
session. Submissions must be based on an implemented and tested system that
pursues one or more innovative ideas in the interest areas of the
conference.
*Topics include (but are not limited to)*
● Health on the Web
● Behavioral analysis and personalization
● Crowdsourcing systems and social media
● Bio-feedback and emotional computation
● New human-computer interfaces
● Internet economics, monetization, and online markets
● Pervasive Web and mobility
● Security, privacy, and trust
● Semantics and knowledge
● Semantic Web, content analysis, and Web mining
● Social networks, social analysis, and computational social science
● Web infrastructure: datacenters, cloud computing, and systems
● User modeling, personalization, and experience
● Mobile, ubiquitous, ambient, and pervasive computation, Web of Things
● Web science, Web search, and Web systems
Demonstrations are encouraged from academic researchers, from industrial
practitioners with prototypes or in-production deployments, as well as from
any W3C-related activities to interact while exploring the latest
techniques for managing web information and knowledge. Software (including
games or learning platforms) and hardware demos will be considered equally,
provided they show innovative use of Web-based techniques. Each submission
must make clear which aspects of the system will be demonstrated, and how.
What exactly will the audience experience? What are the interesting
scenarios to motivate the demonstration? They should strive to state the
significance of the contribution to Web technology or applications. In
other words, submissions should describe the intended audience, point out
the innovative aspects of the system being demonstrated, and explain how
those aspects contribute to the state of the art in the Web and information
technology. Submissions will be peer-reviewed by members of the track
program committee, who will judge the originality, significance, quality,
and clarity of each submission.
*Submission Guidelines*
Demonstration Track submissions must be formatted according to the ACM SIG
Proceedings Template and are limited to four pages (including references
and appendices). It is the authors’ responsibility to ensure that
submissions adhere strictly to the required format. The format cannot be
modified with the objective of squeezing in more material. Submissions that
do not comply with the formatting guidelines will be rejected without
review.
Each demonstration track submission should contain an introduction, brief
description, screenshots, value and contribution. Submissions should also
indicate how the demonstration will be demonstrated and the hardware
requirements (for the organizers).
Submissions must be double-blinded. Submissions must be in PDF and must be
made through the EasyChair system (Demonstrations Track):
https://easychair.org/conferences/?conf=www2020
At least one author of each accepted demonstration paper must register for
the conference and attend in person to demonstrate the system during the
demonstration sessions.
To better identify the value of demonstrations, as well as to reach out to
external audiences, we also encourage authors to submit a pointer to a
screencast, using web-accessible platforms such as Vimeo or YouTube. The
maximum duration of screencasts is 10 minutes. We also highly encourage any
external material related to the demo (e.g., shared code on GitHub).
*Track Co-chairs*
Hsu-Chun Hsiao (National Taiwan University)
De-Nian Yang (Academia Sinica)
Email: demos2020(a)thewebconf.org
_______________________________________________
AI mailing list
AI(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ai
Hello,
last couple of days we've released v0.36.0 & minor follow-up v0.36.1 to
ensure backwards compatibility. We caught the issue before rolling release
out. Version v0.36.1 will roll out on normal train next Tuesday.
Highlights in this release were
- Breaking change: Requiring PHP 7.2.9+, up from 5.6.99/HHVM in alignment
with recent MediaWiki core changes
- Deprecating change: Rename LookupElement's onLookupMenuItemChoose to
onLookupMenuChoose to follow naming scheme listeners – {Emitter}{Event}.
Thanks to Bartosz Dziewoński and Ed Sanders for quickly identifying and
fixing the backwards compatibility issue
- Amending and updating TextInput- and DropdownWidgets paddings minimally
to fully align with Design Style Guide's components templates[0].
You can find details on additional new features, code-level, styling and
interaction design amendments, and all
improvements since v0.35.0 in the full changelog[1].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos[2] and library documentation is available
on mediawiki.org[3], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[4].
OOUI version: 0.36.1
MediaWiki version: 1.35.0-wmf.11
Date of deployment to production: Regular train, starting Tuesday 17
December
[0]- https://design.wikimedia.org/style-guide/components/
[1]-
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
<https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr>
[2]-
https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[3] - https://www.mediawiki.org/wiki/OOUI
[4] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
Regarding Timeless, folks may want to read
https://meta.wikimedia.org/wiki/Grants:Project/Timeless/Post-deployment_sup…
.
I'm cross-posting this thread to the public Design mailing list. That's
usually a quiet list, but I think that if people want to have an extensive
discussion that is focused on design issues then that list would be a good
venue.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
On Sun, Dec 15, 2019 at 8:01 PM Aron Manning <aronmanning5(a)gmail.com> wrote:
> On Sun, 15 Dec 2019 at 18:53, Chris Gates via Wikimedia-l <
> wikimedia-l(a)lists.wikimedia.org> wrote:
>
> > Is this the right time to plug Timeless?
> > It is, well, timeless. Looks modern too.
>
>
> Should be the default imho by now.
> Then the wikimania design features could be added to it, to make it almost
> up-to-date.
>
> Aron
Hey - do you use the design VPS project? It needs to be claimed this month.
---------- Forwarded message ---------
From: Andrew Bogott <abogott(a)wikimedia.org>
Date: Tue, Nov 12, 2019 at 14:18
Subject: Re: [Wikitech-l] Cloud VPS users, please claim your projects to
prevent shut down in December
To: <Cloud-announce(a)lists.wikimedia.org>
CC: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Wikimedia Cloud
Services general discussion and support <cloud(a)lists.wikimedia.org>
Another reminder: please claim your VPS projects. 70 projects are still
unclaimed and will be shut down at the end of the month if they are not
marked. Please visit this URL and mark your projects as used:
https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2019_Purge
The following projects remain unclaimed:
butterfly
cloud-analytics
cloudstore
collection-alt-renderer
community-labs-monitoring
dashiki
design
download
dumps
etcd
etytree
extdist
general-k8s
gerrit
glampipe
globaleducation
grantreview
gratitude
hat-imagescalers
hhvm
hound
huwiki-dev
iiab
incubator
indico
lewton-test
library-card-test
library-upgrader
lta-tracker
math
matrix
mcr-dev
mwoffliner
newsletter
openocr
openrefine
orig
osmit
otrs
packaging
packagist-mirror
partnermetrics
phabricator
planet
qna
queryrapi
reading-web-staging
sentry
services
social-tools
structurednavigation
telnet
test-twemproxy
thumbor
traffic
videowiki
visualeditor
webperf
wikibrain
wikicitevis
wikidata-autodesc
wikidumpparse
wikifactmine
wikilabels
wikimania-support
wikimetrics
wikistream
wikitextexp
wmf-research-tools
wpx
On 9/30/19 11:24 AM, Andrew Bogott wrote:
> Every year or so the Cloud Services team tries to identify and clean
> up unused projects and VMs. We do this via an opt-in process: anyone
> can mark a project as 'in use,' and that project will be preserved for
> another year.
>
> I've created a wiki page the lists all existing projects, here:
>
> https://wikitech.wikimedia.org/wiki/News/Cloud_VPS_2019_Purge
>
> If you are a VPS user, please visit that page and mark any projects
> that you use as {{Used}}. Note that it's not necessary for you to be
> a project admin to mark something -- if you know that you're currently
> using a resource and want to keep using it, go ahead and mark it
> accordingly. If you /are/ a project admin, please take a moment to
> mark which VMs are or aren't used in your projects.
>
> When December arrives, I will shut down and begin the process of
> reclaiming resources from unused projects.
>
> If you think you use a VPS project but aren't sure which, I encourage
> you to poke around on https://tools.wmflabs.org/openstack-browser/ to
> see what looks familiar. Worst case, just email
> cloud(a)lists.wikimedia.org with a description of your use case and
> we'll sort it out there.
>
> Exclusive toolforge users are free to ignore this task.
>
> Thank you!
>
> -Andrew and WMCS team
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
-Toby
Hello,
end of last week saw releases of OOUI v0.35.0 and minor follow-up v0.35.1,
they have rolled-out on normal train this week.
The highlights were
- Using `px` where applicable over `em`s.
For most box sizing properties (min-width, min-height, margin, border,
border-radius, padding, box-shadow, outline) `px` unit is sufficient to
still provide accessible user font preference overrides to scale the text.
Additionally, this change is simplifying and speeding up building
interfaces for designers and developers. See
https://phabricator.wikimedia.org/T220671 for further details. This change
doesn't affect any current interfaces, it should result in no rendering
differences at normal environment settings.
- `infuse-by-id` feature got removed, it has been deprecated since v0.29.7
and has, to our knowledge, only been used internally any more. Use an
HTMLElement or jQuery collection instead. Please verify that you are not
using the feature any more.
You can find details on additional new features, code-level, styling and
interaction design amendments, and all
improvements since v0.34.0 in the full changelog[0].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos[1] and library documentation is available
on mediawiki.org[2], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[3].
OOUI version: 0.35.0
MediaWiki version: 1.35.0-wmf.2
Date of deployment to production: Regular train, starting Tuesday 15 October
[0]-
https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
<https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr>
[1]-
https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[2] - https://www.mediawiki.org/wiki/OOUI
[3] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
--
Senior UX Engineer
Wikimedia Foundation
volker.e(a)wikimedia.org | @Volker_E
Hey folks, I'm helping Rebecca Maung (rmaung(a)wikimedia.org) distribute this
request. Her words below:
The Wikimedia Foundation is asking for your feedback in the annual
Community Insights survey. We want to know how well we are supporting your
work on- and off-wiki, and how we can change or improve things in the
future. The opinions you share will directly affect the current and future
work of the Wikimedia Foundation.
If you are a volunteer developer, and have contributed code to any pieces
of MediaWiki, gadgets, or tools, please complete the survey. It is
available in various languages and will take between 15 and 25 minutes to
complete.
Follow this link to the survey:
https://wikimedia.qualtrics.com/jfe/form/SV_0pSrrkJAKVRXPpj?Target=dev
If you have seen a similar message elsewhere and have already taken the
Community Insights survey, please do not take it twice.
You can find more information about this survey on the project page and see
how your feedback helps the Wikimedia Foundation support contributors like
you. This survey is hosted by a third-party service and governed by this
privacy statement. Please visit our frequently asked questions page to find
more information about this survey.
If you need additional help, send an email to surveys(a)wikimedia.org.
Thank you!
//Johan Jönsson
--
(Note: This is only an early heads-up, to be prepared. Google Code-in
has NOT been announced yet, but last year, GCI mentors asked for more
time in advance to identify tasks to mentor. Here you are. :)
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Google Code-in (GCI) is an annual contest for 13-17 year old students.
GCI 2019 has not yet been announced but usually takes place from late
October to December. It is not only about coding: We also need tasks
about design, docs, outreach/research, QA.
Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors , add
your name to the mentors table, and start tagging tasks in Wikimedia
Phabricator by adding the #gci-2019 project tag.
We will need MANY mentors and MANY tasks, otherwise we cannot make it.
Last year, 199 students successfully worked on 765 tasks supported by
39 mentors. For some achievements from the last round, see
https://wikimediafoundation.org/news/2019/02/20/partnerships-make-it-possib…
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and replace 2 uses of
Linker::link() from the list in T223010" style).
We also have more than 400 unassigned open #good-first-bug tasks:
https://phabricator.wikimedia.org/maniphest/query/3YnDUWYJfXSo/#R
Can and would you mentor some of these tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2019#List_of_Wikimedia_mentors
Thanks (as we will not be able to run this without your help),
andre
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
Hello everyone,
I'm excited to announce that we've released OOUI v0.34.0 today.
Key highlights of this release are (summarizing since v0.33.0):
- Update to OOjs v3.0.0, up from v2.2.2
- Update to jQuery v3.4.1, up from v3.3.1
Both updates above are considered breaking changes. Please carefully
test if they affect your code.
- Element: Implement `#setScrollLeft` and use where needed. Improves
scrolling-related operations in RTL languages
- Frameless buttons are now featuring hover and active state as
standard, improving user navigational experience
- ProcessDialog: Improve secondary action appearance to let users
better focus on content
- WindowManager: Prevent iOS Safari from scrolling the page behind the dialog
You can find details on additional new features, code-level and accessibility
changes, styling and interaction design amendments, and all
improvements since v0.33.0 in the full changelog[1].
If you have any further queries or need help dealing with breaking
changes, please let me know.
As always, interactive demos[0] and library documentation is available
on mediawiki.org[2], there is comprehensive generated code-level
documentation and interactive demos and tutorials hosted on
doc.wikimedia.org[3].
OOUI version: 0.34.0
MediaWiki version: 1.34.0-wmf.22
Date of deployment to production: Regular train, starting Tuesday 10 September
[0] - https://doc.wikimedia.org/oojs-ui/master/demos/#widgets-mediawiki-vector-ltr
[1] - https://phabricator.wikimedia.org/diffusion/GOJU/browse/master/History.md
[2] - https://www.mediawiki.org/wiki/OOUI
[3] - https://doc.wikimedia.org/oojs-ui/master/
Best,
Volker
--
Senior UX Engineer
Wikimedia Foundation
volker.e(a)wikimedia.org | @Volker_E