Hi all,
The Collaboration team is currently working on a variety of
improvements and updates to the Notifications (Echo) extension.[1]
One task is improving how the many different types of notifications
are sorted, into the two fly-out menus. Your feedback would be
especially appreciated here.
TL;DR: Please see this spreadsheet, listing the Current split, and 3
alternative groupings:
https://docs.google.com/spreadsheets/d/1eVQVbzVhhVejEMnVqRBC98weBnfrnZqcGEx…
(or a simplified version, and without the 3rd more complex
"Experimental" grouping, at https://phabricator.wikimedia.org/T123018
)
The team is currently recommending we start off with the "By urgency"
grouping. There is a list of Pros/Cons for each, in the spreadsheet.
Please give us feedback, either at phabricator, or at
https://www.mediawiki.org/wiki/Topic:Sw196pvf5vwt6pku
Detailed information on the goals and background of this task, is
included in both the phabricator and mediawiki.org links.
Much thanks,
Quiddity / Nick
[1] https://www.mediawiki.org/wiki/Notifications#Future_plans_and_requests_for_…
--
Nick Wilson (Quiddity)
Community Liaison
Wikimedia Foundation
Hi,
Here's an interesting video that we didn't get to show on the Developer
Summit.
This is me with my Nexus 5 (Android 6) on 2G in Spain loading
en.m.wikipedia.org/wiki/Barack
Obama
https://www.youtube.com/watch?v=W1w0EcuiUjo
Write your own conclusions, hopefully this will make us think.
If you can set your device from your country to 2G and try it out on an
incognito window (cold cache) and share the results, I would be very
interested to see if your experience is the same as mine.
Cheers,
Joaquin
The Wikimedia Hackathon (Jerusalem, 31 March - 3 April) is approaching and
we are receiving new registrations every day.
Two initiatives are being considered by local members of Wikimedia Levant,
thanks to the proximity of the biggest Wikimedia technical event:
A technical workshop at WikiArabia in Amman (Jordan) on 24-26 March.
https://phabricator.wikimedia.org/T124217
A technical workshop in Ramallah or Birzet (Palestine) one day betweenn
WikiArabia and the Wikimedia Hackathon.
https://phabricator.wikimedia.org/T124721
We are in the earliest stages of planning. People interested, please
subscribe / comment in the tasks.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
I haven't been able to setup the installation for mediawiki-vagrant .
I'm running WAMP stack. Is windows the problem ?
Anyways, I started again from the scratch to avoid any error caused by
myself earlier .Cloned it as ->
ssh://dg7@gerrit.wikimedia.org:29418/mediawiki/vagrant.git
Now ,on vagrant up , it clones the mediawiki as well as other
repositories via https only ,i.e,
https://gerrit.wikimedia.org/r/p/mediawiki/core.git
(
no commit access) .
How should I go about it ?
the log gives the following message at last :
The SSH command responded with
a non-zero exit status ........
The code loads on requesting 127.0.0.1:8080 , The only problem
presently is with this SSH issue .
So, it runs like this with just monobook role enabled .
The screenshot :
https://phab.wmfusercontent.org/file/data/rdduw4p2eua22zs3ed77/
PHID-FILE-sjw6fj5oezch467kkdkh/
3yd57vaes5ncfv3s/Screenshot_%28168%29.png
Now, when I enabled and provisioned for "Flow" role
besides the monobook role, it all broke when I
executed "vagrant reload".
screenshot :
https://phab.wmfusercontent.org/file/data/ae26yakvhhieoizpkday/
PHID-FILE-xpy3pmwv3ejbxsrcntu2/onrit2xyn2mqmp53/
Screenshot_%28169%29.png
log ( provision ) : https://dpaste.de/kO0W
log( reload ) : https://dpaste.de/ePbW
I'm working on this task currently :
https://phabricator.wikimedia.org/T72472
So...
I stopped development on the Persona extension a while ago when Mozilla dropped official support for it, but with persona.org shutting down, I am considering deprecating the extension entirely, especially considering the work that would be required porting it to AuthManager.
But I figured I'd give a sort of last call. Is there anybody here that knows if the extension is being used (despite being marked as experimental) and thinks I should still maintain some sort of support for it?
--
Tyler Romeo
https://parent5446.nyc
0x405D34A7C86B42DF
From: Ryan Kelly <rfkelly(a)mozilla.com>
Reply: dev-identity(a)lists.mozilla.org <dev-identity(a)lists.mozilla.org>
Date: January 11, 2016 at 20:09:31
To: dev-identity(a)lists.mozilla.org <dev-identity(a)lists.mozilla.org>, persona-notices(a)mozilla.org <persona-notices(a)mozilla.org>
Subject: Shutting down persona.org in November 2016
Hi Everyone,
When the Mozilla Identity team transitioned Persona to community
ownership, we committed resources to operational and security support
throughout 2014 [1], and renewed that commitment for 2015 [2]. Due to
low, declining usage, we are reallocating the project’s dedicated,
ongoing resources and will shut down the persona.org services that we run.
Persona.org and related domains will be taken offline on November 30th,
2016.
If you run a website that relies on Persona, you will need to implement
an alternative login solution for your users. We have assembled a wiki
page with additional information and guidelines for migration [3], but
here are the important things you need to know:
Between now and November 30th, 2016, Mozilla will continue to support
the Persona service at a maintenance level:
* Security issues will be resolved in a timely manner and the services
will be kept online, but we do not expect to develop or deploy any
new features.
* Support will continue to be available on the dev-identity mailing
list [4] and in the #services-dev IRC channel [5].
* All websites that rely on persona.org will need to migrate to
another means of authentication during this period.
Beginning on November 30th, 2016, the Persona service hosted by Mozilla
will be decommissioned:
* All services hosted on the persona.org domain will be shut down.
* Mozilla will retain control of the persona.org domain and will
not transfer it to a third party.
* Since the privacy of user data is of utmost importance to Mozilla,
we will destroy all user data stored on the persona.org servers,
and will not transfer it to third parties.
We intentionally designed Persona to expose email addresses rather than
opaque identifiers, which should ease the transition to other systems
that provide verified email addresses. You can find guidelines on
alternative login solutions on the wiki [3] and we will continue to
update them over the coming year. We strongly encourage affected teams
to openly discuss and blog about their migrations on the dev-identity
mailing list so that others can learn from their experience.
Thank you for your support and involvement with Persona. If you have any
questions, please post them to the dev-identity mailing list.
Ryan
[1]
http://identity.mozilla.com/post/78873831485/transitioning-persona-to-commu…
[2] https://groups.google.com/forum/#!topic/mozilla.dev.identity/rPIm7GxOeNU
[3]
https://wiki.mozilla.org/Identity/Persona_Shutdown_Guidelines_for_Reliers
[4] https://lists.mozilla.org/listinfo/dev-identity
[5] http://irc.mozilla.org/#services-dev
_______________________________________________
Persona-notices mailing list
Persona-notices(a)mozilla.org
https://mail.mozilla.org/listinfo/persona-notices
As part of the work of the frontend standards group
https://gerrit.wikimedia.org/r/#/c/260071/ adds require and
module.exports to MediaWiki ResourceLoader. This will make it easier
to share code outside MediaWiki and with nodejs systems as well as
discouraging the overloading of the mediawiki variable.
I'm looking for code review at the moment. If you are familiar with
ResourceLoader's internals I'd appreciate your input.
See https://phabricator.wikimedia.org/T108655 for further background
This is a last call for new arguments and facts related to the
proposal to drop PHP 5.3 and PHP 5.4 support in MediaWiki core git master.
If you have anything new to say about this issue, please comment on
the Phabricator ticket:
https://phabricator.wikimedia.org/T118932
The Architecture Committee plans on making a decision on this issue on
the basis of the Phabricator comments in next week's committee meeting
(January 27).
-- Tim Starling
I was looking through the VisualEditor roadmap (https://www.mediawiki.org/wiki/VisualEditor/Roadmap) and did not notice anything about third-party MediaWiki extensions for the editor. Did I miss it?
I do see plans for "non-Mediawiki" extensions (under "Release for third-party non-MediaWiki users"), and also for Mediawiki admins to
"easily install and use VisualEditor" (under "Release for third-party MediaWiki users"), but nothing about extending it within MediaWiki. For example, adding a button or menu item to insert a particular parser tag.
Is this by design?
I did notice "Non-template transclusions" on the roadmap, which looks like a way to insert parser tags & parser functions if you already know their name (the way template transclusions work right now). That will be a big help. However, for (say) inserting a given parser tag, it would be great if we could easily add a button or menu item for it.
Thank you very much for any info.
DanB
The Wikimedia Foundation has started a consultation about strategic
priorities.
https://meta.wikimedia.org/wiki/2016_Strategy
There is a survey with one question and several possibilities for each of
the main themes: Reach, Community, Knowledge. It is a good chance to
influence the WMF strategy with your individual voice. I really mean it!
Taking the survey took me about 15 minutes and I found the exercise
interesting.
This survey is being promoted across all Wikimedia projects. I'm forwarding
the announcement to this list in order to help assuring that our technical
communities are well represented. Please take the survey, and feel free
forwarding this message to whoever might be interested as well.
---------- Forwarded message ----------
From: Lila Tretikov <lila(a)wikimedia.org>
Date: Tue, Jan 19, 2016 at 2:37 AM
Subject: [Wikimedia-l] Launch of Community Consultation on strategic
approaches
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
Dear Wikimedians,
We are excited to have you participate in an important Community Engagement
regarding our strategic approaches. This is a major step to help us
prioritize the work of the Foundation beginning in July 2016 and running
for the next 12 to 24 months thereafter into a strategic plan.
Throughout 2015 the Foundation has been exploring how to prioritize its
work to best support the movement's goals, set forth, but not yet reached,
in the 2010-15 strategic plan.
The strategic approaches presented here are based on our vision, strategy
consultations in 2010 <https://meta.wikimedia.org/wiki/Strategy/2010-2015>
and 2015
<https://meta.wikimedia.org/wiki/2015_Strategy/Community_consultation>,
research on external impacts, and input from staff and a few small
community think groups on key challenges and potential solutions.
Timeline: These are our target dates for this process.
-
January 11: Put up pages for translation (done)
-
January 18: Launch of community consultation on key questions
-
February 15: Close of consultation
-
By February 26: Release synthesis of consultation
-
By March 4: Publish first draft strategy for comment
We appreciate your time and efforts to help guide the Foundation in its
work to support the movement.
Warm regards,
Lila
_______________________________________________
Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
New messages to: 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
Hi devs/techs,
Is there a wiki page that acts as a first stop or landing page for computer
science students who might be interested in working on coding projects with
Wikipedia/Wikimedia projects?
We have a page on Wikipedia greeting students/instructors who want to do
class projects related to *writing* articles, but do we have a similar
thing for CS instructors and students who might want to do an assignment or
class project with Mediawiki, APIs, or with database dumps?
If anyone could point me to the best of what we have now, that’d be great.
This would be a way to find “shovel ready” challenges for students to work
on, or contribute to projects in progress.
Thanks.
-Andrew