Categorize Google Group lists for Datahub

[balajialg]

We currently have the following lists created to handle varied scenarios,

• ds-infrastructure@lists.berkeley.edu to handle instructor support queries and receive automated alerts from monitoring systems.
• datahub-announce@lists.berkeley.edu to broadcast announcements and solicit inputs from instructors.

@felder and I realized that we might need to create two other google groups with different objectives,

• Data retrieval requests: While serving Data retrieval requests. Signed files are currently sent from @felder's email id which may not be the best way to handle this support request going forward. Given the fact that Caesar and Sara (Student) will support these requests in the near future, there is a need to create datahub-dataretrieval@lists.berkeley.edu or some kind of a list which can be used for sharing the files and includes the relevant stakeholders to track the communication. This list should have Shane, Jonathan, Caesar, Sara, and Myself to track the communication.

• Operations update: We should reconsider receiving operations updates in the ds-infrastructure list as there are a bunch of nontechnical stakeholders receiving these alerts. Maybe, create an operations list that receives alerts and notifications from the monitoring systems and have Shane, Jonathan, Ryan, and (if required) myself looped in? This way ds-infra is only used for instructor support queries and nothing else.

Open to your thoughts on this proposal and the best way forward!

[balajialg]

@shaneknapp and @felder created a new SPA called datahub-support@berkeley.edu. Need to check whether this is specific to data retrieval requests or for operations update in general!

[ryanlovett]

@balajialg Just FYI that a SPA doesn't have the same properties as a mailing list / google group, which was the intention of the first post in this issue. If the eventual decision to create the support address as a SPA was intentional then sorry for the intrusion. :)