You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful to create a unified set of "Get Help" resources/pages that can be deployed/adapted to individual subproject sites, listing the discourse forum, github issues, weekly meeting(s), and other venues for people to connect with help and other resources/expertise. There are many ways to connect with the Jupyter community, we should document them clearly and comprehensively and provide links.
The text was updated successfully, but these errors were encountered:
This should be merged with the current "Get Involved" page of Jupyter.org, I guess.
As a matter of fact, that page ("Get Involved") could be simplified to sections "get help", "contribute", "(calls for) workshops", and "conferences" (JupyterCon).
The document (get_involved.md) in PR #28 tries to organize the different channels somebody with specific doubt/requests or, instead, general questions can go for discussions.
It's good that you're thinking about possible consolidation and topic organization. Here's how I see it:
"Get Help" should be a dedicated single-topic page focused on actions for getting help
"Get Involved" on jupyter.org can probably be consolidated into sections as you mention, but possibly might be better by deep linking to separate pages (with single focused topics) so it feels less overwhelming, perhaps
Because of its length and general heaviness, maybe we should consider breaking up the existing "Get Involved" content into additional separate focused pages and only include short sections with summary info and deep links
I'll take this issue and work something up, then we can sync up on the other page efforts to ensure we're happy with the page structure and content organization :)
It would be helpful to create a unified set of "Get Help" resources/pages that can be deployed/adapted to individual subproject sites, listing the discourse forum, github issues, weekly meeting(s), and other venues for people to connect with help and other resources/expertise. There are many ways to connect with the Jupyter community, we should document them clearly and comprehensively and provide links.
The text was updated successfully, but these errors were encountered: