Change Details

**Type of activity:** "Pre-scheduled session" **Main topic:** None == The problem == At the October 2016 Editing offsite, we built some consensus around a minimum viable product for real-time collaboration. Unfortunately, one of the features axed from the MVP was real-time chat, because it's hard. This was the right decision for the MVP, since users can type at each other in the editing session and there wasn't consensus on how to build a safe and "wiki" chat feature. But let's not leave it there. Let's try to tackle the hard problem. Let's figure out what real-time chat for a wikimedia project *should be*. We'll probably fail a number of times before we get it right, but we need to start trying. == Expected outcome == Some visions for how real-time chat should work on our projects, with an understanding of the associated legal and social issues. A plan for dealing with archives, harassment, and patrol and for keeping the focus of the feature on the work of the projects. == Current status of the discussion == There have been a few strawmen, for example: * Embed a web IRC client, with a chat room name based on the article name. Punt the administrivia to the IRC networks. Some discussion at https://office.wikimedia.org/wiki/Editing_Offsite_2016_Notes/Real-time_collaboration * Something based on Flow or Echo * "Like Google Docs does" == Links == * ...

**Type of activity:** "Pre-scheduled session" **Main topic:** None == The problem == At the October 2016 Editing offsite, we built some consensus around a minimum viable product for real-time collaboration. Unfortunately, one of the features axed from the MVP was real-time chat, because it's hard. This was the right decision for the MVP, since users can type at each other in the editing session and there wasn't consensus on how to build a safe and "wiki" chat feature. But let's not leave it there. Let's try to tackle the hard problem. Let's figure out what real-time chat for a wikimedia project *should be*. We'll probably fail a number of times before we get it right, but we need to start trying. == Expected outcome == Some visions for how real-time chat should work on our projects, with an understanding of the associated legal and social issues. A plan for dealing with archives, harassment, and patrol and for keeping the focus of the feature on the work of the projects. == Current status of the discussion == There have been a few strawmen, for example: * Embed a web IRC client, with a chat room name based on the article name. Punt the administrivia to the IRC networks. Some discussion at https://office.wikimedia.org/wiki/Editing_Offsite_2016_Notes/Real-time_collaboration (NOTE) FIXME: This link requires special permissions. * Something based on Flow or Echo * "Like Google Docs does" == Links == * ...

**Type of activity:** "Pre-scheduled session" **Main topic:** None == The problem == At the October 2016 Editing offsite, we built some consensus around a minimum viable product for real-time collaboration. Unfortunately, one of the features axed from the MVP was real-time chat, because it's hard. This was the right decision for the MVP, since users can type at each other in the editing session and there wasn't consensus on how to build a safe and "wiki" chat feature. But let's not leave it there. Let's try to tackle the hard problem. Let's figure out what real-time chat for a wikimedia project *should be*. We'll probably fail a number of times before we get it right, but we need to start trying. == Expected outcome == Some visions for how real-time chat should work on our projects, with an understanding of the associated legal and social issues. A plan for dealing with archives, harassment, and patrol and for keeping the focus of the feature on the work of the projects. == Current status of the discussion == There have been a few strawmen, for example: * Embed a web IRC client, with a chat room name based on the article name. Punt the administrivia to the IRC networks. Some discussion at https://office.wikimedia.org/wiki/Editing_Offsite_2016_Notes/Real-time_collaboration (NOTE) FIXME: This link requires special permissions. * Something based on Flow or Echo * "Like Google Docs does" == Links == * ...