Difference between revisions of "Water cooler"

From Wikimedia UK
Jump to navigation Jump to search
m (Added youtube link)
Line 77: Line 77:
 
    
 
    
 
[[User:LucyCrompton-Reid (WMUK)|LucyCrompton-Reid (WMUK)]] ([[User talk:LucyCrompton-Reid (WMUK)|talk]]) 13:39, 21 September 2017 (BST)
 
[[User:LucyCrompton-Reid (WMUK)|LucyCrompton-Reid (WMUK)]] ([[User talk:LucyCrompton-Reid (WMUK)|talk]]) 13:39, 21 September 2017 (BST)
 +
 +
== ACTRIAL and new users creating new pages at events ==
 +
 +
Hi All,
 +
 +
Some thoughts on {{wp|WP:ACTRIAL}} and our events:
 +
*It makes sense to encourage new users to work in Draft: name space.
 +
*This doesn't change the fact that it is worth asking people to create an account in advance (and to remember their password!)
 +
*We have to expect that some people won't create an account and most of those who have won't be auto-confirmed - this is OK.
 +
*If there are admins present at the event, they can make new users confirmed.... although I wouldn't stress over it - there is no harm in the Draft: name space.
 +
*All the above is less of an issue if we take the approach of [[#Training from the back of the room]] described above.  If the group is split into teams that are deliberately set to have the full spread of ability, we can encourage people to help other team members, including the following:
 +
**Middle-ability people to show the people with no account how to create an account.
 +
**Experienced editors to help newer editors to find a page that might need editing.
 +
**Experienced editors to create pages that other team members are interested in editing.
 +
You could even get admins to confirm accounts of non-confirmed people in their team, but it might actually be better to not do that.  If the experienced people in the team have actually created the article then at least we know it is in their contributions and so they can steward the article towards improvement. e.g. 1. the day after the event, they might go back to the article and tidy it up, 2. if the article gets tagged for deletion, they are better able to discuss it and improve it, whereas a new user may feel bitten.
 +
 +
[[User:Yaris678|Yaris678]] ([[User talk:Yaris678|talk]]) 14:44, 25 September 2017 (BST)

Revision as of 14:44, 25 September 2017

Welcome to the water cooler
This is a place to find out what is happening and to discuss our external projects and activities. Feel free to suggest ideas that could help our charitable mission or ask questions about how you can help. To discuss the inner workings of the charity, head over to the engine room.
WMUK Grants programme - a piece of cake?
Tile wmuk.jpeg
Applying for a grant is easy.

If Wikimedia UK can help you improve Wikimedia projects, check out our grants page.

Archives.png
2009
2010
2011
2012
2013
2014
2015
2016
2017

Kanban for editathons

A kanban board at the Women in Classical Studies editathon at Senate House, London

I just saw the newsletter with a picture of the kanban board used at the Women in Classical Studies editathon. What a great idea! It helps people share what they are working on. Helps to avoid edit conflicts. Enables organisers to list all the articles that have been improved. It could possibly work well for a recap session at the end too, where people talk about the changes they made.

Who was involved with that editathon? Who has used it elsewhere? I would love to hear how it has been used in practice.

Yaris678 (talk) 15:09, 3 February 2017 (GMT)

Hi Yaris678, I was the lead trainer at the Women in Classical Studies editathon. I saw the kanban in an Instagram post for an Art+Feminism editathon. It worked much better than expected - a fantastic indicator of the achievements of the day.Eartha78 (talk) 19:02, 3 February 2017 (GMT)
Cool. So how did you use it? Did you get people to brainstorm a load of post-its of articles to look at, at the beginning of the day? Did you just say 'if you have an idea, stick it on the board'? Did you come with the post-its filled out already? Yaris678 (talk) 10:25, 11 February 2017 (GMT)
The group were quite well prepared prior to the editathon. They had identified a number of articles to create - some had already done the research and started to writing in their sandbox. When we began the second part of the editathon they each committed to an article, wrote it on a sticky note and stuck it to the wall! Moving the notes from left to right was surprisingly motivating and a good excuse to stretch ones legs. Also used the sticky notes for an evaluation exercise at the end of the session. Eartha78 (talk) 18:27, 16 February 2017 (GMT)
Thank you Eartha78. That is really interesting. I will use this next time I do an editathon. Yaris678 (talk) 09:39, 19 February 2017 (GMT)

Training from the back of the room

Another idea for editathons: Training from the back of the room. I recently went to a training course that used this approach and it was really good. I think it would work particularly well with something like an editathon, which isn't branded as training.

Rough outline of how it could work:

  • After basic intros, etc, ask people to stand up and arrange themselves in order of experience of editing Wikipedia. Speak to the people next to get an idea of their experience.
  • Get the people at each end of the group to talk a little bit about there experience, so we all know the range of experience in the room.
  • Split the group into small teams of ~4 people. Say that is 4 groups, number the line 1,2,3,4,1,2,3,4... etc and everyone with the same number is in the same group. That way the teams all have a range of experience.
  • Get people to explain to their team mates:
    • What they normally do on Wikipedia
    • What they would like to do today
    • Anything they see that might stop them from achieving what they want to do today
  • If there are specific articles to edit, these can go on the kanban board
  • Perhaps other types of aims like "understand referencing" should be written on a flip chart that each team has
  • Organisers should also bring topics to put on the kanban board
  • Encourage people to work as a team on a topics
    • The best way to do this needs thinking about, perhaps something like Mob programming
    • Perhaps do something like two people look at references. One (relatively inexperienced) person does the typing and one person guides that person.
    • The general idea is to encourage people to work together and share there skills
  • If we have a number of trained trainers at the editathon, they would still be part of a team, and help their team achieve its goals.

Yaris678 (talk) 10:28, 11 April 2017 (BST)

Wikimedia UK's plans for 2018 - community consultation

Wikimedia UK is in the process of writing our proposal to the Wikimedia Foundation for funding during 2018/19. The deadline for the bid is 1st October after which it is assessed by staff at the Foundation, there is an opportunity for community feedback and questions, and the Funds Dissemination Committee (FDC) meet to consider proposals and make recommendations about grants.

As 2018/19 is the final year of our 2016 - 2019 strategy, our programme for next year is in many ways a continuation of our activities in 2017 and falls under three key strands:

  1. Diverse content and contributors
  2. Promoting open knowledge
  3. Education and Learning

These strands are directly related to our three strategic goals, which are to:

  • Increase the quality and quantity of coverage of subjects that are currently underrepresented on Wikipedia and the other Wikimedia projects
  • Contribute to the development of open knowledge in the UK, by increasing understanding and recognition of the value of open knowledge and advocating for change at an organisational, sectoral and public policy level
  • Support the use of the Wikimedia projects as important tools for education and learning in the UK

We would welcome input from the UK community into our plans for next year - which we are still shaping - and have created a short video to highlight our programme strands which you can watch here. You can give us feedback on our programme anytime, but if you’d like your views to be taken into account in our submission to the Wikimedia Foundation for funding, please do comment below by Friday 29th September. If you’d prefer to get in touch by email, feel free to contact me on lucy.crompton-reid@wikimedia.org.uk.

There are several questions in particular that I’d like to ask:

  • Is there anything that Wikimedia UK should be doing more of, or new activities that we should consider, in 2018/19?
  • What work would you like to see us continue?
  • Is there anything you think we should do less of or stop doing?
  • How would you like to be involved in Wikimedia UK’s programme next year?

With many thanks indeed for your input.

LucyCrompton-Reid (WMUK) (talk) 13:39, 21 September 2017 (BST)

ACTRIAL and new users creating new pages at events

Hi All,

Some thoughts on WP:ACTRIAL and our events:

  • It makes sense to encourage new users to work in Draft: name space.
  • This doesn't change the fact that it is worth asking people to create an account in advance (and to remember their password!)
  • We have to expect that some people won't create an account and most of those who have won't be auto-confirmed - this is OK.
  • If there are admins present at the event, they can make new users confirmed.... although I wouldn't stress over it - there is no harm in the Draft: name space.
  • All the above is less of an issue if we take the approach of #Training from the back of the room described above. If the group is split into teams that are deliberately set to have the full spread of ability, we can encourage people to help other team members, including the following:
    • Middle-ability people to show the people with no account how to create an account.
    • Experienced editors to help newer editors to find a page that might need editing.
    • Experienced editors to create pages that other team members are interested in editing.

You could even get admins to confirm accounts of non-confirmed people in their team, but it might actually be better to not do that. If the experienced people in the team have actually created the article then at least we know it is in their contributions and so they can steward the article towards improvement. e.g. 1. the day after the event, they might go back to the article and tidy it up, 2. if the article gets tagged for deletion, they are better able to discuss it and improve it, whereas a new user may feel bitten.

Yaris678 (talk) 14:44, 25 September 2017 (BST)