Page MenuHomePhabricator

A new events/meet-ups extension
Open, LowestPublic

Description

I will not be at the hackathon but wanted to propose this idea, even if only to get some feedback about it. Many wiki communities host various events; editathons, hackathons, workshops, conferences, writing contests, meet-ups, etc, which are often listed in the Wikipedia namespace. It would allow for consistent tracking of information, so we can know the outputs and outcomes of events. How many bytes added or removed? How many people attended? How many articles were created or improved? how many photos uploaded by the users? How many talk page interactions? How many editors are still retained?... etc. etc. etc... It would also be easier to put together an event.

The user would be anyone organizing in-person or online events, or anyone attending these events.
The features might include:

  • Locking in a start/end time (in UTC)
  • Ability to "register" for the event
  • Type of event
  • Attendee registration
  • Resources (e.g. learn how to edit a wiki)
  • Data tracking (usernames, bytes added, bytes removed, articles created, etc.), perhaps with the use of bots
  • Space for additional information/ability to customize the event page as needed
  • Ideally, the same event could be simultaneously posted on more than one wiki, for example, some editathons have two languages, and the data tracking would also include more than one wiki.

Some more information from IdeaLab and User:AnotherBeliever:
https://meta.wikimedia.org/wiki/User:Another_Believer/Meetups
https://meta.wikimedia.org/wiki/Grants:IdeaLab/Meetup_Page_Creation_Tool

An example writing contest page:
https://et.wikipedia.org/wiki/Vikipeedia:Eesti-Armeenia_koost%C3%B6%C3%B6n%C3%A4dal

This one uses a bot to update the stats:
https://no.wikipedia.org/wiki/Wikipedia:Ukens_konkurranse/Ukens_konkurranse_2014-10

An example of a collection of related events:
https://en.wikipedia.org/wiki/Wikipedia:Meetup/ArtAndFeminism

Event Timeline

egalvezwmf raised the priority of this task from to Needs Triage.
egalvezwmf updated the task description. (Show Details)
egalvezwmf subscribed.

I think this proposal should be advertised among organizers of such events.

My first impression is that it is a too ambitious project, and that perhaps a single extension is not the best tool to solve all that. However, I have never organize an editathon...

This is an interesting task. Thanks for filing it. :-)

I agree with @Qgil that we'd need to break this down a bit further, but it's definitely feasible.

Aklapper lowered the priority of this task from Low to Lowest.Jun 25 2015, 9:44 AM

Adding Possible-Tech-Projects in an attempt to get more community attention. Removing Developer-Advocacy because the topic is out of scope for us.

This is a message posted to all tasks under "Backlog" at Possible-Tech-Projects. Outreachy-Round-11 is around the corner. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.

This is a message sent to all Possible-Tech-Projects. The new round of Wikimedia Individual Engagement Grants is open until 29 Sep. For the first time, technical projects are within scope, thanks to the feedback received at Wikimania 2015, before, and after (T105414). If someone is interested in obtaining funds to push this task, this might be a good way.

I wonder how different would this extension be to the Education Program extension. Maybe we can just merge this task to T91676: [Epic] Make the Education program dashboard usable for all languages and projects?

There could be many possible ways to tackle the needs described here. I think the Dashboard would be one good way, but it has perhaps more externalities than, say, building a narrowly-scoped MediaWiki extension for meetups and events.

I think education might be a specific case. This idea is more broad. It would include WLM, Editathons, Ed program, GLAM maybe. Here is a great example of WMNO, that pulls stats directly onto the page. But it would be great if this was more integrated and require less overhead, as well as ability to aggregate all metrics across all events. That would be sweet.
https://no.wikipedia.org/wiki/Wikipedia:Ukens_konkurranse/Ukens_konkurranse_2014-10. I think @Abit might already be working with someone internally on this, but I'm not sure.

Yes, I am trying to rustle up some developers to augment the Wikimetrics API such that it can be used to calculate Global metrics on event pages, and build an event template that does that, similar to the Norwegian page egalvez linked. I would also like to eventually integrate any features that would make this the most broadly useful event template possible, such as a "register" button and such.

It seems, talking to developers and event organizers, that this Phabricator task encompasses two different needs that can be fulfilled two different ways:

  1. for an event template that an event organizer can set up quickly and easily, that builds previously manual tasks into the template. This is what I am currently working on above.
  2. for a larger off-wiki system to manage multiple related events, such as series of edit-a-thons or writing contests. There is a project to make this from the Wiki Ed dashboard Education-Program-Dashboard but as I understand it is currently stalled due to lack of developer support. Perhaps @Ragesoss or @awight know more.
IMPORTANT: This is a message posted to all tasks under "Need Discussion" at Possible-Tech-Projects. Wikimedia has been accepted as a mentor organization for GSoC '16. If you want to propose this task as a featured project idea, we need a clear plan with community support, and two mentors willing to support it.
Qgil added a subscriber: Elitre.

I think education might be a specific case. This idea is more broad. It would include WLM, Editathons, Ed program, GLAM maybe.

It looks like Education-Program-Dashboard is going toward this direction?

I think Possible-Tech-Projects should be removed from this task.

Yeah, the "Program and Events Dashboard" may be relevant here. Notice it's a tool though, not an extension.
(Notice that both the title and the FAQ page are highly temporary at this stage.)

Normally with something like this, I would say "try it as a tool first," but we already have tools around this. Is the raison d'être for this task that tools are not good enough and this needs to be integrated into the structure of MediaWiki?