-
Notifications
You must be signed in to change notification settings - Fork 34
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
Simplification #887
base: master
Are you sure you want to change the base?
Simplification #887
Conversation
Signed-off-by: Jakub Balhar <jakub@balhar.net>
Signed-off-by: Jakub Balhar <jakub@balhar.net>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the simplification except for the removal of the community tab which is very important to how I use & instruct new people to use the website.
It was suggested that https://docs.zowe.org/stable/contribute/roadmap-contribute and https://openmainframeproject.org/community/ can sufficiently replace the community tab, but I strongly disagree.
https://docs.zowe.org/stable/contribute/roadmap-contribute does a bad job at replacing the current "community" page.
it's focus is on code contribution, which is just one of several important parts of community.
the community page gives me quick access to highly useful activities. the page jumps right out at you:
Slack: here's good slack channels
Meetings: where to find us
Github: quick links to 2 major repos
the docs page instead is a lot of words about how to search github and write code.
it contains a very minor shoutout about the existence of slack, within a code-focused context, such that the fact slack exists at all could be missed in that page.
and that page does not list the meetings whatsoever
the OMP page https://openmainframeproject.org/community/ is more similar, but wrong focus. it's focused at the OMP level. it leads to a forum that zowe people do not regularly visit, a github link that is not zowe, but it does include Slack which is good since it's the top way people interact with us.
what's the OMP page numbers though? less or more? do you go to the OMP's website to find Zowe things?
The community page needs to be kept because neither of those pages do a good job of replacing it. It'll just lock out people who want to join us because they won't know how.
@1000TurquoisePogs Basically what I hear is we need to make sure that we have one place for anyone joining to learn about the community. E.g. Slack link and key channels, calendar and potentially other key resources. As these things doesn't really change and we already have quite a lot of it in Zowe docs, we should probably make sure that we have proper content in Zowe Docs, rather than here. The main concern for me is that amount of traffic and usage for this site. This is for last 90 days. 256 visits for 119 users which include us. But maybe keeping this information should belong here if we aim to have zowe.org for newcomers and docs site for those using Zowe. |
Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
…sc/zoweorg/simplify
Based on the Feedback from you Sean Grady and thinking about it going forward there is the Community page again with the OMP Calendar it feels like a good candidate for the zowe.org On the other hand I would like to discuss moving the vNext page information to the Zowe Docs. It feels like more natural place for it. |
Add landscape to Community Add Future to the vNext Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
@1000TurquoisePogs Does this change reflect your original concerns? |
Add link to the OMP Conformance Add the landscape for Support. Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
Signed-off-by: Jakub Balhar <jakub.balhar@broadcom.com>
No description provided.