community icon indicating copy to clipboard operation
community copied to clipboard

Create & Manage a Zowe Consumer Distribution List

Open RASakach opened this issue 2 years ago • 3 comments

What: An optional, opt-in Zowe Consumer Distribution list Why: The OMP has provided the Zowe Community with a Zowe Extenders Distribution list, we do not have a similar distribution list for Zowe Consumers and thus rely on Consumers to constantly check-in at Zowe.org, social media, etc. When: ASAP to begin sharing Zowe V2 information and educational opportunities

How: Present zowe.org visitors with an option to JOIN OUR MAILING LIST, where consumers will have the opportunity to add (or remove) their preferred email address. The mailing list will be made available to a limited number of designated Zowe Community Squad Members who will ensure appropriate usage.

The Onboarding Squad is looking for guidance and guidelines from OMP. @jmertic we are hoping you can assist with this request.

RASakach avatar Mar 22 '22 20:03 RASakach

Thanks for raising this @RASakach.

There currently is a https://lists.openmainframeproject.org/g/zowe-user list which probably would make sense to leverage, but not sure if that makes sense to use. It would also be good to know if this is more announcement oriented, or if there is expectation of interaction.

jmertic avatar Mar 23 '22 13:03 jmertic

I think this is done now? @RASakach

jmertic avatar Jun 30 '22 12:06 jmertic

@jmertic Creation is done. Thanks for the help.

We still need to figure out the management part.

balhar-jakub avatar Jun 30 '22 12:06 balhar-jakub

Idea for managing: (1) any new announcement should probably be sent to this list (2) a new OMP blog introduction / contents should be sent to this list (3) Onboarding will produce a policy on how this list is managed, maintained etc.

Finalization is in-progress

RASakach avatar Jan 13 '23 13:01 RASakach

When should we notify the Zowe-User distribution list?

  1. New release
  2. Roadmap update
  3. CVE notifications (once made public)

We agree, we should limit communication to avoid becoming "noise" We agree the communication should be limited to ~ 1 time per month We agree no ongoing maintenance is necessary (there is an opt-out option) We agree to ensure the communications are relevant and professional

RASakach avatar Apr 14 '23 12:04 RASakach