Hello all,
I am trying to develop a chrome extension to work with wikipedia.
Started exploring javascript for login api.
Got this example.
https://www.mediawiki.org/wiki/Example_login_code_in_JS_%28using_JQuery%29
Stored the code as test.html and opened in chrome.
Got the following error.
No 'Access-Control-Allow-Origin' header is present on the requested
resource. Origin 'null' is therefore not allowed access.
How to solve this error?
https://www.mediawiki.org/wiki/Manual:CORS
The examples here are not helpful.
Please guide me on how to login to mediawiki via javascript?
Thanks.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free E-Magazine on Free Open Source Software in Tamil : http://kaniyam.com
Get Free Tamil Ebooks for Android, iOS, Kindle, Computer :
http://FreeTamilEbooks.com
Hi all,
just a moment ago I noticed, that Rob Lanphier seems to (silently) does not
work for the WMF anymore? At least based on a comment on his WMF-account's
talk page[1] and a commit in gerrit[2] it seems he doesn't work at the WMF
anymore.
However: What happened? I haven't seen any public info about this? Can
someone explain what happened? I'm really interested in it, as I really like
RobLa, both as a person (at least from what I saw/read so far) and the
professional /technical input and things he did. Would be nice, if someone
could bring some light into the darkness :P
Best,
Florian
[1] https://meta.wikimedia.org/wiki/User_talk:RobLa-WMF#Goodbye_and_thanks
[2] https://gerrit.wikimedia.org/r/#/c/318656/2
Hi all,
Just so everyone using the deployment-prep instances are aware:
deployment-puppetmaster has been retired in favour of
deployment-puppetmaster02, which runs role::puppetmaster::standalone, which
should behave much closer to how production puppetmasters and the labs
default puppetmaster work.
Details are in https://phabricator.wikimedia.org/T149620
Alex
Hello,
The search-as-you-type completion suggester, which powers the search
function at the top right of every page (or in the sidebar in Monobook),
can now be configured at Special:Preferences. The default setting includes
our most recent improvements to search while the new options make it easy
to restrict the completion suggester. This is useful when searching for
specific text in search queries. A description of the preferences can be
found on MediaWiki.org [0] or inline at Special:Preferences. Feedback and
questions are welcome. [1]
[0]
https://www.mediawiki.org/wiki/Extension:CirrusSearch/CompletionSuggester
[1] https://www.mediawiki.org/wiki/Help:CirrusSearch/CompletionSuggester
Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
The Wikimedia continuous integration system will be unavailable while some
scheduled maintenance is done.
When: Thursday 3rd 2016 for two hours between 16:00 UTC to 18:00 UTC.
Impact: During that time, you will still be able to send patches to Gerrit but
no CI jobs will be run nor will patches be automatically merged when someone
votes "Code-Review +2". All patches sent during the operations will be sent to
the CI system for you as a convenience.
Why: The maintenance will move the core of the CI system (Jenkins and Zuul)
from an aged server to a fresh new machine.
More info: It will be done by Antoine Musso, Tyler Cipriani and Daniel Zahn.
You will be able to watch progress on IRC in the #wikimedia-operations channel.
See also: https://phabricator.wikimedia.org/T95757
Hello all,
I hit across this idea in the recent GSoC Mentors summit, and in the
discussion with Srishti and Sumit on the reducing usability and scope of
GSoC/Outreachy projects[1] among the years.
*The problem*
Students show up one or two weeks before GSoC or Outreachy, and propose a
solution to existing ideas, and often end up completing it and leaving the
project. Due to this, there is a decline in student-proposed ideas as well,
given 1-2 weeks is not enough to understand Wikimedia from any direction.
*How to solve *
Its tricky, and I came across this program codeheat[2] by FOSSASIA which is
kind of like a Google Code In without any age limit. Its open for everyone
(with majority being Univeristy students), and of course - if this runs
before GSoC, these students who shine in this program gets an advantage
while applying for GSoC. Like they would better know the community, and
might be even able to propose a much-needed project.
The timing of the event is pretty important, like if we need students to
stick to their project once they complete one among the outreach programs
(GSoC/Outreachy), they need to be *engaged*. I think a pattern like this
would help.
1. A Wikimedia specific code challenge running from say Jan 15 to Mar
1st with grand prize winners given goodies and maybe a conference ticket
(if funds exists)
2. Student with Google Summer of Code/ Outreachy from Mar 20 - September
6th [3] and later mentoring.
3. Google Code In Mentors from mid November to January 30
The students can then be mentors for the rest of the programs, and thus
feel warm with the community.
What can the* new event cost*
While talking with FOSSASIA, it seems like they just have a registration
app running at [2], and they assign issues via Github to applicants. Since
we have phab, this might be even simple. Since its a challenge, it can get
enough publicity, and specially in Universities which have future
GSoC/Outreach students and mentors.
We might need someone happy enough to run the program too (
Do comment what you think about the idea of retaining GSoC students with
such an event. Feedbacks and comments welcome.
[1] https://www.mediawiki.org/wiki/User:MaxSem/GSoC_analysis
[2] http://codeheat.org/
[3] https://developers.google.com/open-source/gsoc/timeline
Thanks,
Tony Thomas <https://www.mediawiki.org/wiki/User:01tonythomas>
Home <http://www.thomastony.me> | Blog <https://tttwrites.wordpress.com/> |
ThinkFOSS <http://www.thinkfoss.com>
Forwarding.
Pine
---------- Forwarded message ----------
From: Katherine Maher <kmaher(a)wikimedia.org>
Date: Wed, Nov 2, 2016 at 11:22 AM
Subject: [Wikimedia-l] Introducing Victoria Coleman, WMF Chief Technology
Officer
To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>,
wikimediaannounce-l(a)lists.wikimedia.org
Cc: Victoria Coleman <victoria(a)gocolemans.com>
Hi everyone,
I’m excited today to introduce the Wikimedia Foundation's new Chief
Technology Officer, Victoria Coleman. Victoria’s first day is November 7,
and she will be based in the Foundation's office in San Francisco.
Victoria comes to us with more than 20 years of experience in consumer and
enterprise technology. And as you’ll learn quickly when you start getting
to know her, she is deeply passionate about the importance of education,
and how the Wikimedia mission advances education and equity around the
world.
When we started looking for a CTO for the Foundation, projects, and
communities, we knew we were looking for a unique person - someone with the
experience to lead confidently, and the confidence to embrace open
collaboration in leadership. We were looking for someone with a track
record of success leading strategy and execution for technology platforms
at scale, someone will be an effective mentor and leader for our Technology
department, and a strong partner to Product teams. We needed someone who
would thrive in our culture and be an inclusive collaborator with staff and
community. We agreed that Victoria met these requirements and then some.
Victoria has deep experience across consumer and enterprise technology
fields and is a longtime advocate for innovation in education and the
public sector. She has seen and done many things in her career, from
mobility platforms to connected devices to cyber security to web services
at scale. She brings operational excellence in strategic long-term
planning, execution, delivery, and running large distributed teams.
Most recently, Victoria served as Senior Vice President and Chief
Technology Officer for the Connected Home Division of Technicolor, where
she was responsible for innovation strategy, product management, technology
roadmaps, and technical due diligence for acquisitions and partnerships.
Previously, as Senior Vice President of Research and Development at Harman,
she led the core technology platforms of the Infotainment Division
including systems and software, media, tuner, navigation, connectivity, and
advanced driver assist systems. Before this, she served as Vice President,
Emerging Technologies at Nokia, Vice President, Software Engineering of
Hewlett-Packard’s webOS global business unit, and Vice President of
Samsung's Advanced Institute of Technology.
Victoria also has deep familiarity with open source software development,
having witnessed the rise of the Unix movement first as a student and later
as an instructor. She has been actively involved in the development of the
Linux-based LiMo (renamed Tizen). She passionately believes in the power of
open source and is familiar with how a commitment to open source
strengthens platforms and products at an integral level.
Victoria received her B.Sc and M.Sc in Electronic Computer Systems and
Computer
Aided Logic Design respectively from the University of Salford, UK and her
Ph.D. in Computer Science from the University of Manchester, UK. She is the
author of over 60 articles and books (!). She has worked with teams around
the world, including in Belgium, Brazil, China, France, Finland, Germany,
India, Israel, Korea, Russia, the United Kingdom, and the United States.
One thing that struck many of us throughout our conversations was
Victoria's commitment to volunteering her knowledge and expertise outside
of her daily professional activities, serving on advisory councils in
higher education and the public sector. She is on the advisory Board of the
Santa Clara University Department of Computer Engineering, and she is also
a Senior Advisor to the Director of the University of California
Berkeley’s Center for Information Technology Research in the Interest of
Society. She serves as a volunteer advisor on both Lockheed Martin’s
Technology Advisory Group and on the United States Department of Defense’s
Defense Science Board where she offers advice and recommendations on
science, technology, manufacturing, and acquisition processes.
As a native of Greece, Victoria is interested in becoming a contributor on
Greek Wikipedia, and getting to know our colleagues and communities over
the coming months.
As many of you know, the CTO search has been an intensive process and our
highest recruiting priority in recent months. Dozens of people from across
the organization contributed to this effort, most notably the CTO hiring
committee, which included directors and senior staff from the Technology
department. Representatives from the C-level, Technology, and Product teams
also participated in interviews, panels, and lunches. In total, we reviewed
nearly 900 candidates, advancing 190 to recruiter screens, and reviewing 70
with the hiring committee.
I want to personally thank every single person who was involved in this
process. The focus and dedication of the Foundation’s recruiting team were
remarkable, as were the diligence and commitment of the many staff and
volunteers who supported this search.
More information on Victoria’s full background can be found in our blog
post announcing her arrival: https://blog.wikimedia.org/2016/11/02/
victoria-coleman-chief-technology-officer/
Victoria is on CC - please join me in welcoming her to the Foundation and
our movement!
Warmly,
Katherine
***
An on-wiki version of this message is available for translation:
https://www.mediawiki.org/wiki/Wikimedia_Engineering/
Introducing_Victoria_Coleman_-_Chief_Technology_Officer
***
--
Katherine Maher
Wikimedia Foundation
149 New Montgomery Street
San Francisco, CA 94105
+1 (415) 839-6885 ext. 6635
+1 (415) 712 4873
kmaher(a)wikimedia.org
_______________________________________________
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>