Hoi,
The great thing of personal opinion is that they make great arguments, they
have their point When they are presented well they are compelling..
HOWEVER, we are in the habit of testing many of these arguments.
This is a test that is bound to be interesting to many of us.
Thanks,
GerardM
Assuming that we even use icons! I think a text drop down box which lists
the various networks that one could share onto would work just as well.
On 12 January 2015 at 15:35, MZMcBride z...@mzmcbride.com wrote:
Tim Starling wrote:
Yes, there's a risk we could end up with an alphabetical list
On 12/01/15 16:35, MZMcBride wrote:
What problem are we trying to solve here?
The idea is to increase the number of shares, thus increasing the
number of people who read our content, thus educating more people,
thus better meeting our mission.
If the answer is that we want to make it
Your help pushing these tasks to some direction is welcome:
Share button (tools) in Wikipedia
https://phabricator.wikimedia.org/T29027
enhancement - add social sharing feature after upload
https://phabricator.wikimedia.org/T42456
On Mon, Jan 12, 2015 at 9:45 AM, Gerard Meijssen
Tim Starling wrote:
On 12/01/15 16:35, MZMcBride wrote:
What problem are we trying to solve here?
The idea is to increase the number of shares, thus increasing the
number of people who read our content, thus educating more people,
thus better meeting our mission.
You seem to be drawing a very
On Fri, Jan 9, 2015 at 7:25 PM, Erik Bernhardson ebernhard...@wikimedia.org
wrote:
The Co-op team will ask the Bot Approval Group on enwiki to grant their
bot this right.
*enwiki BAG hat on*
FYI, they'll be asked to advertise the request on enwiki [[WP:VPR]], and
probably [[WP:AN]] wouldn't
Tim, I have to disagree on that.
Imagine a world in which every single human being /can/ freely share
in the sum of all knowledge.
Most social media users can already read Wikipedia (and, I suppose, many
Wikipedia readers cannot use social media because of censorship).
And they almost
On 12/01/15 17:11, Jay Ashworth wrote:
I personally attribute that to we're so small, we have to cave on this point
or no one will know we're here, a problem a small journal might have, but
which Wikipedia certainly does not.
Do you suppose Physical Review (the lumbering giant of physics
Win.
PS. Mantle is in the process of being deprecated (see
https://phabricator.wikimedia.org/T85890) so you will be able to
remove that soon.
On Mon, Jan 12, 2015 at 9:07 AM, Chris McMahon cmcma...@wikimedia.org wrote:
On Mon, Jan 12, 2015 at 9:31 AM, Antoine Musso hashar+...@free.fr wrote:
On 15-01-12 08:47 PM, Maximilian Klein wrote:
So how can I have submit the rebroadcast job to the grid and have the
rebroadcasted websocket be accessed by a static address, so that external
people can read it? What is the best strategy?
I can think of several strategies; part of the difficulty
Hello Wikiwizards,
I have developed an application that reads the RCstream, performs a
filter/augmentation operation[1] and then rebroadcasts the filtered
RCstream.
The problem I am running into on Tools-Labs is that when I submit to the
grid, the rebroadcasting of the filtered websocket stream
In the next RFC meeting we would like to discuss the following RFCs:
* Support for user-specific page lists in core
https://www.mediawiki.org/wiki/Requests_for_comment/Support_for_user-specific_page_lists_in_core
* Guidelines for extracting, publishing and managing libraries
Here's perhaps a new way to think about social media. Let's focus on
one particular aspect of not noise: news.
Twitter is a powerful tool for collecting/spreading real time news.
It also has many disadvantages, as we all know.
We have wikinews and other real-time information sources in our
If the SMW output you're using is emitted within table, it will be
stripped entirely for sure. div has mixed luck, see e.g.
https://fr.wikipedia.org/wiki/Askeptosauroidea
Nemo
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
I am pleased to announce that Corey Floyd joins WMF this week as a
Software Engineer for the Mobile App Team.
Corey is based in Philadelphia where he will be working remotely. He
previously worked as a mobile consultant, during which he developed
iOS apps for organizations like the Human Rights
I am pleased to announce that Brian Gerstle joins WMF this week as a
Software Engineer for the Mobile App Team.
Brian comes to us from Spotify, where he worked as an iOS
developer—with a brief stint as a Quality Engineer. He's really
excited to join the team and contribute to the WMF mission by
Hello,
I have crafted and enabled two new jobs:
* mediawiki-phpunit-hhvm
* mediawiki-phpunit-zend
Which are triggered whenever a patch is proposed to the repos:
mediawiki/core
mediawiki/vendor
Or the mobile related extensions:
Echo
JsonConfig
Mantle
On Mon, Jan 12, 2015 at 2:45 PM, MZMcBride z...@mzmcbride.com wrote:
The question was what problem are we trying to solve. An appeal to the
Wikimedia Foundation vision statement is clever, particularly as it uses
the word share, but Wikipedia currently has more visitors than nearly
every
On Mon, Jan 12, 2015 at 9:31 AM, Antoine Musso hashar+...@free.fr wrote:
Hello,
I have crafted and enabled two new jobs:
* mediawiki-phpunit-hhvm
* mediawiki-phpunit-zend
...
Side effect: if one deprecates a function/method in mediawiki/core and
it is used by one of the extensions
On 12 January 2015 at 08:31, Antoine Musso hashar+...@free.fr wrote:
I have crafted and enabled two new jobs:
* mediawiki-phpunit-hhvm
* mediawiki-phpunit-zend
Which are triggered whenever a patch is proposed to the repos:
mediawiki/core
mediawiki/vendor
Or the mobile related
Welcome to the team!
Dan
On 12 January 2015 at 10:25, Tomasz Finc tf...@wikimedia.org wrote:
I am pleased to announce that Corey Floyd joins WMF this week as a
Software Engineer for the Mobile App Team.
Corey is based in Philadelphia where he will be working remotely. He
previously worked
Welcome to the team!
Dan
On 12 January 2015 at 10:25, Tomasz Finc tf...@wikimedia.org wrote:
I am pleased to announce that Brian Gerstle joins WMF this week as a
Software Engineer for the Mobile App Team.
Brian comes to us from Spotify, where he worked as an iOS
developer—with a brief
22 matches
Mail list logo
