All,
The developer team at Wikimedia is making some changes to how accounts
work, as part of our on-going efforts to provide new and better tools
for our users (like cross-wiki notifications). These changes will mean
users have the same account name everywhere, will let us give you new
features that will help you edit & discuss better, and will allow more
flexible user permissions for tools. One of the pre-conditions for
this is that user accounts will now have to be unique across all 900
Wikimedia wikis.[0]
Unfortunately, some accounts are currently not unique across all our
wikis, but instead clash with other users who have the same account
name. To make sure that all of these users can use Wikimedia's wikis
in future, we will be renaming a number of accounts to have "~” and
the name of their wiki added to the end of their accounts' name. This
change will take place on or around 27 May. For example, a user called
“Example” on the Swedish Wiktionary who will be renamed would become
“Example~svwiktionary”.
All accounts will still work as before, and will continue to be
credited for all their edits made so far. However, users with renamed
accounts (whom we will be contacting individually) will have to use
the new account name when they log in.
It will now only be possible for accounts to be renamed globally; the
RenameUser tool will no longer work on a local basis - since all
accounts must be globally unique - therefore it will be withdrawn from
bureaucrats' tool sets. It will still be possible for users to ask on
Meta for their account to be renamed further, if they do not like
their new user name, once this takes place.
A copy of this note is posted to meta [1] for translation. Please
forward this to your local communities, and help get it translated.
Individuals who are affected will be notified via talk page and e-mail
notices nearer the time.
[0] - https://meta.wikimedia.org/wiki/Help:Unified_login
[1] - https://meta.wikimedia.org/wiki/Single_User_Login_finalisation_announcement
Yours,
--
James D. Forrester
Product Manager, VisualEditor
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
Jimmy just tweeted this:
https://twitter.com/jimmy_wales/status/362626509648834560
I think that's the first time I've seen him say "fuck" in a public
communication ...
Anyway, I expect people will ask us how the move to all-SSL is
progressing. So, how is it going?
(I've been telling people it's slowly moving along, we totally want
this, it's just technical resources. But more details would be most
useful!)
- d.
Hello and welcome to the shortest weekly deployment highlights email
thus far.
Full calendar:
https://wikitech.wikimedia.org/wiki/Deployments
Next week:
NOTHING.
Why? Wikimania. Due to decreased availability we will be postponing
deployments of all software until the week after Wikimania (exempting
high-need security or related fixes, of course).
To be explicit: The version of MediaWiki on WMF servers is currently
1.22wmf12 everywhere (all project sites). 1.22wmf13 will rollout to the
test wikis starting Thursday August 15th.
As always, let me know if you have any questions,
Greg
PS: There are some noteworthy deploys planned for the rest of the month
of August noted in the "Near Term" section of the Deployments page.
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
GSoC mentors: read this email through and submit your mid-term
evaluation between 29 July - 2 August in Google Melange. One per project
is enough. If the primary mentor can't make it then the secondary mentor
needs to step in.
VERY IMPORTANT
Missing this deadline means the cancellation of your student's GSoC
project. It also means "damage points" for Wikimedia in the current and
future GSoC editions.
You have the questions of the evaluation below, and you can start
preparing it now. Please add "Mid-term evaluation: WIP" in the table at
https://www.mediawiki.org/wiki/Summer_of_Code_2013 now (so your student
and the org admins know that you are on it). After submitting it change
that line with "Mid-term evaluation: OK".
Students: do not hesitate pinging your mentors about this evaluation if
you don't hear from them. Also remember that your monthly reports are
expected during next week.
https://www.mediawiki.org/wiki/Summer_of_Code_2013#Reporting
Thank you to everybody!
PS: fwiw I'm starting a week of holidays tomorrow and then I will be
flying to Hong Kong for Wikimania on Aug 1-2. If you need and org admin
Lydia Pintscher will be able to help you.
-------- Original Message --------
Subject: [GSoC Mentors Announce] 2013 Google Summer of Code Mentor
Midterm Evaluations 29 July - 2 August
Date: Sun, 21 Jul 2013 13:49:11 -0700
From: Carol Smith <carols(a)google.com>
Reply-To: gsoc-mentors-announce+owners(a)googlegroups.com
To: GSoC Mentors Announce <gsoc-mentors-announce(a)googlegroups.com>
Hi GSoC 2013 Mentors and Org Admins,
Per the program timeline [0], starting on Monday, 29 July you will will
be able to submit an evaluation of your student(s)' progress on their
projects thus far. Here's some important info on midterm evaluations for
those not familiar:
Midterm evaluations are done via Melange [1]. Starting at 19:00 UTC on
29 July you will be able to submit an evaluation for your student(s).You
can find the evaluation links on your dashboard under 'Evaluations', one
for each student you are a mentor (or co-mentor) for. If you are curious
about who can see evaluations after they are submitted, please check out
the FAQ on Evaluations [2]. I have also pre-published the evaluation
questions below in this email so you can prepare. The deadline is 19:00
UTC on Friday, 2 August.
You may not submit your evaluation before or after the evaluation
window. Please ask your org admin to submit your evaluation for you if
you absolutely cannot submit yours during the time allotted. Primary
mentors, co-mentors, and org admins may all submit evaluations of their
students.**Students must have an evaluation on file from both themselves
*and* their mentors in order to receive their midterm payments.** There
is no excuse for missing the submission of a student's evaluation.
You must submit an evaluation for every student you are the primary
mentor for this year. You must fill out the entire survey in one session
as there's no auto-save in Melange. You may submit, modify, and resubmit
an evaluation as many times as you choose up until the deadline.
Please note that failing a student at the midterm evaluation means *this
student is immediately removed from the program.* There is no way to
fail a student at the midterm and have the student continue with the
program to try to "make it up" at the final. If your student fails, your
student is out.
You might find the FLOSS manual on GSoC evaluations [3] helpful as well.
There's some excellent wisdom in there from your fellow mentors and org
admins on the evaluation process.
Finally, a reminder: This year we will not allow any mentor who misses
an evaluation deadline to attend the mentor summit (assuming no one else
submits the evaluation on the mentor's behalf before the deadline
either). Also, any org that misses 2 or more evaluation deadlines (for
the midterm, final, or midterm and final combined) will not be invited
to attend the mentor summit this year.
Please let me know directly if you have questions or concerns.
[0] - http://www.google-melange.com/gsoc/events/google/gsoc2013
[1] - http://google-melange.com <http://google-melange.com/>
[2] -
http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc20…
[3] - http://www.booki.cc/gsoc-mentoring/evaluations/
Cheers,
Carol
------
1.
How many years have you been a mentor for Google Summer of Code
(Total - this doesn’t have to be consecutive)?
1.
This is my first year
2.
2-3 years
3.
More than 3 years
2.
If you answered 2-3 years or more than 3 years, what years did you
participate?
3.
How many years have you been a student in Google Summer of Code?
1.
I have never been a student
2.
1 year
3.
2 years
4.
3+ years
4.
If you answered 2 years or 3+ years, what years did you participate?
5.
At what point did you first make contact with your student?
1.
Before the program was announced
2.
After my organization was selected to participate in Google
Summer of Code
3.
During the student application/acceptance phase of the program
4.
During the community bonding period
5.
After the start of coding
6.
How often do you and your student interact?
1.
Daily
2.
Every few days
3.
Weekly
4.
Every few weeks
5.
Monthly
6.
Less than once a month
7.
How do you communicate with your student? (Check all that apply)
1.
Google+ Hangout
2.
Voice (phone, Skype, etc.)
3.
IM/IRC
4.
Private emails
5.
Mailing Lists
6.
Student blog updates
7.
In-person meeting(s)
8.
Other
8.
Of the communication methods listed above, which do you use most
frequently?
9.
How much time do you spend on Google Summer of Code per week (take
into consideration your interactions with your student as well as
time working with your org and on your own)?
1.
1-5 hours
2.
5-10 hours
3.
10-15 hours
4.
15-20 hours
5.
More than 20 hours per week
10.
How many time zones apart from your student are you?
1.
Less than 3
2.
3-6
3.
More than 6
11.
How often do you require status updates from your student?
1.
Daily
2.
Every few days
3.
Weekly
4.
Only when explicitly asked for by me
12.
Please rate the quality of your interactions and communications with
the student (consider his/her communication with you as well as your
responses).
1.
Very Good (Student is regularly responsive and the quality of
communication is high)
2.
Good (Student is somewhat responsive and the quality of
communication is okay)
3.
Bad (Student is only somewhat or not at all responsive and the
quality of communication is low)
13.
Please rate the quality of the student’s interactions with your
organization and community.
1.
Very Good (Student is regularly responsive and the quality of
communication is high)
2.
Good (Student is somewhat responsive and the quality of
communication is ok)
3.
Bad (Student is only somewhat or not at all responsive and the
quality of communication is low)
14.
Is your student on track to complete his/her project?
1.
The student has already completed his/her project
2.
He/she is ahead of schedule
3.
He/she is on schedule
4.
He/she is behind schedule
15.
Please rate the quality of code/work the student has produced thus far.
1.
Amongst the best people I’ve ever worked with
2.
Solid-quality performance
3.
Good performance
4.
Mediocre performance
5.
Disappointing or not performing at all
16.
How do you feel about the new Google Summer of Code timeline?
1.
Less accommodating to my school/work schedule
2.
Equally accommodating to my school/work schedule
3.
More accomodating to my school/work schedule
17.
If you answered “less accommodating” above, what would be a better
schedule for you?
18.
Give an example of a very good or very bad interaction you had with
your student.
19.
Anything else you’d like to tell us or suggestions on how we could
improve the program?
20.
For the midterm evaluation, should this student pass or fail?
1.
Pass
2.
Fail
--
You received this message because you are subscribed to the Google
Groups "Google Summer of Code Mentors Announce List" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to gsoc-mentors-announce+unsubscribe(a)googlegroups.com.
Visit this group at http://groups.google.com/group/gsoc-mentors-announce.
For more options, visit https://groups.google.com/groups/opt_out.
Below you can find the condensed version of changes made to the WMF
Engineering Roadmap made over the last week. For the full roadmap, see:
http://www.mediawiki.org/wiki/Roadmap
For the diff used to create the below summary, see:
http://www.mediawiki.org/w/index.php?title=Roadmap&diff=748215&oldid=731898
Any questions/clarifications, please don't hesitate to ask!
Greg
== AFT ==
* July: remove from dewiki, support frwiki pilot, start winding down
development
* August: support frwiki and other wikis
== Echo ==
* July: HTML email notifications, release on meta & frwiki
* Aug: relase on more wikis, team transitions to work on Flow
== Mobile ==
* June: Mobile GettingStarted in beta, and EventLogging on betalabs
* July: notification styling changes in beta
* August: Editor dashboards, notifications in stable
== Ops ==
* July: DNS upgrades rolled out, OpenStreetMap (OSM) design work
* Aug: OSM deployment
== Platform ==
* July: Search prototype in Labs, Release Engineering (RelEng) (first)
Quarterly review prep
* Aug: OAuth deployment to all wikis, Search deploy to test2, RelEng
Quarterly review
* Sept: RelEng sprints begin
== QA ==
* Aug: Continue training sessions: failure analysis; ongoing newbie
training
== Wikidata ==
* July: URL datatype, Wikivoyage interwikis
* Aug: Monolingual text
* Sept: Simple queries (one property with one value), Quantity datatype,
arbitrary item access
* Oct: Range queries, statements with ranks, Merge/redirect of entities
* Nov: Visualisations of results, Merge/redirect of entities
* Dec: Conjunctive queries, Defining queries per UI
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
I remeber we discussed using asserts and decided they're a bad idea
for WMF-deployed code - yet I see
Warning: assert() [<a href='function.assert'>function.assert</a>]: Assertion failed in /usr/local/apache/common-local/php-1.22wmf12/extensions/WikibaseDataModel/DataModel/Claim/Claims.php on line 291
Thoughts?
--
Best regards,
Max Semenik ([[User:MaxSem]])
Hi,
I noticed some pages we crawled containing error message like this;
<div id="mw-content-text" lang="zh-CN" dir="ltr" class="mw-content-ltr"><p
class="error">Failed to render property P373:
Wikibase\LanguageWithConversion::factory: given languages do not have the
same parent language</p>
But when I open the url in browser, there is no such message. And using
index.php can also get normal content without error messages.
Here are examples you can retry:
bad
$ wget 'http://zh.wikipedia.org/zh-cn/Google'
good
$ wget 'http://zh.wikipedia.org/w/index.php?title=Google'
Looks like something is wrong on Wikipedia side, anything need to fix?
Thanks
--
Jiang BIAN
This email may be confidential or privileged. If you received this
communication by mistake, please don't forward it to anyone else, please
erase all copies and attachments, and please let me know that it went to
the wrong person. Thanks.