Mailing list IRC support rotation » History » Revision 18
Revision 17 (Greg Farnum, 12/12/2022 01:51 PM) → Revision 18/26 (Greg Farnum, 01/10/2023 01:30 AM)
h1. Mailing list IRC support rotation Rotated weekly: * Jan 7-Jan 14: Dec 10-Dec 17: Patrick/Rishabh * Jan 14-Jan 21: Dec 17-Dec 24: Xiubo/Jos * Jan 21-Jan 28: Dec 24-Dec 31: Milind/Neeraj * Jan 28-Feb 4: Dec 31-Jan 7: Kotresh/Dhairya * Feb 4-Feb 11: Xiubo/Rishabh * Feb 11-Feb 18: Patrick/Jos * Feb 18-Feb 25: Kotresh/Neeraj * Feb 25-Mar 4: Milind/Dhairya ... RINSE AND REPEAT. The goal is to: - develop a close understanding of how our product gets used in the field - seek early user feedback on features - identify gaps in functionality/UX (kind of related to the point above) The system is as follows: Support watch consists of a couple of people every week monitoring the ceph mailing list, identifying issues/topics relevant to CephFS, helping users with the issues they are running into and/or reporting new bugs. Broadly, this involves the following tasks: 1. For a CephFS related query in the mailing list, determine if it's an issue with user confusion or if it's a bug. 1.a If it's a user issue, explain to them how to get it done. This would (normally) involve reading through the documentation and providing suggestions to the user. In many cases, the issue/confusion is due to unclear (confusing) documentation, and this would be a good time to make our docs better (doc PRs!). 1.b If it's a bug, identify existing tracker tickets that match symptoms or create one and share that with users. 2. Share a short summary with the team (in a common google-doc) about what issues users ran into. 3. If the mailing list conversation spills over to the next week (maybe due to delayed response by the user), the "involved" person should still take the conversation to a conclusion (bug vs user issue). Also, note that this applies keeping a close look on IRC channels too, however, mailing lists are where the bulk of users would be seeking help.