Hi all,
I am Manimaran(https://manimaran96.WordPress.com), Free Software Activist
and Android Developer. I developing the app called Spell4Wiki.
*Spell4Wiki - Spell For Wiki*
Spell4Wiki is an mobile application to record and upload audio to wiki
commons for Wiktionary words.Spell4Wiki also act as dictionary. Words
meanings are come from Wiktionary.
*Useful Links*
Source code : https://github.com/manimaran96/Spell4Wiki
APK :
https://github.com/manimaran96/Spell4Wiki/releases/download/devapp_v5/spell…
Workflow :
https://manimaran96.files.wordpress.com/2020/02/spell4wiki_workflow-1.png
Blog :
https://manimaran96.wordpress.com/2019/01/06/spell4wiki-mobile-app-to-recor…
<https://manimaran96.wordpress.com/2020/02/21/spell4wiki-mobile-app-to-recor…>
https://manimaran96.wordpress.com/2020/02/21/spell4wiki-mobile-app-to-recor…
While developing I struggled in some places(listed below). If anyone have
idea about this please help me...
*Problems*
1. While uploading audio some times I got a message “Invalid CSRF”.
2. Once successfully uploaded audio not reflected to UN-Audio words API
<https://ta.wiktionary.org/w/api.php?action=query&format=json&list=categorym…>
and
Word’s Wiktionary page.
Problem : 1Reason I found
1. I think this comes may be session time out or expire or wrong CSRF
token.
2. Once app close session expired
What I tried
1. I am saving first CSRF token after login. Then after every edit
request use same CSRF token -> Not worked.
2. Every time getting new CSRF token for every edit request -> Not
worked.
3. I managed the cookies using android-lib
<https://github.com/franmontiel/PersistentCookieJar> -> Not worked.
Questions
1. How to solve this?
2. Possible to extend login expire time?
3. Which header/cookie is important for every edit request?
Problem : 2
Reason I found
1. I think Wikipedia refresh the UN-Audio word list and Wiktionary word
page after specific period of time.
What I tried
1. Once user uploaded audio of particular word. Then that word stored in
local DB and not showing next time to user -> Not suit for global use.
2. After audio upload edit(Just append text “” empty) the particular
word’s page in Wiktionary
1. This time updated in Wiktionary page suddenly but Un-Audio API
some times only reflected.
2. Sometime IP blocked due to this type of empty edit.
Questions
1. How to solve this?
2. Empty append text in edit action is good or bad?
3. While uploading audio to commons How to manage conflict works or
duplicate works? Because lot of user may contribute same word.
Some General Doubts
1. Client login or OAuth login - Which one is better?
2. In Which license to release uploaded audio file? Public domain or CC
by zero or any ? and reason?
I hope i explained my needs clearly. If you have any doubts/questions ask
me.
I expect collective answers from who are able to help me, at least convey
whatever you know. Which is help to further develop.
Thanks in advance.
Hi Community Metrics team,
This is your automatic monthly Phabricator statistics mail.
Accounts created in (2020-01): 317
Active Maniphest users (any activity) in (2020-01): 1019
Task authors in (2020-01): 550
Users who have closed tasks in (2020-01): 308
Projects which had at least one task moved from one column to another on
their workboard in (2020-01): 305
Tasks created in (2020-01): 2376
Tasks closed in (2020-01): 2378
Open and stalled tasks in total: 43986
Median age in days of open tasks by priority:
Unbreak now: 8
Needs Triage: 552
High: 952
Normal: 1198
Low: 1692
Lowest: 1712
(How long tasks have been open, not how long they have had that priority)
Active Differential users (any activity) in (2020-01): 14
To see the names of the most active task authors:
* Go to https://wikimedia.biterg.io/
* Choose "Phabricator > Overview" from the top bar
* Adjust the time frame in the upper right corner to your needs
* See the author names in the "Submitters" panel
TODO: Numbers which refer to closed tasks might not be correct, as
described in https://phabricator.wikimedia.org/T1003 .
Yours sincerely,
Fab Rick Aytor
(via community_metrics.sh on phab1001 at Wed 26 Feb 2020 06:05:12 PM UTC)
Hello Everyone,
It's time for Wikimedia Tech Talks 2020 Episode 1! This talk will take
place on *26 February 2020 at 6 PM UTC*.
This month's talk will be in an interview format. You are invited to send
questions ahead of time by replying to this email, or you can ask during Q
& A section of the live talk by asking through IRC or the Youtube
Livestream.
Title: Data and Decision Science at Wikimedia
Speaker: Kate Zimmerman, Head of Product Analytics at Wikimedia
Summary:
How do teams at the Foundation use data to inform decisions?
Sarah R. Rodlund talks with Kate Zimmerman, Head of Product Analytics at
Wikimedia, about what sorts of data her team uses and how insights from
their analysis have shaped product decisions.
Kate Zimmerman holds an MS in Psychology & Behavioral Decision Research
from Carnegie Mellon University and has over 15 years of experience in
quantitative and experimental methods. Before joining Wikimedia, she built
data teams from scratch at ModCloth and SmugMug, evolving their data
capabilities from basic reports to strategic analysis, automated
dashboards, and advanced modeling.
The link to the Youtube Livestream can be found here:
https://www.youtube.com/watch?v=J-CRsiwYM9w
During the live talk, you are invited to join the discussion on IRC at
#wikimedia-office
You can watch past Tech Talks here:
https://www.mediawiki.org/wiki/Tech_talks
If you are interested in giving your own tech talk, you can learn more
here:
https://www.mediawiki.org/wiki/Project:Calendar/How_to_schedule_an_event#Te…
Note: This is a public talk. Feel free to distribute through appropriate
email and social channels!
Many kindnesses,
Sarah R. Rodlund
Technical Writer, Developer Advocacy
srodlund(a)wikimedia.org
Sorry for cross-posting.
---------- Forwarded message ---------
From: Jayanta Nath <jayantanth(a)gmail.com>
Date: Sun, Feb 23, 2020 at 8:48 PM
Subject: [MediaWiki-India] India Hackathon 2020 (IH2020)
To: MediaWiki development in India <mediawiki-india(a)lists.wikimedia.org>
Cc: Discussion list on Indian language projects of Wikimedia. <
wikimediaindia-l(a)lists.wikimedia.org>
Greetings from CIS-A2K,
India Hackathon 2020 (IH2020) will take place on 27 - 29 March 2020. India
Hackathon 2020 will be a 3 (three) days residential hackathon where topics
related to MediaWiki, Toolforge will be taken place. Earlier Mediawiki
Training iterations were conducted in 2015, 2016, 2017, 2018 & 2019. This
year we have a plan for a hackathon.
For more information, you can look at -
https://meta.wikimedia.org/wiki/CIS-A2K/Events/India_Hackathon_2020
If any community members from India, who are interested to join this
hackathon, please fill this form
<https://docs.google.com/forms/d/e/1FAIpQLSdUdY5HhubTIzVdNwkXJVhvsJdeM4q1Q-o…>
.
*The last date of showing interest to participate is 1st March 2020.*
Thanks and Regards,
Jayanta Nath
CIS-A2K
_______________________________________________
MediaWiki-India mailing list
MediaWiki-India(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mediawiki-india
Hello,
I have a question. Is anywhere available list of extensions which don't
have mediawiki/mediawiki-codesniffer?
Best regards,
Zoran Dori
volunteer, Wikimedia Serbia
s: zoranzoki21.github.io e: zorandori4444(a)gmail.com
*Замислите свет у коме свака особа на планети има слободан приступ
целокупном људском знању. То је оно на чему ми радимо.*
Hey all,
TL;DR: `docker-compose up` gets you a Docker environment with which
to develop.
The Engineering Productivity group is happy to announce the
availability of a new, official Docker environment for MediaWiki
core. [0] This is a component of our work on improving developer
productivity, as part of the Wikimedia Foundation's "Platform
Evolution" [1] multi-year priority, looking to support faster, more
reliable technical change for our communities. We've been exploring
options for a year now, and we had a great deal of input,
particularly at the TechConf 2019, where Kosta Harlan worked
closely with us to move this forward. [2]
This new environment has been built for simple experimentation,
development, and testing of proposed changes to MediaWiki core. It
is designed to be particularly simple and easy to use, and intended
particularly to be a good option for newbies, be they testers,
designers, developers, or others who have not yet invested a great
deal of their time in setting up local environments.
We intend for this environment to become the official, supported,
and advertised entry point for small-scale development. If you find
issues, or have suggestions for improvements, we'd love to hear
from you. [3] We will be adjusting various bits of documentation
over time to encourage futher use, but if you find some out-of-date
instructions, please do fix them, or flag for us to do.
We know that there are number of people who need a more complex,
configurable, and powerful development and testing environment,
even up to being a "Wikimedia production-like" state. This is not
that environment; we plan to provide a more configurable and thus
more complex, "heavy-weight" alternative for that use case in the
future. You may wish to follow our work in Phabricator. [4]
Our huge thanks to pioneering volunteer and staff colleagues who
have provided support, testing, and advice, and who have explored
different uses of Vagrant, Docker, and other techniques for
providing better forms of MediaWiki testing, development, and
hosting, which have inspired us on how to best provide this. We
all owe you a great debt. Thank you.
Again, if you have questions, comments, or concerns, please do file
a task so that we can help you! [3]
[0] - https://www.mediawiki.org/wiki/Docker
[1] -
https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Medium-term_plan_2019/…
[2] - https://phabricator.wikimedia.org/T238224
[3] - https://phabricator.wikimedia.org/tag/mediawiki-docker/
[4] - https://phabricator.wikimedia.org/tag/local-charts/
Yours,
--
Brennen Bearnes (he/him)
WMF Release Engineering
Hi all,
We (the Commons app team) are hoping to release a Commons iOS app this
year! :) We have received quite a few requests for it, so we have included
it in our Project Grant proposal:
https://meta.wikimedia.org/wiki/Grants:Project/Commons_app/Commons_app_Andr…
.
Additionally, we are proposing a few new features for the Android app, and
stability/code quality improvements.
If this sounds useful or interesting to you, please do take a look at our
proposal, and endorse it if you see fit. Or if you have any questions or
concerns, please feel free to email me or post in the discussion page.
Thank you so much for all of your encouragement and support. We really
appreciate it!
Best regards,
Josephine / @misaochan (Commons app project lead)
All,
Just a friendly heads-up that the branch point for MediaWiki 1.35.0 is
coming up faster than you expect; we're currently on 1.35.0-wmf.20, and
1.35.0-wmf.7 (in seven weeks' time, *i.e.* on 7 April 2020) will be the
final alpha of 1.35, and thus where I cut REL1_35 ahead of rc.0.[0]
There are a lot of proposed blockers to the 1.35 release currently tagged
on Phabricator[1] (and no doubt some of you have vague plans but don't have
them marked out yet). Please do get them done, or re-assess the timeline
for your work, and don't get caught out!
[0] - https://www.mediawiki.org/wiki/MediaWiki_1.35/Roadmap
[1] - https://phabricator.wikimedia.org/tag/MW-1.35-release
Thanks!
--
*James D. Forrester* (he/him <http://pronoun.is/he> or they/themself
<http://pronoun.is/they/.../themself>)
Wikimedia Foundation <https://wikimediafoundation.org/>
