OpenSearch Dashboards Developer Office Hours - 2023-06-01

2023-06-01T17:00:00Z2023-06-01T18:00:00Z

Event page
Meetup page

Meeting Link

Meeting ID: 836 7647 0962
Passcode: 377355

Agenda

  • Slot 1: Open proposals and RFC review
  • Slot 2: Open
  • Slot 3: Open
  • Slot 4: Open

Maintainer topic: Proposal review for Discover 2.0 by @ashwinpc

Sign up for an open slot by replying in this thread with the following template, and we’ll update the agenda accordingly:

  • Topic: [a brief description of what you’d like to discuss]
  • Requested by: [provide GitHub aliases of attendees]
  • GitHub issue or PR links: [before signing up, make sure to create an issue, whether in the OpenSearch Dashboards repository or your own plugin repository]
  • Time required [choose 15, 30, 45, or 60 minutes]
  • Requested maintainer: [optional; provide GitHub alias of any particular maintainer) you’d like to attend]

If you’ve previously signed up, but can no longer attend, just let us know in the thread.

Format

The meeting is divided into four 15-minute slots for community developers to chat with OpenSearch Dashboards project maintainers. Priority will be given to topics that are signed-up in advance, but ad-hoc discussions are welcome in any remaining time. If there are no sign-ups, maintainers will present a brief knowledge-sharing session or demo and the meeting may end early. For more information and FAQs, see the OpenSearch Dashboards communication guide.

After the meeting, we will post the chat log here. We welcome you to keep the conversation going here on the forum, in GitHub, or on Slack.

========
By joining the OpenSearch Dashboards Developer Office Hours Meeting, you grant OpenSearch, and our affiliates the right to record, film, photograph, and capture your voice and image during the OpenSearch Community Meeting (the “Recordings”). You grant to us an irrevocable, nonexclusive, perpetual, worldwide, royalty-free right and license to use, reproduce, modify, distribute, and translate, for any purpose, all or any part of the Recordings and Your Materials. For example, we may distribute Recordings or snippets of Recordings via our social media outlets.

1 Like

Reminder - just add a note for @joshuarrrr and team to add to the agenda!

Thanks for joining us today (7 attendees)!

Here are some of the links and topics we covered:

  1. Proposal review for Discover 2.0 by @ashwinpc
  2. One general UI improvement is to examine the over-use of text truncation. In particular, we should open a new issue for data source truncation in dropdowns/selectors. Other known issues:
    1. [Discuss][Follow-up] Suggestion list cutoff behavior · Issue #2606 · opensearch-project/OpenSearch-Dashboards · GitHub
    2. Disable truncation in visualization legend · Issue #3278 · opensearch-project/OpenSearch-Dashboards · GitHub
    3. Truncate long fields in Discover server-side · Issue #3475 · opensearch-project/OpenSearch-Dashboards · GitHub
  3. Other active proposals worth reviewing:
    1. Navigation changes for administrative features
    2. Alternative storage for saved objects
  4. Current OpenSearch Dashboards initiatives and priorities:
    1. EOL Node version update
    2. Removing Angular.js dependency (migrate to React)
    3. Preparing for major look and feel updates via OUI compliance
  5. Ad-hoc discussion: Issue with the data source selector in the Alerting plugin
    1. We’ll move this issue to GitHub - opensearch-project/alerting-dashboards-plugin: 📟 Manage your monitors, alerts and notifications in OpenSearch Dashboards, and continue the discussion there - likely a straightforward fix by changing the endpoint: alerting-dashboards-plugin/OpensearchService.js at main · opensearch-project/alerting-dashboards-plugin · GitHub
    2. We may open up a campaign/issue to ensure all dashboards plugins have consistent data source selection experiences
    3. We’ll follow-up with the cross cluster replication maintainers to make sure they’re actively triaging issues.
  6. How to find the team on slack:
    1. Communication guide for OpenSearch Dashboards
    2. #dashboards channel for Dashboards
    3. #devrel channel to chat with developer advocates and get more involved in the project
3 Likes