[Wikimedia-l] Re: Fwd: [Wikitech-I] Call for Projects and Mentors for Outreachy Round 27!

[Sage Ross]

One more: 
https://www.mediawiki.org/wiki/Outreachy/Round_27#Improve_how_Wiki_Education_Dashboard_counts_references_added

This one is focused on updating how the Dashboard counts references so
that it can work in every language, and will also be co-mentored by
Amine Hassou, one of the GSoC interns from the summer.

-Sage

On Tue, Sep 5, 2023 at 12:30 PM Sage Ross  wrote:
>
> I've listed a project: https://phabricator.wikimedia.org/T345108
>
> It's focused on improving the documentation for Programs & Events Dashboard 
> and will be co-mentored by one of Google Summer of Code interns!
>
> -Sage
>
> On Tue, Aug 29, 2023 at 7:06 AM Onyinyechi Onifade  
> wrote:
>>
>> Hey Everyone,
>>
>>
>> The deadline to submit projects on the Outreachy website is fast 
>> approaching! If you’re interested in mentoring a project through Outreachy, 
>> share them here as a sub-task of this Phabricator task: 
>> https://phabricator.wikimedia.org/T343871  before September 29th. We’re 
>> looking forward to receiving your projects!
>>
>>
>> Regards,
>>
>> Onyinye & Shiela (Wikimedia Org Admins for Outreachy Round 27)
>>
>>
>>
>> -- Forwarded message -
>> From: Onyinyechi Onifade 
>> Date: Thu, Aug 10, 2023 at 4:44 PM
>> Subject: [Wikitech-I] Call for Projects and Mentors for Outreachy Round 27!
>> To: , , 
>> 
>> Cc: 
>>
>>
>> Hello everyone,
>>
>>
>> TLDR; Wikimedia is participating in the Outreachy Round 27 internship 
>> program <https://www.mediawiki.org/wiki/Outreachy/Round_27 > [1]. 
>> Outreachy's goal is to support people from groups underrepresented in the 
>> technology industry. Interns will work remotely with mentors from our 
>> community. We are seeking mentors to propose projects that Outreachy interns 
>> can work on during their internship. If you have some ideas for coding or 
>> non-coding (design, documentation, translation, outreach, research) 
>> projects, share them by Sept. 29, 2023 at 4 pm UTC here as a subtask of this 
>> parent task: <https://phabricator.wikimedia.org/T343871 > [2]
>>
>>
>> Program Timeline
>>
>> As a mentor, you engage potential candidates in the application period 
>> between October–November (winter round) and help them make small 
>> contributions to your project. You work more closely with the accepted 
>> candidates during the internship period between December–March (winter 
>> round).
>>
>> Important dates are:
>>
>> Aug. 22, 2023 at 4pm UTC - Live Q for Outreachy mentors
>>
>> September 29, 2023 at 4pm UTC - Project submission deadline
>>
>>
>> Guidelines for Crafting Project Proposals
>>
>> * Follow this task description template when you propose a project in 
>> Phabricator: 
>> <https://phabricator.wikimedia.org/tag/outreach-programs-projects> [3]. You 
>> can also use this workboard to pick an idea if you don't have one already. 
>> Add #Outreachy (Round 27) tag.
>>
>> * Project should require an experienced developer ~15 days and a newcomer ~3 
>> months to complete.
>>
>> * Each project should have at least two mentors, including one with a 
>> technical background.
>>
>> * Ideally, the project has no tight deadlines, a moderate learning curve, 
>> and fewer dependencies on Wikimedia's core infrastructure. Projects 
>> addressing the needs of a language community are most welcome.
>>
>>
>> Learn more about the roles and responsibilities of mentors on MediaWiki.org: 
>> <https://www.mediawiki.org/wiki/Outreachy/Mentors> [4][5]
>>
>>
>>
>> Cheers,
>>
>> Onyinye & Sheila (Wikimedia Org Admins for Outreachy Round 27)
>>
>>
>>
>> [1] https://www.mediawiki.org/wiki/Outreachy/Round_27
>>
>>
>> [2] https://phabricator.wikimedia.org/T343871
>>
>>
>> [3] https://phabricator.wikimedia.org/tag/outreach-programs-projects/
>>
>>
>> [4] https://www.mediawiki.org/wiki/Outreachy/Mentors
>>
>>
>> [ 5]  https://www.outreachy.org/mentor/mentor-faq
>>
>>
>> ___
>> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
>> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
>> https://meta.wikimedia.org/wiki/Wikimedia-l
>> Public archives at 
>> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/2727OSETA4RZM5SNYOKTDXBNVBLC5LRW/
>> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/6YNVVRP2AWI2YGDQMOKNL6F7GTR3J2AJ/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Fwd: [Wikitech-I] Call for Projects and Mentors for Outreachy Round 27!

[Sage Ross]

I've listed a project: https://phabricator.wikimedia.org/T345108

It's focused on improving the documentation for Programs & Events Dashboard
and will be co-mentored by one of Google Summer of Code interns!

-Sage

On Tue, Aug 29, 2023 at 7:06 AM Onyinyechi Onifade 
wrote:

> Hey Everyone,
>
>
> The deadline to submit projects on the Outreachy website is fast
> approaching! If you’re interested in mentoring a project through Outreachy, 
> share
> them here as a sub-task of this Phabricator task:
> https://phabricator.wikimedia.org/T343871  before September 29th. We’re
> looking forward to receiving your projects!
>
>
> Regards,
>
> Onyinye & Shiela (Wikimedia Org Admins for Outreachy Round 27)
>
>
>
> -- Forwarded message -
> From: Onyinyechi Onifade 
> Date: Thu, Aug 10, 2023 at 4:44 PM
> Subject: [Wikitech-I] Call for Projects and Mentors for Outreachy Round 27!
> To: , , <
> wikid...@lists.wikimedia.org>
> Cc: 
>
>
> Hello everyone,
>
> TLDR; Wikimedia is participating in the Outreachy Round 27 internship
> program  [1].
> Outreachy's goal is to support people from groups underrepresented in the
> technology industry. Interns will work remotely with mentors from our
> community. We are seeking mentors to propose projects that Outreachy
> interns can work on during their internship. If you have some ideas for coding
> or non-coding (design, documentation, translation, outreach, research)
> projects, share them by Sept. 29, 2023 at 4 pm UTC here as a subtask of
> this parent task:  [2]
>
> Program Timeline
>
> As a mentor, you engage potential candidates in the application period
> between October–November (winter round) and help them make small
> contributions to your project. You work more closely with the accepted
> candidates during the internship period between December–March (winter
> round).
>
> Important dates are:
>
>-
>
>Aug. 22, 2023 at 4pm UTC - Live Q for Outreachy mentors
>
>-
>
>September 29, 2023 at 4pm UTC - Project submission deadline
>
>
>
> Guidelines for Crafting Project Proposals
>
> * Follow this task description template when you propose a project in
> Phabricator: <
> https://phabricator.wikimedia.org/tag/outreach-programs-projects> [3].
> You can also use this workboard to pick an idea if you don't have one
> already. Add #Outreachy (Round 27) tag.
>
> * Project should require an experienced developer ~15 days and a newcomer
> ~3 months to complete.
>
> * Each project should have at least two mentors, including one with a
> technical background.
>
> * Ideally, the project has no tight deadlines, a moderate learning curve,
> and fewer dependencies on Wikimedia's core infrastructure. Projects
> addressing the needs of a language community are most welcome.
>
>
> Learn more about the roles and responsibilities of mentors on
> MediaWiki.org:  [4][5]
>
>
>
> Cheers,
>
> Onyinye & Sheila (Wikimedia Org Admins for Outreachy Round 27)
>
>
>
> [1] https://www.mediawiki.org/wiki/Outreachy/Round_27
>
>
> [2] https://phabricator.wikimedia.org/T343871
>
>
> [3] https://phabricator.wikimedia.org/tag/outreach-programs-projects/
>
>
> [4] https://www.mediawiki.org/wiki/Outreachy/Mentors
>
>
> [ 5]  https://www.outreachy.org/mentor/mentor-faq
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines
> at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/2727OSETA4RZM5SNYOKTDXBNVBLC5LRW/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/7CEIXKXC2T7TZBA2V46SH6XPOWFKBG6A/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Bing-ChatGPT

[Sage Ross]

Luis,

OpenAI researchers have released some info about data sources that
trained GPT-3 (and hence ChatGPT): https://arxiv.org/abs/2005.14165

See section 2.2, starting on page 8 of the PDF.

The full text of English Wikipedia is one of five sources, the others
being CommonCrawl, a smaller subset of scraped websites based on
upvoted reddit links, and two unrevealed datasets of scanned books.
(I've read speculation that one of these datasets is basically the
Library Genesis archive.) Wikipedia is much smaller than the other
datasets, although they did weight it somewhat more heavily than any
other dataset. With the extra weighting, they say Wikipedia accounts
for 3% of the total training.

-Sage

On Wed, Feb 22, 2023 at 8:19 AM Luis (lu.is)  wrote:
>
> Anders, do you have a citation for “use Wikipedia content considerably”?
>
> Lots of early-ish ML work was heavily dependent on Wikipedia, but 
> state-of-the-art Large Language Models are trained on vast quantities of 
> text, of which Wikipedia is only a small part. ChatGPT does not share their 
> data sources (as far as I know) but the Eleuther.ai project released their 
> Pile a few years back, and that already had Wikipedia as < 5% of the text 
> data; I think it is safe to assume that the percentage is smaller for newer 
> models:  https://arxiv.org/abs/2101.00027
>
> Techniques to improve reliability of LLM output may rely more heavily on 
> Wikipedia. For example, Facebook uses Wikipedia rather heavily in this 
> *research paper*: https://arxiv.org/abs/2208.03299 But I have seen no 
> evidence that techniques like that are in use by OpenAI, or that they’re 
> specifically trained on Wikipedia. If you’ve seen discussion of that, or 
> evidence from output suggesting it, that’d be interesting and important!
>
> Social: @luis_in_br...@social.coop
> ML news: openml.fyi
> On Feb 20, 2023 at 1:52 AM -0800, Anders Wennersten 
> , wrote:
>
> BIng with ChatGPT is now released by Micrsoft.
>
> And from what I understand they use Wikipedia content considerably. If
> you ask Who is A B and A B is not widely known, the result is more or
> less identical to the content from the Wikipedia article (but worse, as
> it "makes up" facts that is incorrect).
>
> In a way I am glad to see Wikipedia is fully relevant even in this
> emerging AI-driven search world. But Google search has ben careful to
> always have a link to Wikipedia besides their made up summary of facts,
> which here it is missing (yet?). And for licences, they are all ignored.
>
> So if this is the future the number of  accesses from users to Wikipedia
> will collapse, and also their willingness to donate... (but our content
> still a cornerstone for knowledge)
>
> Anders
>
> (I got a lot of fact from an article in Swedish main newspaper by their
> tech editor. He started asking fact of himself, and when he received
> facts from his Wp article plus being credited to a book he had noting to
> do with, he started to try to tell/learn ChatGPT of this error. The
> chatPGT only got angry accusing the techeditor for lying and in the end
> cut off the conversation, as ChatGPT continued to teat the techeditor as
> lyer and vandal..).
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at 
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/GJJNX2Y7BX5RZYGAIYTUI6O6CSBN72EH/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at 
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/FPPZSZUIG4SKGIWGX57O4K7MGJO4CSI3/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/ET3W3Q2IXZAAJHLDXCMDIU3FELLLMWXX/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Voting now open on the revised Enforcement Guidelines for the Universal Code of Conduct

[Sage Ross]

I tried to vote, and my account ought to be eligible, I'm getting a
message that says I cannot vote and that "you are not in the
predetermined list of users authorized to vote in this election".

-Sage Ross
User:Ragesoss / User:Sage (Wiki Ed)

On Mon, Jan 16, 2023 at 4:15 PM Patrick Earley  wrote:
>
> Hello all,
>
>
> The voting period for the revised Universal Code of Conduct Enforcement 
> Guidelines is now open! [1] Voting will be open for two weeks and will close 
> at 23.59 UTC on January 31, 2023. Please visit the voter information page on 
> Meta-wiki [2] for voter eligibility information and details on how to vote.
>
>
> For more details on the Enforcement Guidelines and the voting process, see 
> our previous message. [3]
>
>
> On behalf of the UCoC Project Team,
>
> Patrick
>
> [1] 
> https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct/Revised_enforcement_guidelines
> [2] 
> https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct/Revised_enforcement_guidelines/Voter_information
> [3] 
> https://meta.wikimedia.org/wiki/Universal_Code_of_Conduct/Revised_enforcement_guidelines/Announcement/Voting_1
> --
> Patrick Earley
> Lead Trust & Safety Policy Manager
> Wikimedia Foundation
> pear...@wikimedia.org
>
> ___
> Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
> https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
> https://meta.wikimedia.org/wiki/Wikimedia-l
> Public archives at 
> https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/JPX7GLUQF74ISYQ2WO4PQQ6M7ROU6VWI/
> To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/HFUYJ25ALC2IINNMU7PMBH5DWSURUL2Y/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Open proxies and IP blocking

[Sage Ross]

On Wed, Apr 20, 2022 at 11:21 AM Florence Devouard  wrote:
>
> Short version : We need to find solutions to avoid so many africans being 
> globally IP blocked due to our No Open Proxies policy.
> https://meta.wikimedia.org/wiki/No_open_proxies/Unfair_blocking
>

This matches up with my observations as well. Over the last couple of
years, it has been increasingly common for new editors to be affected
by range blocks without any understanding of why. We see this
frequently with Wiki Education's student editors, and in most cases,
the editors are not knowingly using a VPN or other non-standard way of
connecting to the internet. In some cases, institutions are now using
VPNs at the network level by default. In other cases, patterns of how
people connect are just shifting so that they are more often assigned
temporary IP addresses that are covered by range blocks.

These kinds of blocks also prevent account creation, which Wiki
Education can easily work around by creating accounts on these user's
behalf (and event organizers using Programs & Events Dashboard
similarly have tools to work around this). But there are certainly
many, many more good faith would-be contributors who are stopped
before they can create an account, and they have no user-friendly
recourse to understand why they are affected by a block or how to work
around it.

My sense is that this is an important problem that merits attention at
the global level.

-Sage
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/55Z32IZM3S64ZHOFULEYD7GZLNGGANG2/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Re: Three Month Update & Wikimedia Foundation Draft Annual Plan

[Sage Ross]

On Thu, Apr 14, 2022 at 6:48 AM Maryana Iskander
 wrote:
>
> Hiring the right talent at this level is both art and science. So far, we 
> have sourced hundreds of candidates in a global search spanning the world, 
> although it will remain a rolling process until we find the right leader. I 
> hope to share more soon.
>

I note that the CTO job listing on greenhouse.io has been taken
down... eagerly waiting to learn more, because I agree that this is an
extremely important role for the movement right now.


Sage Ross
User:Ragesoss / User:Sage (Wiki Ed)
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/MXLLVJ5RD35Z33DCT32JKHCKCJDZ6UO4/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

[Wikimedia-l] Programs & Events Dashboard 2021 user survey

[Sage Ross]

If you've used — or are interesting in using — Programs & Events
Dashboard to organize and track metrics for editathons, education
programs, editing contests, wikidata projects, and other events,
please consider taking our user survey:
https://outreachdashboard.wmflabs.org/surveys/3

Wiki Education's annual plan
(https://wikiedu.org/blog/2021/06/30/announcing-our-2021-22-annual-plan/)
calls for significantly increasing our support for and development of
Programs & Events Dashboard over the next year, and this survey will
help prioritize that work and develop a roadmap. The survey has up to
14 questions, most of which are optional. (You can preview the survey
on-wiki: 
https://meta.wikimedia.org/wiki/Programs_%26_Events_Dashboard/2021_survey)

We'll also be sharing the survey data with WMF's new Campaigns team,
and coordinating with them to improve the tool ecosystem for
supporting program organizers across the movement.

Thanks!

----

Sage Ross
User:Sage (Wiki Ed) / User:Ragesoss
Wiki Education
https://wikiedu.org
___
Wikimedia-l mailing list -- wikimedia-l@lists.wikimedia.org, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
Public archives at 
https://lists.wikimedia.org/hyperkitty/list/wikimedia-l@lists.wikimedia.org/message/5XD665W3RV7AQRFIV6XV7EMD5YIIYP6J/
To unsubscribe send an email to wikimedia-l-le...@lists.wikimedia.org

Re: [Wikimedia-l] Update on Programs & Events Dashboard

[Sage Ross]

On Tue, Apr 9, 2019 at 10:28 AM Galder Gonzalez Larrañaga <
galder...@hotmail.com> wrote:

> I'm interested in the IP limit issue.. could you explain how it works,
> please?
>
> Thanks
>
> Galder
>

If you are one of the facilitators for a program or course on Programs &
Events Dashboard, there will be a button to "Enable account requests" on
the home tab. Once you enable account requests, there are two ways to use
the feature.

A user who follows the enrollment link and is not logged in will have the
option to request an account by entering their email address and desired
username. (The Dashboard will verify that the username is available before
they can submit the request.) Then, the facilitator will be able to see a
message when they view the program page, saying that there is a requested
account waiting to be created. They can click to approve it — at which
point, the Dashboard will create the account (and MediaWiki will email them
the temporary password), and also add that user as an editor for that
program.

A facilitator can also create a new account (and add it to the program)
directly, by entering an email and desired username on the Editors tab.
This is useful especially for in-person events like editathons, so that
those without accounts can get set up immediately upon arriving (rather
than needing to follow a link on their own computer).

How it works behind the scenes is that the facilitator or Dashboard admin
who clicks to create the account will attempt to do the account creation
action through OAuth with their own account (eg,
https://en.wikipedia.org/wiki/Special:Log/Meredithdrum ), but if they
cannot do so because of the IP limit, the account will be created by
User:OutreachDashboardBot instead:
https://en.wikipedia.org/wiki/Special:Log/OutreachDashboardBot

The feature can also be enabled by default for an entire campaign.

We built the initial account creation feature for Art+Feminism 2018, but
this year, we added the OutreachDashboardBot fallback so event organizers
to request Account Creator rights (which is what most people running an Art
+ Feminism event did in 2018).

-Sage
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 

[Wikimedia-l] Update on Programs & Events Dashboard

[Sage Ross]

The Wikimedia Community Tech team is in the final stretch of their
Community Wishlist 2017 work and recently announced the beta launch of
the 'Event Metrics' project they worked on for the #3 wish. Since the
initial proposal [1] was to improve Wiki Education's program
organizing and metrics tool Programs & Events Dashboard [2], we've
heard from a lot of people worried that Event Metrics [3] is supposed
to be a replacement for the Dashboard or that the Dashboard is going
away.

To clear up any potential confusion: Wiki Education will keep
supporting Programs & Events Dashboard as part of our commitment to
making our technology work as useful as possible to the rest of the
Wikimedia movement. Our newly-expanded Technology department, along
with many awesome volunteers and interns, is more committed than ever
to improving the Dashboard as tool for global programs, because it's
been so essential for many of you.

Programs & Events Dashboard recently passed the milestone of 4,000
programs, from more than 100 different wikis, and more than 28,000
editors have logged in [4].

For those who haven't used it before, or haven't done so in a while,
some of the useful features include:

* Account registration for in-person edit-a-thons  — to avoid getting
stopped by the IP limit for new accounts
* Automatically updated metrics for articles edited, number of edits,
Commons uploads, etc. [5]
* Additional downloadable metrics, including 7-day retention of new
editors, the complete list of edits made
* For English and Portuguese Wikipedia, tools for monitoring which
articles are involved in deletion processes [6]
* Translatable, wiki-editable training modules for newcomers [7]
* For all the languages with ORES "article quality" models, extra data
and visualizations based on ORES estimates

We have some additional features planned for the near future as well:

* Metrics for number of citations added
* Wikidata metrics for claims created and references added

If you have feature requests or complaints, please do let us know
either on the Meta talk page [8] or by opening an issue on GitHub [9].
Our team is small, so we rely heavily on the feedback we get from
Programs & Events Dashboard users to identify problems and make
improvements.

-Sage Ross
Wiki Education



[1] 
https://meta.wikimedia.org/wiki/Community_Wishlist_Survey_2017/Programs_and_events/Development_of_the_programs_and_events_dashboard
[2] https://outreachdashboard.wmflabs.org/
[3] https://eventmetrics.wmflabs.org/
[4] https://outreachdashboard.wmflabs.org/usage
[5] 
https://outreachdashboard.wmflabs.org/courses/Wikimedia_ZA/Wiki_Loves_Africa_2019_South_Africa/home
[6] https://outreachdashboard.wmflabs.org/campaigns/artfeminism_2019/alerts
[7] 
https://outreachdashboard.wmflabs.org/training/editing-wikipedia/editing-basics/welcome-new-editor
[8] https://meta.wikimedia.org/wiki/Talk:Programs_%26_Events_Dashboard
[9] 
https://github.com/WikiEducationFoundation/WikiEduDashboard/issues/new/choose

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and 
https://meta.wikimedia.org/wiki/Wikimedia-l
New messages to: Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
<mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe>

Re: [Wikimedia-l] Introducing Victoria Coleman, WMF Chief Technology Officer

[Sage Ross]

In case the link didn't work for anyone else:
https://blog.wikimedia.org/2016/11/02/victoria-coleman-chief-technology-officer/

-Sage

On Wed, Nov 2, 2016 at 11:22 AM, Katherine Maher  wrote:
> 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
> 

Re: [Wikimedia-l] Open Well-Tempered Clavier

[Sage Ross]

On Sat, Mar 21, 2015 at 10:23 AM, Quim Gil q...@wikimedia.org wrote:

 Crowdfunding is on the rise, and tags in this field are important because
 once you fund a project about #tag you get recommendations for more #tag
 projects. Maybe we could partner with Creative Commons and friends to
 request Kickstarter and the other platforms to include a #freeknowledge
 tag, or a similar alternative (this example could have also been
 #public-domain)? Or maybe someone is already working on this?

This is a wonderful idea. There is an occasionally-active hashtag
already, #FundFreeCulture, but it would be a lot more useful if it had
support from Creative Commons and other organizations and the people
asking for funding started using such a tag proactively.

See also the FOSsil Bank updates (run by Chris Sakkas, cc'd, who
started that hashtag) which has intermittent posts about free culture
crowdfunding campaigns:
https://livinglibre1.wordpress.com/category/round-ups/fossil-bank-updates/

-Sage

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] [Wikimediameta-l] Bye

[Sage Ross]

On Tue, Feb 24, 2015 at 10:43 AM, Austin Hair adh...@gmail.com wrote:

 With more and more Wikimedians engaging in crowdfunding, I suppose we
 can talk about whether the mailing list for Wikimedia movement
 organization is the place to advertise in this way. For my part, I
 don't think a simple (i.e., without any additional context) please
 check out this Indiegogo is any different from hey, check out my
 blog, so when the last one came through the queue I rejected it
 without much thought. It certainly wasn't done with any prejudice.


For my part, I always like to see crowdfunding pitches from
Wikimedians. There haven't been *that* many of them (maybe 8 or 10?),
and so far they've all (that I've seen) come from prolific
contributors.

These crowdfunding pitches generally take a lot more effort to put
together than a blog post does, and they are also easy and satisfying
to act on. If I can take 3 minutes and a few dollars to simultaneously
say thanks to a great contributor and help them make even better
contributions, I'm grateful for that opportunity.

-Sage

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Chapters and GLAM tooling

[Sage Ross]

On Tue, Nov 11, 2014 at 1:03 AM, Ilario Valdelli valde...@gmail.com wrote:
 When I start from this page:
 http://wikiedu.org/blog/2014/11/07/user-testing-assignment-design-wizard/

 and I click the wizard.wikiedu.org
 http://wikiedu.org/blog/2014/11/07/user-testing-assignment-design-wizard/wizard.wikiedu.org
 link I arrive in a page which says:
 This is somewhat embarrassing, isn’t it?Is this the aim?


Embarassing indeed! There was a misformed link in the blog post. It
now points to http://wizard.wikiedu.org as intended.

-Sage

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Revamped Wikipedia app for Android now live!

[Sage Ross]

For those without Google Play access or who otherwise prefer
sideloading, here's the APK you can install directly:
https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.0.apk

-Sage

On Wed, Jun 25, 2014 at 2:28 PM, Dan Garry dga...@wikimedia.org wrote:
 Hi everyone,

 If you love Wikipedia and have an Android phone, you’re in for a treat!
 Today we’ve released a revamped Wikipedia for Android app, now
 available on Google
 Play https://play.google.com/store/apps/details?id=org.wikipedia.

 Our new features include:

- *Speed* – Our new, native app allows you to browse and edit Wikipedia
faster than ever before.
- *Editing* – You can edit Wikipedia on the app. Logged in or logged
out, we thank you for all your contributions.
- *Recent pages* – We provide you with your reading history, so you can
tap as many links as you like without ever getting lost.
- *Saved pages* – You can save select pages for offline reading and
browse them even when you don’t have a data connection.
- *Share* – Use your existing social networking apps to share in the sum
of all human knowledge.
- *Language support* – The app allows you to seamlessly switch to
reading Wikipedia written in any language.
- *Wikipedia Zero* – We’ve partnered with cellular carriers around the
world to provide Wikipedia free of data charges to users in many developing
areas.

 Coming soon:

- *Night mode* – We’ve gotten lots of great beta user feedback; one
feature people love is reading Wikipedia in darker environments. The
inverted colour scheme offered by night mode will make that much easier.
- *Discussions* – Talk pages are an important part of Wikipedia for both
new users and experienced editors alike. We’re bringing them to the app.

 This release is just the beginning! We’re still working hard on creating
 new features to make the app the best Wikipedia reading and editing
 experience out there.

 Please help us improve this app by sending a note to our mailing list,
 mobile-android-wikipe...@wikimedia.org.

 Thank you!

 Dan

 --
 Dan Garry
 Associate Product Manager for Platform and Mobile Apps
 Wikimedia Foundation
 ___
 Wikimedia-l mailing list, guidelines at: 
 https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
 Wikimedia-l@lists.wikimedia.org
 Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
 mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Revamped Wikipedia app for Android now live!

[Sage Ross]

On Jun 25, 2014 9:12 PM, Andy Mabbett a...@pigsonthewing.org.uk wrote:

 I've just made my first edit. Unless I missed something, there was no way
 to enter an edit summary.

You can enter an edit summary. Either choose one of the predefined options
for how you improved the page, or pick other to enter a manual edit
summary.

-Sage
___
Wikimedia-l mailing list, guidelines at: 
https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Sponsorship/donations to other organizations

[Sage Ross]

TL;DR: Yes, I think we should be pro-actively putting significant
financial resources into the open source ecosystems we rely on.

Thanks Erik! This is a great discussion to have.

As I see it, we have a whole lot of potential fundraising revenue that
we leave unraised, simply because WMF doesn't have effective ways of
spending it or allocating it within the movement. The fundraising
system has become extremely efficient, so we've increasingly shifted
toward minimizing reader annoyance instead of increasing raising
money. But the annoyance factor of fundraising is so low right now
that (to me) it seems wasteful *not* to be raising and distributing
more, if it can be done in ways that support our mission (broadly
construed).

Wikipedia is the most prominent project of the top, public-facing
layer of a deep free culture / free software ecosystem. It wouldn't be
able to exist without that ecosystem, but because it's in that top
layer that directly serves the public, it generates most of the
goodwill and donation potential. But much of what donors love and
value and want to support about Wikipedia has deeper roots than they
realize. I used to be a regular donor to Wikimedia Foundation, but as
I've learned more about that deeper ecosystem, I've felt it my
responsibility -- because I know how things work beneath that surface
layer -- to focus my giving elsewhere in the free software and free
culture ecosystem. I would happily donate to WMF if I knew that the
fundraising system was aggressively working to gather money to improve
that whole ecosystem. (Instead, donating right now would feel like
making a donation to slightly decrease the number of fundraising
banners seen by readers; if I don't donate, I know there are more than
enough readers who will.)

One strategy for supporting other free software/free culture
organizations would be to make few-strings-attached grants for
specific work that will benefit us. (For example, we give a grant that
lets them pay  a developer's salary for a year to work on this or that
project that will result in better MediaWiki performance, or easier
management of our stack.) That would be consistent with what our
donors intend when they give.

-Sage (ragesoss)

On Tue, Apr 15, 2014 at 3:50 PM, Erik Moeller e...@wikimedia.org wrote:
 Hi folks,

 I'd be interested in hearing broader community opinions about the
 extent to which WMF should sponsor non-profits purely to support work
 that Wikimedia benefits from, even if it's not directed towards a
 specific goal established in a grant agreement.

 This comes up from time to time. One of the few historic precedents
 I'm aware of is the $5,000 donation that WMF made to FreeNode in 2006
 [1]. But there are of course many other organizations/communities that
 the Wikimedia movement is indebted to.

 On the software side, we have Ubuntu Linux (itself highly indebted to
 Debian) / Apache / MariaDB / PHP / Varnish / ElasticSearch / memcached
 / Puppet / OpenStack / various libraries and many other dependencies [2],
 infrastructure tools like ganglia, observium, icinga, etc. Some of
 these projects have nonprofits that accept and seek sponsorship and
 support, some don't.

 One could easily expand well beyond the software we depend on
 server-side to client-side open source applications used by our
 community to create content: stuff like Inkscape, GIMP and LibreOffice
 (used for diagrams). And there are other communities we depend on,
 like OpenStreetMap.

 So, should we steer clear of this type of sponsorship altogether
 because it's a slippery slope, or should we try to come up with
 evaluation criteria to consider it on a case-by-case basis (e.g. is
 there a trustworthy non-profit that has a track record of
 accomplishment and is in actual need of financial support)?

 I could imagine a process with a fixed giving back annual budget
 and a community nominations/review workflow. It'd be work to create
 and I don't want to commit to that yet, but I would be interested to
 hear opinions.

 MariaDB specifically invited WMF to become a sponsor, and we're
 clearly highly dependent on them. But I don't think it makes sense for
 us to just write checks if there's someone who asks for support and
 there's a justifiable need. However, if there's broad agreement that
 this is something Wikimedia should do more of, then I think it's worth
 developing more consistent sponsorship criteria.

 Thanks,
 Erik


 [1] https://wikimediafoundation.org/wiki/Resolution:Freenode_Donation
 [2] Cf. https://www.mediawiki.org/wiki/Upstream_projects
 --
 Erik Möller
 VP of Engineering and Product Development, Wikimedia Foundation

 ___
 Wikimedia-l mailing list
 Wikimedia-l@lists.wikimedia.org
 Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
 mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

___
Wikimedia-l mailing list

Re: [Wikimedia-l] Our next strategy plan-Paid editing

[Sage Ross]

On Tue, Mar 25, 2014 at 7:41 PM, Philippe Beaudette
phili...@wikimedia.org wrote:
 I wouldn't know, Pete.  But as I recall, it was a manual process, wasn't
 it?  And therefore quite difficult to scale and/or adapt for some usages?



 On Tue, Mar 25, 2014 at 4:35 PM, Pete Forsyth petefors...@gmail.com wrote:

 Philippe,

 The Public Policy Initiative produced strong validation for the Wikipedia
 1.0 approach to assessing article quality. Was Amy Roth's research ever
 published, and are there any plans to repeat it with a larger sample size
 etc.? I'd say we're closer than you think to having a good way to measure
 article quality.



That part of Amy Roth's research has not been published except
on-wiki.[1] There was also a followup study after the Public Policy
Initiative using the same method, which found found similar
results.[2]

It's true that these studies were manual processes that took a huge
amount of work and wouldn't scale (at least, without some investing in
tools for easy data generation and collection). But I think Pete's
point is that these studies show that the widespread Wikipedia 1.0
scale itself does a decent job of what it is intended to do.

[1] = https://outreach.wikimedia.org/wiki/Student_Contributions_to_Wikipedia
[2] = 
https://en.wikipedia.org/wiki/Wikipedia:Ambassadors/Research/Article_quality/Results

On Tue, Mar 25, 2014 at 7:55 PM, Marc A. Pelletier m...@uberbox.org wrote:
 On 03/25/2014 07:45 PM, John Mark Vandenberg wrote:
 If nothing else, the existing community quality rating system (i.e. FA, GA,
 etc.) should be used.

 That idea needs to be tempered with a strong caveat: at least for
 enwiki, those processes tend to be highly politized as they are already.
  Focusing strategy on those is likely to have volatile effects and any
 step in that direction has to be done deliberately and with a great deal
 of caution.


While this is true to some degree, if an article *does* make it
through one of these processes, that's a fairly reliable indicator
that it's at least pretty decent. The bigger problem is that the lower
ratings, between Stub and B-class, are often badly out-of-date. For
both the process-based ratings (FA, A, GA) and the informally assigned
ones (Stub, Start, C, B), the ratings are probably best thought of as
a very approximate lower bound for quality. (That is, a B-class
article might really be GA quality and it just never went through the
process, or a Stub might actually have developed well into C-class
territory in the time since its rating was assigned.)

The nice thing about the Wikipedia 1.0 ratings is that we already have
all the data, just waiting for someone to do something cool with it.
The history of this page would be fun to play with:
https://en.wikipedia.org/wiki/User:WP_1.0_bot/Tables/OverallArticles

-Sage

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, 
mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe

Re: [Wikimedia-l] Voice Intro Project

[Sage Ross]

On Fri, Feb 8, 2013 at 10:06 AM, Sarah Stierch sarah.stie...@gmail.com wrote:
 Yeah, it'd be cool to have a tool that allows the subject to record and
 then make their file an ogg, or record it to ogg in a super fast way.

 it's a small, but time consuming thing to record yourself, upload it (or
 whatever) to your computer, and then figure out how to make it into an open
 license.

 -Sarah

Sounds like a job for the Commons mobile apps! If sound recording is
not on the roadmap, it should be.

Yuvi, Brion, are you guys reading this thread? (I'll ping them.)

-Sage

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Office hours

[Sage Ross]

On Sat, Jan 26, 2013 at 8:36 AM, Rui Correia correia@gmail.com wrote:


 Thanks for explaining, but it still leaves puzzled to call a meeting
 office hours, when something less arcane would do - like IRC-Chat,
 Wiki-Chat, Wiki-Miti, Wiki-gether Rendez-VouWiki, etc etc .


I just took a stab at adding the relevant entry in Wiktionary: #2 at
http://en.wiktionary.org/wiki/office_hours

(Any Wiktionarians or would-be Wiktionarians, please improve!)

-Sage

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] 15% off merchandise today at the Wikimedia Shop

[Sage Ross]

On Mon, Jan 14, 2013 at 2:55 PM, Risker risker...@gmail.com wrote:
 On 14 January 2013 14:02, WereSpielChequers 
 werespielchequ...@gmail.comwrote:

  snip

 But if you really want me to get excited about the shop, try stocking flip
 flops with modified soles. I'm sure I'm not the only person who'd like to
 walk along the beach leaving a trail of [citation needed] tracks.

 WSC


 I have to saythis is brilliant. Plus it made me laugh out loud.


A+++ WOULD BUY!

-Sage

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Editor retention (was Re: Big data benefits and limitations (relevance: WMF editor engagement, fundraising, and HR practices))

[Sage Ross]

On Fri, Jan 4, 2013 at 1:06 PM, Peter Coombe thewub.w...@googlemail.com wrote:


 See https://en.wikipedia.org/wiki/Wikipedia:The_Wikipedia_Adventure
 which is a project very much along these lines. I'm not sure what the
 current status of that is, but it definitely seems like a good
 approach for at least some groups of newbies.


There is some neat tech that the E3 team has plans to use, which would
also be a good framework for this kind of interactive training:
https://www.mediawiki.org/wiki/Guided_tours

On a less interactive level, we've also got some trainings tailored to
different groups of people:
http://en.wikipedia.org/wiki/Wikipedia:Training

We've never really tried systematically pointing newbies to a
structured orientation (as opposed to giving them 10 or 20 links to
explore without guidance).

-Sage

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] And you thought the Amazon Wikipedia books were bad

[Sage Ross]

On Thu, Dec 13, 2012 at 1:54 PM, Mathias Schindler
mathias.schind...@gmail.com wrote:
 On Thu, Dec 13, 2012 at 7:25 PM, David Gerard dger...@gmail.com wrote:
 http://singularityhub.com/2012/12/13/patented-book-writing-system-lets-one-professor-create-hundreds-of-thousands-of-amazon-books-and-counting/

 He's patented the method, too. Hopefully he will enforce the patent.

 Noam Cohen wrote about him in 2008:
 http://www.nytimes.com/2008/04/14/business/worldbusiness/14iht-14link.11952478.html?pagewanted=all_r=0
 Little has changed since then.


This, if I recall correctly, is some Wikimedians geeking out over how
cool his methods were:
http://commons.wikimedia.org/wiki/File:Aaron,_SJ_and_Mako_at_Boston_Wikipedia_Meetup,_2009-08-18.jpg

:-)

-Sage

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Copyright on Xrays

[Sage Ross]

On Mon, Aug 20, 2012 at 3:17 PM, geni geni...@gmail.com wrote:
 On 20 August 2012 12:52, David Gerard dger...@gmail.com wrote:
 On 20 August 2012 12:50, Anthony wikim...@inbox.org wrote:
 On Mon, Aug 20, 2012 at 7:47 AM, David Gerard dger...@gmail.com wrote:

 I'm sure that collectively we can bloviate with the best of 'em on the
 topic - but do we have any case law whatsoever anywhere on the topic
 that might give real-world pointers?

 It's a question of fact, not a question of law.


 Then any real-world examples of the question arising.



 I doubt it. Most X-rays aren't worth enough to be worth suing over and
 the handful that are mostly derive for the scientific community who
 tend not to sue people over the issue of copyright.


From what I've seen, copyright doesn't even enter into the
institutional perspective here. The framework is all about controlling
the flow of patient information.

My partner (a doctor doing residency at the main hospital system in
Pittsburgh) would have to go through the Institutional Review Board
system to publish medical images, even ones nominally free of
identifying information. She'd be able to have them published for
certain purposes (case studies and other things that are about medical
practice, but are not research per se) without patient permission. For
research and other purposes, she would need permission of the patients
even for nominally non-identifying medical info. But there aren't any
additional hurdles regarding assignment of copyright to the
publishers.

On the other hand, medical technicians and doctors who create
ultrasound images for pregnant women distribute them to the women (and
even intentionally frame some as portraits, with at least a little
bit of creativity involved) to do with as they please.

I'd say, whatever the copyright status, she'd risk her job by
distributing something like X-rays without going through the IRB
system. And if she got IRB permission, asserting PD status or copyleft
status or whatever wouldn't likely be a problem.

-Sage

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l

Re: [Wikimedia-l] Wikimedia events: staging area?

[Sage Ross]

On Thu, Apr 19, 2012 at 8:19 AM, Lodewijk lodew...@effeietsanders.org wrote:
 Hi all,

 With all the Wikimedia events it is a problem that keeps coming back:
 whether participants do or do not want to be photographed. Often we get to
 a very crude binary result: either everything is allowed, or nothing at
 all. And still most people seem to violate that simply.

 Hence, I was thinking whether a more personal and photo specific option
 would be available - allowing people to veto certain pictures before they
 get 'really' published. After all, Commons doesn't allow deletion simply
 because you dont like the quality or dont want to become public in that
 position.

 Would it be an option to create a staging area, where people can upload
 their event photos of Wikimedia events, and where people can simply veto
 their own pictures? The vetoing doesnt have to be water tight, but rather
 easy. A password to enter the staging area for that specific event could be
 given to the participants where they can check the photos and veto them.
 Then we can proceed with 'no veto = published' and mass upload the
 non-vetoed photos after a while to Wikimedia Commons.

 If we can develop this centrally (and make it available to all Wikimedia
 events) or install something on Wikimedia servers that already does this,
 that would save a lot of event organizers headaches. Any feedback, anyone
 who would be willing and able to pick this up?



This is a really good idea, Lodewijk!

Keeping track of who does and doesn't want their photos up on Commons
(and which photos they want) can be quite a hassle.

-Sage

___
Wikimedia-l mailing list
Wikimedia-l@lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l