Recent leaks suggest almost all commercial x86 processors have been
compromised by closed-source back doors which enable eavesdropping and DRM
copy protection which in turn inhibits fair use.
On Mon, Mar 13, 2017 at 4:41 PM Lodewijk <lodewijk(a)effeietsanders.org>
wrote:
> Hi Jim,
>
> Could you clarify the relationship with Wikimedia on this? I'm missing the
> link.
>
> Best,
> Lodewijk
>
> 2017-03-13 23:03 GMT+01:00 James Salsman <jsalsman(a)gmail.com>:
>
> > Please join me in asking AMD to open-source the PSP (backdoor) in
> > their chips -- a chance to regain secure x86 hardware.
> >
> > https://www.change.org/p/advanced-micro-devices-amd-
> release-the-source-code-for-the-secure-processor-psp
>
>
Hello,
Next week I will remove Zend PHP 5.3 support from CI entirely. It is
only used for MediaWiki REL1_23 branch which is low traffic.
The reason is CI uses Ubuntu Precise instances that comes with PHP 5.3.
The distribution is end of life (as PHP) and it is being phased out of
the Wikimedia infrastructure.
I will replace the jobs by their equivalent running Zend PHP 5.5 which
would still provide test coverage and linting, albeit with a different
version.
References:
Deprecate precise instances in Labs by 03/31/2017
https://phabricator.wikimedia.org/T143349
Depool precise jenkins instances
https://phabricator.wikimedia.org/T158652
--
Antoine "hashar" Musso
Hi,
I'm Harjot Singh 4th year student pursuing Information technology
Engineering.
I've been part of MediaWiki since May 2015.I enjoy working on open source
technologies and love to contribute.
Phabricator link <https://phabricator.wikimedia.org/p/Harjotsingh/>
I've previously worked as Php developer at Daphnis labs and full stack
intern.I would like the opportunity to work on this MediaWiki project for
Gsoc 2017.
I would like to share my proposal for the project :Proposal Link
<https://phabricator.wikimedia.org/T160257>
I made the proposal early in order to get feedback and suggestions.
Thanks,
Harjot Singh
Apologies for cross-posting
Call for Papers, Posters & Workshops and Tutorials
SEMANTiCS 2017 - The Linked Data Conference
13th International Conference on Semantic Systems
Amsterdam, Netherlands
September 11 -14, 2017
http://2017.semantics.cc
For details please go to: https://2017.semantics.cc/calls
Important Dates (Research & Innovation Track):
*Abstract Submission Deadline: May 17, 2017 (11:59 pm, Hawaii time)
*Paper Submission Deadline: May 24, 2017 (11:59 pm, Hawaii time)
*Notification of Acceptance: July 3, 2017 (11:59 pm, Hawaii time)
*Camera-Ready Paper: August 14, 2017 (11:59 pm,
Hawaii time)
Important Dates (Posters & Demos Track):
*Submission Deadline: July 10, 2017 (11:59 pm, Hawaii time)
*Notification of Acceptance: August 10, 2017 (11:59 pm,
Hawaii time)
*Camera-Ready Paper: August 18, 2017 (11:59 pm, Hawaii time)
Important Dates (Workshops & Tutorials):
*Proposals for Workshops with Call for Papers: March 31, 2017 (23:59
Hawaii Time)
*Proposals for Tutorials and Workshops without Call for Papers: June
30, 2017 (23:59 Hawaii Time)
*Notification of Acceptance: April 13, 2017 (23:59 Hawaii Time)
*Workshop Website/Call for Papers Online: April 30, 2017 (23:59 Hawaii Time)
*Camera-Ready Proceedings: September 4, 2017 (23:59 Hawaii Time)
*SEMANTiCS 2017 Workshop & Tutorial Days: September 11 and 14, 2017
Important Dates (Industry & Use Case Presentations):
*Submission Deadline: June 23, 2017
*Notification of Acceptance: July 4, 2017
*Presentation Ready: August 15, 2017
As in the previous years, SEMANTiCS’17 proceedings will be published by
ACM ICPS (pending) and CEUR WS proceedings.
SEMANTiCS 2017 will especially welcome submissions for the following hot
topics:
*Data Science (special track, see below)
*Web Semantics, Linked (Open) Data & schema.org
*Corporate Knowledge Graphs
*Knowledge Integration and Language Technologies
*Data Quality Management
*Economics of Data, Data Services and Data Ecosystems
Following the success of previous years, the ‘horizontals’ (research)
and ‘verticals’ (industries) below are of interest for the conference:
Horizontals:
*Enterprise Linked Data & Data Integration
*Knowledge Discovery & Intelligent Search
*Business Models, Governance & Data Strategies
*Semantics in Big Data
*Text Analytics
*Data Portals & Knowledge Visualization
*Semantic Information Management
*Document Management & Content Management
*Terminology, Thesaurus & Ontology Management
*Smart Connectivity, Networking & Interlinking
*Smart Data & Semantics in IoT
*Semantics for IT Safety & Security
*Semantic Rules, Policies & Licensing
*Community, Social & Societal Aspects
Data Science Special Track Horizontals:
*Large-Scale Data Processing (stream processing, handling large-scale
graphs)
*Data Analytics (Machine Learning, Predictive Analytics, Network Analytics)
*Communicating Data (Data Visualization, UX & Interaction Design,
Crowdsourcing)
*Cross-cutting Issues (Ethics, Privacy, Security, Provenance)
Verticals:
*Industry & Engineering
*Life Sciences & Health Care
*Public Administration
*e-Science
*Digital Humanities
*Galleries, Libraries, Archives & Museums (GLAM)
*Education & eLearning
*Media & Data Journalism
*Publishing, Marketing & Advertising
*Tourism & Recreation
*Financial & Insurance Industry
*Telecommunication & Mobile Services
*Sustainable Development: Climate, Water, Air, Ecology
*Energy, Smart Homes & Smart Grids
*Food, Agriculture & Farming
*Safety, Security & Privacy
*Transport, Environment & Geospatial
FYI
----- Forwarded message from Željko Filipin <zfilipin(a)wikimedia.org> -----
> Date: Fri, 10 Mar 2017 15:22:33 +0100
> From: Željko Filipin <zfilipin(a)wikimedia.org>
> To: "Software quality assurance for Wikimedia projects." <qa(a)lists.wikimedia.org>
> Subject: [QA] Ruby tests updated to Selenium 3
> Reply-To: "QA for Wikimedia projects." <qa(a)lists.wikimedia.org>
>
> The majority of migration was without problems. Three repositories still
> need to be updated because some tests are failing: MobileFrontend,
> RelatedArticles, Wikibase.
>
> This task has all details:
>
> https://phabricator.wikimedia.org/T158074
>
> mediawiki_selenium 1.8.0 release notes document changes.
>
> https://phabricator.wikimedia.org/diffusion/MSEL/browse/master/RELEASES.md
>
> If you have any questions, or you need help upgrading, let me know.
>
> Željko
> _______________________________________________
> QA mailing list
> QA(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/qa
----- End forwarded message -----
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| Release Team Manager A18D 1138 8E47 FAC8 1C7D |
Anna (our current intern through Outreachy) and I are organizing an
information session around GSOC 2017/Outreachy Round 14 for prospective
Wikimedia students on March 14th, 9:00 am PST via YouTube Live.
So far 80 people have signed up for attending this session.
We are looking for 1-2 mentors who are already familiar w/ these programs
to participate and bring their perspective to the discussion.
If you are interested, reply to this email, or ping us here on Phabricator
<https://phabricator.wikimedia.org/T160010>.
Thank you!
--
Srishti Sethi
Developer Advocate
Technical Collaboration team
Wikimedia Foundation
<goog_1898109739>
https://www.mediawiki.org/wiki/User:SSethi_(WMF)
I've got an early draft of some notes
<https://www.mediawiki.org/wiki/User:Brion_VIBBER/Compacting_the_revision_ta…>
for a restructuring of the revision table, to support the following:
* making the revision table itself smaller by breaking large things out
* reducing duplicate string storage for content model/format, username/IP
address, and edit comments
* multi-content revisions ("MCR") - multiple Content blobs of different
types on a page, revisioned consistently
There's also some ideas going around about using denormalized summary
tables more aggressively, perhaps changing where the indexes used for
specific uses live. For instance, a 'contribs' table with just the bits
needed for the index lookups for user-contribs, then joined to the other
tables.
Initial notes at
https://www.mediawiki.org/wiki/User:Brion_VIBBER/Compacting_the_revision_ta…
-- I'll be cleaning this up a bit more in response to feedback and concerns.
If we go through with this sort of change, we'll need to carefully consider
the upgrade transition. We'll also need to make sure that all relevant
queries are updated, and that folks using the databases indirectly (via
tool labs, etc) are all able to cleanly handle the new fun stuff. Feedback
will be crucial here. :)
Potentially we might split this into a couple transitions instead, or
otherwise make major changes to the plan. Nothing's set in stone yet!
-- brion
Greetings,
A final invitation to participate in EMWCon for remote folks. If you would
like to watch the event live you can do so at the link below.
https://www.youtube.com/watch?v=Jad7owAql1E
IRC chat will be in the #enterprise-mediawiki channel on freenode.
Yours,
Chris Koerner