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