Due: 2:30 PM Friday (Europe), March 31 Title: What's new and exciting in JupyterHub abstract for JupyterHub JupyterCon talk Speakers: Min (@minrk) Erik (@consideRatio), erik@2i2c.org anyone else? It's a short slot
5/10/2023Title: Restructuring and improving JupyterHub Documentation Using the Diátaxis framework: Experience and Lessons Audience: The talk targets anyone who authors or contributes to open-source software documentation, including technical writers and team leads. The audience can be working with any programming language but should have intermediate knowledge of technical writing practices, including what it entails and some of the tools used. Summary: JupyterHub has a range of documentation that covers both developer and user audiences in order to help them deploy, maintain, and use their own instance of a JupyterHub. The success of an open source software project to (i) be adopted by users, and (ii) receive meaningful contributions relies heavily on the quality, navigability and accessibility of documentation so that users and developers have all the information they need to achieve what they want to do. A framework for organising technical documentation has arisen called Diátaxis. It takes a systematic approach to understanding user requirements of documentation throughout the lifecycle of interaction with a product and posits that different user needs require different approaches in creation of the documentation, as well as a layout to navigate these different “modes” of documentation.
12/15/2022Title: Improving Accessibility in JupyterHub Audience: Beginner and Intermediate developers who have a good knowledge of HTML and CSS are the intended audience. Knowing what Web accessibility is and how WAVE is used to evaluate the accessibility of web applications is a plus but developers with no knowledge of this can see it demonstrated and easily understand how it works. Summary: Accessibility is the ability of tools (in our case web tools) to be used by a variety of communities with different disabilities. There are a variety of standards and tools for evaluating and ensuring that a web page can be used effectively by as many people as possible. A few of these tools include but aren't limited to WAVE accessibility testing tool and axe DevTools. There is ongoing work by the Jupyter Accessibility team to define a set of standard practices and tools to improve accessibility across the Jupyter ecosystem. During Outreachy's December cohort for 2022 which ran for three months, one of JupyterHub's projects was to improve the accessibility of JupyterHub, implementing the guidelines of the Jupyter Accessibility team. The goal of the project was to ensure we are providing tools that are as useful as they can be to as many people as we can. During the internship, I was the intern that, together with the community, worked on making this happen. We:
12/14/2022Questions we want to be able to answer: What does component X need to talk to (directly), e.g. Hub->proxy, proxy->singleuser/hub, etc. If credentials for component X are compromised, what actions could be taken, and how can I detect/mitigate this? Where are credentials for component X typically stored? If the process of component X is compromised, what actions could be taken? What configuration options mitigate vulnerabilities (e.g. disable_user_config, token expiration, user scopes, session expiration, etc.) Outline looks something like:
8/5/2022or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up