Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next SHARE planning & execution (Kansas City) #2222

Open
RASakach opened this issue Apr 18, 2024 · 2 comments
Open

Next SHARE planning & execution (Kansas City) #2222

RASakach opened this issue Apr 18, 2024 · 2 comments
Assignees
Milestone

Comments

@RASakach
Copy link
Contributor

Plan for upcoming SHARE / GSE conferences

Determine the general, desired plan for the Zowe Track

Ideally, Zowe day
Alternatively a progressive set of Zowe sessions throughout the week

Focus on:
Zowe Administration, use, troubleshooting (recognize that customers are beyond install and want to dig deep in actual use)
Use Cases: All UC sessions should be presented by / accompanied by CUSTOMERS
V3: No focused topic, but should have a slide in all Zowe sessions
ZEN:

Consider a thoughtful division between client-side technology and server-side technology

@RASakach RASakach self-assigned this Apr 18, 2024
@RASakach RASakach changed the title Next SHARE planning (Kansas City) Next SHARE planning & execution (Kansas City) Apr 18, 2024
@RASakach
Copy link
Contributor Author

RASakach commented May 3, 2024

Rose (as track leader) has reviewed all of the Zowe sessions, most were recommended to be accepted.

Action items:

  1. Where does the acceptance stand?
  2. For customers presenting, reach out and get details on their topic to help promote and assist if desired.

@RASakach RASakach added this to the 23PI3 milestone Jul 11, 2024
@RASakach
Copy link
Contributor Author

Waiting on 1 customer that may be attending. Expect to hear in the next 2 weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant