On Mon, Dec 21, 2015 at 11:22 AM, Gnangarra <gnangarra(a)gmail.com> wrote:
> This is going nowhere, one of the big issues is that there is a lack of
> understanding on how WikiData works and whats it purpose is.
>
>
> Wikimedia Australia solution is invest community money into bringing
> someone who has contributed to Wikidata to Australia to do a series of
> talks and workshops around the country over a three week period.
Ah, that sounds interesting. Could you provide more information about
that please? I havent seen this mentioned on the public mailing lists
before.
Wikimedia Indonesia is doing a Wikidata project next year and lapping
up all the training they can get. I am sure they would be interested
in having a trainer stop over in Jakarta on the way to or from
Australia.
--
John Vandenberg
Not a contribution to the discussion at large, but I had the same problem Andreas is mentioning a couple of days ago when doing some of my first WD edits and adding a reference. I had no idea what to chose in that property field and it only showed me “instance of” and “subclass of” as a cold start. (I guess your average new editor might even wonder why to enter a property at all there - they would probably expect a single field to enter the source.) So I just went to some other items and checked how it was done there, which is not optimal. A pre-selection of relevant properties (maybe most used in other items?) in the type-ahead would be nice. And maybe a small explanation of what the property for references means (something like “specifies type of reference” ?). I was also unsure if and when to ever use “imported from” in that field (i.e., if I got the fact from a Wikipedia page, but no primary source exists) or if that was reserved for machine imports.
Fabian
> Date: Sun, 20 Dec 2015 15:59:58 +0000
> From: Andreas Kolbe <jayen466(a)gmail.com <mailto:jayen466@gmail.com>>
> To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org <mailto:wikimedia-l@lists.wikimedia.org>>
> Subject: Re: [Wikimedia-l] Quality issues
>>
> Just try it, Lydia. Click "add" in subsidiaries in
> https://www.wikidata.org/wiki/Q37156 <https://www.wikidata.org/wiki/Q37156> -- enter a company name, and then
> click "add reference". When I do that, the text field contains a greyed-out
> "property", and the drop-down shows the unhelpful items I mentioned above.
>
> And it would be good if the help text actually *asked* people to cite a
> reference.
Hi Giles,
I regret I will probably not be available for the IRC office hours as scheduled.
In the discussion of shared hosting, I worry that en:User:Dispenser's
reflinks project, which requires a 20 TB cache, is being forgotten
again. He tried to host it himself, but it's offline again. This data
is essential in maintaining an audit trail of references as long as
the Internet Archive respects robots.txt retroactively, allowing those
who inherit domains to censor them, even if they have already been
used as a reference in Wikipedia. Keeping the cache is absolutely a
fair use right in the US, in both statutory and case law, and it is
essential to be able to track down patterns of attempts at deceptive
editing to address quality concerns around deliberately biased editing
such as paid editing. Because of the sensitivity of this goal, the
Foundation should certainly bear the risk of hosting the reflinks
cache. However, in the past, 20 TB was considered excessive, even
though the cost was shown to be less than $5000 without whatever Dell
NSA-enabled hardware you usually buy.
Would you please reach out to en:User:Dispenser and offer them the
20TB hosting solution they need for the Foundation to bear the risk of
the reflinks cache? Thank you for your kind consideration.
Best regards,
Jim
Hi,
This actually seems to be an amazing achievemet. Way to go Wikimedia France.
Regards
Satdeep Gill
> On 18-Dec-2015, at 1:12 AM, wikimedia-l-request(a)lists.wikimedia.org wrote:
>
> Re: [Wikimedia France] Certification by IDEAS (Katy Love)
Hi everyone,
A quick email to share with you a good news on our side.
A few month ago, Wikimedia France started a process to apply for a third
party certification called IDEAS. This certification is the first step for
us in a process to get recognized Wikimedia France as a serious
organisation that can be formally trusted by donors.
IDEAS label is hard to get as you have to reach high criterias on 3 grounds
:
* Governance
* Accounting
* Actions effectiveness
The process took a little over 6 month, and required us to provide them
with documents, interviews and explanations of what we are and what we’re
doing.
I’m proud to say that thanks to the work of many, and especially our staff,
we received it with flying colors. Usually, IDEAS grant the label and
includes recommendations for the organization to even do better.
They failed to provide any recommendation in our case and expressed large
congratulations for exceeding their expectations.
Second step, starting now, is to get formal recognition of Wikimedia France
as a General Interest organisation by the french government. Around 10
non-profits get such recognition every year, and right now only 633
organisations have it.
We hope to get it in the coming month.
All the best,
Christophe HENNER | Président
-------------------------------------------------------------------
› Mail : christophe.henner(a)wikimedia.fr
› Mobile : +33(0)6 50 66 47 39
› Tel : +33(0)5 62 89 12 01
› Twitter : @schiste
-----------------------------------------------------
Wikimédia France | Association pour le libre partage de la connaissance |
Visitez notre blog http://blog.wikimedia.fr
Hi, all.
Reaching out here because Wikimedians congregate here, as do people who
know Wikimedians. :)
As some of you have already seen, we are adding an additional WMF Community
Advocate. We're hoping for somebody who already knows and supports the
Wikimedia mission, knows how to communicate clearly and cordially, is
focused on building relationships and finding solutions, can handle tense
conversations and difficult content, is fluent in (an)other major
language(s) in addition to English, has project/people management
experience (even volunteer), and can help with coding and maintaining tools
in PHP, HTML, CSS, Javascript and SQL. (More detail and additional "hope
fors" in the job description
<https://boards.greenhouse.io/wikimedia/jobs/132232?t=3nu14v#.VnMnvJMrLq1>.)
Mind you, that's a wishlist, and our perfect candidate may not check all
boxes. People are more than ingredient lists!
Position is full time and entirely open to remote staffing.
If you're interested, please apply. If you know somebody who might be
interested, please pass it along.
Best,
Maggie
P.S. In case the above link doesn't work, job description:
https://boards.greenhouse.io/wikimedia/jobs/132232?t=3nu14v#.VnMnvJMrLq1
--
Maggie Dennis
Director, Community Advocacy
Wikimedia Foundation, Inc.
No one asked for 10 more wishes? :)
Thanks Danny and the Community Tech team. This is a great model for working
with our Communities.
-Toby
On Wed, Dec 16, 2015 at 12:18 PM, Nirzar Pangarkar <npangarkar(a)wikimedia.org
> wrote:
> It's really cool to see community wish list coming together!
>
> > We're going to talk with the other Wikimedia product teams, to see if
> they can take on some of the ideas the the community has expressed interest
> in.
>
> +1
>
> On Thu, Dec 17, 2015 at 1:42 AM, Danny Horn <dhorn(a)wikimedia.org> wrote:
>
>> Hi everyone,
>>
>> I'm happy to announce that the Community Tech team's Community Wishlist
>> Survey has concluded, and we're able to announce the top 10 wishes!
>>
>> 634 people participated in the survey, where they proposed, discussed and
>> voted on 107 ideas. There was a two-week period in November to submit and
>> endorse proposals, followed by two weeks of voting. The top 10 proposals
>> with the most support votes now become the Community Tech team's backlog of
>> projects to evaluate and address.
>>
>> And here's the top 10:
>>
>> #1. Migrate dead links to the Wayback Machine (111 support votes)
>> #2. Improved diff compare screen (104)
>> #3. Central global repository for templates, gadgets and Lua modules (87)
>> #4. Cross-wiki watchlist (84)
>> #4. Numerical sorting in categories (84)
>> #6. Allow categories in Commons in all languages (78)
>> #7. Pageview Stats tool (70)
>> #8. Global cross-wiki user talk page (66)
>> #9. Improve the "copy and paste detection" bot (63)
>> #10. Add a user watchlist (62)
>>
>> You can see the whole list here, with links to all the proposals and
>> Phabricator tickets:
>> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
>>
>> So what happens now?
>>
>> Over the next couple weeks, Community Tech will do a preliminary
>> assessment on the top 10, and start figuring out what's involved. We need
>> to have a clear definition of the problem and proposed solution, and begin
>> to understand the technical, design and community challenges for each one.
>>
>> Some wishes in the top 10 seem relatively straightforward, and we'll be
>> able to dig in and start working on them in the new year. Some wishes are
>> going to need a lot of investigation and discussion with other developers,
>> product teams, designers and community members. There may be some that are
>> just too big or too hard to do at all.
>>
>> Our analysis will look at the following factors:
>>
>> * SUPPORT: Overall support for the proposal, including the discussions on
>> the survey page. This will take the neutral and oppose votes into account.
>> Some of these ideas also have a rich history of discussions on-wiki and in
>> bug tickets. For some wishes, we'll need more community discussion to help
>> define the problem and agree on proposed solutions.
>>
>> * FEASIBILITY: How much work is involved, including existing blockers and
>> dependencies.
>>
>> * IMPACT: Evaluating how many projects and contributors will benefit,
>> whether it's a long-lasting solution or a temporary fix, and the
>> improvement in contributors' overall productivity and happiness.
>>
>> * RISK: Potential drawbacks, conflicts with other developers' work, and
>> negative effects on any group of contributors.
>>
>> Our plan for 2016 is to complete as many of the top 10 wishes as we can.
>> For the wishes in the top 10 that we can't complete, we're responsible for
>> investigating them fully and reporting back on the analysis.
>>
>> So there's going to be a series of checkpoints through the year, where
>> we'll present the current status of the top 10 wishes. The first will be at
>> the Wikimedia Developer Summit in the first week of January. We're planning
>> to talk about the preliminary assessment there, and then share it more
>> widely.
>>
>> If you're eager to follow the whole process as we go along, we'll be
>> documenting and keeping notes in two places:
>>
>> On Meta: 2015 Community Wishlist Survey/Top 10:
>> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Top_10
>>
>> On Phabricator: Community Wishlist Survey board:
>> https://phabricator.wikimedia.org/tag/community-wishlist-survey/
>>
>> Finally: What about the other 97 proposals?
>>
>> There were a lot of good and important proposals that didn't happen to
>> get quite as many support votes, and I'm sure everybody has at least one
>> that they were rooting for. Again, the whole list is here:
>>
>> https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey/Results
>>
>> We're going to talk with the other Wikimedia product teams, to see if
>> they can take on some of the ideas the the community has expressed interest
>> in. We're also going to work with the Developer Relations team to see if
>> some of these could be taken on by volunteer developers.
>>
>> It's also possible that Community Tech could take on a small-scale,
>> well-defined proposal below the top 10, if it doesn't interfere with our
>> commitments to the top 10 wishes.
>>
>> So there's lots of work to be done, and hooray, we have a whole year to
>> do it. If this process turns out to be a success, then we plan to do
>> another survey at the end of 2016, to give more people a chance to
>> participate, and bring more great ideas.
>>
>> For everybody who proposed, endorsed, discussed, debated and voted in the
>> survey, as well as everyone who said nice things to us recently: thank you
>> very much for coming out and supporting live feature development. We're
>> excited about the work ahead of us.
>>
>> We'd also like to thank Wikimedia Deutschland's Technischer
>> Communitybedarf team -- they came up with this whole survey process, and
>> they've been working successfully on lots of community wishes since their
>> first survey in 2013.
>>
>> You can watch this page for further Community Tech announcements:
>> https://meta.wikimedia.org/wiki/Community_Tech/News
>>
>> Thanks!
>>
>> Danny Horn
>> Product Manager, WMF Community Tech
>>
>> _______________________________________________
>> Wmfall mailing list
>> Wmfall(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>
>>
>
> _______________________________________________
> Wmfall mailing list
> Wmfall(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
>
(splitting as per Richard request)
> Question for the Wikisource folks: would Project Grants be a way to get
> resources for you? If you can design a project and find people with the
> right skills, that avenue might be beneficial for you. I have a software
> developer in mind who would probably like to work with you if resources
are
> available and a project has the support of the community and WMF.
>
> Pine
Hi Pine. My personal answer to your question is: no. Because we've already
tried that, and we did barely scratch the surface of the issues.
I'm on mobile and cannot provide you details and references, but in the
past years we used both IEG and Google Summer of Code for funding
developers, and we had few successinaddressing main issues. Also, tools
that worked and were helpful are now abandoned.
What wikisource lacks is development to core software, not only external,
cool tools, which are fine but in the end don't really solve problems.
I can elaborate further and bore you with details but, ina nutshell, we
just need commitment from people who can bring theirlines ofcode into
production. As Wikisource is formally a Wikimedia project, and provides its
tiny contribution to the mission and also to fundraising, I would expect a
commitment of this sort coming from WMF.
Aubrey
> _______________________________________________
> Wikimedia-l mailing list, guidelines at:
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
> Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
<mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>