P. T. Deutermann

• Aviad.rubinstein (t · th · c · del · cross-wiki · SUL · edit counter · accounts created · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)⁽⁾

I'm co-organizing an edit-a-thon at an academic conference: https://outreachdashboard.wmflabs.org/courses/EC_conference/EC'25_Wiki_edit-a-thon?enroll=owsebpjm

EC (https://ec25.sigecom.org/) is the main academic conference at the intersection of Economics and Computer Science. We're hosting an edit-a-thon to encourage conference attendees to edit, with a focus on technical entries at the interface of our research and general public interest. Aviad.rubinstein (talk) 17:51, 2 July 2025 (UTC)[reply]

That link is dead. Also, if you're using the programs and events dashboard, you should set up the dashboard to allow people to request accounts, which would obviate the need for you to have event coordinator access. * Pppery * _{it has begun...} 18:54, 3 July 2025 (UTC)[reply]

• Effeietsanders (t · th · c · del · cross-wiki · SUL · edit counter · accounts created · non-automated edits · BLP edits · undos · manual reverts · rollbacks · logs ^{(blocks · rights · moves)} · rfar · spi · cci) (assign permissions)⁽⁾

Reason for requesting event coordinator rights I occasionally help out with events - and expect to do this again more often in the future (recently in the Bay Area, going forward in the Netherlands). Being able to create accounts without hitting rate limits due to event-shared wifi would be helpful! In a pinch, I could rely on my adminship in nlwiki, but that feels like an undesirable workaround. This request is triggered specifically by an event on 8 July 2025 at Stanford (which is also referenced by Aviad above), but will be useful beyond that. effeietsanders 00:44, 8 July 2025 (UTC)[reply]