Establish consistency standards in notebooks around (colab vs workbench)

[zeroasterisk]

Sometimes you have code blocks which are commented and you say to uncomment them, sometimes you have codeblocks which are uncommented and you say to comment them.

• https://github.com/search?q=repo%3AGoogleCloudPlatform%2Fgenerative-ai+workbench+comment&type=code
• https://github.com/search?q=repo%3AGoogleCloudPlatform%2Fgenerative-ai+workbench+uncomment&type=code

Instead, can we establish shared conventions for notebook set up, and ideally a runtime conditional allowing it to work in workbench and colab without editing. The fewer things a user needs to do to execute the colab, the better.

Other things to try to standardize on:

• auto-restart of the runtime after package install, if restart needed: https://g.co/bard/share/0df557a3a623
• params for anything you expect a user to edit, just to get the colab to run (eg: no private data stores)
• public sample data for anything you need to use (eg: no private data stores)

[holtskinner]

Related to this: We also should update the "Open In" Links to include Colab Enterprise, now that we can do that for notebooks in this repo. Not sure if we should replace Colab or Vertex AI Workbench or add another box.

URL Format: https://console.cloud.google.com/vertex-ai/colab/import/https:%2F%2Fraw.githubusercontent.com%2FGoogleCloudPlatform%2Fgenerative-ai%2Fmain%2Fgemini%2Fgetting-started%2Fintro_gemini_pro_vision_python.ipynb

[gericdong]

Thank you for the feedback! As @holtskinner commented above, there have been some discussions and work done to standardize notebook style across multiple runtimes. We are tracking the progress in those workstreams. As such we can close this request here.