End result we have picked irc.libera.chat channel #wikimedia-quibble
I am still trying to properly lead the Quibble development and I can't tell I have been very efficient in creating a proper dynamic. @kostajh @awight and @hashar recently resumed weekly meetings which helps settling up decisions. I definitely have troubles allocating proper time to move the project forward and I am surely a review bottleneck.
There is probably a few people who might be interested in following the development in an asynchronous way, and I suspect that if we have a backlog that is easily readable by others, it might spurt interest in jumping into Quibble development to enhance it.
So this task is about creating a communication channels that could be used asynchronously and synchronously. My thoughts:
- Phabricator task such as this one is great for async communication, but lack some dynamic
- Visio conferences are great for sync work and discussion, we should keep those.
- A mailling list would fit the need of async comm, but I am pretty sure we all already receive too many emails
- IRC is excellent for sync communication but lacks backlog
Or to put it in a table:
| Medium | Sync | Async |
|---|---|---|
| Phabricator task | no | YES |
| Mailling list | no | YES |
| Visio conferences | YES | no |
| IRC | YES | no |
So well I am tempted to have a dedicated Slack channel. It has lot of benefits from mailing list (threaded conversations) and is almost appropriate for small sync communication as long as there are not too many people.
The Wikimedia Foundation has a Slack workspace and we can invite persons outside of the WMF (@awight , @Addshore or others from WMDE). Maybe that will help attracts MediaWiki developers as well and get them familiar with the tool.
Thoughts?