We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Jupyterlab notebook availability to switch conda environments
Currently when users work on the command line via ssh, they have a solution for creating user virtual environments and self install packages at their will.However, when they work from Jupyterlab, things are a mess: 1. users don't have access to conda virtual envs 2. users can install anything from pip, without environments, under .local, which introduces broad conflicts One possibility we have discussed is enabling the nb_conda_kernel extension and see if that can be used to allow users to switch environments back and forth, but there may be others. Unfortunately we have not yet been able to create one single new environment that worked correctly in this way.
Do not place IBM confidential, company confidential, or personal information into any field.