I attended the same event as Fabian, and agree with all his comments. It was a fun night, and we could do even better this time..
We already have 25 MPs not standing again, so that's up to 25 new bios we'll need: https://en.wikipedia.org/wiki/United_Kingdom_general_election,_2017#Members_...
Based on the 2015 results plus the exit polls, we should have a very good idea who will win in each of those seats, and can start the draft pages accordingly, ready to go live as soon as the individual results are in. Have we ever had an editathon where we started more than 25 articles? 25 is plenty.
Along with Fabian, I'd be happy to be a trainer on the night, if any training is needed.
Edward Hands (Edwardx on WP)
On 26 April 2017 at 18:01, leutha@fabiant.eu wrote:
Hi all,
I would like to make several suggestions:
- Checkout the General Election 2015 Editathon wikipedia page
https://en.wikipedia.org/wiki/Wikipedia:Meetups/UK/General_Election_2015_Editathon: the aim was clearly stated: "We will endeavour to ensure that Wikipedia is up to date with the UK General Election https://en.wikipedia.org/wiki/UK_general_election_2015 results by the morning of 8th May." We had a link up with cy-wiki. There is a short video about the event and we and sponsorship from Cybersalon and used the basement in Development House. This worked well, even though we did have the Green Party try and persuade us to move somewhere else, somewhat ineffectively. If such an arrangement is to be repeated, the room should be booked soon, and a member of staff identified who would be happy to be present for the night. I did this in 2015, and I must admit it was great fun: a sociable way to stay up all night on election night and to contribute towards the sum of "the *sum of all* human *knowledge"! *There is little point in seeing it as a "training event" as those present were generally all experienced editors. But we did basically succeed with our aim, even if early birds coming on line the next morning also made an important contribution. I would be interested in being involved ifsomeone could arrange a venue and some support re snacks pizza etc. 2. As regards any event before hand, it would seem useful to check the timetable https://en.wikipedia.org/wiki/United_Kingdom_general_election,_2017#Timetable. As 11 may is the deadline for the delivery of candidate nomination papers, it would make sense to have any event after this. 3. We should keep in touch with people who already have built up experience working on UK elections. I know I found Bondegezou https://en.wikipedia.org/wiki/User:Bondegezou very helpful back in 2015. 4. At the risk of sounding hopelessly old-fashioned, it would seem to me be a good idea to move as much of this discussion onto Wikipedia itself as possible, to see how any event which is organised can best fit in with the existing activities of the community.
all the best,
Fabian Tompsett,
aka Leutha
On 24 April 2017 at 11:42 John Lubbock john.lubbock@wikimedia.org.uk wrote:
I think we should do one before. I suggested Sunday 7th May, and Ed has said we can use Newspeak House. So we need a trainer now. Anyone keen?
John
On 24 April 2017 at 08:33, Gordon Joly gordon.joly@pobox.com wrote:
On 21/04/17 18:15, John Lubbock wrote:
What about if we simply did a politics themed editathon after the election when the results had come in and we had something to work with?
With NPOV of course!
Gordo
Wikimedia UK mailing list wikimediauk-l@wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimediauk-l WMUK: https://wikimedia.org.uk
Wikimedia UK mailing list wikimediauk-l@wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimediauk-l WMUK: https://wikimedia.org.uk
Wikimedia UK mailing list wikimediauk-l@wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimediauk-l WMUK: https://wikimedia.org.uk
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Virus-free. www.avast.com https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>